Sometime in the past 48 hours, I got the new option in Google Now to enable the "OK Google" hotword detection from any screen, so of course I went ahead and turned it on, and have been loving it.
A little while ago, I went to record something with the stock Voice Recorder (which unfortunately is something I do quite often), and it won't record. It gives me a message "Unable to start a new recording. Other applications already recording". So I go back into Google, disable the hotword detection from any screen, and look and behold, Voice Recorder works again.
I haven't tried any other recording apps yet to see if they have the same conflict, but I intend to shortly. I just figured I'd let others know about the issue. It seems like a huge oversight on Google's part that such a highly anticipated feature would break one of the stock functions on a popular flagship device. Hopefully they push a fix soon, or someone here finds a way around the problem....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N900T
Just checked, mine too. Fortunately, I have never had a need to use voice recorder.
how do you make it work did you get a update
---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------
Morningstar said:
Sometime in the past 48 hours, I got the new option in Google Now to enable the "OK Google" hotword detection from any screen, so of course I went ahead and turned it on, and have been loving it.
A little while ago, I went to record something with the stock Voice Recorder (which unfortunately is something I do quite often), and it won't record. It gives me a message "Unable to start a new recording. Other applications already recording". So I go back into Google, disable the hotword detection from any screen, and look and behold, Voice Recorder works again.
I haven't tried any other recording apps yet to see if they have the same conflict, but I intend to shortly. I just figured I'd let others know about the issue. It seems like a huge oversight on Google's part that such a highly anticipated feature would break one of the stock functions on a popular flagship device. Hopefully they push a fix soon, or someone here finds a way around the problem....
Sent from my SM-N900T
Click to expand...
Click to collapse
hey i want to get that on my note 3 how does it work
mrej201 said:
how do you make it work did you get a update
---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------
Click to expand...
Click to collapse
I assume you mean the hotword detection? Google is enabling it randomly, account by account (at least that's my understanding). If you really can't wait, there's an app called 'UnleashTheGoogle' that allows you to enable it via debug/developer options. Google it.
Sent from my SM-N900T
Morningstar said:
I assume you mean the hotword detection? Google is enabling it randomly, account by account (at least that's my understanding). If you really can't wait, there's an app called 'UnleashTheGoogle' that allows you to enable it via debug/developer options. Google it.
Sent from my SM-N900T
Click to expand...
Click to collapse
thanx and yea i want the feature for so long
Yeah, just search for 'unleashthegoogle'. I used it on another device, and it's quite easy and only takes a few seconds, but I don't remember exactly what you have to enable off the top of my head, so search for the apk and the instructions.
Sent from my SM-N900T
Morningstar said:
I assume you mean the hotword detection? Google is enabling it randomly, account by account (at least that's my understanding). If you really can't wait, there's an app called 'UnleashTheGoogle' that allows you to enable it via debug/developer options. Google it.
Sent from my SM-N900T
Click to expand...
Click to collapse
try the app but it wont work
phil.culler said:
Just checked, mine too. Fortunately, I have never had a need to use voice recorder.
Click to expand...
Click to collapse
Hmm, this is interesting (and not good at all).
Did anyone try this with call recording?
One fix I can think of before Google fixes it, have a Tasker / Xposed module that disables Google Search when the whitelisted (recording) apps are running. Can some dev confirm this?
I don't have the update yet and unleashthegoogle doesnt seem to work. So can't test.
mrej201 said:
try the app but it wont work
Click to expand...
Click to collapse
https://plus.google.com/app/basic/stream/z12sczagllb1inism235gtbp1mb2j3qb204
This post describes how to do it. I just did it. Interesting that it disables recording voice. I wonder if it breaks video recording audio...
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 08:45 PM ---------- Previous post was at 08:40 PM ----------
I tested the voice on my video recording and it didn't break that. It works fine. I even said the hot word, okay google, and it was fine. Also, the Google keyboard seems to work fine with dictating words as well. I'm dictating this right now.
To the guy above me that's a really good idea, blacklisting Google during certain apps.
Sent from my SM-N900T using XDA Free mobile app
I just tried a few things, and the only thing I've found that it breaks is the stock Voice Recorder app. Camera audio recording works, two guitar tuner apps I have work, and the three 3rd party voice recording apps I tried all work flawlessly. One of them lets you select which microphone to record from, and all those options work fine as well. I haven't tried with call recording, as it's not something I use, but i would imagine it works fine, since hotword detection is (presumably) disabled during a call.
The Tasker idea is a damn good one, and I may just set something like that up in a while. What I'd like to know now, is if the same problem exists on other Samsung devices, or if it's just the Note 3 that's affected...
Sent from my SM-N900T
Dunno why it breaks it, but if you have root and want an alternative, google now for 3rd party launchers xposed module works great for me and it doesn't break any sound recording.
Sent from my SM-N900T using XDA Free mobile app
Yeah, there's several things I can do as an alternative. Right now I'm just using a different voice recorder; might set up a Tasker profile later.
It's not that big of a deal, really. It's just annoying/surprising/disappointing that such a highly sought-after and anticipated feature breaks some of the core functionality on a high-end, popular, flagship device. It's even worse if the issue exists on all Samsung (Touchwiz) devices, which I'm trying to determine. Google dropped the ball on this one...
Sent from my SM-N900T
There's a minor update to Google Search rolling out. I haven't been able to find a changelog anywhere yet, but I just checked it out, and unfortunately it still breaks Voice Recorder. *sigh*
Sent from my SM-N900T
from the screen- select Apps - google folder - google setting- search & now - turn on google now and follow the instructions
Morningstar said:
I assume you mean the hotword detection? Google is enabling it randomly, account by account (at least that's my understanding). If you really can't wait, there's an app called 'UnleashTheGoogle' that allows you to enable it via debug/developer options. Google it.
Sent from my SM-N900T
Click to expand...
Click to collapse
got mine to work
I turned OK google detection off then went and stared a recording I went to turn OK google detection back on while I was recording went back and stopped it and now when in hit record it works.
sharpjustin18 said:
I turned OK google detection off then went and stared a recording I went to turn OK google detection back on while I was recording went back and stopped it and now when in hit record it works.
Click to expand...
Click to collapse
I just tried that and it didn't work for me. Anyone find a fix for this yet? Or at least a formal bug report somewhere?
sharpjustin18 said:
I turned OK google detection off then went and stared a recording I went to turn OK google detection back on while I was recording went back and stopped it and now when in hit record it works.
Click to expand...
Click to collapse
travipross said:
I just tried that and it didn't work for me. Anyone find a fix for this yet? Or at least a formal bug report somewhere?
Click to expand...
Click to collapse
I just tried the suggestion above and it is working for me now. I have not restarted yet and I am not sure if it will stick, but thought ill pass this along.:good:
DesperateScorpion said:
I just tried the suggestion above and it is working for me now. I have not restarted yet and I am not sure if it will stick, but thought ill pass this along.:good:
Click to expand...
Click to collapse
Thanks for the input. I tried again just to be sure. I turn hotword detection off, start a recording, then turn hotword detection back on during the ongoing recording. The recording will continue until I stop it, but I can't start a new one immediately after.
travipross said:
Thanks for the input. I tried again just to be sure. I turn hotword detection off, start a recording, then turn hotword detection back on during the ongoing recording. The recording will continue until I stop it, but I can't start a new one immediately after.
Click to expand...
Click to collapse
Well, it doesn't stick. After a restart its back to the same issue. Did you try using a third party recorder?
DesperateScorpion said:
Well, it doesn't stick. After a restart its back to the same issue. Did you try using a third party recorder?
Click to expand...
Click to collapse
I haven't tried using a third party recorder, no. My workaround for the time being is to just use the "OK Google from home screen" option in Nova Launcher, as opposed to "OK Google anywhere" in Google Search.
It turns out the Google Search option also distorts hangouts voice calls on some Galaxy S4s so theres more than one reason to avoid it until it gets fixed. Fortunately the home screen detection on Nova Launcher doesn't share these issues.
Related
Its driving me crazy! I open a book and it immediately starts reading it out loud.
I press "stop reading aloud" and it turns off, but when I exit the Books app and get back in its reading aloud again!
I have Talkback turned off in System settings and don't know what else to do...
Lol. No one must use Google Books apparently....
Sent from my NookColor using XDA Premium App
Your phone is lonely. It needs somebody to talk to. Lol.
Sent from my Nexus in Texas.
I use Google Books on my tablet lol. I never use the read aloud feature though.
I have this problem too and find it annoying.
Do you use the Light Flow app to control the front LED? I use this app, and I've read the accessibility access it has (seen in Settings-> Accessibility) seems to cause this bug for whatever reason. I haven't tried to reach out to the app developer for comment so I don't know if he's aware or fixing it.
EDIT: I sent an email to the developer to see if he is aware of the issue...
i use google books to read lately, but i didnt even know it had an audio read out loud function. so no i am not having any issues. i just open books and start reading normally with no audio strangeness...
I got a quick response from the Light Flow developer (+1 on that!) and it's a known issue with Android 4.0.
See item # 2 here:
http://www.folioflow.com/ff/page/website/lightflow/pageId/1931
Regarding the workaround, my phone already showed "not allowed" for web scripts, but I tried selecting it again. Time will tell if it did anything...
Kidd_Funkadelic said:
I got a quick response from the Light Flow developer (+1 on that!) and it's a known issue with Android 4.0.
See item # 2 here:
http://www.folioflow.com/ff/page/website/lightflow/pageId/1931
Regarding the workaround, my phone already showed "not allowed" for web scripts, but I tried selecting it again. Time will tell if it did anything...
Click to expand...
Click to collapse
Wow, you're the man!!! Thanks for the heads up and for looking into this and contacting the Light Flow developer.
I do indeed use Light Flow - my phone was set to "not allowed" for web scripts as well...I selected it again as you did and will report back after I get home from work if it stops reading out loud.
bekyndnunwind said:
Wow, you're the man!!! Thanks for the heads up and for looking into this and contacting the Light Flow developer.
I do indeed use Light Flow - my phone was set to "not allowed" for web scripts as well...I selected it again as you did and will report back after I get home from work if it stops reading out loud.
Click to expand...
Click to collapse
Yeah my fingers are crossed too. Keep in mind that I think it takes a reboot for the problem to re-occur anyway...
Well, I starred this bug report on Google Code, and followed one of their suggestions - I disabled light flow in the accessibility settings (and light flow still works), and this stopped the 'read aloud' from happening. Not sure why enabling light flow in accessibility is necessary in the first place but glad it seems to have fixed things.
I really like the Moto X is the "always listening" feature.
I finally figured out how to implement such a feature on the Note 3, and thought I share.
Basically, while the screen is off, say "Hi, Galaxy". S-Voice will activate. S-Voice sucks. So, ask S-Voice to kindly "Open Google Search".
Once Google Search/Now is opened, you can use it fully. Just say "Okay, Google" before every command.
If you haven't done it already, you'll need to update to the latest Google Search/Now to be able to issue continuous "Okay, Google" commands.
Side note: there's Open Mic+ app (awesome app). However, it doesn't have always listening while screen is off yet. So, use S-Voice to wake up the phone from screen off.
Still trying to figure out a way to automatically jump straight into Google Now upon "Hi, Galaxy" command. Any idea?
If you use Tasker this is a very simple profile to implement. Just make a profile for whenever "s-voice" opens to auto open "voice search".
There is a small delay in between, but it's much more streamlined than saying "hi Galaxy" and then "Ok Google" after.
I'm fairly sure there are other automation apps out there that can do the same thing, maybe even free, but I use Tasker myself.
Hope that helps
Lol. Is there a way to do hi galaxy, ok google, how about you Jarvis?
Sent from my SM-N9005
cazwell220 said:
If you use Tasker this is a very simple profile to implement. Just make a profile for whenever "s-voice" opens to auto open "voice search".
There is a small delay in between, but it's much more streamlined than saying "hi Galaxy" and then "Ok Google" after.
I'm fairly sure there are other automation apps out there that can do the same thing, maybe even free, but I use Tasker myself.
Hope that helps
Click to expand...
Click to collapse
Thank you. That's a simple and elegant solution.
Sent from my SM-N900T using Tapatalk
Have you noticed any extra battery drain?
Sent from my SM-N900T using Tapatalk
cazwell220 said:
If you use Tasker this is a very simple profile to implement. Just make a profile for whenever "s-voice" opens to auto open "voice search".
There is a small delay in between, but it's much more streamlined than saying "hi Galaxy" and then "Ok Google" after.
I'm fairly sure there are other automation apps out there that can do the same thing, maybe even free, but I use Tasker myself.
Hope that helps
Click to expand...
Click to collapse
Thanks this works quite well for me in particular in my car as s voice doesn't work well with my cars Bluetooth however google voice search does. So I have Tasker enable it when I'm connected to my cars Bluetooth. But I still prefer s voice when I'm not in my car so I have Tasker set up to go back to svoice when my phone disconnects from my car. Tasker is awesome.
Sent from my SM-N900T using Tapatalk
---------- Post added at 02:07 AM ---------- Previous post was at 02:06 AM ----------
busab said:
Have you noticed any extra battery drain?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I can't tell the difference.
Sent from my SM-N900T using Tapatalk
If qualcomm implemented it well the battery drain shouldnt be noticeable. Haven't heard anybody complain about always on s voice draining battery.
sent from my sm-9005.
get "open mic" from the play store...
Mangani001 said:
get "open mic" from the play store...
Click to expand...
Click to collapse
It holds a wake lock and doesn't allow device to sleep
Sent from my SM-N900V using xda app-developers app
I would like to resurrect this old thread and see if there has been any further development on this. I would like to have my phone automatically open google voice search with the "Hi Galaxy" command and I have tried some of these apps (not Tasker yet) but they have not worked consistently. Sometimes they work and sometimes not. And also sometimes I get a wakelock that drains my battery and if I greenify or disable wakelock for that app it doesn't work.
There has to be a way for a Dev to make it work like stock. Any ideas out there?
Should be an easy way with a rooted phone.
http://www.cnet.com/how-to/start-google-now-with-your-voice-on-the-galaxy-note-3/
Sent from my SM-N900T using xda app-developers app
This worked but like you sometimes it was hit or miss. I haven't tried it in a few weeks though.
Just in case someone else runs into this issue.
My alarm (default app) would get snoozed immideately after going off, thus becoming useless.
I have discovered that if I disable the "OK Google" detection from any screen option, the alarm functions fine.
Hope it helps someone not to miss any important appointments.
The ok google from any screen feature also kills the video camera. You get a "can not record while on a call" warning.
GRRemlin said:
Just in case someone else runs into this issue.
My alarm (default app) would get snoozed immideately after going off, thus becoming useless.
I have discovered that if I disable the "OK Google" detection from any screen option, the alarm functions fine.
Hope it helps someone not to miss any important appointments.
Click to expand...
Click to collapse
Glad I happened to see this post ... For the past week I've been trying to figure out what was automatically dismissing my alarm ... Uninstalled and reinstalled so many apps and xposed modules and never figured it out. Thanks!
Sent from my LG-LS980 using XDA Premium 4 mobile app
iDoc21 said:
Glad I happened to see this post ... For the past week I've been trying to figure out what was automatically dismissing my alarm ... Uninstalled and reinstalled so many apps and xposed modules and never figured it out. Thanks!
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gald I could help. Also, at least I know that it's not only happening on my phone.
I wonder if the bug has to be submitted to Google or LG?
GRRemlin said:
Gald I could help. Also, at least I know that it's not only happening on my phone.
I wonder if the bug has to be submitted to Google or LG?
Click to expand...
Click to collapse
Running in to a similar issue. But instead of the alarm snoozing. I get a pop up message stating "Alarm/Clock has stopped working" and then a flashing notification light. The problem started just this week. I uninstalled the latest Google update and also turned off OK Google" detection from any screen, but that doesn't seem to have had any impact. Odd that I've had no problems with Google Now up until this past Tuesday.
dafever said:
Running in to a similar issue. But instead of the alarm snoozing. I get a pop up message stating "Alarm/Clock has stopped working" and then a flashing notification light. The problem started just this week. I uninstalled the latest Google update and also turned off OK Google" detection from any screen, but that doesn't seem to have had any impact. Odd that I've had no problems with Google Now up until this past Tuesday.
Click to expand...
Click to collapse
I was unable to replicate your issue. I only get the "Snoozed" notification.
However, I moved to Timely alarm app since and it works just fine.
Thank you for the response. I was hoping I'd be able to figure out what's the issue is and continue to use the stock app. But looks like I'll have look into a third-party app.
Thanks again.
dafever said:
Thank you for the response. I was hoping I'd be able to figure out what's the issue is and continue to use the stock app. But looks like I'll have look into a third-party app.
Thanks again.
Click to expand...
Click to collapse
The recent Google Search update seems to have fixed my issue.
Is this working for people? It simply doesn't activate for me even after setting it up.
I used it earlier without taking phone out of my pocket and had no issues.
Yes and its working great for me. Make sure all the Google now sliders are on in Google now settings.
It works for me as long as I talk a certain way. So maybe you need to retrain multiple times so it learns how you speak with both high and low pitch.
Sent from my Nexus 6 using Tapatalk
DOBBY0 said:
It works for me as long as I talk a certain way. So maybe you need to retrain multiple times so it learns how you speak with both high and low pitch.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It works 100% of the time for me when the screen is on, never screen off or locked. Ive retrained, toggled on and off the switch, etc. Any ideas? Could there be some battery saving setting turned on for a certain app impacting this?
EDIT: Tried turning off battery optimization for Google App and no difference.
km8j said:
It works 100% of the time for me when the screen is on, never screen off or locked. Ive retrained, toggled on and off the switch, etc. Any ideas? Could there be some battery saving setting turned on for a certain app impacting this?
EDIT: Tried turning off battery optimization for Google App and no difference.
Click to expand...
Click to collapse
I think I know! If your secure and have a lock on then you need to go into smart lock and setup trusted voice!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 5X using Tapatalk
Trusted voice just brings you right to the Ok Google settings. No matter what I do in there though, Trusted Voice never switches to "On".
I know you have to retrain in Google setting through Google voice I think. That's what I did originally and it works
Sent from my Nexus 5X using Tapatalk
DOBBY0 said:
I know you have to retrain in Google setting through Google voice I think. That's what I did originally and it works
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Trusted voice never turns on for me though.
km8j said:
Trusted voice never turns on for me though.
Click to expand...
Click to collapse
OK so try shutting it off in Google settings. And then take security off phone. Not setup security again then tap smart lock and then trusted voice. It will take you to Google app and switch on all things. Then retrain voice and then go back into smart lock settings make sure trusted voice is on and then you just need to click phone screen off and say okay Google exactly as you did during training.
Sent from my Nexus 5X using Tapatalk
You are a genius. I removed screen security and ok google worked fine. Then set a password and then trusted voice. That now works with the screen off. I never got to the trusted voice disclaimer before this. Thanks!
Question though. The warning says someone could get into my phone with a similar voice. Is it actually unlocking the handset or just allowing this person "using my voice" to conduct certain Google Now actions?
EDIT: What is super weird is the option under OK Google Detection has change. It now says trusted voice instead of "personalized results"... This is super weird though because the OK Google does not even truly unlock the phone and there is no personalized results. I cannot do anything while the phone is locked. It beeps, I give my command but then it waits for a password. Found out why the option is changed but not why it doesn't work right: https://support.google.com/websearch/answer/186263?hl=en
It actually unlocks the phone, but I mean that shouldn't be much of a security hazard. Also I think the not unlocking thing might be caused by on body detection? I haven't solved it yet. I'll try it though
Sent from my Nexus 5X using Tapatalk
DOBBY0 said:
It actually unlocks the phone, but I mean that shouldn't be much of a security hazard. Also I think the not unlocking thing might be caused by on body detection? I haven't solved it yet. I'll try it though
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Mine definitely does not unlock the phone nor is it of any use when the screen is locked. What should happen is the way Motorola implemented it. With the screen locked, I can get weather, make calls, send messages, etc. but cannot retrieve any information nor can I gain full access.
Now the next question... is there an OK GOOGLE command to turn the screen off? That would be killer.
Not sure what the value of that is but I still cannot get mine to work properly
Sent from my Nexus 5X using Tapatalk
DOBBY0 - Thank you for this suggestion. I had everything set up but every time I gave Google a command she would tell me she couldn't do it while my phone was locked. Starting over the way you suggested now works!
Sent from my Nexus 5X using XDA Premium HD app
How's your battery life after enabling this feature? do you still get about 3.5-4 hours screen on time? or does it suck the battery?
I almost got 5hrs SOT and I have every feature turned on with this phone except for ambient display. The "OK google" with the screen off and unplugged works better than my moto X² PE did.
I honestly forgot that they allowed this feature. I set it up but like said before I would rather not allow my phone to be completely unlocked by voice. The feature becomes less cool if I have to unlock it to view Google searches.
km8j said:
Question though. The warning says someone could get into my phone with a similar voice. Is it actually unlocking the handset or just allowing this person "using my voice" to conduct certain Google Now actions?
Click to expand...
Click to collapse
Say "OK Google, open app root browser" Now I can see everything on your phone if I have a voice similar to yours.
Is it only me, or someone else is having issue with running Google assistant?
Tried reset voice commands, clear data for Google app, reinstal Google assistant, I followed help on Google site, nothing is working.
When I run assistant from app it is working, but no reaction on command "ok Google"
Globus.gd said:
Is it only me, or someone else is having issue with running Google assistant?
Tried reset voice commands, clear data for Google app, reinstal Google assistant, I followed help on Google site, nothing is working.
When I run assistant from app it is working, but no reaction on command "ok Google"
Click to expand...
Click to collapse
Same here! It worked the first 1 or 2 days but not anymore
Sent from my HD1903 using Tapatalk
rmaathuis said:
Same here! It worked the first 1 or 2 days but not anymore
Sent from my HD1903 using Tapatalk
Click to expand...
Click to collapse
Working just fine here on 10.04
Try to go in assistants app battery optimization settings and change it to don't optimize. I'm thinking it's the one plus software trying to optimize battery, so assistant is not running in the background and picking up the ok Google
Done this also and it didn't help
Same issue here. 10.0.4. "Tried Everything" No solution. Works once after reboot. Then nothing. Works with the app. The rest of the time, not responding with voice command ok google.
Have given up on it since 2-3 Android generations, I hardly even use the google assistant
bhavstech said:
Have given up on it since 2-3 Android generations, I hardly even use the google assistant
Click to expand...
Click to collapse
We are all glad that You have shared with us this information
Globus.gd said:
Is it only me, or someone else is having issue with running Google assistant?
Tried reset voice commands, clear data for Google app, reinstal Google assistant, I followed help on Google site, nothing is working.
When I run assistant from app it is working, but no reaction on command "ok Google"
Click to expand...
Click to collapse
I couldn't even configure Android Assistant. I had to go to the Google app in the PlayStore, uninstall updates and only then was I able to enable the assistant. After the Google app auto-updated, the assistant settings remained enabled. You may have to uninstall the updates as well.
Globus.gd said:
We are all glad that You have shared with us this information
Click to expand...
Click to collapse
Matter of point being, the google assistant integration iteself has issues , if you could make it work thats great but it would most likely be temporary
Happened to me also. Installing beta app helped me. Make sure battery saver is turned off.
You need to configure google assistant for that. Long press the home button and once the assistant pops up, swipe up to configure the settings and let the assistant recognize your voice. Worked for me.
I've tried a lot of recommendations in here and still can't get "Ok Google" or "Hey Google" to work. It works only when I manually open the assistant from de bottom corner up but it doesn't work with screen off or outside the assistant activated bar.
Google home > Assistant > at the end of this screen, select your phone > activate "Voice Match"
memrom said:
Google home > Assistant > at the end of this screen, select your phone > activate "Voice Match"
Click to expand...
Click to collapse
It's on, retrained voice and it still doesn't work.
Try to disabling installed apps. After disabling every app try to say "ok Google".
Hope You will find app which is causing problems
Do you have an app installed which simulates a led notification? Like NotifyBuddy, LEDBlinker etc Uninstall that one and try again.
Sent from my HD1903 using Tapatalk
rmaathuis said:
Do you have an app installed which simulates a led notification? Like NotifyBuddy, LEDBlinker etc Uninstall that one and try again.
Sent from my HD1903 using Tapatalk
Click to expand...
Click to collapse
This was it, I had the "Shake Light" too shake the screen and turn on the flashlight, uninstalled it and the "Ok google" worked again. Thank you very much!
hectorviov said:
This was it, I had the "Shake Light" too shake the screen and turn on the flashlight, uninstalled it and the "Ok google" worked again. Thank you very much!
Click to expand...
Click to collapse
I literally don't have any apps installed other than google apps and XDA.
Still get the "google assistant unavailable" every so often when I try engage. So very frustrating. Anyone else have any advice on how to get it working reliably?
rmaathuis said:
Do you have an app installed which simulates a led notification? Like NotifyBuddy, LEDBlinker etc Uninstall that one and try again.
Sent from my HD1903 using Tapatalk
Click to expand...
Click to collapse
I noticed the same OK Google issue with Notify Buddy installed, I just uninstalled it and OK Google now works again. Maybe there's a setting in Notify Buddy that can help use it without interfering with the Assistant function?
---------- Post added at 03:52 PM ---------- Previous post was at 03:33 PM ----------
Found this, more 7T owners among the affected app users.
https://forum.xda-developers.com/oneplus-6t/themes/app-amoled-notification-light-t3943715