Maemo Wiki Mirror - User contributions [en]

Phone control

2011-09-12T04:43:27Z

213.240.181.249: /* Securing */

{{ambox
| type = notice
| image=
| text = '''This page is about controlling your Nokia device. For historical reasons this page is called '''phone''' control even though it really covers more than just the phone functions.'''
}}

{{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) 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.

If you answer the call immediately as you receive the Call Coming D-Bus message the phone seems to be in a specific call state where answering yields a <code>com.nokia.csd.Call.Error.NotAllowed</code> exception.

You need to answer the call after a delay of e.g. 1 s.

Another (probably better) approach is to register to the CallStatus D-Bus message (<code>com.nokia.csd.Call</code>, <code>/com/nokia/csd/call/1</code>, <code>com.nokia.csd.Call.Instance.CallStatus</code>) and wait for a call status >= 2 (=<code>CSD_CALL_STATUS_COMING</code>) after the "Coming" message.

====Set Call forwarding====

call forward unanswered calls after 20 sec to 0731234567
dbus-send --system --type=method_call --print-reply --dest=com.nokia.csd.SS /com/nokia/csd/ss com.nokia.csd.SS.DivertActivate uint32:5 string:"0731234567" uint32:20

====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|awk -F "\"" '/g/ {print $2}'

====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|awk -F "\"" '/g/ {print $2}'

====Get SIM status====

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

====Get cellular signal strength====

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

First line is percentage, second is dBm, third unknown.

====Get cellular registration status====

dbus-send --system --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_on

(These loudspeaker ones don't work on my N900. If I add --print-reply I get "Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.nokia.osso_hp_ls_controller was not provided by any .service files".)

====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_off

====Turn loudspeaker on (N900)====

dbus-send --type=method_call --dest=org.maemo.Playback.Manager /org/maemo/Playback/Manager org.maemo.Playback.Manager.RequestPrivacyOverride boolean:true

====Turn loudspeaker off (N900)====
dbus-send --type=method_call --dest=org.maemo.Playback.Manager /org/maemo/Playback/Manager org.maemo.Playback.Manager.RequestPrivacyOverride boolean:false

====Turn mute on (N900)====

dbus-send --type=method_call --dest=org.maemo.Playback.Manager /org/maemo/Playback/Manager org.maemo.Playback.Manager.RequestMute boolean:true

====Turn mute off (N900)====
dbus-send --type=method_call --dest=org.maemo.Playback.Manager /org/maemo/Playback/Manager org.maemo.Playback.Manager.RequestMute boolean:false

====Turn bluetooth override on (N900)====

dbus-send --type=method_call --dest=org.maemo.Playback.Manager /org/maemo/Playback/Manager org.maemo.Playback.Manager.RequestBluetoothOverride boolean:true

====Turn bluetooth override off (N900)====
dbus-send --type=method_call --dest=org.maemo.Playback.Manager /org/maemo/Playback/Manager org.maemo.Playback.Manager.RequestBluetoothOverride boolean:false

====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|awk -F "\"" '/g/ {print $2}'

====Get all profile Values====

You can modify any profile value, eg. clock alarm enabled, im alert volume, keypad sound level, touchscreen sound level, ... To find out which keys exist, to what value they are set and what values can be given you can use the following command. (For the profile "silent" just put "silent" at the end instead of "general".)

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

The returned value is an array of struct. Each struct has 3 strings: key, value, type. Type can be eg. "INTEGER 0-2" saying that the values 0, 1 and 2 are correct values for this key.

====Set a profile value====

To modify the above mentioned profile values you need this method. The method takes three parameters, all strings: profile, key and value. Profile can be "general" or "silent", key is one of the keys from the above (get all profile values), value can be set to anything allowed by "type" from the above method.

To enable vibrating alert for the profile "general" your script would look like this:

dbus-send --type=method_call --dest=com.nokia.profiled /com/nokia/profiled com.nokia.profiled.set_value string:"general" string:"vibrating.alert.enabled" string:"On"

===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 up to 2 minutes for modest to start refreshing and after that it depends on the speed of the connection how fast it is going to be completed, usually up to 5 seconds, 2G can be a bit slower.

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"

Note: This method does not work in Maemo 5. Workaround: http://talk.maemo.org/showthread.php?t=55686

====Change peak_schedule settings====

Check:
run-standalone.sh gconftool-2 -R /apps/activesync

Set (check if yours is named ActiveSyncAccount1):
run-standalone.sh gconftool-2 --set /apps/activesync/ActiveSyncAccount1/schedule/peak_schedule --type=int 15
Where the last number is one of the following (as standard in GUI):

* '''0''' = Always on
* '''-1''' = Manual
* '''15''' = Every 15 minutes
* '''30''' = Every 30 minutes
* '''60''' = Every hour
* '''240''' = Every 4 hours
* '''720''' = Every 12 hours

===Media player===

====Open file in media player====

dbus-send --print-reply --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

====Unpause 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.resume

====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'

====Query Devlock State====

dbus-send --system --type=method_call --dest="com.nokia.mce" --print-reply "/com/nokia/mce/request" com.nokia.mce.request.get_devicelock_mode |awk -F "\"" '/g/ {print $2}'

====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====

This command will unlock and illuminate the screen (useful when accessing the phone externally through [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTY])
dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_tklock_mode_change string:"unlocked"

====Query lock state of screen and keys====

Will return ''locked'' or ''unlocked'' depending on lock state
dbus-send --system --type=method_call --dest="com.nokia.mce" --print-reply "/com/nokia/mce/request" com.nokia.mce.request.get_tklock_mode|awk -F "\"" '/g/ {print $2}'

===Networking===

====Enable ICD log====
There are two methods to enable ICD logs

1. Print to the syslog:
(1)Use the following cmd
(2)$ syslogd
(3)$ icd2 –l0
(4)The log will print to the /var/log/syslog
2. Print to the standard output
(1)Get the source code of icd2
(2)Add the begging of source code of “support/osso-log.h” "#define OSSOLOG_STDOUT"
(3)$ icd2 –l0
(4)The log will print to the standard output

====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.
If not, an error message will occur if you add --print-reply to the dbus-send command.

====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====

=====ICD2=====

dbus-send --print-reply --system --dest=com.nokia.icd2 /com/nokia/icd2 com.nokia.icd2.disconnect_req uint32:0x8000

=====ICD=====

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

On [[Maemo 5/PR1.2|PR1.2]] :
Error org.freedesktop.DBus.Error.UnknownMethod: Method "disconnect" with signature "b" on interface "com.nokia.icd_ui" doesn't exist

====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? Most likely, boolean:true leads to using saved connections if there are any, and boolean:false forces to display the connection dialog.

====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===

====Current Mode====

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

====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}'
or
dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.DefaultAdapter | awk -F'"' '/at/ {print $2}'

====Identify Properties====

dbus-send --system --print-reply --type=method_call --dest=org.bluez $(dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.DefaultAdapter | awk -F'"' '/at/ {print $2}') org.bluez.Adapter.GetProperties

====Enable====

Using the adapter path value returned with first 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.DefaultAdapter | 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.DefaultAdapter | 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.DefaultAdapter | awk -F'"' '/at/ {print $2}')
device=$(dbus-send --system --print-reply --dest=org.bluez ${adapter} org.bluez.Adapter.FindDevice string:${devmac} | awk -F'"' '/at/ {print $2}')
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"

