|
Configuration and preparation
First you should set the port to be used by scmxx. You can do this in three ways:
- at compilation time with the configure parameter
- by setting the environment variable SCMXX_TTY
- by using the --device (-d) parameter
Other ways are not recommended (like symlinking) but might work, too.
After that is done, you should test it:
scmxx --info
If that completes with success than you are ready to continue. Use the output
of the above command to see the abilities of your phone (last two lines).
If that does not complete, you may have to adjust the baudrate either with
scmxx:
- at compilation time with the configure parameter
- by setting the environment variable SCMXX_BAUD
- by using the --baud (-b) parameter
or on the phone (see manual how to do this).
|
syntax of the scmxx command line tool
using in combination with other programs
| kaddressbook |
To dial with scmxx, go to kaddressbook configuration dialog and
use the following telephone script:
konsole -T "dialing %N with scmxx" -e scmxx --dial --number="%N"
Newer versions (e.g. in KDE-3.5) also differ between dialing and sending SMS (nice),
so you can additionally use the SMS sending:
konsole -T "sending SMS to %N with scmxx" -e scmxx --send --sms --direct --number="%N" %F
Bugs: kaddressbook from KDE-3.2.3 does not print leading + for
international numbers.
|
setting up bluetooth in linux
- First load the kernel module. For USB dongles, this is hci_usb and it gets
automatically loaded when you have hotplug installed.
- Use hcitool check that the adapter is present:
hcitool dev
It returns the interface name and it's bluetooth MAC address.
- Use hcitool to scan for devices. It is assumed that "hci0" ist the interface name:
hcitool -i hci0 scan
It returns MAC adresses of bluetooth devices (further called <bdaddr>)
- Make sure that you have a bluetooth PIN program configured in /etc/bluetooth/hcid.conf.
I suggest to install bluez-pin, configure hcid.conf to dbus_pin_helper and start
bluez-pin:
bluez-pin --dbus &
It is started in the background and will later open a window to enter the PIN. If you do
not want to leave the terminal window open (closing it would kill bluez-pin),
run bluez-pin with "nohup".
Note: you must have dbus installed for this to work (it usually runs as a daemon, so
take a look at your process list), else you must configure a fixed pin_helper program.
Do not use the dbus_pin_helper and pin_helper directives at the same
time!
- Use sdptool to check that the device actually supports the serial port profile:
sdptool search --bdaddr <bdaddr> 0x1101
This will also ask you to enter a PIN: choose one and enter on the phone the same. It can
be any number of your choice.
- With versions prior to scmxx-0.9.0, you needed root rights to set up the
rfcomm device file. This is not needed anymore.
- Now you are ready to run scmxx.
|
Reported work-arounds for possible problems
|
Note: please do follow the steps under
"Help" -> "Configuration and preparation"
before trying any
of the below work-arounds.
- If scmxx reports "Timeout on opening device" with an Actisys IrDA dongle,
you might need to:
echo 9600 >/proc/sys/net/irda/max_baud_rate
This was reported on kernel 2.4.14 but it may apply to others, too.
- Someone reported problems with the ME45/S45 (actually the same)
and the serial port. It was solved by him by setting a different
baudrate with the --baud parameter.
this must equal the following setting in the ME45/S45:
Menu -> Setup -> Connectivity -> Baud Rate
This menu entry is only present in firmware revision 14 and earlier.
Firmware revision 21 and later should detect the used serial speed.
(I don't know how well that works.)
- You should only use cables that were designed for the specific model you use.
Newer cables may work with older phones and the other way round but there is
no garanty on that.
One user used a cable for the S25 and his S35i lost network when the cable was
plugged in. Sure, no SMS or the like can be sent with this setup.
|
Tips for specific files
|
Bitmap (.bmp) files:
- the phones do only accept plain bitmap file format,
things like RLE encoding is not supported
(testet with S35i, S45, SL42)
|
|
vCalendar (.vcs) files:
this is based on a mail from George Klein and refers
to a S45. The other supported phones may behave equally.
- Transferring an appointment with only DTSTART and DTEND ends up in the phone as deactivated and not highlighted in the calendar.
- Adding AALARM the same as DTSTART shows as activated and highlighted.
- Adding DALARM the same as DTSTART shows as deactivated and highlighted.
- Adding both AALARM and DALARM shows as activated and highlighted.
- Regarding recurring appointments the phone doesn't follow RFC2445 for RRULE. The only possibilities that I have found that the phone will accept are:
D1 - daily
W1 [MO|TU|WE|TH|FR|SA|SU] - weekly on chosen day (multiple days are also OK)
D7 - in place of W1 above also works
MD1 <day> - monthly on chosen date
YD1 - yearly
I have found no way to set an end date for these, or a number of repeats.
|
|
