Voice search that stops working on an Android phone or a smart speaker is not always due to a simple setting being accidentally disabled. Since Google began replacing its Assistant with Gemini on mobile devices, the technical landscape has changed. A setting that worked the day before may become obsolete after a silent update, and traditional troubleshooting guides do not yet cover these changes.
Transition from Google Assistant to Gemini: the overlooked source of confusion
Most troubleshooting articles assume that Google Assistant is still the default assistant on Android. This is no longer systematically the case. Google has initiated the gradual phasing out of Assistant on Android mobile devices in favor of Gemini, with a shift that has been accelerating since the summer of 2026.
This change has a direct consequence on voice command. Voice Match needs to be reconfigured to work with Gemini, even if it was already active with the old Assistant. A user whose phone has automatically migrated to Gemini may find that the “Hey Google” command is silent, not because it is disabled, but because the voice pairing is no longer recognized by the new assistant.
To identify the causes of voice search being stopped, one must first check which assistant is active on the device. In the Android settings, the “Default apps” section followed by “Digital assistant app” indicates if Gemini has taken over. If so, re-registering your voice print via Voice Match is the first step before any other troubleshooting.
Android settings and microphone permissions: silent blocks
Aside from the transition to Gemini, several internal mechanisms within Android can cut off voice search without visible notification.
Revoked microphone permissions
Android manages microphone permissions on an app-by-app basis. A system update or battery cleaning may revoke the microphone access of the Google or Gemini app. The result: the voice command appears to be enabled in the settings, but the microphone remains blocked at the system level.
Verification is done in Settings, then Apps, then Google (or Gemini), then Permissions. The microphone must be set to “Allow” or “Allow only while using the app”.
Incorrectly configured language and region
A recurring issue concerns language settings. If the phone’s language and that of the voice assistant do not match, the voice command may display an error message stating that it is “not available in this language.” Field reports indicate that this problem affects devices configured in Swiss French or regional variants not supported by the active voice model.
- Check that the assistant’s language (in the Google app settings) is set to “French (France)” and not an unsupported variant.
- Ensure that the Android system language matches that of the assistant, or that it is included in the list of accepted secondary languages.
- On Samsung devices, an additional setting in Bixby may conflict with Google’s voice detection: disabling Bixby’s voice wake-up may resolve the issue.
New Android voice search interface: what changes concretely
Google has begun redesigning the voice search interface on Android by integrating several distinct modes. Recent tests show a voice bar combining Search, AI Mode, Search Live, and Song Search into a single interface. This redesign goes beyond a mere cosmetic change.
Voice search is becoming multimodal and conversational. The classic microphone button may no longer trigger the same behavior as before. On some devices in the testing phase, pressing the microphone now opens a combined interface where traditional voice search is just one option among others.
For a user accustomed to saying “Ok Google” and getting an immediate response, this interface change may give the impression that the function is broken. It is not, but its access has been relocated. Field reports vary on this point: some users regain the classic behavior after manually selecting the “Search” mode in the new bar, while others report that the voice command on wake screen no longer works at all with this interface.
Digital Markets Act and third-party assistants: a factor to watch
The European Union has imposed new obligations on Google through the Digital Markets Act. Android will need to allow competing assistants to access system functions comparable to those of Google, with deployment mentioned for 2027. This regulatory opening is already having concrete effects on the configuration of devices sold in Europe.
On some recent Android phones sold in France, the default assistant is no longer Google upon first startup. The user must actively choose their assistant, and if they do not, the voice command may remain inactive due to the lack of an assigned assistant.
This point is rarely addressed in troubleshooting guides, which assume that Google Assistant (or Gemini) is always pre-installed and active. On a new or reset device, checking that an assistant is properly selected in the default settings becomes a full diagnostic reflex.
Reactivating voice search: checks in order
Rather than a list of random manipulations, here is the diagnostic sequence that covers the most common cases starting from the most likely:
- Identify the active assistant (Google Assistant or Gemini) in the Android settings, under “Default apps.” If no assistant is assigned, select one.
- Re-register the voice print via Voice Match, even if it was already configured. The switch to Gemini may invalidate the old recording.
- Check the microphone permissions of the relevant app (Google, Gemini, or third-party assistant) in the system settings.
- Check the assistant’s language and that of the system. Both must be compatible, ideally identical.
- On smart speakers and displays, check that the physical microphone button is not disabled (red or orange light) and that the device is on the same Wi-Fi network as the phone.
Voice search on Android is going through a period of technical mutation. Between the replacement of Assistant by Gemini, the redesign of the voice interface, and the obligations of the Digital Markets Act, a single symptom (the silent voice command) can have very different origins depending on the device’s update date and the user’s region. Checking which assistant is actually active remains the first diagnostic gesture, before any other manipulation.