===Open a pdf file with the default pdf reader application===

dbus-send --print-reply --dest=com.nokia.osso_pdfviewer /com/nokia/osso_pdfviewer com.nokia.osso_pdfviewer.mime_open string:/home/user/MyDocs/.documents/file_name.pdf

===Open a file with the default notes application===

dbus-send --print-reply --dest=com.nokia.osso_notes /com/nokia/osso_notes com.nokia.osso_notes.mime_open string:/home/user/MyDocs/.documents/file_name

===Open the default notes application===

dbus-send --print-reply --dest=com.nokia.osso_notes /com/nokia/osso_notes com.nokia.osso_notes.top_application

=== Open folder ===

dbus-send --print-reply --dest=com.nokia.osso_filemanager /com/nokia/osso_filemanager com.nokia.osso_filemanager.open_folder string:/home/user/MyDocs/

===Set volume===

dbus-send --type=method_call --dest=com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer /com/nokia/mafw/renderer/gstrenderer com.nokia.mafw.extension.set_extension_property string:volume variant:uint32:50

The value can be between 0 and 100.

===Get volume===

dbus-send --print-reply --type=method_call --dest=com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer /com/nokia/mafw/renderer/gstrenderer com.nokia.mafw.extension.get_extension_property string:volume|awk '/nt/ {print $3}'

===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

====Device Orientation====

dbus-send --system --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.get_device_orientation

==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==

===Take a picture with front camera===

gst-launch v4l2src device=/dev/video1 num-buffers=1 ! ffmpegcolorspace ! jpegenc ! filesink location=frontcam.jpg

===Shoot photo after 10 seconds===

The camera application must be off for it to work. And of course the camera shutter must be open...gst-launch comes with gstreamer-tools (or gst-launch-0.10 and gstreamer0.10-tools)

/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 via the cellular network===

<source lang="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))
</source>

=== Make a phone call via SIP ===
<source lang="python">
#!/usr/bin/python

import dbus
import sys

# Get the target phone number (or SIP address) from the command line
TARGET = sys.argv[1];

# Configure the telepathy path to the SofiaSIP account that we wish to use.
# Use "mc-tool list" (from the libmissioncontrol-utils package) to see your accounts.
SIP_ACCOUNT = 'sofiasip/sip/_31234567_40sipgate_2eco_2euk0'

# This gets us a connnection to the session bus
bus = dbus.SessionBus()

# This sets up a path to the SIP account within telepathy.
PATH = '/org/freedesktop/Telepathy/Account/'
PATH += SIP_ACCOUNT

# This sets up a proxy object as a "handle" to the AccountManager of our target account
account = bus.get_object('org.freedesktop.Telepathy.AccountManager', PATH)

# This launches the actual SIP call with a method call to EnsureChannel on that object
account.EnsureChannel( \
dbus.Dictionary({
dbus.String(u'org.freedesktop.Telepathy.Channel.TargetHandleType'): dbus.UInt32(1),
dbus.String(u'org.freedesktop.Telepathy.Channel.ChannelType'): dbus.String(u'org.freedesktop.Telepathy.Channel.Type.StreamedMedia'),
dbus.String(u'org.freedesktop.Telepathy.Channel.TargetID'): dbus.String(TARGET),
}, signature='sv'),
dbus.UInt64(0),
dbus.String(''),
dbus_interface='com.nokia.Account.Interface.ChannelRequests')

sys.exit(0)

</source>

===Send SMS===

ssms.py using new QtMobility bindings by ossipena:

<source lang="python">
#!/usr/bin/env python
# -*- coding: utf-8 -*-

#ssms Ossipena/TimoP
#send smses from command line
#licence : Do whatever you want
#deps:
#pyside-qt4
#pyside-mobility

'''imports'''
from QtMobility.Messaging import *
from PySide.QtCore import *
import sys
from PyQt4 import QtCore

app = QCoreApplication(sys.argv)

'''get number and name'''
stringit = sys.argv
numpertemp = str(stringit[1:2])
mesits = str(stringit[2:])[2:-2]

num = str(numpertemp[2:-2])

if (mesits == ""):
print "Usage:"
print "python ssms.py 01234567 'message text here'"
sys.exit(69)
else:
print "number is " + str(num)
print "message is " + str(mesits)

'''define message to be sent'''
numperi = QtCore.QString(num)

