Thanks for the link Mark, I understand that identifying an installation or device is not recommended but in the case for my app it is somewhat necessary. The problem I have with the ANDROID_ID is it seems to identify the OS installation (software identifier instead of a hardware identifier unless that ID is persistent with OS upgrades/downgrades*)
* I understand that if the user wipes the OS completely that changes. Anyway, I appreciate that link and gives me a clearer picture to what I can expect if I do go ahead and use the IMEI/MEID. On Sep 26, 6:05 pm, Mark Murphy <[email protected]> wrote: > On Mon, Sep 26, 2011 at 5:58 PM, Wall-E <[email protected]> wrote: > > Am I guaranteed to get the IMEI/MEID by calling getDeviceId() from the > > telephony manager? > > Not really: > > http://android-developers.blogspot.com/2011/03/identifying-app-instal... > > > I ask because you don't always have access to the device phone > > number. I want to be able to have an ID that is specific to the > > hardware and I'm not sure if the ANDROID_ID is constant or if it will > > change if the user upgrades the version of Android. > > To quote the blog posted linked to above: > > "There are many good reasons for avoiding the attempt to identify a > particular device. For those who want to try, the best approach is > probably the use of ANDROID_ID on anything reasonably modern, with > some fallback heuristics for legacy devices." > > -- > 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! -- 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
