Google Assistant is being permanently removed from Android from 4 September 2026

Google Assistant, launched in 2016, has been switched off on Android phones, tablets, Wear OS watches, headphones, and Android Auto. The removal began on 4 September 2026 and is rolling out gradually by device and region over several weeks. Once your device makes the switch, Google is clear about what happens next: “Once availability is removed, you will no longer be able to use or switch back to Google Assistant.”

There is no revert button. This is a one-way door.

What is actually changing

Gemini replaces Google Assistant as the default voice assistant on Android. The “Hey Google” wake word still works, and physical assistant buttons on devices will continue to function. The experience behind those triggers, though, is now Gemini rather than Assistant.

The rollout does not cover everything at once. Cars with Google Built-in will keep running Google Assistant beyond 4 September 2026. Google TV devices, Nest Home speakers, and smart displays are on a separate roadmap and are not affected by this mobile removal. Devices that fall below Gemini’s minimum requirements, specifically Android phones and tablets running Android 9 or older, or with less than 2 GB of RAM, will also retain Assistant for the time being. Android Go devices get a lightweight alternative called Gemini Go.

What Gemini can and cannot do

Gemini handles most of the everyday tasks people used Assistant for: setting alarms, sending messages, controlling device settings, and managing compatible smart-home products. Conversations sync across devices, which Assistant never did, and Gemini is better suited to multi-step requests that need context to be held between turns.

Where things get complicated is the feature gaps. Google’s own support documentation confirms several capabilities that Assistant had and Gemini does not yet have:

Interpreter Mode is gone from Gemini entirely. This feature allowed real-time spoken translation between two people speaking different languages. Google says the equivalent functionality now lives in the Translate app via its “Conversation” button, but it is a separate app, not a voice shortcut.

Routines are partially supported. If you have connected Google Home to Gemini, some routines can still be triggered. But routines with unsupported starters or actions, particularly those requiring follow-up questions, will not work. Shortcuts to start a Routine and Routines attached to alarms in the Clock app no longer function on Android phones.

Media controls have gaps. Podcasts, news, radio stations, and third-party music providers are not supported in Gemini at this stage. If you used Assistant to start a podcast or tune into a radio station by voice, that does not carry over.

Quick Phrases on phones, such as saying “Snooze” to dismiss an alarm without unlocking the screen, appear to no longer work on Android with Gemini active.

Visual response cards have also changed. Weather and similar queries still return an answer, but without the detailed visual cards that Assistant displayed.

What this means for you

If you use Google Assistant for basic queries, reminders, timers, and smart-home control, the transition will mostly be seamless. Gemini handles those well, and in many respects it handles more complex questions better than Assistant ever did.

If your workflow relied on Interpreter Mode, you will need to get used to opening the Translate app manually. It is not a terrible alternative, but it is a different interaction pattern.

If you have built out routines in Google Home and use them heavily, it is worth auditing them now. Open the Google Home app and check which routines are flagged as incompatible with Gemini. Some may need to be rebuilt or simplified.

For media, the workaround is to use individual apps directly rather than asking Gemini to launch a specific podcast or radio station. Voice control for Spotify, YouTube Music, and similar services through Gemini works if those apps support the integration, but it is not as broad as what Assistant offered.

There is also a privacy consideration worth flagging. Gemini’s activity settings are separate from Assistant’s. If you want to prevent future chats from being used to improve Google’s models, you need to turn off the “Keep Activity” setting in Gemini specifically. Note that doing so also disables integrations with Maps, Google Home, Workspace, and YouTube, and Google still retains chats for 72 hours regardless.

Why Google is doing this now

Google Assistant was built to recognise commands and fire off isolated actions. That was a reasonable design in 2016. The expectation from voice assistants has shifted considerably since then, towards understanding intent, maintaining context across a conversation, and handling tasks that span multiple steps or services.

Maintaining two separate assistant experiences, one built on the older command-and-response model and one on a large language model, made less sense as Gemini matured. The Gemini app reached 950 million monthly active users in the second quarter of fiscal 2026, with daily active users tripling year on year. Google is consolidating around the platform that has the momentum.

The timeline did slip. In March 2025, Google said classic Assistant would stop being accessible on most mobile devices later that year. That was pushed to 2026. The 4 September 2026 date is the firm line that Google has now committed to and begun enforcing.

A few things worth doing now

If you have not already made the switch voluntarily, it is worth spending a few minutes on the following before Gemini arrives on your device:

• Check your Assistant routines in the Google Home app and note which ones may not carry over.
• If you relied on Interpreter Mode regularly, download the Google Translate app and familiarise yourself with the Conversation feature.
• Review your Gemini activity settings and decide whether you want Keep Activity on or off, understanding the trade-offs either way.
• If you use third-party media services by voice, test whether they work through Gemini before assuming they do.

The transition is not optional and it is not reversible. Getting ahead of the gaps now is more useful than discovering them mid-conversation later.