[TIMOB-16377] CLI: Android: Restart adb if it stops seeing Android devices
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Low |
| Status | Closed |
| Resolution | Won't Fix |
| Resolution Date | 2016-09-02T21:46:44.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Android, CLI |
| Labels | androidlib |
| Reporter | Chris Barber |
| Assignee | Chris Barber |
| Created | 2014-02-05T01:22:10.000+0000 |
| Updated | 2017-03-23T22:33:29.000+0000 |
Description
There are times when adb stops seeing an Android device despite being connected. This can be fixed by restarting adb, however it can be confusing when the Android build says there are no Android devices connected.
To fix this, we need to scan all connected USB devices and identify all Android devices, then query "adb devices". If "adb devices" does not return all of the connected devices, then restart adb and try again.
To detect connected USB devices on Mac OS X run
system_profiler SPUSBDataType and on Linux run lsusb -v.
I haven't seen this in a long time. This just may have been a side effect of an old version of adb. In any case, I really don't want to do this ticket. It's a hack. We shouldn't have to querying the OS for connected USB devices to validate
adb devicesresults.Closing ticket as Won't Fix with reference to the above comments.