@untitaker, thanks for finding the duplicate.
@onny Please follow up in #578 and the linked OwnCloud issue report.
I was using DAVDroid on my old phone and it worked perfectly with my baikal server. Unfortunately, after buying a new phone that now runs CM13 (Marshmallow) I regularly experience problems with auto-syncs. Although a 120 minute sync is set up in the settings, DAVdroid stops randomly. The issue will not be fixed until I reboot the phone. I set up the account several times but I had no success so far - DAVDroid finally decides to stop after a few hours / days.
Thank you so much in advance for helping me out.
Is there any other way to trigger the sync manually for DAVDROID (via e.g. crontab)?
Synchronization is managed by Android. DAVdroid doesn’t run all time, it’s just called by the synchronization framework of Android. So, if synchronization is not started, I guess there’s something wrong with Android settings.
You can initiate a sync using the
ContentResolver API, see requestSync().
Is your question answered by the recently created FAQ: Why is synchronisation not triggered as set it in sync interval settings?
Thank you very much for remembering my post. That looks like a good explanation - I will try it out. Hopefully it will work, otherwise I will be spending my vacation with writing a force-sync program.
My response is positive: Switching off the battery saving feature is the solution for the sync-problem. DAVDroid works flawlessl now, again. Thank you!
Hopefully this thread will help someone in the community.
@_GrafZahl_ Thanks for your response. DAVdroid 1.2.2 and newer will ask for exemption from battery optimization to reduce such confusion.