[Reposted again from my home account, the original seems to be
stucked somewhere in the cyberspace]

Hi all,

I am trying to synchronize my new Sony Ericsson P900 with evolution
using SyncML (I am also using multisync, with very good results,
to synchronize between Opie and evolution).

I am using Multisync 0.82 on a Fedora Core 2.

The synchronization beginnings have been difficult (I experienced
a lot of timeout problems leading to incomplete synchros, leading then
to duplicates etc), until I did the following steps (detailed in 
case someone else is interested):
        * empty all calendar/todo/agenda entries on the P900
        * in Evolution, select all contacts and export to vcard into
          a backup file somewhere.
        * exit Evolution, 'killall bonobo-activation-server
          evolution-wombat evolution-alarm-notify'
        * backup evolution/local/Calendar/calendar.ics and
          evolution/local/Tasks/tasks.ics 
        * rm -rf evolution/local/Calendar/* evolution/local/Contacts/*
          evolution/local/Tasks/*
        * now you have an empty P900 and an empty evolution
        * rm -rf ~/.multisync (or manually remove the old ids and
          local/remote changes files)
        * launch multisync, configure the conduit (first Evo, nothing
          to change, second SyncML, use http and set a user/pass),
        * check the 'Auto' checkbox besides the Evo <-> SyncML conduit
        * do a sync from the P900 (you have to configure the remote
          sync on the P900, set host URL/user/pass as choosed, set
          calendar/tasks to sync with 'calendar', set contacts to
          sync with 'addressbook'
        * launch Evolution, import the backuped vcard file containing
          the contacts
        * sync
        * Import the backuped calendar.ics into evolution
        * sync
        * Import the backuped tasks.ics into evolution
        * sync
That's it ! Now you should have all entries into both Evolution and
P900. 

If something goes wrong, restart from the beginning (empty up both
Evolution and P900, recreate the multisync conduit, resync ...etc).

Now some caveats/bugs:

* when a calendar entry is synchronized from Evo to the P900, a 
'note' entry is added on the P900 (then propagated back to Evolution)
containing the Summary. Could a filter be written to not send this
information to the P900 ?

* same goes for the vcards, and it is even worse: each entry on the 
P900 is appended with a note containing the name + the addresses of
the entry. The result is that on the P900 each entry has the name
and the addresses displayed twice. I'm not sure exactly why and what
information is duplicated by the P900 (the FN: for sure, but I don't
know for the addresses).

* a serious bug: when a new contact is created in Evolution, it will
not show up in the P900 if you choosed to sync both calendar and 
the addressbook. If you sync only the addressbook it will show up.
The reason for this, looking at the multisync debug output, is that
the P900 does the sync in two passes: first it asks for calendar
modifications, then is asks for addressbook modification. Multisync
should present the new card in the second step but, judging from the
traces, it presents it on the first step. The P900 ignores it
(as it should since it doesn't expect a vcard), and Multisync marks
it as sended, so it will not be send again when P900 asks for
new/changed contacts.

This last bug is a serious one. I can provide full logs if one
of the developers is interested and cannot reproduce.

Stelian.
-- 
Stelian Pop <[EMAIL PROTECTED]>
Alcove - http://www.alcove.com



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Multisync-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/multisync-users

Reply via email to