We have succesfully set up DAVDroid on multiple Nexus 5x devices to sync with the same CALDav / and Carddav account on a Synology NAS.
Unfortunately, using the latest DAVDroid Version we cannot connect to neither the Carddav nor the Caldav service, which works perfectly on the other devices.
Attached are the logs. We hope you can find a solution for other Synology users and ourselves.1_1536599881009_CALDAVdebug.txt 0_1536599881009_CARDDAVdebug.txt
Hello,
@rfc2822
Thank you.
To 1.: I do not have access to the 2.0.4. apk on fdroid yet. I cannot compile myself.
To 2.: As said, we have already used fdroid and multiple Nexus5x clients with the same carddav/caldav account on Synology. No problem so far. So something must have changes in the ressource detection of DAVDroid.
@alig2134 Ok then please wait for 2.0.4, or use an 1.9.x version. Does that work
@rfc2822
Thank you again. Where can I get the last 1.9.x version APK. Fdroid only offers the last few 2.0.x versions unfortunately.
@alig2134 You can use the F-Droid archive, same procedure as described here: https://www.davdroid.com/faq/can-i-use-davdroid-with-an-old-android-version/
Can you tell me whether it works with 1.9.x?
@rfc2822 Excellent.
Just installed 1.9.10-ose from the fdroid repository: Ressource detection took about 4-6 Min, but worked straight away both with CalDAV and with CARDDav. (I then upgraded to 2.0.3-ose maually via fdroid).
So in conclusion something in the present 2.0.3.-ose ressource detection does not work with both Synology’s Carddav as well as CalDavServer (please note I use an older Synology DSM version using the WebDAV server package for CalDAV).
Hope this and my debug logs above help to find a solution for other Synology users. Until then, the workaround with 1.9.10-ose works.
@rfc2822
Apologies, I really admire the work you developers perform here. But I would not call the necessity of a downgrade as a workaround for proper resource detection a “solved” issue.
The actual issue of malfunctioning resource detection with Synology in 2.0.3.-ose still persists.
Is there any plan working on an actual solution to avoid other users having the same problem?
Can you confirm that the problem has been fixed in 2.0.4, which we had already released when I suggested to use 1.9.x until FDroid builds 2.0.4? In the meanwhile, they have built and published 2.0.4. If you want fast updates, I suggest to either compile yourself or download DAVdroid over Google Play.
@rfc2822 THank you again. I can confirm that the problem has been fixed in 2.0.4
Solved! Well done.
@alig2134 Thanks for the update!
