Switch away from the affected channel and back before you do anything else. If it recovers clean, the session stalled and your bandwidth was never the cause. No setting change was needed. If it stalls again immediately, note whether other channels in the same group behave the same way, since that tells you if the fault is scoped to one channel, one group, or the whole service. This single test saves you from restarting a router that was never the problem. It costs ten seconds and rules out roughly half of what people normally try first, which is exactly why it belongs at the front of any fix list instead of the back.

A restart only fixes a stuck local process. It does nothing for a server-side fault or a fault introduced by a recent app update. Post-update regressions are a distinct, recurring cause: an update changes app behavior, not your network. If problems started right after your player app updated, check the app's release notes or try an earlier stable version before assuming anything else changed. This is easy to miss because the timing looks coincidental, a device update and a playback problem landing the same week, when the update is often the actual trigger.

This is a distinct bug from general lag. The app skips a large block of channels on a single button press instead of moving one at a time. It usually traces to a stale channel-list index held in memory rather than a slow connection, so general lag fixes like buffer tuning won't touch it. Refreshing or reloading the full channel list, rather than restarting the whole device, is the more direct fix for this specific symptom. It's worth naming as its own issue rather than folding it into general lag complaints, since the two look similar on the surface but respond to completely different fixes.

Subtitles split across three separate contexts that behave differently: video-on-demand versus live channels, and subtitles rendered by the app's built-in player versus an external player. A fix that works for one context often does nothing for another, which is why 'subtitles are broken' is rarely one single setting. Check which context you're in first, then look for the subtitle toggle specific to that player, not a single global switch. If you switch between an app's built-in player and an external one for the same content, expect to set subtitles separately in each, since they don't share settings.

Live video arrives in roughly 6-second segments, so a buffer set too small for your normal network jitter will freeze even on a fine connection. Set the buffer to the lowest stable value your app offers and switch your DNS to a public resolver. Those two changes resolve most freezing that isn't server-side. If freezing only shows up during clearly busy hours and clears later on its own, that points to server load, which no local setting reaches. Testing both changes on the same channel, one setting at a time, tells you which one actually mattered instead of leaving you guessing which fix did the work.