numper = QMessageAddress(QMessageAddress.Phone, numperi)
mesitsi = QMessage()
mesitsi.setType(QMessage.Sms)
mesitsi.setTo(numper)
mesitsi.setBody(mesits)

'''send message'''
sender = QMessageService()
if (sender.send(mesitsi)):
print "success"
else:
print "fail"
</source>

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

<source lang="python">
#!/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();
</source>

There's also a python script that uses D-Bus instead from http://talk.maemo.org/showpost.php?p=558430&postcount=57:

<source lang="python">
#!/usr/bin/env python2.5
import sched, time
import dbus
import gobject
from dbus.mainloop.glib import DBusGMainLoop

def octify(str):
'''
Returns a list of octet bytes representing
each char of the input str.
'''

bytes = map(ord, str)
bitsconsumed = 0
referencebit = 7
octets = []

while len(bytes):
byte = bytes.pop(0)
byte = byte >> bitsconsumed

try:
nextbyte = bytes[0]
bitstocopy = (nextbyte & (0xff >> referencebit)) << referencebit
octet = (byte | bitstocopy)

except:
octet = (byte | 0x00)

if bitsconsumed != 7:
octets.append(byte | bitstocopy)
bitsconsumed += 1
referencebit -= 1
else:
bitsconsumed = 0
referencebit = 7

return octets

def semi_octify(str):
'''
Expects a string containing two digits.
Returns an octet -
first nibble in the octect is the first
digit and the second nibble represents
the second digit.
'''
try:
digit_1 = int(str[0])
digit_2 = int(str[1])
octet = (digit_2 << 4) | digit_1
except:
octet = (1 << 4) | digit_1

return octet

def deoctify(arr):

referencebit = 1
doctect = []
bnext = 0x00

for i in arr:

bcurr = ((i & (0xff >> referencebit)) << referencebit) >> 1
bcurr = bcurr | bnext

if referencebit != 7:
doctect.append( bcurr )
bnext = (i & (0xff << (8 - referencebit)) ) >> 8 - referencebit
referencebit += 1
else:
doctect.append( bcurr )
bnext = (i & (0xff << (8 - referencebit)) ) >> 8 - referencebit
doctect.append( bnext )
bnext = 0x00
referencebit = 1

return ''.join([chr(i) for i in doctect])

def createPDUmessage(number, msg):
'''
Returns a list of bytes to represent a valid PDU message
'''
numlength = len(number)
if (numlength % 2) == 0:
rangelength = numlength
else:
number = number + 'F'
rangelength = len(number)

octifiednumber = [ semi_octify(number[i:i+2]) for i in range(0,rangelength,2) ]
octifiedmsg = octify(msg)
HEADER = 1
FIRSTOCTETOFSMSDELIVERMSG = 10
ADDR_TYPE = 129 #unknown format
number_length = len(number)
msg_length = len(msg)
pdu_message = [HEADER, FIRSTOCTETOFSMSDELIVERMSG, number_length, ADDR_TYPE]
pdu_message.extend(octifiednumber)
pdu_message.append(0)
pdu_message.append(0)
pdu_message.append(msg_length)
pdu_message.extend(octifiedmsg)
return pdu_message

def sendmessage(number, message):

bus = dbus.SystemBus()
smsobject = bus.get_object('com.nokia.phone.SMS', '/com/nokia/phone/SMS/ba212ae1')
smsiface = dbus.Interface(smsobject, 'com.nokia.csd.SMS.Outgoing')
arr = dbus.Array(createPDUmessage(number.replace('+', '00'), message))

msg = dbus.Array([arr])
smsiface.Send(msg,'')

def callback(pdumsg, msgcenter, somestring, sendernumber):

msglength = int(pdumsg[18])
msgarray = pdumsg[19:len(pdumsg)]

msg = deoctify(msgarray)

if msg > 0:
print 'New message received from %s' % sendernumber
print 'Message length %d' % msglength
print 'Message: %s' % msg

if msg == "ping":
print "Sending reply: pong"
sendmessage(sendernumber.replace("+","00"), "pong")
else:
print "Unknown command"

def listen():
DBusGMainLoop(set_as_default=True)
bus = dbus.SystemBus() #should connect to system bus instead of session because the former is where the incoming signals come from
bus.add_signal_receiver(callback, path='/com/nokia/phone/SMS', dbus_interface='Phone.SMS', signal_name='IncomingSegment')
gobject.MainLoop().run()

if __name__ == '__main__':
import time

def schedule_task(schedule, fn, *args):
import sched
s = sched.scheduler(time.time, time.sleep)
startTime = time.mktime(time.strptime(schedule, '%b %d %H:%M %Y'))
s.enterabs(startTime, 0, fn, args)
s.run()

import getopt, sys
try:
opts, args = getopt.getopt(sys.argv[1:],"hlt:", ["help","listen","time="])

except getopt.GetoptError, err:
# print help information and exit:
print str(err) # will print something like "option -a not recognized"
usage()
sys.exit(2)
listening = False
timeofday = ''
for opt, arg in opts:
if opt in ("-h", "--help"):
usage()
sys.exit()
elif opt in ("-l", "--listen"):
listening = True
elif opt in ("-t", "--time"):
timeofday = arg
else:
assert False, "unhandled option"

number = args[0]
msg = args[1]
if msg != '':
if timeofday == '':
sendmessage(number, msg)
else:
today = time.strftime('%b %d x %Y', time.localtime())
schedule = today.replace('x', timeofday)
schedule_task(schedule, sendmessage, number, msg)
if listening:
listen()
</source>

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

<source lang="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')
</source>

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===

<source lang="python">
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."
</source>

