EPG timezone handling determines how schedule timestamps are interpreted and displayed in the viewer’s local time. A timestamp with an explicit numerical offset identifies its relationship to UTC, while the device’s regional timezone determines local presentation for the relevant date. These are separate stages. XMLTV defines a UTC assumption when an explicit timezone is absent, although real feeds and players can contain mistakes. A fixed manual guide shift can hide one mismatch while creating another. Correct diagnosis starts with an actual source timestamp, its offset and the device’s selected region.
EPG timezone and Broadcast region
A feed's region and its timestamp representation are separate facts.
Interpret first, display second
A programme marked 14:00 with a +0200 offset represents the same instant as 12:00 UTC. A viewer in a region at +0100 would see 13:00 for that date. The player should not simply treat 14:00 as the viewer’s wall-clock time and then add another regional adjustment. Correct conversion preserves the instant while changing its local clock representation.
A timezone is more than an offset
A regional timezone includes date-dependent rules, while a numerical offset describes one relationship to UTC. The region may change offsets seasonally or through policy changes. Selecting a permanently fixed offset can therefore work for part of the year and fail later. Device time-zone data and the source’s per-programme timestamp information both influence accurate future guide display.
Investigate the scope of the shift
Check whether all channels are wrong by the same amount or only one feed is affected. Confirm the device clock and regional setting, then inspect a programme’s raw timestamp. Remove overlapping manual shifts while testing the intended automatic interpretation. A schedule showing the wrong channel’s titles is a mapping issue even if one time offset appears to make a few entries line up.
An illustrative example
A source timestamp says 14:00 +0200, corresponding to 12:00 UTC. On a device whose region is +0100 for that date, the correct displayed start is 13:00. Adding a second one-hour correction because the source “uses another timezone” would move an already correctly converted programme away from its intended instant.
Practical actions
- Compare one raw timestamp and offset with the displayed time.
- Set the device to the correct regional timezone.
- Remove duplicate manual shifts during diagnosis.