Closed
Bug 1270344
Opened 8 years ago
Closed 8 years ago
Autophone - nexus-5-4 is stuck 2016-05-04
Categories
(Testing Graveyard :: Autophone, defect)
Testing Graveyard
Autophone
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bc, Assigned: van)
References
Details
nexus-5-4 became unresponsive and did not recover when autophone-2 rebooted. It shows up in adb devices but hangs when attempting to run shell commands. It appears to be stuck again and needs to be power cycled.
Reporter | ||
Comment 1•8 years ago
|
||
van, stephend: if you are going to be in the office tomorrow, could you check on this device? If not, I'll try to ping someone in #servicedesk.
We also have bug 1270342 for nexus-6p-8
Flags: needinfo?(vle)
Flags: needinfo?(stephen.donner)
(In reply to Bob Clary [:bc:] from comment #1)
> van, stephend: if you are going to be in the office tomorrow, could you
> check on this device? If not, I'll try to ping someone in #servicedesk.
>
> We also have bug 1270342 for nexus-6p-8
Sure, I should be in the office tomorrow, and can take care of both.
Assignee: nobody → stephen.donner
Flags: needinfo?(stephen.donner)
Flags: needinfo?(stephen.donner)
Assignee | ||
Updated•8 years ago
|
Flags: needinfo?(vle)
Assignee | ||
Comment 3•8 years ago
|
||
i was in the office so i took care of this. phone is back online with verified ateam IP.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(stephen.donner)
Resolution: --- → FIXED
Assignee | ||
Updated•8 years ago
|
Assignee: stephen.donner → vle
Reporter | ||
Comment 4•8 years ago
|
||
thanks! verified online and now testing.
Status: RESOLVED → VERIFIED
Updated•3 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•