Casting Android to a TV: 6 Methods and a Diagnostic Order for When It Fails
Casting fails for a small set of reasons, and almost all of them are protocol mismatches or network isolation. A practical comparison of Miracast, Google Cast, DLNA, HDMI and receiver-app setups, plus a six-step troubleshooting order that covers black-screen DRM failures, missing audio, and devices that never appear.
Mirroring a phone to a TV looks like a small feature and has an unusually high failure rate. You get picture but no sound. The TV never appears in the list. The stream stutters like a slideshow. Or it works perfectly until the phone screen locks - then the TV goes black.
The root cause is almost always the same: casting is not one technology, it is five. Each has different compatibility, latency, and rules about protected content. Pick the wrong one and no amount of fiddling helps.
Know the three protocols first
- Miracast (Wi-Fi Display) - Android's built-in "Cast" / "Wireless display" and Windows. Direct device-to-device link, no router needed, 100-300 ms latency, not on every device.
- Google Cast - Chromecast, Google TV, some smart TVs. Runs over the router, powers in-app cast buttons, lowest power, best quality.
- DLNA / UPnP - most budget TVs and set-top boxes. Pushes media files only; cannot mirror the screen.
Beyond those, there are two physical routes: HDMI over USB-C and installing a receiver app on the TV.
Before choosing, determine what the TV actually supports: open TV settings and look for "Screen Share," "Miracast," or "Chromecast built-in," then check whether your phone's quick settings has a Cast / Wireless display tile. If the two sides do not share a protocol, the rest is wasted effort.
Method 1: Built-in wireless display (Miracast)
No apps required.
- Put phone and TV on the same Wi-Fi (some devices allow direct connection).
- On the TV, open the screen-share / "waiting for connection" screen.
- On the phone, pull down quick settings and tap Cast / Wireless display.
- Select the TV and confirm the pairing code if one appears.
Common failures: the TV's receiver screen times out (many are 2 minutes) so the device vanishes from the list - reopen it and search again; audio stays on the phone on some models, so check media volume and look for a "transmit audio" toggle; stuttering usually means 2.4 GHz congestion, so move to 5 GHz and get closer to the router.
Method 2: Chromecast / Google TV
The best quality and stability, if the TV has it built in or you add a Chromecast / Google TV device.
- Same Wi-Fi for everything.
- Install Google Home and confirm the TV appears.
- Two distinct modes: in-app casting - hit the cast icon inside YouTube, Netflix, etc., and the phone can lock or leave the house while playback continues; full screen mirror - Google Home → TV card → "Cast my screen."
The difference matters: in-app casting tells the TV to fetch the stream itself, so battery and frame rate are unaffected. Screen mirroring encodes your display in real time - hot phone, fast drain. Prefer in-app casting whenever it exists.
Method 3: A receiver app on the TV
Many TVs without Miracast can gain it by installing a receiver from the TV's app store. Once installed it shows a device name or QR code the phone can find.
Sideloading on a TV requires enabling installs from unknown sources, and TV malware is far harder to clean up than phone malware. Verify the signing certificate of the package you install - the same discipline as any APK.
Method 4: HDMI over USB-C
A USB-C to HDMI adapter is the lowest-latency option by a wide margin - no Wi-Fi involved, which makes it the only reasonable choice for gaming.
Check your device first. Only phones supporting DP Alt Mode output video over USB-C; many mid-range and budget models have a data-only USB 2.0 port. Buying the adapter before confirming is the usual mistake. Samsung DeX devices and some Xiaomi, OnePlus and Huawei models support wired output.
Method 5: DLNA push
Install a DLNA-capable player (VLC works), enable the TV's DLNA receiver, and push local video to it. This cannot mirror the screen, but the phone stays free, and the file plays natively without re-encoding. Ideal for downloaded movies.
Method 6: TV-native app builds
For streaming services, install the TV build of the app on the TV rather than casting. No phone involvement, no dropped frames, often 4K.
The standard sideload route is to download the TV APK and install it from a USB stick or the TV's file-transfer feature - and to pick the arm64-v8a build, or it will refuse to install or crash on launch.
Diagnostic order when nothing works
Work down this list; it isolates most failures in under three minutes.
- Same network? Guest networks on many routers are isolated and devices cannot see each other.
- Same protocol? A Miracast TV and a Chromecast-only phone will never connect.
- Is the TV still waiting? Receiver screens time out and quietly stop advertising.
- AP isolation enabled? A router setting that hides clients from each other. Turn it off.
- DRM black screen? Netflix and Disney+ block screen mirroring - you get audio and a black frame. This is by design, not a fault. Use in-app casting, which supports DRM.
- Restart both ends. The TV's casting service deadlocks regularly, and a power cycle is faster than any settings hunt.
Choosing in one table
- TV with Chromecast or Google TV → in-app casting (best)
- Miracast-capable TV, occasional use → built-in wireless display
- Budget TV with neither → receiver app or USB-C to HDMI
- Gaming or lowest latency → USB-C to HDMI
- Downloaded movies only → DLNA or a TV-native app build
Most casting frustration is a protocol mismatch wearing a disguise. Two minutes confirming what the TV supports beats two hours of trial and error.
Frequently asked questions
Q: Can I lock the phone while casting?
With in-app casting yes - the phone can lock or leave the network and playback continues. With full screen mirroring, locking usually disconnects the session; look for a keep-awake option or disable the "disconnect on lock" behaviour.
Q: Why does Netflix cast audio but a black picture?
DRM blocks screen mirroring by design. Use the in-app cast button, which uses Google Cast and supports protected playback, instead of system-level mirroring.
Q: Does casting use mobile data?
No. Casting runs over the local network, and in-app casting has the TV fetch the stream itself, consuming the TV's bandwidth rather than your phone's.
Q: Do phone and TV need the same Wi-Fi?
Google Cast requires the same network. Miracast on some devices supports Wi-Fi Direct, which needs no router but does require the two devices to be within range.