SaaS · signalled, not confirmed
Google is discontinuing the classic Google Assistant on mobile devices — phones, tablets, Wear OS watches, compatible headphones, and phone-projected Android Auto — replacing it with Gemini; Google's public post says this happens "later this year," and Google's emails to users (reported 4 August) say removal begins 4 September 2026
departs Date not announced · signalled, not confirmed
Quick answers
- Is it true that Google Assistant is being retired on mobile in favor of Gemini — removal reportedly begins 4 September 2026?
- Not confirmed. Google has signalled this but has not committed to a date.
- When does it take effect?
- No date has been announced yet — Google has flagged the change but not set one.
- What should I use instead?
- No action is required to keep a working voice assistant: Gemini replaces Google Assistant automatically on affected devices, and Google positions it as supporting the most-requested tasks such as playing music, setting timers, and acting from the lock screen.
What this means for you
Google Assistant is the built-in voice assistant on a very large share of Android phones and tablets, Wear OS watches, many compatible headphones and earbuds, and Android Auto when it is projected from a phone. Google is replacing it with Gemini, its newer AI assistant. On its official blog Google states only that "over the coming months" it is upgrading more mobile users to Gemini, and that "later this year" the classic Assistant will no longer be accessible on most mobile devices — no exact date appears on that page. Separately, beginning 4 August 2026, Google emailed Assistant users (reported by 9to5Google, Search Engine Land, Android Authority and Engadget, which quote the notice) telling them it will begin removing access to Google Assistant starting 4 September 2026, with the rollout taking a few weeks to reach everyone. The change is described as one-way: once a device moves to Gemini, the reporting says you cannot switch back to Assistant on that device or its paired accessories. For most people nothing must be done — Gemini takes over automatically — but the swap is not feature-for-feature, and some Assistant capabilities (press reports name Interpreter Mode and certain smart-home routines) are described as not carrying across, so anyone who depends on a specific Assistant behavior should check whether Gemini supports it before their device flips.
Where to go
No action is required to keep a working voice assistant: Gemini replaces Google Assistant automatically on affected devices, and Google positions it as supporting the most-requested tasks such as playing music, setting timers, and acting from the lock screen. The work, where there is any, is in the gaps. If you rely on a particular Assistant feature — Interpreter Mode, a specific Routine, a smart-home or third-party action — confirm Gemini handles it before the change reaches your device, because the reported switch to Gemini cannot be reversed on that device. Older or low-memory Android devices are reported to keep a legacy Assistant for basic tasks rather than moving to Gemini. Not affected for now: cars with Google built-in, and home devices — speakers, smart displays, and TVs — which Google says will keep running Assistant until a separate, later Gemini experience arrives for them. There is no data-export deadline here in the way a shutting-down cloud service has one; the thing to protect is any workflow or accessibility feature that lives specifically in Assistant and may not exist in Gemini yet.
- Gemini — Google's own replacement; it becomes the default assistant on affected mobile devices automatically
- On home devices (speakers, displays, TVs) and cars with Google built-in, Assistant continues to work for now — no immediate change there
- Third-party voice assistants where a needed Assistant feature is not yet available in Gemini
Google Assistant — the voice assistant that has answered “Hey Google” on Android phones, Wear OS watches, headphones, and Android Auto for the better part of a decade — is being retired on mobile. In its place Google is putting Gemini, its newer AI-powered assistant. This is not a small feature deprecation; it is the removal of the default assistant from an enormous number of devices, so it is worth being precise about what Google has actually said, and where.
What Google has officially published
On its own blog, Google frames this as an upgrade rather than a shutdown, and it does not give a date. It says that “over the coming months” it is moving more mobile users from Assistant to Gemini, and that later this year the classic Google Assistant will “no longer be accessible on most mobile devices.” That is the firm, linkable, first-party statement: the retirement is real and it is happening in 2026, on phones and tablets, on watches and headphones that pair to a phone, and in Android Auto. Google also says home devices — speakers, smart displays, and TVs — and cars with Google built-in are not part of this wave; those keep Assistant for now and will get a separate Gemini experience later.
The 4 September date, and why we have not put a countdown on it
Beginning 4 August 2026, Google started emailing Assistant users directly, and multiple outlets — 9to5Google, Search Engine Land, Android Authority, Engadget — reported and quoted that email. Per their reporting, Google told users it will begin removing access to Google Assistant starting 4 September 2026, with the process taking a few weeks to reach everyone, and that once a device has moved to Gemini there is no switching back to Assistant on that device or its paired accessories.
That date comes from Google itself, but it reaches us through an email we cannot link and through press coverage, not through a dated official page. Our rule is that a countdown date has to sit on a first-party source we can point you to and re-check — so this entry is marked signaled with no recorded sunset date, even though 4 September is very likely the real start. If Google publishes the date on a support or blog page, we will record it and start the countdown then. Treat 4 September 2026 as the working date to plan around, not as a date we have independently confirmed on Google’s own page.
What to actually do
For most people: nothing. Gemini takes over on its own, and Google says it now handles the everyday requests — music, timers, alarms, lock-screen actions — that made Assistant useful. The care is warranted only if you lean on something specific. Press reports name Interpreter Mode (live spoken translation) and some smart-home routines as capabilities that do not carry across cleanly; if one of those, or a particular Routine or third-party action, is part of your day, check whether Gemini supports it before the change reaches your device, because the reported switch is one-way. Older, low-memory Android phones are reported to keep a stripped-down legacy Assistant rather than moving to Gemini at all.
There is no data to export and no account to close here — this is not that kind of sunset. What is worth protecting is any accessibility feature or workflow that exists specifically in Assistant and may not have a Gemini equivalent yet. That is the quiet cost of a default being swapped out from under a device: most of it is seamless, and the small part that is not tends to be exactly the part someone built a habit around.
Entry changelog
- — last reviewed.
- — Entry created. Sunset itself confirmed from Google's official blog post (the transition to Gemini, with the classic Assistant gone from most mobile devices "later this year"). The specific 4 September 2026 start date is from Google's emails to users, reported and quoted by multiple outlets on 4 August, but does not yet appear on a linkable official Google page — so the entry is marked signaled with no recorded countdown date until Google publishes the date itself. Surfaced via Layer-2 discovery.
- — Re-checked on the reported 4 September start date (D-020). Google's first-party post still gives no explicit date — it reads only "over the coming months" and "later this year" — so the entry stays signaled with no recorded countdown, per our no-inferred-dates rule. No facts changed. Will re-check again for a first-party dated page and start the countdown the moment Google publishes one.
Put this countdown in your README
Building on Google? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/google-assistant-mobile-sunset)Spot an error or a changed date? Tell us and it’s corrected the same night.