Related
I thought the OnePlus was going to have touchless voice commands. I cant find it anywhere.
I saw in a video "hi snapdragon" but doesn't seem to work
it was removed in the last update.
The Jack of Clubs said:
it was removed in the last update.
Click to expand...
Click to collapse
Why was it removed? Is the feature coming back?
I know you can use 'OK Google' but there are problems with the mic volume, which can be fixed by editing a file, but it isn't a perfect fix. This has been patched in the latest update though, which should be pushed out shortly.
Also, OK Google doesn't seem to be listening everywhere even if it has been set to. I'm hoping they fix this as well.
it didnt work well and they are working on replacing the "hey snapdragon" with "ok oneplus".
Qualcomm was not satisfied with the quality of the pre-recordings that oneplus sent to them.
7ewis said:
Why was it removed? Is the feature coming back?
I know you can use 'OK Google' but there are problems with the mic volume, which can be fixed by editing a file, but it isn't a perfect fix. This has been patched in the latest update though, which should be pushed out shortly.
Also, OK Google doesn't seem to be listening everywhere even if it has been set to. I'm hoping they fix this as well.
Click to expand...
Click to collapse
If you go in to the Google now settings and change the default languae to US you should then be able to activate 'Ok Google' from any screen includong the lock screen and while the device is in standby
I tried to activate this but does not seem to work from the lock screen for the oneplus one. I have 44S update I think but would really love to see this functionality coming back. I was quite impressed with my moto x primarily from this perspective and am looking forward to having this on my oneplusone device.
Any idea when it might come back?
TIA
Anyone else having inconsistent results with saying "OK Google" while the screen is off?
It seems to work fine when actively using the phone, but if I hit the power button to turn off the screen then it may (or may not) turn the screen on with the Assistant after saying "OK Google" (nothing happens).
I tried turning on fingerprint/pin security, but this will still sometimes not respond to the command. Additionally, it will also still sometimes ask me for a pin even though I have "Trusted Voice" enabled.
Not sure if it's a hardware issue or software related (again, everything works perfectly if the phone screen is already on and in use).
Always works for me. Maybe you can try to redo the voice recognition step that was done when the phone was set up.
Yea, I've tried retraining my voice but still with the same results. It will at times always work perfectly and other times will be as if it doesn't hear my voice at all. I don't have any new apps installed and I even did a factory reset. Leaning towards getting an exchange but part of me thinks it's software related.
I think I've run into this issue a few times, but may need to see if it keeps happening.
I think most of the time that it has happened to me is when signal is low. I think signal definitely plays a role since the server has to translate your voice (maybe). At least that's how I think software listens to your voice and recognizes it was you and what you were saying.
Were you in an area with weaker signal when trying to say ok google?
kinetic758 said:
Yea, I've tried retraining my voice but still with the same results. It will at times always work perfectly and other times will be as if it doesn't hear my voice at all. I don't have any new apps installed and I even did a factory reset. Leaning towards getting an exchange but part of me thinks it's software related.
Click to expand...
Click to collapse
I had the issue a couple times when I was experimenting with the feature. I think it is software related.
I think it is quite sensitive because as the warning goes "it can be a less secure method"
If I spam the fingerprint scanner it will say "too fast" and then require pin.
Sent from my sailfish using XDA Labs
ryken229 said:
Always works for me. Maybe you can try to redo the voice recognition step that was done when the phone was set up.
Click to expand...
Click to collapse
xShadoWxDrifTx said:
I think I've run into this issue a few times, but may need to see if it keeps happening.
I think most of the time that it has happened to me is when signal is low. I think signal definitely plays a role since the server has to translate your voice (maybe). At least that's how I think software listens to your voice and recognizes it was you and what you were saying.
Were you in an area with weaker signal when trying to say ok google?
Click to expand...
Click to collapse
I was not connected to wifi but the signal seemed fine. I'll keep an eye on it next time.
nednednerb said:
I had the issue a couple times when I was experimenting with the feature. I think it is software related.
I think it is quite sensitive because as the warning goes "it can be a less secure method"
If I spam the fingerprint scanner it will say "too fast" and then require pin.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
The interesting thing is that it would also not work when I had no lock screen security on at all. In this case it just failed to turn on the screen and initiate the Assistant.
kinetic758 said:
The interesting thing is that it would also not work when I had no lock screen security on at all. In this case it just failed to turn on the screen and initiate the Assistant.
Click to expand...
Click to collapse
Hmm looking here
https://www.google.ca/search?q=ok+google+trusted+voice+not+working
It appears it is definitely a software issue that isn't singled out in the Pixel
Sent from my sailfish using XDA Labs
nednednerb said:
Hmm looking here
https://www.google.ca/search?q=ok+google+trusted+voice+not+working
It appears it is definitely a software issue that isn't singled out in the Pixel
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Hm. But does "trusted voice" even matter if I've disabled all lock screen options? I thought it was only relevant if you had a pin/fingerprint set up (it was flaky with and without fingerprint for me).
kinetic758 said:
Hm. But does "trusted voice" even matter if I've disabled all lock screen options? I thought it was only relevant if you had a pin/fingerprint set up (it was flaky with and without fingerprint for me).
Click to expand...
Click to collapse
In my settings in appears "Trusted Voice" is about waking the screen when it is off and "unlocking" to home screen and assistant EVEN IF other security features are off.
In OK Google settings is where I see trusted voice and the settings to voice wake device. Security settings are a different section.
What happens when you turn all security off and decrypt your device so there is no pin or password whatsoever?
Sent from my sailfish using XDA Labs
nednednerb said:
In my settings in appears "Trusted Voice" is about waking the screen when it is off and "unlocking" to home screen and assistant EVEN IF other security features are off.
In OK Google settings is where I see trusted voice and the settings to voice wake device. Security settings are a different section.
What happens when you turn all security off and decrypt your device so there is no pin or password whatsoever?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
What is scary for me, is any time there is a Pixel commercial on TV and the guy says "OK Google", my phone wakes up. So quite the opposite from the OP experience. Actually scary from a security standpoint. The old Motos used to allow limited functionality via voice but not full unlock (smart idea). There should be a way to remotely disable voice detection if you lose your phone.
kinetic758 said:
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
Click to expand...
Click to collapse
I did this and am still having sporadic issues with it not waking after "OK Google". It fails probably 1 in 10 times which was the same rate as before it was added as a Trusted Location.
dispatch said:
I did this and am still having sporadic issues with it not waking after "OK Google". It fails probably 1 in 10 times which was the same rate as before it was added as a Trusted Location.
Click to expand...
Click to collapse
I'm sorry to hear that. A little comforting to know I'm not the only one with this issue
A buddy of mine has a Pixel as well, and his responds to "OK Google" from sleep 99% of the time, so not sure if there's a difference in hardware tolerance with the mic (or whatever low power hardware they're using for "always on" listening), software, or if his voice is just easier for the phone to recognize.
Besides this issue, the phone is perfect (no scratches, no dead/stuck pixels etc), so I'm really on the fence about asking for an exchange.
I would consider a non-functioning "Hello Google" to be a benefit. The first thing I do on any Android device is remove as much as possible of Google's nasty Spyware, starting with the Google Now launcher and the "Hello Google" search.
Sent from my LG-D801 using Tapatalk
kinetic758 said:
I'm sorry to hear that. A little comforting to know I'm not the only one with this issue
A buddy of mine has a Pixel as well, and his responds to "OK Google" from sleep 99% of the time, so not sure if there's a difference in hardware tolerance with the mic (or whatever low power hardware they're using for "always on" listening), software, or if his voice is just easier for the phone to recognize.
Besides this issue, the phone is perfect (no scratches, no dead/stuck pixels etc), so I'm really on the fence about asking for an exchange.
Click to expand...
Click to collapse
I really don't think it's the hardware, but you never know. I don't yet have a large enough sample size to say if 1 in 10 is accurate in the long run or if it is truly closer to 1 in 100 that it fails to wake. I always assume we're beta testers for Google anyway so I have come to expect things like this.
aquatarkus said:
I would consider a non-functioning "Hello Google" to be a benefit. The first thing I do on any Android device is remove as much as possible of Google's nasty Spyware, starting with the Google Now launcher and the "Hello Google" search.
Click to expand...
Click to collapse
I waffle back and forth on immersing myself (and my data) with Google to get the benefits of their products. However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do. As always though, to each their own.
dispatch said:
I waffle back and forth on immersing myself (and my data) with Google to get the benefits of their products. However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do. As always though, to each their own.
Click to expand...
Click to collapse
This. I've embraced (at least for now) the fact that Google is collecting information about me. I've bought into it (also purchased a Google Home) with the hope that this will make my life easier (if slightly). A double-edged sword, for sure.
dispatch said:
However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do.
Click to expand...
Click to collapse
I figure I'm smart enough not to need Google to run my life for me. I will first root the Pixel and remove the stuff I don't want. When a suitable version of CyanogenMod becomes available, I'll flash that into it, as it provides additional security/privacy controls.
Anyway, I hadn't meant to highjack this thread....
Sent from my LG-D801 using Tapatalk
kinetic758 said:
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
Click to expand...
Click to collapse
Also try training the voice by saying Ok Google at 3 slightly different volumes and with varied pace. Do say it clearly each time. I found voice recognition doesn't work as well if I train it with a forced or monotone rhythm. Cos real voice is more fluid and not always the same.
Good luck
Sent from my sailfish using XDA Labs
Mine works every time.
This was never the case on the Nexus 6P.
The only time the Pixel DIDN'T wake up is when it was on low battery and save mode got enabled. I believe this disables the always listening feature of this app.
Sent from my Pixel using XDA-Developers mobile app
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I have the same issue, the only solution I have is to disable the ok Google option as you said.
xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I think problem should be addressed to Google first cause of Google now, or Huawei, second, cause the service is continuosly listening for "Ok google" activation, but it should stop or, better, stand-by, so the
microphone can be used by the concurrent app, when finished, service automatically restarted. This behaviour doesn't require any error or warning pop-up when happens.
Even I like to know, if anyone knows how to submit issues directly to Huawei/Honor.
Just started having the same issue with the latest Google app update, but I can't even disable the "Ok Google" detection. It just turns itself back on immediately. Here's a screencap of my dilemma:
https://gfycat.com/FancyTepidHornedviper
@Xichael: Tap on "Delete Voice Model" and you can turn it off permanently. This is, as far as I know, the only way other than deleting / deactivating the Google App or possibly tweaking certain permissions. Once you delete the voice model, the "Ok Google" should still work within the app or when long pressing the home button.
@xghost1 Yes, deactivating "Ok Google" on any screen by deleting the voice model is so far the only solution that works permanently. There is currently no way to have "Ok Google" everywhere while also not getting that error message. We'll just have to wait for a fix. I think this only applies to the current "Google Assistant" though. It might be possible to go back to an older version of "Google Now" where "Ok Google" on any screen still works while not getting that error.
Thanks, that solves it for me. I can live without "Ok Google", but that popup was intolerable.
xichael said:
Just started having the same issue with the latest Google app update, but I can't even disable the "Ok Google" detection. It just turns itself back on immediately. Here's a screencap of my dilemma:
https://gfycat.com/FancyTepidHornedviper
Click to expand...
Click to collapse
Remove your trained voice and then "Ok Google" detection on any screen will then turn off. That is the only way I found to disable it.
Sent from my FRD-L04 using Tapatalk
xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I was having similar problem and it's gone after i denied permission for microphone...before it was turning itself and made me crazy...I hope it will help You with this issue
famanfwppc said:
I think problem should be addressed to Google first cause of Google now, or Huawei, second,
Click to expand...
Click to collapse
Other Nougat phones with OK Google active don't have this issue. So I'd say Huawei would be the first to be addressed.
It's hard to know who to blame on this one. When Googling, it looks like it's only a problem on Huawei devices. That said, when I try to disable all-screen OK Google detection, the setting won't stick and always reverts. That sounds like a Google issue. I had to delete the voice model.
Likely it's some combination of both.
I called the service hotline last week and they said it was the update to Google app that was screwing things up. For me it was creating a toast message in my camera app when I would record video or use voice activated shutter control for still pictures. He told me to revoke permissions in the Google app for the microphone, or revert to an older version of the app. I'm assuming pre Google Assistant. I haven't tried that option yet.
Turning off all-screen 'OK Google' detection is likely the best option, especially because you can map your Smart Key to Voice Search and get nearly the same functionality. The only impaired function is if you hands-free dock in your car, but even then I rarely use Assistant anyway in that setting.
Thank you all for your comments and replies.
For your information I was receiving this error even without Google Assistant, since I was using my phone with Portuguese language. I tried to reset and changed it to English, now I have Google Assistante working but the error still remains. So like it was already mentioned my best gues is to associate the problem with Google App and Huawei Software.
To be sure it would be good if anyone could test the issue on a Custom Rom.
Thanks
Go into Playstore and chose to uninstal Google app. It will roll back to a version before Google Assistant and your phone will act as normal, you just don't have assistant. I even noticed an issue prior to this while using Shazam to identify a song I was listening to.
Background processes
"com.google.android.googlequicksearchbox:interactor" is a common Android process.
Huawei is at fault for this bug.
I can confirm only Huawei handsets are experiencing this annoying bug.
Huawei also has their own voice assisted application/processes I.e. Quick calling. If you disable all Huawei voice assisted features, this most likely will solve the problem as well.
It seems Huawei voice assisted processes and Google voice assisted processes cannot be active at the same time without the user seeing this message. If you prefer "Ok Google" and other Google voice assisted processes then try disabling Huawei voice software first.
Go to settings and search "voice" then select "voice control" turn off all Huawei voice assisted processes.
Hopefully this helps.
I guess if I want to disable OK Google and use Huawei's voice assistant instead, I can be away from the evil Google. But what does Huawei voice assistant do? I only found "find my phone" and very few other functions. While from what I heard, in China where Google services are totally disabled, Huawei's voice assistant can do a lot more things. Where are they?
Turning off the Huiwei voice facilities does not work. Still get same error.
To get rid of the box you have to turn off "ok Google" detection from any screen.
If it it turns itself back on (a Google bug) you have to delete the voice model.
To use the assistant you'll have to hold down the home button.
The interactor box is just another big of many that Huawei hasn't bothered patching. Huawei clearly doesn't care. Last time buying a device from them.
SolarisSixth said:
To get rid of the box you have to turn off "ok Google" detection from any screen.
If it it turns itself back on (a Google bug) you have to delete the voice model.
To use the assistant you'll have to hold down the home button.
The interactor box is just another big of many that Huawei hasn't bothered patching. Huawei clearly doesn't care. Last time buying a device from them.
Click to expand...
Click to collapse
Yes. Get that you have to turn off OK Google.
The trouble is, I don't *want* to turn it off.
Very annoying bug for sure.
Sent from my FRD-L09 using Tapatalk
ckckckckck said:
Yes. Get that you have to turn off OK Google.
The trouble is, I don't *want* to turn it off.
Very annoying bug for sure.
Click to expand...
Click to collapse
I totally agree, but that's what we get for giving Huawei money, clearly they don't care.
Has anybody had success with waking/unlocking your phone with the "Ok Google" voice command? I enjoy using it but I don't want to have to unlock my phone to use the voice assistant every time, particularly when it's for simple questions (I know, first world problems). I enabled Trusted Voice but that doesn't seem to work when my phone screen turns off. Any help would be appreciated.
Same here. I also tried to do that. Ultimately i came up with nothing.
same here man.
I can't recall the source, but I'd read somewhere it only wakes up to the Dear Honor voice command activated in settings. Seemed to work when I tested it. Also found an automate module that senses the honor voice app open, closes it and loads the Google one. It's pretty sluggish but that's the only workaround I was able to find.
The okay Google command only works with screen off on Nexus and Pixel devices. Honor has another command that you must use, but it doesn't tap into Google assistant.
Extinguished said:
I can't recall the source, but I'd read somewhere it only wakes up to the Dear Honor voice command activated in settings. Seemed to work when I tested it. Also found an automate module that senses the honor voice app open, closes it and loads the Google one. It's pretty sluggish but that's the only workaround I was able to find.
Click to expand...
Click to collapse
Care to link to that module please?
pyromayniyak said:
Care to link to that module please?
Click to expand...
Click to collapse
Looks like it's been removed from the list. I went ahead and zipped a copy of the flow so I can upload it here.
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Yes I've had the same issue. Not sure what helped in the end. Maybe a phone restart? or reinstalling the google search app?
PuffDaddy_d said:
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Click to expand...
Click to collapse
georgs_town said:
Yes I've had the same issue. Not sure what helped in the end. Maybe a phone restart? or reinstalling the google search app?
Click to expand...
Click to collapse
Had the same issue 2 days ago on my P2XL. A cache and data wipe of the google app fixed it :good:
Badger50 said:
Had the same issue 2 days ago on my P2XL. A cache and data wipe of the google app fixed it :good:
Click to expand...
Click to collapse
Thanks, that worked for now....
PuffDaddy_d said:
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Click to expand...
Click to collapse
Personnaly I've noticed I have to yell the word in order for the phone to wake up. I first thought it was wrongly configurated and wiped the app data several time, until I figured the pixel was a bit deaf..
Aanze said:
Personnaly I've noticed I have to yell the word in order for the phone to wake up. I first thought it was wrongly configurated and wiped the app data several time, until I figured the pixel was a bit deaf..
Click to expand...
Click to collapse
I have noticed that Google Assistant been buggy during last few days. Clearing storage and cache does help but even when its back working sometimes it has issues making the registered action. For, example, setting alarm/timer gets registered (the text appears in google assistant but google assistant is sometimes slow to read the registered command + even after google assistant repeats the command and says its done the actual action does not following, meaning the alarm/timer is not set and only on second try it gets through. Never had similar issues before. Not sure if its google app or December update, but I did not have any issues before.
No issues with things like Weather reports and reminders though..
PuffDaddy_d said:
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Click to expand...
Click to collapse
This kept happening to me last week. My phone was on battery saver which did not turn off automatically after charging. Had to toggle the battery saver and do a restart to have OK Google work somewhat reliably.
jemeljsh said:
I have noticed that Google Assistant been buggy during last few days. Clearing storage and cache does help but even when its back working sometimes it has issues making the registered action. For, example, setting alarm/timer gets registered (the text appears in google assistant but google assistant is sometimes slow to read the registered command + even after google assistant repeats the command and says its done the actual action does not following, meaning the alarm/timer is not set and only on second try it gets through. Never had similar issues before. Not sure if its google app or December update, but I did not have any issues before.
No issues with things like Weather reports and reminders though..
Click to expand...
Click to collapse
I thought this was just a glitch, but my wife's old phone did this right before we upgraded to the Pixel 3. She burned the food in the oven because the timer didn't get set even though the assistant confirmed the command.
Maybe we should start saying please and thank you before the machines rise against us.