#9765 LOW 1.5-sof: frame battery icon lags charging initiation

[Zarro Boogs per Child]

#9765: frame battery icon lags charging initiation
--------------------------------+-------------------------------------------
           Reporter:  mikus     |       Owner:  pgf                              
               Type:  defect    |      Status:  new                              
           Priority:  low       |   Milestone:  1.5-software-later               
          Component:  kernel    |     Version:  Development build as of this date
         Resolution:            |    Keywords:                                   
        Next_action:  diagnose  |    Verified:  0                                
Deployment_affected:            |   Blockedby:                                   
           Blocking:            |  
--------------------------------+-------------------------------------------

Comment(by rsmith):

 Replying to [comment:26 Quozl]:
 > Another experience of ''when battery does not need charging, the frame
 status is inconsistent with battery LED''.
 >
 > A laptop running os119 with 42% remaining battery and no external power
 was suspended by closing lid.  The battery indicator showed black.
 >
 > An hour or two later it was connected to external power but left closed.
 The battery indicator showed orange.
 >
 > The next day, roughly ten hours later, the battery indicator was green,
 and the laptop was opened.
 >
 > The battery status display in the frame showed "1:11 remaining" and
 "42%".  It remained in that state despite the battery capacity being 97%,
 according to /sys/devices/platform/olpc-battery.0/power_supply/olpc-
 battery/capacity

 This should probably be factored out into a separate bug. This is a side
 effect of a purely event driven system when the events in question are
 discarded.

 When the lid is closed all battery events (except critical level) are
 masked.  So all your events went into the bit bucket.  When the kernel
 wakes up its now out of sync with reality and will be that way until some
 sort of battery or power event occurs.

 On resume the kernel needs to acquire the current state of the world from
 the EC and if its different than what it has in its cache then it should
 synthesize the missing events.

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