Database Info

Touchless Control

Is anyone else having a problem with their touch less controls. I can say OK google now and the phone will make a noise. But when google now opens it says " Sorry can't reach google right now ". Same goes for any other kind of voice driven function , texting by voice in the stock messaging app, search in the maps app. They all hive me the same reply. I've checked all my setting. Im at a complete loss
Rooted & unlocked. Otherwise stock .

Have you updated your google search app?

I used HOM and fxz'd my phone . The google vioce app now works but the Moto touchless controls still don't

Google Now needs an active internet connection.

I have tried everything. I've spoken to Verizon who then refered me to Moto. Who had clear partition caches to no avail. Any and all voice recognition on my phone has ceased to work. Sometimes Google will open up to say " Can't reach google at the moment ". However if I manually open the search box Google now and all my cards are there. If I then hit the microphone icon It will again say "Can't reach google at the moment ". I'm at my wits end here. This will happen weather Im using my wifi or 4G signal.
I've fxz'd and that didn't work. I will entertain any and all ideas.

Any resolution with the voice control problem? I am having the same problem with my Droid Maxx running 4.4.4. It just started this week and I have reset it, but that didn't solve the problem. I figured the old apps wouldn't have the same problem as the newer versions. Guess I was wrong. I am trying Verizon Repair assistant to see what it can do for me. We will see.

tombaldwin6 said:
I have tried everything. I've spoken to Verizon who then refered me to Moto. Who had clear partition caches to no avail. Any and all voice recognition on my phone has ceased to work. Sometimes Google will open up to say " Can't reach google at the moment ". However if I manually open the search box Google now and all my cards are there. If I then hit the microphone icon It will again say "Can't reach google at the moment ". I'm at my wits end here. This will happen weather Im using my wifi or 4G signal.
I've fxz'd and that didn't work. I will entertain any and all ideas.
Click to expand...
Click to collapse
Post your touchless/moto voice version from settings/app. They are interchangeable in name now. If you have the newest you must uninstall updates & retrain touchless voice.

I ended up FDRing the phone twice. The first time I let my apps reload automatically and my touchless control still didn't work. So I did it again, but the time I reloaded each app individually. Testing the touchless controls between each install. I ended up reinstalling every app but the one I thought was the culprit. This is no knock on the app I used it and I wish I could put it back in. Elixor2 has a setting where you can control and or turn on/off each of the sensors including the microphone. When I was having the problem I would go into elixir and see that my microphone was off and inaccessible. With out elixor2 on my phone I've had no more problems.

I have done the same type thing as Tom Baldwin6. I "redid" my phone using the Verizon software installation assistant and did a "repair". I then rooted it using TWRP, and started adding stuff. I have not had the problem again as of now.
I was thinking it was the experimental app that was allowing me to mirror my phone using Chromecast, but I am using version 4 of that app and it is still working. I used version 5 before.
My phone hasn't had a problem again after 24 hours, but as I continue to add apps and check, eventually I may find another culprit. I will post here if I get it tracked down.

jmaclean62 said:
I have done the same type thing as Tom Baldwin6. I "redid" my phone using the Verizon software installation assistant and did a "repair". I then rooted it using TWRP, and started adding stuff. I have not had the problem again as of now.
I was thinking it was the experimental app that was allowing me to mirror my phone using Chromecast, but I am using version 4 of that app and it is still working. I used version 5 before.
My phone hasn't had a problem again after 24 hours, but as I continue to add apps and check, eventually I may find another culprit. I will post here if I get it tracked down.
Click to expand...
Click to collapse
I suspected the the chromecast mirror as well It was one of the 1st apps I reloaded. But it wasn't it. I'm certain it has something to do with the microphone

