@fmbonobi Thanks for the debug info, looks good (nothing special there).
The verbose log contains everything DAVx⁵ does, so if it does “too much”, it will be logged there.
Please see the image on https://www.davx5.com/faq/how-to-debug, there’s a screenshot how you can activate verbose logging. It’s as well described in https://forums.bitfire.at/topic/749/read-before-posting-what-s-required-to-diagnose-a-problem:
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).