Google Assistant Is Being Discontinued on Android Phones: What Happens When Gemini Takes Over From 4 September?

From 4 September 2026, Google says it will begin removing access to Google Assistant from eligible Android phones, tablets and paired mobile devices, with Gemini becoming the primary Google assistant. For Sydney and NSW organisations, the practical issue is not simply learning a new interface. Businesses should check device eligibility, work-profile restrictions, connected apps, privacy settings, voice commands and fallback procedures before field staff depend on Gemini during live projects.

The retirement of Google Assistant on Android marks a larger change than replacing one consumer application with another. Google Assistant was largely understood as a command layer. It opened applications, started calls, created reminders, controlled basic phone settings and passed structured instructions to other Google services.

Gemini is being positioned as a broader AI assistant capable of interpreting context, analysing screens, working with connected applications and responding to less structured instructions. That may create considerably more value, but it also changes the operating conditions around accuracy, permissions, privacy, staff training and responsibility.

In Sydney property, construction, renovation and professional-service environments, an Android phone is often part of the delivery system. Site supervisors use phones to call clients, open navigation, review calendars, photograph site conditions, confirm access, send messages, check project notes and coordinate contractors. When the assistant attached to that device changes, businesses need to know which functions remain dependable, which require different settings and which should never become an unreviewed AI action.

What Google Says Will Begin on 4 September

Google first announced in March 2025 that it intended to upgrade most mobile users from Google Assistant to Gemini. The company said the classic Assistant would eventually stop being accessible on most mobile devices and that tablets, watches, headphones and cars connected to phones would also move towards Gemini.

Reporting in August 2026 says Google has now advised users that access removal will begin on 4 September and may take several weeks to reach everyone. Once Assistant availability is removed from an affected device, the user is not expected to be able to switch back.

Eligible Android phones and tablets

Expected position from the September transition: Gemini becomes the available Google mobile assistant.

Business consideration: Test voice actions, account access and permissions before relying on the device at work.

Wear OS watches, compatible earbuds and headphones

Expected position from the September transition: Paired-device assistance is also moving towards Gemini.

Business consideration: Confirm hands-free calling, messaging and notification behaviour.

Vehicles using Android Auto

Expected position from the September transition: Assistant access is included in the reported mobile phase-out.

Business consideration: Drivers should test calls, navigation and messages while stationary before operational use.

Vehicles with Google built-in

Expected position from the September transition: Google Assistant is reportedly remaining available for now.

Business consideration: Do not assume Android Auto and Google built-in vehicles will behave identically.

Google Home, smart displays and televisions

Expected position from the September transition: They are not part of the reported September mobile removal.

Business consideration: Businesses may temporarily operate with different assistants across mobile and premises-based devices.

The staged rollout matters. Two employees using apparently similar Android phones may not change on the same day. A business could therefore have a mixed environment in which one worker still reaches Google Assistant while another receives Gemini from the same activation gesture or “Hey Google” command.

The Real Change Is From Commands to Interpretation

Google Assistant was not perfectly deterministic, but most business users approached it as a command utility. “Call the office”, “set a timer” or “navigate to this address” implied a relatively narrow action.

Gemini can work across language, images, screen content and connected services. It may interpret a request, select information, generate a response and decide which connected capability is relevant. This creates a different risk profile because the assistant is no longer only listening for a recognised instruction. It may also be reasoning about what the user intended.

That distinction is important for any organisation considering whether an AI assistant should participate in an operational workflow. Elyment’s analysis of AI agents compared with deterministic workflow automation explains why repeatable and high-consequence processes often remain better suited to fixed rules, defined fields and explicit approval steps.

Gemini may be appropriate for summarising non-sensitive notes, explaining a general concept or helping a user organise information. It should not be assumed to be the authoritative system for confirming a quotation, changing a project booking, approving a variation, interpreting a legal deadline or issuing a safety instruction.

Why Sydney Field Operations Are More Exposed Than Office Teams

Office employees usually have alternative paths. They can open a laptop, access a browser, search a shared drive or ask another team member. Contractors and project staff working across Sydney may be operating from a basement car park, occupied apartment, commercial tower, warehouse, renovation site or moving vehicle.

Their phone may be the immediate connection to:

• The customer or building manager.
• Site access instructions and strata contacts.
• The project calendar and daily crew allocation.
• Navigation between jobs.
• Photographic condition records.
• Supplier and equipment coordination.
• Variation approval and payment status.
• Emergency escalation contacts.
• Handover notes for the next trade.

A failed music request is an inconvenience. A failed instruction involving access, a customer call, a changed appointment or a site location can delay a crew, create a missed booking or leave a worker without the information expected at the point of delivery.

The correct response is not to prevent staff from using Gemini. It is to separate optional AI assistance from the organisation’s dependable operating systems.

One Business May Experience Several Different Gemini Transitions

Android fleets are rarely uniform. Even small Sydney businesses often have a mixture of personally owned phones, company devices, older handsets, different manufacturers, personal Google accounts, Google Workspace accounts and managed work profiles.

