On Thu, 2012-02-16 at 09:07 +1300, Jane Atkinson wrote: What changes are these? In Evolution? Contacts or calendar? Are you perhaps synchronizing a CalDAV calendar in Evolution with the phone? There was a problem like that with CalDAV calendar where Evolution Data Server did not refresh its copy of the data the first time that SyncEvolution asked for the calendar. commit 7110d70033c06804ae24b421c4f190dc40254b5f Author: Patrick Ohly <patrick.ohly(a)intel.com&gt; Date: Wed Dec 15 12:48:34 2010 +0100 Evolution Calendar: work around delayed update in EDS CalDAV backend (BMC #10265) Running a sync with EDS CalDAV backend as storage to be synchronized ignored changes made before the sync. Running the sync again then found the changes. It seems that the EDS CalDAV backend triggers a refresh from the CalDAV server after the client is done, instead of doing that in e_cal_open(). As a workaround, this patch destroys the newly opened calendar instance and opens it again. This is done for *all* backends, because it is cheap for local storage and other remote storage backends might have the same issue. Please create logs at loglevel=4. -- 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.