Ompower

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m (Fixes in dbus-send commands)
Line 7: Line 7:
 
=== Avoid suspension ===
 
=== Avoid suspension ===
 
If an application wants to tell the phone that it should not suspend, it should send a dbus message. This message could be send by dbus API. In case of a shell script, sending dbus messages could be achieved by the command ''dbus-send'':
 
If an application wants to tell the phone that it should not suspend, it should send a dbus message. This message could be send by dbus API. In case of a shell script, sending dbus messages could be achieved by the command ''dbus-send'':
  dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RequestResourceState? \
+
  dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RequestResourceState \
 
  string:cpu string:my-system-name string:on
 
  string:cpu string:my-system-name string:on
  
 
If the application then is in a state it could be suspendet, it should send:
 
If the application then is in a state it could be suspendet, it should send:
  dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RemoveRequestedResourceState? \
+
  dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RemoveRequestedResourceState \
 
  string:cpu string:my-system-name  
 
  string:cpu string:my-system-name  
  
Line 18: Line 18:
 
=== Requesting suspension ===
 
=== Requesting suspension ===
 
The daemon is also able to request a suspend by explicitely requesting a "power off":
 
The daemon is also able to request a suspend by explicitely requesting a "power off":
  dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RequestResourceState? \
+
  dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RequestResourceState \
 
  string:cpu string:my-system-name string:off
 
  string:cpu string:my-system-name string:off
  

Revision as of 12:21, 18 September 2008

ompower is a suspend handling daemon talking dbus installed by default since Om 2008.8. It is responsible for triggering or aborting suspension of your phone. Applications send dbus messages which are evaluated by ompower. This may be used, for example, to abort suspending the phone while doing GPS tracking.

Contents

How does it work?

ompower manages suspension, but does not enforce it. It does this by a request mechanism. Applications may request either suspension or power-on. As long as requests for "power on" are active, the phone will not suspend. If no such requests are active (all "power-on" requests are removed or no requests have been made so far) ompower will suspend the phone (via calling apm -s), if "power-off" requests are active. The "power-off" requests are usually issued by some application such as Illume. If neither "power-on" and "power-off" requests are in ompowers queue, nothing will happen.

Avoid suspension

If an application wants to tell the phone that it should not suspend, it should send a dbus message. This message could be send by dbus API. In case of a shell script, sending dbus messages could be achieved by the command dbus-send:

dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RequestResourceState \
string:cpu string:my-system-name string:on

If the application then is in a state it could be suspendet, it should send:

dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RemoveRequestedResourceState \
string:cpu string:my-system-name 

"my-system-name" is an identifier telling dbus the requesting source. In case of tangogps, this could be "application-tangogps".

Requesting suspension

The daemon is also able to request a suspend by explicitely requesting a "power off":

dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RequestResourceState \
string:cpu string:my-system-name string:off

Ticket

For further reading see Ticket #2008 (Do not suspend when certain apps are running). That ticket was the reason for writing this article.


Source

You can fetch the source here: http://svn.openmoko.org/developers/raster/ompower/

Personal tools

ompower is a suspend handling daemon talking dbus installed by default since Om 2008.8. It is responsible for triggering or aborting suspension of your phone. Applications send dbus messages which are evaluated by ompower. This may be used, for example, to abort suspending the phone while doing GPS tracking.

How does it work?

ompower manages suspension, but does not enforce it. It does this by a request mechanism. Applications may request either suspension or power-on. As long as requests for "power on" are active, the phone will not suspend. If no such requests are active (all "power-on" requests are removed or no requests have been made so far) ompower will suspend the phone (via calling apm -s), if "power-off" requests are active. The "power-off" requests are usually issued by some application such as Illume. If neither "power-on" and "power-off" requests are in ompowers queue, nothing will happen.

Avoid suspension

If an application wants to tell the phone that it should not suspend, it should send a dbus message. This message could be send by dbus API. In case of a shell script, sending dbus messages could be achieved by the command dbus-send:

dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RequestResourceState? \
string:cpu string:my-system-name string:on

If the application then is in a state it could be suspendet, it should send:

dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RemoveRequestedResourceState? \
string:cpu string:my-system-name 

"my-system-name" is an identifier telling dbus the requesting source. In case of tangogps, this could be "application-tangogps".

Requesting suspension

The daemon is also able to request a suspend by explicitely requesting a "power off":

dbus-send --system --dest=org.openmoko.Power / org.openmoko.Power.Core.RequestResourceState? \
string:cpu string:my-system-name string:off

Ticket

For further reading see Ticket #2008 (Do not suspend when certain apps are running). That ticket was the reason for writing this article.


Source

You can fetch the source here: http://svn.openmoko.org/developers/raster/ompower/