AI-generated conceptual illustration of a phone-linked voice-assistant transition across a watch, headphones and phone-projected car display. It does not depict a Google interface or rollout screen.
Google has told existing users by email that it will begin removing access to Google Assistant from Android phones and tablets on September 4, 2026. The change may take several weeks rather than reaching every device on one day.
The notice, reproduced by 9to5Google and separately reported by The Verge, also covers some experiences that depend on a paired Android phone: Wear OS watches, headphones and Android Auto projected from the phone.
This is a narrower and more qualified development than saying Google Assistant will shut down everywhere on September 4. Cars with Google built-in are expected to retain Assistant beyond that date, while the email does not set a removal date for home or television devices.
What the September notice establishes
According to the emailed notice, removal of Assistant access begins on September 4 and could take weeks to complete. That wording matters: September 4 is the start of a phased change, not a guarantee that every affected device will switch at the same moment.
The reporting establishes that the notice came from Google to existing users. It does not amount to a new public Google product announcement carrying the September deadline. The Verge reported the same email and said it had asked Google for confirmation but had not received a response when its article was published on August 5.
The supported conclusion is therefore specific: Google has communicated the date directly to users, and two publications have reported that communication. The reporting does not independently confirm every rollout mechanism, regional detail or device-specific outcome.
Which device paths are affected
The notice identifies Android phones and tablets as the central affected platforms. It also extends the practical impact to accessories and in-car experiences that rely on an Android phone.
That includes Wear OS watches and headphones paired with the phone, as well as Android Auto when the phone projects the experience to a compatible vehicle display. Users who depend on Assistant through those paths should treat the phone transition as relevant even if the accessory itself is not being replaced.
Cars with Google built-in are a separate case. The notice says Assistant will remain available there beyond September 4, so owners should not assume that phone-projected Android Auto and a vehicle's native Google built-in system follow the same schedule.
The email does not provide the timetable for speakers, smart displays, televisions or other home devices. Their absence from this notice should not be interpreted as either a permanent exemption or confirmation of an imminent change.
This follows Google's longer Gemini transition
Google publicly outlined the broader direction in March 2025, when it said it would move mobile users from Google Assistant to Gemini. At that point, the company described phones as the first major transition and said tablets, cars, headphones and watches would follow later.
The 2025 roadmap also said unsupported mobile devices would remain unchanged at that time. The newly reported email provides a more specific mobile removal window, but the available evidence does not fully explain how every unsupported configuration will be handled during the 2026 rollout.
That distinction is important for support teams and device owners. The strategic direction has been public for more than a year; the September 4 date comes from the newer user communication.
Eligibility and feature differences still matter
Google's current Assistant-to-Gemini comparison says the Gemini mobile experience generally requires Android 9 or later, at least 2GB of RAM, a supported region and a device that is not running Android Go.
Eligibility does not by itself guarantee identical behavior. Google documents differences between Gemini and Assistant, and availability can vary by device, language and feature. It also cautions that Gemini may not always produce correct results.
Users should therefore test the tasks they actually rely on rather than treating the migration as a name change. Voice calling, messaging, media control, navigation, smart-home routines and lock-screen behavior are more useful test cases than a general check that Gemini opens.
Google's current help material still documents an option to switch from Gemini back to Google Assistant. That remains a present configuration path, but the emailed notice says Assistant access will be removed. It should not be treated as a durable workaround after the rollout reaches a device.
What users and support teams should do now
Before September 4, users can check whether each affected phone or tablet meets Gemini's stated requirements and identify the Assistant workflows that matter to them. Anyone using a paired watch, headphones or phone-projected Android Auto should include those paths in the test.
The distinction between projected Android Auto and Google built-in should also appear in support guidance. A change on the phone-dependent path does not establish the same September timetable for a vehicle's native system.
Organizations supporting managed Android fleets should avoid promising that every device will change on September 4. The notice describes a rollout lasting weeks, and the current source record does not establish a per-region or per-model schedule.
The practical deadline is therefore a preparation point rather than a single cutover moment. Users can test compatibility now, record feature gaps that affect daily use and watch Google's public support pages for more precise rollout details.
