Tim Bray posted the following on the Android Developers Blog: http://android-developers.blogspot.com/2011/03/identifying-app-installations.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+blogspot%2FhsDu+%28Android+Developers+Blog%29&utm_content=Google+Feedfetcher
In it, he describes various ways that an app could attempt to get a unique ID for the device it's running on. However, he also laments shortcomings with every approach. In particular, a couple approaches fail because device manufacturers have not correctly implemented Android. Which makes me wonder if there isn't, or shouldn't be, some sort of certification program that Google runs, to make sure that what a manufacturer puts out as Android really is Android. It's hard enough writing apps for all the different devices out there. When a class/ method that should work, doesn't work, that makes it just that much more difficult. Is it merely just a cost problem that Google doesn't want to invest in a robust test framework to certify devices and their OS's? - dave -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en