Google Assistant Starts Disappearing From Android on September 4: What to Test Before Gemini Takes Over

Google Assistant is finally getting a concrete mobile end date. Google says it will begin removing access to classic Google Assistant from phones, tablets and paired mobile devices on September 4, 2026, with the rollout expected to take a few weeks. Where Gemini is available and the device meets its requirements, Gemini becomes Google's assistant experience instead.

The useful part is not mourning another product in the Google graveyard. It is checking whether the five or six voice actions that actually matter each day still work before the old fallback disappears.

There are real edge cases. Google's current Gemini documentation requires Android 9 or later and at least 2 GB of RAM, excludes Android Go, restricts Android Work Profile access, and still lists some familiar Assistant features as unsupported in Gemini. Meanwhile, Google's current help pages still contain older language saying users can switch back to Assistant if a feature is missing — but the new shutdown notice says that once Assistant access is removed, switching back will no longer be possible.

Status check — August 10, 2026: September 4 is the start of the removal, not a promise that Assistant disappears from every device at midnight. Google says the process may take several weeks. Device, account, country and language support can differ.

The quick answer

For most reasonably recent Android phones, the transition should be straightforward: use Gemini as the primary assistant and keep the same familiar invocation methods, including “Hey Google” where supported.

The people who should test early are those who rely on Assistant for hands-free device control rather than general questions — alarms, calls, messages, smart-home commands, media, driving, accessibility routines or language tools.

The key idea is simple: do not test whether Gemini can answer a clever question. Test whether it can replace the boring commands you depend on.

What actually changes on September 4

Google announced the broader migration in March 2025, saying classic Assistant would eventually stop being accessible on most mobile devices while Gemini expanded to phones, tablets, cars, headphones and watches.

The new August 2026 notice adds the missing deadline. Reporting based on Google's user email says the company will begin removing Assistant access on September 4 and expects the change to take a few weeks to reach everyone. After removal reaches a device, users will no longer be able to switch back to classic Assistant there.

The affected mobile ecosystem includes Android phones and tablets plus paired devices such as watches, headphones and earbuds. Android Auto is also part of the migration. Cars with Google built-in are a separate case and are expected to retain Assistant for now.

Google Home speakers, smart displays and Google TV are also on separate migration paths. Google has been rolling out Gemini-powered home experiences, but the September mobile cutoff should not be read as one universal shutdown date for every Assistant-branded device in the house.

That distinction matters because “Google Assistant is shutting down” sounds like one switch. In practice, Google is replacing a family of Assistant experiences on different schedules.

First check: can the phone actually run Gemini?

Google's current minimum requirements for the Gemini mobile app on Android are unusually modest, but they still exclude some older and low-end devices.

As of August 10, Google lists:

• Android 9 or later;
• 2 GB of RAM or more;
• a supported phone or tablet;
• a supported country and language;
• an eligible Google account.

Google also explicitly says Android Go does not support the Gemini mobile app.

For account access, Google says users generally need to be at least 13 or the applicable age in their country, with parental approval available for younger users. Work and school accounts need access to Gemini Apps through the organisation. The Gemini mobile app cannot be accessed in the Android Work Profile.

That produces a small but important decision tree:

Can the device run Gemini?
├─ Yes → test the actual Assistant workflows now
└─ No
   ├─ Is the phone otherwise still useful? → plan manual/app shortcuts for key tasks
   └─ Is assistant access essential? → evaluate an OS/device upgrade on its own merits

A disappearing voice assistant by itself is a poor reason to buy a new phone. First identify which functions would genuinely be lost and whether the underlying apps already provide them directly.

Run this five-command migration test

A general AI benchmark will not tell you whether the transition is good for your life. A five-command test will.

Pick five commands used repeatedly and run each one through Gemini before September 4. Do not invent aspirational use cases; use the commands that would actually be annoying to lose.

1. A clock command

Try something like setting a timer, creating an alarm and then changing or cancelling it.

