Seems there’s timezone issues with the new time zones in Canada - I’m in PCT and e OS has no idea how to handle it. Now I’ve got a bunch of apps confused because calendars are syncing in one time zone, the phone is set to old pacific time with manual adjustment, etc.
Looking forward to hearing about the official situation with android, e OS and the new timezones.
Those with older devices that don’t receive updates may have to manually adjust the time after the transition. To do so, open Settings > search for Date and Time > disable Automatic time zone > Time Zone > Region > choose Canada > choose a time zone with the right offset.
what version are you on? tzdata updates are in android_system_timezone
I just updated to 4.4.1 today, I see 4.4.2 is available now… However, what I’m seeing is in choosing the timezone, it believes Vancouver is GMT-8, which is incorrect, and that’s what I’m closest to.
So doesn’t that seem like 1) I’m essentially up to date, and 2) timezone details are incorrect?
Not sure exactly where you mean when you say something is in ‘android_system_timezone’ - where is that?
Edit: this applies to /e/OS A14 builds and lower, A15+ up builds from AOSP directly where the release revision / tag in the manifest xml matters for what you get from the upstream repo
Same issue for me. I am on fairphone 6 firmware 4.4.2.
Vancouver time shows GMT-8. I can switch to different GMT-7 time zone but some apps are using the system’s Vancouver time e.g. BC Transit app and breezy weather app so think it’s 1 hour earlier.
I believe the issue is with /e/os. Is there anyone that can look into this? I can raise an issue in gitlab.
I was struggling with how to respond in my last reply, as it looks like if /e/ is based on Lineage, which I believe it mostly is, and Lineage took until October to get timezone changes that were released in April (March? April?), it’s then going to take time to roll down to /e/ and eventually to the users.
That being the case, though, /e/ should have ways (and I presume they probably do) to update critical components if/when Lineage has essentially dropped the ball.
Well, that sort of response is hard to respond to as a user.
We’re /e/ OS users, not Lineage users, and we’re (I’m not, anyway) a developer putting releases together myself, so it doesn’t matter what Lineage does, we’re interested in why /e/ hasn’t got us timezone updates that were available 6 months ago.. and if we can’t get a why, then when are we going to see the updates?
I really did not mean to sound hostile … I need to add explanation … /e/ is a fork of Lineage, so for “base items” like Time and Date /e/ will follow Lineage by default.
The Canada regions issue … it looks like did not extend to AOSP at the first pass (??).
The linked changes will pass to /e/OS.
The question “in what way does it not cover” was about can /e/ make effective changes faster than the existing in the pipeline? In reply to “can anyone look into this”.
why /e/ hasn’t got us timezone updates that were available 6 months ago..
if I’m not wrong, the short of it really is Google not updating older release branches in AOSP with those updates. They did it via playservice updates where one can’t replicate easily. Part of a trend since years.
more details..
LineageOS stopped tracking their own timezone repo with A14 to do independent update-tzdb work and relies again on G for higher versions than A14 - and so does /e/OS
and if we can’t get a why, then when are we going to see the updates?
this is a users forum mostly, but manoj does relaying. Possibly /e/OS can track their own timezone repo
Sorry that was poorly phrased post and obviously asking if “anyone is looking into it” was not the best placed comment here as most people here are users obviously. I will raise the issue on Gitlab.
As @tcecyk‘s edit to their comment says, the links only apply to Lineage 21, which is A14. On A15+, Google shipped the tzdb updates to its own devices via Play system updates rather than AOSP. My FP6 on 4.4.2-a16 still has the old GMT-8 rules, so I assume every BC user on A15+ is affected (and likely Alberta, NWT and Manitoba too).
Since /e/ already maintains its own forks of many repos, the team could apply tzdb 2026e themselves, without waiting on Google or LineageOS. If Google isn’t going to update older AOSP releases going forward, it sounds like LineageOS or /e/OS will have to do these updates themselves anyway.
I didn’t have it set to change automatically, and the device is giving conflicting times from 4.3 and 4.4. System clock is OK (taskbar), but widgets/apps are not showing the same time and getting confused. I haven’t adjusted my time zone, because it was correct to begin with and hasn’t changed. I don’t think setting things to the incorrect time zone is going to be a solution I would like to pursue. We will constantly end up changing times and that’s not the idea of being in a time zone that doesn’t change times.