But Google's 'take' on it does not say that there already IS such a thing: it says you can make an approximation to it, an approximation that is probably what you really want in the first place. It also warns against confusing a "unique ID for each Android device" with the number returned by TelephonyManger.getDeviceId(), which is unique only for phones. Worse yet, the API does not work reliably even when you are on a phone, and requires an irritating permission.
But these last two problems are Google's fault: I don't know what they were thinking by requiring READ_PHONE_STATE permission for this. Somebody probably thought it was insecure to allow it, but I don't agree. Besides: putting this under the umbrella of READ_PHONE_STATE suggests that the latter is too coarse a permission in the first place. As for not working reliably, who if not Google was/is in the position to enforce this across all OEMs implementing it? Yet by their own admission, it did not happen. Finally, what I find most interesting in the article is how to make what most developers probably really want: a unique identifier for each installation of their application on whatever device it is installed on. They have valuable hints at that article for making exactly that. On Sep 2, 8:47 am, Nikolay Elenkov <[email protected]> wrote: > On Sat, Sep 3, 2011 at 12:39 AM, Gabriel Marchant <[email protected]> > wrote: > > Ok Nikolay... I heard about a unique ID for each Android device. Do you know > > something about it? > > Yes, there is such thing (universally) :) > > Google's take on this: > > http://android-developers.blogspot.com/2011/03/identifying-app-instal... -- 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