Google said in its original migration announcement that Gemini had been updated to support common Assistant actions including timers. The point of testing is not whether the feature exists in a product description, but whether it behaves correctly on the specific phone, language and lock-screen state being used.

Fallback: make sure the Clock app is easy to reach without voice.

2. A communication command

If voice calling or messaging is important, test one normal contact and the exact app normally used.

Do this while stationary and in a safe setting. A hands-free command that requires extra confirmation or fails to resolve a contact can feel dramatically different in a car or while carrying something, even though both systems technically “support messaging.”

Fallback: pin the relevant contact or messaging action where it can be reached quickly.

3. A smart-home command

Test the real routine: a room, light, thermostat, plug or scene that is used frequently.

Generative answers are not the hard part here. Deterministic execution is. A smart-home command is either sent to the correct device with the correct state or it is not.

Fallback: make sure the same control is visible in the Google Home app or the device maker's app.

4. A media command

This is one of the highest-risk categories for parity gaps. Google's current Gemini help page still says some media providers are unsupported, specifically listing podcasts, news and radio stations, plus some third-party music providers.

Test the exact service and request style normally used. “Play music” working does not prove that a particular radio station, podcast or third-party service will behave the same way.

Fallback: create a direct app shortcut or favourite for the content that matters.

5. The one unusual command that would hurt most to lose

For some people this is Interpreter mode. For others it is a routine, a lock-screen action, a navigation request, an accessibility workflow or a command sent through headphones.

Google's current Gemini help page still lists Interpreter mode among familiar Assistant features that are not supported. That is exactly the kind of gap worth finding now rather than after the fallback is removed.

The test should end with a tiny table:

That table is more useful than arguing about whether Gemini is “better” than Assistant in the abstract.

Check “Hey Google” separately from Gemini availability

A language can support the Gemini app without supporting every assistant-style action.

Google's current availability page marks a number of supported languages with an asterisk and explains that those languages do not support “Hey Google” voice commands and some Gemini action features.

So there are three different questions:

1. Can the Gemini app run in this language?
2. Can “Hey Google” activate it in this language?
3. Can it execute the specific phone or app action needed?

A “yes” to the first does not guarantee a “yes” to the other two.

If hands-free use matters, test the actual trigger, not just the Gemini app icon.

Work accounts are a separate compatibility problem

Gemini support through a personal Google account does not automatically prove that a work setup will behave the same way.

Google says work and school users need Gemini Apps access through their organisation. Its setup documentation also warns that some features, including Assistant-powered quick voice actions, may not be available with work or school accounts.

Android Work Profile adds another boundary: Google currently says the Gemini mobile app cannot be accessed inside the Work Profile itself.

For anyone who mixes personal and managed apps on one phone, the right test is therefore not simply “Does Gemini open?” It is:

• Which Google account is Gemini using?
• Can it access the app or data needed for the command?
• Is that app inside the personal profile or Work Profile?
• Does the organisation permit Gemini Apps?
• Does the action cross a policy boundary the old Assistant workflow handled differently?

Do not try to work around an employer's mobile-management policy just to restore convenience. If a work action matters, the administrator's supported path is the durable one.

The documentation has a temporary contradiction — and it matters

Google's current Gemini help pages still tell users that if a familiar Assistant feature is unsupported, they can switch back to Google Assistant.

The newly reported shutdown notice says something different for the future: once Assistant availability is removed from a device, users will no longer be able to use or switch back to Google Assistant on that phone, tablet or paired device.

Those statements are not necessarily inconsistent in time. The switch-back option can exist today and disappear when the September removal reaches the device.

But it creates a practical deadline. Anyone relying on the switch-back button as a permanent workaround should assume that workaround is temporary unless Google publishes updated guidance saying otherwise.

This is also why feature-parity testing is worth doing before September rather than after it.

Do not confuse the mobile cutoff with Google Home

