forsi.it a spotless world

removed truncated sentence

← Older revision Revision as of 20:50, 10 August 2010 (One intermediate revision not shown)Line 12: Line 12: : (with <code>LC_MESSAGE=en_US.UTF8</code> the program output and the error messages will be in English) : (with <code>LC_MESSAGE=en_US.UTF8</code> the program output and the error messages will be in English) * if you get a SEGFAULT, a backtrace is needed (refer to [[segfault]]) * if you get a SEGFAULT, a backtrace is needed (refer to [[segfault]]) -* if you get encoding errors always use the git version and attach to your report the +* if you get encoding errors always use the git version   * if you are using a Nokia do your tests also with the [[fake driver]] * if you are using a Nokia do your tests also with the [[fake driver]]  +* if you get communication errors, kernel version (and libusb version when using [[dku2libusb|connection = dku2libusb]]) Send resulting report to gnokii-users (at) nongnu.org Send resulting report to gnokii-users (at) nongnu.org Dforsi

--phone: add a valid command to the example

← Older revision Revision as of 14:02, 10 August 2010 Line 13: Line 13: Select a different phone section (by default the global section is used). Select a different phone section (by default the global section is used). -The default section is used if <code>phone_section</code> is an empty string (ie. "") or this option is omitted.+The default section is used if <code>phone_section</code> is an empty string (ie. "") or if this option is omitted. For example, if in your configuration file you add: For example, if in your configuration file you add: Line 21: Line 21:   connection = dku2libusb   connection = dku2libusb you can call: you can call: -  gnokii --phone myconfig+  gnokii --phone myconfig --identify Dforsi

Add troubleshooting section

