Actually I don't think the energy patch will change much. Fact is that,
since we don't provide current_now nor power_now, upower will do,
/* the hardware reporting failed -- try to calculate this */
if (energy_rate < 0.01)
energy_rate = up_device_supply_calculate_rate (supply, energy);
energy_rate will be 0 because of the absence of those two sysfs nodes.
I'd suspect any issue being in this software-based rate calculation.
Something that would be worth trying out is providing a current_now
node, which is something the fuel gauge chip provides. That would allow
upower to use a different rate calculation mechanism and possibly avoid
the issue altogether.
I'll post a quick patch to provide current_now in a bit.
Cheers,
Alex
--
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
