Fix Your Apps. Keep Going.

Screen Mirroring / Cast Not Working on Android? 7 Fixes (2026)

You tap the Cast icon — or open Screen Cast in Quick Settings — and the TV never appears in the list. Or it appears, you tap it, “Connecting...” spins for half a minute, then it quietly gives up. Screen mirroring not working on Android is rarely a broken phone: casting is a two-device handshake, and it fails if either side cannot hear the other.

Think of it as a discovery chain. Your phone asks "is anyone out there?" across the network; the TV's receiver must be awake, listening, and allowed to answer. A break anywhere — wrong band, a router hiding devices from each other, a receiver asleep in standby — gives the same symptom: no TV in the list. This guide works the chain in order, for mirroring to a TV's built-in receiver in general. (A Chromecast dongle that will not connect is a separate case — see our Chromecast guide below.) Covers Android 10 through 14.

Android phone casting its screen to a smart TV — both showing the same mountain-lake photo

Quick Answer

When screen mirroring is not working on Android, the phone and TV are usually on the same Wi-Fi name but different bands (5 GHz vs 2.4 GHz), the router is isolating devices, or the TV's receiver is asleep or off. Put both devices on the same band, unplug the TV for 30 seconds, and confirm the TV's built-in receiver is enabled.

Fix 1: Same Network — and Same Band — for Phone and TV

Every guide says "same Wi-Fi." Fewer mention the trap: many routers run one network name across two bands, 2.4 GHz and 5 GHz, and hand devices whichever they like. Discovery does not always cross between bands, so your phone can sit on 5 GHz while the TV sits on 2.4 GHz — same name, same router, invisible to each other.

Android Wi-Fi settings showing the connected network band

  1. On your phone, open Settings → Network & internet → Wi-Fi, tap the connected network, and note its name and band — 2.4 GHz or 5 GHz.
  2. On the TV, confirm the exact same network name in its network settings. If your router splits bands into two names (like “HomeWiFi” and “HomeWiFi-5G”), put both devices on one — when in doubt, the 2.4 GHz name: most TVs support it and it travels further through walls.
  3. If either device is on a guest network, move it to the main network — guest networks are walled off from other devices by design.
  4. Still nothing? Check the router's wireless settings for AP isolation / client isolation, which stops wireless devices talking to each other. Turn it off.
  5. Reopen the Cast menu and give it ten seconds.

Fix 2: Restart Both Devices Properly (the TV Gets Unplugged)

The TV restart is where most people get cheated. The remote's power button does not turn a modern smart TV off — it parks it in standby, where the receiver apps and network stay half-asleep in whatever stale state they fell into. A TV "off" by remote for three weeks has not really restarted in three weeks.

  1. Restart the phone: hold Power and tap Restart.
  2. On the TV, skip the remote — unplug the power cable from the wall for a full 30 seconds, which clears the receiver's stored network state.
  3. Plug the TV back in and wait until fully booted and back on Wi-Fi.
  4. If discovery has been flaky, restart the router too — unplug for 30 seconds and let it come fully back.

Fix 3: Close the Distance and Clear the Interference

Discovery needs only a whisper of signal; the stream needs much more. A weak or noisy link often lets the phone find the TV, then fail when the video starts or drop out minutes in. Run this five-minute physical test first.

  1. Bring the phone into the same room as the TV and router.
  2. If it works up close but not from your usual spot, the problem is range or interference, not settings. Keep the TV on 2.4 GHz for walls, or move the router closer.
  3. Check the interference suspects: microwaves, baby monitors, and neighbours' networks all fight over 2.4 GHz. In the router's settings, switching that band to channel 1, 6, or 11 can calm it.
  4. For one test, pause other heavy traffic — a console download or cloud backup can starve the stream.

Fix 4: Update Google Home and Play Services, Clear the Cache

On Android, casting runs on plumbing in Google Play Services, managed through Google Home — even when the TV is not a Google device. Stale versions of either are a common cause of an empty Cast list or a connection dying on “Connecting...”.

  1. Open the Play Store → profile icon → Manage apps & device → Updates available and update Google Home if listed.
  2. Search the Play Store for Google Play Services and install any update offered.
  3. Clear the cached discovery data: Settings → Apps → Google Play Services → Storage & cache → Clear cache (cache only, not Clear data). Do the same for the Google Home app.
  4. Restart the phone, then check Google Home for the TV first.

