#8443 HIGH 8.2.0 (: Battery Percentage doesn't update until minutes after resume

[Zarro Boogs per Child]

#8443: Battery Percentage doesn't update until minutes after resume
-----------------------------------+----------------------------------------
   Reporter:  gnu                  |       Owner:  cjb                                         
       Type:  defect               |      Status:  new                                         
   Priority:  high                 |   Milestone:  8.2.0 (was Update.2)                        
  Component:  power manager (OHM)  |     Version:  Development build as of this date           
 Resolution:                       |    Keywords:  blocks-:8.2.0 polish:8.2.0 cjbfor8.2 relnote
Next_action:  design               |    Verified:  0                                           
  Blockedby:                       |    Blocking:                                              
-----------------------------------+----------------------------------------

Comment(by mikus):

 Replying to [comment:9 rsmith]:
 > Please do a discharge/recharge cycle while running olpc-pwr-log and send
 me the log files.  I you have idle-suspend enabled please turn it off.
 I will not do that unless you give me a convincing explanation of what
 good it will do.

 As far as I am concerned, the current problem (percentage shown not
 changing) is that the tools (from batman.fth) that I used, had set the
 battery's eeprom to NOT invoke the periodic interrupt.  With the XO
 software to *recalculate* the charge percentage not being "started", the
 Frame palette keeps showing the same old percentage value (it's now about
 20 hours later, and Frame *still* shows the percentage as 73%).  [Note:
 within about an hour after the battery's eeprom was "cleared", both the
 'battery LED' turned green, and olpc-pwr-log (run then) showed battery
 status as 'Full'.]

 There's an attachment to #8690 that shows olpc-pwr-log output for a period
 right after the 'battery LED' not working was "fixed".  That ought to be
 good enough to convince you that the battery *is* charging properly (so it
 is the XO software that is NOT reporting charge status properly, possibly
 because some bit was not set by the batman.fth tools, that should have
 been set).

-- 
Ticket URL: <http://dev.laptop.org/ticket/8443#comment:10>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system