Understand how Android and aCalendar store event times, handle daylight saving transitions, and display appointments across different timezones.
How Android Stores Timezones
Android stores event timestamps in Unix Time (UTC) paired with an Olson timezone string (e.g., Europe/Berlin or America/New_York) that defines daylight saving rules. All-day events are always stored in UTC.
Sync adapter warning: Faulty third-party sync adapters sometimes assign fixed offsets like GMT+1 instead of a proper region string—this shifts recurring events by one hour when daylight saving time changes.
How aCalendar Displays Timezones
- Seamless default behavior: Timed events are created in your local (or configured home) timezone, so no extra timezone clutter is shown in normal use.
- Globe indicator: When an event is stored in a different timezone than your current setting, a globe icon appears next to the time in calendar views, and both timezones are shown inside Event Details and the editor.
- Timezone database updates: Governments occasionally update daylight saving rules (IANA Time Zone Database). You can check your device's installed timezone version (e.g., 2019b) under aCalendar Settings → Timezones → Device timezone.
Automatic Network Timezone Flaw
Mobile networks only transmit a UTC offset and whether daylight saving is currently active. In regions that do not observe daylight saving alongside neighboring regions that do (such as Arizona, Saskatchewan, or Queensland), automatic detection can assign the wrong timezone during winter—causing events to shift by one hour once summer arrives. Setting your device timezone manually avoids this issue.