adb shell not available on newly created image
Bug #1269556 reported by
Jamie Strandboge
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
android (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I installed 0.1+14.
$ sudo ubuntu-emulator create trusty-proposed
$ ubuntu-emulator run trusty-proposed
I waited until I saw unity8 in the emulator (ie, a long time) and then tried to do 'adb shell', but no devices were available. I tried re-running the image several times and never could get 'adb shell' to work.
Workaround:
I then restarted the adbd server on the host with: 'adb kill-server ; adb start-server'. After this, 'adb devices' shows the emulator and I can connect like normal.
I had this same problem and I noticed the following while booting:
init: cannot find '/sbin/adbd', disabling 'adbd'
It seems during early boot the adb daemon was running for a while in the emulator image, and then in stopped working:
$ adb devices
List of devices attached
emulator-5554 offline
$ adb devices
List of devices attached