Google Home Not Working After Android 17? Fix by Symptom

Do this first: turn off Wi-Fi and open Google Home on mobile data

If Google Home stopped working after the Android 17 update, do not start with a factory reset, router reset, or re-pairing every Nest device. Start with the one test that actually separates the common failure modes: turn off Wi-Fi on your Pixel, leave mobile data on, force close Google Home, then open it again.

That result matters more than the headline. “Google Home not working after Android 17” can mean the app cannot move data over Wi-Fi, the app is crashing, cast targets are hidden by the Android 17 local-network permission gate, or Google Home/Nest is having a server-side incident. Those do not have the same fix.

Match your result before applying a fix

Run the mobile-data test once, then follow only the branch that matches what you see. Mixing fixes is how people end up changing router modes, revoking permissions, and reinstalling apps when only one of those was relevant.

If Google Home works on mobile data but not on Wi-Fi

This is the branch that has caused the most bad advice. If Google Home works as soon as Wi-Fi is off, your Nest devices are not automatically “offline,” and your Google account is not automatically broken. The Pixel is reaching Google Home differently on mobile data than it is through your Wi-Fi path.

Confirm that split before changing the router. With Wi-Fi off, try one simple command in Google Home: turn on a light, change a thermostat setting, or open a camera tile. If it responds on mobile data, the device is still reachable through Google’s cloud path. If it does not respond on mobile data either, stop treating this as the Android 17 Wi-Fi symptom and check the device, hub, power, or account state instead.

Wi-Fi-only failure: workaround status, not confirmed root cause

The reported Android 17 Wi-Fi bug is wider than Google Home. Users have described Google apps and services failing while the phone still shows full Wi-Fi bars. That “connected but not moving the right traffic” detail is why this branch should be handled separately from ordinary smart-device offline troubleshooting.

1. Restart the Pixel once. Do this before router work so you do not chase a stale network state.
2. Forget and rejoin your Wi-Fi network only if the problem returns immediately after the reboot.
3. If you control the router, check whether IPv6 is disabled. Enabling IPv6 is the most repeated user workaround, but it remains a workaround, not a Google-confirmed fix.
4. If IPv6 is already enabled or unavailable, try setting the router DNS to Google DNS: 8.8.8.8 and 8.8.4.4. Keep a note of the original DNS values so you can revert.
5. If your modem and router are both doing routing, check for double NAT. One user report tied resolution to putting the modem into bridge mode, but that is snippet-level evidence and should not be treated as a universal fix.
6. After each router change, restart the Pixel and reopen Google Home on Wi-Fi. Do not change three network variables at once; you will not know which one mattered.

The IPv6 point deserves a warning label because it has been repeated more confidently than the evidence allows. Android Authority reported that it could not reproduce the IPv6 workaround, and BGR separately noted that IPv6 does not appear to be the only factor. [2][7]

So the practical call is narrow: if Google Home works on mobile data but fails on Wi-Fi after Android 17, IPv6, DNS, and double-NAT cleanup are reasonable workaround candidates. They are not proof that your router “caused” the Android 17 bug, and they are not a reason to wipe Google Home or factory-reset speakers that still respond on mobile data.

If Google Home loads but Cast targets vanished

This looks similar from the kitchen counter because the device you want is missing. Underneath, it is a different failure. The app may still load your home, show account data, and talk to Google over the internet, but local discovery is blocked or incomplete.

Android’s local-network permission change is the cleanest explanation for this branch. Android Developers documents that, for apps targeting SDK 37 and higher, local network access is blocked by default, enforced at the networking stack, with only narrow exceptions. The documentation page was updated July 13, 2026. [3]

Grant Nearby devices permission in the places that actually participate in casting

For Cast discovery, the permission can involve more than the front-facing app. Google Play services participates in nearby-device and casting behavior, and the app you are casting from also matters. That is why the GrapheneOS solved thread is useful: the fix was not “reinstall Google Home.” It was grant Nearby devices permission to Google Play services, then reboot. [4]

1. Open Settings on the Pixel.
2. Go to Apps, then show all apps.
3. Open Google Play services.
4. Open Permissions and allow Nearby devices if it is denied or missing from the allowed list.
5. Repeat the same check for the app you are casting from, such as Google Home, Google TV, YouTube, or YouTube Music.
6. Reboot the phone. Do not skip this step; the reported fix included a reboot.
7. Open the casting app again and check whether speakers, displays, TVs, and Chromecast targets reappear.

