ActiveSync produces incorrectly timed events due to winter/summer time setting

OS VERSION: (Vanha Rauma)
HARDWARE: Sony Xperia 10III (XQ-BT52)


Trying to use ActiveSync (“Microsoft Exchange”) mail accounts produces events on the phone with incorrect times IF the events were originally created on a different winter/summer time than what is currently in effect.


You need an account on a mail server supporting the ActiveSync protocol (either an actual Microsoft Exchange server, and/or some kind of emulation of such as Zimbra), where you have older calendar events.


  1. Configure an ActiveSync account with calendar sync on your phone
  2. Note that single-occurance events close to the current date have correct times
  3. Extend sync time from default to eg. 6 months, or sync all events, so that you also get events from before the last winter/summer time change


Also events from differing winter/summer time setting get populated into the phone correctly.


Recurring or older events which were created in different winter/summer time setting end up populated on the phone with one hour error in time.


Added F-Droid, Aurora, Chum, Storeman repositories and apps from these.


Creating separate IMAP/DAV accounts on the phone for the same email server account will populate also the older events with correct times. This might also have something to do with the poor standardization of time zone names used by mail servers.

Could be related to (or a subset of) this already once-fixed bug?

1 Like

Indeed, I reported that bug some time ago and I believe Jolla had said it had been fixed - in the first 4.4 release I thought. I no longer use Exchange accounts for various reasons (this one included) so have not tested it since the claimed fix.

As I said in my report, I think my issue may be a subset of yours, as events in the current winter/summer time setting do get populated on the phone correctly, unlike in your case where all events ended up incorrect?

Well my problem appeared to be when the phone was set to a different timezone to the synchronising server - in my case UK time and UTC time, so it may well be the same sort of thing as the phone being set in a summer time (e.g. BST in the UK) with the server still operating in GMT?

I’ve seen this activesync winter/summertime bug earlier with JollaC aswell.

Note that Microsoft has put in deprecation phase all the ‘Basic Authentication’ methods, which includes ActiveSync, and since October 1st, 2022 will disable all Basic Auth access on Exchange Online.

We did apply some fixes related to timezones that went in to 4.4.0, but unfortunately I was never able to reproduce the issue @Steve_Everett was hitting. That made it both difficult to diagnose, and also difficult to know whether the changes were going to fix it.

I’ve created an internal issue for this more specific bug. I’ll try to reproduce it but may need to come back for more info.