What are mobile phones supporting Java Android?
Is there any Nokia phone supporting this technology?
What should the mobile contain (a framework, a plugin.. etc) if we want to deploy a Java Android Application?
Android can be deployed to many devices with custom builds of the OS; anyone can build Android . It is not limited to particular handset makers and you might want to consult the makers for official lists of deployed devices.
There is nothing the device needs to contain (other then an appropriate targeted version of Andrdoid) to deploy an application.
One important note is that the application IS NOT run in the JVM, the code is only written in Java and then converted to Dalvik bytecode when compiling (Android runs on the Dalvik Virtual Machine). Since the code is written in Java though you can make extensive use of existing libraries and use them in your applications.
There is a fairly comprehensive list on Wikipedia comparing devices running Android, including forthcoming devices.
Nokia seems to have no interest using Android platform for its devices.
If the device is a certified Android platform, there is nothing one needs to add for deployment.
I think most phones that run Android should support Android applications. However, IMHO one would be hard pressed to compile a list of those phone.But rest assured, it's a lot. Someone DID make a list! And yep, it's a lot.
Some quick Googling reveal that Nokia seems to not like Android so I would assume there is not a Nokia phone with Android.
Framework: Eclipse Galileo with the ADT plugin
My advice:
read this site inside and out! http://developer.android.com/index.html
It answers all your questions.
Related
I'm sorry for asking a none-programming question, if it is.
I'm working on a library project that must be compatible through various mobile platforms.
I found some Java TV platforms are constructed on CDC/PBP.
I found Android api (partially) based on the Java 6.
And I want to know, is blackberry sill on the CLDC/MIDP?
According to Programming the BlackBerry With J2ME, it seems so.
Yes, they support MIDP 2.0/CLDC 1.1 and a good number of JSRs. Devices running OS 5.0 and higher have MIDP 2.1 support. Also there are the RIM custom APIs some of which can be used in BlackBerry MIDlets too.
More info here.
UPDATE:
For the new BB10 OS there's the possibility of repackaging an already existing Android app so that it can be run (with some issues) in the Android Runtime.
What alteration should be made in a Java Application to be able to install it on Java Enabled Smartphone?
I tried using a random app of mine to see what happens, when I open it on the cell, it says Install? I say yes, and it says invalid file.
Now I was wondering what alteration should be made?
My smartphone (Samsung S8500) runs on bada which is more or less the same as Android, but alterations in the General.
You need different SDK for smartphones. Like for Android, you need Android SDK 1.5 or any other version. You just cannot install the same application. You need to develop using the resources provided by the SDK.
If your application is Java based mobile application then you can use some tools to convert it for Android. Doesn't work every time but worth a try.
In your case, Bada OS is not like Android what i learn from here. So, you need to develop the application using J2ME .
I have never tried out the Android SDK and do not own an Android phone. However it seems that certain libraries are excellent, for example the text to speech lib. Is it possible to use this library with a desktop VM and did anybody here try this?
You could get the sources from android.git.kernel.org and try to rebuild them against a desktop environment, but it would be a lengthy project - you need not only the java stuff, but the underlying drivers, native libraries, customized c library, and add-on os functionality to support them.
The android SDK includes a qemu-based phone emulator in which most functionality works as on the device. This should be fine for playing with the capabilities, though is not something you would want to use to deploy them. There is also an x86 community build of android which people put on netbooks or run in virtualbox. Word is that the official android emulator may be moving to something similar since it's substantially faster to run x86 code on a customized os image in a vm than to emulate an arm processor.
There's also something of a simulator which tries to provide enough of the android o/s services to sort of run apps natively on the development machine without a vm, but the google folks have implied its a bit of a hack and not well maintained.
I already know the differences between Java Edititions (ME, SE, EE), the ME Configurations (CDC and CLDC), Profiles (like MIDP), and additional APIs specified by JSRs.
But I am totally clueless about the differeces of the several Wireless Toolkits.
For example, Mobile Tools for Eclipse explicitly supports these ones, and states that others exist, too:
Sun Wireless Toolkits
MOTODEV SDK for JavaME
Nokia SDK S40/S60
Sony Ericsson J2ME SDK
Sprint PCS Wireless Toolkit for Java
Siemens SMTK for Series 60
mpowerplayer
Microemulator
I want to develop a MIDP application that runs on as many devices as possible, and I am going to use Antenna for build automation. Anyway, I have to install one or more of the toolkits, but don't know which.
So there are these sub-questions:
What are the differences?
Is there any single one which is the best?
Or do I need to install several / all of them?
I have a Sony Ericsson Device for testing, does this nessecarily mean I need the Sony Erricson J2ME SDK?
The device specific toolkits generally just contain debugging tools and emulators, transfer programs and custom libraries (ie, device specific audio libraries).
Generic midp code should be compatible with all devices, especially Sony Ericssons
I find it is usually audio code which facilitates a need for device SDKs. Nokia also used to use a special kind of canvas but this will only be applicable for really old phones.
EDIT: generally, install an SDK if you need it for something, otherwise use Sun WTK
Each toolkit provides the base CLDC/MIDP classes that are required. In some cases they will be specific to a device, e.g. if you choose the Nokia S60 3rd Edition FP1 toolkit (which I have used) it will use CLDC 1.1 and MIDP 2.0. In addition to this you will find that each vendor specific toolkit will come with added extras that will only be available on certain devices. Since you are looking to write for as many devices as possible you will not be using these extras and should therefore probably stick to the Sun WTK.
When building with Antenna you can specifiy which CLDC and MIDP versions you want to use if you use the Sun WTK too. If you use any other toolkit you might have problems with Antenna because it looks for very specific files (which are hard coded) so if you sepcify your WTK.home variable as Nokia S60 it won't find the files it needs so you will need to do some hacking (all of the class files for Nokia S60 are packaged in 1 jar file, unlike Sun WTK which has them all separated into the JSRs).
I find the Sony toolkit the easiest to use, mainly because it has standard size screens (ie 176x220 and 240x320) that are easily switched between on the emulator
If you are using Antenna to build you applications you should only need to install the WTK and a Blackberry SDK to get a complete set of builds, unless you are going to use device specific apis
Does anybody know if its possible to write a barcode scanning application for the SPT-1800 in Java?
I don't know how to program the Old School Palm OS.. so java would be great.
It looks like you will have to write a Palm app in C to control that model.
See the Software Development Kit (SDK), v. 4.10 and FAQ: Where Can I find the Palm SDK & Development Tool? for more information.
The Motorola/Symbol sites are not very intuitive so here's a link to all of the SPT1800 support documents.
The SDK's are usually very good and get you up and running with a sample application pretty quickly.
I had hoped to use Java for the MC3000 and MC9000 series recently but it appears Motorola/Symbol has stopped releasing updated Java SDK's for those devices and are concentrating on the .NET SDK now.
The Java SDK's also require additional licensing of the JVM from 3rd party vendors which considerably adds to the final cost of deployment.
I would think that Waba/SuperWaba would be your best bet for an older PalmOS device.