Google’s current support information says the Gemini mobile application is available on eligible Android phones and tablets with at least 2 GB of RAM running supported Android versions. Availability can also depend on the country, language, account and device configuration.

Google also states that Gemini cannot be accessed inside an Android work profile. This creates a significant operational distinction. An employee may be able to use Gemini through the personal side of a phone while the organisation’s managed applications and project information remain isolated inside the work profile.

Android version and memory

What may differ: Gemini eligibility and feature availability.

Control required: Record the operating system, model, RAM and update status for each operational device.

Personal or company ownership

What may differ: Who controls updates, permissions and stored activity.

Control required: Define minimum settings for any personal device authorised for business work.

Personal or Workspace account

What may differ: Available features and administrative controls.

Control required: Test the account actually used by the employee rather than a separate demonstration account.

Android work profile

What may differ: Gemini cannot directly operate inside the managed work-profile environment.

Control required: Do not encourage staff to copy protected work information into the personal profile.

Language and region

What may differ: “Hey Google” and some action features may not be available.

Control required: Test the employee’s selected language and actual Australian account configuration.

Paired watch, headset or vehicle

What may differ: Hands-free actions may change separately from the phone interface.

Control required: Test each operational device combination, not only the handset.

The Work-Profile Gap Requires a Policy Decision

The inability to access Gemini within an Android work profile should not be treated as a minor technical limitation. It affects how organisations separate company information from personal applications.

A poorly managed transition could lead employees to:

• Move client information into personal notes so Gemini can access it.
• Take screenshots of managed applications.
• Copy project addresses, messages or documents into personal AI chats.
• Connect personal Gmail, Photos or messaging services to complete work tasks.
• Use an unmanaged personal assistant as an informal bridge between protected systems.

Each shortcut weakens the purpose of the work profile. Businesses should instead decide which information Gemini may access, which work must remain inside managed applications and which capability requires a properly governed integration or controlled workflow automation system.

Where a field worker needs a project address, customer phone number or approved site note, the preferred solution is a reliable mobile project system with role-based access. The employee should not need to expose the information to a personal AI assistant merely to retrieve it quickly.

A Mobile Assistant Is Now a Data-Access Point

Gemini on Android is hosted through the Google application and may use device capabilities such as the microphone, camera, contacts, location and screen context according to the permissions granted. Connected apps can extend its reach into services such as messaging, calendars, files and other Google applications.

This makes the assistant useful, but it also makes configuration important. Staff should understand that invoking Gemini over an application can expose screen context or a screenshot when the relevant settings are enabled. Uploading a photograph, speaking a project address or asking about an open document can introduce operational or personal information into the Gemini interaction.

Google’s Gemini privacy settings also affect functionality. When Gemini Apps activity is turned off, Google says some core phone, messaging and utility connections can remain available, while a broader range of connected services may become unavailable. Even where activity is off, conversations may be retained temporarily so the service can respond and protect its systems.

This creates a real management trade-off. A business cannot simply instruct staff to disable every data feature and assume Gemini will continue to provide the same connected experience. It must decide which functions are necessary, what information those functions may receive and whether the selected account and retention settings comply with the organisation’s privacy position.

The Australian Privacy Question Starts Before the First Prompt

The Office of the Australian Information Commissioner’s guidance on commercially available AI recommends that organisations avoid entering personal information, particularly sensitive information, into publicly available generative AI tools because of the difficulty of controlling how that information may be used, retained or removed.

For a property or renovation business, personal information can appear in ordinary operational material. A prompt may contain a resident’s name, address, access instructions, telephone number, email, photograph, invoice, building issue, insurance detail or legal correspondence. The fact that an employee entered the information by voice rather than typing it does not remove the privacy issue.

A practical mobile AI policy should therefore classify information before staff use the assistant:

1. Open information: Public product information, published guidance, general technical explanations and non-confidential drafting.
2. Internal operational information: Process notes, templates and non-personal project instructions that may still require an approved business account.
3. Client or property information: Names, addresses, photographs, correspondence, access arrangements and project records that should only be used under an approved and documented process.
4. Restricted information: Identity documents, financial information, health information, legal advice, passwords, security codes, keys, alarm details and other information that should not be placed into an open mobile AI interaction.

NSW Government Work Requires an Additional Assurance Layer

NSW Government agencies have a formal requirement to apply the NSW AI Assessment Framework to the use of AI systems. The framework focuses on governance, privacy, security, transparency, accountability and documented risk controls across the AI lifecycle.

Private businesses are not automatically subject to that government framework, but contractors delivering work for councils, agencies, infrastructure operators or public facilities should determine whether client requirements restrict the use of consumer AI assistants around project information.

NSW public-sector recordkeeping guidance also states that AI-generated content forming part of official work must be accurate, complete, securely maintained and lawfully disposed of. A spoken answer from Gemini should not become the only record of an instruction, approval or decision.

What Businesses Should Test Before the Cutover

