Typically there should a fuel gauging application that reads the information from the device kit power using dbus info and can inform the user of the battery conditions
-- provide low battery warning to user, so the users can shutdown unnecessary apps -- provide warning to user indicating when "calls will no longer be possible" given the current rate of discharge The policy manager can also figure out how best to --make emergency calls when the battery is really low (these will depend on battery type, voltage left and modem power etc) Eventually the user space policy manger can define these scenarios -Padma -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Arjan van de Ven Sent: Wednesday, February 09, 2011 9:35 AM To: Rémi Denis-Courmont Cc: [email protected] Subject: Re: [MeeGo-dev] BME (Battery Management Entity) on MeeGo On 2/9/2011 3:30 AM, Rémi Denis-Courmont wrote: > On Saturday 29 January 2011 10:42:28 ext Carsten Munk, you wrote: >> 2011/1/29 Lego Ming<[email protected]>: >>> Hi all, >>> We want to study the Battery Management Mechanism on MeeGo Handset. >> The battery management mechanism on MeeGo handset is up to the >> individual hardware adaptation. You're likely to have to implement >> that yourself depending on your hardware. > Shouldn't the values be readable with the standard power_supply device class > in Linux sysfs at least? absolutely and the layer on top of that is upower which provides a dbus interface to this information. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
