touch-packages team mailing list archive

[Sergio Schvezov <sergio.schvezov@xxxxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1366928

Title:
  adb does not start after reboot

Status in “android-tools” package in Ubuntu:
  New
Status in “dbus-property-service” package in Ubuntu:
  New
Status in “goget-ubuntu-touch” package in Ubuntu:
  New

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).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1366928/+subscriptions