Google Assistant shutdown began 4 Sept 2026 on Android, Wear OS and Android Auto — no revert. The 7-step Gemini migration checklist and what still breaks.
If your phone still says "Hey Google" and gets the old Assistant, that ends within weeks. Google started shutting down Google Assistant on 4 September 2026 across Android phones and tablets, Wear OS watches, headphones and Android Auto, with Gemini taking over as the only assistant. The rollout takes several weeks to reach every device and there is no option to revert once it lands. Cars with Google built-in keep Assistant for now; Google speakers and displays already moved to Gemini for Home on 1 October 2025. The practical answer is to migrate deliberately this week — audit your routines, re-grant Gemini the permissions Assistant had, and test the four task types Gemini still fumbles — rather than discover the change mid-commute.
What actually changes on 4 September 2026
Three things, and they are not equal. First, the Assistant app and its long-press-home trigger are replaced by Gemini on Android phones and tablets. The standalone Assistant app on iOS goes away too. Second, Wear OS watches, connected headphones and Android Auto hand voice requests to Gemini — the same "Hey Google" hotword, a different brain behind it. Third, the change is one-way. Google's own communication to users says there is no path back to Assistant after the switch completes on a device.
The shutdown was originally planned for 2025. Google pushed it a year because Gemini, excellent at summarising a long email, was worse than Assistant at the boring things people use an assistant for: adding an item to a list, firing a smart-home routine, setting a timer in one breath. Google spent the intervening year coding those utility features — timers, media playback, routine management — directly into Gemini rather than bouncing them through Assistant. That is the context for everything below: the 2026 Gemini is a much better assistant than the 2025 one, and it is still not a deterministic one.
One nuance worth stating plainly: a probabilistic language model interpreting "turn off the lights" is a different kind of system from the rule engine Assistant was. Most of the time that is invisible. Occasionally it means Gemini asks a clarifying question where Assistant would have just acted. Plan for that in routines that run while you are driving.
The 7-step migration checklist
We ran this on a Pixel 9, a Pixel Watch and a 2023 Android Auto head unit in the week before the rollout. Total time was under an hour, most of it spent re-testing routines.
1. Update the Gemini app and set it as default now
Do not wait for the forced switch. Open the Gemini app, accept the assistant role when prompted, then confirm under Settings → Apps → Default apps → Digital assistant app. Switching early lets you find breakage on your schedule.
2. Export the routines you actually use
Google says existing routines carry over and you should not have to recreate them. Trust but verify. Open the Google Home app, list every routine, and screenshot the ones with more than two actions. Routines that chain a smart-home action with a media action are the ones most likely to need a re-save after migration.
3. Re-grant permissions Assistant had silently
Gemini asks for calendar, contacts, messages and phone permissions separately, and it asks in context — the first time you say "text Priya I am late" it will stop and request SMS access. Grant them proactively in Gemini → Settings → Apps so the first real request does not become a permissions dialog at a red light.
4. Test the four task types Gemini still gets wrong
Based on our testing and the pattern of complaints that delayed the rollout a year, these four deserve a manual check on your own devices: adding items to a specific named shopping list; starting a multi-device smart-home routine by name; quick one-word follow-ups ("louder", "next", "again") on Wear OS; and offline commands with no data connection. Assistant handled the last one on-device for basic tasks. Gemini needs a connection for most requests.
5. Wear OS: check the watch has the Gemini update
Wear OS watches get Gemini through a system update, not a Play Store install. If the watch still answers as Assistant after your phone has switched, look for a pending update under Settings → System → System updates on the watch. Until it lands, watch and phone can be running different assistants, which produces confusing partial answers.
6. Android Auto: test with the engine running, not in the driveway
Android Auto is where the probabilistic-versus-deterministic difference matters most. Test navigation start, message read-back and media control while actually driving a familiar route. If Gemini asks a clarifying question you cannot safely answer, simplify the phrasing you use — shorter, noun-first commands ("navigate home", "play podcast") worked more reliably for us than natural sentences.
7. Turn on the September features you now get for free
The September 2026 Android drop shipped alongside the switch. Find Hub Remembered (Android 16+) lets you say "remember in Find Hub that I put my passport in the bedroom drawer" and later ask where it is, with an optional photo. Motion Assist (Android 17+) adds a subtle moving bubble overlay to reduce motion sickness in vehicles and auto-activates when it detects movement. Gemini Live is also gaining a Guided Vision mode that talks you through pointing the camera at a label or a menu. None of these existed under Assistant.
Comments · 0
Beta: comments are stored locally on your device and not visible to other readers.
No comments yet. Be the first to share your thoughts.