Closed Bug 1322524 Opened 8 years ago Closed 7 years ago

Autophone - nexus-5-1 in error state 2016-12-08

Categories

(Testing Graveyard :: Autophone, defect)

Product:
Testing Graveyard
Component:
Autophone
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bc, Assigned: van)

References

Details

nexus-5-1 connected to autophone-2 entered an error state where it can not be rebooted and can not access /data/local/tmp. I've attempted to recover it remotely and failed.

It may need to be forced to shut down and restart manually.

Note to self: Need to check /data/local/* when it restarts.

We can take care of this at the same time we do bug 1322401 / nexus-6p-3 on autophone-3.
Flags: needinfo?(stephen.donner)
Flags: needinfo?(mbryant)
As soon as my access to QA Lab - 252 is restored (Service Now request filed), I'll take care of this and bug 1322401.  Leaving need-info? as a reminder to me.
:bc, this phone is unresponsive. the touch screen is hung/unresponsive and holding down the power button doesnt work. i unplugged it in the meantime so the battery drains. is there another way to reset this phone? i see a tiny pin hole but im not sure if that is an actual reset.
Let's let it drain for now and I'll see what I can find out. Not sure if there is anything else we can do.

Worst case we have to replace it if it doesn't come back after discharging/charging. I have the 5 extra Nexus 5 devices here ready to go. All I need are the asset tags and I can ship them out.
after battery fully discharged, i was able to boot up the phone. confirmed by :bc.
Assignee: nobody → vle
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(stephen.donner)
Flags: needinfo?(mbryant)
QA Contact: cshields
Resolution: --- → FIXED
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.