Android Screen Mirroring to TV Not Working: The Fixes, in the Order That Solves It

Updated September 2026 · every app listing re-read on 1 September 2026, refreshing 1 review count and 1 listing date

You tap the cast button, the spinner turns, and your TV just never shows up. Or it pairs once, then refuses the next day. Most of the time the dongle is fine and the TV is fine; the problem sits in between, almost always on your Wi-Fi. This guide works through the causes in the order that fixes the most cases first, and explains the difference between casting one app and mirroring your whole screen, since that trips up a lot of people.

Casting versus mirroring

Casting and mirroring are not the same thing, and they fail for different reasons. Casting sends one app's content to the TV: you tap the cast icon inside YouTube or Netflix, and the TV pulls the video straight from the internet while your phone becomes a remote control. You can lock the phone or switch to other apps and the video keeps playing. Mirroring copies your entire phone screen to the TV in real time, including the home screen and notifications, through the Google Home app's "Cast screen" option. It uses more battery, looks a little softer, and can lag.

This distinction matters for diagnosis. Casting from inside an app and mirroring the whole screen lean on slightly different parts of the same underlying system. If casting a YouTube video works but full-screen mirroring does not, the cause is not your network, it is a mirroring-specific issue, and the fix is usually to update the Google Home app and reboot the phone, covered below. If neither one works, the cause is almost always the network, so the ranked causes below are the place to start.

Back to the fix table

Fixes the most cases by far

Phone and TV on 2.4GHz vs 5GHz · try this if the device never shows up in your cast list at all, on any app · checked 19 August 2026

Signs this is your cause:

• Your router has two network names, or one name that secretly splits into a 2.4GHz and a 5GHz signal.
• The TV or streaming device never appears in your phone's cast list, even though both show a working internet connection.
• An older Chromecast or streaming stick is involved; newer hardware handles 5GHz more reliably.

The fix, in order:

• Check which network name your streaming device is connected to inside the Google Home app, under the device's settings.
• Temporarily connect your phone to that exact same network name and try casting again. If the device suddenly appears, this was the cause.
• For a lasting fix, either keep both devices on the same band permanently, or log into your router and look for a "band steering" setting that lets devices discover each other across bands.

Back to the fix table

The silent blocker when the band already matches

Router setting that walls devices off from each other · try this if the band already matches and the device still will not appear · checked 19 August 2026

Signs this is your cause:

• Phone and TV are confirmed to be on the same network name and band, but the device still never appears.
• The streaming device was set up on a guest Wi-Fi network, which usually isolates devices from each other by default.
• A mesh Wi-Fi system or an internet provider's router is in use; some ship with client or AP isolation turned on out of the box.

The fix, in order:

• Move the streaming device off the guest network and onto your main network.
• Log into your router's admin page and search its settings for "isolation," "AP isolation" or "client isolation," and turn it off for your main network.
• After changing a router setting, give it a minute, then reboot the streaming device so it re-announces itself on the network.

Back to the fix table

The sneaky one, since everything else looks normal

VPN swallowing local network broadcast messages · try this if a VPN app is installed and everything else about the network checks out · checked 19 August 2026

Signs this is your cause:

• Wi-Fi shows full signal, the TV is on and working, and casting simply refuses to connect.
• A VPN app is active on the phone.
• Casting worked before the VPN was installed or turned on, and nothing else about the network changed.

The fix, in order:

• Turn the VPN off completely and try casting again. If it works, the VPN was the cause.
• If you need the VPN running, open it and look for "split tunneling," "LAN bypass" or "local network" options, then exclude the casting app or allow local network traffic.
• Be realistic about the limit here: on Android, split tunneling does not always let the discovery broadcasts through even when the right app is excluded, since that traffic can still get pulled into the tunnel. If the bypass does not work, toggling the VPN off while casting may be the only option.

Back to the fix table

The five-minute fix worth trying early

Corrupted Google Play services or Google Home cache · try this if casting one app works but full-screen mirroring does not, or the cast icon is missing · checked 19 August 2026

Signs this is your cause:

• The cast icon has disappeared from an app that normally shows one.
• Tapping cast starts a spinner that says "Connecting" and never finishes.
• Casting a single app, like YouTube, works fine, but full-screen mirroring through Google Home does not, which points at the Home app itself rather than the network.

The fix, in order:

• Open Settings, then Apps, then Google Play services, tap Storage and cache, then Clear cache. Do not tap Clear storage or Clear data, since that resets Google services and creates more work.
• Repeat the same cache clear for the Google Home app and for the specific app being cast from, then restart the phone.
• Update Google Home, Google Play services and Android System WebView from the Play Store; an out of date Google Home app is a real, common cause of mirroring that refuses to start.

Back to the fix table

The one newer phones sometimes lock down by default

Wi-Fi scanning, location or local network access denied · try this if nothing has ever cast to this device on this specific phone, even once · checked 19 August 2026

Signs this is your cause:

