Database Users

Problem with Ok Google on Nexus 6p

My previous phone was a galaxy s6 (which I'm selling, hit me up if interested) and before that I had a nexus 5 and nexus 4. All of them allowed me to say "Ok Google" and give instructions and it would do things like set alarms or tell me the weather and so-forth. With my nexus 6p it requires that I unlock the phone with my pattern or fingerprint before it will do anything. Is there a setting I need to enable or is this a limitation of the phone?
Any help will be greatly appreciated. THANKS!!

jimmiekain said:
My previous phone was a galaxy s6 (which I'm selling, hit me up if interested) and before that I had a nexus 5 and nexus 4. All of them allowed me to say "Ok Google" and give instructions and it would do things like set alarms or tell me the weather and so-forth. With my nexus 6p it requires that I unlock the phone with my pattern or fingerprint before it will do anything. Is there a setting I need to enable or is this a limitation of the phone?
Any help will be greatly appreciated. THANKS!!
Click to expand...
Click to collapse
Settings->google->now and search. Select voice and then OK Google detection.

jimmiekain said:
My previous phone was a galaxy s6 (which I'm selling, hit me up if interested) and before that I had a nexus 5 and nexus 4. All of them allowed me to say "Ok Google" and give instructions and it would do things like set alarms or tell me the weather and so-forth. With my nexus 6p it requires that I unlock the phone with my pattern or fingerprint before it will do anything. Is there a setting I need to enable or is this a limitation of the phone?
Any help will be greatly appreciated. THANKS!!
Click to expand...
Click to collapse
If you enable trusted voice, it should alleviate your issue.

Thank you both.
Enabling trusted voice solved the issue. Kinda strange though, my wifes GS6 doesnt have it enabled and hers still works. I'm selling my gs6 and reset it a few days ago so I have no idea what mine was set to.
Either way, I appreciate your help. Thank you both.

jimmiekain said:
Thank you both.
Enabling trusted voice solved the issue. Kinda strange though, my wifes GS6 doesnt have it enabled and hers still works. I'm selling my gs6 and reset it a few days ago so I have no idea what mine was set to.
Either way, I appreciate your help. Thank you both.
Click to expand...
Click to collapse
On the sgs6 it is set through the Google now app itself since touchwiz is written to completely change the Android Interface. I believe something is unique between the google voice commands and touchwiz though because when the sgs6 first came out it was broken for a bit on that device. Also all the security features on Samsung are also handled mostly by touchwiz.

having this same issue. trusted voice is set up and was working fine but now whenever i use ok google for anything i have to enter my lock code as well. Ive tried retraining my trusted voice model a few times, tried deleting it and resetting it up as well but whatever i do now trusted voice isnt unlocking the phone.

skimminstones said:
having this same issue. trusted voice is set up and was working fine but now whenever i use ok google for anything i have to enter my lock code as well. Ive tried retraining my trusted voice model a few times, tried deleting it and resetting it up as well but whatever i do now trusted voice isnt unlocking the phone.
Click to expand...
Click to collapse
Yeah it's sometimey I don't think there is any way around it.
Sent from my Nexus 6P using Tapatalk

help me understand

hi to all how any one that has the same setup will help me understand i will try and keep it short first im using samsung note 4 running 6.0.1 now
ok so here goes i use my gear 2 together with my note 4 as a trusted device you know like every time the gear 2 is close the device must stay unlocked but it does not stay unlocked and there is no Bluetooth disconnecting anything like this i look at that so battery is full the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage but i connect it now and its fine but after a wile (don't know the exact time here ) but say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on and there was nothing like it disconnecting it is as if the phone on its own make sure that it asks the finger print every now and again say like i leave it overnight the next morning first fingerprint then you can use the phone i hate this it kind of bugs me if the steal the phone and the range is to big the device will lock any way why lock when the gear 2 it near the phone any help please

honestly, i stopped reading after few seconds.
have you ever heard about punctuation? - you know, the thing that looks like dots and commas, makes reading much easier.

244 characters in 1 sentence.
wow dude, looks like you dont wanna get helped.

biebie29 said:
...say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on...
Click to expand...
Click to collapse
From the Google Smart Lock support page (https://support.google.com/nexus/answer/6093922):
"Note: When you don't use your phone for 4 hours, and after you reboot your phone, you'll need to manually unlock it with your PIN, pattern or password"
It's a security feature.
EDIT: ...and, wow, yes, that was some run-on sentence!

Is there a root app to disable it or not

biebie29 said:
Hi to all. How any one that has the same setup will help me understand. I will try and keep it short. First, i'm using samsung note 4 running 6.0.1 now.
Ok, so here goes:
I use my gear 2 together with my note 4 as a trusted device. You know like every time the gear 2 is close, the device must stay unlocked. But it does not stay unlocked and there is no Bluetooth disconnecting, anything like this. I looked at that. Battery is full, the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage.
I connect it now and its fine, but after a while (don't know the exact time here ), say after 3 hours of no use, i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near. The gear 2 is still on and there was nothing like disconnecting. As if the phone on its own make sure that it asks the finger print every now and again.
For example, i leave it overnight the next morning first fingerprint then you can use the phone.I hate this. It kind of bugs me if they steal the phone and the range is to big, the device will lock any way. Why lock when he gear 2 it near the phone? Any help please.
Click to expand...
Click to collapse
Fixed that for you
I really had to break that down to make it readable for me. But as others said, it's an Android feature. Afaik there is no way of disabling that all together. There might be some xposed module i haven't heard of, but with my moto360 i couldn't get it to work the way you'd want. Sorry mate

Kinsman-UK said:
It's a security feature
Click to expand...
Click to collapse
As the programmers use to says: Its a feature, not a bug

Some people are just plain jerks, and I wish XDA would take these "grammar police" trolls a bit more seriously and penalize them.
Perhaps OP is using a translator, or is from another country, or is young. That should not matter to any of us and we should offer our help regardless of whether he/she includes proper punctuation or not. I'm sure the effort he/she put into typing it was much greater than that of the ridiculous responses some of you gave.

thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing

biebie29 said:
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
Click to expand...
Click to collapse
The Note 4 is problematic all around, but 6.0.1 is a problem for every device that has it. It is the reason I left my Nexus 6P, and my Nexus 6. I have a Xiaomi Mi Max, also on 6.0.1 and it has the same major flaws I experienced on all devices running 6.0.1. The problems I speak of are the WiFi and Data stop working briefly while browsing the web, or downloading something. However, I believe this is an issue related to the security patches related to Qualcomm devices on 6.0.1. It seems like an overall radio problem.

Okay Google with screen off

In my research it looks like Samsung has disabled okay google trusted voice. In other words, when I say okay google with the screen off nothing happens even though I have trusted voice on. It works fine on my 6p.
My question is has anyone ever found a workaround for this.
It really annoys me they are trying to force me to use svoice to have this Android feature.

Yes, if you go to the Apps - settings - Language & Input - Look under virtual keyboard, there will be a little sprocket. You can click on that and tell it to allow 'ok google' only on the main screen, on any screen or anytime even when the phone is locked it will use your voice to unlock it. ,

I believe that if the screen is off, it must be charging so that is not wasting the battery listening for the command.

rbgCODE said:
Yes, if you go to the Apps - settings - Language & Input - Look under virtual keyboard, there will be a little sprocket. You can click on that and tell it to allow 'ok google' only on the main screen, on any screen or anytime even when the phone is locked it will use your voice to unlock it. ,
Click to expand...
Click to collapse
is there a way for nougat?

Outbreak444 said:
I believe that if the screen is off, it must be charging so that is not wasting the battery listening for the command.
Click to expand...
Click to collapse
It seems like that (may be?) true for the Exynos chip. The SnapDragon chip has the hardware built in (and activated) to 'always listen'. The SnapDragon 810 and later has this, and this phone should be able to do it.
This guy figured it out (somehow or other) - has to be the SnapDragon version, I believe, because it's on Sprint https://www.youtube.com/watch?v=zysh2GwYp9U

I have a european S7 (Exynos). I can wake the Phone with S-Voice by saying "Hello Galaxy" also when not charging.
A few weeks ago this also worked (only when charging) by saying "Ok Google", but this doesnt work anymore. I dont know whats the reason. I also dont have an option in the input settings where i can tell the phone when to listen to my voice. Does anyone know how to fix this with google?

I'm in the same boat as the previous comment. I was able to unlock the phone saying OK Google when the phone was plugged into Power. all settings are on for OK Google. Verizon Note 5 latest up-to-date firmware

The newer Google app updates have broken this feature. If you uninstall all updates of the Google app the original one works just fine with the screen off.

Latest Update - Facial Recognition Worse?

When I first got the phone yesterday, unlocking the phone was crazy fast with the facial recognition. This morning, I got the latest software update, and now, it's basically unusable. Has anyone else experienced this?

JDM9499 said:
When I first got the phone yesterday, unlocking the phone was crazy fast with the facial recognition. This morning, I got the latest software update, and now, it's basically unusable. Has anyone else experienced this?
Click to expand...
Click to collapse
The update was to improve the security. You may need to resetup. They made it more sensitive so it can't be unlocked with a pic as easily

bossg4 said:
The update was to improve the security. You may need to resetup. They made it more sensitive so it can't be unlocked with a pic as easily
Click to expand...
Click to collapse
After the update, it was a night and day difference. I tried registering my face again multiple times, and it worked maybe 3-10 times. It was terrible. I just reset my device though after I registering another facial input, and it's back to how it was - super fast. I'll continue to monitor if it reverts back to being unusable.

It's horrible... I can't even open my phone half the time...Just came to XDA to see if I was the only one having this issue

Same issue. The first day I got my phone I was actually bragging to everyone how amazing and fast the face unlock was. After the update it sucks, to the point where I just can't use it. I did register my face again multiple times as well.

kuulhus said:
Same issue. The first day I got my phone I was actually bragging to everyone how amazing and fast the face unlock was. After the update it sucks, to the point where I just can't use it. I did register my face again multiple times as well.
Click to expand...
Click to collapse
It's back to be crap now. After I reset the phone, it was working great again, but now not so much. I even get a pop-up sometimes saying to clean the lens!! It's spotless!
The iris scanner now is what the facial recognition WAS before the update. So, I'll start using that until this is figured out and solved because at least facial recognition works with glasses on.

Try registering your face much closer , cover most of it but not 100%, leave a gap of 2 or 3 cm. Also have you tried turning on the "faster recognition" option?

eniorodriig said:
Try registering your face much closer , cover most of it but not 100%, leave a gap of 2 or 3 cm. Also have you tried turning on the "faster recognition" option?
Click to expand...
Click to collapse
Where's the faster recognition setting

No problems with mine whatsoever. Crossing fingers it'll stay that way.

JDM9499 said:
It's back to be crap now. After I reset the phone, it was working great again, but now not so much. I even get a pop-up sometimes saying to clean the lens!! It's spotless!
The iris scanner now is what the facial recognition WAS before the update. So, I'll start using that until this is figured out and solved because at least facial recognition works with glasses on.
Click to expand...
Click to collapse
Yup using the iris scanner as well now. Surprisingly faster than the first day which is weird, but still not as fast as face unlock . I wonder which takes more battery

laz45 said:
Where's the faster recognition setting
Click to expand...
Click to collapse
Settings -> Lock Screen and Security -> Face Recognition
You should be able to find the "Faster Recognition" option in there. I believe this came bundled with an update i received today, i cannot remember also having this option before. Take a look there and make sure the phone is up to date.
I believe there is improvement to be made here, hopefully once we start rooting this puppy , someone can come along and tweak a few settings.

eniorodriig said:
Settings -> Lock Screen and Security -> Face Recognition
You should be able to find the "Faster Recognition" option in there. I believe this came bundled with an update i received today, i cannot remember also having this option before. Take a look there and make sure the phone is up to date.
Click to expand...
Click to collapse
AT&T user here. Got the OTA update yesterday that made the facial recognition terrible and I don't have the "Faster Recognition" option.
EDIT: I should also mention that I have redone the facial setup multiple times since the update and it's still noticeably worse than before the update.

Mine got slower, but I cleared cache and redid the facial set up, seems to be better again (after TMobile update).

JDM9499 said:
When I first got the phone yesterday, unlocking the phone was crazy fast with the facial recognition. This morning, I got the latest software update, and now, it's basically unusable. Has anyone else experienced this?
Click to expand...
Click to collapse
I have noticed the same I can hardly use facial recognition after update was so fast before. Now using iris

Iris is significantly better, safer and faster.

how safe is the iris scanner - from a medical POV
when activating it - you get loads of disclaimers including one saying to always keep at least 8 inch between eyes and phone to prevent retina damage - i mean WTF!!!!!!
has anyone looked into this ****?

tim2london said:
how safe is the iris scanner - from a medical POV
when activating it - you get loads of disclaimers including one saying to always keep at least 8 inch between eyes and phone to prevent retina damage - i mean WTF!!!!!!
has anyone looked into this ****?
Click to expand...
Click to collapse
Yeah I saw the warning that scared me. I'm a delivery driver and drive around 350mi a day Monday- Friday can't have my eyes damaged. Plus just payed 4500 for lasic

I have had lasik also. I would not worry about it. All things have warnings like that... heck, even your basic computer screens have warnings.

Yeah since the Att update face recognition doesn't work at all for me, wellaybe 1 time out if 10. Annoying. I'm not bothered someone could use a photo of me to unlock. If my phone is ever out of my possession for that long, I'm disabling it remotely anyway

Yep, got my s8 last night, was showing my GF how incredible facial recognition was, THEN I applied the update. Doesn't work at all, the fingerprint scanner is in the worst possible place, and I wear glasses so the iris scanner won't work for me. I can't believe I'm starting to miss the fingerprint scanner on the S7.

Trusted Voice MIA

Hi all, hopefully this has not been discussed. I searched but from the xda app search isn't so great...
Anyway wondering if anyone is having issues with trusted voice. I noticed okay Google was only working when phone was authenticated. And not from secured lock screen. Figured trusted voice was disabled, so I checked and it's just not there. (See image). I'm on 4.5.8 stock not rooted. I have tried clearing data on Google app.
Any suggestions is appreciated.
Thanks!

I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.

3DSammy said:
I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.
Click to expand...
Click to collapse
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.

tsuttie99 said:
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.
Click to expand...
Click to collapse
I'd read that others (UK) switched back to their native language after getting Google Assistant working and all was well. I've left it as US as primary with Canada as a second as it simply doesn't effect me. I like spelling colour as "color" which always made more sense to me.
My real reason for not switching back is that I've done a lot of home automation scripting with Google Assistant/Tasker's Voice Assist/Termux to automate my audio/video equipment and associated lighting. As far as I'm concerned Google Assistant may be in beta for built in functionality but is alpha for any third party integration. Every Google app update seems to break something while fixing other functionality (e.g. macros).
I like the automation I've created enough that I have little interest in rocking the boat at the moment. I had previously retested Trusted voice and the lock screen after updates and will again until it works. Right now I'm using a work around with an app called Caffeine (disables the lock screen timeout when charging) and Screen off (only turns the screen off but does not trigger the lock screen).
Also I may have tried toggling Trusted agents as I did so many tests and retests while working on Google Assistant functionality, I just can't remember.

I think there is something very broken with Smart Lock on this phone's stock OS.... I set up my cars BT as trusted device.... still i need to Authenticate with finger/pattern. Coming from a 6P where this all worked seamlessly it's frustrating.

My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.

ultramag69 said:
My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.
Click to expand...
Click to collapse
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?

3DSammy said:
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?
Click to expand...
Click to collapse
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash

tsuttie99 said:
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash
Click to expand...
Click to collapse
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.

3DSammy said:
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.
Click to expand...
Click to collapse
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.

Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?

tsuttie99 said:
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.
Click to expand...
Click to collapse
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.

Rebel7022 said:
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.
Click to expand...
Click to collapse
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?

tsuttie99 said:
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?
Click to expand...
Click to collapse
There's a xda article on OK Google that has a hack to do that. I tried it it works.. But that was 3 months ago

tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Yep, works from lock screen, not screen off...

tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Well fancy that. I just did your test, locked screen with power button, with screen off there's no reaction to "OK Google". I then double tap the screen and the lock screen displays. Now "OK Google" unlocks the phone and Google Assistant is fully functional.
Kind of feels like a sprinter that falls inches before the finish line. What the heck Google or OnePlus? I wonder if custom ROMs have the same issue?
Thanks for noticing this phenomena and posting about it.