Closed GoogleCodeExporter closed 8 years ago
Confirmed on Ursa Minor beta.
Original comment by adamoutler@gmail.com
on 27 Feb 2011 at 3:13
Upon first boot, with the battery low, the phone reported "Low storage,
battery is low -false" or something to that effect.
I have charged and discharged the phone and at the point when the battery
starts getting low, it gives a proper charging warning....
"Please connect charger
The battery is getting low:
Battery low. Recharg phone
soon to keep using"
I am still collecting information
As a side note: The system Battery usage, regardless of app usage is reported
as exclusively divided between Display and Cell standby.
Original comment by adamoutler@gmail.com
on 27 Feb 2011 at 3:24
[deleted comment]
This issue resurfaced. It would appear to be intermittant
here is an image I shot today. This is on UrsaMinorBeta-1 kernel.
http://i236.photobucket.com/albums/ff111/DrivingTibNaked/DSCN0729.jpg
Clicking "Complete action using" takes you to the display usage statistics
page.
Original comment by adamoutler@gmail.com
on 1 Mar 2011 at 2:33
NOT a kernel issue. See screen shot below of my phone with same kernel as above
and Andromeda 2.0 ROM. It reports the right message. As stated it's in the ROM
not the kernel.
http://www.mediafire.com/?1iyuum8y32xdw36
Original comment by ewa...@gmail.com
on 1 Mar 2011 at 1:37
I've seen both messages on the phone. When the phone runs low on battery and
it being used it may display the proper message.
I have observed this incorrect message a few times. I believe that the
incorrect message is only received when the phone goes low on battery and is in
the locked state.
Original comment by adamoutler@gmail.com
on 1 Mar 2011 at 2:00
It'd be great if someone could test this on another kernel besides Ursa Minor
with NO other changes
Original comment by 3lvam9...@gmail.com
on 3 Mar 2011 at 12:23
I'm working on it.
Original comment by adamoutler@gmail.com
on 3 Mar 2011 at 12:48
This is an Android 2.2 issue, not Andromeda or kernel. Closing as it is an
upstream issue.
Original comment by adamoutler@gmail.com
on 9 Mar 2011 at 2:30
Original issue reported on code.google.com by
adamoutler@gmail.com
on 26 Feb 2011 at 12:26