element-hq / element-hq/element-android
Element Android uses outdated timezone for Almaty (UTC+6 instead of UTC+5)
- Dominant language
- Kotlin
- Stars
- 3.7k
- Forks
- 917
- PR merge metrics
- No merged PRs in 30d
Description
### Steps to reproduce
Summary
Element Android displays message timestamps with the wrong local time in Kazakhstan.
Since March 2025, Kazakhstan officially switched to UTC+5 (permanent, no DST).
However, Element Android still assumes Asia/Almaty is UTC+6, which causes all events to appear 1 hour ahead of the correct local time.
Steps to Reproduce
Set Android system timezone to Asia/Almaty.
Ensure system clock shows the correct local time (UTC+5).
Open Element Android and view any message.
Compare the displayed timestamp with system time.
Expected Result
Message time matches system clock (UTC+5).
Actual Result
Element Android shows timestamps +1 hour ahead, as if Almaty were UTC+6.
### Outcome
What did you expect?
Element Android should display message timestamps according to the correct current timezone of Asia/Almaty (UTC+5), matching the system clock on Android and other Matrix clients.
What happened instead?
Element Android still treats Asia/Almaty as UTC+6, so all message timestamps appear 1 hour ahead of the actual local time, even though the system clock and other clients show the correct time.
### Your phone model
Samsung Galaxy S21
### Operating system version
Android 15
### Application version and app store
Element 1.6.44
### Homeserver
Synapse 1.135.2
### Will you send logs?
Yes
### Are you willing to provide a PR?
Yes
Contributor guide
Assessment
This issue has not been assessed yet.