On 01/04/2014 03:24 AM, Adrian Custer wrote:
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.
iSerial is part of the boot image which is flashed on the phone, and sometimes overloaded on the kernel command line of the bootloader.
If you want to modify the iSerial of a phone, you need to add a new value, and reconnect the phone.
Sadly this method does not work across reboots, in which case you should use getprop/setprop to find if the iSerial is duplicated there. In which case this might be used by the init scripts before the first run of adbd.
This is a known problem which also give a lot of trouble to the automation team. Hopefully, this should no longer be an issue with the reference device as this is part of the spec that each device comes with a unique identifier.
If you want something canonical, you can transform the MAC address into an iSerial, in which case I recommend to remove/replace the ":" as they do not work well with the "-s" option of adb.
-- Nicolas B. Pierron _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
