[PATCH] frameworkd battery status reporting

Neil Jerram neiljerram at googlemail.com
Sat May 1 11:49:31 CEST 2010


I previously wrote about some problems that I observed when switching
from odeviced to fsodeviced, and I think I can now explain those
better:

On 28 February 2010 00:44, Neil Jerram <neiljerram at googlemail.com> wrote:
>
> Well, the Debian version of fsodeviced seems not to work
> straightforwardly yet.  It dates from 10th Jan and appears not to
> provide the GetPower method of org.freesmartphone.Device.PowerControl,

Actually the problem here was that there's now no PowerControl path
for "usb".  I think this makes sense, because the USB can't be powered
on and off in an analogous way to GSM, Wifi, GPS and Bluetooth.  So I
guess it was just an oddity that FSO1's odeviced used to provide that
path, and a bug for openmoko-panel-plugin to use it.  o-p-p users can
work around this by unchecking "usb is Active" in the PanelPlugin tab
of o-p-p's config.

> and the GetInfo method of
> org.freesmartphone.Device.PowerSupply.

The problem here was that

  self.batteryPath = '/org/freesmartphone/Device/PowerSupply/battery'

is wrong now.  It should be

  self.batteryPath = '/org/freesmartphone/Device/PowerSupply/0'

o-p-p users can make this change in panelplugin/BatteryIcon.py.

I should say, though, that I still don't have complete battery
reporting with fsodeviced + o-p-p; I'll write again once I have that.
This change just stops o-p-p from trying its initialization loop over
and over again.

> Also, FWIW, with fsodeviced instead of odeviced, and with
> notification-daemon installed, I get lots of spurious notification
> popups about resource state changes (when nothing is really changing).

This was a consequence of either or both of the above.  o-p-p kept
failing its initialization, so retrying, failing, retrying, etc.

> So, I'm going back to odeviced for now, but will try fsodeviced again
> after it's been updated.

I'm now using fsodeviced again and planning to stick with it (as part
of trying to make sure I'm using up to date kernel and modern stuff).
There's a bit more to do (in o-p-p) to get the battery reporting
right, but everything else looks fine.

Regards,
        Neil



More information about the community mailing list