Since global and lock screen enabled hotword detection of "OK GOOGLE" was released on my phone officially(~8 months), I've used it daily. About two weeks ago, it stopped working.
I have taken quite a few steps to diagnose the issue, including everything in this thread, however, it still doesn't work.
Right now, I can't retrain the voicemodel and that's where its been stuck since just after it stopped working.When I attempt to toggle the checkbox to enable hotword detection "From Any Screen", it takes me to the "OK GOOGLE" voice training screen.from here it simply does not recognize ok google.
I had push bullet and microsoft remote control which were both mentioned as possible causes, I uninstalled them both, rebooted and still no luck. in addition, I've tried everything mentioned in this thread, as well as the HTC Microphone diagnostic, both mic tests passed
Can Anyone Help please,
Completely stock AT&T HTC ONE M7
Please, Anyone?
BUMP DITTY BUMP, Please help!!!!!!
Once every few days I get this notification from Google asking me to say "OK Google" three times to train the device. I always say it, although the recognition of me saying "OK Google" has actually gotten worse and worse. Before Google started asking me this it nearly always worked. Now it works only about 10% of the time I say "OK Google". Now having to say "OK Google" into my phone over and over again in front of others is embarassing. What is going on?
I have the same issue. The only way I was able to fix it was by reverting to the stock Google App (uninstall updates for this app through App Manager) and retraining my voice. Now it's back to normal. To note, the current Google App beta also didn't help things. Same problem.
KruseLudsMobile said:
Once every few days I get this notification from Google asking me to say "OK Google" three times to train the device. I always say it, although the recognition of me saying "OK Google" has actually gotten worse and worse. Before Google started asking me this it nearly always worked. Now it works only about 10% of the time I say "OK Google". Now having to say "OK Google" into my phone over and over again in front of others is embarassing. What is going on?
Click to expand...
Click to collapse
Can you post a screenshot? I am curious what is this
No because it only appears when it wants to. Also, I resolved the issue. I went into Google settings and deleted all the voice data they had about me. Then I noticed the voice recognition of "OK Google" works much better once again.
I'm not sure when this changed. I used to be able to say "OK Google" and the assistant would interact with certain apps, like texting or calendar, when the phone was still locked. Now, as soon as I say the hot-phrase it goes straight to the pattern lock screen and won't go further until I unlock. Is this a function lost on devices without "Trusted Voice"?
I'm running the latest PN with the stock PN kernel. I'm not in beta for the Google app either.
I've tried retraining voice recognition, turning always listening off/on, updated Google app a couple times, tried different launchers (Action and Pixel)...
Any thoughts or recommendations on this?
The way I handle this is using tasker to set the screen lock delay to some thing silly like 10 days when the phone is in a "safe" location. Then the ok google works as expected with the screen off. The rest of the time I live with the fact that I have to unlock the phone to use ok google.
On reflection, smart lock should give the same effect of there is a trusted device connected.
I've considered something like what you've said. I do want the security to work though. I used to be able to do very basic things by voice without unlocking. I don't want to effectively turn off security.
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
fredphoesh said:
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
Click to expand...
Click to collapse
they broke ok google about a year ago, very sad.
SOLUTION!
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
fredphoesh said:
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
Click to expand...
Click to collapse
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
I had this problem, disabled Bixby, works properly now.
Sent from my SM-N950U using Tapatalk
Liface said:
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
Click to expand...
Click to collapse
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Mine get borked every time I toggle between power saving modes. I like to use Extreme power saver for overnight and Medium mode at work.
Medium mode straight up breaks OK Google. Not sure if this is by design or a bug, but it just will not hear me.
Coming out of either mode (and extreme is the worst) and neither "Hi Bixby" or "OK Google" work until I do another full reboot. Sometimes I have to reboot then go back into Google voice setting to switch the option back on manually. If I try to do this before the reboot the option is greyed out and I can't move it. Sometimes just the reboot is enough.
It's random as hell and extremely annoying. I have submitted the bug to Samsung via the feature in the Samsung Members app, but that was over two weeks ago and has seen no response.
Interesting post. My wife's OK Google voice doesn't work but mine does. Both USA T MO version. With works I'm referring to having the Google widget on home screen and saying the sentence OK Google. Mine responds and hers doesn't. With screen ON.
Sent from my SM-N950U using Tapatalk
fredphoesh said:
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Click to expand...
Click to collapse
That's not it, I rarely use battery saving mode and this happens 100% of the time.
Ok google for me just does not work.
Anyone get a fix for this?
"Ok Google" works when screen is on, but if I say it while the screen is off, it makes the noise and I get edge lighting indicating it's listening, however it doesn't respond and when I manually turn on the screen assistant is open saying "can't reach Google at the moment."
Power saving mode is off, tried disabling Bixby, clearing cache, nothing.
Hellothere37 said:
clearing cache, nothing.
Click to expand...
Click to collapse
so clearing cache of Google app and rebooting did not help at all?
bizarre, that fixed it for me...
I have a UK version.
I'd phone Samsung!
I'm frustrated too because I can't figure out how to use it while in power saving mode. I thought I added it correctly in the optimized battery usage apps (disabled google, ok google enrollment and voice assitant there). I can't see it as an option to select under unmonitored apps. Any idea what I'm missing?
Thanks for any help
This is strange to hear. Mine has worked flawlessly, as good as my pixel XL. Screen off and locked or not. I say ok Google, phone unlocks, and then I ask it whatever. Only thing ive done is disabled bixby by way of BK disabler.
Sent from my SM-N950U using Tapatalk
May be coincidental but I have not the slightest problem, and yeah, I uninstalled the Bixter. One thing I have read somewhere or other is that the OK Goog command is also subject to the level you set for Bix. In other words with sensitivity turned down for Bix it's also turned down for Goog. I never tested that one but might be worth looking at...
gingi999 said:
they broke ok google about a year ago, very sad.
Click to expand...
Click to collapse
So two things I wanted to mention the first one was my old phone case actually covered one of the microphone holes. Meaning the cut-out wasn't there so I used a drill and made a hole and it fixed part of the problem.
I have to be honest with you the Note 8 solved all the OK Google problems that I was having the past. For example the lockscreen didn't used to work and it works now I mean it was really a piece of trash with my Galaxy S7 Edge and now I can't imagine living without it.
Having problems like the first post where google assistant/ok google is non responsive all around. I've noticed that if I clear cache and data it falls back to just "ok google" and it work all the time. If I activate the google assitant with ok google it fails immediately. Who can fix this?
Ever since upgrade to AW 2.0, "OK Google" doesn't work 90% of the time. Today, I figured out why. Here's the experiment:
1) Make sure the watch and the phone are connected.
2) Toggle "Personalization -> OK Google detection" off and back on ... "OK Google" now works
3) Toggle phone's Bluetooth off
4) Try "OK Google" on the watch now. It still works, but tells us it can't connect to the phone -- as expected.
5) Toggle Bluetooth on the phone back on. Make sure watch and the phone are now connected again.
6) "OK Google" now never works
I've tried and re-created this scenario multiple times. Does it match everyone else's experience?
Which brings me to the following question -- is there a way to flash the watch with AW 1.5? The watch was infinitely more useful with a reliable voice input; now it's just a notification device.
Just hold down the crown button for a few seconds and Google Assistant will start listening. I think it's more convenient than saying "OK Google" anyway
jbmatson said:
Just hold down the crown button for a few seconds and Google Assistant will start listening. I think it's more convenient than saying "OK Google" anyway
Click to expand...
Click to collapse
That doesn't work all that great when, say, driving or cooking. Having hands free voice commands work close to flawlessly is what made me return Apple Watch and switch to Android; Wear 2.0 was as much of a CF for that functionality as a major upgrade could be, and Google doesn't seem to be in a hurry to fix that.