Dear Multisync and S55 (possibly others) users,
I share all the experience listed in this thread (See 1.), on which I
have some further observation, but I also have some additional
misbehaviour to notify (See 2.).
1. Concerning the capability of S55 of understanding VCARD 3.0:
I experimented by taking all the TYPE=XXXXX strings off the Vcards and
just leaving the XXXXX strings. Then uploaded the resulting vcards to
the S55 via BlueTooth and, at that point, the S55 was actually able to
store and classify all the contacts correctly.
So, apparently, the only protocol difference which is really essential
to handle to avoid scrambling the cellphone phonebook is getting rid of
the 'TYPE=' string
2. Auto-sync stopped working on Evo2 and related plugin
I used to keep multisync always on with auto-sync on, with each change
on Evolution being propagated to the phone within 5 seconds (dwell time)
to the cellphone.
This immediate, Evo2 change-initiated auto-sync does not work anymore
with Evo2 + related plugin. Only the periodic sync works now.
Hope this information can be useful to trigger some update in the
plugin.
Regards and Merry Christmas wishes to all!
Marco Bravi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Multisync-users mailing list
Multisync-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/multisync-users
