That was the problem. Once I gave OpenTasks the permissions manually (didn’t ask for that), DAVX asked me for permission as well. Would be cool if that would be a less confusing process…
I decided today to switch back from the two dmfs apps for Cal Card DAV Sync to DAVDroid/DAVx5 because of continuous different problems.
Now, I have the “funny” difficulty (with DAVx5), that the settings for CardDAV Sync are not accessible/visible, while Cal Sync is working fine and there are no “problems” reported in any way. For me it nearly seem to be a weird GUI problem/bug (maybe?).
Logs and screenshots in shared folder below, I’d apreciate some advice of what else to try out.
New installation of DAVx5 App
Deleting and adding account another time
As there are no errors and phone settings seem to be fine (permissions/power savings etc.), I don’t know where to search…
Thank you very much!
Did you try to set up DAVx5 using our guide for posteo?
I just tested it and it works fine. We also don’t have any other reports that the CardDAV part would not work currently.
Yes, I followed the guide and tried both ports.
I forgot to precise what can be seen on the three screenshots: CardDAV is not appearing in the menu / is only appearing as “headline” on the very bottom in screenshot_03, but I cannot scroll down further. In the DEBUG Info file it is visible that there’s no sync interval set for CardDAV, which might be part of the problem, but I don’t see any possibiltity to change this with the GUI being as it is.
That means that at the time of service detection, there was no CardDAV (or it could not been detected, for instance because you drived through a tunnel exactly at the moment when CardDAV detection was running). Did you try to delete and add the account again?
Yes, twice with each of both suggested ports.
I see. It works here, so I can’t know whats’s your problem. Logs would probably help:
hmm, that’s embarrassing That last time it was indeed a typo, even though in the first place in the first logs above I had already the correct address.
So anyway, it works fine now, thank you very much! Can’t reproduce what was wrong in first place.