Getting Unique Id from all java phones especially from S40 devices

Dear friends ,

I am in urgent requirement of getting an unique identification number programatically from all j2me supported phones.
As we already know getting IMEI / IMSI in S40 devices is almost not possible , bluetooth MAC address / obex push profile UUID may help.But
for this , bluetooth should be turned on in mobile.And i don't know how many device will support jsr82.Is there some other unique id which will
differentiate j2me devices?

No, there are no other unique IDs than IMEI, Bluetooth or WLAN (when available) MAC addresses. Redesign your solution not to depend on such entirely, or so that some ID you generate/assign yourself is sufficient (possibly in conjuntion with a username/password combination).

Hi developer89,

Check [URL="http://stackoverflow.com/questions/3838964/a-unique-identifier-for-cell-phone-other-than-imei-or-imsi"]this[/URL] link.
You can generate a UUID from the timestamp + an optional 4-6 digit random generated number. And store in a permanent RMS or a hidden file.
You can use that UUID as unique identifier for your application. I have used this implemetation in C1-01 and it worked for me...

If its a connected app, you can generate this UUID (as a auto-generated number in your server side db) on the server and send it to device first successful login and store it on the client device in RMS to make it a part of all future request generated from the client app.

Agreed, I was also thinking about suggesting the server-generated approach. However there is a downside too: it does not identify the user/device, it identifies the installation. So an uninstall-reinstall tricks it already which may be or may not be a problem, depending on the use-case.
The same applies to the locally generated UUID/GUID.

For locally generated UUID, against every user it is stored in db and verifying against the id for every login works.
And in the case of uninstalling the app....a reset for that UUID to a particular value and updating with the new UUID if that paticular reset value is met, works like a charm without any conflicts...

[QUOTE=harsha921;907506]And in the case of uninstalling the app....a reset for that UUID to a particular value and updating with the new UUID if that paticular reset value is met, works like a charm without any conflicts...[/QUOTE]Of course it will not conflict with anything since it gets a brand new UUID.
I am talking about the use case when you want to identify a device say 2 years from now, regardless of having it formatted, software reinstalled etc. Such mechanism can not be accomplished without hardware ID-s.
So uniqueness is easy, but having a persistent ID is not.

In that case it will generate a new local UUID if its not located and the reset mechanism follows which will solve the issue...

[QUOTE=harsha921;907523]In that case it will generate a new local UUID if its not located[/QUOTE]Agreed.[QUOTE]and the reset mechanism follows which will solve the issue...[/QUOTE]Probably it will not. Since it is not possible to recognize that the device is already part of the system with an other UUID.

Actually we have to do that reset mechanism manually....as the cases for new installation/reinstallation/software updation is less...