Check the guide source and association
Ask whether guide data comes automatically with the account or requires a separate supported address. Treat any credential-bearing guide URL as private. A guide from an unrelated source may use channel identifiers that do not match your playlist.
Inspect one familiar channel before refreshing an entire catalogue repeatedly. Note whether its name, current programme and next programme correspond with the video.
Separate clock problems from missing listings
Check the device's time, date and timezone first. Then inspect the player's own guide settings. If every listing has the same offset, a timezone or offset setting is a useful direction; if only one channel is wrong, mapping or source data may be involved.
Do not apply multiple manual offsets at the device, app and guide levels. Record the original settings and change one at a time so you can reverse an incorrect adjustment.
Refresh with a clear expectation
Use the app's documented guide-refresh action and record the update time. If the provider does not supply data for a channel or date, repeatedly clearing the cache cannot create it. Ask about the actual coverage window.
Keep favourites and account settings backed up through supported means before taking any action that clears data. A missing guide does not by itself require a complete app reinstall.
Use the guide as a listing, not a content guarantee
A programme appearing in the guide is not proof it is playable, available on catch-up or included in your territory. Check the account and the specific feature separately. This also matters when live sport changes schedule or a broadcaster replaces a programme.
Read a missing guide by its pattern
A blank programme grid has several possible meanings. The most useful first observation is its extent: one row, a whole channel group, today's listings or every date. Keep the working channels visible while testing. Deleting the entire catalogue removes the comparison that could explain the problem.
The following table is a diagnostic guide, not a diagnosis of a particular provider. It helps you ask a precise question without assuming that the internet connection, player or guide publisher is at fault.
| Pattern | First useful comparison | What to ask next |
|---|---|---|
| One row is empty | Another channel in the same group | Does this channel have a guide entry and a matching identifier? |
| Names appear under the wrong video | The source and regional version of that channel | Has this row been associated with the wrong listing? |
| Today works, later dates do not | The published guide coverage window | When are the next listings normally supplied? |
| Everything is blank after import | Whether a guide source is assigned at all | Does this account need a separate supported guide address? |
| Everything is displaced equally | Device clock and one app offset | Which single layer should apply local time? |
Understand identifiers without rewriting a feed
XMLTV's published format connects programme records to channel identifiers. The identifier is not simply a logo or the friendly name shown on screen. Two entries can display similar names while referring to different regions or editions. This is why changing a channel's visible name need not repair its guide association.
If a player supports manual mapping, use the publisher's instructions and change only the affected row. Save the old association. Choose the matching region and programme sequence rather than the first similarly named result. Where mapping is managed by the service, send the problem to that service; there is no need to edit its private feed yourself.
Make an Irish evening schedule comparison
A practical household check is to choose one scheduled evening programme from its official broadcaster listing. Write down the date, channel edition and published local start time. Compare the programme before it, the selected programme and the one after it in the app. Three adjacent entries reveal more than a single matching title.
If the device clock is correct but only that row has yesterday's sequence, report stale or mismatched data rather than adding an hour globally. Conversely, if several unrelated rows are all displaced by the same amount, examine the time configuration before changing individual channel mappings. This is an illustrative method, not a report of a test performed on HexaTV.
Refresh without destroying useful preferences
Before a guide refresh, take a note of the last successful update and which date you are viewing. Then run one supported update and let the app finish. Returning immediately to an old date can make a successful refresh appear ineffective. Check the same three programme entries afterwards.
Keep guide refresh, playlist refresh and clearing application data separate in your notes. They may have very different effects on favourites, account sign-in and custom associations. If the app does not explain a destructive option, consult its documentation before selecting it. Repeatedly resetting a working player is a poor substitute for asking whether the upstream schedule exists.
Keep a short guide fault record
A useful record can read: 'Living-room TV; app and version recorded; local clock correct; Tuesday evening; one channel row shows Monday's programme sequence; other checked rows agree with official schedules; supported guide refresh completed at 18:40 with no change.' Replace these illustrative details with your own observations.
Do not include a full guide URL when it contains a username or token. A cropped picture of the affected programme row, the app version and a redacted source label usually describe the fault more safely. Send credentials only through the service's appropriate private account process when genuinely necessary.