Devices lose adb connection after phablet-flash loop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Phablet Tools |
Invalid
|
Critical
|
Unassigned | ||
android-tools (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
Devices will eventually lose their adb connection to the host computer after running them through a phablet-flash loop. This has been seen in our jenkins upstream merger infrastructure for a while and I've been able to isolate it and reproduce it on my own device (a maguro) using the attached reflash-loop.sh script.
This is seen at a much higher rate on our maguros and not as much on our makos. We have swapped hosts and swapped hubs, neither change helped with the failure rate. On the maguros, it's usually seen within 10 runs. It my test at home, I was able to reproduce multiple times after 4, 6, and 4 iterations.
adb kill-server/
The MTP connection is working, I'm able to browse files on the device.
The device adb connection can be restored by pulling the battery.
[Test script - reflash-loop.sh]
http://
Changed in phablet-tools: | |
status: | New → Confirmed |
Changed in phablet-tools: | |
importance: | High → Critical |
tags: | added: ci-engineering |
Changed in android-tools (Ubuntu): | |
assignee: | nobody → Sergio Schvezov (sergiusens) |
tags: | added: avengers qa-touch rls-s-incoming |
Changed in android-tools (Ubuntu): | |
assignee: | Sergio Schvezov (sergiusens) → nobody |
In any case this is an android-tools bug.