#4204 NORM 8.2.0 (: Batter meter never reaches 100%
Zarro Boogs per Child
bugtracker at laptop.org
Mon Jun 30 01:52:30 EDT 2008
#4204: Batter meter never reaches 100%
-------------------------+--------------------------------------------------
Reporter: Eben | Owner: edsiper
Type: defect | Status: new
Priority: normal | Milestone: 8.2.0 (was Update.2)
Component: sugar | Version:
Resolution: | Keywords: 8.2.0:? needs-testing
Next_action: never set | Verified: 0
Blockedby: | Blocking:
-------------------------+--------------------------------------------------
Changes (by mtd):
* next_action: => never set
Comment:
I can certainly verify this behavior.
Replying to [comment:1 rsmith]:
> Replying to [ticket:4204 Eben]:
> > Although the text in the palette states "Battery fully charged",
neither the meter or the icon for the battery every reach the 100% mark,
despite the fact that the computer has been plugged in for weeks.
>
> This is a result of using the values reported from the EC directly.
Yup. This is still the case in the current git (not trying to argue or
snipe or anything, just pointing out for the record).
> > From the user experience perspective, seeing those graphical elements
reach their full mark is really important, even if in truth capacity is
slightly lower.
>
> The same thing will happen on the low side as well... The red light will
be on but the the meter will still say 10%. 10% really equals about 2-3%.
The display probably needs to scale the output. I think the following
should work.
>
> Scaled% = (int)((1.25 * (float)EC%) - 12.5)
>
> if (Scaled% > 100) Scaled% = 100;
> if (Scaled% < 0) Scaled% = 0;
>
> But because the actual "Full" from the EC will vary there will be cases
where the meter and the EC won't match. The meter will say 100% and the
EC will still have the yellow light on.
>
> Perhaps the meter should hold at 99% until the EC says "full" and then
jump to 100%.
This logic sounds cool! The right place would be in hal's
battery.reporting.* namespace - http://people.freedesktop.org/~david/hal-
spec/hal-spec.html#device-properties-battery - ? Then Sugar
(hardware/hardwaremanager.py, model/devices/battery.py) could display the
numbers as-is.
I have had a quick look at ohm and the plugins architecture seems like it
would be somewhat easy to make do what we want...but I'm not familiar
enough with the code to be sure.
--
Ticket URL: <http://dev.laptop.org/ticket/4204#comment:6>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list