Yes, it’s a limitation of Android, which only provides one set of SyncColumns per event or per contact: this only supports one sync adapter per contacts list or per calendar.
However at the server side there is no such limitation. Any authorised program can connect to the CardDAV or CalDAV server. So if your server is on your PC and you can find a PC program (or write one) which synchronises between the CardDAV server and your Google contacts list or between the CalDAV server and your Google calendar, you can get those synced up with your Android device.
It looks as if Google’s calendar and contacts will now act as CalDAV and CardDAV servers, so an alternative option might be to use those as your server instead of your own PC if you were using that. If you have a PC application that also talks to your server, it should be able to talk to Google’s one as well.
@xuziq2000 I see… Seems like it also works without OAuth2, because DAVx⁵ doesn’t support OAuth.
However your problem seems to be a server problem. Is there is anything specific we can do for you, just let us know.
@rfc2822, may application was moved back to the old server.
now all cipherspecs are available again, nothing was changed on the old server !
Only my Nextcloud was first migrated to a newer server, there Nextcloud was updated from 13.0.7 to 14.0.4, the problems occurred.
now the Nextcloud has been moved back to the old server.
But now it is still Nextcloud 14.0.4 !
Could it be that it’s not the cipherspecs but the old DavDroid has a problem with Nextcloud 14.0.4?
If you have a problem with DAVx⁵, please:
Try the latest DAVx⁵ version. Use the latest version of your server software, if applicable.
Read the Configuration, FAQ and manual pages carefully. The most common issues are explained there.
Use 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.
Search the the Web for the problem, maybe ask friends who are willing to help.
Make sure that it’s not a server or networking problem. Search the FAQ/forums/bug tracker of your server software, too. Many supposed DAVx⁵ bugs are server or networking problems.
See also: FAQ: How to debug DAVx⁵-related problems
When posting, please provide as much information as you can:
Go to DAVx⁵ / 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. It contains the most important information about your device and configuration.
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.
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?
DAVx⁵ / Settings (left navigation drawer in the main screen) / Enable “Verbose logging”. A permanent notification tells you that logging is now active.
Do whatever causes your problem (e.g. “Refresh calendars”, or initiate a sync).
Use the notification to share the log. You may have to expand the notification to see the “Share” action.
Send the logs to yourself (for instance by by email, or with 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.
fixed: changed contacts visibility on every sync
fixed: crash on database upgrade
various refactoring and optimizations
Please note that if you upgrade from v <1.9 to 1.9.4 ≤ v < 1.9.10 directly, the upgrade will still fail (causing all collections to be shown as read-only without possibility to change that). In this case, you have to uninstall DAVdroid and install it again (or to delete all DAVdroid accounts, clear app storage and add the accounts again).
Upgrading from any version, including <1.9, to 1.9.10 should work without problems.
New in 1.8.1:
Better support for read-only address books:
discard local changes on read-only address books when syncing
show a notification when local changes are discarded
show warning when read-only address book is selected for sync in the DAVdroid account
DAVdroid is now written 100% in Kotlin!
rewrite of complete app to Kotlin finished (UI rewritten)
resource detection can now be cancelled (use the back button)
race condition in certificate handling fixed
other minor improvements and bug fixes
upgrade to okhttp/3.8.0 (should fix NoSuchElementException on empty DNS results)
remove “vcard4android” from VCard PRODID to avoid folding for better compatibility
use UUIDs for newly generated event/task UIDs (RFC 7986 5.3 UID Property)
added verbose information about current local and remote resource to debug info (helps to find faulty contacts/events, for instance when they’re not parseable)
new translations, which also fix a crash in the Spanish version
Address book sync.: fall back to PROPFIND when REPORT addressbook-query returns 400, 403, 500 or 501 (for instance, for old OwnCloud versions)
ical4android: treat empty-string task location and URL as null values
vcard4android: ignore raw contact data without MIMETYPE
gracefully ignore when server doesn’t sent Content-Type in GET responses
merge translations from Transifex