I switched from the Moto Voice app to the OK Google because the Moto X voice app is terrible. Everything was working great until a few days ago. OK Google only works from the home screen now. Does anyone else have this issue? Is there a work-around to fix it? Thanks!
I'm assuming that the "From any screen" option is checked in the Google app?
imaginaryenemy said:
I'm assuming that the "From any screen" option is checked in the Google app?
Click to expand...
Click to collapse
Correct, and I did the training. It works perfectly on my Moto G. My Moto X has been acting quirky so I am getting an advanced replacement from Motorola. They are now charging a $25 "Premium Fee" for advance replacement. I hate this company ever since Lenovo took over and this will be my last Motorola phone.
Having the same issue.
Starting to regret this phone deeply.
I just realized that I hadn't checked it since my update to 5.1, and it no longer works for me either. It is not a feature I use, but it is a shame that it is broken.
Me neither, which makes me think it's a server side error.
Broken on my Moto X running 5.1 stock or CM 12.1 and my Nexus 5 in the same scenarios, so I think it's a bug in the app not with our phone.
chrisrozon said:
Me neither, which makes me think it's a server side error.
Click to expand...
Click to collapse
raptir said:
Broken on my Moto X running 5.1 stock or CM 12.1 and my Nexus 5 in the same scenarios, so I think it's a bug in the app not with our phone.
Click to expand...
Click to collapse
These certainly sound like the most likely causes, however, is it strange that we are the only people talking about this? If it were a global problem, I would think more people would be complaining.
I had this exact issue and figured out quite a simple fix.
All you need to do is going to the "Moto" app and disable the "Moto Voice" function. The moto voice function apparently takes control of the mic at all times, stopping google now from doing so. Once I disabled the Moto Voice, I could enable Google Now / Ok Google from all screens and didn't get the "microphone is in use, please restart device" error message anymore.
Hope this helps
Yugnoswam said:
I had this exact issue and figured out quite a simple fix.
Click to expand...
Click to collapse
This is not the problem being discussed here. The problem is, after being setup properly, the "OK Google" command only works on the homescreens. Not on the lock screen, not when an app in is the foreground. Are you able to use "OK Google" in these instances?
imaginaryenemy said:
This is not the problem being discussed here. The problem is, after being setup properly, the "OK Google" command only works on the homescreens. Not on the lock screen, not when an app in is the foreground. Are you able to use "OK Google" in these instances?
Click to expand...
Click to collapse
It seems intermittent ever since the last Motorola OTA I received. I can't seem to do OK google from my homescreen anymore although it will occasionally wake from lock screens and in an app if I use it, it will pull me out of the app to the Google Now search screen. I think the whole thing is pretty much bugged to be honest :/
I've found just going into the google search and hitting the mic button much more reliable and thus faster.
Running stock fresh flashed factory image of Android 6. It appears that "OK Google" no longer works from any screen. I've gone in to Google>Settings>Voice>"OK Google" detection and confirmed "from any screen" is turned on. I've tried clearing cache in apps of the Google App, retraining the voice model, but still no luck. "OK Google does work from the home screen but nowhere else. It worked fine in the 3rd Developer Preview so I'm kind of aggravated at this issue..
For me it works from any screen. Running Android 6 stock rooted. But I was a little bit surprised because I haven't set up it and haven't trained the voice model.
Sent from my Nexus 5 using Tapatalk
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?
Hello,
My new pixel 4xl is working great except for 2 reasons. The main one being I don't get turn by turn voice navigation. I get no voice at all when navigating. COnsidering I drive for Uber on the side this is very bad.
I checked all settings and they are all correct as far as I can tell - play over bluetooth and everything is on. Doesn't matter if I am on BT or not, nothing. I've tried rebooting of course.
Help?
pixelsquish said:
Hello,
My new pixel 4xl is working great except for 2 reasons. The main one being I don't get turn by turn voice navigation. I get no voice at all when navigating. COnsidering I drive for Uber on the side this is very bad.
I checked all settings and they are all correct as far as I can tell - play over bluetooth and everything is on. Doesn't matter if I am on BT or not, nothing. I've tried rebooting of course.
Help?
Click to expand...
Click to collapse
Did you by chance hit the mute button while navigating? I normally turn mine off and it stays off
RoccoN4 said:
Did you by chance hit the mute button while navigating? I normally turn mine off and it stays off
Click to expand...
Click to collapse
Here's a screenshot
Yeah it wasn't that. Thanks though
Sent from my Pixel 4 XL using Tapatalk
RoccoN4 said:
Here's a screenshot
Click to expand...
Click to collapse
hey that's Mississauga!
That's really strange. And you said even not on Bluetooth, so the phone's speakers, you're not getting navigation sounds?
Sent from my Pixel 2 XL using Tapatalk
I uninstalled the beta google maps and now they work. I re-upgraded to the beta and they still work.
pixelsquish said:
I uninstalled the beta google maps and now they work. I re-upgraded to the beta and they still work.
Click to expand...
Click to collapse
Nice you got it working. I'm on beta too so must've just been a random issue.
Sent from my Pixel 4 XL using Tapatalk
Anyone else? P4xl
Only works after I've opened the app
Occasionally when I unlock my phone after being asleep it won't respond to ok Google...
Battery opt is off
Cleared cache with no luck
virtyx said:
Anyone else? P4xl
Only works after I've opened the app
Occasionally when I unlock my phone after being asleep it won't respond to ok Google...
Battery opt is off
Cleared cache with no luck
Click to expand...
Click to collapse
A few reports of the same on Aussie Whirlpool. I wonder if it's language setting bug.
Mine is fine so far, but I'm still stuck on the old Assistant due to having a GSuite account on the P4XL.
xdatastic said:
A few reports of the same on Aussie Whirlpool. I wonder if it's language setting bug.
Mine is fine so far, but I'm still stuck on the old Assistant due to having a GSuite account on the P4XL.
Click to expand...
Click to collapse
Noticed it since moving onto the new assistant
I have the same issue. need to open open first before it works. i think it started to happen on dec build for me
Same here since running custom roms...
Any known fix? Pretty annoying not being able to use a feature properly
Weird, I have the opposite problem. It's overly sensitive for me, it'll just randomly go off in my pocket when I'm having a conversation
Sent from my Pixel 4 XL using Tapatalk