Try the latest DAVx⁵ version. Use the latest version of your server software, if applicable.
Read the Tested services, FAQ and Manual pages carefully. The most common issues are explained there.
Try the forum search – most questions have already been answered.
Have a look at the debug info/error details/logs. You can often get an idea what’s the problem yourself.
Make sure that it’s not a server or networking problem. Have a look at your server logs and search the FAQ/forums/bug tracker of your server software, too.
When posting, please provide as much information as you can:
debug info (see below),
steps to reproduce (what you tried to achieve and what your problem is),
your environment: server software (including version), do other clients work, etc.
How to get debug info:
If you get “No CalDAV/CardDAV service found” when you try to add an account: tap “View logs”.
If you get an error notification while synchronizing: tap the notification. A debug info activity will appear.
Otherwise, use DAVx⁵ / Settings / Debug info.
new option: keep in foreground (may help when the device prevents automatic synchronization)
AccountActivity: finish when account has been removed externally; don’t show “Create addressbook/calendar” when there’s no bind privilege on any homeset
WebDAV service detection: save all information of homesets again
debug info: show number of events, contacts, tasks for each account (to know whether sync is working)
fix sync interval sometimes not updated in UI after changing it
don’t grey out WiFi SSID setting when data saver is active
WebDAV: don’t follow redirects from HTTPS to HTTP
CardDAV: don’t keep SORT-STRING as unknown property
CalDAV tasks: fix rewriting of DTSTART/DUE when one of them is a date and the other a date-time
Before introducing complicated workarounds, I’d ask Yandex first.
A single boolean flag with “don’t exchange pictures/ignore server-supplied picture” semantics hardly qualifies as a “complicated workaround”. (Basically, “don’t use PHOTO field”.)
As for asking Yandex… I have. And all I got from them so far is a pair of links: one to their official CardDAV/CalDAV setup page, another - to 4pda.ru forum. Not exactly useful.
On the subject of complicated workarounds… A complicated workaround would be to store the encoded picture in the NOTE field of the contact card (with some additional markup, of course) and send it to Yandex that way. I tried and it appears that Yandex servers accept it, store it and then serve it back in its unspoiled form. So, that would actually work around Yandex refusal to store PHOTO… until they get wise to it, probably 🙂
Ah! I came here to ask exactly the same question. For some time I have seen these two accounts from my DAVx5: firstname.lastname@example.org and email@example.com ug and I wondered which was the correct place to store my contacts. So I need to use the “ug” one…
@gsauthof Ok, I re-tested this and this was a copy’n’paste error on my side: Since the actual IPv6 address is a bit longer I used a qr-code to copy it to the phone. That QR-Code content was accidentally terminated with a newline character which was also pasted (before the ] character).
When removing this extra character the error is gone.
So the error message ‘Illegal character in authority at index 7’ misled me, because if you start at the beginning and assume 0-based indexing, the index 7 references the [ character. Looks like the index refers to the 8th 16-bit group in the IPv6 address then.
Sorry for the multiple replies, but actually I was wrong on a couple things in my last post. It looks like the stock Android Contacts app exports as X-JABBER
Yes, the Android Contacts app exports vCard 2.0 (CardDAV requires vCard 3 or 4), and even a very “special” flavor of it. As I see it, these exported files can only be used for importing into Android Contacts again. I recommend to not use these exported files for anything else than for importing with the same app.
but the OS in general uses a different DB format and Conversations does work with DAVx5 / IMPP.
Works here, too. I use Conversations and XMPP addresses for contacts myself.
I continue to have to have the problem of phone numbers edited Android-side disappearing in Posteo on sync back. Edited emails don’t have this problem. Also, this occurs when using IMPP:xmpp:firstname.lastname@example.org as suggested
I have checked this and found:
TYPE=MOBILE is not defined, neither in vCard 3 nor 4. So for DAVx⁵, this is a custom label, so it saves the phone number with “type: custom” and custom label: “Mobile”.
When you edit the phone number on Android without changing the type, DAVx⁵ sends the phone number as:
using the X-ABLabel to retain the label.
However, it seems the Posteo Web UI doesn’t understand vCard-compliant grouping and simply doesn’t show the phone number.
If you then change the type to “Mobile” (not Custom: mobile) on Android and then sync, DAVx⁵ will upload TEL;TYPE=cell:.. and the phone number will be shown in Posteo as expected.
Can you please report the missing grouping support to Posteo?
Please fix your vCards so they use TYPE=cell instead of TYPE=mobile, or you risk that things like this happen.
@devvv4ever OK many thanks for this information.
I found an old project on github : https://github.com/caffeinatedgoat/davdroid-davx5
this project is based on 2.5.5-beta1-ose version.
I clone it, just change in /dav4jvm/build.gradle.kts the kotlin version to 1.3.50 and I build the project.
Result -> sync run
The new version probably need STATUS can’t be null.
I will check this in Baikal.
Thanks for help.