@rfc2822 The reason why I first want to try out entering the IPv6 address directly is to avoid the switching from IPv4 to IPv6 (what is the preferred protocol for your okhttp implementation?) or IPv6 gateway mechanisms (4 to 6) behind the URL that I am using.
Since yesterday, davx5 drains my battery significantly. (About 25% a day).
I haven’t got any problem before.
With or without the option optimize the battery, same result.
I’m on android 9 and last version of davx5.
Thanks for any help.
I think there should be helpful information in the verbose logs. Please provide Web server and CalDAV/CardDAV server logs taken while the problem occurs, DAVx⁵ debug info (DAVx⁵ / Settings / Debug info) and verbose DAVx⁵ logs etc as described in [READ BEFORE POSTING] What’s required to diagnose a problem.
You can find debug info here
I don’t know how to find verbose log.
@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).