Gammu - Does some neat things with your cellular phone or modem.
Usage: gammu [parameters] <command> [options]
This program is a tool for mobile phones. Many vendors and phones are supported, for actual listing see <http://wammu.eu/phones/>.
Parameters before command configure gammu behaviour:
-c / --config <filename> ... name of configuration file
-s / --section <confign> ... section of config file to use,
eg. 42
-d / --debug <level> ... debug level (see gammurc(5) for possible values)
-f / --debug-file <filename> ... file for logging debug
messages
Commands can be specified with or without leading --.
show|hide - optional parameter whether to disable call number indication.
get|set - whether to get divert information or to set it.
all|busy|noans|outofreach - condition when apply divert
all|voice|fax|data - call type when apply divert
number - number where to divert
timeout - timeout when the diversion will happen
Sending messages might look a bit complicated on first attempt to use. But be patient, the command line has been written in order to allow almost every usage. See EXAMPLE section for some hints on usage.
There is also an option to use gammu-smsd(1) when you want to send or receive more messages and process them automatically.
-smscset number - SMSC will be taken from set number. Default set: 1
-smscnumber number - SMSC number
-reply - reply SMSC is set
-maxnum number - Limit maximal number of messages which will be created. If there are more messages, Gammu will terminate with failure.
-folder number - save to specified folder.
Folders are numerated from 1.
The most often folder 1 = "Inbox", 2 = "Outbox",etc. Use getsmsfolders to get folder list.
-unread - makes message unread. In some phones (like 6210) you won't see unread sms envelope after saving such sms. In some phones with internal SMS memory (like 6210) after using it with folder 1 SIM SMS memory will be used
-read - makes message read. In some phones with internal SMS memory (like 6210) after using it with folder 1 SIM SMS memory will be used
-unsent - makes message unsent
-sent - makes message sent
-sender number - set sender number
-smsname name - set message name
-sender number - set sender number (default: "Gammu")
-report - request delivery report for message
-validity HOUR|6HOURS|DAY|3DAYS|WEEK|MAX - sets how long will be the message valid (SMSC will the discard the message after this time if it could not deliver it).
-save - will also save message which is being sent
Gammu has support for many SMS formats like:
Nokia Smart Messaging (used for monochromatic picture images, downloadable profiles, monochromatic operator logos, monochromatic caller logos and monophonic ringtones)
Linked SMS (both with 8 and 16-bit identification numbers in headers)
EMS (this is SMS format used for saving monochromatic images, monophonic ringtones, animations, text formatting and others)
MMS notifications
Alcatel logo messages
You need to ensure that the target phone supports message type you want to send. Otherwise the phone will not be able to display it or will even crash, because firmware of phone did not expect this possibility.
Text in SMS can be coded using two ways:
with GSM Default Alphabet - in single SMS you can have maximally 160 chars (Gammu doesn't support compressing such texts according to GSM standards, but it isn't big limit, because there are no phones supporting them), but they're from limited set:
* all Latin small and large
* all digits
* some Greek
* some other national
* some symbols like @ ! " # & / ( ) % * + = - , . : ; < > ?
* few others
with Unicode - in single SMS you can save at most 70 chars, but these can be any chars including all national and special ones. Please note, that some older phones might have problems displaying such message.
Gammu tries to do the best to handle non ASCII characters in your message. Everything is internally handled in Unicode (the input is converted depending on your locales configuration) and in case message uses Unicode the text will be given as such to the message.
Should the message be sent in GSM Default Alphabet, Gammu will try to convert all characters to keep message readable. Gammu does support multi byte encoding for some characters in GSM Default Alphabet (it is needed for ^ { } \ [ ] ~ |). The characters which are not present in GSM Default Alphabet are transliterated to closest ASCII equivalent (accents are removed). Remaining not known characters are replaced by question mark.
Use -yes for answering yes to all questions (backup all messages and delete them from phone), or -all to just backup all folders while keeping messages in phone.
Locations are numerated from 1.
Displays PDU data of encoded SMS messages. It accepts same parameters and behaves same like sendsms.
Locations are numerated from 1.
Folder 0 means that sms is being read from "flat" memory (all sms from all folders have unique numbers). It's sometimes emulated by Gammu. You can use it with all phones.
Other folders like 1, 2, etc. match folders in phone such as Inbox, Outbox, etc. and each sms has unique number in his folder. Name of folders can depend on your phone (the most often 1="Inbox", 2="Outbox", etc.). This method is not supported by all phones (for example, not supported by Nokia 3310, 5110, 6110). If work with your phone, use getsmsfolders to get folders list.
Locations are numerated from 1.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
Please note, that it isn't designed for colour logos available for example in DCT4/TIKU - you need to put bitmap file there inside phone using filesystem commands.
For description of shared parameters see Common parameters for sendsms and savesms.
Saves EMS sequence. All parameters after -unread (like -defsound) can be used few times.
-text - adds text
-unicodefiletext - adds text from Unicode file
-defanimation - adds default animation with ID specified by user.ID for different phones are different.
-animation - adds "frames" frames read from file1, file2, etc.
-defsound - adds default sound with ID specified by user. ID for different phones are different.
-tone10 - adds IMelody version 1.0 read from RTTL or other compatible file
-tone10long - IMelody version 1.0 saved in one of few SMS with UPI. Phones compatible with UPI (like SonyEricsson phones) will read such ringtone as one
-tone12 - adds IMelody version 1.2 read from RTTL or other compatible file
-tone12long - IMelody version 1.2 saved in one of few SMS with UPI. Phones compatible with UPI (like SonyEricsson phones) will read such ringtone as one
-toneSE - adds IMelody in "short" form supported by SonyEricsson phones
-toneSElong - add SonyEricsson IMelody saved in one or few SMS with UPI
-variablebitmap - bitmap in any size saved in one SMS
-variablebitmaplong - bitmap with maximal size 96x128 saved in one or few sms
-fixedbitmap - bitmap 16x16 or 32x32
-protected - all ringtones and bitmaps after this parameter (excluding default ringtones and logos) will be "protected" (in phones compatible with ODI like SonyEricsson products it won't be possible to forward them from phone menu)
-16bit - Gammu uses SMS headers with 16-bit numbers for saving linking info in SMS (it means less chars available for user in each SMS)
-format lcrasbiut - last text will be formatted. You can
use combinations of chars:
l - left aligned
c - centered
r - right aligned
a - large font
s - small font
b - bold font
i - italic font
u - underlined font
t - strikethrough font
Example: gammu savesms EMS -text "Greetings" -defsound 1 -text "from Gammu" -tone10 axelf.txt -animation 2 file1.bmp file2.bmp
will create EMS sequence with text "Greetings" and default sound 1 and text "from Gammu" and ringtone axelf.txt and 2 frame animation read from (1'st frame) file1.bmp and (2'nd frame) file2.bmp
Example: gammu savesms EMS -protected 2 -variablebitmaplong ala.bmp -toneSElong axelf.txt -toneSE ring.txt
ala.bmp and axelf.txt will be "protected"
For description of shared parameters see Common parameters for sendsms and savesms.
Saves a message with MMS indication. The recipient phone will then download MMS from given URL and display it.
Please note that you should provide valid smil data on that URL.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
Please note, that it isn't designed for colour logos available for example in DCT4/TIKU - you need to put bitmap file there inside phone using filesystem commands.
For description of shared parameters see Common parameters for sendsms and savesms.
Read bitmap from 2 colors file (bmp, nlm, nsl, ngg, nol, wbmp, etc.), format into bitmap in Smart Messaging (72x28, 2 colors, called often Picture Image and saved with text) or Alcatel format and send/save over SMS.
For description of shared parameters see Common parameters for sendsms and savesms.
Read ringtone (RTTL) format, bitmap (Picture Image size) and name, format into Smart Messaging profile and send/save as SMS. Please note, that this format is abandomed by Nokia and supported by some (older) devices only like Nokia 3310.
For description of shared parameters see Common parameters for sendsms and savesms.
-long - ringtone is saved using Profile style. It can be longer (and saved in 2 SMS), but decoded only by newer phones (like 33xx)
-scale - ringtone will have Scale info for each note. It will allow to edit it correctly later in phone composer (for example, in 33xx)
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
-flash - Class 0 SMS (should be displayed after receiving on recipients' phone display after receiving without entering Inbox)
-len len - specify, how many chars will be read. When use this option and text will be longer than 1 SMS, will be split into more linked SMS
-autolen len - specify, how many chars will be read. When use this option and text will be longer than 1 SMS, will be split into more linked SMS.Coding type (SMS default alphabet/Unicode) is set according to input text
-enablevoice | -disablevoice | -enablefax | -disablefax | -enableemail | -disableemail - sms will set such indicators. Text will be cut to 1 sms.
-voidsms - many phones after receiving it won't display anything, only beep, vibrate or turn on light. Text will be cut to 1 sms.
-unicode - SMS will be saved in Unicode format
-inputunicode - input text is in Unicode.
-text - get text from command line instead of stdin.
-textutf8 - get text in UTF-8 from command line instead of stdin.
-16bit - Gammu uses SMS headers with 16-bit numbers for saving linking info in SMS (it means less chars available for user in each SMS)
TIP: You can create Unicode file using WordPad in Windows (during saving select "Unicode Text Document" format). In Unix can use for example YUdit.
-replacemessages ID - ID can be 1..7. When you will use option and send more single SMS to one recipient with the same ID, each another SMS will replace each previous with the same ID
-replacefile file - when you want, you can make file in such format: src_unicode_char1, dest_unicode_char1, src_unicode_char2, dest_unicode_char2 (everything in one line). After reading text for SMS from stdin there will be made translation and each src char will be converted to dest char. In docs there is example file (replace.txt), which will change all "a" chars to "1"
TIP: when use ~ char in sms text and -unicode option (Unicode coding required), text of sms after ~ char will blink in some phones (like N33xx)
Example: echo some_text | gammu savesms TEXT
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
Locations are numerated from 1.
Please note that this adds all content of backup file to phone and does not care about current data in the phone (no duplicates are detected).
Use -yes parameter to answer yes to all questions (you want to automatically restore all data).
Use -memory parameter to force usage of defined memory type for storing entries regardless what backu format says.
* phonebook from SIM and phone memory
* calendar notes
* SMSC settings
* operator logo
* startup (static) logo or startup text
* WAP bookmarks
* WAP settings
* caller logos and groups
* user ringtones
There are various backup formats supported and the backup format is guessed based on file extension:
* .lmb - Nokia backup, supports contacts, caller logos and
startup logo.
* .vcs - vCalendar, supports calendar and todo.
* .vcf - vCard, supports contacts.
* .ldif - LDAP import, supports contacts.
* .ics - iCalendar, supports calendar and todo.
* Any other extension is Gammu backup file and it supports all data
mentioned above.
See EXAMPLE section for some hints on manipulating Gammu backup format.
Locations are numerated from 1.
DC = Dialled calls
MC = Missed calls
RC = Received calls
ON = Own numbers
VM = voice mailbox
SM = SIM phonebook
ME = phone internal phonebook
FD = fixed dialling
SL = sent SMS log
Please note that restoring deletes all current content in phone. If you want only to add entries to phone, use addnew.
In some phones restoring calendar notes will not show error, but won't be done, when phone doesn't have set clock inside.
For example if you want to convert single entry from gammu native backup to vCard, you need following command:
gammu savefile CALENDAR output.vcf myPhonebook.backup ME 42
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
Gammu allows to access phones using native protocol (Nokias) or OBEX. Your phone can also support usb storage, which is handled on the operating system level and Gammu does not use that.
-type - file type was required for filesystem 1 in Nokia phones (current filesystem 2 doesn't need this)
-readonly, -protected, -system, -hidden - you can set readonly, protected (file can't be for example forwarded from phone menu), system and hidden (file is hidden from phone menu) file attributes
-newtime - after using it date/time of file modification will be set to moment of uploading
-flatall there are displayed full file/folder details like ID (first parameter in line)
-flat
Please note, that in some phones (like N6230) content of some folders (with more files) can be cut (only part of files will be displayed) for example on infrared connection. This is not Gammu issue, but phone firmware problem.
Display files and folders available in folder with given folder ID. You can get ID's using getfilesystem -flatall.
Please note, that in some phones (like N6230) content of some folders (with more files) can be cut (only part of files will be displayed) for example on infrared connection. This is not Gammu issue, but phone firmware problem.
Display info about drives available in phone/memory card.
The option -overwrite deletes the application's .jad and .jar files bevor installing, but doesn't delete the application data. Option -overwriteall will also delete all data. Both these options work only for Application or Game upload.
Example: gammu nokiaaddfile Application Alien will read Alien.JAD and Alien.JAR and add to Applications
Example: gammu nokiaaddfile Tones file.mid will read file.mid and add to Tones folder
You can use jadmaker(1) to generate a .jad file from a .jar file.
Goes through phone memory and generated playlist for all music files found.
To manually manage playlists:
gammu addfile a:\predefplaylist filename.m3u
Will add playlist filename.m3u
gammu getfilesystem
Will get list of all files (including names of files with playlists)
gammu deletefiles a:\predefplaylist\filename.m3u
Will delete playlist filename.m3u
Format of m3u playlist is easy (standard mp3 playlist):
First line is #EXTM3U, next lines contain names of files (b:\file1.mp3, b:\folder1\file2.mp3, etc.). File needs t have '\r\n' terminated lines. So just run unix2dos on the resulting file before uploading it your your phone.
These options are mainly (there are few expections) for monochromatic logos and images available in older phones. Recognized file formats: xpm (only saving), 2-colors bmp, nlm, nsl, ngg, nol, wbmp, gif (for Samsung).
In new models all bitmaps are saved in filesystem and should go into filesystem section
For description of shared parameters see Common parameters for sendsms and savesms.
Please note, that it isn't designed for colour logos available for example in DCT4/TIKU - you need to put bitmap file there inside phone using filesystem commands.
For description of shared parameters see Common parameters for sendsms and savesms.
Please note, that it isn't designed for colour logos available for example in DCT4/TIKU - you need to put bitmap file there inside phone using filesystem commands.
For description of shared parameters see Common parameters for sendsms and savesms.
Read bitmap from 2 colors file (bmp, nlm, nsl, ngg, nol, wbmp, etc.), format into bitmap in Smart Messaging (72x28, 2 colors, called often Picture Image and saved with text) or Alcatel format and send/save over SMS.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
Ringtones are mostly supported only for older phones. For recent phones you usually just upload them to some folder in phone filesystem.
There are recognized various file formats by options described below: rttl, binary format created for Gammu, mid (saving), re (reading), ott, communicator, ringtones format found in fkn.pl, wav (saving), ime/imy (saving), rng, mmf (for Samsung).
Please note that this adds all content of backup file to phone and does not care about current data in the phone (no duplicates are detected).
Use -yes parameter to answer yes to all questions (you want to automatically restore all data).
Use -memory parameter to force usage of defined memory type for storing entries regardless what backu format says.
* phonebook from SIM and phone memory
* calendar notes
* SMSC settings
* operator logo
* startup (static) logo or startup text
* WAP bookmarks
* WAP settings
* caller logos and groups
* user ringtones
There are various backup formats supported and the backup format is guessed based on file extension:
* .lmb - Nokia backup, supports contacts, caller logos and
startup logo.
* .vcs - vCalendar, supports calendar and todo.
* .vcf - vCard, supports contacts.
* .ldif - LDAP import, supports contacts.
* .ics - iCalendar, supports calendar and todo.
* Any other extension is Gammu backup file and it supports all data
mentioned above.
See EXAMPLE section for some hints on manipulating Gammu backup format.
Get one of "default" ringtones and saves into file
Locations are numerated from 1.
Play one of "built" ringtones. This option is available for DCT4 phones. For getting ringtones list use getringtoneslist.
Please note that restoring deletes all current content in phone. If you want only to add entries to phone, use addnew.
In some phones restoring calendar notes will not show error, but won't be done, when phone doesn't have set clock inside.
-long - ringtone is saved using Profile style. It can be longer (and saved in 2 SMS), but decoded only by newer phones (like 33xx)
-scale - ringtone will have Scale info for each note. It will allow to edit it correctly later in phone composer (for example, in 33xx)
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
TIP: when use ~ char in ringtone name, in some phones (like 33xx) name will blink later in phone menus
In Nokia 3310, 3315 and 3330 these are named "Reminders" and have some limitations (depending on phone firmware version).
Please note that this adds all content of backup file to phone and does not care about current data in the phone (no duplicates are detected).
Use -yes parameter to answer yes to all questions (you want to automatically restore all data).
Use -memory parameter to force usage of defined memory type for storing entries regardless what backu format says.
* phonebook from SIM and phone memory
* calendar notes
* SMSC settings
* operator logo
* startup (static) logo or startup text
* WAP bookmarks
* WAP settings
* caller logos and groups
* user ringtones
There are various backup formats supported and the backup format is guessed based on file extension:
* .lmb - Nokia backup, supports contacts, caller logos and
startup logo.
* .vcs - vCalendar, supports calendar and todo.
* .vcf - vCard, supports contacts.
* .ldif - LDAP import, supports contacts.
* .ics - iCalendar, supports calendar and todo.
* Any other extension is Gammu backup file and it supports all data
mentioned above.
See EXAMPLE section for some hints on manipulating Gammu backup format.
Please note that restoring deletes all current content in phone. If you want only to add entries to phone, use addnew.
In some phones restoring calendar notes will not show error, but won't be done, when phone doesn't have set clock inside.
For example if you want to convert single entry from gammu native backup to vCalendar, you need following command:
gammu savefile CALENDAR output.vcs myCalendar.backup 260
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
Please note that this adds all content of backup file to phone and does not care about current data in the phone (no duplicates are detected).
Use -yes parameter to answer yes to all questions (you want to automatically restore all data).
Use -memory parameter to force usage of defined memory type for storing entries regardless what backu format says.
* phonebook from SIM and phone memory
* calendar notes
* SMSC settings
* operator logo
* startup (static) logo or startup text
* WAP bookmarks
* WAP settings
* caller logos and groups
* user ringtones
There are various backup formats supported and the backup format is guessed based on file extension:
* .lmb - Nokia backup, supports contacts, caller logos and
startup logo.
* .vcs - vCalendar, supports calendar and todo.
* .vcf - vCard, supports contacts.
* .ldif - LDAP import, supports contacts.
* .ics - iCalendar, supports calendar and todo.
* Any other extension is Gammu backup file and it supports all data
mentioned above.
See EXAMPLE section for some hints on manipulating Gammu backup format.
Please note that restoring deletes all current content in phone. If you want only to add entries to phone, use addnew.
In some phones restoring calendar notes will not show error, but won't be done, when phone doesn't have set clock inside.
For example if you want to convert single entry from gammu native backup to vCalendar, you need following command:
gammu savefile CALENDAR output.vcs myCalendar.backup 260
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
Note: Not all phones supports this function, especially most Sony Ericsson phones even if they have notes inside phone.
TIP: you can make such synchronization each time, when will connect your phone and use Gammu. See gammurc(5) for details.
Please note that this adds all content of backup file to phone and does not care about current data in the phone (no duplicates are detected).
Use -yes parameter to answer yes to all questions (you want to automatically restore all data).
Use -memory parameter to force usage of defined memory type for storing entries regardless what backu format says.
* phonebook from SIM and phone memory
* calendar notes
* SMSC settings
* operator logo
* startup (static) logo or startup text
* WAP bookmarks
* WAP settings
* caller logos and groups
* user ringtones
There are various backup formats supported and the backup format is guessed based on file extension:
* .lmb - Nokia backup, supports contacts, caller logos and
startup logo.
* .vcs - vCalendar, supports calendar and todo.
* .vcf - vCard, supports contacts.
* .ldif - LDAP import, supports contacts.
* .ics - iCalendar, supports calendar and todo.
* Any other extension is Gammu backup file and it supports all data
mentioned above.
See EXAMPLE section for some hints on manipulating Gammu backup format.
Please note that restoring deletes all current content in phone. If you want only to add entries to phone, use addnew.
In some phones restoring calendar notes will not show error, but won't be done, when phone doesn't have set clock inside.
Please note that this adds all content of backup file to phone and does not care about current data in the phone (no duplicates are detected).
Use -yes parameter to answer yes to all questions (you want to automatically restore all data).
Use -memory parameter to force usage of defined memory type for storing entries regardless what backu format says.
* phonebook from SIM and phone memory
* calendar notes
* SMSC settings
* operator logo
* startup (static) logo or startup text
* WAP bookmarks
* WAP settings
* caller logos and groups
* user ringtones
There are various backup formats supported and the backup format is guessed based on file extension:
* .lmb - Nokia backup, supports contacts, caller logos and
startup logo.
* .vcs - vCalendar, supports calendar and todo.
* .vcf - vCard, supports contacts.
* .ldif - LDAP import, supports contacts.
* .ics - iCalendar, supports calendar and todo.
* Any other extension is Gammu backup file and it supports all data
mentioned above.
See EXAMPLE section for some hints on manipulating Gammu backup format.
Use -yes for answering yes to all questions (backup all messages and delete them from phone), or -all to just backup all folders while keeping messages in phone.
Please note that restoring deletes all current content in phone. If you want only to add entries to phone, use addnew.
In some phones restoring calendar notes will not show error, but won't be done, when phone doesn't have set clock inside.
For example if you want to convert single entry from gammu native backup to vCalendar, you need following command:
gammu savefile CALENDAR output.vcs myCalendar.backup 260
For example if you want to convert single entry from gammu native backup to vCalendar, you need following command:
gammu savefile CALENDAR output.vcs myCalendar.backup 260
For example if you want to convert single entry from gammu native backup to vCard, you need following command:
gammu savefile CALENDAR output.vcf myPhonebook.backup ME 42
The option -overwrite deletes the application's .jad and .jar files bevor installing, but doesn't delete the application data. Option -overwriteall will also delete all data. Both these options work only for Application or Game upload.
Example: gammu nokiaaddfile Application Alien will read Alien.JAD and Alien.JAR and add to Applications
Example: gammu nokiaaddfile Tones file.mid will read file.mid and add to Tones folder
You can use jadmaker(1) to generate a .jad file from a .jar file.
Goes through phone memory and generated playlist for all music files found.
To manually manage playlists:
gammu addfile a:\predefplaylist filename.m3u
Will add playlist filename.m3u
gammu getfilesystem
Will get list of all files (including names of files with playlists)
gammu deletefiles a:\predefplaylist\filename.m3u
Will delete playlist filename.m3u
Format of m3u playlist is easy (standard mp3 playlist):
First line is #EXTM3U, next lines contain names of files (b:\file1.mp3, b:\folder1\file2.mp3, etc.). File needs t have '\r\n' terminated lines. So just run unix2dos on the resulting file before uploading it your your phone.
Get voice record from location and save to WAV file. File is coded using GSM 6.10 codec (available for example in win32). Name of file is like name of voice record in phone.
Created WAV files require GSM 6.10 codec to be played. In Win XP it's included by Microsoft. If you deleted it by accident in this operating system, make such steps:
1. Control Panel
2. Add hardware
3. click Next
4. select "Yes. I have already connected the hardware"
5. select "Add a new hardware device"
6. select "Install the hardware that I manually select from a
list"
7. select "Sound, video and game controllers"
8. select "Audio codecs"
9. select "windows\system32" directory and file
"mmdriver.inf"
10. if You will be asked for file msgsm32.acm, it should unpacked
from Windows CD
11. now You can be asked if want to install unsigned driver (YES),
about select codec configuration (select what you want) and
rebotting PC (make it)
TIP: For more info about this option, please visit http://www.mwiacek.com and read netmonitor manual.
TIP: test 243 enables all tests (after using command gammu nokianetmonitor 243 in some phones like 6210 or 9210 have to reboot them to see netmonitor menu)
TIP: For more info about this option, please visit http://www.mwiacek.com and read netmonitor manual.
Perform tests for Nokia DCT3 phones.
Note: EEPROM test can show an error when your phone has an EEPROM in flash (like 82xx/7110/62xx/33xx). The clock test will show an error when the phone doesn?t have an internal battery for the clock (like 3xxx).
1. ALS (Alternative Line Service) option menu
2. vibra menu for 3210
3. 3315 features in 3310 5.45 and higher
4. two additional games (React and Logic) for 3210 5.31 and
higher
5. WellMate menu for 6150
6. NetMonitor
and for DCT4:
1. ALS (Alternative Line Service) option menu
2. Bluetooth, WAP bookmarks and settings menu, ... (6310i)
3. GPRS Always Online
...
Enables network monitor in Siemens phone. Currently known values for type are 1 for full and 2 for simple mode.
TIP: For more info about this option, please visit http://www.mwiacek.com and read netmonitor manual.
TIP: test 243 enables all tests (after using command gammu nokianetmonitor 243 in some phones like 6210 or 9210 have to reboot them to see netmonitor menu)
Enables network monitor in Siemens phone. Currently known values for type are 1 for full and 2 for simple mode.
Please note that this adds all content of backup file to phone and does not care about current data in the phone (no duplicates are detected).
Use -yes parameter to answer yes to all questions (you want to automatically restore all data).
Use -memory parameter to force usage of defined memory type for storing entries regardless what backu format says.
* phonebook from SIM and phone memory
* calendar notes
* SMSC settings
* operator logo
* startup (static) logo or startup text
* WAP bookmarks
* WAP settings
* caller logos and groups
* user ringtones
There are various backup formats supported and the backup format is guessed based on file extension:
* .lmb - Nokia backup, supports contacts, caller logos and
startup logo.
* .vcs - vCalendar, supports calendar and todo.
* .vcf - vCard, supports contacts.
* .ldif - LDAP import, supports contacts.
* .ics - iCalendar, supports calendar and todo.
* Any other extension is Gammu backup file and it supports all data
mentioned above.
See EXAMPLE section for some hints on manipulating Gammu backup format.
Locations are numerated from 1.
Locations are numerated from 1.
Locations are numerated from 1.
Please note that restoring deletes all current content in phone. If you want only to add entries to phone, use addnew.
In some phones restoring calendar notes will not show error, but won't be done, when phone doesn't have set clock inside.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
Saves a message with MMS indication. The recipient phone will then download MMS from given URL and display it.
Please note that you should provide valid smil data on that URL.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
Perform tests for Nokia DCT3 phones.
Note: EEPROM test can show an error when your phone has an EEPROM in flash (like 82xx/7110/62xx/33xx). The clock test will show an error when the phone doesn?t have an internal battery for the clock (like 3xxx).
Please note that this adds all content of backup file to phone and does not care about current data in the phone (no duplicates are detected).
Use -yes parameter to answer yes to all questions (you want to automatically restore all data).
Use -memory parameter to force usage of defined memory type for storing entries regardless what backu format says.
* phonebook from SIM and phone memory
* calendar notes
* SMSC settings
* operator logo
* startup (static) logo or startup text
* WAP bookmarks
* WAP settings
* caller logos and groups
* user ringtones
There are various backup formats supported and the backup format is guessed based on file extension:
* .lmb - Nokia backup, supports contacts, caller logos and
startup logo.
* .vcs - vCalendar, supports calendar and todo.
* .vcf - vCard, supports contacts.
* .ldif - LDAP import, supports contacts.
* .ics - iCalendar, supports calendar and todo.
* Any other extension is Gammu backup file and it supports all data
mentioned above.
See EXAMPLE section for some hints on manipulating Gammu backup format.
Please note that restoring deletes all current content in phone. If you want only to add entries to phone, use addnew.
In some phones restoring calendar notes will not show error, but won't be done, when phone doesn't have set clock inside.
PHONE:
DEV:
ALL:
Clear user settings
* removes or set logos to default
* set default phonebook and other menu settings
* clear T9 words,
* clear call register info
* set default profiles settings
* clear user ringtones
UIF:
* changes like after ALL
* disables netmon and PPS (all "hidden" menus)
FACTORY:
* changes like after UIF
* clear date/time
Read ringtone (RTTL) format, bitmap (Picture Image size) and name, format into Smart Messaging profile and send/save as SMS. Please note, that this format is abandomed by Nokia and supported by some (older) devices only like Nokia 3310.
For description of shared parameters see Common parameters for sendsms and savesms.
For description of shared parameters see Common parameters for sendsms and savesms.
This option is available only if Gammu was compiled with debuging options.
By default, commands are read from standard input, but you can optionally specify a file from where they would be read (special case - means standard input).
Get voice record from location and save to WAV file. File is coded using GSM 6.10 codec (available for example in win32). Name of file is like name of voice record in phone.
Created WAV files require GSM 6.10 codec to be played. In Win XP it's included by Microsoft. If you deleted it by accident in this operating system, make such steps:
1. Control Panel
2. Add hardware
3. click Next
4. select "Yes. I have already connected the hardware"
5. select "Add a new hardware device"
6. select "Install the hardware that I manually select from a
list"
7. select "Sound, video and game controllers"
8. select "Audio codecs"
9. select "windows\system32" directory and file
"mmdriver.inf"
10. if You will be asked for file msgsm32.acm, it should unpacked
from Windows CD
11. now You can be asked if want to install unsigned driver (YES),
about select codec configuration (select what you want) and
rebotting PC (make it)
1. ALS (Alternative Line Service) option menu
2. vibra menu for 3210
3. 3315 features in 3310 5.45 and higher
4. two additional games (React and Logic) for 3210 5.31 and
higher
5. WellMate menu for 6150
6. NetMonitor
and for DCT4:
1. ALS (Alternative Line Service) option menu
2. Bluetooth, WAP bookmarks and settings menu, ... (6310i)
3. GPRS Always Online
...
mM - Menu
nN - Names key
pP - Power
uU - Up
dD - Down
+- - +-
gG - Green
rR - Red
123456789*0# is numeric keyboard
Note: some phones will make hard reset even with SOFT option.
~/.gammurc
/usr/share/doc/gammu/*
/dev/ircomm?
/dev/ttyS?
/dev/ttyACM?
gammu returns 0 on success. In case of failure non zero code is returned.
Errors codes greater than 100 map to the GSM_Error values increased by 100:
To check it out, you need to have configuration file for gammu, see gammurc(5) for more details about it.
echo "All your base are belong to us" | gammu savesms TEXT
or
gammu savesms TEXT -text "All your base are belong to us"
echo "All your base are belong to us" | gammu savesms TEXT -len 400
or
gammu savesms TEXT -len 400 -text "All your base are belong to us"
or
gammu savesms EMS -text "All your base are belong to us"
gammu savesms EMS -text "Greetings" -defsound 1 -text "from Gammu" -tone10 axelf.txt -animation 2 file1.bmp file2.bmp
gammu savesms EMS -protected 2 -variablebitmaplong ala.bmp -toneSElong axelf.txt -toneSE ring.txt
If you will backup settings to Gammu text file, it will be possible to edit it. It's easy: many things in this file will be written double - once in Unicode, once in ASCII. When you will remove Unicode version Gammu will use ASCII on restore (and you can easy edit ASCII text) and will convert it according to your OS locale. When will be available Unicode version of text, it will be used instead of ASCII (useful with Unicode phones - it isn't important, what locale is set in computer and no conversion Unicode -> ASCII and ASCII -> Unicode is done).
You can use any editor with regular expressions function to edit backup text file. Examples of such editors can be vim <http://www.vim.org/> or TextPad <http://www.textpad.com/> which both do support regular expressions.
Find: ^Entry\([0-9][0-9]\)VoiceTag = \(.*\)\n
Replace:
Find: Type = NumberGeneral\nEntry\([0-9][0-9]\)Text = "\+36\(20\|30\|60\|70\)\n
Replace: Type = NumberMobile\nEntry\1Text = "\+3620
Find: Type = NumberGeneral\nEntry\([0-9][0-9]\)Text = "\+36\([2367]0\)\([^\"]*\)"\nEntry\([0-9][0-9]\)TextUnicode = \([^\n]*\)\n
Replace: Type = NumberMobile\nEntry\1Text = "\+36\2\3"\n
Copyright © 2003 - 2010 Marcin Wiacek, Michal Cihar and other
authors. License GPLv2: GNU GPL version 2 <http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
There are definitely many bugs, reporting to author is welcome. Please include some useful information when sending bug reports (especially debug logs, operating system, it's version and phone information are needed).
To generate debug log, enable it in gammurc (alternatively you can do it on command line using -d textall -f /tmp/gammu.log):
[gammu] YOUR CONNECTION SETTINGS logfile = /tmp/gammu.log logformat = textall
With this settings, Gammu generates /tmp/gammu.log on each connection to phone and stores dump of communication there. You can also find some hints for improving support for your phone in this log.
See <http://wammu.eu/support/bugs/> for more information on reporting bugs.
Please report bugs to <http://bugs.cihar.com>.
You can contact authors on <gammu-users@lists.sourceforge.net>.
Michal Cihar <michal@cihar.com> is current project maintainer and contributor of most of AT and OBEX code.
Marcin Wiacek <marcin@mwiacek.com> is project iniciator and contributor of most Nokia code.
As this project grew from Gnokii, we would like to thanks all Gnokii developers, especially Pavel Janik, Pawel Kot and Manfred Jonsson (see CREDITS from Gnokii for all their contributor).
Many other people have helped with various features, check ChangeLog for more details.
gammu-smsd(1), gammu-smsd-inject(1), gammurc(5), jadmaker(1)
Some more hints can be found in README file or on wiki <http://www.gammu.org/>.
Related programs which can be used with GSM modem:
minicom(1)
Graphical interfaces for Gammu:
wammu(1), gmobilemedia(1)