If you use it while using items like android.os.Build.PRODUCT or something similar you should be able to create a unique ID. Of course with this is the assumption that no manufacturer will duplicate.
On Mon, Mar 15, 2010 at 7:58 AM, Greg Donald <[email protected]> wrote: > On Mon, Mar 15, 2010 at 10:48 AM, Mark Murphy <[email protected]> > wrote: > > ANDROID_ID is fine for casual use, but it's not exactly the Rock of > > Gibraltar, if you know what I mean. > > I can't think of a scenario where I would ever need it "casually". > Either I need it or I don't. > > > -- > Greg Donald > destiney.com | gregdonald.com > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Writing code is one of few things that teaches me I don't know everything. Make Call Girl Manager great! Join the forums. http://www.fuligin.com/forums -- 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
