From GnokiiWiki
Jump to: navigation, search


Supported phones

You can assume that your phone is supported, however you will get very limited functionality with gnokii if the phone doesn't support Nokia's FBUS protocol and if it supports only a small subset of AT commands (this is the case of Windows Mobile phones, iPhone, Symbian 3rd Edition phones and probably Blackberry) in which case you might be able to access contacts and events using the SyncML protocol. See also Known limitations.

The sample gnokiirc has extensive comments and lists all available parameters, but in most cases you only need to set model, connection and port. The file to do configure gnokii is located in $XDG_CONFIG_HOME/gnokii/config (in most cases $HOME/.config/gnokii/config) or in $XDG_CONFIG_DIRS/gnokii/config (mostly /etc/xdg/gnokii/config). Legacy versions were configured in $HOME/.gnokiirc or /etc/gnokiirc, these files won't be read without further actions in current versions.

Remember that every config line needs to be within a particular section. If in doubt place is into [global] section and refer to the sample gnokiirc.

There is also an experimental configuration assistant named gnokii-configure written in python+glade in utils/.


If you have a fairly modern phone you should use the following model setting in your config file:

If you have some older Nokia (like 6210) phone you may try using its brand name, eg. model = 6210.

For supported Smart Card readers use model = APDU.



For Bluetooth connection it is suggested to use connection = bluetooth and port = aa:bb:cc:dd:ee:ff (use your phone's Bluetooth address) and a suitable value for rfcomm_channel = ? (it is autodetected if omitted, but connection is slightly faster if you explicitly provide a channel; you can look at the debug output or use sdptool search SP or sdptool search DUN or sdptool browse to find the right channel). As an alternative you may use rfcomm to setup the communication and use connection = serial and port = /dev/rfcomm0 (or whatever device you created, see man rfcomm).


For infrared connection it is suggested to use connection = irda and the port parameter is ignored. Use the irda_string = parameter to specify a device name if you need to differentiate among several devices in range. As an alternative you may use irattach to setup the communication and use connection = serial and port = /dev/ircomm0 (or whatever device you created, see man irattach).

USB / RS-232

For RS-232 and USB connections, the name depends on type of cable and phone model. Some values are connection = serial to use the AT protocol and connection = dku2libusb to use the FBUS protocol (if supported by cable and phone).

Smartcard Reader

For supported Smart Card readers use connection = APDU.


For USB connections, port name depends on type of cable: some cables create a /dev/ttyACM0, others create a /dev/ttyUSB0. When using connection = dku2libusb, port = 1 chooses the first phone, port = 2 the second, and so on. See /var/log/messages and Cables for details.

For Bluetooth and infrared connections see above.

On Windows the port parameter is most likely a virtual COM port created by the drivers, eg. port = COM1: or port = \\.\COM10 for numbers greater than 9 or a Bluetooth address.

For pcsc connections, port = can be the name of a reader or a number that identifies a reader configured in reader.conf.

Tested phones

See the Configuration category page for a list of all documented configurations.

If your phone model is not listed below, it will probably work with one of the settings above.

From Nokia

Older Nokia phones

From other vendors

Related pages