I've developed an Android app which has replaced two previous systems written in J2ME. My boss has the old source code and needs it compiling for Samsung tocco phones. Which sdk/jar file do i need in Eclipse to make the source code compile?
I've had a look on the samsung web site but can't seem to find anything. Also it's not clear which operating system the Tocco phones use.
thanks in advance Matt
You may try installing Samsung SDK 1.2.2 for the Java ME platform:
http://developer.samsung.com/java/tools-sdks/New-Samsung-Java-SDK-1-2-2-release-28th-October-2010
And then taking the steps on how to create a Hello world with it:
http://developer.samsung.com/java/tools-sdks/Developing-HelloWorld-MIDlet-using-Samsung-SDK
Related
I have a Unity project that I'm switching from APKs to AABs (app bundles). Previously, when I was building it as an APK, the Google Play Console told me the APK was 64-bit compliant.
Now that I'm building an aab, I'm getting the warning:
This release is not compliant with the Google Play 64-bit requirement.
The following APKs or App Bundles are available to 64-bit devices, but
they only have 32-bit native code
I have both ARM7 and ARM64 architectures set.
I am excluding x86.
When I open the .aab in an archive viewer, the lib folder has all of
the .so's for both arm64-v8a and armabi-v7a.
I'm using IL2CPP, .NET 4.x
I'm using Unity 2018.3.7f1
My ndk version is 16b
My
Android Studio is up to 3.4.2 and gradle is 3.2
A lot of similar threads here talk about following the "Learn more" links, which I've done. I had already done all of the work to get my app 64-bit compliant before switching to app bundles.
Other threads talk about Android Studio solutions, which I can't use because my automated build process involves building with Unity from command line, so it has to be Unity configurations or bust.
My expectation was the app bundles were supposed to be the hot new way to let Google build better APKs for you, but it seems like it's getting confused on whether or not aabs are actually 64-bit compliant, which seems to defeat the whole purpose.
Is this a Unity problem, does Google have an error in their system with regards to app bundles, or is there some other step I'm missing?
For those who have this problem since yesterday (August 19, 2019):
In Player Settings > Other Settings you must now uncheck the x86 box (It is for the 32-bit Intel architecture).
You will now only have the following warning:
The device types on which your application can be installed will be more restricted.
But, in my case, it drops from 12392 devices to 12385 devices.
Here is the opinion of a Unity member on the issue:
x86 is used by less than 0.4% of all Android devices, so it shouldn't have any real impact.
x86 target will be removed completely in Unity 2019.3.
It looks that there was a bug in the Play Console where this message was displayed even when the AAB was compliant. This should have been fixed last Friday afternoon.
Try again now.
I recently start using Intel XDK. I found that for each platform creation my code will go to Intel cloud center to perform the build. Its a feature mentioned at Product Brief Intel® XDK.
Can I build that locally? I mean can I build locally in my system itself using Intel XDK? If so, then how?
are you afraid of intel knowing your code? in cordova\html5 app your code is available to anyone just get the apk from the store open with winrar and your code is there
if you want offline build there is no problem just read the cordova\phonegap docs step by step.
As you, I needed to build locally my application, principally to debug once Intel XDK, at least in the version 1621, does not provide support to load third-party-plugins(eg: PhoneGap Push Plugin) on Intel App Preview debug mode. Another problem was generate an iPhone build for beta tests.
My solution was, as the others suggested, to create an similar cordova project and copy the main files from my Intel XDK Project, www folder to be more specific. Config files will be found in platforms folder once you build using cordova/phonegap.
It allowed me to build for android on my machine. Debug was easy using "Chrome Inspect" because cordova generates an debug-unaligned.apk.
Allowed me to have access to the iOS build files, this is a good thing to do if you want to build using Xcode instead.
I Hope it help you.
This may be an incredibly stupid question, but I have not gotten a clear answer through google. Will the eclipse Blackberry plugin work for the new Blackberry as well as older versions? I am actually an android developer so this is quite a change for me. Any hint will be appreciated. Thanx
EDIT You can use the BlackBerry Runtime for Android apps to run Android Jelly Bean 4.2.2 (10.2) platform applications on the BlackBerry 10 OS. If you are developing for a previous version of BlackBerry 10 OS, use Android Gingerbread 2.3.3. To use the runtime, you must first repackage your Android applications to BAR file format, which is the compatible file format required for an application to run on the BlackBerry 10 OS.
Got this from here. Does this mean that I should write two apps? One for the old blackberry devices and one for the new one?
I'm not sure that the above is clear, so thought I would restate the position as I understand it:
Android applications, repackaged to run on BlackBerry devices, can be used on BB10 and PlayBook devices only. These can not be run on BBOS devices, i.e. BB 5/6/7.
The later releases of BB10, specifically 10.2+, supports Android applications developed using Jelly Bean 4.2.2.
PlayBook and previous levels of BB10, support Gingerbread 2.3.3.
So for example, my Z10, which is running BB10.1, would only be able to load repackaged Android applications developed using Gingerbread. My Curve, running OS 7.0, can't run any Android applications.
I'm following a tutorial that utilizes the Motorola Java ME sdk for device profile customization, as it uses quite a user-friendly UI, but this SDK seems to no longer exist. Can anyone suggest an alternative?
I'm using netbeans as my IDE.
Currently you can't find any Motorola emulator for Java ME. Because they fully moved to Android. So better you can try with some other emulator for Java ME.
I have installed android tools and eclipse successfully (making the hello World and hello widget examples) and have run these successfully on the Xperia X10 add-on that I downloaded from the developer site of SE.
However, my phone is running the updated Android 2.1, and any apps that I make will either have to run on 1.6, or will not be able to be tested on the Xperia X10 during development without moving it to my physical phone.
I have contacted Sony and they told me there is no add-on with 2.1 on it. And that is all they would say.
My Question:
Is there anyone out there who has developed for this phone, who knows what to do? Do I somehow run the SE update tool on the virtual phone to upgrade the OS of the image? Or am I missing something much more obvious?
As of April 2011, this is (an estimate of) Android usage share:
That's 3.5% for Android 1.6 and 2.7% for Android 1.5. As time goes by, those percentages will only decrease.
Just develop for 2.1.
Why do you prefer to use the emulator, anyway? Most Android devs (myself included) have found that the emulator is painfully slow, and it's just plain easier to plug in a real phone and test on that.
You can use the adb for getting your phone in debug mode.
Or you can just install your APKs via OTA or via USB in your physical phone.
Or you could just develop on 2.1 knowing that almost everything will work. I don't get the problem, really.