New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 663765 link

Starred by 1 user
Status: Fixed
Owner:
█ pschmidt@chromium.org
Last visit > 30 days ago
Closed: Nov 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: ----



Sign in to add a comment

Device offline on Android Nexus5 Perf (1)

Project Member Reported by sullivan@chromium.org, Nov 9 2016 
Link to buildbot status page:
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%281%29/builds/4640

0accace943e4af1c: adb status offline

Note this seemed to have come back online in  bug 663537 , but it seems to have gone back offline again.

Comment 1 by pschm...@google.com, Nov 9 2016

Owner: pschmidt@chromium.org
Status: Assigned (was: Untriaged)
Via the touch screen the N5 seemed responsive.  Disconnected it from the host and connected it to my laptop, it would respond to adb until I power cycled the N5.

Have re-flashed it and added it back.  Effective starting with https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%281%29/builds/4640

List of devices attached
0acbf65743e4b10a	device
0acc13b443e4b104	device
0a9c636f43e4b7c9	device
0d88e86a43e4b0cc	device
0d890b5f25995524	device
0accace943e4af1c	device
03848d7af0e9447d	device

Comment 2 by pschmidt@chromium.org, Nov 10 2016 

Re-flashing did not work.  Will start replacing parts tomorrow a.m.

Comment 3 by pschm...@google.com, Nov 10 2016 

 Issue 664165  has been merged into this issue.

Comment 4 by pschmidt@chromium.org, Nov 10 2016 

Replacing 0accace943e4af1c  with 06c10127003ba4f4.

It will take abut another 30 min before it is fully charged.

Comment 5 by pschmidt@chromium.org, Nov 11 2016 

Devices are still unstable.  Will be switching host so that there is a complete usb 3.0 path.
Project Member

Comment 6 by bugdroid1@chromium.org, Nov 11 2016 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome-golo/chrome-golo.git/+/498cf1a044cfadf6885d4878207414584cfbad13

commit 498cf1a044cfadf6885d4878207414584cfbad13
Author: Peter Schmidt <pschmidt@google.com>
Date: Fri Nov 11 20:56:28 2016
Project Member

Comment 7 by bugdroid1@chromium.org, Nov 11 2016 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome-golo/chrome-golo.git/+/498cf1a044cfadf6885d4878207414584cfbad13

commit 498cf1a044cfadf6885d4878207414584cfbad13
Author: Peter Schmidt <pschmidt@google.com>
Date: Fri Nov 11 20:56:28 2016

Comment 8 by zh...@chromium.org, Nov 14 2016

Summary: Device offline on Android Nexus5 Perf (1) (was: Device offline on chromium.perf)
One device becomes offline again today.

Device 03848d7af0e9447d blacklisted

Comment 9 by zh...@chromium.org, Nov 15 2016

Status: Fixed (was: Assigned)
device offline problem seems gone now
►

Sign in to add a comment