Hello Mark, I'd venture to say that impossible what you're asking. With #1 you would have a problem with privacy/security. With #2, having a storage spot would mean you wouldn't need Content Providers. It's intuitive for there to be a permission placed on this info. So just do the Overkill, putting a permission in there shouldn't be a problem.
- Juan T. On Oct 15, 5:58 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > I need a unique ID for each phone, just enough to distinguish it from > any other Android phone. In theory, TelephonyManager#getDeviceId() would > be fine, except that it requires READ_PHONE_DATA as a permission, and > that seems overkill. > > The catch is that I need this ID to be cross-application; two > applications on the same device need to get the same ID. > > So, two questions: > > 1. Is there some other API in Android-land that returns a unique value > for each phone, that I just haven't found yet? One that does not require > any special permission to access? I even considered a MAC address, but > Android doesn't offer NetworkInterface#getHardwareAddress(), unfortunately. > > 2. If the answer to #1 is "no, silly", is there a spot (that I just > haven't found yet) where I could tuck a world-readable UUID that could > serve this purpose? It doesn't seem like there's any good > cross-application storage spot outside of the SD card, and I can't count > on all devices having one. > > Thanks in advance! > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 1.3 Published! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