Same issue here. Been a week since I FDR'd (NOT rooted or unlocked). The apps restored, touchless control no longer allows to register voice (does not recognize sound ONLY for Touchless Control).
Saw that Touchless Control has been updated to "Moto Voice",
Uninstalled Moto Voice to return to previous version. No luck. Again updated to Moto Voice.
Wipe Cache Partition, no luck.
I've installed Open Mic+, which works for the most part (never got it to work from lock screen)
Stopped Open Mic+.
I then went in Language & input ---> Google voice typing settings (or Voice Search), disabled/re-enabled Speech Output. Clicked on "Ok Google Detection" and did the standard Google Now/OK Google setup again.
Went back to Touchless Control and this time it recognized my voice and allowed me to setup Touchless Control and all is working again.
Although the new "Moto Voice" on the "1st Gen [2013] Ultra/Maxx etc.., you cannot customize the "OK Google Now" at this time (coming feature for Gen 1's).
Rebooting now to ensure operation. Will updated/verify 'fix' in a moment.
Upon restart, my Open Mic+ restarted, and the "OK Google Now" was not working. Stopped the Open Mic+ and touchless control working again. Went in and re-trained to verify. Unintalling Open Mic+ and rebooting now.
Now again working 100%, now just awaiting Moto Voice update to allow additional features for 1st gen's.

i have got mine working gain too. I still haven't reinstalled everything though. I will reinstall x tether this weekend. I am hoping that it isn't cuseing any problems. Can't imagine why it would, but we will see. Do you guys have it installed?

Did you happen to open the Google app, scroll to the bottom, tap the three dot menu control on the bottom right, tap settings, voice, OK Google detection, and turn off the setting "On any screen"?
If that is on, I think it block touchless controls, maddeningly. I know it stops the Assist driving feature from being able to capture voice when it prompts you.

doogald said:
Did you happen to open the Google app, scroll to the bottom, tap the three dot menu control on the bottom right, tap settings, voice, OK Google detection, and turn off the setting "On any screen"?
If that is on, I think it block touchless controls, maddeningly. I know it stops the Assist driving feature from being able to capture voice when it prompts you.
Click to expand...
Click to collapse
I set "on any screen" option and touchless controls does work from any screen, needing only "OK Google".
I am not driving now but will check Assist in about 2 hours.

iamtek7 said:
I set "on any screen" option and touchless controls does work from any screen, needing only "OK Google".
I am not driving now but will check Assist in about 2 hours.
Click to expand...
Click to collapse
I don't think that's touchless controls - I think that's the Google search app listening and responding to ok Google , and, with that setting on, that's probably why you couldn't train in the Touchless controls settings (though I haven't tested that myself, since my phone is already trained.)
I know it's a subtle difference, but Touchless controls is a front end to google search most of the time, though sometimes it does its own thing (ok Google now, what's up?)
I do know that the any screen setting screws up some other things, like preventing the camera app from capturing video (because the microphone is in use).

I'm all set now. If this is still an issue for anyone, let me know.
Sent from my XT1080 Developer Edition using Tapatalk

"OK Google" command not always waking the phone up

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

Giant security issue

ok so... with the phone on the table and the screen is off (standby). if i say "ok google" and do a search for anything. once im done i can hit the home button and it takes me right into home screen without inputting my finger print or password. So that means anyone can now say "ok google" and bypass any of the securities. come you guys confirm this as this is a major problem for me. I have the verizon edition pixel.

