http://android-developers.blogspot.com/2011/03/identifying-app-installations.html
This link suggests and advises identifying accounts, not specific devices.
However, sometimes you can't get around it. E.g. if you have an app that
publishes digital content under DRM, you usually have to be able
Do you use any sort of a naming convention, so you can identify what's
what for later comparison purposes? I'm thinking something a bit along
the lines of URL schemes (imsi:... or even imsi-v10:... for an IMSI
reported by API Level 10, where the ... is the actual IMSI value).
For example, it may
We use the generated device-id for DRM purposes. The generated device-id is
not used as-is. The DRM code creates encrypts it and creates a hash. The
hash is used for identifying the device on the DRM server.
It is true that an upgrade from 2.2. to 2.3 can trigger a different result
if the
The vast majority of our support issues is from users that have reflashed
the ROM on their device which results in a different Android_ID more often
than not. We also decided to use the fallback scenarios of either IMEI or
MAC address. (can't use the fancy 2.3 stuff as most users are still on
In my apps, I assign the user a username, and then generate a UUID (v4) and
associate it with the user name. That way I can maintain it across
installs, as long as the user uses the same account,
Thanks
On Mon, Dec 5, 2011 at 9:41 PM, Streets Of Boston
flyingdutc...@gmail.comwrote:
We use the
http://developer.android.com/reference/android/provider/Settings.Secure.html#ANDROID_ID
--
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,
6 matches
Mail list logo
