If you have a problem with DAVx⁵, please:
Try the latest DAVx⁵ version. Use the latest version of your server software, if applicable.
Read the Configuration, FAQ and manual pages carefully. The most common issues are explained there.
Try the forum search – most questions have already been answered.
Have a look at the debug info/error details/logs. You can often get an idea what’s the problem yourself.
Search the the Web for the problem, maybe ask friends who are willing to help.
Make sure that it’s not a server or networking problem. Search the FAQ/forums/bug tracker of your server software, too. Many supposed DAVx⁵ bugs are server or networking problems.
See also: FAQ: How to debug DAVx⁵-related problems
When posting, please provide as much information as you can:
Go to DAVx⁵ / Settings (left navigation drawer in the main screen) / Debug info. Send these information to yourself (using the “Share” action, for instance by email). Paste the info to fpaste.org or a similar service and provide a link. It contains the most important information about your device and configuration.
Describe exactly what you were doing (steps to reproduce), what you tried to achieve and what your problem is. Imagine someone else who wants to reproduce the problem to find a solution and provide all necessary information.
Give information about your environment: what is your server software (including version), what are your calendar URLs, do other clients work, etc.
If possible, try to explain what you already have tried to solve your problem.
If you get “No CalDAV/CardDAV service found” when you try to add an account:
Tap “View logs”. Send those logs to yourself (using the “Share” action, for instance by email).
Paste the logs to fpaste.org or a similar service and provide a link (feel free to let it expire in a month).
If you get an error notification while synchronizing:
Tap the notification. A debug info activity will appear.
Send the debug info to yourself (using the “Share” action, for instance by email).
Paste the debug info (≠ logs) to fpaste.org or a similar service and provide a link (feel free to let it expire in a month). Short debug output can be inserted in the text, but please quote with ``` (at the beginning and the end).
If additional logs are required to diagnose the problem, continue below.
Your problem doesn’t cause a notification or you need verbose logs?
DAVx⁵ / Settings (left navigation drawer in the main screen) / Enable “Verbose logging”. A permanent notification tells you that logging is now active.
Do whatever causes your problem (e.g. “Refresh calendars”, or initiate a sync).
Use the notification to share the log. You may have to expand the notification to see the “Share” action.
Send the logs to yourself (for instance by by email, or with Share with HTTP).
Remove private data from the logs, if applicable.
Paste the logs to fpaste.org or a similar service and provide a link (feel free to let it expire in a month). Short parts of the logs can be inserted in the text, but please quote with ``` (at the beginning and the end).
If your problem has been solved, it would be kind to let other people (who were willing to help you) know the actual solution.
notify on invalid tasks/vCard objects (events will follow)
add app setting for notification channels: Notification settings (only Android 8+)
use default time-zone to store floating DATE-TIMEs
exceptions of recurring events: use main event’s DTSTART time zone for RECURRENCE-ID
minor improvements and bug fixes
When you tap a notification about invalid iCalendar/vCard objects, you can see more information, including the URL of the invalid object. You can hide all “Sync warnings” in the app notification settings (Android 8+ only, because this depends on notification channels), but we recommend to care about these messages, because it means that some events/tasks could not be synchronized.
did you read the help page for synchronization problems? I strongly suggest a read of this page because you have a Xiaomi device. Does it help?
I had the same problem where I was able to enter my account in davdroid and Davdroid itself successfully found all my calendars, however none of them would sync with the phone’s calendar programs (both the native calendar and e-tar). Seems like a bug / change in android 7 broke calendar syncing. I was unable to get davdroid to work for months, however now that there’s a new DAVx5 client I decided to try it. They fixed it! The link is broken in the fdroid repo’s BTW, however I managed to install davx5 manually and everything’s working. So if anyone else has the same issue, give the new davx5 a shot!
@Kim-Heinrich “Synchronization with Google CalDAV/CardDAV is not officially supported by Google or DAVx⁵. For some people it seems to work, for others it doesn’t. Google officially requires OAuth 2, which is not supported by DAVx⁵.” If you have suggestions for better wording, please let us know. Of course you can always get a refund, although those Google problems costs us work time without any benefit. Just write to email@example.com or in forum chat
Thanks for your response.
I’m on a local network. Whenever I need to sync, I turn on WiFi and disable mobile data. This is the way I’ve been syncing successfully for some years, until this issue started to occur.
I’m able to access my Nextcloud server’s web interface, I can also refresh the calendar, as I said in my post. And certainly I can reach the CalDAV URL from my browser (I get an error about the GET method not being supported, as expected).
Thanks for the screenshot. I was looking in the wrong place (system settings -> accounts). However, I really think that I had tried this button, with no effect (but I can’t test this anymore), so forget it.
Anyway, the current label in French does not have exactly the same meaning:
In this screenshot it is “adressbücher neu erkennen” which I suppose could be translated by “discover new address books” (it is a guess based on what I found in online translators)
in French it is “Actualiser le carnet d’adresses” which would be literally translated by “update address book”.
I am using DAVx5 220.127.116.11-ose(267). So I joined Transifex to check the translations, and indeed, the German translation has the good meaning. I just updated the French translation to fix this issue (strings 103 and 105):
Refresh address book list -> Actualiser la liste des carnets d’adresses
Refresh calendar list -> Actualiser la liste des calendriers
Synchronization with Google CalDAV/CardDAV is not officially supported by Google or DAVx⁵. For some people it seems to work, for others it doesn’t. Google officially requires OAuth 2, which is not supported by DAVx⁵.
We have received updated information about Google CalDAV:
The old endpoint https://www.google.com/calendar/dav is deprecated and no longer supported.
Now you shout suggest https://apidata.googleusercontent.com/caldav/v2/calid/events
Please have a look on https://developers.google.com/calendar/caldav/v2/guide
Google Account security:
If you use 2-Step-Verification for your Google account (recommended): Create an app password for DAVx⁵ and use the app password for signing in with DAVx⁵.
If you’re not using 2-Step-Verification: To allow Basic auth clients like DAVx⁵ to connect, you need to “Allow less secure apps” in your Google account before setting up DAVx⁵.
If you have further information, please just post here.
So I’m trying to connect DAVX5 with a Nextcloud service on an onion address but run into some problems. I’ve got version 18.104.22.168 of DAVX5 from Fdroid and version 15.0.7 of Nextcloud. And as I said I’m running it as hidden service so I need to connect to an .onion address and on the same device I’ve got Orfox and with I can connect to the onion address. But not with DAVX5. I get HTTP 405 Method Not Allowed. When I look into the apache logs on the server there is nothing special there at all.