On 14-01-04 06:29 AM, Alexandre Lissy wrote:
Le 04/01/2014 12:24, Adrian Custer a écrit :
The Android community has been tackling this need for a long time and
has developed multiple approaches though, in modern versions, the OS
provides a way for user code (Java) to obtain a unique id per device. See
*
http://android-developers.blogspot.com/2011/03/identifying-app-installations.html
* http://www.pocketmagic.net/2011/02/android-unique-device-id/
* http://stackoverflow.com/questions/13744565/android-device-id-confusion
for discussion of the issues and various solutions.
So far I am poking around in /proc and /sys land from 'adb shell' but
have not yet found anything canonical. There is
cat /sys/devices/virtual/android_usb/android0/iSerial (MSM7627A)
cat /sys/devices/virtual/android_usb/android0/idProduct (9025)
cat /sys/devices/virtual/android_usb/android0/idVendor (05c6)
but I am not sure how 'unique' the iSerial number is. (Note that the
idVendor is probably, in general, related to the list on the page:
What device are you experiencing on ? How did you flashed it ?
As far as I can say, iSerial should not be overwritten in public devices
and build, but it's the case on some build you can do by yourself.
It's possible iSerial may change on different devices, but the value
above is
the part number for the CPU of the phone.
--m.
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
