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.
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 */ supply_ calculate_ rate (supply, energy);
if (energy_rate < 0.01)
energy_rate = up_device_
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