• A fresh phone, a recent Android update, or a newly installed Google Home app is involved.
• No cast device shows up at all, even for a TV that used to work fine.
• The phone is a work device or managed by an employer profile.

The fix, in order:

• In Settings, under Apps, open Google Home's own permissions and confirm Nearby devices and Local network access are both allowed.
• Make sure Wi-Fi scanning and location are available to the system generally, since some discovery features depend on them even when GPS itself is not needed.
• Turn mobile data off for a moment while testing, since a phone occasionally tries to reach the device over cellular and gives up instead of using Wi-Fi. If the phone is managed by an employer, casting may be blocked by policy, which only whoever manages the device can change.

Back to the fix table

The app behind all of this

4.0 stars from 3,652,403 reviews · 1B+ installs · free to install, no ads, in-app purchase range listed as $0.05 to $999.99, which the listing does not break down · by Google LLC · Play listing updated 26 August 2026 · checked 1 September 2026 · Play listing

Every fix in this guide runs through one app: Google Home. It is the app that pairs your Chromecast or Google TV Streamer to your Wi-Fi, holds the "Cast screen" mirroring option, and is where most of the permission and cache fixes above actually live. Keeping it updated is not optional busywork, it is one of the most common single fixes for mirroring that refuses to start.

A note on hardware, not just the app. On 6 August 2024 Google announced the end of the line in its own words: "we're ending production of Chromecast, which will now only be available while supplies last," introducing the Google TV Streamer as its successor. The Verge reported it the same day as Google discontinuing the Chromecast line, though Google itself never uses that word. Reassuring for anyone still running one: Google added that "there are no changes to our support policy for existing Chromecast devices, with continued software and security updates to the latest devices." The newer Google TV Streamer and recent Chromecast hardware handle 5GHz Wi-Fi reliably; older Chromecast dongles are more often the ones that only support 2.4GHz, which is the root of the single most common cause on this page.

Back to the fix table

The full power cycle

Restarting fixes a surprising number of stuck states, but most people do it wrong by only tapping restart in a menu. Do it at the power level instead: unplug the streaming device from power, not the HDMI cable, and wait at least 20 to 30 seconds so it fully drains before plugging it back in. While it reboots, also unplug the router for 30 seconds; a router that has been running for months can get confused about which device is which on the network. Restart the phone too, since that clears whatever the Wi-Fi stack was holding onto. Bring everything back up, wait until the TV reaches its home screen, then try casting again. This single step, done properly at the power level rather than through a software restart, clears a lot of cases that otherwise look unexplainable.

Back to the fix table

The last resort

If every step above has been tried and the device still will not behave, reset it and pair it fresh. This wipes its stored Wi-Fi credentials and starts clean, which clears out old settings from a network you no longer use. For a Google TV Streamer or Chromecast with Google TV, go into Settings, then System, then About, then Factory reset. For an older Chromecast dongle, hold the physical button on the device for about 25 seconds until the light flashes, then release. After the reset, open the Google Home app, tap to add a device, and follow the setup to put it back on your Wi-Fi.

This is genuinely a last resort, not a first move: a factory reset throws away every saved setting on the device, so work through the ranked causes above first. Most mirroring problems are a Wi-Fi band mismatch, an isolation setting, a VPN, or a stale cache, all of which are faster to fix and do not require re-pairing from scratch.

Checked 19 August 2026: the app this whole guide depends on, Google Home, was never linked; it now has its own dedicated section with a current Play listing and figures. A specific claim about a factory-reset pairing bug affecting some second-generation Chromecasts in early 2025 could not be confirmed against any primary or press source found today, so it has been removed rather than repeated on faith. The claim that the Chromecast line was discontinued in 2024 was already correct but had no date or source; it is now dated precisely, 6 August 2024, against Google's own retrospective published that day and The Verge's reporting on the same announcement. The troubleshooting steps themselves, Wi-Fi band mismatches, AP isolation, VPN interference, cache clearing and permission checks, were already accurate and are preserved, now reordered into a ranked fix table at the top and given consistent, scannable sections. A ranked cause table, an "Our answer" capsule, a dated verification box and this changelog are new. Re-audited the same day: the Google Home in-app purchase range carried a parenthetical explaining what those purchases cover; the listing states no such thing, so the invented explanation has been dropped and the range is now presented as what it is, an unexplained figure Play publishes without a breakdown. Google's own Chromecast retrospective was also cited here as confirming the line was "discontinued"; that post never uses the word, framing the change as a transition instead, so the discontinuation wording is now attributed to The Verge. A second pass corrected that correction: Google's post does state the ending in its own voice, "we're ending production of Chromecast, which will now only be available while supplies last," and the word "transition" that briefly stood in for it here came from the AI-generated summary widget above the article rather than from Google's own text. Both are now quoted from the editorial body, and Google's commitment in the same post that "there are no changes to our support policy for existing Chromecast devices" has been added, since this page previously told readers older devices eventually lose update support.