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.
@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.
@sergio Workaround still works (using DAVx⁵ 2.2.1-ose and OpenTasks 1.1.15), however, once I check a task as done in OpenTasks the issue returns with the next sync.
Now I’m using aCalendar+ as calendar app and OpenTasks to sync tasks. When I get a notification for a due task, I just check it as done in the aCalendar+ notification. Notifications from OpenTasks are deactivated. A sync thereafter does not trigger Vibration.
So the Vibration only happens after checking within the OpenTasks notification.
Wenn du den Mac mit iCloud benutzt ist das ein typischer Anwendungsfall den viele User haben. Sowohl die am Mac oder iPhone eingetragenen Termine werden auf der iCloud gespeichert. Am Android richtest du DAVx⁵ mit den Einstellungen für iCloud ein. Du kannst dann auf allen Geräten Termine anlegen, ändern oder löschen. Genauso die Kontakte und Reminder, falls du das willst. Am Android musst du nur sicherstellen, dass neue Termine auch im richtigen Konto (im Dropdown des Termin-Anlegen-Dialoges), nämlich dem DAVx5-icloud-Konto gespeichert werden.
@rparkins said in Sync getting done too late:
However if some devices can in fact start the same sync in parallel, the problem is real.
Yes, but I will only make one level of workaround for these broken devices, not workarounds for the workarounds.
If you could provide information about the device and how this could happen, it would be interesting. Maybe it can be avoided by DAVx⁵, or the problem could be reported to the vendor.
I can only say again that DAVx⁵ does not delete collections from the server unless it’s explicitly requested by the user and confirmed in the UI. Also, we have never heard such a thing before, which is strange when you think how many people uninstall DAVx⁵.
Will mark this is invalid until steps to reproduce or any other indications for this problem are given.
@Triton said in Logging: no attachment when sharing log to K-9 mail:
Personally I think that installing “Amaze” or “Share via HTTP” is a higher risk to the phone than temporarily storing a log of contact and calendar data transactions.
What are the security risks in installing “Amaze” or “Share via HTTP” in your opinion? (Of course, there are many other options you can use with “Share”, for instance upload to your own WebDAV server, send to your own mail server etc.)
As said above, leaving logs in external storage allows all installed apps with external storage permission to immediately access those logs. I’ll consider the way the Android docs: Sharing files recommends to be better, more secure and easier to use. That’s why we have implemented it and I hope that it will be useful for you and other users.
By the way, I have renamed “Share log” to “Send log” to make it more clear that you don’t have to share anything.
If logging doesn’t work again, feel free to post here again!
The solution was to re-execute the git clone --recurse-submodules https://gitlab.com/bitfireAT/davx5-ose.git with a stable internet connection. Inspection of the command in a re-try showed it had not completed successfully.
Retrying the command until it completed successfully was sufficient for Android Studio to build the project. I apologize for this sloppiness.
Sorry for my non existing response, I somehow missed your post. The Issue is probably as @devvv4ever writes not nextcloud related. I changed for testing purposes my dav-Server to baïkal and katana (both are no longer maintained), still had the problem.
As written in my previous post, resetting my phone did help at first. A few days ago, I broke the camera of my old HTC 10 with LOS 14.1, time to move to my Nokia 6.1. Well, after setting everything up the issue is back
ICSdroid is also affected, interval is switching back to manual after a reboot.
I’d like to help troubleshooting this issue, what can I do?
P.S.: can I unmark this thread as solved?