Short answer: Google Assistant starts shutting down on Android phones, tablets, and Wear OS watches on September 4, 2026, rolling out over several weeks, with Gemini taking over automatically and no option to switch back. Once the change reaches your device, saying "Hey Google" or holding the power button opens Gemini instead.
What does Google Assistant shutting down actually mean?
Google Assistant, the default voice assistant on Android for 10 years, is being retired on Google's own timeline; the company emailed users to announce that Gemini is taking over assistant duties. This isn't an opt-in update — once the transition reaches your device, there's no way to reopen the old Assistant.
The shutdown was originally planned for 2025 but got pushed to 2026. The date is now confirmed: the rollout begins September 4, 2026, and reaching every eligible device can take a few weeks.
That adds a new line to how GPT-Live, Gemini, and Claude compare as voice assistants: Gemini is no longer just a chat assistant, it's Android's default voice layer.
Which devices are affected?
Android phones, tablets, Wear OS watches, headphones, and vehicles running phone-projected Android Auto are affected starting September 4. Google Home speakers, smart displays, and vehicles with "Google built-in" keep Google Assistant working for now — Gemini is coming to those form factors later.
The table below breaks down which devices are affected and when:
Device/platform | Status (as of September 2026) |
|---|---|
Android phone and tablet | Switching to Gemini from September 4 |
Wear OS watch, headphones | Switching to Gemini from September 4 |
Phone-projected Android Auto | Switching to Gemini from September 4 |
"Google built-in" car systems | Assistant keeps working for now |
Google Home speaker, smart display | Not yet affected, Gemini coming later |
Google TV | Not yet affected, Gemini coming later |
What happens to my data during the switch?
If Web & App Activity is turned on in your account settings, your past sessions with Assistant stay saved the same way they always were, and Gemini continues that same history instead of starting a separate record. Routines, some personal data, and third-party integrations either carry over into Gemini's framework automatically or get lost in the migration, depending on the device and integration.
That makes it worth noting down the routines you rely on — alarm chains, smart-home commands — before the switch, then checking after the transition whether Gemini has rebuilt them.
Why is Google replacing Assistant with Gemini?
Google's official reasoning is that Gemini runs on a large language model, giving it far more flexible natural-language understanding than Assistant's older command-template architecture. Assistant was built to recognize commands matching fixed patterns; Gemini is built on a model that retains context and can follow a multi-step conversation.
In practice, that means requests beyond a single command — like "I have a meeting tomorrow, set an alarm for it and suggest what to wear based on the weather" — can be handled in one pass. There's a trade-off: the new architecture doesn't always recognize old command patterns identically, so some routines may need re-testing in the first few days.
How do I check or control the switch?
Eligible devices switch automatically, so there's nothing you need to do. To check whether the switch has reached your device, go to Google Settings > Google Assistant and look for a message redirecting you to Gemini. If it hasn't arrived yet, you can manually download the Gemini app and set it as your default assistant — that pulls the automatic switch forward by a few weeks.
Reading this alongside how AI assistants compare across Android and iPhone gives a clearer picture: Google is no longer growing two separate assistants, it's consolidating everything into a single Gemini core.
What does this change for developers?
Third-party integrations still tied to Assistant's older Actions on Google infrastructure — smart-home devices, custom voice commands — hit a breaking point that needs re-testing during the switch. Gemini's expanding integration surface works on logic similar to how Claude pulls live data through MCP: instead of fixed command templates, it's a more flexible, context-driven connection to linked services.
The practical takeaway for developers: if you shipped an integration through Actions on Google, check during September 2026 whether it has been migrated to Gemini's current developer tooling — otherwise it can quietly stop working.
What problems are being reported during the switch?
The most common complaint from early adopters is that some smart-home routines — like a "good night" command that turns off multiple devices at once — don't work on the first try right after the switch. That's because Gemini interprets the command through a different natural-language model; the routine typically works once it's re-saved or phrased slightly differently, but that's an extra step users didn't expect.
The second common complaint is increased battery drain on Wear OS watches in the first few days after the switch; Google says this is temporary and resolves once the model finishes device-specific optimization in the background. A third issue: recognition accuracy in some regional dialects and accents starts out lower than Assistant's, because Gemini's voice model hasn't been fine-tuned as deeply for that region yet — this improves over time.
Are Gemini's privacy settings different from Assistant's?
The core privacy framework stays the same: the Web & App Activity setting still controls whether conversation history is saved, and it carries over directly from Assistant to Gemini. The difference is that Gemini holds onto more contextual information by default — previous questions, preferences — for a short time, so it can follow multi-step conversations, meaning it processes somewhat more data than Assistant did with its single-shot commands.
For privacy-conscious users, the practical move is reviewing Gemini's activity history under Google Account > Data & Privacy after the switch and shortening the auto-delete window (3, 18, or 36 months) if needed. That setting existed under Assistant too, but given Gemini retains richer context, it's worth confirming that control again.
Frequently Asked Questions
When exactly does Google Assistant shut down?
The shutdown rolls out starting September 4, 2026, reaching all eligible Android phones, tablets, and Wear OS devices over several weeks. Once it reaches your device, there's no option to switch back to Assistant.
Will Assistant still work on my Google Home speaker?
Yes, this announcement doesn't currently cover Google Home speakers, smart displays, or Google TV. Google says Gemini is coming to those devices later but hasn't given a firm date.
Do I lose my old routines and data after the switch?
If Web & App Activity is turned on, your conversation history carries over to Gemini, but some routines and third-party integrations may not transfer automatically depending on the device. The safest approach is noting your frequently used routines before the switch and testing them in Gemini afterward.
Can I switch to Gemini manually instead of waiting?
Yes, you can download the Gemini app and set it as your device's default assistant now, without waiting for the automatic rollout. The automatic switch will reach everyone within a few weeks regardless.
Will my Assistant integrations built on Actions on Google still work?
That depends on whether the integration has been migrated to Gemini's current developer infrastructure; an old, unmigrated integration can quietly stop working after the switch. If you use a smart-home device or custom voice command, checking the manufacturer's support page for its current status during September 2026 is the safest move.
