> Like I said, although it shouldn't make any difference if I'm using > the fully qualified path or not, I did try your suggestion and it > still gave me null. > I'm not questioning your program, I'm asking for help with my > particular case. > There are lots of examples on this subject that use the exact same > code, I even downloaded a project of an application that should do the > same, but I still got nothing. > > I know this code should work, and as far as I know nothing else is > needed to use it (like permissions and such), but it just doesn't work > on both devices I have.
It's not quite clear how you are expecting us to help, though. If the code the rest of us use successfully does not work for you, it's incumbent upon *you* to figure out what is different between your environment and what we're all using. For example, perhaps your devices are rooted or have otherwise undergone a firmware replacement. In that case, ANDROID_ID may have gotten whacked, since that's stored in a system SQLite database AFAICT, and may not be maintained across a rooting operation or firmware replacement. Unfortunately, I'm not aware of any place in the Settings app or anywhere that you can see the ANDROID_ID value without code, to see if that is the source of your difficulty. Perhaps you can find a pre-compiled app on the Market that will report that information. -- Mark Murphy (a Commons Guy) http://commonsware.com Android App Developer Books: http://commonsware.com/books.html -- 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
