Re: [SyncEvolution] testing phone sync

Chen Congwu wrote: Close, but it's actually "Server ID" on the phone that needs to match "remoteIdentifier" on syncevolution peer config. I tried "PC Suite" first but the phone wouldn't let me: It seems there's a hidden PC Suite profile already but I can't see it. This is probably because I've never used PC Suite. Anyway, matching "Server ID" to "remoteIdentifier" actually got me a response. The resulting error was the same as before but at least there's huge log file now :) $ syncevolution nokia-n85 invalid tag <client> at line 1429 col 2 [INFO] todo: inactive [INFO] calendar: inactive [INFO] addressbook: inactive Local data changes to be applied to server during synchronization: *** memo *** no changes [INFO] Server sending SAN 1 invalid tag <client> at line 1489 col 2 [ERROR] OBEX Request 3 got a failed response Forbidden [ERROR] ObexTransprotAgent: Underlying transport error [INFO] Aborted with unexpected result (20015) That 20015 is LOCERR_WRONGUSAGE. I've filed a bug on this: http://bugzilla.moblin.org/show_bug.cgi?id=8782, we can continue there. - Jussi