Deadline: 4 September 2026
Google Assistant is becoming Gemini: what breaks, and how to fix it
Starting 4 September 2026, Google removes Google Assistant from Android phones, tablets, Wear OS watches, supported headphones, and Android Auto — and replaces it with Gemini. There is no opt-out and no way back. This site catalogs what actually breaks, the fixes that really work, and your options if Gemini isn’t good enough.
The one-sentence version
Your phone will switch to Gemini within a few weeks of 4 September whether you like it or not; your smart speakers and displays are not on that deadline yet — and the speaker upgrade, unlike the phone one, is still your choice. Choose carefully: it’s irreversible.
The verified timeline
| Date | What happens |
|---|---|
| 4 Aug 2026 | Google emailed users: “Google Assistant is going away on mobile devices.” |
| 4 Sept 2026 | Removal begins on Android phones, tablets, Wear OS watches, supported headphones/earbuds, and Android Auto (projected from a phone). Rollout “may take a few weeks to reach everyone.” |
| When it reaches your device | The “Switch to Google Assistant” option in the Gemini app disappears without warning. After that: “you will no longer be able to use or switch back to Google Assistant on your phone, tablet, or paired devices.” |
| Speakers & displays | No forced deadline announced yet. The “Gemini for Home” upgrade is currently opt-in per home — and permanent once accepted. |
| Google TV / Pixel Tablet | Gemini is coming; timing unclear. Google TV already has a documented Gemini setup-loop bug. |
Who keeps Assistant (the only exceptions)
- Cars with Google Built-in — Assistant runs on the vehicle’s own hardware and keeps working beyond 4 September.
- Phones below Gemini’s minimums (Android 9 or older, under 2GB RAM) — they keep a legacy Assistant; ultra-budget Android Go phones get the lightweight “Gemini Go” instead.
- Unsupported regions — retained until the broader retirement concludes.
Everyone else: no trick, registry hack, or old APK preserves Assistant on a supported phone. Anyone claiming otherwise is guessing.
What breaks — the honest inventory
Gone for good no replacement
- Interpreter Mode — live conversation translation on speakers/displays. Single-phrase translation survives; the conversation mode doesn’t.
- Family Bell — scheduled household announcements (a scheduled-automation rebuild recovers most of it — recipe here).
- Assistant Driving Mode — the Google Maps driving dashboard is removed entirely.
- Automatic daily briefings and birthday-reminder routines.
- Photo voice controls and voice-adjusted ambient display settings.
- Assistant on Bluetooth/AUX car accessories.
Degraded or different workarounds exist
- Routines — Gemini can start them, but not every starter or action survives: no typed triggers, no multi-step conversational actions, and broken voice keyphrases after the upgrade are widely reported. Full rebuild guide.
- Reminders — they now live in Google Tasks, not Assistant. They look “lost” but usually aren’t.
- Alarms/timers — phantom “Action failed” errors on phones; Nest Hubs that briefly couldn’t set alarms at all. Improving with updates.
- Smart home control — devices showing “offline” after the home upgrade (Google has acknowledged this), failed status questions, and occasional non-sequitur responses.
- News briefing — “play the news” no longer behaves like Assistant’s curated briefing.
- Speed — on-device Gemini needs a 2026 flagship chip and 12GB+ RAM; everything older (Pixel 9, Galaxy S25 included) runs via the cloud, permanently slower for simple commands.
- Wear OS — Gemini replaces Assistant with feature gaps that Google is filling monthly.
Works fine under Gemini no action needed
Core smart-home control, media playback, alarms and timers (post-updates), calendar, notes and lists, general questions, broadcasts, and Continued Conversation — which is now built in rather than a setting. The “Hey Google” wake word carries over unchanged.
Do these six things before 4 September
- Screenshot every routine you have (Google Home app → Automations, and Assistant settings → Routines). There is no export tool and no migration report — your screenshots are the only inventory you’ll get.
- Test your daily commands in Gemini now, while you can still compare. In the Gemini app you can temporarily switch back to Assistant until removal reaches your device — use the overlap to find what needs rebuilding.
- Move fragile routines into the Google Home app as household automations with exact voice-phrase starters — the single most effective fix for post-migration routine breakage. How-to.
- Update everything: Google app, Gemini, Android Auto, Google Home app (4.1+), and speaker/display firmware. Several headline bugs (Android Auto calls failing, alarm errors) are already fixed in current versions.
- Decide about your speakers deliberately. The Gemini for Home upgrade is optional today and irreversible forever. If your household depends on routines and precise commands, declining for now costs you nothing.
- Check Google Tasks for your reminders so nothing surprises you later.
Find your fix
Interactive troubleshooter
Pick your symptom — broken routine, dead Nest Hub commands, Android Auto errors, missing features — and get the specific fix, or an honest “no fix exists” with alternatives.
Start troubleshooting →
Routine rebuild guide
Recreate morning briefings, Family Bell, bedtime and leaving-home routines under Gemini — and where Google can’t do it any more, where it can be done instead.
Rebuild your routines →
Escape hatches
Staying with Gemini vs Home Assistant vs Alexa — real costs, honest trade-offs, and what your existing devices can carry over.
Compare your options →
FAQ
Is Google Assistant really going away? Can I keep it? Why is Gemini slower? Short, sourced answers.
Read the FAQ →
Why trust this site
Every claim here traces to Google’s own announcements and support documentation, or to documented user reports covered by 9to5Google, Android Authority, TechRadar, PCWorld, PhoneArena, and Google’s own support communities. Where a fix is unverified or a fact is still rolling out, we say so instead of pretending. Where no fix exists — and for several features none does — we say that too. Sources are linked inline throughout the troubleshooter.