When Google Assistant stops responding to your voice commands on the Pixel 10 Pro XL, it kills one of the phone's best features. You say "Hey Google" and nothing happens, or the Assistant pops up but doesn't process what you said. Let's get this working again.
Check the Google Assistant Settings
Start by making sure Assistant is actually set up to listen for your voice. This sounds basic, but it's the most common culprit.
Open the Google app on your Pixel 10 Pro XL. Tap your profile picture in the top right corner, then go to Settings > Google Assistant > Hey Google & Voice Match. Make sure Hey Google is toggled on. While you're here, tap Voice Match and confirm it's enabled too.
If you've never trained Assistant to recognize your voice, this is also where you'll do it. Tap Voice model and follow the prompts to say "Hey Google" a few times. That initial training step matters more than most people realize.
Retrain the Voice Model
Even if Assistant was working before, your voice can change subtly or background noise can throw off the recognition. Retraining often fixes that drop in responsiveness.
Go back to Settings > Google Assistant > Hey Google & Voice Match. Tap Delete voice model to remove your current voice profile. Then tap Voice Match and go through the setup process again. Say the four phrases clearly in your normal speaking voice, not louder or slower than usual.
I've seen this fix work after everything else failed. It takes about 60 seconds and it's totally risk-free.
Check for Interfering Settings
Several features on Android 16 can block or interfere with Google Assistant without you realizing it. Do Not Disturb mode is the biggest one. When DND is active, Assistant might only respond when your phone is unlocked, or it may not respond at all depending on your settings.
Pull down the notification shade and check if the crescent moon icon is highlighted. If it is, tap it to turn off Do Not Disturb temporarily and test Assistant again. You can also adjust DND settings to allow Assistant through even when it's on: Settings > Sound & vibration > Do Not Disturb > Apps > Google Assistant.
Sound Recognition (the accessibility feature that listens for smoke alarms or crying babies) can also conflict with Assistant. Go to Settings > Accessibility > Sound Notifications and make sure it's turned off if you're having issues.
Is the Microphone Blocked or Dirty?
The Pixel 10 Pro XL has multiple microphones, but the main one for voice pickup is at the bottom near the USB-C port. If you're using a thick case or a screen protector that extends over the bottom edge, it could be muffling your voice commands.
Pop the case off and test Assistant without it. If that fixes the problem, you know the case is the issue. Some third-party cases cover the microphone cutout just enough to cause problems.
Dirt and pocket lint can also clog the microphone grille. Take a look at the tiny holes near the charging port. If you see any gunk, use a dry soft-bristled toothbrush or a clean toothpick to gently clean it out. Don't use anything metal or sharp.
The Phone Position Matters
By default, Google Assistant won't respond when your Pixel 10 Pro XL is face down on a surface. This is a privacy feature, but it can be confusing if you've set the phone down and then try to call out to Assistant.
You can change this behavior. Go to Settings > Google Assistant > Hey Google & Voice Match and look for the option that says something like "Respond when phone is face down." Toggle it on if you want Assistant to listen regardless of position.
Similarly, if your phone is in your pocket or bag, Assistant will typically ignore voice commands by default. That's a battery saving measure and it's hard to override.
Check the Volume and Audio Output
Sometimes Assistant is actually hearing you and responding, but you can't hear it because the volume is too low. Press the volume up button on the side of your Pixel 10 Pro XL and make sure media volume isn't turned all the way down.
You can also check where Assistant sends its responses. Open the Google app, go to Settings > Google Assistant > Audio output. Make sure it's set to your preferred device (phone speaker, not a paired Bluetooth device that's not in range).
Bluetooth Accessories Can Cause Conflicts
If you've got Bluetooth headphones, a smartwatch, or a car system connected to your Pixel, they can sometimes hijack the microphone and leave Assistant unable to hear you properly. Disconnect all Bluetooth devices by turning Bluetooth off in the quick settings panel, then test Assistant.
If Assistant starts working again, pair your devices back one at a time to figure out which one was causing the problem. Some older Bluetooth headsets don't play nice with Android 16's voice wake features.
Battery Optimization Might Be Too Aggressive
Android 16 is smart about managing battery life, but it can sometimes put Google Assistant into a deep sleep to save power. If Assistant is being killed in the background, it won't be listening for your voice.
Go to Settings > Apps > See all apps > tap the three dots in the top right > Show system > search for Google Assistant. Tap it, then go to Battery and select Unrestricted. This tells the system not to restrict Assistant's background activity.
Do the same for the Google app itself. Both need to be running without battery restrictions for voice wake to work reliably.
Restart Your Pixel 10 Pro XL
A quick restart clears out temporary glitches that can mess with Assistant. If the phone has been on for days or weeks, there could be any number of small software hiccups building up.
Press and hold the Power button and the Volume up button together. The power menu will pop up. Tap Restart. Wait for the phone to fully boot up, then test Assistant.
If your phone is completely unresponsive and you can't get to the power menu, use the force restart method instead: press and hold the Volume up and Power buttons simultaneously for 10 seconds. Release when the device restarts. This won't erase any data.
Update Android 16 and the Google App
Google pushes regular updates to Assistant's backend through the Google app, and system updates can fix underlying bugs. Being behind on either can cause voice recognition to degrade over time.
Open the Play Store, tap your profile picture, and go to Manage apps & device. Tap Update all to make sure the Google app and every related component are current. Then go to Settings > System > Software update and install any pending system updates.
After updating, restart the phone and retrain your voice model as described above. The combination of fresh software and a fresh voice profile often resolves stubborn cases.
Reset the Google App's Data
If Assistant still won't respond after everything else, resetting the Google app's data can clear out corrupted settings that aren't visible in the normal menus. This is more thorough than just clearing the cache.
Go to Settings > Apps > See all apps > tap the three dots > Show system > find Google (not Google Assistant). Tap Storage & cache > Manage storage > Clear all data. This will sign you out of the Google app and remove any cached data, but your photos, contacts, and other info remain untouched. You'll need to sign back into the app and set up Assistant again from scratch.
It takes a few minutes to go through the setup, but this step has fixed Assistant for people who had tried everything else. Just make sure you're on Wi-Fi when you do it, because the setup requires a solid internet connection.