testing a kernel with teh above patch doesnt seem to fix it either ...
but i made an intresting observation:
right after first boot
ogra@nexus7:~$ upower -d |grep energy-full:
energy-full: 73.66 Wh
the "energy-full" value actually should be a fixed value coming from the
battery describing the upper charge level...
after a reboot:
ogra@nexus7:~$ upower -d |grep energy-full:
energy-full: 69.42 Wh
and indeed the battery applet (with "show time" set in the options)
immediately show 100% charge at boot (even though thats nonsense indeed)
so i think our base value used to compute the time in upower is reported
wrongly (or read wrongly by upower)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1093543
Title:
Battery status behaves erratically
Status in Ubuntu on the Nexus 7:
New
Status in “linux-nexus7” package in Ubuntu:
Confirmed
Status in “upower” package in Ubuntu:
Confirmed
Bug description:
I've recently updated my nexus and I've noticed that the battery
system behaves very erratically. It will say that the battery is at
43%, 1 hour left, then say it is low with 43% and 1 minute left. At
some points it says the battery is critical and shuts down the screen,
only to re-awake soon after saying that the battery is simply low. The
percentage seems to remain constant, however the time left changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1093543/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
