Re: Problems with Evolution 2 and Siemens SL55

Tom Parker wrote:

>Tom Parker <[email protected]> wrote:
>
>  
>
>>I'm having some trouble with Multisync, Evolution 2 and a Siemens SL55 via
>>IrDA on Debian testing. This configuration worked well until a recent update,
>>however I don't sync very often so I can't be sure when the problem started.
>>It could have been introduced in debian testing a month or two ago.
>>    
>>
>
>If I'd done some more digging, I would have found that this is a known
>problem!
>
>http://sourceforge.net/mailarchive/forum.php?thread_id=6221779&forum_id=12899
>
>Has anyone solved it in a hackish kind of way? I understand most
>development focus has shifted to opensync related work? The above thread
>suggests that all I need to do is change the version number of the VCARD to
>2.1 during the transfer. I haven't looked at the multisync code, but this
>shouldn't be too hard to do. I'm enough of a C programmer to do it tomorrow if
>there isn't already a solution.
>
>  
>
i dont think that there is a solution already for the current multisync 
version. After all i also started opensync to be able to fix these 
problems without applying a major hack each time.

>Also this thread meantions that tasks are not syncing properly either. I've
>found this is still the case. Does anyone have any insight into this problem?
>
>Can anyone explain the functionality of the "resync" button. I've used that a
>couple of times and I've also created brand new sync pairs and used the
>normal sync. In the process I have duplicated my tasks, and my appointments
>and some of my contacts. Is the duplicate checking code supposed to prevent
>this? I was asked about some near duplicates and possibly some actual
>duplicates, but the vast majority of appointments were silently duplicated. I
>believe I used the debian packaged version of multisync for this test, rather
>than the CVS compiled version. Is there a bugfix missing from the debian
>package?
>
>  
>
no i dont think that the debian package is missing bugfixes. The 
duplication checking code in the current multisync is very simple and 
wont catch duplicates in a lot of cases.

The "resync" button does a slow-sync. This means that each device is 
queried for all items (instead of only the changes). This helps if the 
device does not return the changes but might lead to duplication.

>At the moment multisync is mostly useless for me, and my phone has only the
>year old addressbook that my last phone put in the sim card :-( I'm also
>getting a bit nervous about syncing as it does more damage to both my phone
>and my evolution data every time :-(
>
>  
>
>--
>Tom Parker - [email protected]
>           - http://www.carrott.org
>
>
>
>-------------------------------------------------------
>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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>_______________________________________________
>Multisync-users mailing list
>Multisync-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>https://lists.sourceforge.net/lists/listinfo/multisync-users
>  
>



-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click