Google voice search suddenly stopping to respond is affecting an increasing number of Android users. The problem is not always limited to a faulty microphone or a forgotten setting. Between the migration to Gemini, the automatic deactivation bugs reported since 2024, and sometimes missing system modules, the causes are multiple and their solutions very different from each other.
Migration to Gemini and voice search: what has changed on Android
On recent versions of Android, Google has gradually replaced the classic Assistant with Gemini as the default voice assistant. This switch has moved the voice activation settings to a different path: Settings > Google > Services > Search, Assistant and Voice > Gemini > Talk to Gemini hands-free.
You may also like : Practical Tips: How to Drill Cellular Concrete Without Damaging It
Many users think the feature has disappeared when it has simply changed location. If Gemini is not configured or not allowed on the phone, the command “Hey Google” may remain inactive without an explicit error message.
| Cause of malfunction | Observed symptom | Resolution path |
|---|---|---|
| Unfinished migration to Gemini | “Hey Google” does not trigger anything, no error message | Settings > Google > Gemini > enable hands-free mode |
| Automatic deactivation bug (reported since 2024) | The command works for 1 to 2 days then stops | Reactivate Voice Match, clear the cache of the Google app |
| Missing hotword modules (custom ROM, partial GApps) | “Hey Google” unavailable even after activation | Check hotword packages via the system manager |
| Incorrectly configured language or language conflict | Message “command not available in your language” | Settings > Languages and input > check the primary language |
| Power saving mode active | Intermittent or absent voice detection | Disable power saving mode for the Google app |
This table covers the majority of cases encountered. Understanding why Google voice search is not working anymore starts with identifying the right cause before attempting random manipulations.
You may also like : How to Invest Smartly in Cryptocurrencies and Maximize Your Returns
Hey Google automatic deactivation bug: a server-side issue
Since 2024, several threads in the Google Assistant community describe a recurring pattern: the user activates “Hey Google” in the settings, the function responds correctly for one or two days, then deactivates itself without intervention.
This behavior points to a bug on Google’s side rather than a configuration error. Affected users have attempted to reinstall the app, retrain the voice model via Voice Match, and clear the cache, without lasting results.
What to do in the face of this persistent bug
- Regularly check that the “Hey Google” option is still checked in the Assistant or Gemini settings, as it may uncheck itself after an update
- Disable and then re-enable Voice Match by re-recording your voice print, which forces the system to recreate the recognition files
- Ensure that the Google app and Google Play services are up to date, then clear the cache (not the data) of the Google app via Settings > Apps > Google > Storage
- Monitor the Google app’s update notes for any potential official fix, as the issue seems related to an unresolved server malfunction for all devices
For affected users, the only reliable workaround remains to manually check the status of voice activation every few days, while waiting for a stable fix.
Hotword modules and custom ROMs: the invisible cause
Consumer troubleshooting guides never mention Google hotword modules. On a standard Android device delivered by the manufacturer, these modules are pre-installed and manage the continuous detection of the keyword “Hey Google” or “OK Google”.
On devices equipped with custom ROMs (LineageOS, CalyxOS) or that have installed Google Apps via packages like NikGapps, these modules may be absent or partially installed. The result: the “Hey Google” option appears in the settings but produces no effect.
Technical check on custom ROM
The command pm list packages | grep hotword executed via a terminal confirms whether the necessary packages are present. If nothing shows up, the voice detection modules are not installed. You then need to add the corresponding hotword addons for the version of GApps used.
This case remains minority, but it explains a category of failures that neither reinstalling the Google app nor resetting the settings can fix.
Language conflict and microphone permissions: two quick checks
The message “this command is not available in your language” sometimes appears even when the phone is set to French. Several users on Google forums have reported this issue on Huawei and Xiaomi devices. The frequent cause: the Assistant’s language and the system’s language do not match.
On Xiaomi, the path goes through Settings > Additional settings > Languages and input > Manage keyboards, then check that Google voice input is indeed enabled. On devices where Google is not the default voice engine, you also need to manually select Google as the voice recognition service.
- Check that the Google Assistant language (in the Google app settings) exactly matches the phone’s system language
- Grant microphone permission to the Google app via Settings > Apps > Google > Permissions > Microphone
- Disable power saving mode or exclude the Google app from battery optimization, as this mode cuts off voice detection in the background
These checks take less than a minute and resolve a significant portion of cases where voice search seems to have disappeared. If the problem persists after these steps and after consulting the diagnostic table above, the malfunction is likely due to the automatic deactivation bug or a conflict with the Gemini migration, two situations that depend on a fix from Google.