An XMLTV timestamp can carry its own timezone offset, and the player can convert that time for local display. Applying an additional manual shift when the conversion is already correct moves every programme away from its intended slot. Start by checking the device timezone and the original guide timestamps.
Identify the time represented by the source
A guide written in UTC can display correctly in many countries without each source being rewritten. The offset describes the source timestamp. Your device’s local timezone describes how that instant should appear on screen.
Use a recognizable programme as an anchor
Choose an airing with an independently known local start time. Compare its source timestamp and displayed slot. A consistent difference across several entries can reveal whether the error is in the source, device timezone or a manual EPG offset.
Remove stacked corrections
A global shift, channel-specific shift and device-time change can compensate for one another accidentally. Keep a record of each setting and return unnecessary offsets to neutral before applying a new correction.
A practical sequence
- Verify the device timezone and automatic clock.
- Inspect the guide’s timestamp offset.
- Change only one guide-shift setting at a time.
An example
If a UTC listing is already converted to local time by the player, adding the local UTC offset again creates a second conversion and shifts the programme twice.
Questions about this topic
Does a UTC guide work outside UTC?
Yes, when the reader converts timestamps correctly.
Should every country get a different manual shift?
No. Correct timezone conversion should normally handle location differences.
