@Aurel-P This is always occuring when you import erroneus vcf directly into the Synology. Synology does not correct these vcfs and on DAVx5’s request the server crashes by delivering these data.Please delete the address book. Create an empty one and make a DAVx5 account connected to this new address book. Then import the vcf files directly on Android into this new account. Synchronize Then it should work.
Sync not running automatically
Using davdroid, i saw a bug. Sometimes the schedule sync is not working, as shown on this first screen (see the dates)
To resolve, i just have to open davdroid app and validate the popup like here
When i do it, going back to account and the sync is done…
It seems the popup is making problems ?
- Please use the forum syntax properly, because the links are nearly unusable. There’s a help function (questing mark) on the right top of the edit field. You can also attach files directly, without using another hoster.
- The open-source popup is in no way related to synchronization.
- Android will show “synchronization problems” on soft errors, i.e. if your mobile connection is interrupted during a synchronization. The problem will disappear as soon as another synchronization is done correctly. This may have a random temporal correlation with clicking on popups.
- Please provide steps to reproduce, debug info and verbose logs.
Sorry for delay.
To reproduce, nothing to do. Just have a working caldav/carddav account, and wait some days…
In accounts on android parameters I see the account is not refreshed since days. Forcing manually update do nothing. The only way to make it work again is start manually davdroid app, and it’s resolved, until next time.
Logs will probably show nothing because when I start the debug mode, the app was running so account refreshed…
Here are debug info :
SOFTWARE INFORMATION DAVdroid version: 1.1.1 (104) Wed Jun 22 08:34:09 GMT+02:00 2016 Installed from: org.fdroid.fdroid JB Workaround installed: no CONFIGURATION System-wide synchronization: automatically Account: email@example.com Address book sync. interval: 1440 min Calendar sync. interval: 60 min OpenTasks sync. interval: manually SQLITE DUMP android_metadata | locale | | fr_FR | ---------- settings | setting | value | | hint_OpenTasksNotInstalled | 0 | | logToExternalStorage | 1 | ---------- services | _id | accountName | service | principal | | 1 | firstname.lastname@example.org | carddav | https://hidden/cal.php/principals/nicolas/ | | 2 | email@example.com | caldav | https://hidden/cal.php/principals/nicolas/ | ---------- sqlite_sequence | name | seq | | services | 2 | | homesets | 2 | | collections | 2 | ---------- homesets | _id | serviceID | url | | 1 | 2 | https://hidden/cal.php/calendars/nicolas/ | | 2 | 1 | https://hidden/cal.php/addressbooks/nicolas/ | ---------- collections | _id | serviceID | url | readOnly | displayName | description | color | timezone | supportsVEVENT | supportsVTODO | sync | | 1 | 2 | https://hidden/cal.php/calendars/nicolas/it/ | 0 | IT | <null> | <null> | <null> | 1 | 0 | 1 | | 2 | 1 | https://hidden/cal.php/addressbooks/nicolas/contacts/ | 0 | Contacts | Tous mes contacts | <null> | <null> | <null> | <null> | 1 | ---------- SYSTEM INFORMATION Android version: 6.0.1 (MTC19V) Device: LGE Nexus 5X (bullhead)
Verbose los are attached.
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. Maybe adb logcat would reveal more information.
Is your question answered by the recently created FAQ: Why is synchronisation not triggered as set it in sync interval settings?
It’s probably related to doze mode, but i use my phone very often and when it happens davdroid do not sync for days.
@ouafnico Does it help to turn off doze mode / app standby for DAVdroid? Android settings / Battery / Battery optimization / DAVdroid and then choose “Don’t optimize”.
It seems to correspond to the app standby.
I’ve added davdroid out of battery optimization. I will see…