← Older revision Revision as of 09:37, 8 August 2010 Line 104: Line 104: You'll find the USB compatibility table at [http://europe.nokia.com/nokia/0,,79898,00.html Nokia site]. You'll find the USB compatibility table at [http://europe.nokia.com/nokia/0,,79898,00.html Nokia site].  +  +== Troubleshooting ==  +  +If you got communication timeout it means that gnokii does not receive any answer from the phone. In general there are two major reasons for that:  +* the cable is not supported by the operating system (see above)  +* the port is used by some other program or driver (see also http://wiki.gnokii.org/index.php/DKU2) Pkot

fake driver now supports gnokii --savesms, smsd and xgnokii

← Older revision Revision as of 14:32, 7 August 2010 (One intermediate revision not shown)Line 2: Line 2: It duplicates some functionality of the [[atgen driver|AT driver]] but prints commands to stdout instead of sending them to a phone. It duplicates some functionality of the [[atgen driver|AT driver]] but prints commands to stdout instead of sending them to a phone. -Only a subset of libgnokii commands is currently implemented in the fake driver.+Only a subset of libgnokii commands is currently implemented in the fake driver:  +* since 0.6.29 it supports also --savesms (it prints to stdout)  +* since 0.6.30 it supports also smsd (sending and receiving both the internal and the file SMS) and partially xgnokii === Configuration === === Configuration === Line 30: Line 32: sms_inbox = /tmp/sms sms_inbox = /tmp/sms </pre> </pre> -Then create the <code>/tmp/sms</code> directory with some files containing valid PDUs in HEX format, as printed by <code>--sendsms</code> or by <code>--getsms</code> when using the [[AT driver]]; file names are ignored, only the order as seen by <code>readdir()</code> is important.+Then create the <code>/tmp/sms</code> directory with some files containing valid PDUs in HEX format; PDU's can be obtained using <code>--sendsms</code> with the fake driver, or read in the [[debug output]] printed by <code>--sendsms</code> or by <code>--getsms</code> when using the [[AT driver]]; file names are ignored, only the order as seen by <code>readdir()</code> is important. For more examples see the tests in the <code>[http://git.savannah.gnu.org/cgit/gnokii.git/tree/testsuite testsuite]</code> directory which are done using the fake driver. For more examples see the tests in the <code>[http://git.savannah.gnu.org/cgit/gnokii.git/tree/testsuite testsuite]</code> directory which are done using the fake driver. Dforsi

← Older revision Revision as of 12:18, 7 August 2010 Line 20: Line 20: * [http://qgnokii.sourceforge.net/ QGnokii] by Piotr Jedryczak, alternative frontent for gnokii written in Qt; client and daemon parts are separated * [http://qgnokii.sourceforge.net/ QGnokii] by Piotr Jedryczak, alternative frontent for gnokii written in Qt; client and daemon parts are separated * [http://xanadux.cvs.sourceforge.net/viewvc/xanadux/qomunicator/ Qomunicator], Qt frontend communicating with libgnokii over unix socket based proxy; targetted at MDA devices supported by [http://wiki.xda-developers.com/index.php?pagename=Xanadux Xanadux] project * [http://xanadux.cvs.sourceforge.net/viewvc/xanadux/qomunicator/ Qomunicator], Qt frontend communicating with libgnokii over unix socket based proxy; targetted at MDA devices supported by [http://wiki.xda-developers.com/index.php?pagename=Xanadux Xanadux] project -* [http://www.developershome.com/sms/smsLinux.asp SMS] handling with Linux, article+* [http://www.developershome.com/sms/smsLinux.asp SMS] handling with Linux and gnokii, article at Developer's Home * [http://libsyncml.opensync.org/ SyncML library] * [http://libsyncml.opensync.org/ SyncML library] * [http://tuxmobil.org/ TUX Mobil] * [http://tuxmobil.org/ TUX Mobil] Pkot

New user account

New page

Shajis001

New user account

New page

EmelinaBertman

Add more details

← Older revision Revision as of 20:55, 15 July 2010 Line 1: Line 1: -Before reporting a problem with gnokii make sure that the problem still exists+Before reporting a problem with gnokii make sure that: -with [http://www.gnokii.org/git.shtml current version].+* it isn't a known problem (use a search engine)  +* it still exists in the [http://www.gnokii.org/git.shtml current development version]  +* you can explain how to reproduce it -When you report a problems please attach the following information:+Your report will be useless without the following information: * phone model and how do you connect (Bluetooth/IrDa/cable with its type) * phone model and how do you connect (Bluetooth/IrDa/cable with its type) * the values of the configuration parameters <code>model</code>, <code>connection</code> and <code>port</code> * the values of the configuration parameters <code>model</code>, <code>connection</code> and <code>port</code> -* gnokii version (<code>gnokii --version</code>) along with source for it: git, tarball, binary package+* which program you are using (gnokii, xgnokii, smsd) and its version (<code>gnokii --version</code> or <code>smsd --version</code>) along with source for it: git, tarball, binary package -* edit your <code>gnokiirc</code> and enable debugging, e.g.:+* edit your <code>gnokiirc</code> and enable debugging (see below) and attach gzipped output to the email: -    [logging]+     LC_MESSAGES=en_US.UTF8 gnokii {parameters} >errfile 2>&1 -    debug = on+: (with <code>LC_MESSAGE=en_US.UTF8</code> the program output and the error messages will be in English) -and attach gzipped output to the email:+* if you get a SEGFAULT, a backtrace is needed (refer to [[segfault]]) -     LC_MESSAGES=en_US.UTF8 (x)gnokii(d) [parameters] 2>errfile+* if you get encoding errors always use the git version and attach to your report the -(with <code>LC_MESSAGE=en_US.UTF8</code> the program putput and the error messages will be in English)+* if you are using a Nokia do your tests also with the [[fake driver]] - + -It would be good if you name the problem in the subject if possible and+ -name if it meets [[gnokii]], [[xgnokii]] or [[gnokiid]] binaries or gnokii as a whole.+ -* if you get a SEGFAULT, a backtrace is needed (refer to [[segfault]]).+ -* if you get encoding errors always use the git version and if you are using a Nokia do your tests also with the [[fake driver]]+ Send resulting report to gnokii-users (at) nongnu.org Send resulting report to gnokii-users (at) nongnu.org -If you want to debug yourself, by default the git version adds -g to CFLAGS+If you want to debug yourself, use the git version and run autogen.sh (or configure) with -when generating makefiles and the defines needed to print debug+<code>--disable-shared</code> to build statically linked -messages when generating <code>include/config.h</code> then in your <code>gnokiirc</code> set <code>debug=on</code>+versions that are easier to deal with, in this case the executables can be run as: -to see messages about libgnokii or gnokii and <code>xdebug=on</code> to see messages+ -about xgnokii or smsd.<br/>+ -At configure time you may add <code>--disable-shared</code> to build statically linked+ -versions that are easier to deal with.<br/>+ -make clean; make and then you can make install or run the programs from their+ -directory if they are statically linked:  +   gnokii/gnokii   gnokii/gnokii   xgnokii/xgnokii   xgnokii/xgnokii   smsd/smsd   smsd/smsd  +  +== Enabling debug output ==  +  +Debug routines are compiled in by default and can be enabled in the <code>[logging]</code> section of the configuration file.  +  +To enable the debug output for the drivers and for gnokii, set <code>debug = on</code>  +  +To enable the debug output for higer level routines of smsd and xgnokii, set <code>xdebug = on</code>  +  +  [logging]  +  debug = on  +  xdebug = on Dforsi

← Older revision Revision as of 08:08, 12 July 2010 Line 11: Line 11: ** sendsms ** sendsms ** getphonebook ** getphonebook  +** writephonebook - vCard properties FN, TEL, EMAIL and NOTE are written; N, NICKNAME, PHOTO, URL, ADR, ORG, BDAY, TZ, GEO and CATEGORIES are ignored.  +** deletephonebook * Doesn't Work * Doesn't Work Line 41: Line 43: ** setringtone ** setringtone ** deletecalendarnote ** deletecalendarnote -** writephonebook  ** all WAP stuff ** all WAP stuff ** all security stuff ** all security stuff ** all file stuff ** all file stuff L0b0

Nokia 6210 Navigator is handled by the Nk6510 driver.

← Older revision Revision as of 19:22, 11 July 2010 Line 1: Line 1:  +'''Note''': ''Nokia 6210 Navigator'' is a Series 40 phone handled by the [[Nk6510 driver]], not by this one.  + {{Config| {{Config| |description=Linux, serial connection /w DLR-3 cable on port COM1 |description=Linux, serial connection /w DLR-3 cable on port COM1 Dforsi

Move a note in a more relevant page

← Older revision Revision as of 19:19, 11 July 2010 Line 1: Line 1: -'''Note''': ''Nokia 6210 Navigator'' phones are handled by the [[Nk6510 driver]].  -  == Supported models == == Supported models == Dforsi

Series 40 3rd: use {{Config}} template

New page

You can assume that your phone is supported, however there are rare cases that you will get very limited functionality with gnokii.

This page lists those cases.

= Nokia =

== Series 40 3rd ==

Phone doesn't support <code>AT*NOKIAFBUS</code> so <code>model = series40 connection = serial port = /dev/ttyACM0</code> doesn't work.

Phone doesn't support reading SMS with <code>model = AT</code>.

Phone sends a notification with empty fields when SMS is received.

=== Workarounds ===

{{Config|
|description=preferred configuration for [[DKU2]] cable and similar
|port = 1
|model = series40
|connection = dku2libusb
}}

=== Phones showing this behaviour ===

* Nokia 5300
* probably all other [http://www.forum.nokia.com/Devices/Series_40/ Series 40 3rd Ed.] and later.

== Series 60 3rd ==

Phone doesn't support FBUS (<code>model = series60</code>) over Bluetooth, only over USB (<code>connection = dku2libusb</code>).

Phone doesn't support reading SMS and phonebook, neither with <code>model = AT</code> nor with <code>model = series60</code> nor with other settings.

=== Workarounds ===

To read the phonebok you can use the OBEX protocol.

This gets the whole phonebook in vCard 2.1 format (getting a single entry doesn't seem to work):
obexftp --bluetooth 00:11:22:33:44:55 --get telecom/pb.vcf

=== Phones showing this behaviour ===

* Nokia N73
* probably all other [http://www.forum.nokia.com/Devices/Device_specifications/matrix_s60_1.html Series 60 3rd Ed.] and later.

= Related pages =

* [[Config]] Dforsi

Created page with 'You can assume that your phone is supported, however there are rare cases that you will get very limited functionality with gnokii. This page lists those cases. = Nokia = == …'

New page

You can assume that your phone is supported, however there are rare cases that you will get very limited functionality with gnokii.

This page lists those cases.

= Nokia =

== Series 40 3rd ==

Phone doesn't support <code>AT*NOKIAFBUS</code> so <code>model = series40 connection = serial</code> doesn't work, use <code>connection = dku2libusb</code> instead.

Phone doesn't support reading SMS with <code>model = AT</code>.

Phone sends a notification with empty fields when SMS is received.

=== Phones showing this behaviour ===

* Nokia 5300
* probably all other [http://www.forum.nokia.com/Devices/Series_40/ Series 40 3rd Ed.] and later.

== Series 60 3rd ==

Phone doesn't support FBUS (<code>model = series60</code>) over Bluetooth, only over USB (<code>connection = dku2libusb</code>).

Phone doesn't support reading SMS and phonebook, neither with <code>model = AT</code> nor with <code>model = series60</code> nor with other settings.

=== Workarounds ===

To read the phonebok you can use the OBEX protocol.

This gets the whole phonebook in vCard 2.1 format (getting a single entry doesn't seem to work):
obexftp --bluetooth 00:11:22:33:44:55 --get telecom/pb.vcf

=== Phones showing this behaviour ===

* Nokia N73
* probably all other [http://www.forum.nokia.com/Devices/Device_specifications/matrix_s60_1.html Series 60 3rd Ed.] and later.

= Related pages =

* [[Config]] Dforsi

New user account

New page

Blessani

changed group membership for User:L0b0 from (none) to gnokii

New page

Pkot

Problems with libusb on Ubuntu

← Older revision Revision as of 10:18, 10 July 2010 Line 104: Line 104: * ruels syntax for your version of udev (eg. older versions used "=" instead of "==") * ruels syntax for your version of udev (eg. older versions used "=" instead of "==") * there aren't conflicting rules (eg. rules that reference <tt>SYSFS{idVendor}=="0421"</tt>) * there aren't conflicting rules (eg. rules that reference <tt>SYSFS{idVendor}=="0421"</tt>)  +  +==== Check libusb version ====  +If you get the error:  + No idle setting  +and you use Ubuntu check your libusb version:  + $ dpkg -l libusb\*  + Desired=Unknown/Install/Remove/Purge/Hold  + | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend  + |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)  + ||/ Name            Version                  Description  + +++-===============-=========================-===================================================================  + ii  libusb-0.1-4    2:0.1.12-14ubuntu0.1      userspace USB programming library  + ii  libusb-1.0-0    2:1.0.6-1ubuntu0~ppa1    userspace USB programming library  + ii  libusb-dev      2:0.1.12-14ubuntu0.1      userspace USB programming library development files  + un  libusb0        <none>                    (no description available)  + ii  libusbmuxd1    1.0.2-1ubuntu2            USB multiplexor daemon for iPhone and iPod Touch devices - library  +The version <tt>2:0.1.12-14ubuntu0.1</tt> from Ubuntu Lucid and Maverick (at least) has a bug and does not work with gnokii. Currently the solution is to downgrade to version <tt>2:0.1.12-14</tt>:  + $ sudo apt-get install libusb-0.1-4=2:0.1.12-14 libusb-dev=2:0.1.12-14 Pkot

New user account

New page

XaviPedrez

New user account

New page

Siberic

New user account

New page

Bzinyemba

Debug udev rules: do not add /sys

← Older revision Revision as of 21:58, 25 June 2010 (2 intermediate revisions not shown)Line 85: Line 85:   /dev/bus/usb/003/005   /dev/bus/usb/003/005 Use node name to get "devpath" Use node name to get "devpath" -  $ udevinfo --query path --name /dev/bus/usb/003/005+  $ udevadm info --query path --name /dev/bus/usb/003/005   /devices/pci0000:00/0000:00:0c.1/usb3/3-2   /devices/pci0000:00/0000:00:0c.1/usb3/3-2  +For older distributions use <code>udevinfo</code> instead of <code>udevadm info</code> -Add <tt>/sys</tt> in front of output to get "devpath"  - /sys/devices/pci0000:00/0000:00:0c.1/usb3/3-2  Use "devpath" as an argument to <tt>udevtest</tt> to debug udev rules Use "devpath" as an argument to <tt>udevtest</tt> to debug udev rules -  $ udevtest /devices/pci0000:00/0000:00:0c.1/usb3/3-2/+  $ udevadm test /devices/pci0000:00/0000:00:0c.1/usb3/3-2/   [...]   [...]   udev_node_add: creating device node '/dev/bus/usb/003/005', major=189, minor=260, mode=0664, uid=0, gid=46   udev_node_add: creating device node '/dev/bus/usb/003/005', major=189, minor=260, mode=0664, uid=0, gid=46   [...]   [...] In the output above ownership of the device is given to group id 46. In the output above ownership of the device is given to group id 46.  +For older distributions use <code>udevtest</code> instead of <code>udevadm test</code>   $ grep 46 /etc/group   $ grep 46 /etc/group   plugdev:x:46:user1,user2   plugdev:x:46:user1,user2 Dforsi