Please see this poll: https://twitter.com/davdroidapp/status/1006892001126690816
71 % have voted for keeping current behavior (no automatic selection)
However, to improve user experience, we have introduced a small message to indicate that collections must be selected to be synchronized:
This message is only shown if there are no collections selected when the activity is started.
If you have a problem with DAVdroid, please:
Try the latest DAVdroid version. Use the latest version of your server software, if applicable.
Read the Configuration and FAQ pages carefully. The most common issues are explained there.
Use the forum search! Most questions have already been answered.
Search the the Web for the problem, maybe ask friends who are willing to help.
Make sure that it's not a server problem. Search the FAQ/forums/bug tracker of your server software, too. Many supposed DAVdroid bugs are server (configuration) problems.
Provide helpful and verbose information!
If you expect other people to help you, provide as much information as you can. It's no fun to debug a problem without knowing about what's actually the problem.
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.
Important: Go to DAVdroid / 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.
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?
DAVdroid / Settings (left navigation drawer in the main screen) / Enable "log to external storage." A notification with the log file path appears.
Do whatever causes your problem (e.g. "Refresh calendars", or initiate a sync).
Disable "log to external storage" again. Please keep in mind that those log files may contain private information and are accessible by any app which has the permission to access external storage, so delete them after those steps.
Send the logs to yourself (e.g. in the file manager and then send by email, or use the brilliant app 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.
I add TLSv1 support for Nginx confifure. And upgrade DAVdroid from F-droid. It work now.
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
@chrstn-hntschl If we could only reproduce this problem… Unfortunately, we don't have an Android 8.0 device, and in the 8.0 emulator, I can't reproduce the problem.
To dig into this, I'd really need to reproduce that.
The iCalendar is invalid:
A calendar object on a CalDAV server must not have a METHOD property. (Doesn't matter here)
PRIORITY must be an integer between 0 and 9
Your iCalendar contains PRIORITY:80, which is not valid and cannot be synchronized. Please fix your iCalendars.
Does that help?
@devvv4ever I solved it. My DAVDroid account was named the same as my email ID on one occasion and "DAVDroid" on another occasion. I just changed it to just "Droid" and synced it again. Everything has started working now. Thank you.
@rfc2822 Ich werde mich mal an den eM Client Support wenden. Mal sehen, was die sagen.
Melde mich wieder, wenn ich eine Antwort habe. Sollte dabei nichts rauskommen, kann ich ja mal noch die Debug-Logs, etc schicken.
Erstmal vielen Dank!
@rfc2822: "I think the only solution is to give DAVdroid all required permissions and to turn off functions that block DAVdroid."
That's for sure. My request was about DAVdroid beeing able to defect that permissions are missing and warn. But when implementation of "privacy protection" is like you say, I think it's the exact intention of that feature that the app does not know there is anything blocked.
So please close this thread.
Can you please provide
steps to reproduce,
DAVdroid debug info (DAVdroid / Settings / Debug info) and
if possible, verbose DAVdroid logs etc as described in [READ BEFORE POSTING] What's required to diagnose a problem?
We'd have to be able to reproduce the problem to have a look at that.