Reporting Bugs in Wammu and Gammu

Use bug tracker to report a bug or a feature requests. Please take care that you include all information necessary for the developer to investigate the problem. The most important things to include are:

Obtaining Debugging Log

Debugging log contains transcription of communication between Gammu and your phone. As such it might contain your private data. If it is the case or you are not sure, you should mark the bug private, so that only developers are allowed to see the data in it, but it is not publicly accessible as other bug reports.

To make Gammu generate debug log, you need to tell it to do so. It is possible either by command line (gammu --debug textalldate --debug-file /tmp/gammu.log identify) or using configuration file:

[gammu]
connection = your connection setting
port = your port name
logformat = textalldate
logfile = /tmp/gammu.log

Wammu automatically creates debugging log in temporary directory (/tmp on Unix systems or Windows it is usually placed under Application Data folder in your profile), where it is kept in case Wammu has crashed. You can also save the current debug log while running Wammu from Help menu.

Gammu SMSD logging is configured in more levels, to include all messages, set debuglevel to 255:

[smsd]
debuglevel = 255
logfile = /tmp/smsd.log

Troubleshooting Windows Service

If Gammu fails to start as a Windows service (you will usually get "Error 1053: The service did not respond to the start or control request in a timely fashion"), first check your SMSD logs. If they do not contain any useful hint, try starting SMSD manually with exactly same parameters as you installed the service (without -i). You should also check if you pass all paths as absolute (eg. path to configuraiton file).

For example the command line can look like:

gammu-smsd.exe -c c:\gammu\smsdrc

You now should be able to get errors from SMSD even if it fails to start as a service.