Closed
Bug 1342153
Opened 8 years ago
Closed 8 years ago
Autophone - device interventions autophone-3 nexus-6p-12 not charging 2017-02-23
Categories
(Testing Graveyard :: Autophone, defect)
Testing Graveyard
Autophone
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bc, Assigned: stephend)
References
Details
Attachments
(1 file)
(deleted),
image/gif
|
Details |
nexus-6p-12 went into a charging state in autophone due to a low battery level. I checked on it and found the level was down to 13%. I rebooted the device remotely to remove any stuck processes and checked dumpsys batteryinfo and found
nexus-6p-12
Current Battery Service state:
AC powered: false
USB powered: true
Wireless powered: false
Max charging current: 500000
status: 3
health: 2
present: true
level: 13
scale: 100
voltage: 3645
temperature: 272
technology: Li-ion
status 3 means the device is discharging.
Van, Stephen or Michael: Can you drop by the lab and check on this device? At this rate it will completely discharge and go off line in a short time frame.
Flags: needinfo?(vle)
Flags: needinfo?(stephen.donner)
Flags: needinfo?(mbryant)
Reporter | ||
Comment 2•8 years ago
|
||
FYI, nexus-6p-12 is attached to one of the front ports on autophone-3: USBFRONT2.2
Reporter | ||
Comment 3•8 years ago
|
||
and it has powered off now.
uber is not available either now that I recall.
Stephen, are you available today? We should probably connect it to AC to recharge and attempt a different front port if possible.
Flags: needinfo?(mbryant)
Assignee | ||
Comment 4•8 years ago
|
||
(In reply to Bob Clary [:bc:] from comment #3)
> and it has powered off now.
>
> uber is not available either now that I recall.
>
> Stephen, are you available today? We should probably connect it to AC to
> recharge and attempt a different front port if possible.
Not today, sorry, but I will be in and available to take care of this early, first thing tomorrow.
Reporter | ||
Comment 5•8 years ago
|
||
That would be totally awesome!
Reporter | ||
Comment 6•8 years ago
|
||
Stephen: I was thinking we could:
move nexus-5-2 from USBCARD3.6 to USBFRONT2.1
move nexus-6p-12 from USBFRONT2.1 to USBCARD3.6
that should give it a bit more power.
Assignee | ||
Comment 7•8 years ago
|
||
I've taken the phone off the rack and am manually charging it via USB -> AC outlet. It's currently at 7% now, and the updated (since photo) ETA is 2 hours until full charge, at which point (or shortly thereafter), I'll attempt to re-attach it to the lab setup.
Assignee | ||
Comment 8•8 years ago
|
||
(In reply to Bob Clary [:bc:] from comment #6)
> Stephen: I was thinking we could:
>
> move nexus-5-2 from USBCARD3.6 to USBFRONT2.1
> move nexus-6p-12 from USBFRONT2.1 to USBCARD3.6
>
> that should give it a bit more power.
Oops, sorry; literally went straight to just post my earlier update, without seeing this, first.
I'll do this once the device gets a good base charge, and see if that + this USB-port swapping help, after lunch (in 2-3 hours).
Assignee | ||
Comment 9•8 years ago
|
||
The Nexus 6 (p-12) reached 100% charge, so I put it back in the lab, and swapped its port with the Nexus 5 (2), per comment 6.
Hopefully it's all set, for now, at least!
Flags: needinfo?(stephen.donner) → needinfo?(bob)
Reporter | ||
Comment 10•8 years ago
|
||
The devices are both visible. nexus-6p-12 looks fine. nexus-5-2 has started testing but its battery status is 4 - not charging. It could just be that it is full and has stopped charging until it discharges a bit more. Let me keep an eye on it and see if it begins charging.
Reporter | ||
Comment 11•8 years ago
|
||
It is now at status 2 and is working so far! Thanks Stephen!
Assignee: nobody → stephen.donner
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(bob)
Resolution: --- → FIXED
Assignee | ||
Comment 12•8 years ago
|
||
(In reply to Bob Clary [:bc:] from comment #11)
> It is now at status 2 and is working so far! Thanks Stephen!
Great to hear; you're welcome (as always!)
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
•