ync is a software for syncing your contacts and events from your mobile to your favorite pim application(i.e. evolution). It uses the java microedition to access your pim data and sends it via bluetooth to [multisync http://multisync.sourceforge.net/] or [openync http://www.opensync.org/] on your pc. Multisync can sync your data to many other pim applications, other mobile phones or to any syncml backend.

= Requirements =

* linux/unix box (multisync should be able to run there)
* multisync(0.8x) or opensync 
* a mobile device that runs J2ME (mips 2.0, jsr 75, jsr 82)

= Mobile devices known to work =

* Motorola A1200 (Ming)
(please add your device after testing)

= FAQ =

* Is my mobile device working ? see above and test it!

= Files =

* multisync plugin
* j2mesync java application

J2MESync Midlet for Opensync (0.1x)/Multisync(0.8x) Download is http://www.ohli.de/download/j2mesync_midlet.tar.bz2 

Multisync (0.8x) Download is http://www.ohli.de/download/j2mesync_multisync.tar.bz2 

Opensync (0.1x) Download is http://www.ohli.de/download/j2mesync_opensync.tar.bz2 

Opensync (0.1x) Debian Plugin http://www.ohli.de/download/j2mesync_plugin-1-1_i386.deb (thanks to Kie)

Opensync (0.2x) Download is http://www.ohli.de/download/j2mesync_opensync-0.22.tar.bz2 

Opensync (0.3x) Download is http://www.ohli.de/download/j2mesync_opensync-0.34.tar.bz2 

= Installation (Multisync Part) =

First you should have working linux box with an installed multisync. On many distros you can use your package installer and select it. In case you use the source distro of the j2mesync plugin you should also select the multisync and bluetooth development files(the headers and such things). 

So now we have a multisync installation. Now you have to download the plugin package from this site. 

If you decide to compile the plugin yourself, you have to unpack the file.

0 tar xvjf j2mesync.tar.bz2
0 cd j2mesync_plugin
0 ./autogen.sh
0 make
0 make install
so it's done you can now start to configure multisync.
simply create a sync pair by pressing the new button and select the j2mesync plugin as the first or second plugin. Then press the options button and fill in your bluetooth mac address and the rfcomm channel. Normally the channel is 7 but you can change this on the mobile device. It only has to be the same number here and there. 

Know you have to configure the second plugin the i.e. evolution or backup one.

So the work on the linux box is done and you have to do some work on your mobile device.

First download the jar and jad files from this page and transfer it to your mobile device with your favorite software (some vendors releases special software to install java apps on their devices). It is very importend that the java app have the right permissions the read and write your pim data and open a bluetooth server.

After you have sucessfully installed the midlet, you have to set the bluetooth channel and if you like the directory where you want to store your local backups. 

Congratulations. You are finished! Now you can start the j2mesync midlet on your mobile device and multisync on your unix box and press the sync button. 

= Installation (Opensync Part) =

First you should have working linux box with an installed opensync. On
many distros you can use your package installer and select it. In case
you use the source distro of the j2mesync plugin you should also select
the opensync and bluetooth development files(the headers and such
things). If you are using opensync >=0.30 you need the cmake package as well.

So now we have a opensync installation. Now you have to download the
plugin package from this site. 

case opensync (<0.30)

If you decide to compile the plugin yourself, you have to unpack the file.

0 tar xvjf j2mesync.tar.bz2 
0 cd j2mesync_plugin 
0 ./autogen.sh 
0 make 
0 make install 

case opensync (>=0.30)

0 tar xvjf j2mesync_opensync-0.34.tar.bz2
0 mkdir j2mesync_build
0 cd j2mesync_build
0 cmake ../j2mesync-plugin
0 make
0 make install

so it's done you can now start to configure opensync. If you are mysynctool, you create a pair by doing:

0 msynctool --addgroup mygroup
0 msynctool --addmember mygroup j2mesync-plugin
0 msynctool --addmember mygroup otherplugin
0 msynctool --discover mygroup 1 (for opensync >=0.30)
0 msynctool --discover mygroup 2 (for opensync >=0.30)
0 msynctool --configure mygroup 1
0 msynctool --configure mygroup 2

now you get an editor with a xml config file. simply add your bluetooth mac
addr(you get it by running "hcitool scan") and the bluetooth channel(normaly 7).
If your otherplugin doesn't need any configuration you can start syncing by :
0 msynctool --sync mygroup

So the work on the linux box is done and you have to do some work on
your mobile device.

First you need a working Wireless Toolkit from sun 
(http://java.sun.com/products/sjwtoolkit/ ). With this
you are able to open the project in the java directory and build the
java part. Now you can transfer the jar and jad to your mobile device
with your favorite software (some vendors releases special software to
install java apps on their devices). It is very importend that the java
app have the right permissions the read and write your pim data and open
a bluetooth server.

After you have sucessfully installed the midlet, you have to set the
bluetooth channel and if you like the directory where you want to store
your local backups. 

(you can find the jar/jad files in the j2mesync-plugin archives above in the java folder)

Congratulations. You are finished! Now you can start the j2mesync midlet
on your mobile device and multisync on your unix box and press the sync
button. 

== Some Things you should know ==
0 the syncing is not very fast (at least not on my ming device) because the phone has to serialize data from it's internal memory.
0 i have to press "yes" many times because i have to acknowledge every type of write access (at least one time). Hopefully you can disable that or acknowledge them at the start
