Check the list, guide and media independently. A playable channel with no programme entry is a guide-data problem to investigate; a guide entry with a failing stream is a different result. Record feed, date range and the exact dataset that failed before refreshing or deleting anything.
Use a three-part observation
Open the player and find one affected channel. Can you see its list entry? Does it show a current programme? Does its media begin? Write three answers. Repeat on one unrelated authorised feed. A category thumbnail or programme title is not evidence that the referenced media is available, and smooth media does not establish future guide coverage.
Keep the player, connection and account fixed while making the first comparison. If the issue began after a source refresh or app update, note that event. Avoid applying a clock offset until you know that the guide has the correct programme entries to move.
Describe blank, wrong and shifted differently
A blank cell lacks an entry. A wrong title can come from another feed or inaccurate data. Correct titles shifted consistently in time point toward a different investigation. The difference matters because no single refresh or hour adjustment addresses every pattern.
| Visible result | First useful question |
|---|---|
| Stream plays; guide blank | Is guide data supplied and retrieved for this feed/date range? |
| Stream plays; guide shows another region | Is the intended feed attached to the correct guide identity? |
| Matching titles shifted consistently | How are source time and display zone interpreted? |
| Guide present; stream fails | What media-stage error occurs after selection? |
| List itself absent | Did account/source data load at all? |
Check feed identity before display names
A brand can operate several national, regional or time-shift feeds. Record the complete edition. In XMLTV workflows, programme references use channel identifiers; similar display names do not establish the same identity. Whether a player exposes manual mapping depends on its exact edition and provider configuration.
A fictional example: "Studio East" plays the intended regional feed, but the guide contains "Studio West" programmes. Moving all guide entries by an hour might make one programme look plausible while leaving the identity wrong. Ask for mapping or source correction rather than hiding the mismatch with a time setting. This example uses invented feeds and claims no account test.
Choose a refresh with known scope
Use the publisher’s documented guide-update control when retrieval needs checking. Distinguish updating guide data from clearing saved data or refreshing the entire catalogue. Let the operation finish and note its completion state. Repeated rapid refreshes can add confusion without producing new source data.
MYTVOnline 3 provides a useful documented example: content retrieval has an apply step, and guide update is separate from clearing stored EPG information. Its controls can affect all connected portals. That edition-specific distinction should not be copied as a menu recipe for MYTVOnline 2,4 or another player. The detailed reference covers the applicable actions.
Record the missing coverage range
State whether today is blank, only future days are missing or past entries disappear. Include exact dates and viewing zone. A provider may supply different coverage depths for different feeds; this article does not establish a promised Hot IPTV range. A future programme can also change after initial publication.
Compare the broadcaster’s current official schedule for the same feed when reporting an inaccurate title. Distinguish schedule changes from an app that has not retrieved new data. If a last-update indicator exists, report what it actually shows rather than assuming it records the source’s publication time.
Keep catch-up and recording separate
Past guide entries can help navigate a catch-up feature, but their presence does not prove that replay is authorised or technically available. Likewise, a blank guide does not establish that a device’s permitted local recording cannot function. Feature eligibility, storage and guide information need their own checks.
Ask the provider about account-specific catch-up support and the publisher about the selected connection method. Do not buy a drive or licence to solve an unconfirmed server feature. Keep cloud replay and local timeshift distinct.
Verify the dataset you changed
After a documented update, revisit the original feed and date range. Then check the unrelated comparison feed. Record whether guide entries arrived, mapping changed or the stream remained the same. A useful result can be limited: "media plays; today’s guide blank on this one regional feed after completed update".
Send that record with player edition and any guide setting changed, keeping private source addresses out. No guide feed was downloaded or media played in preparing this article. The workflow turns a broad "EPG broken" report into a specific request while preserving a working viewing setup.
Sources and review
- XMLTV Document Type Definition — XMLTV project
- Refresh - MYTVOnline 3 — Formuler
- How to use Cloud Timeshift in Mytvonline? — Formuler
