23.06.2015 Pavel Rojtberg:
its just in the root of the repository… but I can put an additional
downlaod link in the readme.
Thank you very much for your effort and support! I deeply appreciate this!
Cheers to you
Roy
See http://stackoverflow.com/questions/14522393/android-exdate-format-when-adding-a-calendar-event
Android has a very own implementation of the EXDATE property which causes that 1:1 synchronization of iCal events with EXDATE Android calendar provider EXDATE doesn’t work.
DAVdroid could (should?) rewrite .ical EXDATEs so that they are understood by the Android calendar provider.
I can reproduce the problem using my DAViCal server. The problem is also present when using AndroidCaldavSyncAdapater https://github.com/gggard/AndroidCaldavSyncAdapater. It is not surprising if it is a bug in Android and not in the sync adapter themselves.
More info for this problem: DAVDroid 0.5.2 on my phone (Android 4.0) and tablet (Android 4.3) against a DAViCal server. Modifying an instance of a repeating even works correctly on the device used to modify it, but the change is not properly synced. Steps:
If I delete the rescheduled instance using CalDavZAP, then DAVDroid:
As this is not a DAVdroid problem and there are far more important issues, I’ll close this for now.
Reading the corresponding kolab feature request, I wonder whether a workaround is even possible.
This unanswered Stackoverflow question sounds related.
Also, these two issues point to the Google Product Forums. The only forum that sounded somehow suitable was the one for Nexus devices, so I posted the problem there.
Note: should be implemented with 5b7947034a656c463ca477e198f7728cccc9e4c1
I have now testing DAVdroid 0.8.3 against Kolab (kolabnow.com) again, and I am generally happy:
So: Thank you!