Battery Saving
(→Actions on phone lock/unlock) |
|||
| Line 6: | Line 6: | ||
== Actions on phone lock/unlock == | == Actions on phone lock/unlock == | ||
| + | |||
| + | One of the simplest uses of [[DbusScripts]] is to detect when the phone is locked or unlocked, and run scripts accordingly. | ||
=== Suspend user processes === | === Suspend user processes === | ||
Revision as of 23:41, 15 May 2011
This page aims to document "power user" techniques for extending battery life, i.e. automating various aspects of the phone's behaviour with a view to extending battery life. It is currently a stub/work in progress; the aim is not to reinvent the wheel but to draw together a variety of approaches to battery saving.
Contents |
Background power saving
Techniques in the "background power saving" section should have little or no negative impact on the performance or usability of the phone but should save power in the background when the phone is not actively being used.
Actions on phone lock/unlock
One of the simplest uses of DbusScripts is to detect when the phone is locked or unlocked, and run scripts accordingly.
Suspend user processes
See Xagoln's post: http://talk.maemo.org/showpost.php?p=1005668&postcount=1
Change kernel powersave bias
Details on the Overclocking page.
Invasive power saving
Techniques in the "invasive power saving" section save power by intentionally limiting the activity and/or functionality of the phone. This can have unintended consequences, so be sure you understand what you are instructing the phone to do before you do it.