adb does not start after reboot

Bug #1366928 reported by Jamie Strandboge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
android-tools (Ubuntu)
New
Undecided
Unassigned
dbus-property-service (Ubuntu)
New
Undecided
Unassigned
goget-ubuntu-touch (Ubuntu)
New
Undecided
Unassigned

Bug Description

On r228-r230 (earlier versions may also be affected), adb does not start on reboot.

Steps to reproduce:
1. create an image and set a PIN (there are multiple bugs in this process, so I won't enumerate all the steps to do this)
2. enable developer mode in system settings
3. phablet-shell into the image (it works)
4. reboot

At this point, after a successful reboot/power cycle, I would expect adb to start. However, 'adb devices' only shows 'offline' and phablet-shell does not work. This is a pretty serious regression in the emulator because there appears to be no workaround: unchecking and checking developer mode in system settings does not work, there is no route to the emulator ip so 'android-gadget-service enable ssh' doesn't help, and there is no terminal available for the emulator, so the only recourse is to regenerate the image (which even if you have a cached image and use --revision=... it takes a while to first boot the emulator).

description: updated
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

I don't see from these steps how this can be a provisioning problem, so I'm assigning the recently added/changed components to the list.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.