On Sun, Aug 15, 2010 at 4:47 PM, Maps.Huge.Info (Maps API Guru) <[email protected]> wrote: > Here are other devices I see (for the month of August only) that have > this probem: > > 753 DROID2 > 4 DROIDX > 1 European Vogue > 2 Full Android on Vogue > 90 HTC Desire > 15 HTC HD2 > 1 HTC Vogue FroYo > 1 LG-MS690 > 2 MSM > 4 Nexus One > 1 boydTouch HD2 > 2 thunderc > > Here are the builds: > > 117 FRF91 > 2 MASTER > 757 VZW
Just to clarify, by "this problem" you mean having the same ANDROID_ID as others of its model, or having this one magic ANDROID_ID? If the latter...do you distribute your app outside of the Android Market? > Looks like this problem is wider than just Motorola, although it could > be the other devices are custom ROM's. Custom ROMs would be one possibility -- the ROM mixer might have grabbed the ANDROID_ID value out of the emulator. The reason I asked about distribution is that I seem to recall that ANDROID_ID is somehow tied into Google accounts and the Android Market. I'm wondering if this magic ANDROID_ID is the new default value. If so, devices that are not set up with the Android Market (e.g., emulator) might return this value. That wouldn't explain the DROID2 -- if 100% of DROID2's aren't getting the Market, that'd be *huge* -- but it might explain some of your other ones. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.1 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
