Storage, updates and backups

Storage and caches

The local catalogue lets you browse without downloading the entire source again. EPG data, posters, logs, buffers and recordings have different lifetimes.

Use Settings > Storage and cache to inspect app-owned usage. Clearing a disposable image cache is different from deleting a source, app data or recordings.

• Do not clear Android app data as the first response to a failed import.
• Keep enough real free storage for an atomic update; the last complete generation is retained while a replacement is prepared.
• Recording and timeshift storage is not a metadata cache.

Source and library updates

Source update options distinguish a scheduled interval, updates on app start and explicit manual refreshes. Existing choices are retained; the app should not create an unrestricted background catalogue loop after you leave it.

A large import can take time. The completed/partial/error state matters more than a momentary title counter.

App updates

An installed development version and the public download version can differ. Check the actual version and build in About, not only the APK filename.

A verified preserving update retains the app identity and signing key. Android or Play Protect may require a genuine installation check. Do not disable device protection to dismiss a harmful-app classification.

1. Open the app update action or the published download route.
2. Review the version and download result.
3. Complete the Android installer only when its checks permit it.
4. Reopen the app and verify your sources and viewing profile.

Backups and restore

Create and keep an encrypted backup before deliberate configuration changes. Keep its recovery information private.

Restoring a configuration is not the same as synchronising a household. Review what a restore will replace. Do not overwrite newer device state with an old test baseline.