That is what I was using also. But Mark Murphy picked up an Archos 5 and found that it does not return a 16 byte hex number like described in the SDK. This will no longer work for me if I can't expect the ID to be 16 bytes. My previous post explains how I am going to use the ID along with other non-unique values in an attempt to create a unique ID. I have to rewrite my backend also but that is pretty simple.
On Tue, Oct 20, 2009 at 8:44 AM, junker37 <[email protected]> wrote: > > This is what I have been using for a unique phone id. > > Settings.Secure.getString(contentResolver, > Settings.Secure.ANDROID_ID); > > On Oct 20, 10:11 am, Greivin Lopez <[email protected]> wrote: > > Ok I see IMEI is not valid as a device identifier for Android > > devices. What do you guys suggest to use instead of the IMEI to > > identify the device? Is there any best practice in Android environment > > to do that? > > > > I'm asking because I also working on that part of my application right > > now. > > > > Thanks for your help. > > > -- Writing code is one of few things that teaches me I don't know everything. http://www.fuligin.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