Credits: took code from [http://stackoverflow.com/questions/69645/take-a-screenshot-via-a-python-script-linux here].

There is also a way using PyQt:
<source lang="python">
import sys
import time
from PyQt4.QtGui import QPixmap, QApplication
app = QApplication(sys.argv)
file = "/home/user/MyDocs/.images/Screenshots/Screenshot-"+time.strftime("%Y%m%d")+"-"+time.strftime("%H%M%S")+".png"
QPixmap.grabWindow(QApplication.desktop().winId()).save(file, 'png')
</source>

===Make an "Email Style" notification dialog===

<source lang="python">
import dbus

bus = dbus.SessionBus()
proxy = bus.get_object('org.freedesktop.Notifications', '/org/freedesktop/Notifications')
interface = dbus.Interface(proxy,dbus_interface='org.freedesktop.Notifications')
interface.Notify('Notification', 0, 'control_bluetooth_paired', 'Testing 123', 'Hello World', [], {}, 0)
</source>

Credits: MohammadAG (on irc).

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

DbusScripts

2011-09-09T05:37:02Z

213.240.181.249: add wait for dbus, otherwise it may fail

[http://www.cobb.uk.net/770/#dbus-scripts dbus-scripts] is a daemon that can execute a command when various actions occurs on D-Bus. Some D-Bus signals you can watch for are :

* keyboard slide
* battery full, low or empty
* connection or disconnection from a network
* sms or phone call arriving
* desktop started (ie. after boot is completed)
* bnep or usb network started or stopped (use to configure or run firewalls etc)

You can find dbus-scripts in [[extras-devel]] (so be careful, your [[Nokia N900|N900]] could crash).

There's some documentation in the [http://www.cobb.uk.net/770/dbus-scripts-example dbus-scripts config file]

There's also a configurator program [http://maemo.org/packages/view/dbus-scripts-settings/ dbus-scripts-settings] written by Matan Ziv-Av. You can use dbus-scripts-settings settings to configure dbus-scripts or just to browse.
Thanks to Graham and Matan.

== Configuration ==

=== Basic configuration ===

Configuration files for dbus-scripts are in <code>/etc/dbus-scripts.d</code> and you can find some documentation in <code>/etc/dbus-scripts.d/dbus-scripts-example</code>:

# Example of dbus-scripts control file
#
# Each line of these files represents a filter to call a script.
# Tokens are separated by white space.
# First token on line is the script to execute.
# Subsequent tokens are filters to match arguments from dbus message.
# Filters are matched like shell wildcards (using fnmatch(3)).
# If a filter is specified (even if it is *), the corresponding argument
# must be present in order to get a match.
#
# First argument is sender
# Second argument is destination
# For SIGNAL and METHOD_CALL, third argument is interface
# For SIGNAL and METHOD_CALL, fourth argument is member
# Other arguments depend on the message
#
# Example: to act on WLAN interface state changes use:
#/some/script * * com.nokia.icd status_changed * WLAN_INFRA
# In /some/script, $5 will be the interface name and $7 the new state (IDLE, CONNECTED, etc.)

* this rule will match all wlan network events

/some/script * * com.nokia.icd status_changed * WLAN_INFRA

* this one will match all events for wlan network id of 91f493fb-7c89-4fc6-ac2c-b822923dde45, it's mine

You can find the wlan id with the command
gconftool-2 -R /system/osso/connectivity/IAP

/some/script * * com.nokia.icd status_changed 91f493fb-7c89-4fc6-ac2c-b822923dde45 WLAN_INFRA

* this one will match only the CONNECTED (wifi works) dbus event for my wlan network :

/some/script * * com.nokia.icd status_changed 91f493fb-7c89-4fc6-ac2c-b822923dde45 WLAN_INFRA CONNECTED

=== dbus-scripts-settings ===

There's also a configurator program [http://maemo.org/packages/view/dbus-scripts-settings/dbus-scripts-settings] written by Matan Ziv-Av. You can use dbus-scripts-settings settings to configure dbus-scripts or just to browse.

:As of 2010-07-16, dbus-scripts-settings is missing a dependency on package 'gnome-python-dev'. If the program crashes and at command line you get the error

<source lang="text">
Traceback (most recent call last):
File "/usr/bin/dbus-scripts-settings", line 5, in <module>
from gnome import gconf
ImportError: No module named gnome
</source>

:then the fix is to install gnome-python-dev. [[User:magick777|magick777]] 14:09, 16 July 2010 (UTC)

=== dbus-scripts daemon options ===

==== Running dbus-scripts on the session bus ====

By default, the dbus-scripts daemon listens on the system message bus, which reports system events but not those from the user session. If you want to access events such as an application being launched, you'll need to configure the daemon to listen to the session bus as well. You'll probably want to run a second instance of dbus-scripts without breaking the one on the system bus.

Ignore <code>/etc/init.d/dbus-scripts</code> and <code>/etc/default/dbus-scripts</code> as these would seem to have been superseded by upstart. Make a copy of <code>/etc/event.d/dbus-scripts</code> as <code>/etc/event.d/dbus-scripts-session</code> and edit it so your <code>/etc/event.d/dbus-scripts-session</code> will look like this:

<source lang="text">
Nokia-N900:~# cat /etc/event.d/dbus-scripts
description "dbus-scripts-session"
author "Graham Cobb <g+770@cobb.uk.net>"

start on started hildon-desktop
stop on stopping hildon-desktop

console none

pre-start script
/usr/bin/run-standalone.sh /usr/sbin/waitdbus session
end script

exec run-standalone.sh /usr/sbin/dbus-scripts --session

respawn
</source>

and you can then configure dbus-scripts with statements such as

<source lang="text">
#:Browser launched
/usr/bin/onbrowser * * com.nokia.HildonDesktop.AppMgr LaunchApplication browser
</source>

to react to, in this example, the browser being started.

==== The incredibly useful --debug flag ====

The --debug flag is essential for looking at what's going on if you plan to write your own scripts. Run "dbus-scripts --debug" in a terminal and then perform whatever actions on the phone, to see all the events you can process using dbus-scripts. To see events on the session bus, make that "dbus-scripts --debug --session" (but you will need to run it through <code>run-standalone.sh</code>). For example:

<pre>
sudo dbus-scripts --debug
sudo /usr/bin/run-standalone.sh dbus-scripts --debug --session
</pre>

== Usage, tips and tricks ==

dbus-scripts does not reread edited configuration automatically. After editing (or creating/removing) a configuration file, you need to restart it.

On N900 it can easily be done with
killall dbus-scripts
since it is then restarted by upstart. On 770/N800/N810, use
/etc/init.d/dbus-scripts restart

The package dbus-scripts-settings contains a script <code>logit.sh</code> which simply logs its parameters to the file <code>/media/mmc1/logit.log</code>. If you want to find out if some event generates D-Bus events, and what configuration line to use for it, create a file in <code>/etc/dbus-scripts.d/</code> containing:

/usr/bin/logit.sh *

And generate the event. Reading the log file will show you all the D-Bus activity.

== Limitations ==

For the moment dbus-scripts will only pass simple D-Bus type arguments like string, boolean and int32 et uint32 to your scripts. You will miss variant, array and all other complex type arguments. So if you want to play, for example, with text of received SMS, you can't yet use dbus-scripts as the text is an array of bytes.

== Some scripts ==

Here are some things you can do, if you have others, add them. Those examples aren't rocket science and I've stolen some ideas from here and there on web.

=== when connect on my wifi home network register only SIP and turn on noisy ring ===

When I come back home I want my SIP call redirected to my mobile phone and the phone ring turn on and when I leave I want my ring turn off so I wait for D-Bus event on my home wifi network and register/unregister SIP and turn on/off the ring.

I use this dbus-scripts config file :

'''/etc/dbus-scripts.d/athome'''
/home/user/bin/athome * * com.nokia.icd status_changed * WLAN_INFRA

and this script to register/unregister SIP and turn on/off the ring.

'''/home/user/bin/athome'''
<source lang="python">
#!/usr/bin/python

import dbus
import sys
import re
import telepathy

wifi = '91f493fb-7c89-4fc6-ac2c-b822923dde45'

# /home/user/bin/w32g * * com.nokia.icd status_changed * WLAN_INFRA *

wifi_id,state = sys.argv[5],sys.argv[7]

# if we are not on the good wifi network we do nothing and exit
if wifi and not re.search(wifi_id, wifi, re.IGNORECASE):
sys.exit(0)

bus = dbus.SessionBus()
account = bus.get_object('org.freedesktop.Telepathy.AccountManager',
'/org/freedesktop/Telepathy/Account/sofiasip/sip/_309517129090')
profile = bus.get_object('com.nokia.profiled', '/com/nokia/profiled')

def change_state(prof, presence_const, presence_text):
profile.set_profile(prof, dbus_interface='com.nokia.profiled')
account.Set('org.freedesktop.Telepathy.Account', 'RequestedPresence', \
dbus.Struct(( dbus.UInt32( presence_const) , presence_text, ""), signature='uss'),
dbus_interface='org.freedesktop.DBus.Properties')

if state == "CONNECTED":
print "available"
change_state('general', telepathy.constants.CONNECTION_PRESENCE_TYPE_AVAILABLE, 'available')
elif state == "IDLE":
print "offline"
change_state('silent', telepathy.constants.CONNECTION_PRESENCE_TYPE_OFFLINE, 'offline')
else:
sys.exit("Usage: %s (start|stop)" % sys.argv[0])
</source>

=== turn to 2g when connected to wifi network ===

There's already an [[Fcron#Auto_2G_with_WiFi|alternative method with fcron]]. Here is a D-Bus method :

'''/etc/dbus-scripts.d/w32g'''
/home/user/bin/w32g.py * * com.nokia.icd status_changed * WLAN_INFRA

Installation documentation is at the beginning of the script and configuration documentation is at the beginning of the configuration file:

'''/home/user/bin/w32g.py'''
<source lang="python">
#!/usr/bin/python

import sys
import os
import ConfigParser
import re

# You need to install dbus-scripts (BE CAREFUL, it's a devel package)
#
# as root you need to create a file /etc/sudoers.d/w32g
# with this line :
# user ALL = NOPASSWD: /bin/ping
# and run the command update-sudoers because only root can use ping
#
# always as root and you need to create another file
# /etc/dbus-scripts/w32g with the following line :
#
# /home/user/bin/w32g * * com.nokia.icd status_changed * WLAN_INFRA *
#
# and copy this script in /home/user/bin/w32g

conf_file = '/home/user/.w32g.conf'

config = { 'message_on_idle': '3G cellular mode set',
'message_on_connected': '2G (GSM) cellular mode set',
'connection_test': 'sudo /bin/ping -c 1 www.google.com',
'change_on_idle': 'true',
'change_to_dual': 'true',
'wifi': ''
}

config_parser = ConfigParser.SafeConfigParser()

try:
config_parser.read(conf_file)
for item in config_parser.items('w32g'):
config[ item[0] ] = item[1]
except ConfigParser.NoSectionError:
pass

def to_bool(string):
if re.search('true', string, re.IGNORECASE):
return True

config['change_on_idle'] = to_bool(config['change_on_idle'])
config['change_to_dual'] = to_bool(config['change_to_dual'])

wifi_id,state = sys.argv[5],sys.argv[7]

# if we are not on the good wifi network we do nothing and exit
if config['wifi'] and not re.search(wifi_id, config['wifi'], re.IGNORECASE):
sys.exit(0)

dbus_wifi = "dbus-send --system --type=method_call --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.set_selected_radio_access_technology";

dbus_notif = "dbus-send --system --type=method_call --print-reply --dest=org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.SystemNoteInfoprint";

if state == 'CONNECTED':
# we verified that the connection works
if config['connection_test']:
ret = os.system(config['connection_test']);
else:
ret = 0
if ret == 0:
os.system(dbus_wifi + " byte:1");
os.system(dbus_notif + " string:'" + config['message_on_connected'] + "'")

elif state == 'IDLE' and config['change_on_idle']:
dual = "2"
if config['change_to_dual']: dual = "0"
print dual
os.system(dbus_wifi + " byte:" + dual);
os.system(dbus_notif + " string:'" + config['message_on_idle'] + "'")
</source>

'''/home/user/.w32g.conf'''
<pre>
[w32g]

### the comment reflect the default configuration
### true is true (case insensitive), everything else is false

### the command used to test the wifi connection before downgrading to 2g
### if you don't want to do test just delete after =
# connection_test = sudo /bin/ping -c 1 www.google.com

### notification message when going to 3g
# message_on_idle = 3G cellular mode set
### notification message when going to 2g
# message_on_connected = 2G (GSM) cellular mode set

### shall we go back to 3g when wlan disconnect ?
#### if you want to have false just delete after =
# change_on_idle = true
### shall we go back to dual or 3g ?
# change_to_dual = true

### if you want go to 2g only when connected to some wlan you can add their wlan id here
### you can find the wlan id using the command
### gconftool-2 -R /system/osso/connectivity/IAP
### For example :
### wifi = 91f493fb-7c89-4fc6-ac2c-b822923dde45 9ee5dd55-9a32-4ee9-9131-c464ad31d907
# wifi =
</pre>

=== Enable tethering when connecting to Bluetooth PAN ===

Tethering is a bit of a hassle in Maemo. Most people refer to JoikuSpot, which is definitely the most comfortable solution, but it's not free. So, why not use builtin (or easily installable) functionality to use the N900 as a modem?

For this script to work, you need to have at least bluetooth-dun and iptables installed. Possibly other packages too, please test and correct.

'''/etc/dbus-scripts.d/tethering'''
/usr/bin/tethering.sh * * org.freedesktop.Hal.Manager DeviceAdded
/usr/bin/tethering.sh * * org.freedesktop.Hal.Manager DeviceRemoved

'''/usr/bin/tethering.sh'''
<source lang="bash">
#!/bin/sh
#
# /usr/bin/tethering.sh
#
# Enable tethering on USB network and Bluetooth PAN.
#
# Note that the INETDEV must be up and running when this script is
# started, or forwarding will not be enabled.
# Having tethering on multiple devices concurrently is possible,
# but forwarding will be disabled once the first device disconnetcs.
# A better check is necessary.
#
# Put this into /etc/dbus-scripts/tethering :
# /usr/bin/tethering.sh * * org.freedesktop.Hal.Manager DeviceAdded
# /usr/bin/tethering.sh * * org.freedesktop.Hal.Manager DeviceRemoved
#
# dbus-scripts doesn't give us the event path, so we have to use a more
# convoluted method of getting the network interface.
#

EVENT="$4"
UDI="$5"
HALDEV="$(echo $UDI | sed 's#.*/$[0-9a-zA-Z_]*$#\1#')"
LOG="/tmp/tethering.log"
INETDEV="gprs0"
RUNFILE="/var/run/tethering.$HALDEV.pid"
IFACEFILE="/var/run/tethering.$HALDEV.iface"

if [ "$EVENT" = "DeviceAdded" ]; then
IFACE=$(hal-get-property --udi $UDI --key net.interface)
case $IFACE in
bnep0 )
IF_ADDRESS=192.168.254.254
IF_RANGE=192.168.254.1,192.168.254.254
;;
usb0 )
IF_ADDRESS=192.168.253.254
IF_RANGE=192.168.253.1,192.168.253.254
;;
* )
exit 0
;;
esac

