On Mi, 2011-04-20 at 10:34 +0100, HeviiGuy wrote:
> After having suffered a BIG crash and then re-installing everything,
> my previously-temperamental syncing of calendar items and memos is now
> non-existent (thanks to recent assistance, my "contacts" sync well!).
> If anybody is successfully syncing with a Nokia N86 8MP, could you
> please post the config settings which you are using. If nobody has
> this phone, typical config settings from other Nokia owners would
> likely be very helpful as well so that I can try various
> possibilities.

The included Nokia template should work fine for the N86. How did you
set up your config? If you followed some howtos on the web about
manually creating config files, please, ignore them. Most of that tends
to be more complicated than it has to be and gets stale.

> If this may help, here are my present settings:
[...]
> /peers/myfone/sources/calendar/config.ini
> sync = two-way 
> type = calendar:text/calendar
> uri = Calendar
> 
> /peers/myfone/sources/calendar+todo/config.ini
> sync = none
> type = virtual:text/x-calendar:1.0
> uri = Calendar
[...]
> /peers/myfone/sources/todo/config.ini
> sync = disabled
> type = todo
> uri = task

This will break if your phone has tasks in its "Calendar" database,
because you disabled the splitting of tasks and events into separate
databases. Eventually Evolution will complain about not being able to
store some task item. The config should be instead:

/peers/myfone/sources/calendar/config.ini
sync = disabled
type = calendar:text/calendar
uri =

/peers/myfone/sources/calendar+todo/config.ini
sync = two-way
type = virtual:text/x-calendar:1.0
uri = Calendar

/peers/myfone/sources/todo/config.ini
sync = disabled
type = calendar:text/calendar
uri =

> /soures/calendar+todo/config.ini
> type = virtual:text/x-calendar:1.0
> evolutionsource = HeviiCalendar,HeviiTasks

This has to be "calendar,todo".

-- 
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

Reply via email to