On Mon, 2012-08-13 at 21:02 +0200, Patrick Ohly wrote: > On Mon, 2012-08-13 at 13:44 -0400, Ross Vandegrift wrote: > > This has partially broken sync with my S40 phone. It imposes a max > > message size of 3k, and the images push those contacts over the limit. > > Syncevolution notices this: > > WARNING: outgoing item is larger (5334) than MaxObjSize (3000) of remote > > -> suppress now/mark for resend > > A small message size would lead to splitting of items. But the phone > also imposes that size for every single item, and therefore larger items > can never be sent.
In that circumstance, if one oversized item is too large, are all changes to the contact reverted? I updated two contacts, one with photo and one without. I added an email to both. Google and Evo show the updated data correctly, but after syncing with the phone, only the photo-less contact has been updated. > > The sync mostly works, but takes around 15 minutes to finish. The > > first time, my phone's progress indicator stuck at 95% complete. On > > subsequent syncs, the phone finishes quickly but syncevo still waits > > for 15 minutes. Oddly, the times in the log do not reflect this. > > Could this be because of dumping data? When you run SyncEvolution > 1.2.99.x on the command line, you should see some output indicating that > it is busy doing these data dumps (usually enabled for the automatic > backup feature). Yea - terminal says that, and disabling dumpData and printChanges fixes the delay. It seems weird that the backup is taking so long - prior to the photos being added, backups took no more than 5 or 10 seconds. [snip] > Actually, there is probably an easier way. Can you look at a > syncevolution-log.html and send me the model and manufacturer string of > your phone? Sure - the log records the reported model as "Nokia 3720c". In case the software version matters, that is recorded as "V 10.16 07-12-09 RM-518 (c) N." > I'm going to try updating the script files so that for this phone, PHOTO > data is stripped before encoding the data as vCard. Further work will be > needed to ensure that receiving an update from the phone the photo is > not removed on the host. That sounds good to me - I'm happy to test anything you need. I gave it a shot, and think I have the right idea, but can't figure out how to put the pieces together. Thanks, Ross
signature.asc
Description: This is a digitally signed message part
_______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
