Leave the stalled channel, wait a moment, then return to it. If it plays clean, the session hung, which happens for reasons that have nothing to do with your connection speed at that moment. This is the cheapest, most discriminating test you have, and almost no page walks through why it actually works: a fresh session simply doesn't inherit whatever caused the last one to stall, so if bandwidth were truly the problem, the fresh session would stall too, immediately, on the exact same connection. When it doesn't, you've learned something real in under ten seconds, and you've saved yourself from restarting a router or reinstalling an app that was never at fault in the first place.

Then the cause sits past the session, in your line, the player itself, or a server-side fault somewhere upstream of your device. Check whether the freeze is limited to one channel, one group, or everything you try across different categories. That scope check, paired with a failed switch test, narrows things down fast and tells you whether the next step is a setting change on your end or simply waiting on the provider's side to resolve a shared fault. Skipping straight to settings without this step means you might spend twenty minutes adjusting things that were never going to matter.

Setting the buffer to none or minimum means playback starts sooner and the app recovers faster after any single stalled segment, instead of building a backlog behind a large buffer window that keeps falling further behind live. A public DNS resolver usually answers faster than your ISP's default, cutting a delay that looks identical to buffering on screen even though it happens before any video actually loads. Neither change fixes a session that's genuinely stuck or a server-side fault, but both remove two specific, checkable sources of delay that are worth ruling out once the switch test has told you the problem sits on your end.

One channel buffering while everything else plays fine points to that channel's own source, and no setting change on your device reaches a source-level fault. The whole app buffering across every channel points instead to your connection, your device's free memory, or a setting like buffer size, all of which are things you can actually test and adjust. Confirm which case you're in before deciding whether a setting change is even worth trying, since spending time tuning settings for a single bad channel is time you won't get back and won't fix anything.