Android Cast / Chromecast Not Working?

Android Cast not working is a Wi‑Fi discovery problem until Google Home shows the speaker or TV offline forever. In the shop, “Chromecast is dead” is usually guest Wi‑Fi, VPN, or AP isolation — not a fried stick.

Related: Wi‑Fi keeps disconnecting on Android · Chrome on Android · MacBook Wi‑Fi · Samsung TV remote · Android notifications.

Symptom map

What you see	Likely cause	First move
No Cast icon in YouTube / Netflix	Discovery blocked	Same SSID; VPN off; permissions
Device missing in Google Home	Stick offline / wrong account	Power-cycle stick; check Home
Cast starts, drops in minutes	Band steering / weak Wi‑Fi	5 GHz test; reboot router hop
Phone finds Cast, TV stays black	HDMI / TV input	TV input + TV remote basics
Works on Wi‑Fi A, fails on guest	Isolation by design	Move to main LAN
Chrome tab Cast fails, apps OK	Chrome / Cast component	Update Chrome + Play Services

1. Same LAN — not “same house Wi‑Fi”

Cast discovery needs the phone and Chromecast / Google TV / Nest display on a network that allows device-to-device traffic.

Check:

1. Phone and Cast device show the same SSID (not Home vs Home-Guest)
2. Guest / IoT / “smart device” SSIDs with client isolation are off the table for testing
3. Mesh: phone and Cast on nodes that still bridge LAN (avoid guest VLANs)
4. Corporate / dorm networks that block mDNS — use a phone hotspot test as a control

If Android Wi‑Fi itself is flaky, fix that first (Wi‑Fi disconnecting guide). Mac users debugging a Mac→Cast path can mirror the same LAN rules in our MacBook Wi‑Fi guide.

2. Kill discovery blockers for one controlled test

Temporarily:

• Turn VPN fully off (not just “pause for one app”)
• Disable experimental Private DNS / weird ad-block DNS for the test
• Turn off random MAC / “privacy Wi‑Fi” only if your router’s parental controls fingerprint MAC and isolate new clients (re-enable after)
• Stop Bluetooth-only “smart” remotes fighting the TV input while you cast

Then open YouTube → Cast and look for the device. Keep the phone powered so it doesn’t die mid-setup — a known USB-C PD hub on Amazon plus a proper brick is enough to keep a Pixel/Galaxy alive through Google Home pairing.

3. Power-cycle the Cast path (stick, TV, phone)

Stale mDNS entries are real:

1. Unplug the Chromecast / Google TV stick (or power-cycle the TV with built-in Cast) for 60 seconds
2. Reboot the phone
3. Reboot the router only if the stick never returns online
4. Confirm the TV input / HDMI source actually shows the Cast boot screen or Google TV UI

Fans spinning / stick warm but TV black can be an HDMI path — treat like other living-room signal tickets before you blame the phone (Samsung TV remote / input basics).

4. Google Home must show the device online

Cast icons in apps are useless if Home never sees the hardware.

1. Open Google Home signed into the same account used during setup
2. Confirm the Chromecast / TV / speaker is online (not “offline” grey)
3. If missing: Set up device → New device and re-link on the working SSID
4. Factory-reset the Cast device only after same-SSID + VPN-off + reboot fail (use the button reset for your stick generation)

Also allow Nearby devices / location-adjacent permissions that modern Android versions require for casting apps — denied permissions look exactly like “no devices found.” If Home notifications never appear, check OS notification blocks (notifications guide).

5. Update the whole Cast stack

Out-of-date pieces break discovery silently:

• Google Home
• Google Play Services
• YouTube / Netflix / Chrome
• Cast firmware (Home → device → settings → firmware / system update)

Retry Cast from Home’s device card first, then from the app. If app Cast fails but Home can screen-cast / play a test sound on the speaker, the network is fine and the app needs an update or cache clear.

Dropping every few minutes

Likely cause	Test
Band steering bouncing 2.4↔5	Temporary 5 GHz-only SSID
Weak mesh hop	Move phone closer to the Cast AP
Phone Wi‑Fi power save	Keep screen on; disable extreme battery savers for the test
Dual-NAT / extender isolation	Bypass the extender once

6. When hardware is the patient

Escalate after same LAN, VPN off, dual reboot, Home online, and updates:

• Stick never boots (no LED / no HDMI splash on a known-good TV port)
• Burned USB power supply for the Cast stick (try another 5V adapter)
• TV HDMI port dead (try another port / cable)
• Nest display with cracked digitizer that still Casts but can’t finish setup UI

Don’t replace the TV for AP isolation. Do replace a stick that never enumerates on a proven network and proven HDMI input.

Do / Don’t

Do

• Use the main SSID with isolation off
• Pause VPN for discovery tests
• Confirm Google Home shows online before hunting Cast icons
• Keep the phone charged during setup (PD hub)

Don’t

• Diagnose on guest Wi‑Fi
• Factory-reset the stick on day one
• Blame Netflix before confirming Home can see the device
• Assume 2.4 and 5 GHz SSIDs with the same name always bridge clients

Bottom line

Same Wi‑Fi → no VPN → reboot Cast + phone → Google Home online → update the stack. Guest networks and isolation create fake “dead Chromecast” tickets. Prove discovery on the main LAN before anyone quotes a new TV.