There are ongoing stability issues with Google services right now, following a major outage that hit Google Meet and other services on November 26/27.
Here is the breakdown of why “Hey Google” is likely failing for you and how to fix it.
1. The “Gemini” Conflict (Most Likely Cause on Phones)
Google is currently forcing a transition from the old Google Assistant to the new Gemini AI. This often breaks voice activation.
The Fix: Check which assistant is active.
Open the Google app (not Chrome).
Tap your profile picture > Settings.
Tap Google Assistant > “Digital Assistants from Google”.
If Gemini is selected, try switching back to Google Assistant. Gemini currently has bugs with “Hey Google” voice activation on many devices.
2. Service Outage
Your device may be affected by the server instability that hit the region this week (mostly affecting Google Meet and Cloud services).
Symptoms: You say “Hey Google,” and it either spins endlessly or says “Something went wrong.”
The Fix: This is a server-side issue.
Restart your router: Unplug your WiFi router for 30 seconds. This forces your devices to find a new, potentially less congested route to Google’s servers.
3. The “Mic Switch” Glitch (Smart Speakers/Nest)
If this is happening on a Google Nest/Home speaker, the physical microphone switch often gets dirty or stuck.
Check the switch: Look for a physical switch on the back or side. If you see orange, the mic is muted.
The “Wiggle” Fix: Even if it looks “On,” toggle the switch back and forth 5-10 times rapidly. This cleans the internal contacts, which is a known fix for Nest Minis that stop listening.
Also Read : Wicked Whims Not Working | Easy Fix
4. Samsung/Pixel Specific Bug
If you are on a Samsung or Pixel phone, a recent update might have removed the “Voice Match” permission.
Go to Settings > Apps > Google > Permissions.
Ensure Microphone is set to “Allow all the time” (or “Allow only while using the app”).
Then, go to Google Assistant Settings > Hey Google & Voice Match and Retrain Voice Model.
Quick Check:
If you are using a JBL Authentics speaker, there is a known firmware bug causing Assistant to fail every morning. A factory reset is the only temporary fix until JBL releases a patch.
Be the first to comment