echo "$(date) Enabling tethering on interface $IFACE" >> $LOG
echo "$IFACE" > $IFACEFILE
ifconfig "$IFACE" "$IF_ADDRESS"
/sbin/modprobe ipt_MASQUERADE
/usr/sbin/iptables -t nat -A POSTROUTING -o $INETDEV -j MASQUERADE
start-stop-daemon -S -p "$RUNFILE" -m -b -x /usr/sbin/dnsmasq -- -k -I lo -i "$IFACE" -a $IF_ADDRESS -z -F $IF_RANGE,3600
echo 1 > /proc/sys/net/ipv4/conf/$IFACE/forwarding
echo 1 > /proc/sys/net/ipv4/conf/$INETDEV/forwarding
fi

if [ "$EVENT" = "DeviceRemoved" ]; then
if [ ! -f "$IFACEFILE" ]; then
exit 0
fi
IFACE="$(cat $IFACEFILE)"
rm "$IFACEFILE"
echo "$(date) Disabling tethering on device $IFACE" >> $LOG
echo 0 > /proc/sys/net/ipv4/conf/$INETDEV/forwarding
start-stop-daemon -K -p "$RUNFILE" -x /usr/sbin/dnsmasq
/usr/sbin/iptables -t nat -D POSTROUTING -o $INETDEV -j MASQUERADE
fi

