Separate guide time, device time and programme time

Use one identifiable programme

Choose a programme with a known feed, date and official schedule. A broadcaster can have national, regional, language or time-shift versions with similar names. Record the expected programme title and the guide’s displayed title before comparing hours. Studio coverage can begin before an event, so a sports kickoff alone may not be the guide entry’s start.

Write the date with every time. Around midnight, a programme can belong to different calendar days in different zones. "One hour wrong" is incomplete if the expected entry is actually from the previous date or a different feed.

Keep three time descriptions separate

The source timestamp describes an instant in its stated reference. The device clock supplies the platform’s current date/time. The player can display guide entries in a chosen zone or with an extra offset. These layers may interact, but they are not interchangeable controls. Changing the whole device date to make one programme cell line up can disrupt other functions.

IANA maintains time-zone data reflecting changes to civil offsets and daylight-saving rules; users commonly receive those rules through software and OS updates. A fixed manual offset cannot express all date-dependent rules. A device with stale time-zone information may therefore need a supported update rather than a permanent compensating guide adjustment.

Calculate one fictional conversion

Suppose an invented listing explicitly represents 18:00 UTC on 8 November. A viewer whose applicable offset is+0500 would see 23:00 on 8 November. A second invented listing at 22:30 UTC would appear at 03:30 on 9 November in that same offset. These are original arithmetic examples, not current schedules or a claim about any country’s rules.

If a source is XMLTV, its timestamp convention must also be interpreted correctly; an explicit offset matters. Use the detailed timestamp reference when those values are available. If the player does not expose them, do not guess what the source contains from the programme name. Provide the visible comparison to support instead.

Choose the branch that matches the evidence

Compare more than one entry on the same feed. A single programme can move in the broadcaster’s schedule, while a true uniform offset should affect several matching entries. Check another date when a clock change is relevant.

Make one documented correction

First confirm the device’s automatic date/time and appropriate zone using its manufacturer’s instructions. Note the current player offset. If the evidence establishes a consistent difference and the player documents an offset control, change only that control and compare the same entries. Avoid applying corrections in the source, player and device simultaneously.

A hypothetical one-hour correction that works for today but fails next month suggests a rule-dependent problem. Recheck the actual dates and OS time-zone updates. Do not keep adding offsets until the current cell looks plausible; that can hide a feed mismatch and leave other dates wrong.

Verify and report the remaining difference

A useful result aligns matching programme entries on the intended feed while preserving the device’s correct real time. Check an entry near midnight and another ordinary daytime entry where possible. If the problem remains, report expected title, displayed title, feed, both dates/times, viewing zone, player edition and any offset changed.

Keep private guide URLs out of screenshots. A corrected guide does not establish catch-up retention or recording permission, and a blank guide does not prove playback is down. No guide feed or device clock was tested for this article. Use the programme-guide workflow for coverage and mapping issues that the time comparison has ruled out.