TV guides

Fix a TV guide that is one hour off

Confirm an hour-wide guide shift against a real programme and its UTC offset before changing the device clock or adding a player correction.

Check two channels and the exact programme date

When the entire grid shifts by an hour around a clock change, look at the television’s time zone, the programme’s source offset and any guide shift in the app. Start with two channels and a current programme you can verify independently. An error confined to one station may be a different feed or an upstream schedule mistake.

For example, a London programme scheduled at 20:00 on 16 July 2026 is at 19:00 UTC. At 20:00 on 16 January 2026, London is at 20:00 UTC. A fixed one-hour adjustment that hides the July error can move the January entry away from its actual time.

Original XMLTV startUTC instantWhat London should display
20260716200000 +010016 July 2026, 19:00 UTC20:00 BST
20260116200000 +000016 January 2026, 20:00 UTC20:00 GMT
20260716200000 with no offset16 July 2026, 20:00 UTC under the XMLTV default21:00 BST

Clear duplicate corrections before adding a new one

  1. Verify the device’s automatic date and geographic time zone. Pick the correct region or city rather than a permanent numeric offset when the device supports it.
  2. Write down the original programme start string and the guide’s shown time. Convert the source value to UTC using its explicit offset.
  3. Inspect any global guide shift and channel-level override. Record current values before testing a zero-shift baseline.
  4. Compare the resulting slot with the programme’s published local schedule. Refresh once after changing a setting and look at the same programme.

The test result tells you where to go

If two players show different times from the same guide row on correctly configured devices, compare their guide settings and timestamp parsing. If both display the same wrong time, check the source’s explicit offset and confirm the station edition. If one city feed is correct and another is a full hour out, fixing the device time zone globally can damage the correct listings.

A support report with the original string, expected UTC instant and displayed local time gives all parties the same reference point. Include the event date because the local offset can change even on the same device.

Sources and further reading