Maemo Wiki Mirror - User contributions [en]

SMSCON

2010-09-12T15:04:25Z

82.95.252.184: /* Current version v0.4.3 */

SMSCON provides complete control of your [[Nokia N900|N900]] by sending SMS messages to it. This is particularly handy in case you cannot find your phone, for example if it has been lost or stolen.

SMSCON is a two part Python script running in CLI; <code>smscon</code> and <code>smscon_daemon</code>. <code>smscon</code> is the CLI control part and <code>smscon_daemon</code> is the "running in the background" part. The configuration file for all the user settings is in the <code>smscon_config</code> file.

=Functionality=

SMSCON can:

* autoload at boot (this is default set at install of smscon package); when device reboots it loads <code>smscon_daemon</code> in the background.
* creates a log file (on the device)
* detect SIM card change and sends new phonenumber and IMSI code (returns SMS) to other known mobile number; if somebody has stolen your phone and put his/hers own SIM card in it.
* send current GPS location coordinates (returns SMS or EMAIL with GoogleMaps picture with location on it).
* reboot the phone; only works if your SIM card hasn't a lock code.
* shutdown the phone.
* open a reverse ssh connection to your own server (GPRS connection); control the device at CLI level from your own home.
* email a frontcam picture to your email address (GPRS connection); to see where your phone is or who is using it.
* send the current remaining battery charge (returns SMS).
* make the phone call you; you can listen where your phone is (returns phonecall)
* lock the device; nobody can control your device anymore.

=Installation=

SMSCON is writen in Python and needs the following packages installed on your device to install and run:

<pre>
apt-get install maemo-python-device-env
apt-get install python-location
apt-get install pexpect
apt-get install gstreamer-tools
apt-get install openssh
</pre>

The two (<code>smscon</code> and <code>smscon_daemon</code>) are placed in the <code>/usr/bin</code> directory.

Also you need a fixed IP address on your remote server for the reverse-ssh (port 22) connection, if you want to use the 'Remoteon' / 'Remoteoff' function.

=Usage=

SMSCON is triggered by a SMS message with a predefined known command and then will execute the task in the background. If so it will send a reply SMS with the information.

==Commands==
The default commands are:
<pre>
Nokia-N900:~# smscon -sms
COM_CHECK = 'Check'
COM_REBOOT = 'Reboot'
COM_POWEROFF = 'Poweroff'
COM_POWER = 'Power'
COM_LOCATION = 'Location'
COM_REMOTEON = 'Remoteon'
COM_REMOTEOFF = 'Remoteoff'
COM_CAMERA = 'Camera'
COM_CALL = 'Call'
COM_LOCK = 'Lock'
COM_UNLOCK = 'Unlock'
COM_TRACKON = 'Trackon'
COM_TRACKOFF = 'Trackoff'
</pre>

These commands can be altered in the <code>smscon_config</code> file:

<pre>
# smscon user settings (v0.4.2)
# (edit only the user settings below!)

# Sms settings
SENDERNUMBER = '+XXXXXXXXXXX'

# Sms commands
COM_CHECK = 'Check'
COM_REBOOT = 'Reboot'
COM_POWEROFF = 'Poweroff'
COM_POWER = 'Power'
COM_LOCATION = 'Location'
COM_REMOTEON = 'Remoteon'
COM_REMOTEOFF = 'Remoteoff'
COM_CAMERA = 'Camera'
COM_CALL = 'Call'
COM_LOCK = 'Lock'
COM_UNLOCK = 'Unlock'
COM_TRACKON = 'Trackon'
COM_TRACKOFF = 'Trackoff'

# Email settings
# (only works for smtp access without secure authentication!)
EMAILADDRESS = 'XXXXX@XXXXXXXXXXX.XX'
USER = 'XXXXXXXX'
PASSWORD = 'XXXXXXXX'
EMAILFROM = 'XXXXXXXX@XXXXXX.XX'
MAILSERVER = 'XXXX.XXXXXX.XX'
MAILPORT = 25

# Reverse-ssh settings
REMOTEHOST = 'XXXXXXXXXXX.XX'
REMOTEPORT = 22
REMOTEUSER = 'XXXXXXXXXXXXX'
REMOTEPASSWORD = 'XXXXXXXXXX'

# Send acknowledge sms
# (send acknowledge sms after receiving valid sms command: 'yes' / 'no')
COMMANDREPLY = 'no'

# Device lock
# (lock device after receiving valid sms command: 'yes' / 'no')
AUTODEVICELOCK = 'no'

# Gps setings
# (if no gps coordinates acquired after 600 seconds then stop)
GPSTIMEOUT = 600
# (number of gps coordinates to acquire and use the most accurate in "Location" mode)
GPSPOLLING = 4
# (time between sending coordinate sms in 'Trackon' mode: 10 / 20 / 30 / 60 / 120)
GPSINTERVAL = 60
# (method to send gps coordinates: 'email' / 'sms')
GPSSEND = 'email'
</pre>

==Options==
The available options for SMSCON are:

<pre>Nokia-N900:~# smscon
== smscon v0.4.2 - Nokia N900 remote control utility ==
Options:
-start : start smscon_daemon
-stop : stop smscon_daemon
-status : get smscon_daemon status
-log : show log file
-del log : erase log file
-sms : show sms commands
-help : this help menu
Special options:
-boot : start smscon_daemon at device boot
-unboot : remove start of smscon_daemon at device boot
-reset : factory default
-imsi : show imsi code file
-del imsi : delete smscon_code file
-init : create default smscon_config
-del config : delete smscon_config file
</pre>

SMSCON is intended for people who have Python programming / Linux experience so you can adjust the script to their own needs.

==After installation==

