On Thu, 2004-04-08 at 15:28, Michael Below wrote: > Hi Vincent, > > Vincent Frison <[EMAIL PROTECTED]> writes: > > > But I have problems with the SyncML plugin. Has anyone a successful > > story with Multisync/P900 via USB? > > My P800 seems to work alright. Some Evolution addresses still don't > show up on the phone, but syncing the dates works fine. > > > I have followed the instructions published on the Edd Dumbill blog and > > cleaned my p900/evolution addressbook (just one entry for each of them). > > The connection is established, some Syncml data are exchanged, but.. the > > process failed while the P900 syncml client GUI is displaying > > "writting". > > My report to this list was: > ,---- > | Now it does work. I swapped the plugins: Evolution has to be first, > | SyncML second. Also one should select the "always use entry from > | second plugin" conflict resolution method, "ask user" or "use both" > | seem to fail. > | > | When I was able to sync in both directions, I ended up with doublettes > | of each entry in both databases. The doublettes had the name and the > | address of the contact also repeated in the "country" field. To solve > | this, I had to delete each first occurence of an entry in Evolution > | and the second one on the P800. > `----
I have tried many times from yesterday and here is what I can report: 1) Timeouts I don't know BlueTooth effective bitrate but with USB it's pretty slow (10 kB/s max.) and I suspect that may be problematic for heavy addressbooks or calendars. In a previous thread, Dominik Schl�sser have mentioned timeout issue. Bob said the latest CVS releases has improvements regards to the timeouts, so I have tried it (thanks to Packman for the Debian packages) and the result is better i.e. more entries are synchronized, *but not all*! 2) Maximum message size In addition I can saw suspicious messages in the log (export MULTISYNC_DEBUG=1') like this: SyncML: Got modifications (1647 of them). SyncML: Sending modify. SyncML: Got engine cmd: 1 SyncML: Action: 1 0 0 0 SyncML: Maximum message size almost reached (180098 bytes of 200000). As my calendar has thousands of entries (the size of my calendar.ics is more thant 500 kB), maybe there is max. size issue. I don't know the SyncML protocol but it seems to be a limitation from the client side. Maybe the SyncML plugin have some difficulties to "hash" properly the data regarding to the client constraints? 3) Doublette issue This is not harmless!!! I don't known why but some entries are doubled (even tripled) in the Evolution calendar (not in the P900 side). It concerns about hundred of entries, so I think I have to restore an old backup.. Michel how do you manage it? You said you just delete each first occurrence of an entry in Evolution and the second one on the P800, but you don't need to do it after each sync don't you?!? 4) Useless conflicts Maybe it's related to the previous point but I don't think so because I'm using the manual resolution mode so the conflicts should visible when they occurs (and I haven't seen hundred of conflicts). But sometimes there are some conflicts and if I'm looking for differences, I just find escaping issues: \\n <=> \n (I don't remember the sides). It's minor but sufficient for Multisync to consider it as a conflict. In conclusion I'm a little disappointed by the calendar problems, but now the addressbook sync works fine and I can already consider Multisync as a killer app.. -- Vincent ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Multisync-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-users
