Another Motorola phone with ANDROD_ID issues?
Since Google has LVL, where using ANDROID_ID is recommended to identify
the device, shouldn't this be added to the compliance suite?
-- Kostya
16.11.2010 3:27, John Gaby пишет:
Thanks, I will give those a try.
On Nov 15, 4:24 pm, Mark Murphy<mmur...@commonsware.com> wrote:
On Mon, Nov 15, 2010 at 7:17 PM, John Gaby<jg...@gabysoft.com> wrote:
I just double checked it on a Motorola Devour running 1.6 and it is
definitely returning a null. I will see if I can find another 1.6
device and check to see if it is just this particular one. Given that
this call CAN return null, is there some other way to get a unique id
for the device?
There are a few. They all suck for one reason or another, as I recall.
This has been discussed probably 20 times on this list in the past 20
months. Please search the archives for more details. Here are two off
the top of my head:
-- IMEI from TelephonyManager and getDeviceId()
-- MAC address from WifiManager and getConnectionInfo()
--
Mark Murphy (a Commons
Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy
Warescription: Three Android Books, Plus Updates, One Low Price!
--
Kostya Vasilyev -- WiFi Manager + pretty widget -- 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
