SyncEvolution 1.0 alpha and above allow you to synchronize the PIM data on your SyncML-capable phone via Bluetooth. Nokia Symbian-based phones are the most common SyncML-capable phones. Contacts, calendar, todos and notes are supported, although the support is not yet complete.
This has been tested with a Nokia 7210c (Symbian S40 5th edition), but it also works on other Symbian devices. See the list of test reports [3] for details on which phones are known to be compatible.
Note: If your phone is running Android or iOS, this method is not for you, since these operating systems do not natively support SyncML. After installing any (working...) SyncML-client, you can use the HTTP method for syncing. You can find more information here: Syncevolution and HTTP [4]
For Bluetooth synchronization, the phone must be paired with the computer. It must support SyncML (sometimes called OMA DS) over Bluetooth. Instructions are available for a variety of systems on how to pair your Bluetooth phone:
After pairing, the graphical Sync UI can be used to configure synchronization.
For instance, In MeeGo, do the following:
Synchronization with a Bluetooth phone can also be configured using the command-line client, as follows:
hcitool scan
This will print a list of discoverable Bluetooth devices, together with the address of each device. Find your phone in the list and set a variable for later usage. For example, run:
deviceAddress=01:23:45:67:89:01
if your device address is listed as ‘01:23:45:67:89:01’.syncevolution -l ?${matchstring}
where ‘${matchstring}’ is the string that you want to search for. For example, try using the name of yur phone, the model number or the manufacturer as the match string:
syncevolution -l ?Nokia
syncevolution --configure --template ${template} --sync-property syncURL=obex-bt://${deviceAddress} MyPhone
creates a configuration called ‘MyPhone’ with the template ‘${template}’ for the Bluetooth device with the device address ‘${deviceAddress}’. Substitute your values for the configuration name, template name and device address.syncevolution MyPhone
synchronizes your phone with the configuration name ‘MyPhone’. Substitute your configuration name for ‘MyPhone’. You will receive some informational output from SyncEvolution about the synchronization process, together with a summary at the end, which includes the number or synchronization items transferred, duration of the procedure, and so on.SyncEvolution currently has a limited set of configuration templates for SyncML-capable phones. If a template does not exist for your phone, you can create one with the ‘syncevo-phone-config’ tool, which is part of SyncEvolution. The tool tries to communicate with your phone and automatically create a template.
To do a thorough check, create a configuration and print a configuration template (which can then be
submitted to the wiki [17]) type the following command at a terminal:
syncevo-phone-config --bt-address ${BtAddress} --advanced --create-config=${configName}
and replace ‘${BtAddress}’ with the Bluetooth address of the phone, and ‘${configName}’ with a name of your choice for the new configuration template.
If the tool succeeds, you can configure SyncEvolution to use the new template, using the same name that you chose earlier. Please also submit the details to the wiki [17] so that other users may benefit from your findings.
If you wish to use the template with the graphical UI, there are additional steps before the configuration will be shown:
mkdir -p ~/.config/syncevolution-templates
~/.config/syncevolution-templates/my-template
See a blog post with screenshots [18] for a detailed guide.
hcitool scan
on the computer's command line must find the phone (see 'Command-line synchronization' above)sdptool search --bdaddr ${BtAddress} SYNCML
(with ${BtAddress} replaced by the address found in the previous step) must find a SyncML client.Example:
$ hcitool scan
Scanning ...
A0:4E:04:1E:AD:30 Nokia N97
$ sdptool search --bdaddr A0:4E:04:1E:AD:30 SYNCML
Searching for SYNCML on A0:4E:04:1E:AD:30 ...
Service Name: SyncMLClient
Service RecHandle: 0x1000b
Service Class ID List:
UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 7
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00000002-0000-1000-8000-0002ee000002)
Version: 0x0100
If the sync fails, try the following possible solutions:
Links
[1] https://syncevolution.org/taxonomy/term/bluetooth
[2] https://syncevolution.org/taxonomy/term/development
[3] https://syncevolution.org/taxonomy/term/phone
[4] https://syncevolution.org/wiki/synchronizing-evolution-http-howto
[5] http://library.gnome.org/users/gnome-help/stable/bluetooth-connect-device.html
[6] http://help.meego.com/netbook/bluetooth/add-bluetooth-device
[7] http://help.meego.com/netbook/applications/applications-panel
[8] https://syncevolution.org/sites/syncevolution.org/files/bluetooth_pair_sync.png
[9] https://syncevolution.org/sites/syncevolution.org/files/sync_firstrun.png
[10] https://syncevolution.org/sites/syncevolution.org/files/sync_select_service_bluetooth_0.png
[11] https://syncevolution.org/sites/syncevolution.org/files/sync_bluetooth_setup.png
[12] https://syncevolution.org/sites/syncevolution.org/files/sync_bluetooth_setup2.png
[13] https://syncevolution.org/sites/syncevolution.org/files/start.png
[14] https://syncevolution.org/sites/syncevolution.org/files/syncing.png
[15] https://syncevolution.org/sites/syncevolution.org/files/receiving.png
[16] https://syncevolution.org/sites/syncevolution.org/files/complete.png
[17] https://syncevolution.org/wiki/phone-compatibility-template
[18] http://mobileyog.blogspot.com/2010/06/easiest-way-to-sync-your-mobile-phone.html