Android Oreo is finally here for some Pixel and Nexus devices. While Google promises the new Android version will improve the overall performance of your phone, it appears that’s not exactly the case. Because people have already encountered various issues caused by Android O.
According to some reports, Android Oreo breaks the OK Google feature on some devices. Even though everything was fine in Android Nougat, users are now unable to perform some sound commands.
I’ve searched online for potential solutions, and as it appears, there’s a way to fix the problem. Unlike some other issues, that users basically have to wait for Google to fix them through updates. So, Let’s see what can we do about OK Google issues in Android O.
Solution 1 – Retrain OK Google
The solution that helped the majority of Android users with the OK Google problem is simply retraining the assistant. It looks like installing the update somehow disrupted the assistant, so retraining is needed.
In case you’re not sure how to retrain Google Assistant, follow these instructions:
- Go to Settings
- Go to Apps & notifications > expand Advanced > Default apps > Assist & voice input
- Tap the settings (gear) icon next to Assist app
- Go to “Ok Google” detection
- Now, choose Delete voice model, to reset Google Now settings
- After that, choose Retrain voice model
- Finish the training
That’s all. After re-training your assistant, Google Now should be working seamlessly once again. However, if re-training didn’t get the job done, move on to the next solution.
Solution 2 – Check your language settings
There’s also a slight chance installing Android Oreo corrupted your language settings. So, check if your Voice language matches your system language, to be sure Google Now will work well.
To check Voice language settings, follow these instructions:
- Go to Settings
- Go to Apps & notifications > expand Advanced > Default apps > Assist & voice input
- Tap the settings (gear) icon next to Assist app
- Tap Languages
- Make sure the right language is selected
Solution 3 – Check for updates
And finally, maybe the update itself disrupt Google Now, with some internal bug. That’s not the case with the Nexus and Pixel devices, but could be with other manufacturers (this article was written at the time when only Nexus and Pixel devices had Android Oreo).
If the update indeed caused the problem, Google will eventually acknowledge the issue, and release a fixing patch. So, if you’ve tried both of the abovementioned solutions, and still have problems with Google Now assistant, make sure your phone is up to date.
That’s about it. I certainly hope at least one of these solutions helped you resolve the problem with OK Google after installing the Oreo update. If not, let me know in the comments below, or reach me out on Twitter.
Yeah I have a G5 and my ok google has stopped as well…Really sucks when your job is driving for a living … TRIED EVERYTHING so frustrated
no more ok google and hey google on oreo now.
I have the Oreo 8.0 in a brand new Xiaomi A1 and ok Google is not an option. It appears in light grey, can’t turn on and when the system suggested me to use it, I clicked on it and the same as some users in the comments happened: connection fail… Me wifi works just fine. I can’t retrain it 🙁
O have the same problem in xiaomi mi a1 if you can fix that text me the solution please
I am using a Cubot X18 running Android 7 and everything was running perfectly, including the new ‘Hey Google’ Google Assistant feature. The Google app was updated and I suddenly noticed that voice commands were not working anymore. I tried to retrain the voice but although it was asking me to say ‘Ok Google’ the voice training wasn’t being accepted. The actual part of the menu where you turned the Google Assistant on was greyed out. As a last resort I uninstalled the latest update and then the phone would let me retrain the voice which gave me back ‘Ok Google’ but not the Google Assistant. I physically tapped ‘Voice Search’ a few times and got a prompt that the new ‘Google Assistant’ was available. I tapped on the prompt and then everytime I said ‘Ok Google’ I got Google Assistant back BUT not the ‘Hey Google’ command. Reinstalling the update put me back to square one and I had to do it all over again, so the update is obviously buggy, but at least I’ve got the Google Assistant back, but only by using the command ‘Ok Google’ there is no option now to train the voice to accept ‘Hey Google’ as previously.
Further to this issue here’s the fix. Go to the Google app and uninstall updates. Then you will be prompted to set up the app again and do voice training. It will ask you to say “OK GOOGLE” 3 times and then it is trained and works to unlock the phone using the Smart lock feature in settings under security. Auto updates will then update all associated apps and functions. Once this is done you will get a notification that Hey Google voice commands are available. DO NOT DO THIS AND JUST CLEAR THAT NOTIFICATION. The smart lock voice identification doesn’t work if you update it with the Hey Google command. You can only continue to use Ok Google but it works. I tried this on 3 different pixel 2 and this is still working. Good luck
I have 3 brand new pixel 2 xl and all 3 voice trained during initial set up and then all 3 voice for smart lock turned off and couldn’t be retrained. Google assistant still responds to ok Google properly. Google support doesn’t acknowledge there is a problem so I say let’s every pixel owner return for a refund and buy a Samsung or other phone. Bet they find a fix real fast if this happens.
Thanks for the help, but I am experiencing the exact same issue as Stephen in the comments. I can’t even make it to the suggested steps as my OK Google detection is entirely turned off and when I try to re-enable it, I just get a loading screen and then after about 15 seconds I get a window saying that I can’t connect (My Network is working at 100%). Very frustrating but I can hold out for an Update Fix as long as I know it’s an issue being addressed. My phone is an Original Pixel XL on Verizon.
Thanks for the help, but I am experiencing the exact same issue as Stephen in the comments. I can’t even make it to the suggested steps as my OK Google detection is entirely turned off and when I try to re-enable it, I just get a loading screen and then after about 15 seconds I get a window saying that I can’t connect (My Network is working at 100%). Very frustrating but I can hold out for an Update Fix as long as I know it’s an issue being addressed. My phone is an Original Pixel XL on Verizon.
After 8.1 it doesn’t work at all. I can’t even turn okay google detection on anymore it is just permanently greyed out. I guess google is taking a page out of apples playbook and taking features away from customers in order to press them to buy the new phone
After 8.1 it doesn’t work at all. I can’t even turn okay google detection on anymore it is just permanently greyed out. I guess google is taking a page out of apples playbook and taking features away from customers in order to press them to buy the new phone
I was quite happy with 8.0, after the upgrade to 8.1 I found that the voice assistant’s operation erratic. Frequently, it will respond to the OK Google and then not do anything thereafter. What is annoying is that I’ve become rather dependent on it and now have to go back to the old fashioned way. BTW, I have a first gen Pixel XL.
Can you revert to 8.0 and how?
I was quite happy with 8.0, after the upgrade to 8.1 I found that the voice assistant’s operation erratic. Frequently, it will respond to the OK Google and then not do anything thereafter. What is annoying is that I’ve become rather dependent on it and now have to go back to the old fashioned way. BTW, I have a first gen Pixel XL.
This annoying error makes me crazy. I follow the steps above but everything configured differently. I even factory reset my phone. And even that didn’t solve my issue. Now I think I have to go to my carrier provider.
This annoying error makes me crazy. I follow the steps above but everything configured differently. I even factory reset my phone. And even that didn’t solve my issue. Now I think I have to go to my carrier provider.