Audigy187 said:
ok so... with the phone on the table and the screen is off (standby). if i say "ok google" and do a search for anything. once im done i can hit the home button and it takes me right into home screen without inputting my finger print or password. So that means anyone can now say "ok google" and bypass any of the securities. come you guys confirm this as this is a major problem for me. I have the verizon edition pixel.
Click to expand...
Click to collapse
Settings>>Google>>Search & Now>>Voice>>OK Google Detection - In here you can set options to secure this feature to your liking. Notice the 'Trusted Voice' Option which detects its YOU before unlocking. There of course is room for error where someone sounding similar to you in might be able to get it. That's why these features are there to disable if it matters to you.
I personally don't care much..
Cheers!
(There might be a faster way to get to those settings. That's just how I always remember to do it)

And it also makes you acknowledge everything you just said before enabling trusted voice.... you must've missed that part.

i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.

Audigy187 said:
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Click to expand...
Click to collapse
How long has your friend been using their V20? I know they become much more accurate the longer you use it, similar to the fingerprint scanner. Google has you train it to understand you with 3 sets of 'ok google' but that doesn't mean it's done learning. Give it some more time maybe? Just thinking...

hes been using it for 4 about a week now. the v20 is a nice. i feel it is noticeably faster than the note 7 i had. only issues are the screen it average. Its sharp but color is average. the hole phone vibrates from the speakers which is a downside for me.
Ill give the pixel some time to learn my voice and report back. hopefully i cant fool it lol

Try this
Audigy187 said:
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Click to expand...
Click to collapse
Press power button while Pixel is in sleep mode. That will bring up the lock screen. At the bottom of the screen you will notice a fingerprint icon. Tap that and you will get the message "Device will remain locked until you manually unlock."
No amount of saying "OK, Google" will allow access now until you either use the fingerprint scanner or enter your pass code.

Yea I pointed this out here: http://forum.xda-developers.com/showpost.php?p=69303648&postcount=12
It is a big issue. It should allow limited assistant functionality, but not entire phone.

as always, if you are so concerned about security on your phone, dont keep anything on it that you are afraid of someone else accessing..
very simple solution

wase4711 said:
as always, if you are so concerned about security on your phone, dont keep anything on it that you are afraid of someone else accessing..
very simple solution
Click to expand...
Click to collapse
Thats horrible.

Audigy187 said:
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Click to expand...
Click to collapse
km8j said:
Yea I pointed this out here: http://forum.xda-developers.com/showpost.php?p=69303648&postcount=12
It is a big issue. It should allow limited assistant functionality, but not entire phone.
Click to expand...
Click to collapse
Both of you! Turn "trusted voice" off
It is a setting in Google -> Search and Now -> voice -> and OK Google detection.
Turn off "trusted voice"
No more "GLARING SECURITY HOLES" in... Your knowledge of your phone.
Because, asking for limited functionality of Assistant when trusted voice is off doesn't sound right to me.... Like asking for AI to know which questions are answerable while screen is locked seems too tricky at this time.
The design is to use a lock or leave it off, currently.
Sent from my sailfish using XDA Labs

nednednerb said:
Both of you! Turn "trusted voice" off
It is a setting in Google -> Search and Now -> voice -> and OK Google detection.
Turn off "trusted voice"
No more "GLARING SECURITY HOLES" in... Your knowledge of your phone.
Because, asking for limited functionality of Assistant when trusted voice is off doesn't sound right to me.... Like asking for AI to know which questions are answerable while screen is locked seems too tricky at this time.
The design is to use a lock or leave it off, currently.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Well 1) the voice recognition isn't good 2) we want the functionality 3) the assistant could act on limited functionality: weather, reminders, send texts, make a phone call. If someone gets my phone and wants to manipulate a voice to send texts, whatever. This is how moto handled their voice assistant and it was perfect.

Oh this thread is now a feature request? It was about a security issue. Things can change.
Give Google feedback through "about phone" in settings! Maybe they will add the feature.
Sent from my sailfish using XDA Labs

Turn off trusted voice in Smart Unlock.

HeCareth said:
Turn off trusted voice in Smart Unlock.
Click to expand...
Click to collapse
Finally somebody with a smart answer...this controversy could all be avoided by a simple google search telling you how to disable the the trusted voice in smart lock, as the person states above. Im all about helping newbs out but research before you post...especially security stuff...... the title of you post makes it sounds as if there has been a security breach or major security flaw in the firmware.

Sounds about like the guy I sold a Gear 2 Neo too. I was showing him how to use some things and he freaked out when the Trusted Device feature left his phone without a passcode. So we disabled it, then he wanted to add a passcode to the watch to get get into it which really only works if it's disconnected from the phone. He was pretty honest about his reason. He's cheating on his wife and didn't want her to find out.
Sent from my Pixel using Tapatalk

