Why a Channel Plays on Your Phone but Not on Your TV
This is the single most confusing IPTV failure, because everything points at the app: same account, same playlist, same Wi-Fi, one device works. It is almost never the app. It is that a television can only play what its decoder chip was built to play, and unlike a phone, that chip never changes.
The short answer
- Phones decode in silicon that is a few years old; a 2018 television decodes in silicon from 2018, forever.
- The usual culprit is H.265/HEVC video, or AC-3/E-AC-3 audio the TV cannot decode.
- A black screen with working audio, or audio with no picture, is a codec symptom — not a network one.
- No player app can fix a missing hardware decoder. It can only tell you clearly what happened.
A television is frozen in the year it was made
When you buy a phone, you get whatever decoder silicon shipped that year, and you replace it every few years. A television is bought once and kept for a decade, and its decoder is fixed at manufacture. A set sold in 2018 decodes exactly what 2018 hardware decoded, and a software update will not add a codec — the capability is in the chip, not the firmware.
The same is true of the browser engine these apps run inside. An LG set from 2018 runs the Chromium 53 engine it shipped with and will never receive a newer one; a Samsung set of the same year runs Chromium 56. That is why our TV apps are built against those engines deliberately, with a build-time check that fails the release if newer web features slip in. It is also why "just update the app" cannot solve a decoding problem.
The two codecs that cause almost all of it
Video: H.264 is universal — essentially every device made in the last fifteen years decodes it in hardware. H.265, also called HEVC, is roughly twice as efficient, so providers like it for HD and 4K, but hardware support only became common around 2016 and is still patchy on budget televisions and older streaming sticks. A provider that re-encodes a channel to HEVC to save bandwidth will silently break it on exactly those devices.
Audio: this one surprises people, because the picture is fine and only the sound is missing. AC-3 (Dolby Digital) and E-AC-3 are common in broadcast-sourced streams, and support on a given TV depends on licensing that varies by model and region. A stream can therefore show video perfectly and produce silence.
Reading the symptom
The failure mode tells you a surprising amount, and it is worth learning to read:
- Black screen, audio plays — the video codec is unsupported, almost always HEVC on a device that only does H.264.
- Video plays, no audio — an unsupported audio codec, usually AC-3 or E-AC-3.
- Video plays but stutters badly while the network is fine — the device is falling back to software decoding, which it is too slow to sustain.
- Instant error, nothing plays, other channels fine — more likely the stream itself or the container, not the codec.
- Everything on the device fails — not a codec issue; look at the network or the playlist.
Why the same channel works on the phone
Your phone almost certainly has an HEVC decoder, because it needed one to record video in HEVC — Apple moved to it in 2017 and Android followed. So the phone plays the stream, you conclude the stream is fine, and you conclude the TV app is broken. Both conclusions are reasonable and only the first is right.
This is also why testing on a second device is such a good diagnostic and such a misleading one at the same time. It proves the stream and your network are fine. It does not prove the TV can play it.
What can actually be done
Ask the provider whether the channel is available in H.264. Many providers carry the same channel in more than one encoding, and will simply point you at the other one. This is the fix that works most often and costs nothing.
Failing that, put a device with a modern decoder in front of the television — a recent streaming stick is inexpensive and replaces the TV's ageing silicon entirely, without replacing the TV.
What will not help: reinstalling the app, changing player, clearing cache, or upgrading your internet. None of them add a decoder.
If a channel plays on one TV in the house and not another, compare the two model years before assuming anything else. That single comparison resolves most of these reports.
What a good player should do about it
It cannot decode what the hardware cannot, but it can stop pretending the failure is mysterious. Reporting "this channel uses a video format this TV cannot play" is far more useful than a spinner that never resolves, and it is the difference between a user blaming the app and a user emailing their provider with the right question.
That is the honest limit of any player on this problem, and any app claiming to "fix codec issues" on a fixed-function decoder is describing something that cannot work.
Step-by-step instead?
Frequently asked questions
Your provider is the reliable source — ask whether a given channel is H.264 or H.265. Symptom-reading gets you close: a black screen with working audio is very likely HEVC on a device that cannot decode it.
If the cause is the television's decoder, yes — the stick decodes and sends finished pictures over HDMI, so the TV's own capabilities stop mattering. If the cause is your network or the provider, it changes nothing.
Bandwidth. HEVC delivers similar quality at roughly half the bitrate, which halves their delivery cost. The trade-off lands on whoever owns older hardware.
No. Hardware decoding is done by the device, and an app cannot add a codec the chip does not implement. A player can choose how gracefully it reports the failure, which is a real difference, but not whether the channel can play.