I would like to suggest following the system default theme that is available from Android 10 (API level 29):
https://developer.android.com/guide/topics/ui/look-and-feel/darktheme

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 idea. I’ve added it to our already pretty long roadmap.

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)
2=approved
3=rejected

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)
1=approved
2=rejected

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.

Hi,

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?

No, Google is the only service with OAuth I know and at the moments, there are no plans in DAVx⁵ to add and maintain OAuth just for Google.

Thanks for your detailed explanation.
Keep up the good work!

@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.
HOWTO:

in the Android device use sqlite to access the services.db. You need root:

sqlite /data/data/at.bitfire.davdroid/databases/services.db

take a look at the contents:

.dump

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
VERSION:2.0
CALSCALE:GREGORIAN
X-WR-CALNAME:AnotherCal
X-WR-TIMEZONE:Asia/Almaty
BEGIN:VTIMEZONE
TZID:Asia/Almaty
X-LIC-LOCATION:Asia/Almaty
BEGIN:STANDARD
TZOFFSETFROM:+0600
TZOFFSETTO:+0600
TZNAME:+06
DTSTART:19700101T000000
END:STANDARD
END:VTIMEZONE
END:VCALENDAR
',1,0,0,NULL,1);

push this INSERT statement to sqlite restart DAVx5

Calendar ids obtained from that calendar Settings.
Good luck! and be careful.

Thank you for your fast response! So the allowBackup setting was a bug, which I saw you already fixed. Thank you!

Hi,

Same as https://forums.bitfire.at/topic/2136/lists-syncing-contents-not? Can you provide logs? Without verbose information, we’re not able to say “why”.

Duplicate of https://forums.bitfire.at/topic/2121/please-support-nextclouds-singlesignon-sso

Hello,

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.

@tusch001 It’s not a perfect solution, but at least it’s working as intended. Thanks for the update!

I’m often wiping phones for testing purposes. One of the first apps I install afterwards is davdroid (DAVx5 ). Having multiple accounts I would like to have the possibility to export / import not only the accounts but also all the individual calendars, address books and task lists (> 10!). If possible even saved if they are marked for synchronisation (I keep some address books only for backup).
For security reasons without passwords or only when hashed properly.

Just a thought.
Thanks

Steps to reproduce:

Set up a Caldav calendar (mailbox.org here). With DAVx5 connect to this calendar. Cause an sync error. In this case deleting a recurrent birthday reminder caused an error 403 (Forbidden) from the server.

Current behaviour:

DAVx5 writes a log file with technical error information (e. g. HTTP request and response, technical device information, Java stacktrace). The information might help the developer, but it doesn’t help a non-tech user at all. The information about the failure appears as a tiny icon in the status bar only, where it can easily be overlooked.

Expected behaviour:

DAVx5 informs the user in a visible message, in understandable, non-tech words that it could not synchronize, which item is affected (the displayed name of the contact, date or task), what caused the error, how he/she can solve the problem and go on. For instance see https://www.nngroup.com/articles/top-10-application-design-mistakes/, chapter 3. If the log file is needed for the developer, DAVx5 helps the end-user with easy-to-follow steps to send it to the developer.

Steps to reproduce:

Set up a Caldav calendar (mailbox.org here). With DAVx5 connect to this calendar. Cause an syncing error. In this case deleting a recurrent birthday reminder caused an error 403 (Forbidden) from the server.

Expected behaviour:

DAVx5 continues with the next sync item, trying to sync as many items as possible. DAVx5 informs the user about all failed items.

Actual behaviour:
DAVx5 stops the sync. Many other sync items are not synced because one single failure.