[maemo-developers] Power friendliness is in the hands of the app developers, but...

From: Attila Csipa maemo at csipa.in.rs
Date: Mon Oct 26 13:28:08 EET 2009
On Saturday 24 October 2009 10:07:34 Ville M. Vainio wrote:
> > for all the ways power-saving might be an issue. For example do I really
> > need to watch focus and window state events like a hawk to see when I
> > have been minimized and thus in a position to cut some slack for the CPU
> > ?
> That stuff isn't too bad because your process will be in running state
> on those occasions anyway. The badness comes from waking up, raher
> than not doing something when having woken up.

The point I'm trying to make is that there are several distinct levels of 
power-usage scenarios (think about it as like what governors are to CPU 
speed), and a 'fixed' powersave scheme (like the don't do this and don't do 
that), while good, is still not optimal. I would like to see a recommended 
power strategy list (like - how to react when you're a CPU heavy program and 
you're backgrounded, or the screen is blanked, or an inactivity timer is 
triggered, etc, etc), basically the things an application can *proactively* 
do to conserve energy, and in that context code examples CAN help standardize 
this .
More information about the maemo-developers mailing list