OpenSync
From openSUSE
| This article needs to be expanded. If you can help please do so in line with the openSUSE Style Guide.
If you are looking for something to do, see the other articles that need expanding |
Contents |
Introduction
OpenSync is a synchronization framework that is platform and distribution independent. It consists of several plug-ins that can be used to connect to devices, a powerful sync engine, and the framework itself. The synchronization framework is kept very flexible and is capable of synchronizing any type of data, including contacts, calendar, tasks, notes, and files.
OpenSync is still under heavy development. The project is still looking for more developer and testers. The current state of the OpenSync project is not a "productive state".
|
Plugins
In openSUSE 10.2 we will have 14 OpenSync plugins. Some plugins are still experimental and don't have a configuration dialog in the graphical frontends. This requires that you have to configure it with msynctool. Please read the README for further instruction how to configure the plugin. And which known problems and issues exist.
Evolution
The Evolution plugin (evo2-sync) allows to synchronize with the evolution-data-server Contact, Events and Todos with the OpenSync framework. evo2-sync.
File-Sync
The file-sync plugin is intended to synchronize all kind of data (all object types), like events, contacts and todos , directly to the file-system. It is also intended to create Backup of your mobile device. For more details see file-sync.
Gnokii-Sync
The gnokii-sync plugin is based on libgnokii from the gnokii project. The gnokii project provides many connectivity functions for Nokia mobile phones. This plugin should be used for older Nokia mobile phones which don't support SyncML. For more details and supported devices see gnokii-sync.
Google-Calendar
This plugin allows to synchronize your Google Calendar with the OpenSync framework. More details can be found at Google-Calendar
GPE
This plugin allows GPE Palmtop Environment based devices to synchronize with the OpenSync framework. More details and supported devices can be found at GPE
IrMC-Sync
This plugin allows applications using OpenSync to synchronize mobile phones with IrMC support. IrMC synchronization is mostly used by Siemens and Sony Ericsson mobile phones. For details about the plugin and supported devices see irmc-sync.
KDEPIM
The kdepim-sync plugin is intended to synchronize the KDE PIM applications like kaddressbook, korganizer and knotes with other OpenSync plugins kdepim-sync. Hint: kdepim-sync doesn't have/need any configuration yet (version 0.20)
Moto-Sync
This plugin is intended to synchronize Motorola mobile phones via the AT command set. Present Motorola mobile phones, like the Motorola Razr V3, only support synchronize with SyncML via HTTP. The moto-sync plugin solve this fact and allows a local synchronization. For details about the plugin and supported devices see moto-sync.
Opie-Sync
The opie-sync plugin allows OPIE based devices to synchronize with the OpenSync framework. For more information about OPIE:
More details about the opie-sync plugin and supported devices can be found at opie-sync.
Palm
The palm-sync plugin is based on libpisock from pilot-link project. The palm plugin is intended to synchronize Palm OS based devices like PalmOne, Tungsten, Treo, Sony Clie and others. For more details see palm-sync.
Python Module
This is actually not a synchronization plugin. The python module is the OpenSync interface for python plugins like moto-sync.
Sunbird
The Sunbird plugin synchronize WebDAV (Mozilla Calendar) with the OpenSync framework. For more details see Sunbird.
Synce
The Synce plugin is based on the libraries of the synce package, which allows to synchronize Windows CE and Window Mobile devices. For more details and supported devices see synce.
SyncML
The SyncML plugin actually consists of two parts. SyncML OBEX Client and SyncML HTTP Server. SyncML HTTP requires to setup a network connection between the host and the mobile phone. Also additional configuration on the mobile phone side is required for HTTP synchronization.
Frontends
There are three frontends for the OpenSync framework at the moment. The KDE and GNOME frontends share the names of their ancestors.
Kitchensync
KDE frontend for the OpenSync frontend which replaced the kitchensync from the kdepim3-sync package in openSUSE 10.2.
Multisync (multisync-gui)
GTK frontend for the OpenSync frontend and is called like the ancestor. Multisync 0.82 is also available for openSUSE 10.2. To avoid conflicts the package OpenSync frontend package is called multisync-gui. (For most plugin a configuration dialog is missing in Beta 2. This will be improved in the next releases.)
msynctool
Command line interface for the OpenSync framework and very powerful. Mostly used for developing and debugging.
Supported Devices
Feel free to add your device and the working plugin in this list. To help other users to choose the right plugin.
3COM
| Model | Firmware | Plugin |
|---|---|---|
| Palm V | | palm-sync |
Handspring
| Model | Firmware | Plugin |
|---|---|---|
| Treo 270 | 3.5.2H5.7 | palm-sync |
Motorola
| Model | Firmware | Plugin |
|---|---|---|
| Razr V3 | | moto-sync |
Nokia
| Model | Firmware | Plugin |
|---|---|---|
| 6300 | v5.0 | SyncML-OBEX-Client |
| 6230 | v5.50 | SyncML-OBEX-Client |
| 6230 | < v5.50 | Gnokii-Sync |
| 6230i | v3.70 | SyncML-OBEX-Client |
| 6233 | | SyncML-OBEX-Client |
| 6822 | v4.52 | SyncML-OBEX-Client |
| 9300 | v5.22(1) | SyncML-OBEX-Client |
| 9300i | v6.27 | SyncML-OBEX-Client |
Palm Inc
| Model | Firmware | Plugin |
|---|---|---|
| Tungsten X | 5.4.9 | palm-sync |
Siemens
| Model | Firmware | Plugin |
|---|---|---|
| SL55 | | irmc-sync |
| M75 | | irmc-sync, msynctool |
Sony Ericsson
| Model | Firmware | Plugin |
|---|---|---|
| K750i | | irmc-sync |
| K750i | | SyncML-OBEX-Client |
| V800i | | irmc-sync |
FAQ
Links
The OpenSync project

