Re: [SyncEvolution] N9 Bluetooth sync incomplete, 500 status for Delete (was: Re: syncevo-dbus-server dies - SIGPIPE)
Am Donnerstag, den 03.11.2011, 14:57 +0100 schrieb Patrick Ohly:
On Thu, 2011-11-03 at 13:28 +0100, Frederik Elwert wrote:
> >On Wed, 2011-11-02 at 15:00 +0100, Frederik Elwert wrote:
> >> >On Mon, 2011-10-31 at 13:57 +0100, Frederik Elwert wrote:
> >Can you try again with "refresh-from-server" for
"calendar+todo"?
>
> I tried again with calendar+todo.
>
> A subsequent normal sync again did a slow sync.
That shouldn't have happened. The refresh-from-server sync completed
without errors, at least as far as the server can tell. But then in the
next sync, the N9 sends the old, obsolete anchor as if the
refresh-from-server sync had failed.
I tried with a Noki N97, which worked fine.
As far as I can tell, the N9 Bluetooth SyncML is not working properly
when it comes to calendar data. Another reason not to use it is the
limitation to vCalendar 1.0. That will be problematic in combination
with different time zones and detached recurrences.
A better solution is probably to set up SyncEvolution as HTTP SyncML
server and use SyncEvolution also on the N9.
Okay, sad enough. I was more than happy that direct sync seemed to work
without the need to install additional software. And AFAIK,
syncevolution on the N9 currently only provides a command line
interface. I understand that it still is the technically superior
solution, but I think I will stay with end user solution for now,
despite its limitations.
However, thank you very much for the help!