On Wed, 2012-02-15 at 11:47 +0200, Juha Pahkala wrote: > I'm trying to use syncevolution http server to sync may Android phone > (Nexus S) to my Evolution backend. On the Nexus I use the Funambol > SyncML client for Android.
Beware that previous attempts to sync with that client failed because of SyncML protocol violations in the client. It seemed to be written specifically for the Funambol server. It might be better now. Your problem however is something else. > I'm using Ubuntu 11.10 distribution and I've > compiled version 1.2.2 of syncevolution using configuration: > > ./configure --prefix=/usr --enable-gui --enable-dbus-service > --disable-ecal --disable-ebook --disable-shared > > I've tried following various HOWTO:s to no avail. From the mailing list > archives I've gatherd, that this one: > > http://syncevolution.org/wiki/synchronizing-evolution-http-howto > > should be the up-to-date one. Is this correct? No. It's the one "to keep a phone in sync with Evolution". It's based on the assumption that you are using Evolution Data Server, which you explicitly disabled. I know that this can be confusing, so the HOWTO above explicitly says "Setting up SyncEvolution as such an intermediary on an Internet server is explained in another HOWTO": http://syncevolution.org/wiki/http-server-howto Do you have a suggestion how such a misunderstanding can be avoid in the future? > Anyhow, when I try to sync my phone, using a minimal config from the > HOWTO, I get the following: > > jpahka@laptop:~$ rm -fr .config/syncevolution > jpahka@laptop:~$ syncevolution --configure --template SyncEvolution_Client \ > > --sync-property remoteDeviceId=fac-355031040909281 \ > > --sync-property username= \ > > --sync-property password= \ > > --source-property addressbook/uri=contacts \ > > nexus The key difference in the HOWTOs is that the configuration you are quoting here implicitly uses the backend=addressbook, which doesn't work without the EDS backend. Please have a look at the other HOWTO, it shows how to set up the file backend instead. > jpahka@laptop:~$ > jpahka@laptop:~$ syncevo-http-server http://127.0.0.1:9000 > > [INFO] syncevo-http: new SyncML session for 192.168.10.52 > [INFO] sync: matched deviceID fac-355031040909281 against config nexus > (/home/jpahka/.config/syncevolution/default/peers/nexus) > [INFO] sync: todo: inactive > [INFO] sync: memo: inactive > [INFO] sync: addressbook: inactive > [INFO] sync: calendar: inactive [...] > And indeed, there seems to be no sources active in the configuration. I think that's a side effect of not having a functional backend for these sources. They are not activated unless that check succeeds. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
