On Mo, 2010-02-15 at 07:10 +0000, Eildert Groeneveld wrote: > There are a number of questions, the answers to which might put me on the > right track. > should the following work or are there other options: There are many different options. You have different, mostly independent choices to make: * use SyncEvolution on the N900 vs. the builtin SyncML support: * using SyncEvolution allows us to analyze and fix problems, whereas the builtin one is closed source * the builtin one can be access from a desktop via Bluetooth, which does not work with SyncEvolution * use Bluetooth vs. HTTP/IP: one is easier to use, the other faster * use desktop or N900 as SyncML server: better use the desktop with SyncEvolution as server, because of the bug fixing aspect * initiate the sync on desktop or N900: personal preference, but not depends on some of the other choices There are some limitations: * When initiating the sync on the desktop, Bluetooth and the builtin SyncML client have to be used. * Setting up a desktop to accept connections from the N900, either via Bluetooth or HTTP, is more complex, but possible. * Last but not least, there is no stable Akonadi backend yet. It is being worked on by Sascha Peilicke, though. * Only SyncEvolution 1.0x can act as SyncML server. > 1. syncevolution direct: N900<->laptop (kde4.4/kubuntu) > > seems to work going by the documentation > is that so? The Akonadi backend is not stable yet. > only via BT? You could run SyncEvolution's syncevo-http-server.py on the desktop, then contact it with SyncEvolution as SyncML client on the N900. See http://syncevolution.org/development/http-server-howto > syncevolution from 30.1. would be running in the N900 > on the laptop 1:0.9.2+1.0beta1 You need 1.0x on the laptop. > 2. syncevolution n900 -- google -- laptop > > same packages as above Google only supports contact sync via SyncML. > 3. akonadi on the laptop side again syncing with google Depends on the Akonadi backend and is limited to contacts by Google, but would work. > Which would be the best route to follow? The easiest solution is to use SyncEvolution 1.0x as SyncML server on the laptop. How well it works depends on the builtin-SyncML support, which has not been tested much. > Thus far, I have not been able to sync the N900 with google: I cannot > establish contact, eventually syncevolution times out on the N900. > For configuration with google: > sync url and web url are as proposed by syncevol > the other specs are: > username: tredlie(a)googlemail.com > password : xxxxxxx Does it time out because there is no connection established or because SSL verification fails? > contacts database: contacts (what actually should go in here?) That's correct. > calendar database: left empty at this stage ( (what actually should go in > here?) > notes: not set Not supported by Google, leave emtpy and don't enable them. > other fileds : normal Sync > > can this be expected to work? If yes: any idea what might be wrong? > Is there a log somewhere? Yes, in ~/.cache/syncevolution. On the command line, use "--print-sessions".

On Mo, 2010-02-15 at 15:01 +0000, Eildert Groeneveld wrote: > Patrick > > thanks so much for your response! > > Choices are good but in the end I need to pick one; so let me try to > narrow the options down to one, which I would then try to pursue. > (remember, the objective is to sync kdepim on the my laptop with the N900 > phone.) > > 1. use SyncEvolution on the N900 ( 0.9.2-3) > 2. use the desktop with SyncEvolution as server (syncevolution-1.0beta1 > > > 3. initiate sync on the desktop - requires (at this stage) Bluetooth > > - you write Bluetooth and the builtin SyncML client have to be used > > is that the builtin SyncML client on the N900 not the SyncEvolution > 0.9.2-3? > > does this make sense? Choice 3 (initiate from desktop) conflicts with choice 1 (use SyncEvolution on the N900). You'll have to use the builtin SyncML client on the N900. This has been reported to work, but without detailed testing. > If yes, how can the KDE kalendar and addressfiles etc be linked to > syncevolution? You'll have to wait for Sascha Peilicke or someone else to finish, test and support the Akonadi backend.

Please ask me again when the KDE support in SyncEvolution is in place. By that time we might have done more thorough testing of the builtin SyncML support in the N900. That would be my recommended solution, if it works well enough.