N900 software power management

(Powertop)
(Powerscript)
Line 72: Line 72:
Install i2c-tools from extras-devel.
Install i2c-tools from extras-devel.
-
Please note the warning, experimenting with the tools in this package may cause hardware damage. Know what the [[I2C|N900 Hardware Bus I2C]] bus and device you are accessing is, before making any changes to the below.
+
Please note the warning, experimenting with the tools in this package may cause hardware damage. Know what the [[N900 Hardware Bus I2C|I2C]] bus and device you are accessing is, before making any changes to the below.
-
 
+
  #!/bin/sh
  #!/bin/sh
 +
echo 0 >/proc/timer_stats
  while true
  while true
  do
  do
-
  echo 1>/proc/timer_stats;sleep 5;tail -1 /proc/timer_stats|tr -d "\n" ;echo $((`i2cget -y 2 0x55 0x14 w` * 3570 / 22 / 1000))mA"
+
  echo 1 >/proc/timer_stats
 +
sleep 5
 +
echo 0 >/proc/timer_stats
 +
echo `date` $((`i2cget -y 2 0x55 0x14 w` * 3570 / 22 / 1000))mA `tail -1 /proc/timer_stats`
  done
  done

Revision as of 20:33, 7 August 2010

This is a work in progress. It is not yet ready for public consumption. Please don't link it into wiki yet.

Contents

Overview

This page may be useful to application developers, as well as those interested in reducing power usage of software by configuring it correctly.

Why software uses power

Software should use power to do what the user wants in the most battery efficient way, without letting the battery efficiency get in the way unless it's unavoidable.

For example, it might be nice to always keep the backlight on, from a user-experience point of view, but this will lead to a battery life of several hours at best, so the compromise of blanking the screen when inactive and on battery is usually made.

Direct

Direct power use is quite simple. The intended function of the application uses power. For example, 'flashlight'.

This application turns on the LED Flash so the user can see.

Once it is active, it needs no CPU, and the screen can be blanked. Almost all of the battery usage in this mode is to cause the desired effect.

'Flashlight' as an application could be viewed as 95% efficient - only 5% or so of the battery is used for stuff other than keeping the flash lit.

Indirect

Indirect is when there is no direct hardware way to perform an action, and some part of the system has to be made to do this without the user explicitly turning it on.

For example, a task-list application might want to alert the user if they get within a certain distance of a task, so they could consider doing it.

So, the application needs some means to get a notion of location. For example, it could run the GPS, or scan wifi networks in range.

The user doesn't know or care about how the application does it, but how it is done may have a significant effect on battery life.

User Training

User training is very important, in some ways more important than the rest of this guide.

In some cases, there is no way for the user to avoid battery use.

They need to see - they turn on 'flashlight'.

In others, minor changes to their behaviour, that might even make their experience better, may greatly change battery life.

For example, when listening to audio, if the user knows that instead of streaming programs from their local radio station over 3g, both FM radio or downloading a podcast over wifi would use a tiny fraction of the power, they can make that choice.

Pathological

The application chooses - or the system software only permits - an inefficient way to perform a task.

For example, an alarm application that after it has been told to beep after 12 hours, turns on the audio system immediately to make that beep, then checks every second to see if the 12 hours is up yet.

Details of each case, with examples.

Direct

Indirect

Pathological

Avoidable

  • Not properly becoming idle when the screen is locked.
  • Leaving GPS on when screen is locked, when it does not aid the application. (for example, if the application gets a GPS fix, displays location related data, and does not turn off the GPS, even when the screen is locked).
  • Keeping audio active when idle. Pulseaudio can use a large amount of power in some cases, playing 'silence'.
  • Improper use of timers. If you need to do something every second to update the display, don't do it when the screen is locked, or your window is hidden.
    • If you need to update internal state, and you normally do this every time you update the window, consider carefully how infrequently you can do this when the user is not looking at the display.
  • Listening to events that are irrelevant. When you got a mainloop with a central wait like e.g pause() (2), then you should not create a situation where irrelevant events cause signals sent to the waiting process and cause "active discarding" of the signal. Generally whenever there's a test in a signal handler subroutine that discards certain classes of signalled events, you should check if there's no way to disable the signals from being sent to your process at all. (Example: a widget that doesn't react to any touchscreen events is maybe better off not to receive any X events at all. Especially applicable if this property not to care about touchscreen events is just temporary - don't make the process use CPU time just to decide it's been an event that doesn't matter)

By Design

Unavoidable

Tools

Powertop

Powerscript

The below is a simple script to read the bq27200 battery meter, and output instantanous current, as well as wakeups/second. It outputs once per 5 seconds a summary of the activity in the preceding period.

Install i2c-tools from extras-devel.

Please note the warning, experimenting with the tools in this package may cause hardware damage. Know what the I2C bus and device you are accessing is, before making any changes to the below.

#!/bin/sh
echo 0 >/proc/timer_stats
while true
do
echo 1 >/proc/timer_stats
sleep 5
echo 0 >/proc/timer_stats
echo `date` $((`i2cget -y 2 0x55 0x14 w` * 3570 / 22 / 1000))mA `tail -1 /proc/timer_stats`
done

Top

Htop

Dbus-monitor

mdbus2