I would add a line in the gitlab readme as you don't use issues there:
"For bug reports and feature request use the [Forum]"
Same for the https://www.davdroid.com/ page:
"The source code is available, and you can download the app on F-Droid." add "For feature requests and bugs, please use our [Forum]"
And add it to the "Links" section:
"Contribute in our Forum" or "Discussions" oder sowas..
@psycho_bunny Unfortunately, I can't help you in this case. You will have to find out why you can't connect to this IP/port from your phone. I suggest to use the browser to test the connection. As soon as the connection works in the browser, it should also work with DAVdroid.
I am newbie so I am inevitably lost in relation to your answer.
how can this be a protocol problem related to android 7 if i use a nextcloud application on android 7 which it works properly.
I naively thought it was a nginx tweak to made.
I'm afraid that my skills will not allow me to solve this problem.
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.
@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!
I don't know whether this falls within the obligation of the operating system or okhttp. However, I wonder why you have an IPv6 address when your carrier doesn't support IPv6?
This seems to be a network connectivity problem and should affect all apps, not only DAVdroid. Are other apps working?
I had the same exception all of a sudden this afternoon. I updated DAVdroid to 1.11.4-beta4-ose (from F-Droid) yesterday evening, syncing flawlessly during the entire morning. Disabling and enabling claendars in DAVdroid didn't make any difference. I also deleted the calendar storage data from the Android settings > apps, same error occurred.
Hum, that is interesting... A basic reinstallation of DAVdroid 1.11.3-gplay was not helping, but when I have installed 1.9.9-gplay, the sync worked as expected. Then I've installed 1.11.2-gplay and it worked too. Then I have installed 1.11.3-gplay back, and so it has also worked.
That's basically what seems to have helped also for me: I uninstalled DAVdroid 1.11.1-ose (the oldest version F-Droid is offering) and synced my calendars. Then I updated to 1.11.2-ose and synced, no problem occurred. Finally I updated to 1.11.4-beta4-ose and up until now sync works like a charm.
I hope this help aniling the culprit down.
@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.
Can you provide a test account (with data) so that we can reproduce the problem? Otherwise, we would at least need logs…
By the way, do you really use 17k contacts on your mobile phone? May I ask what the use case is? Is the Contacts app even usable with such amounts of contacts?
Thanks for your report! Contact synchronization with Nextcloud is known to work well.
Can you please provide steps to reproduce (maybe a test account?), Web server and CalDAV/CardDAV server logs taken while the problem occurs, DAVdroid debug info and verbose DAVdroid logs etc as described in [READ BEFORE POSTING] What's required to diagnose a problem.