How Tevium reconnects a dropped live channel
Automatic live-channel retries, HLS alternatives and persistent player messages make connection recovery clear.
A dropped stream should not leave you staring at a spinner with no explanation. Tevium reconnects live TV up to five times and keeps connection status inside the player. You can read what is happening without a system popup taking over.
After a connection failure
After the initial connection fails, retries use delays of 1, 2, 4, 8 and 10 seconds. A channel buffering continuously for 30 seconds can also trigger recovery.
These delays give the network or source time to recover. Ten seconds of stable playback resets the budget, so a separate interruption later has its own recovery attempts.
Changing channels cancels the previous channel's pending attempt. Pausing suspends recovery until viewing resumes.
HLS alternatives
An HLS playlist can contain several versions of the stream. When a compatible alternative is available, playback can exclude a failing rendition and try another bitrate or format.
A playlist with one rendition has no alternate track to choose. Reconnection then works with the source you supplied.
Backup hosts
If your provider supplies another host for the same service, configure it as a backup. Tevium can use configured hosts within its recovery attempts. Use addresses supplied or approved by your provider.
Read the player message
The player reports reconnecting progress and keeps the final error visible when recovery stops. It stays inside the interface instead of disappearing as an Android TV toast.
For a denied login or connection-limit error, check your provider account. For an unsupported codec, choose a version your device can decode. Those errors need a different response from reconnecting the same stream.
Regular dropouts
Check whether the same provider stream fails on another device and whether wired networking helps. For 4K HEVC testing, a supported physical device is more useful than an emulator with a limited decoder.
The VOD disk cache serves a different purpose: reusing downloaded on-demand data when returning to cached sections. It is not a live TV buffer.