> > Thanks, I found it in handset source repo.
> > But the new question is why those patch are remove from contextkit-maemo?
> > That, Handset can get those context properties defined in
> contextkit-meego
> > ,
> > but netbook can't work well.
> >
>
> contextkit-maemo is for maemo.  contextkit-meego is for meego.  MeeGo's
> contextkit plugins aren't useful to maemo and most of maemo's aren't
> useful to meego.  For instance, maemo's battery plugin relies on closed
> components such as BME.  The open implementation of meego cannot rely on
> closed components like that thus it made sense for us to create an
> additional plugin that uses UPower instead.  In addition to the above
> reason, contextkit-meego contains plugins that provide context from
> connman and ofono both of which don't exist in maemo.
>
> I'm using the contextkit-meego package on my netbook.  It works fine.
>



I use meego1.0.9 release handset image(2010/9/21) on my netbook and try to
test contextkit by command line tool.
Here are the command and message I got.

*context-provide*
   "Starting service failed, no D-Bus or the service name is already taken."

   ==>The service are started failed and the context property are register
failed.


*context-listen Battery.IsCharging*
   "Battery.IsCharging subscribtion started"
   "DeviceKitPowerProvider Initializing Devicekit provider"
   "DeviceKitPowerProvider Subscribed to DeviceKit provider"
   "first subscriber appeared!"
   "DeviceKitPowerProvider First subscriber appeared, connecting to
DeviceKit"
   "DeviceKitPowerProvider No Valid battery device found"

   ==> I check the sourcecode of Battery Plugin and I found that Battery
service is "org.freedesktop.UPower". Does Upower be in meego now or later??


Thanks a lot.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to