Ive asked in some threads thinking this is ROM specific however this is most definitely not. I'm curious if anyone on a either variant of a S8 that uses OK google anywhere (AKA when the screen is off) also has the same problem that occurs for myself.
Issue is as follows:
Randomly when idle and screen off OK/Hey Google fails to respond (Not sure if consistent timeframe)
The workaround: Doing this will allow the Hot word detection to work properly until whatever circumstances occur that disable it
Engage Google assistant manually
I've tried various scenarios involving eliminating lock screens. Stock imgages from samsung etc...
This is not related to Smart Lock or unlocking the phone with hotwords. Only related to the response portion.
My theory is the processes being terminated for some odd reason (Yes its installed as a system service otherwise you cannot enable Ok google anywhere)
PS my pixel 3 sitting in my backpack for days responds 100% but apparently the S8 seems flawed... ASOP roms such as Lineage seem to not be affected although I only tested for about a day or so. I'm pretty bent on this is a Samsung issue since they cant create a piece of software for the life of em.
Is Bixby disabled? I've read about issues with Ok Google not working after a phone call, and the cause there was the microphone becoming available after the call triggers a call to Bixby (presumably to resume Bixby Voice's similar voice command listening feature) so if you have removed or disabled Bixby Voice it may be the problem here as well. Screen on if Ok Google Anywhere is disabled would possibly be a condition that wakes the microphone in a similar way.
Related
After testing the note 4 nexus 6 and s5 prime, i have come to the conclusion that the always on feature of the note 4 is not always on.
With the google search bar widget floating on the homescreen with the screen on the note 4 would pick up the okay google command 100% of the time.
Now with the screen off or locked, it would pick up the command 100% of the time at times, 0% sometimes( doing this test makes me feel retarded). This leads me to believe that when it doesnt respond, the mic simply isnt listening, an s voice issue. And that the google floating widget uses a completely separate routine for its listening.
Anyone have any inputs on this? Will lollipop fix it? Or is it something that cannot be fixed?
It works for me - on, off, locked or not.
It does for me. Just not consistently.
shinasurada said:
After testing the note 4 nexus 6 and s5 prime, i have come to the conclusion that the always on feature of the note 4 is not always on.
With the google search bar widget floating on the homescreen with the screen on the note 4 would pick up the okay google command 100% of the time.
Now with the screen off or locked, it would pick up the command 100% of the time at times, 0% sometimes( doing this test makes me feel retarded). This leads me to believe that when it doesnt respond, the mic simply isnt listening, an s voice issue. And that the google floating widget uses a completely separate routine for its listening.
Anyone have any inputs on this? Will lollipop fix it? Or is it something that cannot be fixed?
Click to expand...
Click to collapse
Im having the same issue. Ive just got my self a wear watch and configured now to take instructions. Also like being able to wake my note 4 by shouting at it.
I think its when it goes in to deep sleep... still testing...
I always felt like there was a conflict between Svoice and Google Now so I usually uninstall or disable Svoice (cos i prefer GN) but i read somewhere the always listening only works with Google Now Launcher. What launcher are you using? But anyway, Svoice should work with TW, otherwise Samsung are selling defective phones!
Im on the google launcher.
I dont think its a deep sleep issue since it fails to register ok google sometimes even when the screen is on.
E.g. in an app, lock screen and screen off.
however it never fails in any screen with a google now microphone. E.g. maps, google now or any homescreen with the google now search bar widget.
It's because it keeps Un ticking listen all the time in Google now as soon as I set s voice. As stated earlier, I think only one can be the always listening and now doesn't do screen off.
I have got round it by setting tasker profiles to open now when svoice is open.
So I can shout galaxy to wake it, ok google then instruct it to do a billion other tasks I have set through commandr. This set till slows me to use Google now with my LG round. All round it's working pretty good, exept it not waking from time to time...
I use nova launcher (has enable ok google for nova in settings)
But unfortunately have failed to get all other non Google apps to work with ok google, the 3rd party ok google x posed module breaks commandr.
Hope this helps some one.
Looking forward to fixing this "not listening" from time to time.
Everyone still having the same issue? I am still no solution, can't identify the problem or what's causing it either...
Same issue here. Works 100% from home screen or Google search/now. Very unreliable everywhere else
snowblind2142 said:
Everyone still having the same issue? I am still no solution, can't identify the problem or what's causing it either...
Click to expand...
Click to collapse
After making S-Voice a Phone Admin, the problem appears to have been solved - for myself at least. S-Voice still has some issues recognizing my voice if I'm in a particularly loud area, but I can always count on it otherwise.
Just a suggestion (for those who haven't tried yet): Try to record your wake-up command in different ways to help its accuracy (kind of like how you did your fingerprint). Oh and be as relaxed and natural as possible :good:
Can you elaborate on making s voice a phone admin please?
shinasurada said:
Can you elaborate on making s voice a phone admin please?
Click to expand...
Click to collapse
I assume he means in accessibility. I did this but still seemed to have the problem but will try again. I even left double home tap as s voice as I heard it makes it "always wait" to be pressed, and I assumed this would ensure it was running in the background.
Will let you know if it solves the issue for me.
So while GA unlocks my phone by voice when the screen is on and the phone is locked, GA doesn't seem to respond when you shut the screen off, even though the setting for secure voice is active.
I don't know if this is working as planned but it seems to really defeat the purpose of this.
While I get no response from my DT2, my DT1 actually responds with the sound prompt while the screen is off. However, I can't issue any commands.
Anyone else experience this?
Yes, same on my DT2. Saying Ok Google with screen off won't trigger Assistant. Does fine with screen on. Makes me want to go back to Moto Voice, which works every time.
Yeah, this is a real pissed, especially coming from the Nexus 6. I'm definitely bummed that you can't open phone with Okay Google
I have the same exact problem. Anyone know if this is an acknowledged bug that might be fixed? Or is it some weird conflict with Moto Voice, that we're stuck with?
Pretty sure it's got something to do with Moto Voice, don't these phones have a separate processor just for voice or something to that extent?
What happens if you set your moto voice activation sentence to "ok google"?
Am I the only one plus 5 user who cannot access ok google while the phone is locked and screen off? All the settings are enabled in voice setting inside the google app.
I have tried while the phone is charging with the original charger and 3rd party. OK google works normally throughout the phone but not while it is plugged in and screen off. Can someone test it and let me know!
Hi Kevin,
Got the same issue on mine.
It does work of the screen is on while phone locked.
However, it does not if the screen has turned off.
I used to use it like this all the time with my OP2.
Wondering if it's Google Assistant specific?
If there is anyone who hasn't forced Google Assistant onto their phone (unlike myself which had to use the US English trick) I would be interested to know if the same still applies.
same here . doesn't work when screen is off
kevingonzalez said:
Am I the only one plus 5 user who cannot access ok google while the phone is locked and screen off? All the settings are enabled in voice setting inside the google app.
Click to expand...
Click to collapse
As other mentioned the screen off/locked combo will not respond to Google Assistant (GA) commands. I can get "OK Google" to work with the screen off but unlocked which I do while its in the charger with a hacky work around. I use a combo of the Caffeine app (overrides screen lock timeout while charging) and a Screen off app then turns the screen off but does not lock. I have a Google Assistant macro to launch the Screen off app on command.
I sure wish Google/OnePlus would fix this issue at least while charging as I like to use the OP5 for home automation and can see no reason to purchase a Google Home when I already have a more powerful device which is more versatile (the OP5). I have Google Assistant (GA) set up to control my audio/video equipment and associated lighting and am finding additional uses for GA everyday.
Hello everyone, I just came from a Nexus 6P, and was wondering if "ok google" from screen off is a feature on the OnePlus 5. I have swore I had it when I first got the phone but now it doesn't seem to be working. I've looked around a little and there seems to be a lot of disagreement about whether it's possible or not. Does anyone want to test it and post whether it works for them or not? (or used to work)
jplafor1 said:
Hello everyone, I just came from a Nexus 6P, and was wondering if "ok google" from screen off is a feature on the OnePlus 5. I have swore I had it when I first got the phone but now it doesn't seem to be working. I've looked around a little and there seems to be a lot of disagreement about whether it's possible or not. Does anyone want to test it and post whether it works for them or not? (or used to work)
Click to expand...
Click to collapse
I never used stock OOS, only xXx and Pure Fusion, and "ok google" doesn't work on either while phone is locked (which, to my understanding, is not the same thing as "screen off")
I have been missing this ever since I got this phone and moved away from my Moto x Pure. It's really aggravating there is no way to get this to function correctly, or at all, with the screen off. I don't get it.
jplafor1 said:
Hello everyone, I just came from a Nexus 6P, and was wondering if "ok google" from screen off is a feature on the OnePlus 5. I have swore I had it when I first got the phone but now it doesn't seem to be working. I've looked around a little and there seems to be a lot of disagreement about whether it's possible or not. Does anyone want to test it and post whether it works for them or not? (or used to work)
Click to expand...
Click to collapse
FYI: This was answered in a thread on Google Assistant.
1. "OK Google" will NOT work from the lock screen even when "Trusted voice" is enabled and the screen is off.
2. "OK Google" will unlock the lock screen when "Trusted voice" is enabled AND the screen is on.
3. "OK Google" will react if the screen is off but the lock screen is not on.
I hope that helps.
From what I read its speculated that with OOS it was chosen to save battery by turning off "listening" when the lock screen is on and the screen is off. Personally I think that OOS should be "listening" under those conditions if your also charging or at least have that option as a settings toggle.
I've personally had to hack a way around this issue by using a couple of apps (Caffeine, Screen Off (no lock)) to get into a #3 (above) condition when I'm attached to the charger so my OP5 can double as a Google Home and have my screen off most of the time without automatically locking.
3DSammy said:
FYI: This was answered in a thread on Google Assistant.
1. "OK Google" will NOT work from the lock screen even when "Trusted voice" is enabled and the screen is off.
2. "OK Google" will unlock the lock screen when "Trusted voice" is enabled AND the screen is on.
3. "OK Google" will react if the screen is off but the lock screen is not on.
I hope that helps.
From what I read its speculated that with OOS it was chosen to save battery by turning off "listening" when the lock screen is on and the screen is off. Personally I think that OOS should be "listening" under those conditions if your also charging or at least have that option as a settings toggle.
I've personally had to hack a way around this issue by using a couple of apps Caffeine, Screen Off (no lock)to get into a #3 (above) condition when I'm attached to the charger so my OP5 can double as a Google Home and have my screen off most of the time without automatically locking.
Click to expand...
Click to collapse
I understand that this feature has been cut off as a measure to optimize battery life but
This thread is not on xda just to discuss what OEMs have restricted us to, right?
Besides there are many of us who would prefer this feature over an hour or two of battery life
I've also been doing some research
I've tried those apps that keep your display "Always on" after you press the power button, but that option wasn't very robust:
One extra press of the power button would turn off the app and thus the screen
Ok Google detection works well if the device was locked recently, not working at all after a few hours
Associated with an hour less of battery life
But the app made checking time and notifications a bit less tedious
Basically the AOD feature from recent Samsung devices
Let me know of any workarounds that involve least number of third party apps
BTW, I use trusted voice, and it works well, friends tried a lot to get through but never could , helps with the unlocking part of the above feature
TL;DR: It is very much possible!
I was were you guys were some weeks ago and also thought that it would be nice to have true hands-free capabilities, so I searched for an app that could do this. The main issue with the "OK Google"-detection, as @3DSammy already stated, is that the screen has to be on in order for it to work (and trusted voice has to be enabled, obviously). The best workaround for this is an app that keeps your screen turned on without draining the battery too much. For this purpose I downloaded an app called "Always On AMOLED - BETA" (https://play.google.com/store/apps/details?id=com.tomer.alwayson&hl=en), which enables an always-on display, as the name suggests. The app itself works really well with few bugs and doesn't drain the battery too much, although it is noticeable. It will automatically start once you lock your device and is customizable to your liking. While it is running, you can use "OK Google" at any time when it's outside your pocket (and the always-on display is on), just make sure to disable aggressive doze and enable auto-start for the app to prevent it from getting choked off by the OS. Root access may also help. When pressing the power button the app will close and open your lockscreen as you would expect, and the fingerprint sensor does also work straight from the a-o display, which can't be said for every app out there. The sensor is a bit slower though...
Hope I could help!
It's possible to set up for when locked in Settings > Security > Smart Lock, but I'm not sure if you can do it when it's OFF.
Chaphasilor said:
TL;DR: It is very much possible!
I was were you guys were some weeks ago and also thought that it would be nice to have true hands-free capabilities, so I searched for an app that could do this. The main issue with the "OK Google"-detection, as @3DSammy already stated, is that the screen has to be on in order for it to work (and trusted voice has to be enabled, obviously). The best workaround for this is an app that keeps your screen turned on without draining the battery too much. For this purpose I downloaded an app called "Always On AMOLED - BETA" (https://play.google.com/store/apps/details?id=com.tomer.alwayson&hl=en), which enables an always-on display, as the name suggests. The app itself works really well with few bugs and doesn't drain the battery too much, although it is noticeable. It will automatically start once you lock your device and is customizable to your liking. While it is running, you can use "OK Google" at any time when it's outside your pocket (and the always-on display is on), just make sure to disable aggressive doze and enable auto-start for the app to prevent it from getting choked off by the OS. Root access may also help. When pressing the power button the app will close and open your lockscreen as you would expect, and the fingerprint sensor does also work straight from the a-o display, which can't be said for every app out there. The sensor is a bit slower though...
Hope I could help!
Click to expand...
Click to collapse
Thank you, but my fingerprint doesnt work until I turn on my screen
yuval328 said:
Thank you, but my fingerprint doesnt work until I turn on my screen
Click to expand...
Click to collapse
maybe try contacting the dev of the app for that? It's been some time since I used this setup myself
https://docs.google.com/spreadsheets/d/1Tvr5z8A_EvZ-BC-ZP2bKARReKwAG3nVpvEYEpwujfoU/
Above is an editable Google Sheet I created to document the issues present on Pixel 2 / XL devices, amongst others. I've been having rather buggy experiences with my Pixel 2 lately and thought it would be best to have these all in one place, along with the amount of days the issue has been present and unfixed.
Feel free to add in any issues you have personally noticed that are currently plaguing your phone, just make sure to include all relevant information.
I would not like to disrupt your organised data with some raw unconcrete data which I have no statistics about how much people are complaining about it, But here's some stuffs that could be investigated into, then maybe added to your list.
All below are as from android P preview
Turning off the screen causes an annoying delay sometimes for the clock display to appear.
Double tapping the screen to wake up phone sometimes does not work.
Phone randomly puts notification sound level to zero(lowest).
Google voice recognition to wake up phone sometimes trigger out of nowhere( it displays message voice not recognised though).
Face recognition to wake up has too little timeout and requires you to insert pin/ fingerprint afterwards, unless you turn off your screen again and restart the operation.
Sometimes taking a picture on my phone rotates the picture to landscape for no reason.
atifaslam7 said:
I would not like to disrupt your organised data with some raw unconcrete data which I have no statistics about how much people are complaining about it, But here's some stuffs that could be investigated into, then maybe added to your list.
All below are as from android P preview
Turning off the screen causes an annoying delay sometimes for the clock display to appear.
Double tapping the screen to wake up phone sometimes does not work.
Phone randomly puts notification sound level to zero(lowest).
Google voice recognition to wake up phone sometimes trigger out of nowhere( it displays message voice not recognised though).
Face recognition to wake up has too little timeout and requires you to insert pin/ fingerprint afterwards, unless you turn off your screen again and restart the operation.
Sometimes taking a picture on my phone rotates the picture to landscape for no reason.
Click to expand...
Click to collapse
If you are able to find bug reports or product forums detailing the bugs listed, I would be happy to add them to the list. Also given that Android P is in active development, it's much more likely for there to be bugs, as opposed to in Android 8.1 which is months past its initial development.
steejo said:
https://docs.google.com/spreadsheets/d/1Tvr5z8A_EvZ-BC-ZP2bKARReKwAG3nVpvEYEpwujfoU/
Above is an editable Google Sheet I created to document the issues present on Pixel 2 / XL devices, amongst others. I've been having rather buggy experiences with my Pixel 2 lately and thought it would be best to have these all in one place, along with the amount of days the issue has been present and unfixed.
Feel free to add in any issues you have personally noticed that are currently plaguing your phone, just make sure to include all relevant information.
Click to expand...
Click to collapse
Sorry, I can't say that I've experienced a single one of these issues.