If targets disappear again after an app update, the same GrapheneOS thread reported a revoke-then-regrant pattern: remove the permission, grant it again, then reboot. That is annoying, but it is still better than resetting a Chromecast or rebuilding a home structure when the missing piece is permission state on the phone. [4]

Keep app-version bugs in their own lane. MichaelBTech documented Google TV 4.39.4536 casting trouble fixed in 4.39.4634, and also called out YouTube Music 9.24.51 as a separate affected app version. Those are adjacent to the local-network permission problem, but they are not the same claim as “all Google Home Wi-Fi broke.” [8]

If Google Home crashes, freezes, or setup cannot connect

If the app itself crashes, freezes, or fails during Android TV/Chromecast setup even when you are on mobile data, use the app path. Router IPv6 changes are the wrong first move for this symptom.

1. Open Settings > Apps > Google Home.
2. Tap Force stop.
3. Open Storage & cache and clear cache. Do not clear storage unless you are prepared to sign in and re-check app settings.
4. Update Google Home from the Play Store.
5. Restart the phone, then try Google Home again before changing router settings.

This branch has the clearest first-party app-update signal. Google’s June 23, 2026 early-access update for Google Home said it reduced crash rates and fixed connection issues during Android TV and Chromecast setup. That supports updating the app for crash/setup symptoms; it does not confirm a fix for the separate Wi-Fi data bug. [5]

If everyone is seeing white screens or spinning wheels today

Sometimes the correct phone fix is no phone fix. On Aug. 18, 2026, users reported Google Home and Nest white screens, spinning wheels, and broad app failures; Google confirmed the issue was resolved the same day. [6]

That outage is useful as a discriminator, not as evidence for the Android 17 Wi-Fi bug. If failures start suddenly across multiple phones, accounts, and networks, check current outage chatter or Google status channels before changing router modes. A same-day cloud incident can look like a broken home from inside the app.

The short Android 17 timeline, only where it helps

The date sequence matters because it stops unrelated bugs from being pulled into the same pile. Android 17 stable rollout began June 16, 2026, and Wi-Fi-related user reports appeared the next day across Android coverage. [1][2]

A July 8, 2026 Android 17 patch fixed other problems, including boot loops, app crashes, and widget issues, but Tech Advisor reported that it did not resolve the Wi-Fi bug. [9]

Later, Android 17 QPR1 Beta 5 coverage added widget-fix context, but that still should not be read as a confirmed Google Home Wi-Fi repair. [10]

Older Google Home crash reports, January 2026 offline-light display issues, and January 2025 Nest voice-response complaints may be real problems, but they do not explain the Android 17 Pixel triage unless your symptom and date line up. If your only affected devices are Matter bulbs, keep the Android 17 test result in mind and then check the device-side basics in the Matter smart bulb guide.

What to record if the matching fix does not work

If your branch still fails, collect the boring details before posting or escalating. They are what separate a useful report from another “Google broke my home” thread.

• Pixel model and Android 17 build.
• Google Home app version.
• Whether Google Home works on mobile data.
• Whether other Google apps fail only on Wi-Fi.
• Router model, IPv6 status, DNS setting, and whether modem/router double NAT is present.
• Whether Nearby devices is allowed for Google Play services and the casting app.
• Whether the problem is app crash, Wi-Fi-only loading failure, missing Cast targets, or broad white-screen outage behavior.

That is the line worth holding: “Google Home broke after Android 17” is too vague to fix. “Works on mobile data only,” “app crashes,” “Cast targets vanished,” or “everyone is getting white screens today” points to a real next step.

References

1. Android 17 stable rollout begins for Pixel phones — Android Police, June 16, 2026
2. Android 17 appears to be breaking Wi-Fi for some Pixel owners — Android Authority, June 17, 2026
3. Local network permission — Android Developers, updated July 13, 2026
4. Google Cast not detecting devices — GrapheneOS Forum, June 27, 2026
5. Google Home app release notes — Google Nest Help, June 23, 2026
6. Google Home and Nest outage leaves users with white screens and spinning wheels — 9to5Google, Aug. 18, 2026
7. Android 17 Wi-Fi bug is not just an IPv6 issue — BGR, June 17, 2026
8. Google Cast Android 17 local network permission fix — MichaelBTech
9. Android 17 update still has not fixed Pixel Wi-Fi bug — Tech Advisor, July 8, 2026
10. Android 17 QPR1 Beta 5 fixes Pixel widget issues — Android Central