exit 0
</source>

=== Set MSN (pecan) to stay offline when disconnected ===

Since MSN allows only one client connection at a time, signing into MSN from the N900 disconnects it on my desktop PC, and vice versa.

Pidgin on my desktop PC handles this gracefully by disabling the account until I manually connect it. msn-pecan, on the other hand, helpfully auto-reconnects on its own authority and fails to respect my disabling auto-connect via mc-tool; if the requested status remains as "available", it reconnects, and that disconnects Pidgin on my desktop again. Grr.

You need an instance of dbus-scripts '''on the session bus''' for this one (see above), then you can do the following:

==== /etc/dbus-scripts.d/dbus-scripts-settings ====
<source lang="text">
#:MSN (pecan) disconnected (session bus)
/usr/bin/offmsn * * org.freedesktop.DBus ReleaseName org.freedesktop.Telepathy.Connection.pecan.msn_pecan.*
</source>
==== /usr/bin/offmsn ====

<source lang="bash">
#!/bin/sh
# If we got disconnected from MSN (eg by signing in via Pidgin on desktop PC) then set it offline until further notice
mc-tool list | grep "pecan/msn" | awk {'print "mc-tool request "$1" offline"'} | sh
</source>

== Links to other scripts ==

=== automatically register on public wifi network when connected ===