After installation <code>smscon</code> will generate a new configuration file (<code>/usr/bin/smscon_config</code>) which you *must* edit to your own needs (i.e. change all "xxxxxxx"'s).

'''''Warning:''' Use Putty / WinSCP on Windows for this. Don't use a Windows editor, this may break the config file!''

SMSCON will also be installed to autoload at boot, this can be disabled with the command "<code>smscon -unboot</code>" and re-enabled by "<code>smscon -boot</code>".

The first time you start SMSCON (<code>smscon -start</code>) it loads the configured user settings file and is now active. <code>smscon_daemon</code> then stores your valid IMSI code in a file (<code>/usr/bin/smscon_code</code>) if the file doesn't exist. When later a new SIM card is inserted the new IMSI code is verified with the code in the stored file. This is the "SIM card change detect".

<pre>
Nokia-N900:~# smscon -start
smscon_daemon started.
</pre>

All user action and behavior of <code>smscon_daemon</code> will be logged in the log file:

<pre>
Nokia-N900:~# smscon -log
SMSCON INFO: smscon_daemon active (09-09-2010 11:00:48)
DAEMON INFO: user settings succesfully loaded from "smscon_config" file (09-09-2010 11:00:49)
DAEMON INFO: reading valid IMSI code (XXXXXXXXXXXXXXX) from file (09-09-2010 11:00:49)
DAEMON INFO: authorized IMSI code found (09-09-2010 11:00:49)
DAEMON INFO: smscon autoloads at boot (09-09-2010 11:00:49)
</pre>

==Remote SSH connection==

When the (reverse-)SSH connection is made (default command 'Remoteon' / 'Remoteoff') you can from the server side (your own server) connect to your Nokia device with the following command:

<pre>
ssh -p 8080 localhost -l root
</pre>

=Current version v0.4.3=

REMOVE PREVIOUS VERSION FROM NOKIA BEFORE USING 0.4.0 or higher
(reason: major change in <code>smscon_config</code> file)!

* new sms number now only save in <code>smscon_config</code> file if sms contains command. This behavior wasn't in 0.4.2; all sms numbers were saved, bug fix.
* bug fixes.
* sms commands have changed; you can now use spaces in commands (THIS IS NOT TRUE, DON'T USE SPACES).
* <code>smscon_daemon</code> will use only GPRS connection for sending email and reverse-ssh connection.
* <code>smscon_daemon</code> will lock the device after first valid sms command is received (user configurable).
* <code>smscon_daemon</code> now stores the phonenumber where you send your control sms's from into <code>smscon_config</code> (<code>SENDERNUMBER</code>).
* added new control command "Lock" and "Unlock"; you now can lock and unlock your device so nobody can use your device.
* added new control command "Trackon" and "Trackoff"; continiously send (after <code>GPSINTERVAL</code> time) sms's (with current location) or email messages (HTML email with current location as a GoogleMaps picture!).
* at the moment SMSCON can only connect to a smtp server (for sending email) without secure authentication. (will be solved in the future I hope).
* email sending and ssh connection -only works- through GPRS connection.
* when installing future updates of SMSCON user settings file (<code>smscon_config</code>) is not deleted or overwritten (only for version 0.4.0 or higher)
* command smscon -reset resets your complete configuration to the state after your smscon package installation. (deleting boot, config, code and log file)
* <code>smscon_daemon</code> will stop if no SIM card is found at boot. No SMS sending/receiving capability --> no control.
* changed the way the log file is shown.

=Known Issues=
==Version 0.4.3 (current)==
* "Trackon" is reported not to work (confirmed)
* <code>smscon_daemon</code> does not start at boot when requested (confirmed)

==Version 0.4.2==
* the default number is replaced by every mail received and not only those requesting a command. (confirmed & fixed in version 0.4.3)

==Version 0.4.1==
* "Trackon" is reported not to work (confirmed)
* Reply command sends duplicates (unconfirmed)
==Version 0.4.0==
* will not work due to a typo in variable name (confirmed and fixed in version 0.4.1)

=Future development=

* saving all <code>smscon_config</code> user variables in gconf database. No need for <code>smscon_config</code> file anymore.
* only send camera picture (command "Camera") when keyboard slider is opened.

=Testers needed=

Please test this software, I like to hear if it works for you or not. I only could test it with two Vodafone SIM cards from The Netherlands, I want to know if it also works with other cards and networks in other countries...

=License=
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published
by the Free Software Foundation; version 2 only.

=Disclaimer=
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

[[Category:Software]]
[[Category:N900]]

SMSCON

2010-09-09T20:58:30Z

82.95.252.184: /* Current version v0.4.0 */

SMSCON provides complete control of your [[Nokia N900|N900]] by sending SMS messages to it. This is particularly handy in case you cannot find your phone, for example if it has been lost or stolen.

Smscon is a two part Python script running in CLI; <code>smscon</code> and <code>smscon_daemon</code>. <code>smscon</code> is the CLI control part and <code>smscon_daemon</code> is the "running in the background" part. The configuration file for all the user settings is in the <code>smscon_config</code> file.

==What can it do==

Smscon can:

* autoload at boot (this is default set at install of smscon package); when device reboots it loads <code>smscon_daemon</code> in the background.
* creates a log file (on the device)
* detect SIM card change and sends new phonenumber and IMSI code (returns SMS) to other known mobile number; if somebody has stolen your phone and put his/hers own SIM card in it.
* send current GPS location coordinates (returns SMS or EMAIL with GoogleMaps picture with location on it).
* reboot the phone; only works if your SIM card hasn't a lock code.
* shutdown the phone.
* open a reverse ssh connection to your own server (GPRS connection); control the device at CLI level from your own home.
* email a frontcam picture to your email address (GPRS connection); to see where your phone is or who is using it.
* send the current remaining battery charge (returns SMS).
* make the phone call you; you can listen where your phone is (returns phonecall)
* lock the device; nobody can control your device anymore.

==Installation==

Smscon is writen in Python and needs the following packages installed on your device to install and run:

<pre>
apt-get install maemo-python-device-env (the Python language package)
apt-get install python-location
apt-get install pexpect
apt-get install gstreamer-tools
apt-get install openssh
</pre>

The two (<code>smscon</code> and <code>smscon_daemon</code>) are placed in the <code>/usr/bin</code> directory.

Also you need a fixed IP address on your remote server for the reverse-ssh (port 22) connection, if you want to use the 'Remoteon' / 'Remoteoff' function.

==Usage==

Smscon is triggered by a SMS message with a predefined known command and then will execute the task in the background. If so it will send a reply SMS with the information.

The default commands are:
<pre>
Nokia-N900:~# smscon -sms
COM_CHECK = 'Check'
COM_REBOOT = 'Reboot'
COM_POWEROFF = 'Poweroff'
COM_POWER = 'Power'
COM_LOCATION = 'Location'
COM_REMOTEON = 'Remoteon'
COM_REMOTEOFF = 'Remoteoff'
COM_CAMERA = 'Camera'
COM_CALL = 'Call'
COM_LOCK = 'Lock'
COM_UNLOCK = 'Unlock'
COM_TRACKON = 'Trackon'
COM_TRACKOFF = 'Trackoff'
</pre>

These commands can be altered in the <code>smscon_config</code> file:

<pre>
# smscon user settings (v0.4.0)
# (edit only the user settings below!)

# Sms settings
SENDERNUMBER = '+XXXXXXXXXXX'

# Sms commands
COM_CHECK = 'Check'
COM_REBOOT = 'Reboot'
COM_POWEROFF = 'Poweroff'
COM_POWER = 'Power'
COM_LOCATION = 'Location'
COM_REMOTEON = 'Remoteon'
COM_REMOTEOFF = 'Remoteoff'
COM_CAMERA = 'Camera'
COM_CALL = 'Call'
COM_LOCK = 'Lock'
COM_UNLOCK = 'Unlock'
COM_TRACKON = 'Trackon'
COM_TRACKOFF = 'Trackoff'

# Email settings
# (only works for smtp access without secure authentication!)
EMAILADDRESS = 'XXXXX@XXXXXXXXXXX.XX'
USER = 'XXXXXXXX'
PASSWORD = 'XXXXXXXX'
EMAILFROM = 'XXXXXXXX@XXXXXX.XX'
MAILSERVER = 'XXXX.XXXXXX.XX'
MAILPORT = 25

# Reverse-ssh settings
REMOTEHOST = 'XXXXXXXXXXX.XX'
REMOTEPORT = 22
REMOTEUSER = 'XXXXXXXXXXXXX'
REMOTEPASSWORD = 'XXXXXXXXXX'

# Send acknowledge sms
# (send acknowledge sms after receiving valid sms command: 'yes' / 'no')
COMMANDREPLY = 'no'

# Device lock
# (lock device after receiving valid sms command: 'yes' / 'no')
AUTODEVICELOCK = 'no'

# Gps setings
# (if no gps coordinates acquired after 600 seconds then stop)
GPSTIMEOUT = 600
# (number of gps coordinates to acquire and use the most accurate in "Location" mode)
GPSPOLLING = 4
# (time between sending coordinate sms in 'Trackon' mode: 10 / 20 / 30 / 60 / 120)
GPSINTERVAL = 60
# (method to send gps coordinates: 'email' / 'sms')
GPSSEND = 'email'
</pre>

Options for smscon are:

<pre>Nokia-N900:~# smscon
== smscon v0.4.0 - Nokia N900 remote control utility ==
Options:
-start : start smscon_daemon
-stop : stop smscon_daemon
-status : get smscon_daemon status
-log : show log file
-del log : erase log file
-sms : show sms commands
-help : this help menu
Special options:
-boot : start smscon_daemon at device boot
-unboot : remove start of smscon_daemon at device boot
-reset : factory default
-imsi : show imsi code file
-del imsi : delete smscon_code file
-init : create default smscon_config
-del config : delete smscon_config file
</pre>

Smscon is intended for people who have Python programming / Linux experience so you can adjust the script to your own needs.

==After installation==

After installation <code>smscon</code> will generate a new config file (<code>/usr/bin/smscon_config</code>) which you *must* edit to your own needs (change all "xxxxxxx"'s). I use Putty / WinSCP on Windows for this. Don't use a Windows editor, this may break the config file! Smscon will also be installed to autoload at boot, this can be disabled with the command "<code>smscon -unboot</code>" and re-enabled by "<code>smscon -boot</code>".

The first time you start <code>smscon</code> (<code>smscon -start</code>) it loads the configured user settings file and is now active. <code>smscon_daemon</code> then stores your valid IMSI code in a file (<code>/usr/bin/smscon_code</code>) if the file doesn't exist. When later a new SIM card is inserted the new IMSI code is verified with the code in the stored file. This is the "SIM card change detect".

<pre>
Nokia-N900:~# smscon -start
smscon_daemon started.
</pre>

All user action and behavior of <code>smscon_daemon</code> will be logged in the log file:

<pre>
Nokia-N900:~# smscon -log
SMSCON INFO: smscon_daemon active (09-09-2010 11:00:48)
DAEMON INFO: user settings succesfully loaded from "smscon_config" file (09-09-2010 11:00:49)
DAEMON INFO: reading valid IMSI code (XXXXXXXXXXXXXXX) from file (09-09-2010 11:00:49)
DAEMON INFO: authorized IMSI code found (09-09-2010 11:00:49)
DAEMON INFO: smscon autoloads at boot (09-09-2010 11:00:49)
</pre>

==Remote SSH connection==

When the (reverse-)SSH connection is made (default command 'Remoteon' / 'Remoteoff') you can from the server side (your own server) connect to your Nokia device with the following command:

<pre>
ssh -p 8080 localhost -l root
</pre>

==Testers needed==

Please test this software, I like to hear if it works for you or not. I only could test it with two Vodafone SIM cards from The Netherlands, I want to know if it also works with other cards and networks in other countries...

==Current version v0.4.0==

* bug fixes, bug fixes, bug fixes in data connection handling (I hope, you test it).
* sms commands have changed; you can now use spaces in commands.
* <code>smscon_daemon</code> will use only GPRS connection for sending email and reverse-ssh connection.
* <code>smscon_daemon</code> will lock the device after first valid sms command is received (user configurable).
* <code>smscon_daemon</code> now stores the phonenumber where you send your control sms's from into <code>smscon_config</code> (<code>SENDERNUMBER</code>).
* added new control command "Lock" and "Unlock"; you now can lock and unlock your device so nobody can use your device.
* added new control command "Trackon" and "Trackoff"; continiously send (after <code>GPSINTERVAL</code> time) sms's (with current location) or email messages (HTML email with current location as a GoogleMaps picture!).
* at the moment smscon can only connect to a smtp server (for sending email) without secure authentication. (will be solved in the future I hope).
* email sending and ssh connection -only works- through GPRS connection.
* when installing future updates of smscon user settings file (<code>smscon_config</code>) is not deleted or overwritten.
* command smscon -reset resets your complete configuration to the state after your smscon package installation. (deleting boot, config, code and log file)
* <code>smscon_daemon</code> will stop if no SIM card is found at boot. No sms sending/receiving capability --> no control.
* changed the way the log file is shown.

==Future development==

* saving all <code>smscon_config</code> user variables in gconf database. No need for <code>smscon_config</code> file anymore.
* only send camera picture (command "Camera") when keyboard slider is opened.

==Disclaimer==

If this software does harmfull/unwanted things (not to be expected) to your device in any way I can't be responsible for this.

[[Category:Software]]
[[Category:N900]]

N900 Hardware Phone

2010-08-11T21:25:53Z

82.95.252.184: /* AT commands */

The [[Nokia N900|N900]], unlike previous Nokia internet tablets has a phone module.

==Hardware==

The phone is a 2G/3G modem, with quadband GSM, and several bands of 3G. It may not have the required band for 3G in your country, for example, only one US carrier (T-Mobile) and only one Canadian carrier (Wind Mobile) support 3G on the N900.

The phone module controls the [[N900 Hardware GPS|GPS]], and contains software to generate locations.

==Software==

For the GPS, [http://maemo.org/api_refs/5.0/5.0-final/liblocation/ liblocation] is used.

The modem can be accessed 'directly' - through pnatd.

[http://www.gossamer-threads.com/lists/maemo/developers/59363 This thread on the maemo-developer] mailing list gives some examples of using pnatd - but it is not a reference guide.

[[Documentation/Maemo_5_Developer_Guide/Using_Connectivity_Components/Maemo_Connectivity#Internet_Access|ICD]] is the daemon that deals with internet connectivity, including managing data connections to the phone.

More documentation on ICD is [http://maemo.org/api_refs/5.0/5.0-final/icd2/ found here].

SMSs are stored using [http://maemo.org/api_refs/5.0/5.0-final/eventlogger/ eventlogger]

wappushd-dev

===AT commands===
* Modem model number.
at+cgmm
Nokia N900
* Modem serial number
at+cgsn
314159230138902
* Modem manufacturer
at+gmi
Nokia
* Connection quality?
at+csq
+CSQ: 6,99
* Modem capability
at+gcap
+GCAP: +CGSM,+DS,+W

at+cpas
+CPAS: 0

* List Operators
at+COPS=?
+COPS: (2,"T-Mobile",,"23430",0),
(3,"O2 - UK",,"23410",0),,(0,1,3),(0,2)
* Modem version number
at+gmr
V ICPR82_10w08
25-02-10
RX-51
(c) Nokia
Nokia N900 (RX-51 rev 2101)
Maemo 5 (10.2010.19.1.203.1)
Linux version 2.6.28-omap1
Product 0593611A
*IMSI
at+cimi
234308342147672
*Subscriber number (read from SIM, may not work with some SIMs)
at+cnum
+CNUM: ,"+447443895922",145

at+creg=1
OK

+CREG: 2

* SMS commands
at+cmgf
ERROR
at+cmgs
ERROR

* Battery charge information
at+cbc
+CBC: 0,63

at+ceer
OK

at+cmer
ERROR
at+cpas
+CPAS: 2

OK
at+cpas=?
+CPAS: (0,2,3,4)

at+clcc
OK

[[Category:N900 Hardware]]
[[Category:Cellular]]

Phone control

2010-05-30T08:40:27Z

82.95.252.184: /* Media player */

{{Recommended phone usage}}

=D-Bus=

These D-Bus commands can be run from terminal or as shell scripts. Useful for scheduling events with [[fcron]], executing from [[Desktop Command Execution Widget scripts|Desktop Command Execution Widget]] or [[Queen BeeCon Widget]], startup events, install scripts, etc. They should be run as:

run-standalone.sh SCRIPT.sh
run-standalone.sh dbus-send COMMAND

This is important to set up the environment correctly otherwise they may barf. If run as user "user" this is not needed.

Also note that most commands don't need "--print-reply" option. Those that don't need it should be '''tested without it''' and this page should be edited.

==Phone==

===Open Phone application===

dbus-send --type=method_call --dest=com.nokia.HildonDesktop.AppMgr /com/nokia/HildonDesktop/AppMgr com.nokia.HildonDesktop.AppMgr.LaunchApplication string:"rtcom-call-ui"

===Make a phone call===

dbus-send --system --type=method_call --print-reply --dest=com.nokia.csd.Call /com/nokia/csd/call com.nokia.csd.Call.CreateWith string:"$NUMBER" uint32:0

Change $NUMBER to phone number you want to call.

===End current phone call===

dbus-send --system --print-reply --dest=com.nokia.csd.Call /com/nokia/csd/call com.nokia.csd.Call.Release

This will release/end/hangup/reject the current call (or possibly all calls if more then one call is active - needs testing to verify behavior when more then 1 call active) or do nothing if no calls are active.

===Answer current phone call===

dbus-send --system --print-reply --dest=com.nokia.csd.Call /com/nokia/csd/call/1 com.nokia.csd.Call.Instance.Answer

This will answer/pickup the current (first) call.

TODO: Early experiments show that this function throws <tt>com.nokia.csd.Call.Error.NotAllowed</tt> exception. How to get around this?

===Get [[:wikipedia:International_Mobile_Equipment_Identity|IMEI]]===

dbus-send --system --type=method_call --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM/security Phone.Sim.Security.get_imei

===Get [[:wikipedia:International_Mobile_Subscriber_Identity|IMSI]]===

dbus-send --system --type=method_call --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_imsi

===Get phone registration status===

dbus-send --system --type=method_call --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_registration_status

===Turn loudspeaker on===

dbus-send --type=method_call --dest=com.nokia.osso_hp_ls_controller /com/nokia/osso_hp_ls_controller com.nokia.osso_hp_ls_controller.loudspeaker.force_loudspeaker_off

===Turn loudspeaker off===

dbus-send --type=method_call --dest=com.nokia.osso_hp_ls_controller /com/nokia/osso_hp_ls_controller com.nokia.osso_hp_ls_controller.loudspeaker.force_loudspeaker_on

===Start vibrating===

dbus-send --system --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_vibrator_pattern_activate string:PatternIncomingCall

===Stop vibrating===

dbus-send --system --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_vibrator_pattern_deactivate string:PatternIncomingCall

==Profiles==

===Set General===

dbus-send --type=method_call --dest=com.nokia.profiled /com/nokia/profiled com.nokia.profiled.set_profile string:"general"

===Set Silent===

dbus-send --type=method_call --dest=com.nokia.profiled /com/nokia/profiled com.nokia.profiled.set_profile string:"silent"

===Query current profile===

dbus-send --type=method_call --print-reply --dest=com.nokia.profiled /com/nokia/profiled com.nokia.profiled.get_profile

===List all profiles===

dbus-send --type=method_call --print-reply --dest=com.nokia.profiled /com/nokia/profiled com.nokia.profiled.get_profiles

==LED==

===Activate LEDs===

dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:"PatternCommunicationIM"

===Deactivate LEDs===

dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_deactivate string:"PatternCommunicationIM"

==Messaging==

===New e-mail===

dbus-send --type=method_call --dest=com.nokia.modest /com/nokia/modest com.nokia.modest.MailTo string:"mailto:"

===Send and receive e-mail===

It works, but it takes looong time (up to minute and a half) via GPRS (2.5, 3 or 3.5). Network and/or speed is not the problem, it just takes long via GPRS. It is much faster via Wi-Fi.

dbus-send --type=method_call --dest=com.nokia.modest /com/nokia/modest com.nokia.modest.SendReceive

===Set presence===

dbus-send --type=method_call --print-reply --dest=org.freedesktop.Telepathy.MissionControl /org/freedesktop/Telepathy/MissionControl org.freedesktop.Telepathy.MissionControl.SetPresence uint32:2 string:"I'm here"

==Media player==

===Open file in media player===

dbus-send --dest=com.nokia.mediaplayer /com/nokia/mediaplayer com.nokia.mediaplayer.mime_open string:"file:///$1"

===Pause what's currently playing===

dbus-send --dest=com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer /com/nokia/mafw/renderer/gstrenderer com.nokia.mafw.renderer.pause

===Stop what's currently playing===

dbus-send --dest=com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer /com/nokia/mafw/renderer/gstrenderer com.nokia.mafw.renderer.stop

===Play what's currently selected===

dbus-send --dest=com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer /com/nokia/mafw/renderer/gstrenderer com.nokia.mafw.renderer.play

===Play next mediafile===

dbus-send --dest=com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer /com/nokia/mafw/renderer/gstrenderer com.nokia.mafw.renderer.next

===Play previous mediafile===

dbus-send --dest=com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer /com/nokia/mafw/renderer/gstrenderer com.nokia.mafw.renderer.previous

==Notifications==

===Send notification (orange one line popup)===

dbus-send --type=method_call --dest=org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.SystemNoteInfoprint string:"NOTIFICATION"

===Send dialog notification (orange multi line popup requiring user interaction)===

dbus-send --type=method_call --dest=org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.SystemNoteDialog string:"QUESTION?" uint32:0 string:"OK"

Not sure what string "OK" does, but it is needed and can be anything.

==Securing==

===Lock===

dbus-send --system --type=method_call --dest=com.nokia.system_ui /com/nokia/system_ui/request com.nokia.system_ui.request.devlock_open string:"com.nokia.mce" string:"/com/nokia/mce/request" string:"com.nokia.mce.request" string:"devlock_callback" uint32:'3'

===Unlock===

dbus-send --system --type=method_call --dest=com.nokia.system_ui /com/nokia/system_ui/request com.nokia.system_ui.request.devlock_close string:"com.nokia.mce" string:"/com/nokia/mce/request" string:"com.nokia.mce.request" string:"devlock_callback" uint32:'0'

===Lock screen and keys===

dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_tklock_mode_change string:"locked"

===Unlock screen and keys===

dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_tklock_mode_change string:"unlocked"

==Networking==

===Connect to specific saved connection===

dbus-send --system --type=method_call --dest=com.nokia.icd /com/nokia/icd com.nokia.icd.connect string:"IAP_ID" uint32:0

IAP_ID is internet access point identifier and can be obtained with the following command:

gconftool -R /system/osso/connectivity/IAP

Find lines which matches /system/osso/connectivity/IAP/<IAP_ID>

For GPRS connections replace "@32@" with a space in IAP_ID string.

Keep in mind that phone has to be disconnected in order to connect via this call.

===Connect to any saved connection===

dbus-send --system --type=method_call --dest=com.nokia.icd /com/nokia/icd com.nokia.icd.connect string:"[ANY]" uint32:0

===Disconnect internet===

dbus-send --system --dest=com.nokia.icd /com/nokia/icd_ui com.nokia.icd_ui.disconnect boolean:true

===Connect (show change connection UI)===

dbus-send --system --type=method_call --dest=com.nokia.icd_ui /com/nokia/icd_ui com.nokia.icd_ui.show_conn_dlg boolean:false

If "boolean:true" at the end, one-line notification saying "No saved connections available" appears. Maybe affects more than that?

===Enable cellular radio===

dbus-send --system --type=method_call --dest=com.nokia.phone.SSC /com/nokia/phone/SSC com.nokia.phone.SSC.set_radio boolean:true

===Disable cellular radio===

dbus-send --system --type=method_call --dest=com.nokia.phone.SSC /com/nokia/phone/SSC com.nokia.phone.SSC.set_radio boolean:false

==Radio mode==

===2G===

dbus-send --system --type=method_call --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.set_selected_radio_access_technology byte:1

===3G===

dbus-send --system --type=method_call --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.set_selected_radio_access_technology byte:2

===Dual===

dbus-send --system --type=method_call --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.set_selected_radio_access_technology byte:0

==Bluetooth==

===Identify adapter path===

You need to know adapter path in order to send D-Bus call to the right place. You can get it with entering this command into the terminal:

dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.ListAdapters | awk -F'"' '/at/ {print $2}'

===Enable===

Using the adapter path value returned with previous command, for example ''/org/bluez/906/hci0''.

dbus-send --system --type=method_call --dest=org.bluez /org/bluez/906/hci0 org.bluez.Adapter.SetProperty string:Powered variant:boolean:true

This one automatically inserts adapter path:

dbus-send --system --type=method_call --dest=org.bluez $(dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.ListAdapters | awk -F'"' '/at/ {print $2}') org.bluez.Adapter.SetProperty string:Powered variant:boolean:true

===Disable===

dbus-send --system --type=method_call --dest=org.bluez /org/bluez/906/hci0 org.bluez.Adapter.SetProperty string:Powered variant:boolean:false

With auto-discovery of adapter path:

dbus-send --system --type=method_call --dest=org.bluez $(dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.ListAdapters | awk -F'"' '/at/ {print $2}') org.bluez.Adapter.SetProperty string:Powered variant:boolean:false

===Connect to specific device===

devmac=00:11:22:33:44:55
service=AudioSink

adapter=$(dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.ListAdapters | awk -F'"' '/at/ {print $2}')
device=$(dbus-send --system --print-reply --dest=org.bluez ${adapter} org.bluez.Adapter.FindDevice string:${devmac} | sed -ne 's/^.*object path //p' -e 's/"//g')
dbus-send --system --type=method_call --print-reply --dest=org.bluez ${device} org.bluez.${service}.Connect

Change the AudoSink to any service and the devmac to the MAC of bluetooth device.

==Check for updates==

dbus-send --type=method_call --dest=com.nokia.hildon_application_manager /com/nokia/hildon_application_manager com.nokia.hildon_application_manager.check_for_updates

==Open link in browser==

dbus-send --system --type=method_call --dest=com.nokia.osso_browser /com/nokia/osso_browser/request com.nokia.osso_browser.load_url string:"google.com"

==Reboot==

dbus-send --system --type=method_call --print-reply --dest=com.nokia.mce "/com/nokia/mce/request" com.nokia.mce.request.req_reboot
This is same as rebooting from power key menu (needs uncommenting in certain XML file to appear) and has been identified as insecure way to reboot the device (no filesystem synchronization, etc.). Better command is to simply enter "reboot" in root terminal.

==Shutdown==

dbus-send --system --type=method_call --print-reply --dest=com.nokia.mce "/com/nokia/mce/request" com.nokia.mce.request.req_shutdown
See warning at reboot D-Bus call (needs testing).

==Show dashboard==

dbus-send /com/nokia/hildon_desktop com.nokia.hildon_desktop.exit_app_view

==Other==

===D-Bus Scripts===

You can also use [[DbusScripts|dbus-scripts]] to execute any command when various actions are triggered on D-Bus.

===Panucci (pause)===

dbus-send --type=method_call --dest=org.panucci.panucciInterface /panucciInterface org.panucci.panucciInterface.playPause

=GConf=

==Reset GPRS data counter==

The commands are PR1.2 compliant and do not work on previous versions.

gconftool-2 -u /system/osso/connectivity/network_type/GPRS/gprs_home_rx_bytes
gconftool-2 -u /system/osso/connectivity/network_type/GPRS/gprs_home_tx_bytes
gconftool-2 -s /system/osso/connectivity/network_type/GPRS/gprs_home_reset_time --type=string $(date +%s)

=Command line=

==Enable FM Transmitter==

/usr/bin/fmtx_client -p 1

==Disable FM Transmitter==

/usr/bin/fmtx_client -p 0

=GStreamer=

==Shoot photo after 10 seconds==

The camera application must be off for it to work. And of course the camera shutter must be open...

/bin/sleep 10 ; /usr/bin/gst-launch v4l2camsrc device=/dev/video0 num-buffers=1 \! video/x-raw-yuv,width=2592,height=1968 \! ffmpegcolorspace \! jpegenc \! filesink location=/home/user/MyDocs/DCIM/photo.jpg

To shoot from the front camera, change '''/dev/video0''' to '''/dev/video1''' and the proper resolution:

/bin/sleep 10 ; /usr/bin/gst-launch v4l2camsrc device=/dev/video1 num-buffers=1 \! video/x-raw-yuv,width=640,height=480 \! ffmpegcolorspace \! jpegenc \! filesink location=/home/user/MyDocs/DCIM/photo.jpg

Other way:

/bin/sleep 10; /usr/bin/gst-launch v4l2camsrc ! ffmpegcolorspace ! jpegenc ! identity error-after=1 ! filesink location=/home/user/MyDocs/DCIM/photo.jpg

=Python=

==Make a phone call==

import dbus
def place_call(number):
bus = dbus.SystemBus()
csd_call = dbus.Interface(bus.get_object('com.nokia.csd',
'/com/nokia/csd/call'),
'com.nokia.csd.Call')
csd_call.CreateWith(str(number), dbus.UInt32(0))

==Send SMS==

From:
http://talk.maemo.org/showpost.php?p=548948&postcount=52

#!/usr/bin/env python2.5

import pexpect
import time
from subprocess import *

child = pexpect.spawn('pnatd');
child.send('at\r');
time.sleep(0.25);
child.send('at+cmgf=1\r');
time.sleep(0.25);
child.send('at+cmgs="+XXXXXXX"\r');
child.send('SMSTEXTSMSTEXTSMSTEXT');
child.send(chr(26));
child.send(chr(26));
child.sendeof();

==Send dialog notification (orange multi line popup requiring user interaction)==

import dbus
def show_notification_dialog(message, mode="single"):
bus = dbus.SystemBus()
iface = dbus.Interface(bus.get_object('org.freedesktop.Notifications',
'/org/freedesktop/Notifications'),
'org.freedesktop.Notifications')
if mode == "single":
iface.SystemNoteInfoprint(message)
elif mode == "multiline":
iface.SystemNoteDialog(str(message), dbus.UInt32(0), 'Ok')

This function allows you to show notification either with multiline (on maemo pre-5 it will show a dialog with an "Ok" button) or single line (tiny notifications hiding automatically).

==Take a screenshot==

import gtk.gdk

w = gtk.gdk.get_default_root_window()
sz = w.get_size()
print "The size of the window is %d x %d" % sz
pb = gtk.gdk.Pixbuf(gtk.gdk.COLORSPACE_RGB,False,8,sz[0],sz[1])
pb = pb.get_from_drawable(w,w.get_colormap(),0,0,0,0,sz[0],sz[1])
if (pb != None):
pb.save("screenshot.png","png")
print "Screenshot saved to screenshot.png."
else:
print "Unable to get the screenshot."

Credits: took code from [http://stackoverflow.com/questions/69645/take-a-screenshot-via-a-python-script-linux here], where there is also a QT way to do it.

[[Category:Power users]]
[[Category:Development]]

Phone control

2010-05-30T08:39:20Z

82.95.252.184: /* Media player */

Phone control

2010-05-30T08:31:34Z

82.95.252.184: /* Media player */

{{Recommended phone usage}}

=D-Bus=

These D-Bus commands can be run from terminal or as shell scripts. Useful for scheduling events with [[fcron]], executing from [[Desktop Command Execution Widget scripts|Desktop Command Execution Widget]] or [[Queen BeeCon Widget]], startup events, install scripts, etc. They should be run as:

run-standalone.sh SCRIPT.sh
run-standalone.sh dbus-send COMMAND

This is important to set up the environment correctly otherwise they may barf. If run as user "user" this is not needed.

Also note that most commands don't need "--print-reply" option. Those that don't need it should be '''tested without it''' and this page should be edited.

==Phone==

===Open Phone application===

dbus-send --type=method_call --dest=com.nokia.HildonDesktop.AppMgr /com/nokia/HildonDesktop/AppMgr com.nokia.HildonDesktop.AppMgr.LaunchApplication string:"rtcom-call-ui"

===Make a phone call===

dbus-send --system --type=method_call --print-reply --dest=com.nokia.csd.Call /com/nokia/csd/call com.nokia.csd.Call.CreateWith string:"$NUMBER" uint32:0

Change $NUMBER to phone number you want to call.

===End current phone call===

dbus-send --system --print-reply --dest=com.nokia.csd.Call /com/nokia/csd/call com.nokia.csd.Call.Release

This will release/end/hangup/reject the current call (or possibly all calls if more then one call is active - needs testing to verify behavior when more then 1 call active) or do nothing if no calls are active.

===Answer current phone call===

dbus-send --system --print-reply --dest=com.nokia.csd.Call /com/nokia/csd/call/1 com.nokia.csd.Call.Instance.Answer

This will answer/pickup the current (first) call.

TODO: Early experiments show that this function throws <tt>com.nokia.csd.Call.Error.NotAllowed</tt> exception. How to get around this?

===Get [[:wikipedia:International_Mobile_Equipment_Identity|IMEI]]===

dbus-send --system --type=method_call --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM/security Phone.Sim.Security.get_imei

===Get [[:wikipedia:International_Mobile_Subscriber_Identity|IMSI]]===

dbus-send --system --type=method_call --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_imsi

===Get phone registration status===

dbus-send --system --type=method_call --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_registration_status

===Turn loudspeaker on===

dbus-send --type=method_call --dest=com.nokia.osso_hp_ls_controller /com/nokia/osso_hp_ls_controller com.nokia.osso_hp_ls_controller.loudspeaker.force_loudspeaker_off

===Turn loudspeaker off===

dbus-send --type=method_call --dest=com.nokia.osso_hp_ls_controller /com/nokia/osso_hp_ls_controller com.nokia.osso_hp_ls_controller.loudspeaker.force_loudspeaker_on

===Start vibrating===

dbus-send --system --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_vibrator_pattern_activate string:PatternIncomingCall

===Stop vibrating===

dbus-send --system --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_vibrator_pattern_deactivate string:PatternIncomingCall

==Profiles==

===Set General===

dbus-send --type=method_call --dest=com.nokia.profiled /com/nokia/profiled com.nokia.profiled.set_profile string:"general"

===Set Silent===

dbus-send --type=method_call --dest=com.nokia.profiled /com/nokia/profiled com.nokia.profiled.set_profile string:"silent"

===Query current profile===

dbus-send --type=method_call --print-reply --dest=com.nokia.profiled /com/nokia/profiled com.nokia.profiled.get_profile

===List all profiles===

dbus-send --type=method_call --print-reply --dest=com.nokia.profiled /com/nokia/profiled com.nokia.profiled.get_profiles

==LED==

===Activate LEDs===

dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:"PatternCommunicationIM"

===Deactivate LEDs===

dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_deactivate string:"PatternCommunicationIM"

==Messaging==

===New e-mail===

dbus-send --type=method_call --dest=com.nokia.modest /com/nokia/modest com.nokia.modest.MailTo string:"mailto:"

===Send and receive e-mail===

It works, but it takes looong time (up to minute and a half) via GPRS (2.5, 3 or 3.5). Network and/or speed is not the problem, it just takes long via GPRS. It is much faster via Wi-Fi.

dbus-send --type=method_call --dest=com.nokia.modest /com/nokia/modest com.nokia.modest.SendReceive

===Set presence===

dbus-send --type=method_call --print-reply --dest=org.freedesktop.Telepathy.MissionControl /org/freedesktop/Telepathy/MissionControl org.freedesktop.Telepathy.MissionControl.SetPresence uint32:2 string:"I'm here"

==Media player==

===Open file in media player===

dbus-send --dest=com.nokia.mediaplayer /com/nokia/mediaplayer com.nokia.mediaplayer.mime_open string:"file:///$1"

===Pause what's currently playing===

dbus-send --dest=com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer /com/nokia/mafw/renderer/gstrenderer com.nokia.mafw.renderer.pause

===Stop what's currently playing===

dbus-send --dest=com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer /com/nokia/mafw/renderer/gstrenderer com.nokia.mafw.renderer.stop

===Play what's currently selected===

dbus-send --dest=com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer /com/nokia/mafw/renderer/gstrenderer com.nokia.mafw.renderer.play

==Notifications==

===Send notification (orange one line popup)===

dbus-send --type=method_call --dest=org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.SystemNoteInfoprint string:"NOTIFICATION"

===Send dialog notification (orange multi line popup requiring user interaction)===

dbus-send --type=method_call --dest=org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.SystemNoteDialog string:"QUESTION?" uint32:0 string:"OK"

Not sure what string "OK" does, but it is needed and can be anything.

==Securing==

===Lock===

dbus-send --system --type=method_call --dest=com.nokia.system_ui /com/nokia/system_ui/request com.nokia.system_ui.request.devlock_open string:"com.nokia.mce" string:"/com/nokia/mce/request" string:"com.nokia.mce.request" string:"devlock_callback" uint32:'3'

===Unlock===

dbus-send --system --type=method_call --dest=com.nokia.system_ui /com/nokia/system_ui/request com.nokia.system_ui.request.devlock_close string:"com.nokia.mce" string:"/com/nokia/mce/request" string:"com.nokia.mce.request" string:"devlock_callback" uint32:'0'

===Lock screen and keys===

dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_tklock_mode_change string:"locked"

===Unlock screen and keys===

dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_tklock_mode_change string:"unlocked"

==Networking==

===Connect to specific saved connection===

dbus-send --system --type=method_call --dest=com.nokia.icd /com/nokia/icd com.nokia.icd.connect string:"IAP_ID" uint32:0

IAP_ID is internet access point identifier and can be obtained with the following command:

gconftool -R /system/osso/connectivity/IAP

Find lines which matches /system/osso/connectivity/IAP/<IAP_ID>

For GPRS connections replace "@32@" with a space in IAP_ID string.

Keep in mind that phone has to be disconnected in order to connect via this call.

===Connect to any saved connection===

dbus-send --system --type=method_call --dest=com.nokia.icd /com/nokia/icd com.nokia.icd.connect string:"[ANY]" uint32:0

===Disconnect internet===

dbus-send --system --dest=com.nokia.icd /com/nokia/icd_ui com.nokia.icd_ui.disconnect boolean:true

===Connect (show change connection UI)===

dbus-send --system --type=method_call --dest=com.nokia.icd_ui /com/nokia/icd_ui com.nokia.icd_ui.show_conn_dlg boolean:false

If "boolean:true" at the end, one-line notification saying "No saved connections available" appears. Maybe affects more than that?

===Enable cellular radio===

dbus-send --system --type=method_call --dest=com.nokia.phone.SSC /com/nokia/phone/SSC com.nokia.phone.SSC.set_radio boolean:true

===Disable cellular radio===

dbus-send --system --type=method_call --dest=com.nokia.phone.SSC /com/nokia/phone/SSC com.nokia.phone.SSC.set_radio boolean:false

==Radio mode==

===2G===

dbus-send --system --type=method_call --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.set_selected_radio_access_technology byte:1

===3G===

dbus-send --system --type=method_call --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.set_selected_radio_access_technology byte:2

===Dual===

dbus-send --system --type=method_call --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.set_selected_radio_access_technology byte:0

==Bluetooth==

===Identify adapter path===

You need to know adapter path in order to send D-Bus call to the right place. You can get it with entering this command into the terminal:

dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.ListAdapters | awk -F'"' '/at/ {print $2}'

===Enable===

Using the adapter path value returned with previous command, for example ''/org/bluez/906/hci0''.

dbus-send --system --type=method_call --dest=org.bluez /org/bluez/906/hci0 org.bluez.Adapter.SetProperty string:Powered variant:boolean:true

This one automatically inserts adapter path:

dbus-send --system --type=method_call --dest=org.bluez $(dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.ListAdapters | awk -F'"' '/at/ {print $2}') org.bluez.Adapter.SetProperty string:Powered variant:boolean:true

===Disable===

dbus-send --system --type=method_call --dest=org.bluez /org/bluez/906/hci0 org.bluez.Adapter.SetProperty string:Powered variant:boolean:false

With auto-discovery of adapter path:

dbus-send --system --type=method_call --dest=org.bluez $(dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.ListAdapters | awk -F'"' '/at/ {print $2}') org.bluez.Adapter.SetProperty string:Powered variant:boolean:false

===Connect to specific device===

devmac=00:11:22:33:44:55
service=AudioSink

adapter=$(dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.ListAdapters | awk -F'"' '/at/ {print $2}')
device=$(dbus-send --system --print-reply --dest=org.bluez ${adapter} org.bluez.Adapter.FindDevice string:${devmac} | sed -ne 's/^.*object path //p' -e 's/"//g')
dbus-send --system --type=method_call --print-reply --dest=org.bluez ${device} org.bluez.${service}.Connect

Change the AudoSink to any service and the devmac to the MAC of bluetooth device.

==Check for updates==

dbus-send --type=method_call --dest=com.nokia.hildon_application_manager /com/nokia/hildon_application_manager com.nokia.hildon_application_manager.check_for_updates

==Open link in browser==

dbus-send --system --type=method_call --dest=com.nokia.osso_browser /com/nokia/osso_browser/request com.nokia.osso_browser.load_url string:"google.com"

==Reboot==

dbus-send --system --type=method_call --print-reply --dest=com.nokia.mce "/com/nokia/mce/request" com.nokia.mce.request.req_reboot
This is same as rebooting from power key menu (needs uncommenting in certain XML file to appear) and has been identified as insecure way to reboot the device (no filesystem synchronization, etc.). Better command is to simply enter "reboot" in root terminal.

==Shutdown==

dbus-send --system --type=method_call --print-reply --dest=com.nokia.mce "/com/nokia/mce/request" com.nokia.mce.request.req_shutdown
See warning at reboot D-Bus call (needs testing).

==Show dashboard==

dbus-send /com/nokia/hildon_desktop com.nokia.hildon_desktop.exit_app_view

==Other==

===D-Bus Scripts===

You can also use [[DbusScripts|dbus-scripts]] to execute any command when various actions are triggered on D-Bus.

===Panucci (pause)===

dbus-send --type=method_call --dest=org.panucci.panucciInterface /panucciInterface org.panucci.panucciInterface.playPause

=GConf=

==Reset GPRS data counter==

The commands are PR1.2 compliant and do not work on previous versions.

gconftool-2 -u /system/osso/connectivity/network_type/GPRS/gprs_home_rx_bytes
gconftool-2 -u /system/osso/connectivity/network_type/GPRS/gprs_home_tx_bytes
gconftool-2 -s /system/osso/connectivity/network_type/GPRS/gprs_home_reset_time --type=string $(date +%s)

=Command line=

==Enable FM Transmitter==

/usr/bin/fmtx_client -p 1

==Disable FM Transmitter==

/usr/bin/fmtx_client -p 0

=GStreamer=

==Shoot photo after 10 seconds==

The camera application must be off for it to work. And of course the camera shutter must be open...

/bin/sleep 10 ; /usr/bin/gst-launch v4l2camsrc device=/dev/video0 num-buffers=1 \! video/x-raw-yuv,width=2592,height=1968 \! ffmpegcolorspace \! jpegenc \! filesink location=/home/user/MyDocs/DCIM/photo.jpg

To shoot from the front camera, change '''/dev/video0''' to '''/dev/video1''' and the proper resolution:

/bin/sleep 10 ; /usr/bin/gst-launch v4l2camsrc device=/dev/video1 num-buffers=1 \! video/x-raw-yuv,width=640,height=480 \! ffmpegcolorspace \! jpegenc \! filesink location=/home/user/MyDocs/DCIM/photo.jpg

Other way:

/bin/sleep 10; /usr/bin/gst-launch v4l2camsrc ! ffmpegcolorspace ! jpegenc ! identity error-after=1 ! filesink location=/home/user/MyDocs/DCIM/photo.jpg

=Python=

==Make a phone call==

import dbus
def place_call(number):
bus = dbus.SystemBus()
csd_call = dbus.Interface(bus.get_object('com.nokia.csd',
'/com/nokia/csd/call'),
'com.nokia.csd.Call')
csd_call.CreateWith(str(number), dbus.UInt32(0))

==Send SMS==

From:
http://talk.maemo.org/showpost.php?p=548948&postcount=52

#!/usr/bin/env python2.5

import pexpect
import time
from subprocess import *

child = pexpect.spawn('pnatd');
child.send('at\r');
time.sleep(0.25);
child.send('at+cmgf=1\r');
time.sleep(0.25);
child.send('at+cmgs="+XXXXXXX"\r');
child.send('SMSTEXTSMSTEXTSMSTEXT');
child.send(chr(26));
child.send(chr(26));
child.sendeof();

==Send dialog notification (orange multi line popup requiring user interaction)==

import dbus
def show_notification_dialog(message, mode="single"):
bus = dbus.SystemBus()
iface = dbus.Interface(bus.get_object('org.freedesktop.Notifications',
'/org/freedesktop/Notifications'),
'org.freedesktop.Notifications')
if mode == "single":
iface.SystemNoteInfoprint(message)
elif mode == "multiline":
iface.SystemNoteDialog(str(message), dbus.UInt32(0), 'Ok')

This function allows you to show notification either with multiline (on maemo pre-5 it will show a dialog with an "Ok" button) or single line (tiny notifications hiding automatically).

==Take a screenshot==

import gtk.gdk

w = gtk.gdk.get_default_root_window()
sz = w.get_size()
print "The size of the window is %d x %d" % sz
pb = gtk.gdk.Pixbuf(gtk.gdk.COLORSPACE_RGB,False,8,sz[0],sz[1])
pb = pb.get_from_drawable(w,w.get_colormap(),0,0,0,0,sz[0],sz[1])
if (pb != None):
pb.save("screenshot.png","png")
print "Screenshot saved to screenshot.png."
else:
print "Unable to get the screenshot."

Credits: took code from [http://stackoverflow.com/questions/69645/take-a-screenshot-via-a-python-script-linux here], where there is also a QT way to do it.

[[Category:Power users]]
[[Category:Development]]

Overclocking

2010-04-20T20:47:04Z

82.95.252.184: /* Battery */

=Overclocking=

This page is about overclocking the N900.
For the N8x0 see [http://talk.maemo.org/showthread.php?t=12464 this]

<nowiki>#</nowiki> ''WORK IN PROGRESS, HELP IF YOU WANT''

Overclocking is discussed in [http://talk.maemo.org/showthread.php?t=39753 this thread].
Benchmark results can be found [http://talk.maemo.org/showthread.php?p=605189 here].
If you're more interested in power saving read [http://talk.maemo.org/showthread.php?t=49654 this].

=Warnings=

- Overclocking WILL VOID YOUR WARRANTY 
- The lifetime of your device will get reduced 
- You could lose the data in your device (file system corruption) 
- Every device is an individual, what is stable for others might not be for you 
- If you encounter ANY unusual problems, lower your clock frequency 
- You do it at your own responsibility. No whining afterwards. If you're unsure, don't do it. 
- [http://depot.javispedro.com/nit/thewarningtm.jpeg Nokia's overclocking warning]: 500MHz is the normal frequency. Everything above is not good for your device, even with the stock kernel. 
- Igor Stoppa's [http://talk.maemo.org/showpost.php?p=596149&postcount=904 warning] and [http://talk.maemo.org/showpost.php?p=603833&postcount=66 comment]
- [http://talk.maemo.org/showpost.php?p=596274&postcount=937 chip vendors specs]

=Available kernels=

Overclocking requires installation of a custom kernel.
There are two types of kernels:
# modified PR1.1 kernels by Lehto and others. The only difference to the stock Nokia kernel is that the change the available hardcoded frequencies.
# enhanced kernels by titan. They are compatible with PR1.2 (!) , contain lots of additional features (IPv6, NAT etc) and bugfixes. In addition they include a large set of possible frequencies (125MHz-1.15GHz) which you manually set an try out without flashing a new kernel. The defaults are set to the standard 250-600MHz range. The kernel can be installed via HAM from the extras-devel catalouge.

== Installation of Lehto's PR1.1 kernels ==

[http://talk.maemo.org/showpost.php?p=594200&postcount=309 Lehto's Kernels]

[http://talk.maemo.org/showpost.php?p=595582&postcount=774 talk.maemo.org: Jakiman's Overclock Guide / Summary]

== Installation of titan's enhanced kernels ==
This kernel makes it possible dynamically change the maximum frequency up to 1.15GHz (supported frequencies are 125,250,500,550,600,700,750,805,850,900,950,1000,1100,1150MHz).
WARNING: Overclocking may damage your device and is at your own risk! It may void your warranty and destroy your data. You have been warned.

[http://talk.maemo.org/showthread.php?t=43420 talk.maemo.org: Discussion of the enhanded kernel]

'''Note:''' all commands on this page must be run as root in X Terminal (install rootsh package and enter "sudo gainroot")

=== Installation of the more stable [https://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/kernel-power-flasher/2.6.28-maemo24/ kernel (maemo24)] from extras-testing ===
With this kernel you can change the frequency limits, the voltages and DSP frequencies online.
It requires firmware PR1.1 or newer.
# Install the package kernel-power-settings (section system in HAM). It will automatically also install kernel-power-flasher.
# shutdown and boot again. There's no need for reflashing etc.
[Configuring_the_kernel_settings read this for configuration]

=== Installation of the experimental [https://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/kernel-power-flasher/2.6.28-maemo25/ kernel (maemo25)] from extras-devel ===
This kernel version contains additional experimental features and patches.
Changelogs are posted [https://garage.maemo.org/news/?group_id=1528 here].
# Install the package "Enhanced kernel for power users" (section system in HAM).
# shutdown and boot again. There's no need for reflashing etc.
Read the instructions for the stable kernel for more information.

=== Upgrade from older versions (< maemo24) ===
The package was previously called kernel-flasher-maemo.
If you have one of the older packages installed it it recommended that you upgrade in X Terminal
sudo gainroot
apt-get install -y kernel-power-flasher
apt-get remove kernel-flasher-maemo
If the new kernel still doesn't boot up, try
apt-get install --reinstall -y kernel-power kernel-power-flasher
Also try [http://talk.maemo.org/showpost.php?p=608343&postcount=2603 other hints] for deinstalling the old package.

Make sure you reset /etc/pmconfig to the defaults:
# Power management configuration file
enable_off_mode 1
sleep_while_idle 1
sr_vdd1_autocomp 0
sr_vdd2_autocomp 0
clocks_off_while_idle 1
voltage_off_while_idle 1
scaling_governor ondemand
scaling_max_freq 600000
scaling_min_freq 125000
sleep_ind 1

=== Deinstallation ===
sudo gainroot
apt-get install --reinstall -y kernel kernel-flasher
apt-get remove kernel-power kernel-power-modules

=== Configuring the kernel settings ===
[http://talk.maemo.org/showpost.php?p=610967&postcount=2718 read this for more details].

First verify, that the kernel is actually running:
uname -r
should return "2.6.28.10power-omap1"
It it does not, you should reboot or try to install again
apt-get install --reinstall -y kernel-power kernel-power-flasher
reboot, and test again.

Make sure the packages ''kernel-power-settings'' and ''rootsh'' are installed.
'''All commands need to be run as root user.'''
If you are normal user in X Terminal either "sudo gainroot" or prepend "sudo" to every command.

1) to try a configuration (you can replace "ideal" with default, lv, ulv, xlv or specify a file you created based on the template /usr/share/kernel-power-settings/default )
/usr/sbin/kernel-load /usr/share/kernel-power-settings/ideal
'''Note''': do [[NOT]] modify the files in /usr/share/kernel-power-settings/!
see '''Creating your own configuration:'' below.

2) to permanently install a default configuration
rm -f /etc/default/kernel-power
ln -s /usr/share/kernel-power-settings/ideal /etc/default/kernel-power
3) or your own config
rm -f /etc/default/kernel-power
cp <filename> /etc/default/kernel-power
4) and to immediately apply it
sudo /usr/sbin/kernel-load

'''For beginners:''' first reboot. then try 1) and check whether the device is stable. then do 2).

'''Creating your own configuration'''
5) copy the template to your mydocs (when not in mass storage mode)
cp /usr/share/kernel-power-settings/ideal /home/user/MyDocs/kernel.txt
6) edit the file ''/home/user/MyDocs/kernel.txt''. The defaults are
#UP_THRESHOLD=75
#SAMPLING_RATE=150000
VDD1_OPPS_VSEL="30 30 38 48 54 48 60 60 60 60 60 60 60 72 72"
DSP_OPPS_RATE="90 90 180 360 400 430 430 430 430 500 500 500 500 520 520"
MIN_FREQ=250000
MAX_FREQ=599000
SMARTREFLEX_VDD1=0
SMARTREFLEX_VDD2=0
For changing the frequency range change MIN_FREQ/MAX_FREQ (see "Temporarly change of the frequency limits" below ).
Either edit the file with an editor on your device (e.g., leafpad)
or USB mount it to edit it on the PC. unmount and unplug USB.
After editing load the configuration with
/usr/sbin/kernel-load /home/user/MyDocs/kernel.txt
and repeat 6) until you're happy.

7) to permanently install this new configuration
rm -f /etc/default/kernel-power
cp /home/user/MyDocs/kernel.txt /etc/default/kernel-power
/usr/sbin/kernel-load

8) to reset the device to the defaults use
rm -f /etc/default/kernel-power
/usr/sbin/kernel-load /usr/share/kernel-power-settings/default

'''Note''': the package automatically detects whether a certain misconfiguration has caused '''reboot loop.'''
It your device reboots twice within 5 minutes, it will load the default settings (250-600Mhz) so that you can fix or remove the invalid configuration file.
This also means that, when for some reason you manually reboot too quickly (<5min) your configuration will not be loaded.
To load it nonetheless run after booting
/usr/sbin/kernel-load

=== Temporarly change of the frequency limits ===
sudo gainroot
echo 250000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 599000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
The last line shows which values were actually set.
To set 125MHz use 124999, for 600MHz 599999, for everthing else x000 with x=MHz.
This setting takes effect immediately and is cleared with the next reboot.

=== Permanently change of the frequency limits ===
WARNING: Permanent overclocking is very dangerous!

Install kernel-power-settings and follow [http://talk.maemo.org/showpost.php?p=610967&postcount=2718 those instructions].

=== Battery ===
In kernels version >=maemo20 you can read out the current battery info:
modprobe bq27x00_battery
cat /sys/class/power_supply/bq27200-0/capacity
cat /sys/class/power_supply/bq27200-0/voltage_now
cat /sys/class/power_supply/bq27200-0/current_now
cat /sys/class/power_supply/bq27200-0/temp

*'capacity' value in percentage of battery level.
*'voltage_now' value in mV of battery voltage level.
*'current_now' value in mA of battery current consumption. (???)
*'temp' value in degrees C of battery temperature.

To remove this kernel module use:

modprobe -r bq27x00_battery

=== Holding a kernel version ===
It your manually installed kernel should be not upgraded to the one in extras* try [http://talk.maemo.org/showpost.php?p=603915&postcount=2063 this]:
echo kernel-power-flasher hold | dpkg --set-selections
echo kernel-power hold | dpkg --set-selections
echo kernel-power-modules hold | dpkg --set-selections
to unlock the version:
echo kernel-power-flasher install | dpkg --set-selections
echo kernel-power install | dpkg --set-selections
echo kernel-power-modules install | dpkg --set-selections

=== Remarks ===
# The screen calibration in settings crashes immediately. It is a known bug in the calibration app, not in the kernel. It's mentioned in the kernel package description and is due to additional evdev (joystick,mouse) support. Just calibrate once with the stock kernel before you install the fully featured kernel.
# The kernel supports 125MHz but this frequency is [http://talk.maemo.org/showpost.php?p=617488&postcount=3095 disabled by default]. In version <25, it is enabled by specifying "124999", in later versions it is set in ''/sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies'' and can be enabled with
echo > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
# similarily, individual frequencies can be disabled in >=v25
echo 125000 250000 750000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
# even if 125Mhz is disabled, the telephone app will always try to set the minimum freq. to 125Mhz after a phone call, but it is ignored unless you enable 125Mhz.
# if you enable 125MHz also set "echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load" [http://talk.maemo.org/showpost.php?p=602687&postcount=185 hint]

# [http://talk.maemo.org/showpost.php?p=597703&postcount=141 the 125MHz issue]
# Installing another version of the enhanced kernel will just overwrite the older version. The stock kernel modules are preserved so that you can simply reflash the stock kernel via USB.
# If you for some reason get errors like this during removal or installation "rm: cannot remove '/lib/modules/2.6.28.10maemo-lv-omap1/modules.*': No such file or directory".try this [http://talk.maemo.org/showpost.php?p=603938&postcount=196 workaround]. There was a bug in one of the early LV kernels but it should be fixed in more recent versions.
# This kernel will not conflict with the future PR1.2 upgrade. The upgrade will, however, overwrite this kernel and you'll have to install it again.

=Additional information and hints=

# the frequencies available in the Nokia kernel are: 250, 500, 550 and 600MHz.
# Nokia [http://talk.maemo.org/showpost.php?p=601691&postcount=1823 locks the device to 600MHz] during phone calls. This may be a bug. It also [http://talk.maemo.org/showpost.php?p=600721&postcount=1720 affects] Lehto's kernels.
# the telephone app is closed-source and broken. After a phone call it sets the maximum to 600Mhz and the minimum to 250MHz (or 125MHz if available) irrespective of what you have set before.
# when connected via USB the device locks the minimum frequency to 500Mhz.
# By default the device is configured to use 125MHz as the lowest frequency but it not enabled in the kernel [https://bugs.maemo.org/show_bug.cgi?id=7116 pmconfig bug]
# [http://talk.maemo.org/showpost.php?p=599870&postcount=170 improving responsiveness]
# [http://talk.maemo.org/showpost.php?p=599618&postcount=168 safe pmconfig configuration]
# the warning "WARNING: at arch/arm/mach-omap2/clock34xx.c:443 omap3_noncore_dpll_set_rate+0x28c/0x2dc()" in the kernel logs (dmesg) only happens if the invalid 800MHz frequency was selected. ignore it.
# [http://talk.maemo.org/showpost.php?p=603585&postcount=189 saving more battery power when idle]
# EvilJazz had photoshopped a [http://talk.maemo.org/showpost.php?p=605523&postcount=90 picture of a device being overclocked 1.7GHz]. It's a JOKE!
# reading one of the temperature sensors "cat /sys/devices/platform/omap34xx_temp/temp1_input"

=Useful stuff=

==Show current CPU frequency==

awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

==Set maximum CPU frequency==

From root terminal:

rootsh echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq | echo ""

Replace 600000 with desired maximum frequency. Pay attention to the two exceptions in titan's kernels (124999 and 599000). The list of available frequencies on your device/kernel can be obtained with command:

awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

==Script for analyzing time_in_state (by rooted) - rev6==

This script prints percentage of frequencies (states) used and some additional info useful for posting on the forum (debugging). It displays all frequencies, works with all kernels and it is not affected by the bug which resets minimum frequency after phone call.

The script is in active development. I'm adding new features and resolving bugs if they are reported. Please update your script to newest revision and report if something doesn't work properly.

Temperature may not be listed if you don't have module bq27x00_battery installed or enabled. Also kernel-maemo version is not listed if you don't use titan's kernel.

#!/bin/sh

currfreq=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`
idlefreq=`awk '{if ($2 > 0) print $1}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state | tail -n 1`
tis1=`awk '{sum += $2} END {print sum}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`
tis2=`awk '$1 == "'"$idlefreq"'" {idle = $2} {sum += $2} END {print sum-idle}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`

echo -e "
SCRIPT FOR ANALYZING TIME_IN_STATE
By rooted (maemo.org)
Revision 6

The script is in active development.
Update your script to current revision from:
wiki.maemo.org/Overclocking

FREQUENCY\tUSED\t\tWHEN BUSY\n"
awk '
{if ($1 >= 1000000) printf ("%.0f MHz\t",$1/1000); else printf ("%.0f MHz\t\t",$1/1000)}
{if ($2 == 0) printf "unused"; else printf ("%.1f %\t\t",($2*100)/"'"$tis1"'")}
{if ($2 == 0 || $2/"'"$tis2"'" > 1) printf "\n"; else printf ("%.1f %\n",($2*100)/"'"$tis2"'")}
' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

echo -e "
Current frequency: $(($currfreq/1000)) MHz
Idle frequency: $(($idlefreq/1000)) MHz
Kernel: `uname -r`
kernel-maemo: `dpkg -l kernel* | awk '/kernel-maemo/ {print $3}'`
Uptime: `uptime | sed -e 's/.*p *//' -e 's/, l.*//' -e 's/ / /'`
Load: `uptime | sed 's/.*e: //'`
Boot reason: `cat /proc/bootreason`
Temperature: `cat /sys/class/power_supply/bq27200-0/temp` °C\n"

Output example:

SCRIPT FOR ANALYZING TIME_IN_STATE
By rooted (maemo.org)
Revision 6

The script is in active development.
Update your script to current revision from:
wiki.maemo.org/Overclocking

FREQUENCY USED WHEN BUSY

1200 MHz unused
1100 MHz unused
1000 MHz unused
950 MHz unused
900 MHz unused
850 MHz unused
810 MHz 1.6 % 56.7 %
750 MHz 0.0 % 0.8 %
700 MHz 0.1 % 1.9 %
600 MHz 0.0 % 1.5 %
550 MHz 0.0 % 1.2 %
500 MHz 1.0 % 37.8 %
250 MHz 97.3 %
125 MHz unused

Current frequency: 250 MHz
Idle frequency: 250 MHz
Kernel: 2.6.28.10maemo-ulv-omap1
kernel-maemo: 2.6.28-maemo21
Uptime: 2 days, 2:27
Load: 0.11, 0.04, 0.01
Boot reason: pwr_key
Temperature: 25 °C

==Analyzing time in state, including idle mode stats (by ArbitRabbit)==
The following script will show the current frequency and statistics for each state, including time spent in idle mode when the CPU is actually sleeping.
This script works with the special frequency handling in Titan's kernel.

To run this script as user and be able to set the frequencies you will need to install "[[Root_access|rootsh]]" via apt-get.

'''scheduler_stats.sh'''

#!/bin/sh
awk '{print "\nCurrent frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
awk '{print "Minimum frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
awk '{print "Maximum frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

tis1=`awk '{SUM += $2} END {printf("%.0f",SUM/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`

idle0=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state0/time`

idle1=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state1/time`

idle2=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state2/time`

idle3=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state3/time`

totaltime=$(($idle0+$idle1+$idle2+$idle3+$tis1))
echo -e "FREQUENCY\tUSED"
SUM=0
awk '
{
printf (($1/1000)" MHz \t");
if ($2 == 0)
{
printf "0 %\n";
}
else {
SUM+=$2;
printf("%.3f %\n",($2/10)/"'"$totaltime"'");
}
}
END{
printf ("Time spent in idle mode is %2.2f %\n",(1-((SUM/1000)/"'"$totaltime"'"))*100);
}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
echo ""

'''Sample Output'''

Current frequency: 500 MHz

Minimum frequency: 500 MHz

Maximum frequency: 810 MHz

FREQUENCY USED
1200 MHz 0 %
1100 MHz 0 %
1000 MHz 0 %
950 MHz 0 %
900 MHz 0 %
850 MHz 0 %
810 MHz 0.000 %
750 MHz 0.000 %
700 MHz 0.000 %
600 MHz 0.000 %
550 MHz 0.000 %
500 MHz 0.010 %
Time spent in idle mode is 99.99 %

Known Bugs: Requires the Phone to be booted for an hour or so before it results in decent stats.

==Combined helper script (by evilJazz)==

The following script will show the current frequency and statistics. It also accepts two optional parameters that will set the max and/or min frequencies (in MHz unit). Calling the script without these parameters will not set the new clocking. Instead it will just show the current frequencies and statistics.

This script works with the special frequency handling in Titan's kernel.

To run this script as user and be able to set the frequencies you will need to install "[[Root_access|rootsh]]" via apt-get.

overclock.sh [max freq] [min freq]

#!/bin/sh
max=${1}000
min=${2}000

# Handle and rewrite special cases in Titan's kernel...
[ "$max" == "600000" ] && max=599000
[ "$min" == "125000" ] && min=124999

if [ $(id -u) -ne 0 ]; then
[ "$max" != "000" ] && echo "echo $max > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" | sudo gainroot
[ "$min" != "000" ] && echo "echo $min > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq" | sudo gainroot
else
[ "$max" != "000" ] && echo $max > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[ "$min" != "000" ] && echo $min > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
fi

awk '{printf("\nCurrent frequency: %7s MHz\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
awk '{printf("Minimal frequency: %7s MHz\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
awk '{printf("Maximal frequency: %7s MHz\n\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

sum=$(awk '{SUM += $2} END {print SUM}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state)
awk '{printf("%7s MHz: %5.1f % (%8d)\n", ($1/1000), ($2 * 100)/"'"$sum"'", $2)}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
echo

Output example:

~ $ ./overclock.sh 600 250

Current frequency: 250 MHz
Minimal frequency: 250 MHz
Maximal frequency: 599 MHz

1200 MHz: 0.0 % ( 0)
1100 MHz: 0.0 % ( 0)
1000 MHz: 0.0 % ( 0)
950 MHz: 0.0 % ( 0)
900 MHz: 0.2 % ( 271)
850 MHz: 0.0 % ( 0)
810 MHz: 0.0 % ( 0)
750 MHz: 0.0 % ( 0)
700 MHz: 0.0 % ( 0)
600 MHz: 9.0 % ( 13663)
550 MHz: 0.5 % ( 701)
500 MHz: 15.4 % ( 23379)
250 MHz: 75.0 % ( 114021)
124.999 MHz: 0.0 % ( 0)

=Changing the Kernel=

==Installing a modified Kernel==

===Flashing using PC===

1. Power off the N900 completely.

2. Hold "u" on the N900's keyboard, while holding, connect it to the PC via USB cable.

3. You will see usb icon on top right of white Nokia screen.

4. Now you can let go of "u" on the keyboard.

5. Now use flasher utility with the kernel file located in the same directory.

flasher-3.5 -k image_file_name -f -R

6. It should take about 1-2 seconds then it'll say Done.

7. Now your N900 will show white Nokia screen. (reboot)

8. At this time, you can pull out the USB cable.

9. N900 should finish booting up if all goes well.

10. Test out your phone as usual. (Apps, browser, camera, phone etc etc)

11. If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again.
note: For Windows7 64bit users, you may need to use WindowsXP mode. ([http://www.youtube.com/watch?v=Bx6dblXl2eo Youtube Tutorial])

===Flashing from N900 xterminal===

* do a backup, have a pc nearby and know you are able to flash the n900 with flasher-3.5 - just in case

0. Launch xterminal app then type sudo gainroot (need rootsh installed)

1. type
softupd -vv -s --local
(thats double v)

2. open new terminal

3. type
flasher --local -f -k <kernel_zimage_file_with_path>

4. you see the flashing (takes some time)

5. type "sync" to save changes

6. type "reboot" and enter to restart

7. Test out your phone as usual. (Apps, browser, camera, phone etc etc)

8. If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again.

'''You are fully responsible for any damage caused by overclocking. Not anyone else.'''

==Reverting to the Original Kernel==

If you want to revert to the original kernel, execute:

apt-get install --reinstall kernel kernel-flasher

=Voltage tables=

One factor reducing CPU lifetime is the current it is running with.

<code>CPU dynamic power = capacitance * frequency * voltage^2</code> (source?)([http://en.wikipedia.org/wiki/Dynamic_frequency_scaling])

As can be seen from the formula lower voltage plays greater part in CPU consumption than frequency. By reducing the voltage the damage of overclocking can be reduced and the battery life time extended.

==Calculating voltages==

According to [http://talk.maemo.org/showpost.php?p=606031&postcount=2375 this calculations] the voltage can be varied in steps of 0.0125 V with values 0-72. The formula is (with x being the kernel parameter value):

<code>V = x * 0.0125 + 0.6</code>

Examples:

Lowest voltage (x = 0): 0 * 0.0125 + 0.6 = 0 + 0.6 = 0.6 V
Highest voltage (x = 72): 72 * 0.0125 + 0.6 = 0.9 + 0.6 = 1.5 V
Random voltage (x = 38): 38 * 0.0125 + 0.6 = 0.475 + 0.6 = 1.075 V

==Summary==

FREQUENCY Nokia LV ULV XLV ideal
0 MHz 30 30 25 30 30
125 MHz 30 30 25 20 30
250 MHz 38 38 25 30 30
500 MHz 48 48 33 33 30
550 MHz *54* 48 38 38 33
600 MHz 60 *54* 38 38 38
700 MHz 54 45 45 45
750 MHz 54 45 45 45
810 MHz 54 48 48 48
850 MHz 54 48 48 48
900 MHz 54 *54* *54* *54*
950 MHz 54 54 54 54
1000 MHz 60 60 60 60
1100 MHz 72 72 72 72
1150 MHz 72 72 72 72
1200 MHz 72 72 72 72

Note: Asterisks indicate the first frequency in the kernel which needs overvoltage.

==/sys/power/vdd1_opps_vsel values==

LV: "30 30 38 48 48 54 54 54 54 54 54 54 60 72 72"
ULV: "25 25 25 33 38 38 45 45 48 48 54 54 60 72 72"
XLV: "30 20 30 33 38 38 45 45 48 48 54 54 60 72 72"
ideal: "30 30 30 30 33 38 45 45 48 48 54 54 60 72 72"

==Kernels' specifications==

===Nokia's kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
38 1.075V 250 MHz
48 1.200V 500 MHz
54 1.275V 550 MHz
60 1.350V 600 MHz

===titan's LV kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
38 1.075V 250 MHz
48 1.200V 500 MHz
48 1.200V 550 MHz
54 1.275V 600 MHz
54 1.275V 700 MHz
54 1.275V 750 MHz
54 1.275V 810 MHz
54 1.275V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1200 MHz

===titan's ULV kernel===

VALUE VOLTAGE FREQUENCY
25 0.912V 0 MHz
25 0.912V 125 MHz
25 0.912V 250 MHz
33 1.012V 500 MHz
38 1.075V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1200 MHz

===titan's XLV kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
20 0.850V 125 MHz
30 0.975V 250 MHz
33 1.012V 500 MHz
38 1.075V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1150 MHz

===titan's ideal kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
30 0.975V 250 MHz
30 0.975V 500 MHz
33 1.012V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1150 MHz

[[Category:Power users]]

Overclocking

2010-04-20T20:40:35Z

82.95.252.184: /* Battery */

=Overclocking=

This page is about overclocking the N900.
For the N8x0 see [http://talk.maemo.org/showthread.php?t=12464 this]

<nowiki>#</nowiki> ''WORK IN PROGRESS, HELP IF YOU WANT''

Overclocking is discussed in [http://talk.maemo.org/showthread.php?t=39753 this thread].
Benchmark results can be found [http://talk.maemo.org/showthread.php?p=605189 here].
If you're more interested in power saving read [http://talk.maemo.org/showthread.php?t=49654 this].

=Warnings=

- Overclocking WILL VOID YOUR WARRANTY 
- The lifetime of your device will get reduced 
- You could lose the data in your device (file system corruption) 
- Every device is an individual, what is stable for others might not be for you 
- If you encounter ANY unusual problems, lower your clock frequency 
- You do it at your own responsibility. No whining afterwards. If you're unsure, don't do it. 
- [http://depot.javispedro.com/nit/thewarningtm.jpeg Nokia's overclocking warning]: 500MHz is the normal frequency. Everything above is not good for your device, even with the stock kernel. 
- Igor Stoppa's [http://talk.maemo.org/showpost.php?p=596149&postcount=904 warning] and [http://talk.maemo.org/showpost.php?p=603833&postcount=66 comment]
- [http://talk.maemo.org/showpost.php?p=596274&postcount=937 chip vendors specs]

=Available kernels=

Overclocking requires installation of a custom kernel.
There are two types of kernels:
# modified PR1.1 kernels by Lehto and others. The only difference to the stock Nokia kernel is that the change the available hardcoded frequencies.
# enhanced kernels by titan. They are compatible with PR1.2 (!) , contain lots of additional features (IPv6, NAT etc) and bugfixes. In addition they include a large set of possible frequencies (125MHz-1.15GHz) which you manually set an try out without flashing a new kernel. The defaults are set to the standard 250-600MHz range. The kernel can be installed via HAM from the extras-devel catalouge.

== Installation of Lehto's PR1.1 kernels ==

[http://talk.maemo.org/showpost.php?p=594200&postcount=309 Lehto's Kernels]

[http://talk.maemo.org/showpost.php?p=595582&postcount=774 talk.maemo.org: Jakiman's Overclock Guide / Summary]

== Installation of titan's enhanced kernels ==
This kernel makes it possible dynamically change the maximum frequency up to 1.15GHz (supported frequencies are 125,250,500,550,600,700,750,805,850,900,950,1000,1100,1150MHz).
WARNING: Overclocking may damage your device and is at your own risk! It may void your warranty and destroy your data. You have been warned.

[http://talk.maemo.org/showthread.php?t=43420 talk.maemo.org: Discussion of the enhanded kernel]

'''Note:''' all commands on this page must be run as root in X Terminal (install rootsh package and enter "sudo gainroot")

=== Installation of the more stable [https://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/kernel-power-flasher/2.6.28-maemo24/ kernel (maemo24)] from extras-testing ===
With this kernel you can change the frequency limits, the voltages and DSP frequencies online.
It requires firmware PR1.1 or newer.
# Install the package kernel-power-settings (section system in HAM). It will automatically also install kernel-power-flasher.
# shutdown and boot again. There's no need for reflashing etc.
[Configuring_the_kernel_settings read this for configuration]

=== Installation of the experimental [https://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/kernel-power-flasher/2.6.28-maemo25/ kernel (maemo25)] from extras-devel ===
This kernel version contains additional experimental features and patches.
Changelogs are posted [https://garage.maemo.org/news/?group_id=1528 here].
# Install the package "Enhanced kernel for power users" (section system in HAM).
# shutdown and boot again. There's no need for reflashing etc.
Read the instructions for the stable kernel for more information.

=== Upgrade from older versions (< maemo24) ===
The package was previously called kernel-flasher-maemo.
If you have one of the older packages installed it it recommended that you upgrade in X Terminal
sudo gainroot
apt-get install -y kernel-power-flasher
apt-get remove kernel-flasher-maemo
If the new kernel still doesn't boot up, try
apt-get install --reinstall -y kernel-power kernel-power-flasher
Also try [http://talk.maemo.org/showpost.php?p=608343&postcount=2603 other hints] for deinstalling the old package.

Make sure you reset /etc/pmconfig to the defaults:
# Power management configuration file
enable_off_mode 1
sleep_while_idle 1
sr_vdd1_autocomp 0
sr_vdd2_autocomp 0
clocks_off_while_idle 1
voltage_off_while_idle 1
scaling_governor ondemand
scaling_max_freq 600000
scaling_min_freq 125000
sleep_ind 1

=== Deinstallation ===
sudo gainroot
apt-get install --reinstall -y kernel kernel-flasher
apt-get remove kernel-power kernel-power-modules

=== Configuring the kernel settings ===
[http://talk.maemo.org/showpost.php?p=610967&postcount=2718 read this for more details].

First verify, that the kernel is actually running:
uname -r
should return "2.6.28.10power-omap1"
It it does not, you should reboot or try to install again
apt-get install --reinstall -y kernel-power kernel-power-flasher
reboot, and test again.

Make sure the packages ''kernel-power-settings'' and ''rootsh'' are installed.
'''All commands need to be run as root user.'''
If you are normal user in X Terminal either "sudo gainroot" or prepend "sudo" to every command.

1) to try a configuration (you can replace "ideal" with default, lv, ulv, xlv or specify a file you created based on the template /usr/share/kernel-power-settings/default )
/usr/sbin/kernel-load /usr/share/kernel-power-settings/ideal
'''Note''': do [[NOT]] modify the files in /usr/share/kernel-power-settings/!
see '''Creating your own configuration:'' below.

2) to permanently install a default configuration
rm -f /etc/default/kernel-power
ln -s /usr/share/kernel-power-settings/ideal /etc/default/kernel-power
3) or your own config
rm -f /etc/default/kernel-power
cp <filename> /etc/default/kernel-power
4) and to immediately apply it
sudo /usr/sbin/kernel-load

'''For beginners:''' first reboot. then try 1) and check whether the device is stable. then do 2).

'''Creating your own configuration'''
5) copy the template to your mydocs (when not in mass storage mode)
cp /usr/share/kernel-power-settings/ideal /home/user/MyDocs/kernel.txt
6) edit the file ''/home/user/MyDocs/kernel.txt''. The defaults are
#UP_THRESHOLD=75
#SAMPLING_RATE=150000
VDD1_OPPS_VSEL="30 30 38 48 54 48 60 60 60 60 60 60 60 72 72"
DSP_OPPS_RATE="90 90 180 360 400 430 430 430 430 500 500 500 500 520 520"
MIN_FREQ=250000
MAX_FREQ=599000
SMARTREFLEX_VDD1=0
SMARTREFLEX_VDD2=0
For changing the frequency range change MIN_FREQ/MAX_FREQ (see "Temporarly change of the frequency limits" below ).
Either edit the file with an editor on your device (e.g., leafpad)
or USB mount it to edit it on the PC. unmount and unplug USB.
After editing load the configuration with
/usr/sbin/kernel-load /home/user/MyDocs/kernel.txt
and repeat 6) until you're happy.

7) to permanently install this new configuration
rm -f /etc/default/kernel-power
cp /home/user/MyDocs/kernel.txt /etc/default/kernel-power
/usr/sbin/kernel-load

8) to reset the device to the defaults use
rm -f /etc/default/kernel-power
/usr/sbin/kernel-load /usr/share/kernel-power-settings/default

'''Note''': the package automatically detects whether a certain misconfiguration has caused '''reboot loop.'''
It your device reboots twice within 5 minutes, it will load the default settings (250-600Mhz) so that you can fix or remove the invalid configuration file.
This also means that, when for some reason you manually reboot too quickly (<5min) your configuration will not be loaded.
To load it nonetheless run after booting
/usr/sbin/kernel-load

=== Temporarly change of the frequency limits ===
sudo gainroot
echo 250000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 599000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
The last line shows which values were actually set.
To set 125MHz use 124999, for 600MHz 599999, for everthing else x000 with x=MHz.
This setting takes effect immediately and is cleared with the next reboot.

=== Permanently change of the frequency limits ===
WARNING: Permanent overclocking is very dangerous!

Install kernel-power-settings and follow [http://talk.maemo.org/showpost.php?p=610967&postcount=2718 those instructions].

=== Battery ===
In kernels version >=maemo20 you can read out the current battery info:
modprobe bq27x00_battery
cat /sys/class/power_supply/bq27200-0/capacity
cat /sys/class/power_supply/bq27200-0/voltage_now
cat /sys/class/power_supply/bq27200-0/current_now
cat /sys/class/power_supply/bq27200-0/temp

*'capacity' value in percentage of battery level.
*'voltage_now' value in mV of battery voltage level.
*'current_now' value in mA of battery current consumption (???)
*'temp' value in degrees C of battery temperature.

To remove this kernel module use:

modprobe -r bq27x00_battery

=== Holding a kernel version ===
It your manually installed kernel should be not upgraded to the one in extras* try [http://talk.maemo.org/showpost.php?p=603915&postcount=2063 this]:
echo kernel-power-flasher hold | dpkg --set-selections
echo kernel-power hold | dpkg --set-selections
echo kernel-power-modules hold | dpkg --set-selections
to unlock the version:
echo kernel-power-flasher install | dpkg --set-selections
echo kernel-power install | dpkg --set-selections
echo kernel-power-modules install | dpkg --set-selections

=== Remarks ===
# The screen calibration in settings crashes immediately. It is a known bug in the calibration app, not in the kernel. It's mentioned in the kernel package description and is due to additional evdev (joystick,mouse) support. Just calibrate once with the stock kernel before you install the fully featured kernel.
# The kernel supports 125MHz but this frequency is [http://talk.maemo.org/showpost.php?p=617488&postcount=3095 disabled by default]. In version <25, it is enabled by specifying "124999", in later versions it is set in ''/sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies'' and can be enabled with
echo > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
# similarily, individual frequencies can be disabled in >=v25
echo 125000 250000 750000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
# even if 125Mhz is disabled, the telephone app will always try to set the minimum freq. to 125Mhz after a phone call, but it is ignored unless you enable 125Mhz.
# if you enable 125MHz also set "echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load" [http://talk.maemo.org/showpost.php?p=602687&postcount=185 hint]

# [http://talk.maemo.org/showpost.php?p=597703&postcount=141 the 125MHz issue]
# Installing another version of the enhanced kernel will just overwrite the older version. The stock kernel modules are preserved so that you can simply reflash the stock kernel via USB.
# If you for some reason get errors like this during removal or installation "rm: cannot remove '/lib/modules/2.6.28.10maemo-lv-omap1/modules.*': No such file or directory".try this [http://talk.maemo.org/showpost.php?p=603938&postcount=196 workaround]. There was a bug in one of the early LV kernels but it should be fixed in more recent versions.
# This kernel will not conflict with the future PR1.2 upgrade. The upgrade will, however, overwrite this kernel and you'll have to install it again.

=Additional information and hints=

# the frequencies available in the Nokia kernel are: 250, 500, 550 and 600MHz.
# Nokia [http://talk.maemo.org/showpost.php?p=601691&postcount=1823 locks the device to 600MHz] during phone calls. This may be a bug. It also [http://talk.maemo.org/showpost.php?p=600721&postcount=1720 affects] Lehto's kernels.
# the telephone app is closed-source and broken. After a phone call it sets the maximum to 600Mhz and the minimum to 250MHz (or 125MHz if available) irrespective of what you have set before.
# when connected via USB the device locks the minimum frequency to 500Mhz.
# By default the device is configured to use 125MHz as the lowest frequency but it not enabled in the kernel [https://bugs.maemo.org/show_bug.cgi?id=7116 pmconfig bug]
# [http://talk.maemo.org/showpost.php?p=599870&postcount=170 improving responsiveness]
# [http://talk.maemo.org/showpost.php?p=599618&postcount=168 safe pmconfig configuration]
# the warning "WARNING: at arch/arm/mach-omap2/clock34xx.c:443 omap3_noncore_dpll_set_rate+0x28c/0x2dc()" in the kernel logs (dmesg) only happens if the invalid 800MHz frequency was selected. ignore it.
# [http://talk.maemo.org/showpost.php?p=603585&postcount=189 saving more battery power when idle]
# EvilJazz had photoshopped a [http://talk.maemo.org/showpost.php?p=605523&postcount=90 picture of a device being overclocked 1.7GHz]. It's a JOKE!
# reading one of the temperature sensors "cat /sys/devices/platform/omap34xx_temp/temp1_input"

=Useful stuff=

==Show current CPU frequency==

awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

==Set maximum CPU frequency==

From root terminal:

rootsh echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq | echo ""

Replace 600000 with desired maximum frequency. Pay attention to the two exceptions in titan's kernels (124999 and 599000). The list of available frequencies on your device/kernel can be obtained with command:

awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

==Script for analyzing time_in_state (by rooted) - rev6==

This script prints percentage of frequencies (states) used and some additional info useful for posting on the forum (debugging). It displays all frequencies, works with all kernels and it is not affected by the bug which resets minimum frequency after phone call.

The script is in active development. I'm adding new features and resolving bugs if they are reported. Please update your script to newest revision and report if something doesn't work properly.

Temperature may not be listed if you don't have module bq27x00_battery installed or enabled. Also kernel-maemo version is not listed if you don't use titan's kernel.

#!/bin/sh

currfreq=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`
idlefreq=`awk '{if ($2 > 0) print $1}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state | tail -n 1`
tis1=`awk '{sum += $2} END {print sum}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`
tis2=`awk '$1 == "'"$idlefreq"'" {idle = $2} {sum += $2} END {print sum-idle}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`

echo -e "
SCRIPT FOR ANALYZING TIME_IN_STATE
By rooted (maemo.org)
Revision 6

The script is in active development.
Update your script to current revision from:
wiki.maemo.org/Overclocking

FREQUENCY\tUSED\t\tWHEN BUSY\n"
awk '
{if ($1 >= 1000000) printf ("%.0f MHz\t",$1/1000); else printf ("%.0f MHz\t\t",$1/1000)}
{if ($2 == 0) printf "unused"; else printf ("%.1f %\t\t",($2*100)/"'"$tis1"'")}
{if ($2 == 0 || $2/"'"$tis2"'" > 1) printf "\n"; else printf ("%.1f %\n",($2*100)/"'"$tis2"'")}
' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

echo -e "
Current frequency: $(($currfreq/1000)) MHz
Idle frequency: $(($idlefreq/1000)) MHz
Kernel: `uname -r`
kernel-maemo: `dpkg -l kernel* | awk '/kernel-maemo/ {print $3}'`
Uptime: `uptime | sed -e 's/.*p *//' -e 's/, l.*//' -e 's/ / /'`
Load: `uptime | sed 's/.*e: //'`
Boot reason: `cat /proc/bootreason`
Temperature: `cat /sys/class/power_supply/bq27200-0/temp` °C\n"

Output example:

SCRIPT FOR ANALYZING TIME_IN_STATE
By rooted (maemo.org)
Revision 6

The script is in active development.
Update your script to current revision from:
wiki.maemo.org/Overclocking

FREQUENCY USED WHEN BUSY

1200 MHz unused
1100 MHz unused
1000 MHz unused
950 MHz unused
900 MHz unused
850 MHz unused
810 MHz 1.6 % 56.7 %
750 MHz 0.0 % 0.8 %
700 MHz 0.1 % 1.9 %
600 MHz 0.0 % 1.5 %
550 MHz 0.0 % 1.2 %
500 MHz 1.0 % 37.8 %
250 MHz 97.3 %
125 MHz unused

Current frequency: 250 MHz
Idle frequency: 250 MHz
Kernel: 2.6.28.10maemo-ulv-omap1
kernel-maemo: 2.6.28-maemo21
Uptime: 2 days, 2:27
Load: 0.11, 0.04, 0.01
Boot reason: pwr_key
Temperature: 25 °C

==Analyzing time in state, including idle mode stats (by ArbitRabbit)==
The following script will show the current frequency and statistics for each state, including time spent in idle mode when the CPU is actually sleeping.
This script works with the special frequency handling in Titan's kernel.

To run this script as user and be able to set the frequencies you will need to install "[[Root_access|rootsh]]" via apt-get.

'''scheduler_stats.sh'''

#!/bin/sh
awk '{print "\nCurrent frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
awk '{print "Minimum frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
awk '{print "Maximum frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

tis1=`awk '{SUM += $2} END {printf("%.0f",SUM/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`

idle0=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state0/time`

idle1=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state1/time`

idle2=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state2/time`

idle3=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state3/time`

totaltime=$(($idle0+$idle1+$idle2+$idle3+$tis1))
echo -e "FREQUENCY\tUSED"
SUM=0
awk '
{
printf (($1/1000)" MHz \t");
if ($2 == 0)
{
printf "0 %\n";
}
else {
SUM+=$2;
printf("%.3f %\n",($2/10)/"'"$totaltime"'");
}
}
END{
printf ("Time spent in idle mode is %2.2f %\n",(1-((SUM/1000)/"'"$totaltime"'"))*100);
}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
echo ""

'''Sample Output'''

Current frequency: 500 MHz

Minimum frequency: 500 MHz

Maximum frequency: 810 MHz

FREQUENCY USED
1200 MHz 0 %
1100 MHz 0 %
1000 MHz 0 %
950 MHz 0 %
900 MHz 0 %
850 MHz 0 %
810 MHz 0.000 %
750 MHz 0.000 %
700 MHz 0.000 %
600 MHz 0.000 %
550 MHz 0.000 %
500 MHz 0.010 %
Time spent in idle mode is 99.99 %

Known Bugs: Requires the Phone to be booted for an hour or so before it results in decent stats.

==Combined helper script (by evilJazz)==

The following script will show the current frequency and statistics. It also accepts two optional parameters that will set the max and/or min frequencies (in MHz unit). Calling the script without these parameters will not set the new clocking. Instead it will just show the current frequencies and statistics.

This script works with the special frequency handling in Titan's kernel.

To run this script as user and be able to set the frequencies you will need to install "[[Root_access|rootsh]]" via apt-get.

overclock.sh [max freq] [min freq]

#!/bin/sh
max=${1}000
min=${2}000

# Handle and rewrite special cases in Titan's kernel...
[ "$max" == "600000" ] && max=599000
[ "$min" == "125000" ] && min=124999

if [ $(id -u) -ne 0 ]; then
[ "$max" != "000" ] && echo "echo $max > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" | sudo gainroot
[ "$min" != "000" ] && echo "echo $min > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq" | sudo gainroot
else
[ "$max" != "000" ] && echo $max > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[ "$min" != "000" ] && echo $min > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
fi

awk '{printf("\nCurrent frequency: %7s MHz\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
awk '{printf("Minimal frequency: %7s MHz\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
awk '{printf("Maximal frequency: %7s MHz\n\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

sum=$(awk '{SUM += $2} END {print SUM}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state)
awk '{printf("%7s MHz: %5.1f % (%8d)\n", ($1/1000), ($2 * 100)/"'"$sum"'", $2)}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
echo

Output example:

~ $ ./overclock.sh 600 250

Current frequency: 250 MHz
Minimal frequency: 250 MHz
Maximal frequency: 599 MHz

1200 MHz: 0.0 % ( 0)
1100 MHz: 0.0 % ( 0)
1000 MHz: 0.0 % ( 0)
950 MHz: 0.0 % ( 0)
900 MHz: 0.2 % ( 271)
850 MHz: 0.0 % ( 0)
810 MHz: 0.0 % ( 0)
750 MHz: 0.0 % ( 0)
700 MHz: 0.0 % ( 0)
600 MHz: 9.0 % ( 13663)
550 MHz: 0.5 % ( 701)
500 MHz: 15.4 % ( 23379)
250 MHz: 75.0 % ( 114021)
124.999 MHz: 0.0 % ( 0)

=Changing the Kernel=

==Installing a modified Kernel==

===Flashing using PC===

1. Power off the N900 completely.

2. Hold "u" on the N900's keyboard, while holding, connect it to the PC via USB cable.

3. You will see usb icon on top right of white Nokia screen.

4. Now you can let go of "u" on the keyboard.

5. Now use flasher utility with the kernel file located in the same directory.

flasher-3.5 -k image_file_name -f -R

6. It should take about 1-2 seconds then it'll say Done.

7. Now your N900 will show white Nokia screen. (reboot)

8. At this time, you can pull out the USB cable.

9. N900 should finish booting up if all goes well.

10. Test out your phone as usual. (Apps, browser, camera, phone etc etc)

11. If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again.
note: For Windows7 64bit users, you may need to use WindowsXP mode. ([http://www.youtube.com/watch?v=Bx6dblXl2eo Youtube Tutorial])

===Flashing from N900 xterminal===

* do a backup, have a pc nearby and know you are able to flash the n900 with flasher-3.5 - just in case

0. Launch xterminal app then type sudo gainroot (need rootsh installed)

1. type
softupd -vv -s --local
(thats double v)

2. open new terminal

3. type
flasher --local -f -k <kernel_zimage_file_with_path>

4. you see the flashing (takes some time)

5. type "sync" to save changes

6. type "reboot" and enter to restart

7. Test out your phone as usual. (Apps, browser, camera, phone etc etc)

8. If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again.

'''You are fully responsible for any damage caused by overclocking. Not anyone else.'''

==Reverting to the Original Kernel==

If you want to revert to the original kernel, execute:

apt-get install --reinstall kernel kernel-flasher

=Voltage tables=

One factor reducing CPU lifetime is the current it is running with.

<code>CPU dynamic power = capacitance * frequency * voltage^2</code> (source?)([http://en.wikipedia.org/wiki/Dynamic_frequency_scaling])

As can be seen from the formula lower voltage plays greater part in CPU consumption than frequency. By reducing the voltage the damage of overclocking can be reduced and the battery life time extended.

==Calculating voltages==

According to [http://talk.maemo.org/showpost.php?p=606031&postcount=2375 this calculations] the voltage can be varied in steps of 0.0125 V with values 0-72. The formula is (with x being the kernel parameter value):

<code>V = x * 0.0125 + 0.6</code>

Examples:

Lowest voltage (x = 0): 0 * 0.0125 + 0.6 = 0 + 0.6 = 0.6 V
Highest voltage (x = 72): 72 * 0.0125 + 0.6 = 0.9 + 0.6 = 1.5 V
Random voltage (x = 38): 38 * 0.0125 + 0.6 = 0.475 + 0.6 = 1.075 V

==Summary==

FREQUENCY Nokia LV ULV XLV ideal
0 MHz 30 30 25 30 30
125 MHz 30 30 25 20 30
250 MHz 38 38 25 30 30
500 MHz 48 48 33 33 30
550 MHz *54* 48 38 38 33
600 MHz 60 *54* 38 38 38
700 MHz 54 45 45 45
750 MHz 54 45 45 45
810 MHz 54 48 48 48
850 MHz 54 48 48 48
900 MHz 54 *54* *54* *54*
950 MHz 54 54 54 54
1000 MHz 60 60 60 60
1100 MHz 72 72 72 72
1150 MHz 72 72 72 72
1200 MHz 72 72 72 72

Note: Asterisks indicate the first frequency in the kernel which needs overvoltage.

==/sys/power/vdd1_opps_vsel values==

LV: "30 30 38 48 48 54 54 54 54 54 54 54 60 72 72"
ULV: "25 25 25 33 38 38 45 45 48 48 54 54 60 72 72"
XLV: "30 20 30 33 38 38 45 45 48 48 54 54 60 72 72"
ideal: "30 30 30 30 33 38 45 45 48 48 54 54 60 72 72"

==Kernels' specifications==

===Nokia's kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
38 1.075V 250 MHz
48 1.200V 500 MHz
54 1.275V 550 MHz
60 1.350V 600 MHz

===titan's LV kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
38 1.075V 250 MHz
48 1.200V 500 MHz
48 1.200V 550 MHz
54 1.275V 600 MHz
54 1.275V 700 MHz
54 1.275V 750 MHz
54 1.275V 810 MHz
54 1.275V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1200 MHz

===titan's ULV kernel===

VALUE VOLTAGE FREQUENCY
25 0.912V 0 MHz
25 0.912V 125 MHz
25 0.912V 250 MHz
33 1.012V 500 MHz
38 1.075V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1200 MHz

===titan's XLV kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
20 0.850V 125 MHz
30 0.975V 250 MHz
33 1.012V 500 MHz
38 1.075V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1150 MHz

===titan's ideal kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
30 0.975V 250 MHz
30 0.975V 500 MHz
33 1.012V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1150 MHz

[[Category:Power users]]

Overclocking

2010-04-20T20:34:56Z

82.95.252.184: /* Battery */

=Overclocking=

This page is about overclocking the N900.
For the N8x0 see [http://talk.maemo.org/showthread.php?t=12464 this]

<nowiki>#</nowiki> ''WORK IN PROGRESS, HELP IF YOU WANT''

Overclocking is discussed in [http://talk.maemo.org/showthread.php?t=39753 this thread].
Benchmark results can be found [http://talk.maemo.org/showthread.php?p=605189 here].
If you're more interested in power saving read [http://talk.maemo.org/showthread.php?t=49654 this].

=Warnings=

- Overclocking WILL VOID YOUR WARRANTY 
- The lifetime of your device will get reduced 
- You could lose the data in your device (file system corruption) 
- Every device is an individual, what is stable for others might not be for you 
- If you encounter ANY unusual problems, lower your clock frequency 
- You do it at your own responsibility. No whining afterwards. If you're unsure, don't do it. 
- [http://depot.javispedro.com/nit/thewarningtm.jpeg Nokia's overclocking warning]: 500MHz is the normal frequency. Everything above is not good for your device, even with the stock kernel. 
- Igor Stoppa's [http://talk.maemo.org/showpost.php?p=596149&postcount=904 warning] and [http://talk.maemo.org/showpost.php?p=603833&postcount=66 comment]
- [http://talk.maemo.org/showpost.php?p=596274&postcount=937 chip vendors specs]

=Available kernels=

Overclocking requires installation of a custom kernel.
There are two types of kernels:
# modified PR1.1 kernels by Lehto and others. The only difference to the stock Nokia kernel is that the change the available hardcoded frequencies.
# enhanced kernels by titan. They are compatible with PR1.2 (!) , contain lots of additional features (IPv6, NAT etc) and bugfixes. In addition they include a large set of possible frequencies (125MHz-1.15GHz) which you manually set an try out without flashing a new kernel. The defaults are set to the standard 250-600MHz range. The kernel can be installed via HAM from the extras-devel catalouge.

== Installation of Lehto's PR1.1 kernels ==

[http://talk.maemo.org/showpost.php?p=594200&postcount=309 Lehto's Kernels]

[http://talk.maemo.org/showpost.php?p=595582&postcount=774 talk.maemo.org: Jakiman's Overclock Guide / Summary]

== Installation of titan's enhanced kernels ==
This kernel makes it possible dynamically change the maximum frequency up to 1.15GHz (supported frequencies are 125,250,500,550,600,700,750,805,850,900,950,1000,1100,1150MHz).
WARNING: Overclocking may damage your device and is at your own risk! It may void your warranty and destroy your data. You have been warned.

[http://talk.maemo.org/showthread.php?t=43420 talk.maemo.org: Discussion of the enhanded kernel]

'''Note:''' all commands on this page must be run as root in X Terminal (install rootsh package and enter "sudo gainroot")

=== Installation of the more stable [https://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/kernel-power-flasher/2.6.28-maemo24/ kernel (maemo24)] from extras-testing ===
With this kernel you can change the frequency limits, the voltages and DSP frequencies online.
It requires firmware PR1.1 or newer.
# Install the package kernel-power-settings (section system in HAM). It will automatically also install kernel-power-flasher.
# shutdown and boot again. There's no need for reflashing etc.
[Configuring_the_kernel_settings read this for configuration]

=== Installation of the experimental [https://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/kernel-power-flasher/2.6.28-maemo25/ kernel (maemo25)] from extras-devel ===
This kernel version contains additional experimental features and patches.
Changelogs are posted [https://garage.maemo.org/news/?group_id=1528 here].
# Install the package "Enhanced kernel for power users" (section system in HAM).
# shutdown and boot again. There's no need for reflashing etc.
Read the instructions for the stable kernel for more information.

=== Upgrade from older versions (< maemo24) ===
The package was previously called kernel-flasher-maemo.
If you have one of the older packages installed it it recommended that you upgrade in X Terminal
sudo gainroot
apt-get install -y kernel-power-flasher
apt-get remove kernel-flasher-maemo
If the new kernel still doesn't boot up, try
apt-get install --reinstall -y kernel-power kernel-power-flasher
Also try [http://talk.maemo.org/showpost.php?p=608343&postcount=2603 other hints] for deinstalling the old package.

Make sure you reset /etc/pmconfig to the defaults:
# Power management configuration file
enable_off_mode 1
sleep_while_idle 1
sr_vdd1_autocomp 0
sr_vdd2_autocomp 0
clocks_off_while_idle 1
voltage_off_while_idle 1
scaling_governor ondemand
scaling_max_freq 600000
scaling_min_freq 125000
sleep_ind 1

=== Deinstallation ===
sudo gainroot
apt-get install --reinstall -y kernel kernel-flasher
apt-get remove kernel-power kernel-power-modules

=== Configuring the kernel settings ===
[http://talk.maemo.org/showpost.php?p=610967&postcount=2718 read this for more details].

First verify, that the kernel is actually running:
uname -r
should return "2.6.28.10power-omap1"
It it does not, you should reboot or try to install again
apt-get install --reinstall -y kernel-power kernel-power-flasher
reboot, and test again.

Make sure the packages ''kernel-power-settings'' and ''rootsh'' are installed.
'''All commands need to be run as root user.'''
If you are normal user in X Terminal either "sudo gainroot" or prepend "sudo" to every command.

1) to try a configuration (you can replace "ideal" with default, lv, ulv, xlv or specify a file you created based on the template /usr/share/kernel-power-settings/default )
/usr/sbin/kernel-load /usr/share/kernel-power-settings/ideal
'''Note''': do [[NOT]] modify the files in /usr/share/kernel-power-settings/!
see '''Creating your own configuration:'' below.

2) to permanently install a default configuration
rm -f /etc/default/kernel-power
ln -s /usr/share/kernel-power-settings/ideal /etc/default/kernel-power
3) or your own config
rm -f /etc/default/kernel-power
cp <filename> /etc/default/kernel-power
4) and to immediately apply it
sudo /usr/sbin/kernel-load

'''For beginners:''' first reboot. then try 1) and check whether the device is stable. then do 2).

'''Creating your own configuration'''
5) copy the template to your mydocs (when not in mass storage mode)
cp /usr/share/kernel-power-settings/ideal /home/user/MyDocs/kernel.txt
6) edit the file ''/home/user/MyDocs/kernel.txt''. The defaults are
#UP_THRESHOLD=75
#SAMPLING_RATE=150000
VDD1_OPPS_VSEL="30 30 38 48 54 48 60 60 60 60 60 60 60 72 72"
DSP_OPPS_RATE="90 90 180 360 400 430 430 430 430 500 500 500 500 520 520"
MIN_FREQ=250000
MAX_FREQ=599000
SMARTREFLEX_VDD1=0
SMARTREFLEX_VDD2=0
For changing the frequency range change MIN_FREQ/MAX_FREQ (see "Temporarly change of the frequency limits" below ).
Either edit the file with an editor on your device (e.g., leafpad)
or USB mount it to edit it on the PC. unmount and unplug USB.
After editing load the configuration with
/usr/sbin/kernel-load /home/user/MyDocs/kernel.txt
and repeat 6) until you're happy.

7) to permanently install this new configuration
rm -f /etc/default/kernel-power
cp /home/user/MyDocs/kernel.txt /etc/default/kernel-power
/usr/sbin/kernel-load

8) to reset the device to the defaults use
rm -f /etc/default/kernel-power
/usr/sbin/kernel-load /usr/share/kernel-power-settings/default

'''Note''': the package automatically detects whether a certain misconfiguration has caused '''reboot loop.'''
It your device reboots twice within 5 minutes, it will load the default settings (250-600Mhz) so that you can fix or remove the invalid configuration file.
This also means that, when for some reason you manually reboot too quickly (<5min) your configuration will not be loaded.
To load it nonetheless run after booting
/usr/sbin/kernel-load

=== Temporarly change of the frequency limits ===
sudo gainroot
echo 250000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 599000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
The last line shows which values were actually set.
To set 125MHz use 124999, for 600MHz 599999, for everthing else x000 with x=MHz.
This setting takes effect immediately and is cleared with the next reboot.

=== Permanently change of the frequency limits ===
WARNING: Permanent overclocking is very dangerous!

Install kernel-power-settings and follow [http://talk.maemo.org/showpost.php?p=610967&postcount=2718 those instructions].

=== Battery ===
In kernels version >=maemo20 you can read out the current battery info:
modprobe bq27x00_battery
cat /sys/class/power_supply/bq27200-0/capacity
cat /sys/class/power_supply/bq27200-0/voltage_now
cat /sys/class/power_supply/bq27200-0/current_now
cat /sys/class/power_supply/bq27200-0/temp

*'capacity' value in percentage of battery level.
*'voltage_now' value in mV of battery voltage level.
*'current_now' value in mA of battery current consumption (???)
*'temp' value in degrees C of battery temperature.

=== Holding a kernel version ===
It your manually installed kernel should be not upgraded to the one in extras* try [http://talk.maemo.org/showpost.php?p=603915&postcount=2063 this]:
echo kernel-power-flasher hold | dpkg --set-selections
echo kernel-power hold | dpkg --set-selections
echo kernel-power-modules hold | dpkg --set-selections
to unlock the version:
echo kernel-power-flasher install | dpkg --set-selections
echo kernel-power install | dpkg --set-selections
echo kernel-power-modules install | dpkg --set-selections

=== Remarks ===
# The screen calibration in settings crashes immediately. It is a known bug in the calibration app, not in the kernel. It's mentioned in the kernel package description and is due to additional evdev (joystick,mouse) support. Just calibrate once with the stock kernel before you install the fully featured kernel.
# The kernel supports 125MHz but this frequency is [http://talk.maemo.org/showpost.php?p=617488&postcount=3095 disabled by default]. In version <25, it is enabled by specifying "124999", in later versions it is set in ''/sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies'' and can be enabled with
echo > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
# similarily, individual frequencies can be disabled in >=v25
echo 125000 250000 750000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
# even if 125Mhz is disabled, the telephone app will always try to set the minimum freq. to 125Mhz after a phone call, but it is ignored unless you enable 125Mhz.
# if you enable 125MHz also set "echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load" [http://talk.maemo.org/showpost.php?p=602687&postcount=185 hint]

# [http://talk.maemo.org/showpost.php?p=597703&postcount=141 the 125MHz issue]
# Installing another version of the enhanced kernel will just overwrite the older version. The stock kernel modules are preserved so that you can simply reflash the stock kernel via USB.
# If you for some reason get errors like this during removal or installation "rm: cannot remove '/lib/modules/2.6.28.10maemo-lv-omap1/modules.*': No such file or directory".try this [http://talk.maemo.org/showpost.php?p=603938&postcount=196 workaround]. There was a bug in one of the early LV kernels but it should be fixed in more recent versions.
# This kernel will not conflict with the future PR1.2 upgrade. The upgrade will, however, overwrite this kernel and you'll have to install it again.

=Additional information and hints=

# the frequencies available in the Nokia kernel are: 250, 500, 550 and 600MHz.
# Nokia [http://talk.maemo.org/showpost.php?p=601691&postcount=1823 locks the device to 600MHz] during phone calls. This may be a bug. It also [http://talk.maemo.org/showpost.php?p=600721&postcount=1720 affects] Lehto's kernels.
# the telephone app is closed-source and broken. After a phone call it sets the maximum to 600Mhz and the minimum to 250MHz (or 125MHz if available) irrespective of what you have set before.
# when connected via USB the device locks the minimum frequency to 500Mhz.
# By default the device is configured to use 125MHz as the lowest frequency but it not enabled in the kernel [https://bugs.maemo.org/show_bug.cgi?id=7116 pmconfig bug]
# [http://talk.maemo.org/showpost.php?p=599870&postcount=170 improving responsiveness]
# [http://talk.maemo.org/showpost.php?p=599618&postcount=168 safe pmconfig configuration]
# the warning "WARNING: at arch/arm/mach-omap2/clock34xx.c:443 omap3_noncore_dpll_set_rate+0x28c/0x2dc()" in the kernel logs (dmesg) only happens if the invalid 800MHz frequency was selected. ignore it.
# [http://talk.maemo.org/showpost.php?p=603585&postcount=189 saving more battery power when idle]
# EvilJazz had photoshopped a [http://talk.maemo.org/showpost.php?p=605523&postcount=90 picture of a device being overclocked 1.7GHz]. It's a JOKE!
# reading one of the temperature sensors "cat /sys/devices/platform/omap34xx_temp/temp1_input"

=Useful stuff=

==Show current CPU frequency==

awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

==Set maximum CPU frequency==

From root terminal:

rootsh echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq | echo ""

Replace 600000 with desired maximum frequency. Pay attention to the two exceptions in titan's kernels (124999 and 599000). The list of available frequencies on your device/kernel can be obtained with command:

awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

==Script for analyzing time_in_state (by rooted) - rev6==

This script prints percentage of frequencies (states) used and some additional info useful for posting on the forum (debugging). It displays all frequencies, works with all kernels and it is not affected by the bug which resets minimum frequency after phone call.

The script is in active development. I'm adding new features and resolving bugs if they are reported. Please update your script to newest revision and report if something doesn't work properly.

Temperature may not be listed if you don't have module bq27x00_battery installed or enabled. Also kernel-maemo version is not listed if you don't use titan's kernel.

#!/bin/sh

currfreq=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`
idlefreq=`awk '{if ($2 > 0) print $1}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state | tail -n 1`
tis1=`awk '{sum += $2} END {print sum}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`
tis2=`awk '$1 == "'"$idlefreq"'" {idle = $2} {sum += $2} END {print sum-idle}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`

echo -e "
SCRIPT FOR ANALYZING TIME_IN_STATE
By rooted (maemo.org)
Revision 6

The script is in active development.
Update your script to current revision from:
wiki.maemo.org/Overclocking

FREQUENCY\tUSED\t\tWHEN BUSY\n"
awk '
{if ($1 >= 1000000) printf ("%.0f MHz\t",$1/1000); else printf ("%.0f MHz\t\t",$1/1000)}
{if ($2 == 0) printf "unused"; else printf ("%.1f %\t\t",($2*100)/"'"$tis1"'")}
{if ($2 == 0 || $2/"'"$tis2"'" > 1) printf "\n"; else printf ("%.1f %\n",($2*100)/"'"$tis2"'")}
' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

echo -e "
Current frequency: $(($currfreq/1000)) MHz
Idle frequency: $(($idlefreq/1000)) MHz
Kernel: `uname -r`
kernel-maemo: `dpkg -l kernel* | awk '/kernel-maemo/ {print $3}'`
Uptime: `uptime | sed -e 's/.*p *//' -e 's/, l.*//' -e 's/ / /'`
Load: `uptime | sed 's/.*e: //'`
Boot reason: `cat /proc/bootreason`
Temperature: `cat /sys/class/power_supply/bq27200-0/temp` °C\n"

Output example:

SCRIPT FOR ANALYZING TIME_IN_STATE
By rooted (maemo.org)
Revision 6

The script is in active development.
Update your script to current revision from:
wiki.maemo.org/Overclocking

FREQUENCY USED WHEN BUSY

1200 MHz unused
1100 MHz unused
1000 MHz unused
950 MHz unused
900 MHz unused
850 MHz unused
810 MHz 1.6 % 56.7 %
750 MHz 0.0 % 0.8 %
700 MHz 0.1 % 1.9 %
600 MHz 0.0 % 1.5 %
550 MHz 0.0 % 1.2 %
500 MHz 1.0 % 37.8 %
250 MHz 97.3 %
125 MHz unused

Current frequency: 250 MHz
Idle frequency: 250 MHz
Kernel: 2.6.28.10maemo-ulv-omap1
kernel-maemo: 2.6.28-maemo21
Uptime: 2 days, 2:27
Load: 0.11, 0.04, 0.01
Boot reason: pwr_key
Temperature: 25 °C

==Analyzing time in state, including idle mode stats (by ArbitRabbit)==
The following script will show the current frequency and statistics for each state, including time spent in idle mode when the CPU is actually sleeping.
This script works with the special frequency handling in Titan's kernel.

To run this script as user and be able to set the frequencies you will need to install "[[Root_access|rootsh]]" via apt-get.

'''scheduler_stats.sh'''

#!/bin/sh
awk '{print "\nCurrent frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
awk '{print "Minimum frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
awk '{print "Maximum frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

tis1=`awk '{SUM += $2} END {printf("%.0f",SUM/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`

idle0=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state0/time`

idle1=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state1/time`

idle2=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state2/time`

idle3=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state3/time`

totaltime=$(($idle0+$idle1+$idle2+$idle3+$tis1))
echo -e "FREQUENCY\tUSED"
SUM=0
awk '
{
printf (($1/1000)" MHz \t");
if ($2 == 0)
{
printf "0 %\n";
}
else {
SUM+=$2;
printf("%.3f %\n",($2/10)/"'"$totaltime"'");
}
}
END{
printf ("Time spent in idle mode is %2.2f %\n",(1-((SUM/1000)/"'"$totaltime"'"))*100);
}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
echo ""

'''Sample Output'''

Current frequency: 500 MHz

Minimum frequency: 500 MHz

Maximum frequency: 810 MHz

FREQUENCY USED
1200 MHz 0 %
1100 MHz 0 %
1000 MHz 0 %
950 MHz 0 %
900 MHz 0 %
850 MHz 0 %
810 MHz 0.000 %
750 MHz 0.000 %
700 MHz 0.000 %
600 MHz 0.000 %
550 MHz 0.000 %
500 MHz 0.010 %
Time spent in idle mode is 99.99 %

Known Bugs: Requires the Phone to be booted for an hour or so before it results in decent stats.

==Combined helper script (by evilJazz)==

The following script will show the current frequency and statistics. It also accepts two optional parameters that will set the max and/or min frequencies (in MHz unit). Calling the script without these parameters will not set the new clocking. Instead it will just show the current frequencies and statistics.

This script works with the special frequency handling in Titan's kernel.

To run this script as user and be able to set the frequencies you will need to install "[[Root_access|rootsh]]" via apt-get.

overclock.sh [max freq] [min freq]

#!/bin/sh
max=${1}000
min=${2}000

# Handle and rewrite special cases in Titan's kernel...
[ "$max" == "600000" ] && max=599000
[ "$min" == "125000" ] && min=124999

if [ $(id -u) -ne 0 ]; then
[ "$max" != "000" ] && echo "echo $max > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" | sudo gainroot
[ "$min" != "000" ] && echo "echo $min > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq" | sudo gainroot
else
[ "$max" != "000" ] && echo $max > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[ "$min" != "000" ] && echo $min > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
fi

awk '{printf("\nCurrent frequency: %7s MHz\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
awk '{printf("Minimal frequency: %7s MHz\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
awk '{printf("Maximal frequency: %7s MHz\n\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

sum=$(awk '{SUM += $2} END {print SUM}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state)
awk '{printf("%7s MHz: %5.1f % (%8d)\n", ($1/1000), ($2 * 100)/"'"$sum"'", $2)}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
echo

Output example:

~ $ ./overclock.sh 600 250

Current frequency: 250 MHz
Minimal frequency: 250 MHz
Maximal frequency: 599 MHz

1200 MHz: 0.0 % ( 0)
1100 MHz: 0.0 % ( 0)
1000 MHz: 0.0 % ( 0)
950 MHz: 0.0 % ( 0)
900 MHz: 0.2 % ( 271)
850 MHz: 0.0 % ( 0)
810 MHz: 0.0 % ( 0)
750 MHz: 0.0 % ( 0)
700 MHz: 0.0 % ( 0)
600 MHz: 9.0 % ( 13663)
550 MHz: 0.5 % ( 701)
500 MHz: 15.4 % ( 23379)
250 MHz: 75.0 % ( 114021)
124.999 MHz: 0.0 % ( 0)

=Changing the Kernel=

==Installing a modified Kernel==

===Flashing using PC===

1. Power off the N900 completely.

2. Hold "u" on the N900's keyboard, while holding, connect it to the PC via USB cable.

3. You will see usb icon on top right of white Nokia screen.

4. Now you can let go of "u" on the keyboard.

5. Now use flasher utility with the kernel file located in the same directory.

flasher-3.5 -k image_file_name -f -R

6. It should take about 1-2 seconds then it'll say Done.

7. Now your N900 will show white Nokia screen. (reboot)

8. At this time, you can pull out the USB cable.

9. N900 should finish booting up if all goes well.

10. Test out your phone as usual. (Apps, browser, camera, phone etc etc)

11. If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again.
note: For Windows7 64bit users, you may need to use WindowsXP mode. ([http://www.youtube.com/watch?v=Bx6dblXl2eo Youtube Tutorial])

===Flashing from N900 xterminal===

* do a backup, have a pc nearby and know you are able to flash the n900 with flasher-3.5 - just in case

0. Launch xterminal app then type sudo gainroot (need rootsh installed)

1. type
softupd -vv -s --local
(thats double v)

2. open new terminal

3. type
flasher --local -f -k <kernel_zimage_file_with_path>

4. you see the flashing (takes some time)

5. type "sync" to save changes

6. type "reboot" and enter to restart

7. Test out your phone as usual. (Apps, browser, camera, phone etc etc)

8. If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again.

'''You are fully responsible for any damage caused by overclocking. Not anyone else.'''

==Reverting to the Original Kernel==

If you want to revert to the original kernel, execute:

apt-get install --reinstall kernel kernel-flasher

=Voltage tables=

One factor reducing CPU lifetime is the current it is running with.

<code>CPU dynamic power = capacitance * frequency * voltage^2</code> (source?)([http://en.wikipedia.org/wiki/Dynamic_frequency_scaling])

As can be seen from the formula lower voltage plays greater part in CPU consumption than frequency. By reducing the voltage the damage of overclocking can be reduced and the battery life time extended.

==Calculating voltages==

According to [http://talk.maemo.org/showpost.php?p=606031&postcount=2375 this calculations] the voltage can be varied in steps of 0.0125 V with values 0-72. The formula is (with x being the kernel parameter value):

<code>V = x * 0.0125 + 0.6</code>

Examples:

Lowest voltage (x = 0): 0 * 0.0125 + 0.6 = 0 + 0.6 = 0.6 V
Highest voltage (x = 72): 72 * 0.0125 + 0.6 = 0.9 + 0.6 = 1.5 V
Random voltage (x = 38): 38 * 0.0125 + 0.6 = 0.475 + 0.6 = 1.075 V

==Summary==

FREQUENCY Nokia LV ULV XLV ideal
0 MHz 30 30 25 30 30
125 MHz 30 30 25 20 30
250 MHz 38 38 25 30 30
500 MHz 48 48 33 33 30
550 MHz *54* 48 38 38 33
600 MHz 60 *54* 38 38 38
700 MHz 54 45 45 45
750 MHz 54 45 45 45
810 MHz 54 48 48 48
850 MHz 54 48 48 48
900 MHz 54 *54* *54* *54*
950 MHz 54 54 54 54
1000 MHz 60 60 60 60
1100 MHz 72 72 72 72
1150 MHz 72 72 72 72
1200 MHz 72 72 72 72

Note: Asterisks indicate the first frequency in the kernel which needs overvoltage.

==/sys/power/vdd1_opps_vsel values==

LV: "30 30 38 48 48 54 54 54 54 54 54 54 60 72 72"
ULV: "25 25 25 33 38 38 45 45 48 48 54 54 60 72 72"
XLV: "30 20 30 33 38 38 45 45 48 48 54 54 60 72 72"
ideal: "30 30 30 30 33 38 45 45 48 48 54 54 60 72 72"

==Kernels' specifications==

===Nokia's kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
38 1.075V 250 MHz
48 1.200V 500 MHz
54 1.275V 550 MHz
60 1.350V 600 MHz

===titan's LV kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
38 1.075V 250 MHz
48 1.200V 500 MHz
48 1.200V 550 MHz
54 1.275V 600 MHz
54 1.275V 700 MHz
54 1.275V 750 MHz
54 1.275V 810 MHz
54 1.275V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1200 MHz

===titan's ULV kernel===

VALUE VOLTAGE FREQUENCY
25 0.912V 0 MHz
25 0.912V 125 MHz
25 0.912V 250 MHz
33 1.012V 500 MHz
38 1.075V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1200 MHz

===titan's XLV kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
20 0.850V 125 MHz
30 0.975V 250 MHz
33 1.012V 500 MHz
38 1.075V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1150 MHz

===titan's ideal kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
30 0.975V 250 MHz
30 0.975V 500 MHz
33 1.012V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1150 MHz

[[Category:Power users]]

Overclocking

2010-04-20T20:28:32Z

82.95.252.184: /* Battery */

=Overclocking=

This page is about overclocking the N900.
For the N8x0 see [http://talk.maemo.org/showthread.php?t=12464 this]

<nowiki>#</nowiki> ''WORK IN PROGRESS, HELP IF YOU WANT''

Overclocking is discussed in [http://talk.maemo.org/showthread.php?t=39753 this thread].
Benchmark results can be found [http://talk.maemo.org/showthread.php?p=605189 here].
If you're more interested in power saving read [http://talk.maemo.org/showthread.php?t=49654 this].

=Warnings=

- Overclocking WILL VOID YOUR WARRANTY 
- The lifetime of your device will get reduced 
- You could lose the data in your device (file system corruption) 
- Every device is an individual, what is stable for others might not be for you 
- If you encounter ANY unusual problems, lower your clock frequency 
- You do it at your own responsibility. No whining afterwards. If you're unsure, don't do it. 
- [http://depot.javispedro.com/nit/thewarningtm.jpeg Nokia's overclocking warning]: 500MHz is the normal frequency. Everything above is not good for your device, even with the stock kernel. 
- Igor Stoppa's [http://talk.maemo.org/showpost.php?p=596149&postcount=904 warning] and [http://talk.maemo.org/showpost.php?p=603833&postcount=66 comment]
- [http://talk.maemo.org/showpost.php?p=596274&postcount=937 chip vendors specs]

=Available kernels=

Overclocking requires installation of a custom kernel.
There are two types of kernels:
# modified PR1.1 kernels by Lehto and others. The only difference to the stock Nokia kernel is that the change the available hardcoded frequencies.
# enhanced kernels by titan. They are compatible with PR1.2 (!) , contain lots of additional features (IPv6, NAT etc) and bugfixes. In addition they include a large set of possible frequencies (125MHz-1.15GHz) which you manually set an try out without flashing a new kernel. The defaults are set to the standard 250-600MHz range. The kernel can be installed via HAM from the extras-devel catalouge.

== Installation of Lehto's PR1.1 kernels ==

[http://talk.maemo.org/showpost.php?p=594200&postcount=309 Lehto's Kernels]

[http://talk.maemo.org/showpost.php?p=595582&postcount=774 talk.maemo.org: Jakiman's Overclock Guide / Summary]

== Installation of titan's enhanced kernels ==
This kernel makes it possible dynamically change the maximum frequency up to 1.15GHz (supported frequencies are 125,250,500,550,600,700,750,805,850,900,950,1000,1100,1150MHz).
WARNING: Overclocking may damage your device and is at your own risk! It may void your warranty and destroy your data. You have been warned.

[http://talk.maemo.org/showthread.php?t=43420 talk.maemo.org: Discussion of the enhanded kernel]

'''Note:''' all commands on this page must be run as root in X Terminal (install rootsh package and enter "sudo gainroot")

=== Installation of the more stable [https://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/kernel-power-flasher/2.6.28-maemo24/ kernel (maemo24)] from extras-testing ===
With this kernel you can change the frequency limits, the voltages and DSP frequencies online.
It requires firmware PR1.1 or newer.
# Install the package kernel-power-settings (section system in HAM). It will automatically also install kernel-power-flasher.
# shutdown and boot again. There's no need for reflashing etc.
[Configuring_the_kernel_settings read this for configuration]

=== Installation of the experimental [https://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/kernel-power-flasher/2.6.28-maemo25/ kernel (maemo25)] from extras-devel ===
This kernel version contains additional experimental features and patches.
Changelogs are posted [https://garage.maemo.org/news/?group_id=1528 here].
# Install the package "Enhanced kernel for power users" (section system in HAM).
# shutdown and boot again. There's no need for reflashing etc.
Read the instructions for the stable kernel for more information.

=== Upgrade from older versions (< maemo24) ===
The package was previously called kernel-flasher-maemo.
If you have one of the older packages installed it it recommended that you upgrade in X Terminal
sudo gainroot
apt-get install -y kernel-power-flasher
apt-get remove kernel-flasher-maemo
If the new kernel still doesn't boot up, try
apt-get install --reinstall -y kernel-power kernel-power-flasher
Also try [http://talk.maemo.org/showpost.php?p=608343&postcount=2603 other hints] for deinstalling the old package.

Make sure you reset /etc/pmconfig to the defaults:
# Power management configuration file
enable_off_mode 1
sleep_while_idle 1
sr_vdd1_autocomp 0
sr_vdd2_autocomp 0
clocks_off_while_idle 1
voltage_off_while_idle 1
scaling_governor ondemand
scaling_max_freq 600000
scaling_min_freq 125000
sleep_ind 1

=== Deinstallation ===
sudo gainroot
apt-get install --reinstall -y kernel kernel-flasher
apt-get remove kernel-power kernel-power-modules

=== Configuring the kernel settings ===
[http://talk.maemo.org/showpost.php?p=610967&postcount=2718 read this for more details].

First verify, that the kernel is actually running:
uname -r
should return "2.6.28.10power-omap1"
It it does not, you should reboot or try to install again
apt-get install --reinstall -y kernel-power kernel-power-flasher
reboot, and test again.

Make sure the packages ''kernel-power-settings'' and ''rootsh'' are installed.
'''All commands need to be run as root user.'''
If you are normal user in X Terminal either "sudo gainroot" or prepend "sudo" to every command.

1) to try a configuration (you can replace "ideal" with default, lv, ulv, xlv or specify a file you created based on the template /usr/share/kernel-power-settings/default )
/usr/sbin/kernel-load /usr/share/kernel-power-settings/ideal
'''Note''': do [[NOT]] modify the files in /usr/share/kernel-power-settings/!
see '''Creating your own configuration:'' below.

2) to permanently install a default configuration
rm -f /etc/default/kernel-power
ln -s /usr/share/kernel-power-settings/ideal /etc/default/kernel-power
3) or your own config
rm -f /etc/default/kernel-power
cp <filename> /etc/default/kernel-power
4) and to immediately apply it
sudo /usr/sbin/kernel-load

'''For beginners:''' first reboot. then try 1) and check whether the device is stable. then do 2).

'''Creating your own configuration'''
5) copy the template to your mydocs (when not in mass storage mode)
cp /usr/share/kernel-power-settings/ideal /home/user/MyDocs/kernel.txt
6) edit the file ''/home/user/MyDocs/kernel.txt''. The defaults are
#UP_THRESHOLD=75
#SAMPLING_RATE=150000
VDD1_OPPS_VSEL="30 30 38 48 54 48 60 60 60 60 60 60 60 72 72"
DSP_OPPS_RATE="90 90 180 360 400 430 430 430 430 500 500 500 500 520 520"
MIN_FREQ=250000
MAX_FREQ=599000
SMARTREFLEX_VDD1=0
SMARTREFLEX_VDD2=0
For changing the frequency range change MIN_FREQ/MAX_FREQ (see "Temporarly change of the frequency limits" below ).
Either edit the file with an editor on your device (e.g., leafpad)
or USB mount it to edit it on the PC. unmount and unplug USB.
After editing load the configuration with
/usr/sbin/kernel-load /home/user/MyDocs/kernel.txt
and repeat 6) until you're happy.

7) to permanently install this new configuration
rm -f /etc/default/kernel-power
cp /home/user/MyDocs/kernel.txt /etc/default/kernel-power
/usr/sbin/kernel-load

8) to reset the device to the defaults use
rm -f /etc/default/kernel-power
/usr/sbin/kernel-load /usr/share/kernel-power-settings/default

'''Note''': the package automatically detects whether a certain misconfiguration has caused '''reboot loop.'''
It your device reboots twice within 5 minutes, it will load the default settings (250-600Mhz) so that you can fix or remove the invalid configuration file.
This also means that, when for some reason you manually reboot too quickly (<5min) your configuration will not be loaded.
To load it nonetheless run after booting
/usr/sbin/kernel-load

=== Temporarly change of the frequency limits ===
sudo gainroot
echo 250000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 599000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
The last line shows which values were actually set.
To set 125MHz use 124999, for 600MHz 599999, for everthing else x000 with x=MHz.
This setting takes effect immediately and is cleared with the next reboot.

=== Permanently change of the frequency limits ===
WARNING: Permanent overclocking is very dangerous!

Install kernel-power-settings and follow [http://talk.maemo.org/showpost.php?p=610967&postcount=2718 those instructions].

=== Battery ===
In kernels version >=maemo20 you can read out the current battery info:
modprobe bq27x00_battery
cat /sys/class/power_supply/bq27200-0/capacity
cat /sys/class/power_supply/bq27200-0/current_now
cat /sys/class/power_supply/bq27200-0/temp
cat /sys/class/power_supply/bq27200-0/voltage_now

=== Holding a kernel version ===
It your manually installed kernel should be not upgraded to the one in extras* try [http://talk.maemo.org/showpost.php?p=603915&postcount=2063 this]:
echo kernel-power-flasher hold | dpkg --set-selections
echo kernel-power hold | dpkg --set-selections
echo kernel-power-modules hold | dpkg --set-selections
to unlock the version:
echo kernel-power-flasher install | dpkg --set-selections
echo kernel-power install | dpkg --set-selections
echo kernel-power-modules install | dpkg --set-selections

=== Remarks ===
# The screen calibration in settings crashes immediately. It is a known bug in the calibration app, not in the kernel. It's mentioned in the kernel package description and is due to additional evdev (joystick,mouse) support. Just calibrate once with the stock kernel before you install the fully featured kernel.
# The kernel supports 125MHz but this frequency is [http://talk.maemo.org/showpost.php?p=617488&postcount=3095 disabled by default]. In version <25, it is enabled by specifying "124999", in later versions it is set in ''/sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies'' and can be enabled with
echo > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
# similarily, individual frequencies can be disabled in >=v25
echo 125000 250000 750000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
# even if 125Mhz is disabled, the telephone app will always try to set the minimum freq. to 125Mhz after a phone call, but it is ignored unless you enable 125Mhz.
# if you enable 125MHz also set "echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load" [http://talk.maemo.org/showpost.php?p=602687&postcount=185 hint]

# [http://talk.maemo.org/showpost.php?p=597703&postcount=141 the 125MHz issue]
# Installing another version of the enhanced kernel will just overwrite the older version. The stock kernel modules are preserved so that you can simply reflash the stock kernel via USB.
# If you for some reason get errors like this during removal or installation "rm: cannot remove '/lib/modules/2.6.28.10maemo-lv-omap1/modules.*': No such file or directory".try this [http://talk.maemo.org/showpost.php?p=603938&postcount=196 workaround]. There was a bug in one of the early LV kernels but it should be fixed in more recent versions.
# This kernel will not conflict with the future PR1.2 upgrade. The upgrade will, however, overwrite this kernel and you'll have to install it again.

=Additional information and hints=

# the frequencies available in the Nokia kernel are: 250, 500, 550 and 600MHz.
# Nokia [http://talk.maemo.org/showpost.php?p=601691&postcount=1823 locks the device to 600MHz] during phone calls. This may be a bug. It also [http://talk.maemo.org/showpost.php?p=600721&postcount=1720 affects] Lehto's kernels.
# the telephone app is closed-source and broken. After a phone call it sets the maximum to 600Mhz and the minimum to 250MHz (or 125MHz if available) irrespective of what you have set before.
# when connected via USB the device locks the minimum frequency to 500Mhz.
# By default the device is configured to use 125MHz as the lowest frequency but it not enabled in the kernel [https://bugs.maemo.org/show_bug.cgi?id=7116 pmconfig bug]
# [http://talk.maemo.org/showpost.php?p=599870&postcount=170 improving responsiveness]
# [http://talk.maemo.org/showpost.php?p=599618&postcount=168 safe pmconfig configuration]
# the warning "WARNING: at arch/arm/mach-omap2/clock34xx.c:443 omap3_noncore_dpll_set_rate+0x28c/0x2dc()" in the kernel logs (dmesg) only happens if the invalid 800MHz frequency was selected. ignore it.
# [http://talk.maemo.org/showpost.php?p=603585&postcount=189 saving more battery power when idle]
# EvilJazz had photoshopped a [http://talk.maemo.org/showpost.php?p=605523&postcount=90 picture of a device being overclocked 1.7GHz]. It's a JOKE!
# reading one of the temperature sensors "cat /sys/devices/platform/omap34xx_temp/temp1_input"

=Useful stuff=

==Show current CPU frequency==

awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

==Set maximum CPU frequency==

From root terminal:

rootsh echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq | echo ""

Replace 600000 with desired maximum frequency. Pay attention to the two exceptions in titan's kernels (124999 and 599000). The list of available frequencies on your device/kernel can be obtained with command:

awk '{print $1/1000" MHz"}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

==Script for analyzing time_in_state (by rooted) - rev6==

This script prints percentage of frequencies (states) used and some additional info useful for posting on the forum (debugging). It displays all frequencies, works with all kernels and it is not affected by the bug which resets minimum frequency after phone call.

The script is in active development. I'm adding new features and resolving bugs if they are reported. Please update your script to newest revision and report if something doesn't work properly.

Temperature may not be listed if you don't have module bq27x00_battery installed or enabled. Also kernel-maemo version is not listed if you don't use titan's kernel.

#!/bin/sh

currfreq=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`
idlefreq=`awk '{if ($2 > 0) print $1}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state | tail -n 1`
tis1=`awk '{sum += $2} END {print sum}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`
tis2=`awk '$1 == "'"$idlefreq"'" {idle = $2} {sum += $2} END {print sum-idle}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`

echo -e "
SCRIPT FOR ANALYZING TIME_IN_STATE
By rooted (maemo.org)
Revision 6

The script is in active development.
Update your script to current revision from:
wiki.maemo.org/Overclocking

FREQUENCY\tUSED\t\tWHEN BUSY\n"
awk '
{if ($1 >= 1000000) printf ("%.0f MHz\t",$1/1000); else printf ("%.0f MHz\t\t",$1/1000)}
{if ($2 == 0) printf "unused"; else printf ("%.1f %\t\t",($2*100)/"'"$tis1"'")}
{if ($2 == 0 || $2/"'"$tis2"'" > 1) printf "\n"; else printf ("%.1f %\n",($2*100)/"'"$tis2"'")}
' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

echo -e "
Current frequency: $(($currfreq/1000)) MHz
Idle frequency: $(($idlefreq/1000)) MHz
Kernel: `uname -r`
kernel-maemo: `dpkg -l kernel* | awk '/kernel-maemo/ {print $3}'`
Uptime: `uptime | sed -e 's/.*p *//' -e 's/, l.*//' -e 's/ / /'`
Load: `uptime | sed 's/.*e: //'`
Boot reason: `cat /proc/bootreason`
Temperature: `cat /sys/class/power_supply/bq27200-0/temp` °C\n"

Output example:

SCRIPT FOR ANALYZING TIME_IN_STATE
By rooted (maemo.org)
Revision 6

The script is in active development.
Update your script to current revision from:
wiki.maemo.org/Overclocking

FREQUENCY USED WHEN BUSY

1200 MHz unused
1100 MHz unused
1000 MHz unused
950 MHz unused
900 MHz unused
850 MHz unused
810 MHz 1.6 % 56.7 %
750 MHz 0.0 % 0.8 %
700 MHz 0.1 % 1.9 %
600 MHz 0.0 % 1.5 %
550 MHz 0.0 % 1.2 %
500 MHz 1.0 % 37.8 %
250 MHz 97.3 %
125 MHz unused

Current frequency: 250 MHz
Idle frequency: 250 MHz
Kernel: 2.6.28.10maemo-ulv-omap1
kernel-maemo: 2.6.28-maemo21
Uptime: 2 days, 2:27
Load: 0.11, 0.04, 0.01
Boot reason: pwr_key
Temperature: 25 °C

==Analyzing time in state, including idle mode stats (by ArbitRabbit)==
The following script will show the current frequency and statistics for each state, including time spent in idle mode when the CPU is actually sleeping.
This script works with the special frequency handling in Titan's kernel.

To run this script as user and be able to set the frequencies you will need to install "[[Root_access|rootsh]]" via apt-get.

'''scheduler_stats.sh'''

#!/bin/sh
awk '{print "\nCurrent frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
awk '{print "Minimum frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
awk '{print "Maximum frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

tis1=`awk '{SUM += $2} END {printf("%.0f",SUM/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`

idle0=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state0/time`

idle1=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state1/time`

idle2=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state2/time`

idle3=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state3/time`

totaltime=$(($idle0+$idle1+$idle2+$idle3+$tis1))
echo -e "FREQUENCY\tUSED"
SUM=0
awk '
{
printf (($1/1000)" MHz \t");
if ($2 == 0)
{
printf "0 %\n";
}
else {
SUM+=$2;
printf("%.3f %\n",($2/10)/"'"$totaltime"'");
}
}
END{
printf ("Time spent in idle mode is %2.2f %\n",(1-((SUM/1000)/"'"$totaltime"'"))*100);
}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
echo ""

'''Sample Output'''

Current frequency: 500 MHz

Minimum frequency: 500 MHz

Maximum frequency: 810 MHz

FREQUENCY USED
1200 MHz 0 %
1100 MHz 0 %
1000 MHz 0 %
950 MHz 0 %
900 MHz 0 %
850 MHz 0 %
810 MHz 0.000 %
750 MHz 0.000 %
700 MHz 0.000 %
600 MHz 0.000 %
550 MHz 0.000 %
500 MHz 0.010 %
Time spent in idle mode is 99.99 %

Known Bugs: Requires the Phone to be booted for an hour or so before it results in decent stats.

==Combined helper script (by evilJazz)==

The following script will show the current frequency and statistics. It also accepts two optional parameters that will set the max and/or min frequencies (in MHz unit). Calling the script without these parameters will not set the new clocking. Instead it will just show the current frequencies and statistics.

This script works with the special frequency handling in Titan's kernel.

To run this script as user and be able to set the frequencies you will need to install "[[Root_access|rootsh]]" via apt-get.

overclock.sh [max freq] [min freq]

#!/bin/sh
max=${1}000
min=${2}000

# Handle and rewrite special cases in Titan's kernel...
[ "$max" == "600000" ] && max=599000
[ "$min" == "125000" ] && min=124999

if [ $(id -u) -ne 0 ]; then
[ "$max" != "000" ] && echo "echo $max > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" | sudo gainroot
[ "$min" != "000" ] && echo "echo $min > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq" | sudo gainroot
else
[ "$max" != "000" ] && echo $max > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[ "$min" != "000" ] && echo $min > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
fi

awk '{printf("\nCurrent frequency: %7s MHz\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
awk '{printf("Minimal frequency: %7s MHz\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
awk '{printf("Maximal frequency: %7s MHz\n\n", $1/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

sum=$(awk '{SUM += $2} END {print SUM}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state)
awk '{printf("%7s MHz: %5.1f % (%8d)\n", ($1/1000), ($2 * 100)/"'"$sum"'", $2)}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
echo

Output example:

~ $ ./overclock.sh 600 250

Current frequency: 250 MHz
Minimal frequency: 250 MHz
Maximal frequency: 599 MHz

1200 MHz: 0.0 % ( 0)
1100 MHz: 0.0 % ( 0)
1000 MHz: 0.0 % ( 0)
950 MHz: 0.0 % ( 0)
900 MHz: 0.2 % ( 271)
850 MHz: 0.0 % ( 0)
810 MHz: 0.0 % ( 0)
750 MHz: 0.0 % ( 0)
700 MHz: 0.0 % ( 0)
600 MHz: 9.0 % ( 13663)
550 MHz: 0.5 % ( 701)
500 MHz: 15.4 % ( 23379)
250 MHz: 75.0 % ( 114021)
124.999 MHz: 0.0 % ( 0)

=Changing the Kernel=

==Installing a modified Kernel==

===Flashing using PC===

1. Power off the N900 completely.

2. Hold "u" on the N900's keyboard, while holding, connect it to the PC via USB cable.

3. You will see usb icon on top right of white Nokia screen.

4. Now you can let go of "u" on the keyboard.

5. Now use flasher utility with the kernel file located in the same directory.

flasher-3.5 -k image_file_name -f -R

6. It should take about 1-2 seconds then it'll say Done.

7. Now your N900 will show white Nokia screen. (reboot)

8. At this time, you can pull out the USB cable.

9. N900 should finish booting up if all goes well.

10. Test out your phone as usual. (Apps, browser, camera, phone etc etc)

11. If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again.
note: For Windows7 64bit users, you may need to use WindowsXP mode. ([http://www.youtube.com/watch?v=Bx6dblXl2eo Youtube Tutorial])

===Flashing from N900 xterminal===

* do a backup, have a pc nearby and know you are able to flash the n900 with flasher-3.5 - just in case

0. Launch xterminal app then type sudo gainroot (need rootsh installed)

1. type
softupd -vv -s --local
(thats double v)

2. open new terminal

3. type
flasher --local -f -k <kernel_zimage_file_with_path>

4. you see the flashing (takes some time)

5. type "sync" to save changes

6. type "reboot" and enter to restart

7. Test out your phone as usual. (Apps, browser, camera, phone etc etc)

8. If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again.

'''You are fully responsible for any damage caused by overclocking. Not anyone else.'''

==Reverting to the Original Kernel==

If you want to revert to the original kernel, execute:

apt-get install --reinstall kernel kernel-flasher

=Voltage tables=

One factor reducing CPU lifetime is the current it is running with.

<code>CPU dynamic power = capacitance * frequency * voltage^2</code> (source?)([http://en.wikipedia.org/wiki/Dynamic_frequency_scaling])

As can be seen from the formula lower voltage plays greater part in CPU consumption than frequency. By reducing the voltage the damage of overclocking can be reduced and the battery life time extended.

==Calculating voltages==

According to [http://talk.maemo.org/showpost.php?p=606031&postcount=2375 this calculations] the voltage can be varied in steps of 0.0125 V with values 0-72. The formula is (with x being the kernel parameter value):

<code>V = x * 0.0125 + 0.6</code>

Examples:

Lowest voltage (x = 0): 0 * 0.0125 + 0.6 = 0 + 0.6 = 0.6 V
Highest voltage (x = 72): 72 * 0.0125 + 0.6 = 0.9 + 0.6 = 1.5 V
Random voltage (x = 38): 38 * 0.0125 + 0.6 = 0.475 + 0.6 = 1.075 V

==Summary==

FREQUENCY Nokia LV ULV XLV ideal
0 MHz 30 30 25 30 30
125 MHz 30 30 25 20 30
250 MHz 38 38 25 30 30
500 MHz 48 48 33 33 30
550 MHz *54* 48 38 38 33
600 MHz 60 *54* 38 38 38
700 MHz 54 45 45 45
750 MHz 54 45 45 45
810 MHz 54 48 48 48
850 MHz 54 48 48 48
900 MHz 54 *54* *54* *54*
950 MHz 54 54 54 54
1000 MHz 60 60 60 60
1100 MHz 72 72 72 72
1150 MHz 72 72 72 72
1200 MHz 72 72 72 72

Note: Asterisks indicate the first frequency in the kernel which needs overvoltage.

==/sys/power/vdd1_opps_vsel values==

LV: "30 30 38 48 48 54 54 54 54 54 54 54 60 72 72"
ULV: "25 25 25 33 38 38 45 45 48 48 54 54 60 72 72"
XLV: "30 20 30 33 38 38 45 45 48 48 54 54 60 72 72"
ideal: "30 30 30 30 33 38 45 45 48 48 54 54 60 72 72"

==Kernels' specifications==

===Nokia's kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
38 1.075V 250 MHz
48 1.200V 500 MHz
54 1.275V 550 MHz
60 1.350V 600 MHz

===titan's LV kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
38 1.075V 250 MHz
48 1.200V 500 MHz
48 1.200V 550 MHz
54 1.275V 600 MHz
54 1.275V 700 MHz
54 1.275V 750 MHz
54 1.275V 810 MHz
54 1.275V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1200 MHz

===titan's ULV kernel===

VALUE VOLTAGE FREQUENCY
25 0.912V 0 MHz
25 0.912V 125 MHz
25 0.912V 250 MHz
33 1.012V 500 MHz
38 1.075V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1200 MHz

===titan's XLV kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
20 0.850V 125 MHz
30 0.975V 250 MHz
33 1.012V 500 MHz
38 1.075V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1150 MHz

===titan's ideal kernel===

VALUE VOLTAGE FREQUENCY
30 0.975V 0 MHz
30 0.975V 125 MHz
30 0.975V 250 MHz
30 0.975V 500 MHz
33 1.012V 550 MHz
38 1.075V 600 MHz
45 1.163V 700 MHz
45 1.163V 750 MHz
48 1.200V 810 MHz
48 1.200V 850 MHz
54 1.275V 900 MHz
54 1.275V 950 MHz
60 1.350V 1000 MHz
72 1.500V 1100 MHz
72 1.500V 1150 MHz

[[Category:Power users]]

Phone control

2010-01-08T21:42:15Z

82.95.252.184: /* From Python : */

=DBUS=

Here's a number of dbus examples that can be run as simple shell scripts. When running them they should be run with `run-standalone.sh` in front of them to set up the environment correctly. Otherwise they may barf when run from cron, startup, install scripts, etc. They run fine when run as user "user" without `run-standalone.sh`. Example:
run-standalone.sh dbus-send /foo bar 'boo'

===dbus-send-call===
dbus-send --system --dest=com.nokia.csd.Call --type=method_call --print-reply \
/com/nokia/csd/call com.nokia.csd.Call.CreateWith string:"$1" uint32:0

With this fantastic command you can make a fone call from the command line. Change $1 to whatever number you want, or if you put this in a shell script, run it and use the number you want to call as the option, ala:
dbus-send-call 15555551234

====From Python :====

import dbus
def place_call(number):
bus = dbus.SystemBus()
csd_call = dbus.Interface(bus.get_object('com.nokia.csd',
'/com/nokia/csd/call'),
'com.nokia.csd.Call')
csd_call.CreateWith(str(number), dbus.UInt32(0))

===dbus-send-call-start-ui===
dbus-send --print-reply --type=method_call --dest=com.nokia.HildonDesktop.AppMgr /com/nokia/HildonDesktop/AppMgr com.nokia.HildonDesktop.AppMgr.LaunchApplication string:'rtcom-call-ui'

===dbus-release-call===

dbus-send --system --dest=com.nokia.csd.Call --print-reply \
/com/nokia/csd/call com.nokia.csd.Call.Release

This will release/end/hangup/reject the current call (or possibly all calls if more then one call is active - needs testing to verify behavior when more then 1 call active) or do nothing if no calls are active.

===dbus-send-activate-led===
dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:PatternCommunicationIM

===dbus-send-deactivate-led===
dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_deactivate string:PatternCommunicationIM

===dbus-send-disconnect-net===
dbus-send --system --dest=com.nokia.icd /com/nokia/icd_ui com.nokia.icd_ui.disconnect boolean:true

===dbus-send-email-new===
dbus-send --print-reply --type=method_call --dest=com.nokia.modest /com/nokia/modest com.nokia.modest.MailTo string:mailto:

===dbus-send-email-tx-rx===
Doesn't work
dbus-send --session --type=method_call --dest=com.nokia.osso_email /com/nokia/osso_email com.nokia.osso_email.send_and_receive

===dbus-send-get-imei===
dbus-send --system --print-reply --type=method_call --dest=com.nokia.phone.SIM /com/nokia/phone/SIM/security Phone.Sim.Security.get_imei

===dbus-send-google===
dbus-send --system --type=method_call --dest="com.nokia.osso_browser" --print-reply /com/nokia/osso_browser/request com.nokia.osso_browser.load_url string:"google.com"

===dbus-send-hello-world===
dbus-send --print-reply \
--type=method_call --dest=org.freedesktop.Notifications \
/org/freedesktop/Notifications org.freedesktop.Notifications.SystemNoteDialog \
string:'Hello, world!' uint32:0 string:'NAO OK!'

===dbus-send-im-here===
dbus-send --type=method_call --print-reply --dest=org.freedesktop.Telepathy.MissionControl /org/freedesktop/Telepathy/MissionControl org.freedesktop.Telepathy.MissionControl.SetPresence uint32:2 string:"I'm here"

===dbus-send-lock===
dbus-send --print-reply --system --type=method_call --dest=com.nokia.system_ui /com/nokia/system_ui/request com.nokia.system_ui.request.devlock_open string:'com.nokia.mce' string:'/com/nokia/mce/request' string:'com.nokia.mce.request' string:'devlock_callback' uint32:'3'

===dbus-send-media-play===
dbus-send --print-reply --dest=com.nokia.mediaplayer /com/nokia/mediaplayer com.nokia.mediaplayer.mime_open string:"file:///$1"

===dbus-send-music-pause===
dbus-send --dest=com.nokia.osso_media_server /com/nokia/osso_media_server com.nokia.osso_media_server.music.pause

===dbus-send-notification===
Usage:
dbus-send-notification "foo bar boo bah bang"

dbus-send --print-reply \
--type=method_call --dest=org.freedesktop.Notifications \
/org/freedesktop/Notifications org.freedesktop.Notifications.SystemNoteDialog \
string:"$1" uint32:0 string:'NAO OK!'

====From Python :====

import dbus
def show_notification_dialog(message, mode="single"):
bus = dbus.SystemBus()
iface = dbus.Interface(bus.get_object('org.freedesktop.Notifications',
'/org/freedesktop/Notifications'),
'org.freedesktop.Notifications')
if mode == "single":
iface.SystemNoteInfoprint(message)
elif mode == "multiline":
iface.SystemNoteDialog(str(message), dbus.UInt32(0), 'Ok')

This function allows you to show notification either with multiline (on maemo pre-5 it will show a dialog with an "Ok" button) or single line (tiny notifications hiding automatically).

===dbus-send-pause-panucci===
dbus-send --type="method_call" --dest=org.panucci.panucciInterface /panucciInterface org.panucci.panucciInterface.playPause

===dbus-send-reboot===
dbus-send --system --type=method_call --dest="com.nokia.mce" --print-reply "/com/nokia/mce/request" com.nokia.mce.request.req_reboot

===dbus-send-regist-status===
dbus-send --system --print-reply --type=method_call --dest='com.nokia.phone.net' /com/nokia/phone/net Phone.Net.get_registration_status

===dbus-send-show_conn===
dbus-send --print-reply --system --dest=com.nokia.icd_ui /com/nokia/icd_ui com.nokia.icd_ui.show_conn_dlg boolean:true

===dbus-send-shutdown===
dbus-send --system --type=method_call --dest="com.nokia.mce" --print-reply "/com/nokia/mce/request" com.nokia.mce.request.req_shutdown

===dbus-send-speaker-off===
dbus-send --type=method_call --dest=com.nokia.osso_hp_ls_controller /com/nokia/osso_hp_ls_controller com.nokia.osso_hp_ls_controller.loudspeaker.force_ loudspeaker_off

===dbus-send-speaker-on===
dbus-send --type=method_call --dest=com.nokia.osso_hp_ls_controller /com/nokia/osso_hp_ls_controller com.nokia.osso_hp_ls_controller.loudspeaker.force_ loudspeaker_on

===dbus-send-task-switcher===
dbus-send --type=signal --session /com/nokia/hildon_desktop com.nokia.hildon_desktop.exit_app_view

===dbus-send-unlock===
dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_tklock_mode_change string:"unlocked"

===dbus-send-unlock2===
dbus-send --print-reply --system --type=method_call --dest=com.nokia.system_ui /com/nokia/system_ui/request com.nokia.system_ui.request.devlock_close string:'com.nokia.mce' string:'/com/nokia/mce/request' string:'com.nokia.mce.request' string:'devlock_callback' uint32:'0'

Phone control

2010-01-08T21:41:43Z

82.95.252.184: /* From Python : */