14.03.2011 21:01, Marcin Orlowski ?????:
On 14 March 2011 18:54, Maps.Huge.Info <http://Maps.Huge.Info> (Maps
API Guru) <[email protected] <mailto:[email protected]>> wrote:
Just keep in mind that Secure.ANDROID_ID isn't reliably unique.
It's not reliable at all. On some devices all you get is null (i.e.
Milestone). On other it's not unique.
I definitely get a non-null ANDROID_ID value on my Milestone. Do you
have any Google accounts set up on yours?
Too true about non-unique IDs, including the Droid 2 and others.
So one really needs three plans : Plan A for ANDROID_ID, Plan B for the
telephony ID, and Plan C for when to use which one :)
--
Kostya Vasilyev -- http://kmansoft.wordpress.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
