This is the question to ask before you touch any setting. Open the channel that freezes, then open two or three others in the same category. If only that one channel struggles, the fault sits upstream on that specific source feed and no local fix reaches it. If the whole category freezes, the fault is server-side for that group. If every channel freezes, including ones outside that category, the problem is your line, your player, or your session. Each of those three outcomes points at a completely different fix, which is why guessing at settings before you scope the problem wastes time.

1. 1One channel = source feed
2. 2One group = server-side fault
3. 3Everything = line, player, or session

This is the cheapest, most useful test you have, and almost no troubleshooting guide mentions it. Switch off the frozen channel, wait a few seconds, then switch back. If it plays clean, the session had stalled, not your bandwidth, since your connection never actually changed in that window and nothing about your line improved between the two attempts. If it freezes again immediately, the fault is more persistent, either on that feed or in your local session state. This single test, run in under a minute, tells you whether to keep digging locally, wait out a server-side issue, or move on to checking your connection path with a second device.

A live channel does not arrive as one continuous file. It comes in short segments, typically around 6 seconds each, that your player downloads and stitches together in order. Your buffer holds a few of these segments ahead of what you are watching. If a segment is late for longer than your buffer can absorb, playback stalls until the next one arrives, and that stall is what you see as a freeze. Post-update regressions are a separate, recurring cause: an app update can quietly change buffer or codec handling and introduce freezing that was not there the day before.

A useful check: log into the same account on mobile data, or through a VPN on the same device, while your home Wi-Fi is still connected to the router. If streaming is clean on that other path but freezes on your direct home connection, the fault is isolated to that one network path, not your account or the app itself. Some home routers or ISPs deprioritize sustained video traffic during peak hours, especially in the evening when overall network demand is highest, and this test tells you that in a couple of minutes instead of guessing at router settings or calling your provider's support line first.

Some freezing is oversold server capacity on the provider's side, and no device setting reaches that. If scope points to a whole group or the whole service, and switching away and back does not help, you are looking at a capacity problem upstream rather than anything on your device or your line. That is a reason to ask any provider what its uptime actually is, in a specific figure you can check, rather than accepting a general claim of reliability. IP4KTV publishes 99.99% uptime, which works out to about 53 minutes of downtime a year, and that number is something you can hold a provider to.