Janker5050 said:
Finally somebody with a smart answer...this controversy could all be avoided by a simple google search telling you how to disable the the trusted voice in smart lock, as the person states above. Im all about helping newbs out but research before you post...especially security stuff...... the title of you post makes it sounds as if there has been a security breach or major security flaw in the firmware.
Click to expand...
Click to collapse
It is a security flaw if you can get through it with someone else's voice easily.

km8j said:
It is a security flaw if you can get through it with someone else's voice easily.
Click to expand...
Click to collapse
When I click on it in settings it tells me directly that it can be "less secure."
Yep. So it is not a flaw. It is a feature.
You should feel informed by the warning in settings, not like "it doesn't work.."
It is a fact more voices are similar and voices are easier to mimic than... Fingerprints. Rhythm and pitch are easy to steal. Ever hear of a cover band? Or confuse yourself which band you're listening to because of singer? If never... Wow dude.
Sent from my sailfish using XDA Labs

Ok Google detection?

Maybe I am missing a setting somewhere or something, but the Google Assistant on my XZP only responds when the screen is on. I have it set to "any time" in the Assistant settings. Is this normal? I'm pretty sure it worked whenever (screen off/locked/charging/etc.) on my last couple of phones. I'd like it to at least work while the phone is charging.
Any ideas?

well yeah I had the same problem, apparently, Google changed the settings of the program, and it was only working while the phone is charging, so whenever u upgrade the application to its latest version you will lose this privilege. my advice and that's what I'm doing is to uninstall the updates from the google app and then give it all the permissions it needs and you will have it to work anytime the phone is charging no matter if the screen is on or off !!
btw my Google app version is 7.2.26.21.arm64

This is something that I absolutely hate about the Google assistant. Google should allow the assistant to be used regardless of the device being locked or charging like you can with Siri and Cortana (on WM). It's so irritating to have to actually turn my screen on to use the Google assistant.
Sent from my SGP511 using Tapatalk

Jake_09 said:
This is something that I absolutely hate about the Google assistant. Google should allow the assistant to be used regardless of the device being locked or charging like you can with Siri and Cortana (on WM). It's so irritating to have to actually turn my screen on to use the Google assistant.
Sent from my SGP511 using Tapatalk
Click to expand...
Click to collapse
Yeah, once the phone is in my hand I don't really need the assistant. I can do it myself...

Heinous said:
Yeah, once the phone is in my hand I don't really need the assistant. I can do it myself...
Click to expand...
Click to collapse
Exactly. It's really pointless to have an assistant that requires me to interact with the phone. It's like Google doesn't understand what an assistant is for. I really wish they would also implement what Cortana does in terms of how she handles text messages when connected to Bluetooth devices. I love that she would ask if I want her to read it to me and then after reading it will ask me if I want to dictate a reply and send it.
Honestly, for some of the flak that I've seen Cortana getting lately, she's a much better and much more useful assistant than Google or Sri and she's probably the thing I miss the most from WM10.
Sent from my G8141 using Tapatalk

Jake_09 said:
Exactly. It's really pointless to have an assistant that requires me to interact with the phone. It's like Google doesn't understand what an assistant is for.
Click to expand...
Click to collapse
It's not sure it's entirely Google's fault. It worked properly on previous android phones that I've owned.

I just noticed that it seems to work now with the Oreo update. My phone now wakes up and responds to "ok, Google" while the screen is off/locked. ?

This is by far the best part of the Oreo update. Google Assistant is at least 800x more useful now that it is actually hands-free.

Doesn't work wih mine. It blinks like I could say somehing, but stays closed. When I unlock it, nothing happens. My old phone then went into the assistant mode.
Which options do i have to set?

Google Assistant / "OK Google" Wake-Up and Unlock

