Database Users

Doesn't ANYONE have issues with "Ok Google!" stopping working?

No matter what rom I'm on....stock or modified...whether I'm fully wiped or not..."OK GOOGLE" detection stops listening and unchecks itself, (Always on and Personal results turn off).
Restarted, wiped cache, downgraded Google app, etc, etc. This is a major flaw and the ONLY reason I'm unhappy with this phone...isn't anyone else having these issues? H910 here, rooted with DirtySanta. VERY frustrated.
THIS is the closest thing I've seen relating to the bug I'm experiencing....but Accessibility fixes NOTHING. https://www.xda-developers.com/psa-disabling-accessibility-services-breaks-ok-google-feedback/

I don't have that issue. I am using NotSoStock rom on vs995. The only thing I changed was the build prop so that I can use the pixel launcher and google assist.

yes, I see it as well. Out of the blue the Hot Word Detection will be turned off. I am forced to turn it back on. My voice model is still in tact though, have no idea as to why this setting keeps turning itself off either.
curious, are you using TBO Black Out gapps?

I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.

reaktor TuT said:
I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.
Click to expand...
Click to collapse
The app doesnt seem to be forgetting my voice. The setting just gets turned off for what ever reason. When I toggle it back ON its not asking to train, so the voice remains there.
edit...I have a android wear device (smart watch) with the "OK Google" enabled. maybe it gets turned off on my v20 in favor of the wear device.
here is when it crashes
Code:
01-18 05:02:43.939 3064 23321 W AlwaysOnHotwordDetector: startRecognition() failed with error code -19
full log, from enabling to the auto disable that occurs if anyone is interested
http://pastebin.com/Qc5YRTGT

I also have an android wear watch. You may be right, I haven't been wearing my watch the last fortnight, about the time the V20 has been behaving...

reaktor TuT said:
I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.
Click to expand...
Click to collapse
I thought it was only me...maybe it's a Google thing

bobafx said:
I don't have that issue. I am using NotSoStock rom on vs995. The only thing I changed was the build prop so that I can use the pixel launcher and google assist.
Click to expand...
Click to collapse
I had it on that rom, too. Worked, no updates at all, no system apps restored from Titanium...then stopped. Tried all of the "solutions" I found online, none worked. Kept toggling itself back off and freezing. Same as on stock. I'm on bone stock now with attkernel that I flashed and it's flying. So far, so good. But...give it a few more days. LOL.

reaktor TuT said:
I also have an android wear watch. You may be right, I haven't been wearing my watch the last fortnight, about the time the V20 has been behaving...
Click to expand...
Click to collapse
Nope, I definitely don't have a watch or anything. The above post talks about a bug with Accessiblilties but none of what he said fixed my issue.

cordell12 said:
The app doesnt seem to be forgetting my voice. The setting just gets turned off for what ever reason. When I toggle it back ON its not asking to train, so the voice remains there.
edit...I have a android wear device (smart watch) with the "OK Google" enabled. maybe it gets turned off on my v20 in favor of the wear device.
here is when it crashes
Code:
01-18 05:02:43.939 3064 23321 W AlwaysOnHotwordDetector: startRecognition() failed with error code -19
full log, from enabling to the auto disable that occurs if anyone is interested
http://pastebin.com/Qc5YRTGT
Click to expand...
Click to collapse
I don't have a watch. Only a bluetooth headset, car audio and bluetooth speaker. Other than that...no paired anything, in any way. It just decided to toggle "Always On" off and stay off...even after retraining, it freezes and untoggles, even on a restart or battery pull.

reaktor TuT said:
I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.
Click to expand...
Click to collapse
I thought so too...but I blocked updates...and am on root so I froze all apps that I usually install. Broke again. I'm on stock w/ root and att kernel at the moment and all SEEMS good...been a day. But, I'll update when it breaks again.

