How to Refresh EPG Data Without Losing Your Setup

Check whether the guide is truly stale

Look at the last programme date and compare one channel with a current schedule. A guide can appear unchanged when a programme block repeats, while an empty future grid usually indicates that the source stopped publishing or the player stopped updating.

If the player shows a last-updated time, note it before running a manual refresh. That timestamp helps distinguish a failed download from a source that downloaded successfully but contained old records.

Run a manual EPG update first

Find Update EPG, Refresh TV guide, or a similarly named action in the player settings. Keep the app open until the task completes and check any reported error. On lower-powered devices, parsing can continue after the download finishes.

Open the guide again and check both the current slot and future listings. If the update timestamp changed but the programme horizon did not, investigate the source rather than repeating the same refresh.

Clear only cached EPG data when necessary

If a successful update does not replace obviously stale rows, use the app's clear EPG or clear guide-data option, then import the source once. This is narrower than clearing the complete application storage.

Back up the player configuration before any broader reset. Clearing all storage can remove playlists, favorites, channel order, manual mappings, and credentials, making the original problem harder to diagnose.

Set a sensible automatic refresh schedule

Enable automatic updates at an interval supported by the player and guide provider. More frequent polling does not create newer listings and may be limited by the source. A daily update is common, but the right interval depends on how often the feed changes.

On mobile and TV devices, background restrictions can prevent scheduled work. Check battery optimization, data-saving settings, free storage, and whether the app needs to be opened periodically.

Know when the source needs attention

If several devices receive the same old guide from the same URL, the source is the likely cause. If one device is stale while another updates, compare the player configuration, cache, and background behavior on the affected device.