It fetches a playlist, renders a channel list you can drive with a D-pad, and hands each stream to the device decoder. That is the whole job. The player supplies no content of its own; the subscription line does. Live IPTV arrives as roughly 6-second segments rather than one continuous file, so the player is constantly requesting the next chunk and holding a short buffer ahead of playback. Android TV has no touchscreen and no portrait mode, so every action has to be reachable with five buttons. A player designed for phones and stretched onto a TV usually fails there first: menus you can see but cannot focus, and a list that scrolls one row per press through tens of thousands of entries.

1. 1The decoder belongs to Android, not to the app
2. 2The playlist belongs to the service, not to the app
3. 3The interface, guide and buffer belong to the app

Player apps keep the visible channel list in memory so the guide scrolls without hitting the server on every keypress. That design is fine at 2,000 channels and unstable above roughly 18,000 visible ones, especially on boxes with 2 GB of RAM. The symptom is not a playback fault: the app takes twenty seconds to open, the guide stutters, or it closes on launch. Hiding unused groups is a genuine fix rather than a workaround, because it reduces what the app has to hold. With 54,000+ live channels and 219,577+ VOD titles available, a typical US household might display two or three groups and leave the rest hidden until needed. Splitting live and VOD into separate playlists helps for the same reason.

1. 1Slow launch and guide stutter are memory symptoms, not bandwidth symptoms
2. 2Hidden groups still exist on the line and can be re-enabled any time

Android hands video to MediaCodec, which selects a hardware decoder when the device exposes one for that codec. Hardware is the sensible default: it uses far less CPU and stays cool through a three-hour event. Software decoding is the fallback for a device with a missing or buggy HEVC decoder, and it is worth trying once, on one problem channel, before you blame the line. HEVC needs roughly half the bitrate of H.264 for the same picture, so an HEVC-capable box lowers your bandwidth floor on a 25 Mbps 4K feed. Older boxes and first-generation sticks often decode H.264 in hardware but drop to software on HEVC, which is where audio drift and dropped frames start.

1. 1Change the decoder on one channel, not globally, and note the result
2. 2Audio drift that builds over minutes points at software decoding

Run the tests that separate a player problem from a line problem while you can still get your money back. Scope first: one channel stalling is a single source, a whole group failing is server-side, and everything failing points at the line, the player or the session. Then switch away and back. Recovery on switch-back means the session stalled and bandwidth was never the cause, which is a cheap and highly discriminating test. Time a cold start with the full list loaded, then again with unused groups hidden, and record the difference. Finally, watch one live event end to end, because sustained load is what a two-minute demo never covers. Plans carry a 7-day money-back window, and these tests belong inside it.

1. 1Scope the fault before changing any setting
2. 2Switch-away-and-back separates a stalled session from real bandwidth limits