Every now and then, DAVdroid stops syncing without throwing an error. This is very annoying. It’s difficult to know when it happens as I only notice it when I miss an appointment or so… I’m not sure but last time it happened may have been when I updated my OS (auto update of Lineage OS).
When it happens, the only way to have it back working is to delete all accounts in DAVdroid and add them again. Then it works again until… who knows?
The very first priority in a calendar syncing application should be to be absolutely sure that the sync has worked. If there is ANY problem, an error should be thrown! I prefer 100 false errors than one missed appointment!
How can I switch on a notification if it does not sync anymore?
Version: 2.0.1-ose
Hello,
First we’d have to know why the system doesn’t call DAVdroid anymore. Did you had a look at https://www.davdroid.com/faq/synchronization-is-not-run-as-expected/?
Can you please provide debug info, as described in https://forums.bitfire.at/topic/749/read-before-posting-what-s-required-to-diagnose-a-problem?
By the way, please always use the latest version of DAVdroid, see https://www.davdroid.com/faq/how-to-debug/
Thanks for your answer.
Well, the thing is that the system does call DAVdroid sync. I can also sync by hand, in the DAVdroid UI, and I see the bar animation moving for 2-3 seconds. No error, but no sync, i.e. new events are not shown.
I will enable “log to external storage.” and make a manual sync next time it happens. Or would it be better to switch on logging from now on until it happens?
I have now updated to 2.0.4-ose
@mmueller said in DAVdroid stops syncing without throwing an error.:
Well, the thing is that the system does call DAVdroid sync. I can also sync by hand, in the DAVdroid UI, and I see the bar animation moving for 2-3 seconds. No error, but no sync, i.e. new events are not shown.
How do you know that? But let’s wait for the logs and the debug info 
Guessing around without definite information is boring.
Just enable external logging and then force synchronization.
How do you know that?
Because I have multiple accounts in DAVdroid. One of them is only reachable on a particular network. When I’m outside this network, I still get the error notifications for this particular account. That’s why I guess the system is calling DAVdroid.
But let’s wait for the logs and the debug info
Just enable external logging and then force synchronization.
Yes, I will do that as soon as it happens again and new events don’t sync
