Hi,
after update of nextcloud, the problem has been solved.

One remark, after each update of nextcloud I have to apply the hint from
https://help.nextcloud.com/t/davdroid-no-longer-works-with-nc-10-0-1-ovh/3683
maybe you should add this to the FAQ or Configuration section.

best regards,
Hubert

@rfc2822 I was able to start radicale again and after a sync it worked. Thank you very much for your help!

I always have a lot of problems with radicale. Is there any caldav server you recommend?

Has been fixed with ical4j/2.0.5 and ical4android/929555e0.

The connections never got past TLS negotiation so there is no chance that a well-known URL or a redirect could have been given by the server and there are none defined on that 12345 port URL hierarchy anyway. Also there are no related SRV records in the DNS.

I tried again and looked a bit further into the data streams. It looks like the server configuration had limited cipher suites so that no common suite was found between DAVdroid and the server on port 12345. The client tried twice, both times ending in the server sending a TLS alert due to cipher suite mismatch. After that I see a DNS SRV query for _carddavs._tcp.server.name.here.invalid which is answered with no such name (nxdomain). Immediately after that traffic to port 443 starts and the note about invalid server cert on port 443 is shown. The cipher suite configuration on port 443 has been compatible enough all the time, so a handshake to that port goes far enough to return the certificate.

I loosened up the acceptable cipher suite list on the server on port 12345 enough to include a cipher suite sent by DAVdroid in the client hello and now it works. Pretty weird / misleading user experience.

Anyway thank you for your work on DAVdroid! Not having native DAV synchronization is a significant deficiency in Android, DAVdroid seems to be filling that gap nicely.

Thank you for your reply.

It was a painful lesson.

Great it's work ! Thank you very much.

Great!

I think that you can switch back to your old notation using 26.+ (if you really want), since you've added the new Google maven repository.

However, you have the same "problem" with the build tools. And for both cases, Android Studio should notify you in case of updates. Unfortunately, there was no notification for the new maven repository.

Thanks for the clarification. It'll be a donation, then!

Thanks mate, your hint led me to the solution.
I had to remove the %20 out of the ORGANIZER property. i.e. i changed the Account Name on DAVdroid from "Idefix Kalender" to "IdefixKalender"
I works

Obviously eMClient does not like the %20 as that is invalid for mail addresses.

Thanks

Wow, did not think it would be that basic. Thank you, that did the trick.

@devvv4ever hmm, how do I close this ticket / topic?

@hobarrera That's exactly what DAVdroid does normally, when there's not just released with a ProGuard misconfiguration

Problem solved. It was the OpenTasks app.

SOLUTION: In the permissions settings of the OpenTasks app the option "Contacts" (in german "Kontakte") has to be turned on.

https://github.com/dmfs/opentasks/issues/404

Thanks for your help.

Thanks for the quick resolution, enjoy your , see your paypal .

I think I've found the issue, it looks identical to the issue reported here.

@rfc2822 @Mister_Slowhand

You don't see the synced contacts in your default app ? You have to check at least one of the accounts, last screenshot looks like you didn't select any ? You might also want to select the default account (where new contacts are inserted). It should be in parameters, not in accounts in the default app.

Yeah, from the image I posted earlier, I cannot find Davdroid address books in system default Contacts app. The others three in the image are Google/Outlook ones which I want to abandon.

In a word, Davdroid addressbooks does not show up in the list! The only solution I found is switching to 'True Contacts' app.

The drawback is 'True Contacts' does not integrate into my ROM (i.e. cannot connect to the stock 'Dialer' app).

I used the WebDAV server of Synology. i Could find this kind of setting extended MKCOL

Both issues have gone away with 1.6.5-ose from F-Droid. Thanks for the update.

@kralle Thanks for your feedback. Should be fixed with cert4android/2303f98d.

See DAVdroid 1.6.3 release notes: Android 4.1 is required now