A useful migration test should reproduce real work rather than ask staff whether they like the Gemini interface.

1. Confirm device eligibility. Record the phone model, operating system, RAM, Google application version, account type and whether the device uses a managed work profile.
2. Record current Assistant-dependent actions. Identify the commands employees actually use for calls, navigation, timers, messages, calendars, reminders, utilities and paired devices.
3. Repeat those actions with Gemini. Use the worker’s normal language, account, headset, watch and vehicle configuration. Do not rely on a demonstration performed on a new flagship phone.
4. Check permissions and connected apps. Review microphone, camera, contacts, location, screen context, lock-screen access and every connected service.
5. Test without sensitive information. Use fictional client names, sample addresses and non-confidential project data during evaluation.
6. Define the fallback. Staff should know how to make a call, open navigation, retrieve a contact or report a problem without using the assistant.
7. Document the approved uses. Create a short mobile AI instruction that explains permitted tasks, prohibited information, verification requirements and escalation paths.

Businesses with larger or more complex device fleets can use an AI readiness assessment for Sydney operations to map users, devices, data, permissions and business consequences before approving broader AI access.

The Transition Needs an Owner, Not Just an IT Ticket

The September change crosses several areas of responsibility. Technology staff may understand the device configuration, but they may not know which voice actions are essential to a site supervisor. Operations staff may know the workflow, but not how activity retention and connected applications function. Privacy staff may identify information risk without knowing how a hands-free restriction affects workers travelling between projects.

Operations manager

Transition task: Identify critical mobile actions and unacceptable workflow failures.

IT or managed-service provider

Transition task: Audit devices, accounts, operating systems, profiles, permissions and update status.

Privacy or compliance lead

Transition task: Define prohibited information, retention expectations and approved account types.

Project managers

Transition task: Test site access, communication, navigation and handover scenarios.

Team leaders

Transition task: Brief staff, collect problems and reinforce fallback procedures.

Executive sponsor

Transition task: Accept residual risk and fund device replacement or workflow changes where required.

Older Phones Should Not Be Treated as a Permanent Exception

Google’s original transition announcement said Assistant functionality would not change at that time for mobile devices that did not meet Gemini’s minimum requirements. That statement provided a temporary exception, not a long-term device-support commitment.

Organisations should not retain outdated Android phones merely to preserve the classic Assistant. Older devices may create wider security, support, battery, application-compatibility and mobile-device-management risks. Where a handset cannot support the approved future operating environment, replacement should be assessed through the normal fleet lifecycle.

The correct question is not whether an old phone can keep Assistant for a little longer. It is whether the device remains supportable, secure and capable of running the applications required for the employee’s work.

Where the Cost Will Appear

Gemini itself may not create a separate migration invoice for every user, but the transition can still produce operational costs:

• Replacement of unsupported or unreliable devices.
• Staff testing and training time.
• Managed-service or mobile-device-management changes.
• Privacy and acceptable-use policy updates.
• Redesign of shortcuts that depended on Assistant behaviour.
• Support requests during the staged rollout.
• Lost time where workers cannot complete expected hands-free actions.
• Development of controlled alternatives for sensitive workflows.

These costs should be compared with the operational benefit. Gemini may reduce time spent interpreting notes, finding general information, preparing drafts or understanding content visible on a screen. The return depends on whether the business gives employees safe, relevant use cases rather than unrestricted access with no measurement.

What Should Remain Outside the Mobile Assistant

A mobile AI assistant should not become the organisation’s final authority for:

• Pricing, scope or contractual commitments.
• Variation approval.
• Legal or conveyancing deadlines.
• Payment instructions or bank details.
• Worker safety directions.
• Technical confirmation of a substrate, structure or hazardous material.
• Strata approval status.
• Customer identity verification.
• Access codes, keys or alarm information.
• The final project record.

Gemini may help a person prepare, locate or explain information. The source system, approved document and responsible person should still determine what the organisation does.

Review the Workflow Before the Assistant Changes

Assess Android devices, work profiles, permissions, connected apps, privacy controls, staff instructions and operational fallbacks before Gemini becomes part of day-to-day project delivery.

Request a Project and Workflow Review

The Operational Lesson From Google’s Assistant Change

Google Assistant’s removal is a visible example of a wider business issue. Consumer technology can become embedded in operational delivery without ever being formally approved as infrastructure. Staff develop habits, shortcuts and informal processes around a feature, then the platform owner changes it.

The answer is not to freeze technology or avoid AI. It is to identify where external tools have become operational dependencies and place appropriate controls around them.

For Sydney and NSW organisations, the 4 September transition should be treated as a practical mobile changeover. Inventory the devices. Test the real commands. Review the data settings. Protect managed information. Brief staff. Maintain a fallback. Keep approvals and project records in controlled systems.

Gemini may become a considerably more capable assistant than the product it replaces. Capability, however, is not the same as operational readiness. The businesses that manage the transition well will be those that decide where AI may assist, where a person must verify and where a dependable workflow must remain in control.