Google Assistant disappears September 4. Test the boring stuff now.

Google told existing users by email that it will begin removing access to Google Assistant on September 4, 2026. The rollout may take several weeks. After it reaches an eligible device, saying “Hey Google” or holding the power button will open Gemini, and the option to return to Assistant will be gone.

This phase covers Android phones and tablets plus devices that borrow their assistant from the phone: Wear OS watches, compatible headphones and earbuds, and vehicles using phone-projected Android Auto. Cars with Google built-in keep Assistant beyond September 4 for now. Google Home speakers, smart displays and Google TV are not part of this mobile cutoff, though Google has separately said Gemini is coming to more home devices.

There are carve-outs. Google says devices that do not meet Gemini’s minimum requirements are not being moved yet, and availability still depends on region, language, account and hardware. Most eligible Android users should treat September 4 as the start of a one-way migration, not one synchronized shutdown minute.

Google’s Gemini help page currently gives holdouts this advice: if a feature you rely on is not supported, switch back to Google Assistant. The same page names media services such as podcasts, news, radio stations and some third-party music providers as unsupported in Gemini. Interpreter mode is also listed as an Assistant feature to switch back for.

That advice has an expiry date now. It is useful before the migration reaches your phone and useless afterward. The documentation may change before September, but the contradiction tells you exactly where to look: not at Gemini’s best new tricks, but at the old commands Google still describes with caveats.

There is plenty that already works. Google documents alarms and timers, flashlight and device controls, media playback, notification reading and replies, screenshots, calls, messages and some lock-screen actions through Gemini and its connected Utilities app. Some capabilities require permissions. Some are rolling out gradually. Some differ by phone maker. A feature existing in a help article does not prove your exact phone, account, language and lock-screen settings are ready.

Start with the phone locked. Ask Gemini to set a two-minute timer, name it, check how much time remains and stop it. Then create a repeating weekday alarm and delete it. Watch the Clock app, not only Gemini’s spoken answer. The result matters more than the reply.

Next, try one communication task the way you actually use it. Call a trusted contact, or draft and send a harmless message with their permission. Repeat the test while the phone is locked if hands-free use matters to you. Google’s support pages note that lock-screen calls and messages depend on settings, permissions and account state.

Run your most important routine. Do not test a novelty scene. Test the one that would annoy the household if it failed: bedtime lights, morning weather, the thermostat before leaving or whatever you use every week. Google says routines can start through Gemini when Google Home is connected, but some starters and actions remain unsupported.

Ask for the media you normally play. Use the same podcast, radio station or third-party music service, then repeat it through your usual earbuds and in Android Auto while parked. “Media works” is too broad. Your provider, paired device and driving surface are the test.

If you use Interpreter mode, supervised accounts, a work or school account, or one of the languages where Voice Match features vary, check that path separately. These are not edge cases to the people who depend on them. Google’s documentation explicitly says availability changes across accounts, languages and countries.

Finally, write down the manual route for anything that misses: the Clock app, Phone app, Google Home controls, media app, car screen or another translation tool. A backup does not need to be clever. It needs to be findable when the voice shortcut is not.

Ivy Chen would skip the feature tour and ask each person in the household for the two commands they use without thinking. Put the overlap into one short list, test it on the actual phone, watch and car, then save the manual fallback beside each miss. The person who set up Gemini should not become permanent family tech support.

Theo Marlow would keep the source boundary visible. The September 4 date comes from a Google email reported by several outlets; Google’s public migration post confirms the broader move but still uses older timing language. Google’s live help pages document both new Utilities support and remaining gaps. None of that proves every listed command works on every eligible device today.

Ivy is optimizing for a calm September morning. Theo is refusing to turn a capability list into a reliability claim. Both are useful because migrations fail in the space between “supported” and “worked when I needed it.”

A long conversation about a vacation can show what Gemini adds. It cannot tell you whether a six-word command survives a locked screen, spotty car connection or different clock app.

For each command, check four things: did the real app or device change, did Gemini report the result accurately, did it work without unlocking when that matters, and could you recover quickly when it did not? A polished answer with no changed timer is a miss. A timer that starts while Gemini says it failed is also a miss, because now you have to check by hand.

Keep the test small enough to repeat after an app update. Five ordinary commands beat a fifty-feature checklist nobody will run again. If one command is important for medication, accessibility, caregiving or driving, test it more than once and keep a non-voice route available.

Google is retiring a limited, predictable assistant for one that can reason over a screen, plan, write and hold a real conversation. That is a genuine upgrade in range.

Range is not the same as dependability. People build habits around the commands that work while cooking, carrying bags, wearing gloves, driving or waking up half-asleep. Those habits are small pieces of infrastructure in a day.

September 4 is not only a product deadline. It is the day Google starts removing the fallback its own support pages still recommend. Test the boring stuff now. The future can wait fifteen minutes.