How to fix Google Home casting on Pixel after Android 17

If Android 17 made the Google Home app on your Pixel lose sight of the same Chromecast or Nest devices that also vanished from YouTube, Netflix, or the Cast button elsewhere, start with permissions, not with a factory reset. The pattern that matters is not “one bad app.” It is several apps failing to discover the same cast targets at the same time.

The best-documented repair path comes from a June 2026 GrapheneOS thread where casting to a 2nd-gen Chromecast stopped after Android 17 and no app could see the target. The user-reproduced fix was to allow the Nearby devices permission for Google Play services, then restart; later replies also reported recurrence after subsequent updates, which is why this should stay labeled as a workaround rather than a permanent fix. [1]

Do this first: reopen Nearby Devices for Google Play services

On a Pixel, cast-device discovery can fail before YouTube, Netflix, Google Home, or Google TV gets a fair chance to show the device list. That is why restarting only the Google Home app can feel useless: the app is asking for devices through a path that may already be blocked.

1. Open Settings on the Pixel.
2. Go to Apps, then open the full app list.
3. Use the menu to show system apps if Google Play services is not visible.
4. Open Google Play services.
5. Open Permissions.
6. Find Nearby devices and set it to Allow.
7. Restart the Pixel.
8. After the restart, open Google Home first and wait for the device list to repopulate before testing the Cast button in another app.

That restart is not decorative. In the reported Android 17 failure pattern, allowing Nearby devices and restarting was the combination that brought Chromecast discovery back. [1]

Then check the app that is trying to cast

Do not stop at Google Play services if the app doing the casting also has Nearby devices denied. Google’s own Google TV support thread points users toward the Google TV app’s Nearby devices permission for an Android 17 connection problem, which gives the permission check a safer footing than “somebody on a forum said so.” [2]

• For Google Home: Settings → Apps → Google Home → Permissions → Nearby devices → Allow.
• For Google TV: Settings → Apps → Google TV → Permissions → Nearby devices → Allow.
• For YouTube, Netflix, or another casting app: open that app’s permission screen and allow Nearby devices if the option is present.

Now test the failure pattern, not just one button. Open Google Home and see whether the speaker, display, Chromecast, or Google TV target appears. Then open one casting app and tap Cast. If both recover after the same permission change and restart, you have probably repaired the shared discovery break, not just refreshed a single app.

If you are on an older Pixel or a model that did not follow the same Android 17 update path as newer phones, keep the label cautious. The available reports do not verify the same behavior evenly across Pixel 6 through Pixel 10. The fix is still low-risk and worth trying, but the evidence is not strong enough to say every Pixel model has the identical Android 17 casting bug.

If only Google TV’s “Connect TV” is broken, use the Google TV app workaround

There is a second failure class that looks similar from across the kitchen but should not be merged with the Android 17 discovery regression: Google TV’s own “Connect TV” flow. If Google Home and normal Cast buttons can see your devices, but the Google TV app’s Connect TV feature fails, treat that as a Google TV app problem first.

The community-corroborated workaround for that narrower Google TV issue is to uninstall updates to the Google TV app, then retest Connect TV. I would not call that a Google-confirmed Android 17 OS fix from the available material. It is an app rollback test for a specific Google TV flow.

1. Open Settings → Apps → Google TV.
2. Tap the three-dot menu if it appears.
3. Choose Uninstall updates, if the option is available.
4. Open Google TV again and try Connect TV.

Uninstalling updates is also part of Google’s ordinary Pixel app troubleshooting ladder, so the action itself is not exotic. [3] What is not official here is the diagnosis that a particular Google TV app rollout caused your Connect TV break.

Use the standard Pixel app ladder only after the targeted checks

The normal Pixel troubleshooting ladder is still useful; it just should not bury the permission gate. Google’s Pixel help flow for an installed app that is not working includes restarting the phone, checking for app updates, force stopping the app, clearing cache, clearing storage or data, and uninstalling updates where available. [3]

If your problem is not casting discovery at all — for example, Google Home will not open, cannot control a device, shows Wi-Fi or mobile-data trouble, or reports devices offline — use Google Home Not Working After Android 17? Fix by Symptom instead. The same symptom-matching approach also matters in device-control cases like our Pixel 11 Pro Google Home control troubleshooting.

Do not blame the Aug. 17/18 Google Home outage for this pattern

Google Home and Nest had a separate service outage on Aug. 17/18, 2026, and the community notice marks it resolved. [4] That matters only because it is an easy wrong turn. A resolved service outage does not explain a Pixel that, after Android 17, locally stops seeing Chromecast-class targets across multiple casting apps.

A server outage usually makes many people’s homes misbehave at once. The Android 17 casting pattern in this article is device-side invisibility: your phone cannot list targets that still exist and may still be reachable from another phone, tablet, or voice assistant. The repair path is different.

What counts as fixed

Count it as restored if Google Home can see the target again and at least one separate casting app can also list it after the Nearby devices changes and restart. That is the practical fix you needed tonight.

Do not count it as proof that Android 17 itself has been repaired. The primary report thread includes users who saw the issue recur after later updates, and no official OS-level confirmation or patch was found as of Aug. 25, 2026. [1] If discovery disappears again after another update, rerun the permission checks before replacing hardware, resetting the router, or tearing apart the Google Home setup.

References

1. Casting to 2nd Gen Chromecast broken since 17 — GrapheneOS Forum, June 2026
2. Google TV no longer can connect to Android 17 device — Google TV Help
3. Fix an installed app that isn't working on a Pixel phone — Google Pixel Phone Help
4. Service Outage - 17/18th August 2026 - Resolved — Google Home & Nest Community