![]() ![]() Which is also the same device id reported by the emulator, btw. As far as I've been able to determine, all affected devices have the same ANDROID_ID, which is 9774d56d682e549c.Several devices by several manufacturers are affected by the ANDROID_ID bug in 2.2.Only 2.2 has the problems mentioned in the post. ANDROID_ID is perfectly reliable on versions of Android =2.3. Here's what I discovered that's NOT mentioned in the aforementioned blog post: I spoke with someone at Google to get some additional clarification on a few items. As Dave Webb mentions, the Android Developer Blog has an article that covers this.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |