Incorrect battery level reporting in Power Off Charging Mode
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
New
|
Undecided
|
Unassigned | ||
| krillin |
Incomplete
|
High
|
Unassigned | ||
| vegetahd |
New
|
Undecided
|
Unassigned | ||
Bug Description
Vegeta had been left in the drawer for some days. On attempting to power on the device the backlight flashed briefly but the phone was unable to boot at all. This is usually a sign of completely drained battery.
Connected the device to a wall charger, device turned on and entered Power Off Charging Mode, showed the battery graphic but the reported charge level was 40%. Tried disconnecting charger with the same outcome.
Decided to flash the device using flash tool thing the was to stable r2, not sure of original version. On completing the flash and reconnecting the charger the battery graphic now read 1% which seemed more likely to be the true state of the battery.
It is possible this is the first time I have seen an incidence of this bug that was closed some time ago because of inability to reproduce: https:/
| John McAleely (john.mcaleely) wrote | #1 |
| John McAleely (john.mcaleely) wrote | #2 |
| John McAleely (john.mcaleely) wrote | #3 |
| John McAleely (john.mcaleely) wrote | #4 |
| Changed in barajas: | |
| status: | New → Incomplete |
| assignee: | nobody → John McAleely (john.mcaleely) |
| status: | Incomplete → Confirmed |
| importance: | Undecided → High |
| importance: | High → Critical |
| milestone: | none → ww34-2015 |
| John McAleely (john.mcaleely) wrote | #5 |
| Changed in barajas: | |
| assignee: | John McAleely (john.mcaleely) → Vicamo Yang (vicamo) |
| Yuan-Chen Cheng (ycheng-twn) wrote | #6 |
| Changed in barajas: | |
| assignee: | Vicamo Yang (vicamo) → Chunsang Jeong (chunsang) |
| Changed in barajas: | |
| assignee: | Chunsang Jeong (chunsang) → Alex Tu (alextu) |
| Changed in barajas: | |
| assignee: | Alex Tu (alextu) → Alex Kaluzhny (alex-kaluzhny) |
| status: | Confirmed → Incomplete |
| John McAleely (john.mcaleely) wrote | #7 |
| Changed in barajas: | |
| milestone: | ww34-2015 → ww40-2015 |
| Alex Kaluzhny (alex-kaluzhny) wrote | #8 |
| Changed in barajas: | |
| assignee: | Alex Kaluzhny (alex-kaluzhny) → Pat McGowan (pat-mcgowan) |
| Pat McGowan (pat-mcgowan) wrote | #9 |
| Changed in barajas: | |
| milestone: | ww46-2015 → none |
| Changed in barajas: | |
| importance: | Critical → High |
| assignee: | Pat McGowan (pat-mcgowan) → nobody |
| information type: | Embargoed → Proprietary |
| affects: | barajas → avila-private |
| affects: | avila-private → avila |
| information type: | Proprietary → Public |
| affects: | avila → krillin |
I have just seen this on my phone, a krillin at the tip of rc-proposed.
Taking the phone out of my bag, I noticed it was powered down, which I did not expect. Late yesterday, the phone had good charge, and I would expect the phone to idle overnight without fully discharging. Thinking I had an instance of bug #1467580, I attempted to boot to fastboot, to flash a recovery & grab logs without booting the phone.
The phone would boot to the text selection menu, but selecting either fastboot or recovery resulted in the phone booting to the 'android' charging mode. It displayed on screen an indication of 41% charge.
I am allowing the phone to charge, and will attempt to get some logs after a charging period