cordell12 said:
yes, I see it as well. Out of the blue the Hot Word Detection will be turned off. I am forced to turn it back on. My voice model is still in tact though, have no idea as to why this setting keeps turning itself off either.
curious, are you using TBO Black Out gapps?
Click to expand...
Click to collapse
Nope. No gapps. Was on Not So Stock...but for weeks have been going back and forth to stock w/ root and back, trying to troubleshoot. I'm now on bone stock, w/ Nova launcher and att kernel. I'm flying on it...same as other roms...and Google Now works just fine, but it's been a DAY. I'll update when/if it stops working.

Yup I had thought I may have fixed it once - but turns out it still switches off on me too. I'm on H910 with NSS ROM. I'm wondering if it has something to do with the kernel if yours is working currently on complete stock. But at least it does work on my home screen so I dont really mind much.
But yeah when going into the settings and switching Always On to ON state, and then when you go back in - the app freezes up for awhile (like about 30secs to a minute). Then it comes back up, but the Always On is toggled OFF again.
Edit: or maybe it is due to being a deODEX'ed ROM? I know occasionally issues happen for different apps when its deODEXed.

twistedvip said:
Yup I had thought I may have fixed it once - but turns out it still switches off on me too. I'm on H910 with NSS ROM. I'm wondering if it has something to do with the kernel if yours is working currently on complete stock. But at least it does work on my home screen so I dont really mind much.
But yeah when going into the settings and switching Always On to ON state, and then when you go back in - the app freezes up for awhile (like about 30secs to a minute). Then it comes back up, but the Always On is toggled OFF again.
Edit: or maybe it is due to being a deODEX'ed ROM? I know occasionally issues happen for different apps when its deODEXed.
Click to expand...
Click to collapse
FANTASTIC! I was trying to tell people I wasn't imagining it! LOL. Here's the kernel I'm using, which flies for me, zero lag, and is bone stock AT&T. https://www.androidfilehost.com/?fid=385035244224411218...Thank Team DevDigitel for providing this awesome kernel thread. https://forum.xda-developers.com/v20/development/device-kernel-aka-boot-img-s-carrier-t3533426
I'm running this...day two of perfection... AlkaliV2's https://www.androidfilehost.com/?fid=457095661767123457 BONE STOCK IMAGE...attboot.img here :https://www.androidfilehost.com/?fid=385035244224411218.....whatever else you want like Viper4Android from here...http://downloadmirror.co/2zYA/ViPER4Android_2.5.0.5_guitardedhero.zip (Don't forget to delete or add .bak to audio_effects.conf, in file manager in TWRP at system/vendor/etc, after mounting system) ...and of course lastly, don't forget to flash SuperSU 2.79 flashable zip from here: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip. I then, only use Titanium Backup Pro to restore apps only, no data...and no system apps.
Try it and lemme know how you fare. I'm glad I'm cruising beautifully for now...with the exception of Viper4Android stopping working like I've experienced on all roms.
Best of luck!!!!:good:

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.

"Ok Google" is not reliable

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.

OK Google while AOD (Screen off)

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.

Ok google with screen off?

I wonder If someone knows any rom or any method for enabling Ok google detection when screen off
I had the feature in nexus 5x..and it is lot lot useful

Not at this time on OOS (any version). I've not heard of any custom ROM with that feature as your question has been discussed a number of times. I posted a clumsy work around when the OP5 is in a charger using two apps but I only do that because I use the phone as a Google Home and want to avoid screen burn-in.

Ah ok, understand
Well, about your workaround, dont you think it might be harmful for the phone to be pluged in all the time?

http://www.droidviews.com/force-ok-google-detection-screen-off/

I had also seen a Xposed module that had this option. I don't remember the name. Maybe you can try some combinations of google now search etc. in the xposed repository.

Great find. thanks, but like others in the comment section of the article this doesn't work with the OP5 with OOS. When the battery set command is activated it automatically turns the screen back on. So the normal lockscreen timeout goes into an endless loop of screen off then automatically back on, not something you could tolerate. There may be a way to work around by adding another command but so far I've not found a compatible command. Tasker's own Sys Lock isn't an option as it forces a pin/swipe unlock (no fingerprint) and definitely cuts off trusted voice.

Hmm ok, thanks both! So maybe it would work with custom roms then...but for now is not my plan. But thanks anyway

Ok thank you! I've not installed Xposed yet but I note it so I will check when I do