@Puksom had said in another thread that he had OK Google working to wake up the phone, but I've heard from many others that it doesn't.
Hoping anyone running various versions of MIUI Global and/or Chinese can chime in if they have this feature working.
If it works for you, please let me know your build number. I can confirm it doesn't work on the latest Chinese stable, but, since I still have another couple days for bootloader unlock, I can't confirm much else.
Note that by OK Google wake-up, I mean with the screen off, and the phone unplugged.
By unlock, I mean that you set a PIN/Password, and that saying OK Google can bypass this lock screen if your voice matches.
(By the way, a somewhat difficult work-around for people who need this feature but can't get it working...)
You can set up, on the Chinese builds, a voice wake-up for the Chinese assistant.
Although you'll need to pronounce it well, you need to program the wake-up word, Xiao ai, by saying Xiao ai tong xue
Then saying "Xiao ai" can make the phone wake up... from there, you can say "OK google" and access assistant. But of course we all want to access assistant directly.

I have that working I'm on official Chinese rom with Google apps and services installed it works ok

I'm running Global Version (9.5.4), and it doesn't work.
When the screen is off, it's not listening. When the screen is on, on the lock screen, it activates, but it doesn't unlock the phone (there's no Trusted Voice), so you need to enter your PIN/pattern.
Trusted Places is not available either, so there is no way to have the phone unlock automatically except using a Mi Band or some other bluetooth device.
@funziebear What is working for you exactly? OK Google with screen off? Does it also unlock your phone automatically or do you have to enter your pattern/pin as well? I though no version of MIUI supported any of those features, based on what I have been able to dug up.

I'm also on the Global Rom and it does NOT work. As well as not having any face unlock options.
Very disappointing.

I'm on official chinese stable. Installed all Google Apps and gave full permissions and autostart permissions to all Google Apps. Installed Assistant and was even able to activate it properly with wake-up and trusted voice. But it's still not working. There was once a message from within the assistant, that said Xiao Ai is still the default assistant and Google Assistant is not set as default.
It's working with screen on, but not unlocking
It's not working with screen off

funziebear said:
I have that working I'm on official Chinese rom with Google apps and services installed it works ok
Click to expand...
Click to collapse
Are you sure? Can you say OK Google with the screen off, and it wakes up?

can you guys please figure this out definitively ? Cuz I'm willing to buy the phone, but i will not buy it if google's assistant isn't able to wake-up the phone. pretty please figure it out.

It currently does not work with the screen off.

SolarisSixth said:
It currently does not work with the screen off.
Click to expand...
Click to collapse
within your helm of knowledge do you believe it's going to receive this feature in a near-future update?
Cuz I ran into this EXACT same issue with my Galaxy S7 and saw people with Galaxy S6 and S8 facing the same issue, all of them can wake-up the screen, even the word can be configured to whatever word the user wants as long as it is phonetically pronounceable in the 5 most common languages, but the catch is that it only works with Samsung Voice later renamed to Bixby. And I even tried running both Samsung and Google's assistants simultaneously, it doesn't work, they both compete for the exclusive use of the microphone so the idea of using one to wake-up the screen and the other to execute the command is not practical or viable since the second one will only have access to the microphone-audio-stream after the first one released it. So in the end I deactivated the ****ty Samsung Voice crap and decided to stay with Google's Assistant even though it does not wake-up the phone.
what a barbaric decision this is specially coming from Xiaomi. truly ****ed up

Any updates on this? I haven't tried newer MIUI 10 versions, wondering if they added support.

Google Assistant works
Unlock by face works
MIUI 10 8.8.3 xiaomi.eu

k-vadim7 said:
Google Assistant works
Unlock by face works
MIUI 10 8.8.3 xiaomi.eu
Click to expand...
Click to collapse
+1

k-vadim7 said:
Google Assistant works
Unlock by face works
MIUI 10 8.8.3 xiaomi.eu
Click to expand...
Click to collapse
Adriano-A3 said:
+1
Click to expand...
Click to collapse
But unlocking by Google assistant doesn't work

Flatric said:
But unlocking by Google assistant doesn't work
Click to expand...
Click to collapse
+1

I take it nothing's changed with the more recent releases?
I tried the MIUI 10 Global Stable, and still no wake-up by voice.