Guillaume Perrot wrote: > In my job, I have to use a unique device ID that is not the IMEI or any > other info provided by the TelephonyManager (for some privacy reasons) > so I would like to rely on ANDROID_ID. > But people I work for don't trust the ANDROID_ID because they don't know > exactly what it is and we don't have the guarantee that it's globally > unique (since this is set only by device manufacturers' will). > Anyone have any idea on how these IDs are built ? I need more info to > convince them to use that damn id...
Bear in mind that this ID is stored in a SQLite database and can be modified on rooted phones. Also bear in mind that there is only modest coordination on ANDROID_ID. For example, ARCHOS shipped their first Internet table where the ANDROID_ID value did not correspond to the API documentation (wasn't a hex string). This may be because they do not have the Android Market, and so get to invent their own strings. Reputedly, the ANDROID_ID value comes from the Market on first use. ANDROID_ID is fine for casual use, but it's not exactly the Rock of Gibraltar, if you know what I mean. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Beginning Android_ from Apress Now Available! -- 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