That last step is a useful split-test: if the TV shows in Google Home but not in your gallery app, phone and TV are fine — that app needs updating or reinstalling.

Fix 5: Switch the TV's Receiver Back On

Most smart TVs receive casts through a built-in receiver — Chromecast built-in (Android TV / Google TV) or the manufacturer's mirroring service (Samsung, LG, others). That receiver is software, and it can be off — disabled in a tidy-up, slept by eco mode, broken by a firmware update. The phone cannot find a listener that is not listening.

Smart TV settings menu with the built-in Chromecast option switched on

  1. Android TV / Google TV: open Settings → Apps → See all apps → Show system apps, make sure Chromecast built-in is enabled. On some models it sits under Device Preferences → Chromecast built-in, with a let-others-cast option — allow it.
  2. Samsung: confirm the TV shows connected under Settings → General → Network — its receiver is normally ready by default.
  3. LG: open the Screen Share app and leave it open, then cast — some LG models only announce themselves while that app is awake.
  4. Whatever the brand, leave the TV fully on at its home screen — not standby, not an HDMI input — and try again.
  5. Install any pending TV firmware update (Settings → Support / About → Software update) — receiver bugs are what those updates fix.

Fix 6: Turn Off VPN, Private DNS, and Ad-Blockers

Anything that reroutes your phone's traffic can hide it from the TV. A VPN is the obvious one; stealthier culprits are ad-blockers that work through a local VPN profile, and Android's Private DNS, which can interfere with local discovery lookups.

  1. Disconnect any VPN (Settings → Network & internet → VPN) and pause ad-blockers that use a VPN profile.
  2. Turn off Private DNS: Pixel — Settings → Network & internet → Private DNS → Off. Samsung — Settings → Connections → More connection settings → Private DNS → Off.
  3. Set the casting plumbing to ignore battery saving: Settings → Apps → Google Home → Battery → Unrestricted, and the same for the app you cast from.
  4. Force-close and reopen the casting app, then retry. If it works now, that is your culprit — most VPNs can exclude local traffic via split tunneling.

Fix 7: Reset the TV's Network Side — or Go Wired

If the chain still breaks, reset the TV's network configuration rather than the whole TV — a lighter reset that keeps your apps and logins.

  1. On the TV, find Network settings and choose reset or re-run network setup (wording varies). Reconnect to your main Wi-Fi, same band as the phone (Fix 1).
  2. For testing, cast through the Google Home app (the TV's device tile, or Cast my screen) instead of the TV brand's mirroring shortcut or a third-party app. If it works there, the vendor layer was the problem.
  3. The honest last resorts: connect the TV to the router by Ethernet cable — a wired TV on the same router usually still appears for casting, and streams more steadily. Need the picture up tonight? A USB-C to HDMI cable bypasses wireless entirely. And if the TV stays invisible to every phone, its wireless hardware has failed — a plug-in streaming stick is cheaper than a TV repair.

Watch: Screen Mirroring / Cast Fixed Step by Step

Prefer to watch it done? This video walks through fixing Cast / screen mirroring step by step:

Video by Guiding Tech — full credit to the creator.

What the Failure Pattern Is Telling You

Read the shape of the failure — it points at the culprit:

  • The TV never appears, on any phone: not your phone — think receiver off or asleep (Fix 5), or router isolation (Fix 1).
  • The TV appears in Google Home but not in one app: that app — update or reinstall it.
  • It connects, plays, then drops: discovery worked — this is signal and bandwidth (Fix 3).

Screen Mirroring Questions Readers Ask Us

My TV appears for YouTube casting but not for screen mirroring. Why?

Related, but separate features. YouTube casting hands the TV a link to play; full mirroring duplicates your display through the TV's mirroring receiver — often a different service. If app casting works and mirroring does not, wake the receiver (Fix 5), or use Google Home's "Cast my screen" instead of your brand's shortcut.

Why does the mirrored picture stutter or lag behind my phone?

Bandwidth and interference, not discovery. Move closer to the router, keep both devices on one band — 2.4 GHz for range, 5 GHz for a cleaner short-range signal — and pause heavy traffic. Slight delay is normal; repeated freezing means the link is struggling (Fix 3).

By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026