Smart speakers and displays are easy to misunderstand because they also use the Assistant name.

Google's original migration announcement said home devices would receive a separate Gemini-powered experience. Current Gemini documentation likewise treats non-mobile devices differently, and Google now has a distinct Gemini for Home rollout for eligible home devices.

The September 4 mobile removal therefore should not be used as a reason to factory-reset a Nest speaker, rebuild a smart-home routine or replace a TV.

For each device category, check its own product notice:

• phone/tablet: mobile Gemini transition;
• watch/headphones/earbuds: paired-device transition;
• Android Auto: in-car mobile transition;
• Google built-in vehicle: separate timeline;
• Home speaker/display: Gemini for Home timeline;
• Google TV: separate TV rollout.

One Google account can sit across all of these without every device changing on the same day.

A 10-minute pre-shutdown checklist

This is the low-effort version worth doing before September 4.

Minutes 0–2: check eligibility

Open Android settings and confirm the OS version. If the phone is unusually old or low-memory, check Google's current Gemini device requirements rather than assuming support.

Minutes 2–4: make Gemini the assistant now

On eligible phones, Google says the Google app should be set as the default digital assistant app. Gemini can then be selected as the mobile assistant and invoked through supported touch or voice methods.

Minutes 4–7: run the five commands

Test clock, communication, smart home, media and one critical personal workflow. Test the same language and normal lock-screen state used in real life.

Minutes 7–9: create fallbacks

Add shortcuts for anything unreliable. The goal is not to reproduce Assistant perfectly. It is to make sure a missing voice command cannot block a basic task.

Minute 10: write down the failures

Keep only failures that matter repeatedly. Then re-test them after major Gemini updates before the shutdown reaches the device.

This avoids two bad reactions: assuming the migration will be seamless, or assuming every Gemini limitation requires changing phones or ecosystems.

What should not be assumed yet

Several things can change between August 10 and the end of the September rollout.

Do not assume today's unsupported-feature list is final. Google has been adding Assistant-style actions to Gemini, and a feature missing today may arrive before or during the transition.

Do not assume the old switch-back instructions will remain valid. The shutdown notice explicitly says the option disappears once removal reaches the device.

Do not assume every device changes on September 4. Google says the removal begins then and may take weeks.

Do not assume every Gemini language has the same voice/action support. Google's own language list distinguishes full assistant-style support from app availability.

Do not assume a work account behaves like a personal account. Licensing, administrator settings and Work Profile boundaries can change what is available.

The migration is broad, but the failure modes are very local.

What to watch next

Three updates matter more than another generic “Gemini vs Assistant” comparison.

First, watch Google's Gemini help pages for feature-parity changes, especially media services and Interpreter mode.

Second, watch for an updated Google support notice that replaces the current “switch back to Assistant” wording with post-shutdown instructions. That will clarify the final fallback behaviour.

Third, watch device-specific migration notices for Android Auto, watches, headphones, Google built-in cars and home devices. Those categories are close enough to feel like one assistant ecosystem but are not on one identical schedule.

Bottom line

Google Assistant's mobile retirement is no longer a vague future plan. The removal begins September 4, 2026 and is expected to roll out over several weeks.

For most recent Android phones, Gemini should become the Google-provided assistant. The useful preparation is not a full phone migration project. It is ten minutes of testing: confirm device and account eligibility, run the handful of commands that matter, identify any unsupported media or language workflows, and create a manual fallback for the failures.

The biggest mistake would be discovering after the rollout that the one “boring” Assistant command used every day was the one Gemini still handles differently.

Sources

Checked August 10, 2026:

• Google — The Assistant experience on mobile is upgrading to Gemini
• Google Gemini Help — Gemini mobile app availability and device requirements
• Google Gemini Help — Get started with the Gemini mobile app
• Google Gemini Help — What you can do with the Gemini mobile app
• The Verge — Google Assistant will disappear from your phone next month, August 5, 2026