touch-packages team mailing list archive

[Francis Ginther <francis.ginther@xxxxxxxxxxxxx>]

Sergio, I will investigate that and apply 'reboot bootloader' to half of
the devices in use and update this within a few days with results. I
have not see any stuck makos within the last 36 hours. I need to go
through the logs and see how many re-flashes were did and how many
triggered the second reboot-bootloader.

-- 
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/1359488

Title:
  Makos don't always enter bootloader with 'adb reboot-bootloader'

Status in “android-tools” package in Ubuntu:
  New

Bug description:
  The basic scenario is that immediately after running a test, the
  device is reflashed and made ready for the next test. This involves:

  adb -s $SERIAL reboot-bootloader
  ubuntu-device-flash --serial $SERIAL --channel ubuntu-touch/utopic-proposed --bootstrap

  A portion of the time 'reboot-bootloader' does not work and the device
  performs what looks like a reboot. It show up as a device with 'adb
  devices'. Sometimes trying again works, sometimes a few cycles of
  reboot/reboot-bootloader works and sometimes I give up and have to
  have the device rebooted via button pushes.

  [version]
  $ apt-cache policy android-tools-adb
  android-tools-adb:
    Installed: 4.2.2+git20130218-3ubuntu26
    Candidate: 4.2.2+git20130218-3ubuntu26
    Version table:
   *** 4.2.2+git20130218-3ubuntu26 0
          500 http://ppa.launchpad.net/phablet-team/tools/ubuntu/ trusty/main amd64 Packages
          100 /var/lib/dpkg/status
       4.2.2+git20130218-3ubuntu23 0
          500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages

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