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 device-id calculation is called again. This would happen if the user upgrades the device to 2.3 and 'clears the data' of our app. There are also other ways to have the device-id generate a different calculation if the user chooses to 'clear data' of our app later (e.g. on a WiFi only device running 2.2: download our app, never open it, then open it for the first time in airplane mode (by accident), clear data and then open it again at some later point with WiFi enabled). These two scenarios are possible, although they are very unlikely. We have customer support to deal with this issue (when the user finds he or she can't read a book due to a device limit being reached incorrectly). -- 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
