touch-packages team mailing list archive

[Sergio Schvezov <sergio.schvezov@xxxxxxxxxxxxx>]

** Changed in: android-tools (Ubuntu)
     Assignee: Sergio Schvezov (sergiusens) => (unassigned)

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

Title:
  Devices lose adb connection after phablet-flash loop

Status in Phablet Tools:
  Invalid
Status in “android-tools” package in Ubuntu:
  Confirmed

Bug description:
  Devices will eventually lose their adb connection to the host computer
  after running them through a phablet-flash loop. This has been seen in
  our jenkins upstream merger infrastructure for a while and I've been
  able to isolate it and reproduce it on my own device (a maguro) using
  the attached reflash-loop.sh script.

  This is seen at a much higher rate on our maguros and not as much on
  our makos. We have swapped hosts and swapped hubs, neither change
  helped with the failure rate. On the maguros, it's usually seen within
  10 runs. It my test at home, I was able to reproduce multiple times
  after 4, 6, and 4 iterations.

  adb kill-server/start-server on the host have no effect. The device
  itself completes flash and is sitting at the Intro screen (waiting for
  me to try the right edge). The device appears to be fully functional.
  With the terminal app, I was able to determine that adbd was running
  on the device (via "ps -ef | grep adbd").

  The MTP connection is working, I'm able to browse files on the device.

  The device adb connection can be restored by pulling the battery.

  [Test script - reflash-loop.sh]
  http://paste.ubuntu.com/6379760/

To manage notifications about this bug go to:
https://bugs.launchpad.net/phablet-tools/+bug/1249162/+subscriptions