I think about buying the Axon 7, but got one question left and haven't found an answer anywhere:
Is the OK Google Command working without the screen being turned on or the device being charged?
Basically: is it behaving like a Nexus device would? I know many devices only react to "OK Google" if the device is turned on and/or charging.
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Delete
xxBrun0xx said:
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Click to expand...
Click to collapse
This is not true. When charging, I can say ok google and the devices listens to me. Also, if the screen is on and I'm not charging, I can still say ok google and it will listen.
notese said:
This is not true. When charging, I can say ok google and the devices listens to me. Also, if the screen is on and I'm not charging, I can still say ok google and it will listen.
Click to expand...
Click to collapse
Could be wrong but it sounded like he was asking if off screen voice commands worked while the phone was not charging?
xxBrun0xx said:
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Click to expand...
Click to collapse
And the V20 apparently
xxBrun0xx said:
Could be wrong but it sounded like he was asking if off screen voice commands worked while the phone was not charging?
Click to expand...
Click to collapse
You are right! I got really used to using "OK Google" while the phone is in stand-by, i.e., screen turned off and not charging.
Why are vendors not able to properly implement this? The Snapdragon is technically able to do this.
smuurfi said:
And the V20 apparently
You are right! I got really used to using "OK Google" while the phone is in stand-by, i.e., screen turned off and not charging.
Why are vendors not able to properly implement this? The Snapdragon is technically able to do this.
Click to expand...
Click to collapse
Yeah it really breasts me. I miss that from my Nexus 6p, but that's about the only thing I miss other than camera and nougat. The snapdragon 820 is amazing and battery life on the Axon is better than the 6p.
Sorry to bring up an old thread, but I've missed being able to say Okay Google from when the screen is off like I was able to on the 6P. I've been trying to figure out why and I think maybe one of two things (maybe both) is happening. One is that the power manager automatically screen cleans the Google app. The app isn't in the power management menu so that you can toggle off screen cleaning. The other is that I think the phone turns off the mic when the screen turns off and locks. However, if I just used Google Assistant and turn off the screen, I am able to use Okay Google with the screen off if I say it a split second after I turn off the screen with the power button. Sometimes it works, sometimes I have to enter my PIN, but it always has to be right after using Google Assistant and locking the screen. Throwing this out there with the hopes that someone might be able to figure out how to get around this.
Yep same
Mike
Related
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
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.
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.
As title suggests, voice recognition has been really unreliable through my daily usage.
If the phone is locked - "Ok Google" never works, yes i have set Smart unlock to unlock through voice.
if the phone is unlocked - "Ok Google" works, but if connected to my car's Bluetooth, it doesn't.
any of you guys can share their experience?
gilad215 said:
As title suggests, voice recognition has been really unreliable through my daily usage.
If the phone is locked - "Ok Google" never works, yes i have set Smart unlock to unlock through voice.
if the phone is unlocked - "Ok Google" works, but if connected to my car's Bluetooth, it doesn't.
any of you guys can share their experience?
Click to expand...
Click to collapse
I have the same issue...
Same issue here. I think it's because of Samsung's aggressive management that won't allow Google Now to run in the background when the screen is off.
Sent from my SM-G950F using Tapatalk
Same issue here
I normally have to reboot to get "Okay Google" command to work.
for me ok google works for while, then stops working and a reboot is the only way to fix it. only annoying thing is i need to reboot every other day. this issue doesn't seems to be covered much?
electric0ant said:
for me ok google works for while, then stops working and a reboot is the only way to fix it. only annoying thing is i need to reboot every other day. this issue doesn't seems to be covered much?
Click to expand...
Click to collapse
fix for the OK Google issue on S8 & S8+ is to have the software re-flashed by Samsung or one of their retailers such as Best Buy. Other than rooting the device, there is nothing that can be done at the consumer level nor with tech support assistance that will resolve the issue.
Sikrik said:
fix for the OK Google issue on S8 & S8+ is to have the software re-flashed by Samsung or one of their retailers such as Best Buy. Other than rooting the device, there is nothing that can be done at the consumer level nor with tech support assistance that will resolve the issue.
Click to expand...
Click to collapse
what difference would re-flashing the software achieve?
flashing stock firmware can be achieved using odin.
and after rooting what can be done to fix this issue?
I don't know why re-flashing it worked but, it did. I also don't care. The phone works perfectly now. I keep seeing the same remedies over and over on forums such as this and NONE of them worked. Now that my phone is working, I shared what I did to get it fixed. I'm not a techie, I'm a truck driver so, if you said that I can flash stock firmware with Odin, you'd be wrong. Besides, why would I? Samsung screwed it up, they can fix it. It was free and it worked.
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
dancooper93 said:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
Click to expand...
Click to collapse
Can Tasker achieve something like this? I have only returned to Android after a 3 years break, any advice is much appreciated!
dancooper93 said:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
Click to expand...
Click to collapse
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
srdjanLeo said:
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
Click to expand...
Click to collapse
I have that setting enabled. It works on the lock screen where you can swipe to unlock, but not on the darker lock screen, where it shows the time and the outline of your notifications.
srdjanLeo said:
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
Click to expand...
Click to collapse
I have enabled them options. It works on the light lockscreen, where you can scroll your notifications and have the 2 icons in the bottom corners.
It does not work on the darker lock screen, or the Always On Display screen, where it only shows the time and the outline of notifications you have.
dancooper93 said:
I have enabled them options. It works on the light lockscreen, where you can scroll your notifications and have the 2 icons in the bottom corners.
It does not work on the darker lock screen, or the Always On Display screen, where it only shows the time and the outline of notifications you have.
Click to expand...
Click to collapse
Works here as it should. With AOD and without. Are you rooted? If you are try other ROM. If you are not, try reflashing stock firmware with Odin or with Side Sync or whatever Samsung kies is now called.
srdjanLeo said:
Works here as it should. With AOD and without. Are you rooted? If you are try other ROM. If you are not, try reflashing stock firmware with Odin or with Side Sync or whatever Samsung kies is now called.
Click to expand...
Click to collapse
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
dancooper93 said:
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
Click to expand...
Click to collapse
Same for me Dan, works after you swipe but not from AOD, every tutorial I have seen says the same, has to be "open" before it will work.
Bixby will unlock from the AOD screen if you set that up, hope that helps
MilgeS said:
Same for me Dan, works after you swipe but not from AOD, every tutorial I have seen says the same, has to be "open" before it will work.
Bixby will unlock from the AOD screen if you set that up, hope that helps
Click to expand...
Click to collapse
What do you mean 'open'?
I have Bixby set up, which I just use to open Google now, not ideal, but it is a workaround nonetheless!
dancooper93 said:
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
Click to expand...
Click to collapse
I am rooted. With custom ROM, NOTE 8 Port.
Charging works as it should, OK Google trigger works as well. I really don't have any problem.
srdjanLeo said:
I am rooted. With custom ROM, NOTE 8 Port.
Charging works as it should, OK Google trigger works as well. I really don't have any problem.
Click to expand...
Click to collapse
It works for you because you are using a Note 8 ported ROM. Because Samsung enabled this feature on the Note 8. It will not currently work on the stock S8 ROM. Some people seem to be in a server side test to enable this feature though.
Okay, I see.
Does charging not stop at 80% for you because you are rooted?
artikle said:
It works for you because you are using a Note 8 ported ROM. Because Samsung enabled this feature on the Note 8. It will not currently work on the stock S8 ROM. Some people seem to be in a server side test to enable this feature though.
Click to expand...
Click to collapse
It was working for me on Bat Stock ROM and it is S8 ROM. I never used stock ROM so I can't say anything about that, I rooted my device and flashed custom ROM before even setting it up after unboxing.
srdjanLeo said:
It was working for me on Bat Stock ROM and it is S8 ROM. I never used stock ROM so I can't say anything about that, I rooted my device and flashed custom ROM before even setting it up after unboxing.
Click to expand...
Click to collapse
I forgot to quote you, sorry.
Question:
Does charging not stop at 80% for you because you are rooted?[
dancooper93 said:
I forgot to quote you, sorry.
Question:
Does charging not stop at 80% for you because you are rooted?[
Click to expand...
Click to collapse
It stops. But there is a workaround if you have Snapdragon version. Mine is Exynos so it is as Samsung set it up.
srdjanLeo said:
It stops. But there is a workaround if you have Snapdragon version. Mine is Exynos so it is as Samsung set it up.
Click to expand...
Click to collapse
I am now rooted
What Note 8 ROM did you use?
dancooper93 said:
What do you mean 'open'?
I have Bixby set up, which I just use to open Google now, not ideal, but it is a workaround nonetheless!
Click to expand...
Click to collapse
I meant "open" as in on lock screen re your above post, the screen after AOD, sorry for any confusion
Same here works after you swipe but not from AOD, every time tutorial I have seen says the same has to be "open" before it will work.
It's best to think of the always-on display as "Screen Off", which is why OK Google doesn't work on stock ROM. That's standard Android procedure to avoid draining the battery by always listening for voice commands.
At one point, Google Assistant was able to listen when the screen was off, so long as the phone was being charged. Unfortunately, that feature disappeared at some point in the past half year or so (which caused me some confusion when it stopped working and I could no longer find the toggle).
scatterthought said:
It's best to think of the always-on display as "Screen Off", which is why OK Google doesn't work on stock ROM. That's standard Android procedure to avoid draining the battery by always listening for voice commands.
At one point, Google Assistant was able to listen when the screen was off, so long as the phone was being charged. Unfortunately, that feature disappeared at some point in the past half year or so (which caused me some confusion when it stopped working and I could no longer find the toggle).
Click to expand...
Click to collapse
That's not true. It still works on a Google Pixel running stock Android with the screen off and not charging. You never had to have it plugged in or charging for that to work. Samsung is the ONLY Android phone I know of that OK Google doesn't work with the screen off.
Source: I've owned the Nexus 6, Nexus 5x, the Nexus 6P, the Pixel XL, a number of Galaxy phones, and a few Motorola's and a couple LGs.