@ragged by the way: “And it would be very useful to be able to change the calendar after adding it.” This would be a feature of the calendar app, not of the sync adapter.
One hour time difference for nextcloud synced events
@aqeeliz When events are moved one hour, it sounds like a timezone problem. We’d need a certain event that has a different time on Android and Nextcloud/Thunderbird; then I can have a look.
@rfc2822 I have got the event from Thunderbird
BEGIN:VEVENT DTSTAMP:20210105T103803Z UID:7a9316a0-4d3b-4ed7-b6a5-937ced86b759 SUMMARY:Test evet STATUS:CONFIRMED DTSTART;TZID=Asia/Karachi:20210105T190000 DTEND;TZID=Asia/Karachi:20210105T200000
This was created from mobile for 18:00, it show up as 19:00 on nextcloud and thunderbird.
Any idea how I can get this from phone? Also, just to double check, is there any other place (other than Date & Time setting) in phone that shows my current timezone?
Edit: I have checked the timezone in both Samsung’s Calendar app, and acalendar+, both show it as Asia/Karachi, which is same as the one in event mentioned above.
Is Asia/Karachi the correct time zone?
- enable logging in DAVx5 (DAVx5 settings / Logging)
- create an event on your mobile phone
- sync it and make sure that it appears in Nextcloud/Thunderbird
- send the .zip with the logs to email@example.com
- disable logging
@rfc2822 Yes, it’s the correct timezone.
I have sent the debug info, one thing that is obvious from logs is that nextcloud isn’t doing anything, event is sent to server with one hour added to it, so issue is definitely in phone, now just need to figure out what is causing this.
I forgot to mention in email, but I created the event for 10:00 - 10:30 am.
@aqeeliz Thanks for the logs. I could identify the problem, but unfortunately we have suddently got a lot of work, so it will take some time until I can try to fix it.
@rfc2822 Sure, no problem. Take your time, and thanks for all the help!
For reference: https://github.com/ical4j/ical4j/issues/475
@aqeeliz You can easily workaround that issue when choosing a timezone similar to Karachi. Like for example Yekaterinburg - which has also GMT+5. It should work until we got that fixed in DAVx⁵.
@aqeeliz Does that workaround (Yekaterinburg) work for you?
@devvv4ever Thanks for the tip. Changing device’s timezone to Yekaterinburg solved the issue for any new event created, but it didn’t update events already created. Is there any way to fix all those without removing and re-adding the account?
@aqeeliz Unfortunately, this workaround only works for new events (or changed events when you change them to Yekaterinburg on the server and they are synced again).
And you don’t have to change the device timezone if you don’t want, it’s sufficient to only set the time zone of the events (e.g. in Nextcloud; either per-event or as a default setting, which will apply to new events).
@rfc2822 Ah, okay. There are only couple of recurring events which are problematic for me right now, will manually update them.
Thanks for the help.