Closed Bug 863081 Opened 12 years ago Closed 7 years ago

B2G Phones have identical serial id in ADB

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: cmtalbert, Unassigned)

Details

All b2g phones use the same serial ID in the adb devices list. This means that we cannot specifically target them if we have more than one plugged into a machine at a time. This is making our lives difficult in automation because we'd like to run several phones per machine. We would normally use the agent for interacting with the phones thus severing the need for adb except that we need to flash the phones, and flashing must be done via fastboot over USB connections. So there are two ways to solve this: 1. We give each phone a unique adb serial number 2. We create a means to flash a phone without using fastboot over USB and we wire that into the agent.
mwu, is there an easy way to include some random uid in the adb serial number?
Flags: needinfo?(mwu)
We made a way for MWC, but it varies by device. Some devices just end up changing their ID every boot. Some devices set a unique serial correctly. I'll need to know the device to give you more information.
Flags: needinfo?(mwu)
Maybe use all or a portion of either the Bluetooth or WiFi MAC address?
Currently, the problem is with unagi, whose device serial is always 'full_unagi'. But, we'll soon have this issue with inari builds, plus others as we stand them up in automation.
The set of devices I care about are (from most to least at the moment): * ikura (the open) * inari * leo device Essentially any phone that you want us to run in automation is going to need this change. At the moment there is some discussion whether we will be putting ikura or inari into automation next, so my priority may change as we sort that out. (From what I understand we would prefer to use ikura unless we can't get them). FWIW: here is my document detailing which phone is which, sorry for the intranet link: https://intranet.mozilla.org/Engagement/Developer_Engagement/FirefoxOS_Developer_Devices
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.