You can find a script [http://talk.maemo.org/showpost.php?p=555757&postcount=6 in this post on tmo]

== Thanks ==

Thanks to Graham Cobb for dbus-scripts and Matan for dbus-scripts-settings

[[Category:Software]]
[[Category:Power users]]

LED patterns

2010-02-20T19:09:31Z

213.240.181.249: /* Community-Made Patterns */

== N800 ==

The N800 has a single-colour (blue) LED behind the dpad.

== N810 ==

The N810 has an RGB LED.

== N900 ==

=== File Location ===

The file defining patterns can be found in
/etc/mce/mce.ini

An application ([http://talk.maemo.org/showthread.php?t=27818 mcedit]) for modifying LED patterns was written for the n8x0, but this will not work with the n900 due to the new mce.ini format.

=== Pattern Format ===
The patterns are broken down as follows:

:<tt>PatternName=Priority;ScreenOn;Timeout;LEDsToMap;Engine1Pattern;Engine2Pattern</tt>

==== Priority ====

0-255, 0 is highest, 255 is lowest.

Since currently only a single pattern at a time can be displayed, this is used to assign importance to the LED patterns. Although only a single LED pattern can be displayed at any time, multiple patterns may be active, the pattern with the highest priority being displayed.

A common example of this is where the n900 is on charge, the battery is full (starting PatternBatteryFull with a priority of 40), and an SMS message is received (PatternCommunicationSMS with a priority of 30). On receipt of the SMS, the LED begins to display the flashing blue led of an SMS. Once that SMS has been dismissed, the green LED of the full battery notification is again displayed.

==== ScreenOn ====

* 0: only show pattern when the display is off
* 1: show pattern even when the display is on
* 2: only show pattern when the display is off, including acting dead
* 3: show pattern even when the display is on, including acting dead
* 4: only show pattern if the display is off, or if in acting dead
* 5: always show pattern, even if LED disabled

==== TimeOut ====

This is the time-out of the LED pattern in seconds. 0 for infinite, i.e. until the notification is dismissed.

If this is set to 20, the pattern will display for 20 seconds, and then stop.

==== LEDsToMap ====

There are two engines that can be used to make custom LED patterns.<ref name="engines">Actually there are three, but the third engine is used exclusively for the keyboard LED.</ref>

r, g, or b maps the corresponding colour channel to Engine 1.

R, G, or B maps the corresponding colour channel to Engine 2.

For example, "rG" maps the red channel to Engine 1, and the green channel to Engine 2.

You should avoid mapping the same channel to both engines, for example "rR", "gG" or "bB"

==== Engine Pattern ====

This is a series of text that describes the speed and intensity of changes in the LED(s) beign managed by that particular engine. See below for a breakdown of the patterns. Each can be at most 16 commands long.

=== Lysti Format Engine Patterns and Commands ===

The LED patterns are of the form
:<tt>9d8040007f007f0040ff7f007f000000</tt>

Breaking this down for ease of reading we get a list of 8 commands, each of which is four characters long.
:<tt>9d80 4000 7f00 7f00 40ff 7f00 7f00 0000</tt>

==== 9d80 - Refresh Engine Multiplexor ====

This is to be used as the first command of every pattern). If this is excluded from the pattern, the led won't flash.

==== 40xx - Set channel brightness ====

Where xx are two hexadecimal digits, e.g. 00 (for a brightness of 0) or ff (for a brightness of 255).

==== xxyy - Adjust channel brightness ====

Increment or decrement the channel brightness over a period of time (xx) and a number of steps (yy).

Where xx and yy are hexadecimal digits

xx - Time (per step?)

yy - Number of steps

The following rules apply to these:
* If xx is even, the steps are increment steps and brightness will increase.
* If xx is odd, the steps are decrement steps and brightness will decrease.
* If xx is between 02 and 3f, a short step time is used (granularity 0.49ms)
* If xx is between 42 and 7f, a long step time is used (granularity 15.6ms)
* yy can be any value between 00 and ff (0 to 255)
* Pauses can be achieved by using 00 steps, e.g. 7f00 where, where the 7f is how long each step takes and 00 is how many increment steps to take.

The mce.ini instructions (/etc/mce/mce.ini) also state that
:Two consecutive increment/decrement sequences are needed to cover the entire range from 0-255
However I believe this is a throwback to the older patterns, and the full range of 00 to ff is available in a single step for the number of steps, since whether these are increment or decrement steps are now handled through use of even or odd xx values.

==== 0000 - Jump to start ====

Jump to the start of the pattern for this channel. You will see this at the end of most repeating patterns.

This command may not actually be needed to make the pattern repeat. If this is removed, the pattern will repeat anyway, although it's useful to have it there as an explicit command to repeat for clarity. If you wanted a pattern to run once and then terminate you would use the c000 command.

==== c000 - End pattern execution ====

The pattern is terminated without repeating. It is important to note here that although that pattern has stopped, it is still active until the Timeout time has passed. As a consequence of this any higher priority patterns (patterns with a lower priority value, since 0 is the highest and 255 is the lowest) will not be displayed until the pattern has fully expired. In the case that the timeout is 0, it will not display until the notification is dismissed.

==== Sending and receiving engine triggers ====

Further complexity in patterns can be added through use of triggers. This is especially useful if we want to synchronise the two engines in time, for example to wait until the LED has turned red before turning it immediately to green. Rather than waste time with steps doing nothing, we can simply wait for a trigger to be received from the other engine.

The following pattern does exactly that:
:<tt>PatternTest=29;1;0;rG;9d80400008ffe0044000c000;9d80e08040ffc000</tt>

===== e002, e004, e008 - Send engine trigger =====

e002 - Send trigger to engine 1

e004 - Send trigger to engine 2

e008 - Send trigger to engine 3 (used by keyboard backlight)

A signal is sent from the current engine to signal another engine.

Although the trigger information for engine 3 is listed we have no control over the keyboard LED, so it has no effect. Attempting to add a pattern for engine 3 after the pattern for engine 2 causes the pattern to no longer function.

===== e080, e100, e200 - Wait for engine trigger =====

e080 - Wait for trigger from engine 1

e100 - Wait for trigger from engine 2

e200 - Wait for trigger from engine 3 (used by keyboard backlight)

Although the trigger information for engine 3 is listed we have no control over the keyboard LED, so it has no effect. Attempting to add a pattern for engine 3 after the pattern for engine 2 causes the pattern to no longer function.

=== Default LED Patterns for Nokia N900 ===

PatternError=0;5;0;r;9d8040007f007f0040ff7f007f000000;9d800000
PatternDeviceOn=254;0;0;rgb;9d804000422043207f100000;9d800000
PatternDeviceSoftOff=253;0;0;rg;9d804000423f433f7f100000;9d800000
PatternPowerOn=9;3;0;rgb;9d80400042ff02ffc000;9d800000
PatternPowerOff=10;3;0;rgb;9d80400001ff43ff7f007f00c000;9d800000
PatternCommunicationCall=30;1;0;b;9d80400002ff03ff02ff03ff71080000;9d800000
PatternCommunicationIM=30;1;0;b;9d80400002ff03ff02ff03ff71080000;9d800000
PatternCommunicationSMS=30;1;0;b;9d80400002ff03ff02ff03ff71080000;9d800000
PatternCommunicationEmail=30;1;0;b;9d80400002ff03ff02ff03ff71080000;9d800000
PatternCommonNotification=30;1;0;b;9d80400002ff03ff02ff03ff71080000;9d800000
PatternWebcamActive=20;1;0;r;9d80400004ffc0000000;9d800000
PatternBatteryCharging=50;4;0;rg;9d804000427f0d7f7f007f0042000000;9d800000
PatternBatteryFull=40;4;0;g;9d80407f0000;9d800000

=== Community-Made Patterns ===
''Please note that these patterns should all be on one line.''
''They can also be used for any notification.''

A traffic-light battery charging pattern, courtesy of [http://talk.maemo.org/showthread.php?p=512430#post512430 blue_led]
PatternBatteryCharging=50;4;0;Rg;9d80407f7f00e0047f0040007f007f007f00407f7f00e0047f007f000000;9d804000e080407fe0800000

A police-siren style pattern, idea by [http://talk.maemo.org/showthread.php?p=499305#post499305 mihapodb].
PatternCommunicationEmail=30;1;0;rB;9d8040ff7f00e00440007f000000;9d80e08040ff7f0040000000

Cehteh's patterns with some comments

Slow dark glowing in cyan, never goes fully off, so you can locate the device in the dark:
PatternDeviceOn=254;0;0;gb;9d804001620863087f007f007f007f007f007f007f007f007f007f007f000000;9d800000

Similar to the above but gets brighter in yellow:
PatternBatteryCharging=50;3;0;rg;9d804001427f0d7f7f007f0042000000;9d800000

Same as PatternDeviceOn, but white:
PatternBatteryFull=40;3;0;rgb;9d804001620863087f007f007f007f007f007f007f007f007f007f007f000000;9d800000

White, bright flashing, must be enabled in 'LEDPatterns=':
PatternExample=42;1;30;rgb;9d8040007f007f0040ff42000000;9d800000

=== Step by step instructions ===

* Open terminal
* Gain [[Root access]]
* Make a backup (not necessary!) from original mce.ini -file, for example:
cp /etc/mce/mce.ini /etc/mce/mce.ini_old
* Open /etc/mce/mce.ini with a text editor (nano, vim, leafpad...)
* Search for a line:
[LEDPatternLystiRX51]
* Make your changes to the lines below
* Save
* Restart mce -process. Either reboot or type to terminal:
initctl stop mce; sleep 2; initctl start mce

Please note: restarting mce several times in 2 minutes will cause the n900 to think there is a problem with mce, and not restart it. The initctl program will inform you of this. When it does, simply wait a while before trying again.

=== Low Level ===

The N900 has a LP5521<ref name="lp5521-spec">http://www.national.com/pf/LP/LP5521.html</ref> <ref name="lp5521-driver">http://mxr.maemo.org/fremantle/source/kernel/drivers/i2c/chips/lp5521.c</ref> programmable three channel controller LED Driver which handles the leds.
(actually it has a LP5523 it seems <ref name="lp5523-spec">http://www.national.com/pf/LP/LP5523.html</ref> <ref name="leds-lp5523-driver">http://mxr.maemo.org/fremantle/source/kernel/drivers/leds/leds-lp5523.c</ref>, which has 3 engines like LP5521 but can drive 9 LEDs via a multiplexer)

The controller can be programmed via "/sys/class/i2c-adapter/i2c-2/2-0032" (FIXME: is this stable?). In that directory there are three files corresponding to the three channels: engine1_mode, engine2_mode and engine3_mode. Each file "stores" one of "run", "load", "disabled" (it seems that there is another mode "direct" but it doesn't work):
* run: The program runs
* disabled: The channel is disabled - not running
* load: In that state, there are two more files in that directory:
** engine1_leds is in the form "0000rgb00" (9 digits), where rgb control which leds should participate
** engine1_load accepts a string as specified above (e.g. 9d804000427f0d7f7f007f0042000000).
After that, when the state is changed to "run", the program will be ran by the controller.

In order for the leds to work, the led_current of the appropriate leds need to be set to non-zero values. This is accomplished by writing to files leds:lp5523:[bgr]/led_current under the same directory. Perhaps (?) not or values are suitable.

NOTE: There must be a delay (how much? The specs of LP5521 mentions it) between writes to sysfs files.

{{Reflist}}

[[Category:N900 Hardware]]
[[Category:Power users]]