I figured this out. Just generate a random string (using Java UUID)
and save it in Settings. That's enough to distinguish each user :)
On Mar 27, 5:49 pm, Anna PS annapowellsm...@googlemail.com wrote:
Yes, I really wanted to avoid TelephonyManager because it has
particularly scary-looking
On Mon, Apr 5, 2010 at 3:30 PM, Anna PS annapowellsm...@googlemail.com wrote:
I figured this out. Just generate a random string (using Java UUID)
and save it in Settings. That's enough to distinguish each user :)
Wouldn't re-installing the app change it though?
--
Greg Donald
destiney.com |
There is a fair amount of sometimes conflicting information about
this. Here are some previous threads.
http://groups.google.com/group/android-developers/browse_thread/thread/cbc9d4cad48a7fb7/42aceb303e8b42f6?#42aceb303e8b42f6
Yes, I really wanted to avoid TelephonyManager because it has
particularly scary-looking permissions.
And indeed I don't need to know any identifying info about the phone
or the user: I just need an easy way to distinguish one phone from
another (so that I can ban problem users if necessary).
Can't say anything about the ANDROID_ID thing. What's wrong with the
TelephonyManager? You can get the device ID, subscriber ID, Sim serial
number, etc. I think the only permission you need is
uses-permission android:name=android.permission.READ_PHONE_STATE/
in the manifest.
Ken
On Mar 25,
I also use TelephonyManager in my app, but I do, on occasion, get an angry
e-mail asking why the app needs to make phone calls. Many users just don't
understand the phone state permission.
On Fri, Mar 26, 2010 at 2:20 PM, Ken H hunt1...@gmail.com wrote:
Can't say anything about the ANDROID_ID
6 matches
Mail list logo
