Please help us to make DAVx⁵ available in as many languages as possible! It is very easy to help us in this matter.
Simply join transifex.com and visit our projects page there:
Request a language to be maintained by you and start translating the available strings.
Or review an existing translation and help us to improve the quality of previously translated strings.
Here is a small visual guide of how easy it is to translate DAVx⁵
Thank you very much for your support!!
I had a experience of my calendar conflict between my Android mobile and Nextcloud Calendar App. DAVx5 returns me HTTP code 500, after i manually disable some calendars (i have few calendars in my account), sync, re-enable some of them step by step. It can sync again, i believe DAVx5 handled my conflict.
Then i read the document from – https://www.davx5.com/manual/technical_information.html#conflict-handling , i realize that server data wins and replaced the Android data.
Could i suggest to sync the data as still Server data wins, but do not delete Mobile Android data, just move that bad data to a new event, eg. title as “Conflict data: XX_original_title_XX”?
Thanks for changing the title for me.
As for the Qt-CalDAV thing - I totally understand that CalDAV doesn’t have anything to do with Qt or the way it interprets color values. Qt also doesn’t have any idea about CalDAV. If you asked me, then I would say that this is just a total coincidence that Korganizer correctly displays calendar colors sent by the Runbox calendar service. The support for SVG color names was implemented in QColor for totally different reasons, not with Apple’s calendar-color in mind (Qt as a programming framework just supports SVG as one of many graphics formats, that’s why QColor needs to understand SVG color names). QColor, of course, supports also RGB(A) color values. And most probably Runbox chose to use SVG color names for their calendars because it was just more convenient for them (we give users 120 predefined SVG colors for their calendars - they be happy; we have less work - we be happy as well).
Unfortunately, I also have no knowledge of the Apple’s calendar-color specification. From the DAVx5 logs I just assumed that these color names are Apple-defined and are part of their calendar-color specification. Turned out that my assumption was wrong. It seems that this caused a lot of unnecessary confusion
Thank you for the information. Google is the only service we know that uses OAuth. It’d be a lot of work for only one service provider, so we didn’t do that yet. Please consider migrating away from their CalDAV/CardDAV services if you can’t/don’t want to use gapps…
Thank you, that was quite quick.
Well, you can set values there, how else could you update appointments - but I understand that there is probably no way to find out which calendar app made the entry in order to know whether they have to be corrected - or is there?
As stated before, it if was an empty field (like null) or if a distinct value like 0 was used and
1=tentative (thank you for the correct term)
this could be recognized and there could be an (advanced) option in DAVx5 about how to handle that.
On the other hand if it is set to 0 and
0=tentative (thank you for the correct term)
DAVx5 may not be able to distinguish an App that uses the 0 value correctly and apps like Business Calendar 2 and Samsung Calendar that have this issue.
And yes, I understand and agree that this should be fixed by the calendar app, but as this seems to be an quite widespread issue it would be nice to add a fix if it is similar easy as thought of in my post. I doubt that Samsung will fix it, as it has been around at least 1.5 years.
Thank you so much for the reply. I was not aware that for this to work, the CalDAV client had to write this into the remote calendar (and thus require a calendar with r/w privileges) - I thought it could be added only locally during sync.
I am actually using BC2, so I will give their birthday calendar implementation a spin.
Thanks for your suggest.
@olantrust said in Supporting Custom Fields that some Android apps create:
Currently, Users using, for example, TruePhone, can add custom fields to their contacts.
These do not seem to get to DavX or else are not passed over by DavX.
Yes, DAVx⁵ can only synchronize fields it knows.
a) represent Nextcloud fields such as Language, Relationship, Geo, Timezone, Deathdate etc (most of which are RFC standard) on the Android handset.
b) sync the custom fields created in Android apps that allow it, so at the very least the data is retained in the vCard, if not displayed at the server end. I assume these properties are stored by the relevant apps in a custom way…?
It would be possible to store such fields in the Contacts database, but with a proprietary (custom) MIME type. As I see it, the most difficult part is that DAVx⁵ only stores/retrieves the data, while the Contacts apps provide UI. So implementing this would require cooperating with Contacts apps. Do you know Contacts apps whose developers would be interested in that?
Also, just for curiosity: What are your most needed additional fields and what is your use case for that?
@rfc2822 ideally it would be used by all apps that use Nextcloud login but it currently has shortcomings which can only be addressed by further work on how the server (Nc) handles app tokens.
One would say the most important thing is push, but that takes along quite a lot of things with it - ATM that means remote wipe for example and potentially other things in the future. Like I said above, this will hopefully be addressed in one of the future versions of Nextcloud.
I’d also say UX is currently better when you just do the auth screen on your side, but that’s a matter of opinions as both ways have their pros’ and cons’.
WARNING: this is quite complicated and techie. You must fully understand what you’re doing. If accept, then read on.
As some of us (users) already succeeded to sync with Google Contacts and Google Calendar, there is one serious limitation: one calendar per sync account.
Though DAVx5 GUI doesn’t allow adding more calendars, low-level hack indeed is able to accomplish that.
in the Android device use sqlite to access the services.db. You need root:
take a look at the contents:
find the calendar entry in the “collection” table (INSERT statement)
change some fields to deal with another calendar:
INSERT INTO “collection” VALUES(55,5,‘CALENDAR’,‘https://www.google.com/calendar/dav/********%40group.calendar.google.com/events/’,1,1,0,‘AnotherCal’,'AnotherCal’,NULL,'BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
push this INSERT statement to sqlite
Calendar ids obtained from that calendar Settings.
Good luck! and be careful.
I’d love to have options like
synch only between X o’clock and Y o’clock
synch only on ( ) Monday ( ) Tuesday ( ) Wednesday… etc
The reason for this request is servers that are not available at certain times, eg office machines that are switched off at night and at the week end. Choosing time frames, when to synch and when not, would avoid error messages.