Also, one of my statements above is wrong:
If you delete the entry on the server and change it on your device, the next time DAVdroid syncs it:
tries to upload the contact, which will succeed, syncs all entries from the service to the device, including the newly uploaded. “DAVdroid wins”
Correct is (I have just tested it):
If you delete the entry on the server and change it on your device, the next time DAVdroid syncs it:
tries to upload the contact, replacing exactly the old version that is referenced by its ETag, which will not succeed becaues this precondition fails (because the event is gone), syncs all entries from the service to the device, resulting in the locally-changed event to be deleted. “Server wins”So, the server always wins, which is the desired strategy.