Related
100% stock verizon s3. not rooted , & barley any thing on it.
Today it started to read practically everything to me....mostly facebook, but also texts, & calls.
Driving mode is off,
talk back is off
i dont have Lightflow installed.
im confused. the ONLY thing that i did do today was enable Driving mode to test it out, the i turned it off. (via the notification area, as well as enabled then disabled it via the settings menu...)
anyone have any ideas WTF is going on?> also a reboot did not fix it.
My Nexus 7 did the same thing to, but it stopped on its own
enohand said:
100% stock verizon s3. not rooted , & barley any thing on it.
Today it started to read practically everything to me....mostly facebook, but also texts, & calls.
Driving mode is off,
talk back is off
i dont have Lightflow installed.
im confused. the ONLY thing that i did do today was enable Driving mode to test it out, the i turned it off. (via the notification area, as well as enabled then disabled it via the settings menu...)
anyone have any ideas WTF is going on?> also a reboot did not fix it.
My Nexus 7 did the same thing to, but it stopped on its own
Click to expand...
Click to collapse
no one has any idea how to turn this off?
its now also reading everything from the XDA app
Go into settings, accessability, and turn off text to speech feature
I think I just figured out, the number one tool to own if you're going to own a Samsung phone is a sense of humor.
I'm sorry OP, but your thread cracks me up and every time I read your post
no one has any idea how to turn this off?
its now also reading everything from the XDA app
Click to expand...
Click to collapse
I LOL some more. I'm giving this **** 5 stars.
I should not have to turn it off. Then is mostly a circumvent and not a solution
Also I am not sure what is so entertaining about the post
Sent from my Nexus 7 using xda app-developers app
Unless you are visually impaired or need total hands free operation Text to Speech should be disabled.
enohand said:
100% stock verizon s3. not rooted , & barley any thing on it.
Today it started to read practically everything to me....mostly facebook, but also texts, & calls.
Driving mode is off,
talk back is off
i dont have Lightflow installed.
im confused. the ONLY thing that i did do today was enable Driving mode to test it out, the i turned it off. (via the notification area, as well as enabled then disabled it via the settings menu...)
anyone have any ideas WTF is going on?> also a reboot did not fix it.
My Nexus 7 did the same thing to, but it stopped on its own
Click to expand...
Click to collapse
i installed LED flow which needed to have some accessibility options enabled, and after that my voice started too. i never did check the box to turn it on, but it did it on its own.
i uninstalled LED flow as i did not like it, and everything else returned to normal.
When you click a folder on your home screen does it say "The folder is open" and/or "The folder is closed"? If it does it means you have something in accessibility turned on. I use tasker. Some of the features requires tasker accessibility turned on. When I do that I get the annoying text to speech notifications like that. Only way to turn them off is to have nothing all at enabled in accessibility. I dont have to disable tts in language and input, so I can still use google now, eva voice assistant and astrid still reads me my reminders. But I cannot use any tasker task that requires accessibility, without hearing" the folder is open. The folder is closed" etc etc etc.
sfetaz said:
When you click a folder on your home screen does it say "The folder is open" and/or "The folder is closed"? If it does it means you have something in accessibility turned on. I use tasker. Some of the features requires tasker accessibility turned on. When I do that I get the annoying text to speech notifications like that. Only way to turn them off is to have nothing all at enabled in accessibility. I dont have to disable tts in language and input, so I can still use google now, eva voice assistant and astrid still reads me my reminders. But I cannot use any tasker task that requires accessibility, without hearing" the folder is open. The folder is closed" etc etc etc.
Click to expand...
Click to collapse
That's what it was saying to me. It was annoying. Like I said I went in and removed led flow, reset all the accessibility settings and it's silent now.
Sent from my SCH-I535 using xda app-developers app
Turn off driving mode. Or go to setting>text to speech> touch the word driving mode> uncheck what you do not want for S3 to speak
Sent from my SCH-I535 using xda app-developers app
Is anyone else having a problem with their touch less controls. I can say OK google now and the phone will make a noise. But when google now opens it says " Sorry can't reach google right now ". Same goes for any other kind of voice driven function , texting by voice in the stock messaging app, search in the maps app. They all hive me the same reply. I've checked all my setting. Im at a complete loss
Rooted & unlocked. Otherwise stock .
Have you updated your google search app?
I used HOM and fxz'd my phone . The google vioce app now works but the Moto touchless controls still don't
Google Now needs an active internet connection.
I have tried everything. I've spoken to Verizon who then refered me to Moto. Who had clear partition caches to no avail. Any and all voice recognition on my phone has ceased to work. Sometimes Google will open up to say " Can't reach google at the moment ". However if I manually open the search box Google now and all my cards are there. If I then hit the microphone icon It will again say "Can't reach google at the moment ". I'm at my wits end here. This will happen weather Im using my wifi or 4G signal.
I've fxz'd and that didn't work. I will entertain any and all ideas.
Any resolution with the voice control problem? I am having the same problem with my Droid Maxx running 4.4.4. It just started this week and I have reset it, but that didn't solve the problem. I figured the old apps wouldn't have the same problem as the newer versions. Guess I was wrong. I am trying Verizon Repair assistant to see what it can do for me. We will see.
tombaldwin6 said:
I have tried everything. I've spoken to Verizon who then refered me to Moto. Who had clear partition caches to no avail. Any and all voice recognition on my phone has ceased to work. Sometimes Google will open up to say " Can't reach google at the moment ". However if I manually open the search box Google now and all my cards are there. If I then hit the microphone icon It will again say "Can't reach google at the moment ". I'm at my wits end here. This will happen weather Im using my wifi or 4G signal.
I've fxz'd and that didn't work. I will entertain any and all ideas.
Click to expand...
Click to collapse
Post your touchless/moto voice version from settings/app. They are interchangeable in name now. If you have the newest you must uninstall updates & retrain touchless voice.
I ended up FDRing the phone twice. The first time I let my apps reload automatically and my touchless control still didn't work. So I did it again, but the time I reloaded each app individually. Testing the touchless controls between each install. I ended up reinstalling every app but the one I thought was the culprit. This is no knock on the app I used it and I wish I could put it back in. Elixor2 has a setting where you can control and or turn on/off each of the sensors including the microphone. When I was having the problem I would go into elixir and see that my microphone was off and inaccessible. With out elixor2 on my phone I've had no more problems.
I have done the same type thing as Tom Baldwin6. I "redid" my phone using the Verizon software installation assistant and did a "repair". I then rooted it using TWRP, and started adding stuff. I have not had the problem again as of now.
I was thinking it was the experimental app that was allowing me to mirror my phone using Chromecast, but I am using version 4 of that app and it is still working. I used version 5 before.
My phone hasn't had a problem again after 24 hours, but as I continue to add apps and check, eventually I may find another culprit. I will post here if I get it tracked down.
jmaclean62 said:
I have done the same type thing as Tom Baldwin6. I "redid" my phone using the Verizon software installation assistant and did a "repair". I then rooted it using TWRP, and started adding stuff. I have not had the problem again as of now.
I was thinking it was the experimental app that was allowing me to mirror my phone using Chromecast, but I am using version 4 of that app and it is still working. I used version 5 before.
My phone hasn't had a problem again after 24 hours, but as I continue to add apps and check, eventually I may find another culprit. I will post here if I get it tracked down.
Click to expand...
Click to collapse
I suspected the the chromecast mirror as well It was one of the 1st apps I reloaded. But it wasn't it. I'm certain it has something to do with the microphone
Same issue here. Been a week since I FDR'd (NOT rooted or unlocked). The apps restored, touchless control no longer allows to register voice (does not recognize sound ONLY for Touchless Control).
Saw that Touchless Control has been updated to "Moto Voice",
Uninstalled Moto Voice to return to previous version. No luck. Again updated to Moto Voice.
Wipe Cache Partition, no luck.
I've installed Open Mic+, which works for the most part (never got it to work from lock screen)
Stopped Open Mic+.
I then went in Language & input ---> Google voice typing settings (or Voice Search), disabled/re-enabled Speech Output. Clicked on "Ok Google Detection" and did the standard Google Now/OK Google setup again.
Went back to Touchless Control and this time it recognized my voice and allowed me to setup Touchless Control and all is working again.
Although the new "Moto Voice" on the "1st Gen [2013] Ultra/Maxx etc.., you cannot customize the "OK Google Now" at this time (coming feature for Gen 1's).
Rebooting now to ensure operation. Will updated/verify 'fix' in a moment.
Upon restart, my Open Mic+ restarted, and the "OK Google Now" was not working. Stopped the Open Mic+ and touchless control working again. Went in and re-trained to verify. Unintalling Open Mic+ and rebooting now.
Now again working 100%, now just awaiting Moto Voice update to allow additional features for 1st gen's.
i have got mine working gain too. I still haven't reinstalled everything though. I will reinstall x tether this weekend. I am hoping that it isn't cuseing any problems. Can't imagine why it would, but we will see. Do you guys have it installed?
Did you happen to open the Google app, scroll to the bottom, tap the three dot menu control on the bottom right, tap settings, voice, OK Google detection, and turn off the setting "On any screen"?
If that is on, I think it block touchless controls, maddeningly. I know it stops the Assist driving feature from being able to capture voice when it prompts you.
doogald said:
Did you happen to open the Google app, scroll to the bottom, tap the three dot menu control on the bottom right, tap settings, voice, OK Google detection, and turn off the setting "On any screen"?
If that is on, I think it block touchless controls, maddeningly. I know it stops the Assist driving feature from being able to capture voice when it prompts you.
Click to expand...
Click to collapse
I set "on any screen" option and touchless controls does work from any screen, needing only "OK Google".
I am not driving now but will check Assist in about 2 hours.
iamtek7 said:
I set "on any screen" option and touchless controls does work from any screen, needing only "OK Google".
I am not driving now but will check Assist in about 2 hours.
Click to expand...
Click to collapse
I don't think that's touchless controls - I think that's the Google search app listening and responding to ok Google , and, with that setting on, that's probably why you couldn't train in the Touchless controls settings (though I haven't tested that myself, since my phone is already trained.)
I know it's a subtle difference, but Touchless controls is a front end to google search most of the time, though sometimes it does its own thing (ok Google now, what's up?)
I do know that the any screen setting screws up some other things, like preventing the camera app from capturing video (because the microphone is in use).
I'm all set now. If this is still an issue for anyone, let me know.
Sent from my XT1080 Developer Edition using Tapatalk
I just noticed that my phone will not recognize the "OK Google" Command. I've tried trainging it by saying "OK Google" 3 tims but even then, the phone does hear me. It will hear me and recognize my words ok if i press the microphone button first and then speak. Anyone else have the same issue?
brandypuff said:
I just noticed that my phone will not recognize the "OK Google" Command. I've tried trainging it by saying "OK Google" 3 tims but even then, the phone does hear me. It will hear me and recognize my words ok if i press the microphone button first and then speak. Anyone else have the same issue?
Click to expand...
Click to collapse
Nop, works for me even on BT. Maybe you have it disabled?
so what should I do? under the screen "OK Google" detection, it shows, From the Google App=on, but the other options are greyed out. When I turn on From Any Screen, it asks me to Just say OK Google three times, and it's listening, but it never recognizes my voice even if I say it 100 times. But, I can do a voice search OK in I manually click the google microphone button.
I have the same problem. Recently bought an Idol 3 5.5, and cannot get 'OK Google' to work. Any amount of 'OK Google' commands in different accents (and by different people) are useless. I can do voice search by clicking the microphone button on Google search app. Not sure what is the problem here. How do I make sure this feature is not disabled on my phone?
Same issue here as well. It "will" work if you open the Google App first. It then recognizes commands without having to select the microphone. But yes, without first opening the google app, it does not work.
you have to add english as primary language in google settings (beside the language you use). Works for me (i am from Europe). It also works from any screen.
There is something wrong with it on the Idol 3. If you boot into safe mode, you can enable it but only from safe mode. I did this and it workd for awhile but then something disabled it again. Very Frustrating. Unfortunately, I doubt we will get any fixes from Alcatel. BTW, to boot into safe mode, press the power button and then long press on either restart or power off. I can't remember which.
like i said it works well on my and many other devices, so you have to set it right.
DallasCZ said:
you have to add english as primary language in google settings (beside the language you use). Works for me (i am from Europe). It also works from any screen.
Click to expand...
Click to collapse
Yes, it works from any screen as long as you have "previously" opened the "Google App", and, it's still running in the background.
For instance, if I cycle my phones power, and come to the home screen, "Ok Google" will not work, it simply doesn't work. But, if I open the "Google App" after a reboot, and then go back to my home screen, or any screen, it will work. You have to open that "Google App" first, or it doesn't recognize any command, because it's not "listening" / running in the background. If I "close" all running apps, which you should be doing quite often, "Ok Google" will not work, until I again open that "Google App".
The phone should "Always" be listening (provided you want to use this feature), without the need to run the "Google App" first, but that's simply not the case. To me it's just poor implementation, because it forces you to always make sure the "Google App" is running, or hit the microphone. This shouldn't be necessary. It should just work from the moment the phone has booted up (again, if you want this feature), but it doesn't.
Better implementation would have been a "service" you either turn on, or off, under settings, so it's always running (from the moment the phones powered up), or it's not running.
I hope that's clear, and makes sense?
Makes sense that that's what happening to me as well. I recall it worked just fine previously. I wonder if the recent updates did something to that interface.
I'm having the same problem after doing a factory reset and reloading everything.
It was working fine before the reset and since it will only work if I've recently opened the Google app. I've checked all of the settings multiple times, uninstalled/reinstalled the Google app, and it's still occurring.
Has anyone found any possible solutions?
(Not sure if this is anyhow related, but before the reset the flip to mute and snooze gestures didn't work at all. Since the reset, they work perfectly.)
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I have the same issue, the only solution I have is to disable the ok Google option as you said.
xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I think problem should be addressed to Google first cause of Google now, or Huawei, second, cause the service is continuosly listening for "Ok google" activation, but it should stop or, better, stand-by, so the
microphone can be used by the concurrent app, when finished, service automatically restarted. This behaviour doesn't require any error or warning pop-up when happens.
Even I like to know, if anyone knows how to submit issues directly to Huawei/Honor.
Just started having the same issue with the latest Google app update, but I can't even disable the "Ok Google" detection. It just turns itself back on immediately. Here's a screencap of my dilemma:
https://gfycat.com/FancyTepidHornedviper
@Xichael: Tap on "Delete Voice Model" and you can turn it off permanently. This is, as far as I know, the only way other than deleting / deactivating the Google App or possibly tweaking certain permissions. Once you delete the voice model, the "Ok Google" should still work within the app or when long pressing the home button.
@xghost1 Yes, deactivating "Ok Google" on any screen by deleting the voice model is so far the only solution that works permanently. There is currently no way to have "Ok Google" everywhere while also not getting that error message. We'll just have to wait for a fix. I think this only applies to the current "Google Assistant" though. It might be possible to go back to an older version of "Google Now" where "Ok Google" on any screen still works while not getting that error.
Thanks, that solves it for me. I can live without "Ok Google", but that popup was intolerable.
xichael said:
Just started having the same issue with the latest Google app update, but I can't even disable the "Ok Google" detection. It just turns itself back on immediately. Here's a screencap of my dilemma:
https://gfycat.com/FancyTepidHornedviper
Click to expand...
Click to collapse
Remove your trained voice and then "Ok Google" detection on any screen will then turn off. That is the only way I found to disable it.
Sent from my FRD-L04 using Tapatalk
xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I was having similar problem and it's gone after i denied permission for microphone...before it was turning itself and made me crazy...I hope it will help You with this issue
famanfwppc said:
I think problem should be addressed to Google first cause of Google now, or Huawei, second,
Click to expand...
Click to collapse
Other Nougat phones with OK Google active don't have this issue. So I'd say Huawei would be the first to be addressed.
It's hard to know who to blame on this one. When Googling, it looks like it's only a problem on Huawei devices. That said, when I try to disable all-screen OK Google detection, the setting won't stick and always reverts. That sounds like a Google issue. I had to delete the voice model.
Likely it's some combination of both.
I called the service hotline last week and they said it was the update to Google app that was screwing things up. For me it was creating a toast message in my camera app when I would record video or use voice activated shutter control for still pictures. He told me to revoke permissions in the Google app for the microphone, or revert to an older version of the app. I'm assuming pre Google Assistant. I haven't tried that option yet.
Turning off all-screen 'OK Google' detection is likely the best option, especially because you can map your Smart Key to Voice Search and get nearly the same functionality. The only impaired function is if you hands-free dock in your car, but even then I rarely use Assistant anyway in that setting.
Thank you all for your comments and replies.
For your information I was receiving this error even without Google Assistant, since I was using my phone with Portuguese language. I tried to reset and changed it to English, now I have Google Assistante working but the error still remains. So like it was already mentioned my best gues is to associate the problem with Google App and Huawei Software.
To be sure it would be good if anyone could test the issue on a Custom Rom.
Thanks
Go into Playstore and chose to uninstal Google app. It will roll back to a version before Google Assistant and your phone will act as normal, you just don't have assistant. I even noticed an issue prior to this while using Shazam to identify a song I was listening to.
Background processes
"com.google.android.googlequicksearchbox:interactor" is a common Android process.
Huawei is at fault for this bug.
I can confirm only Huawei handsets are experiencing this annoying bug.
Huawei also has their own voice assisted application/processes I.e. Quick calling. If you disable all Huawei voice assisted features, this most likely will solve the problem as well.
It seems Huawei voice assisted processes and Google voice assisted processes cannot be active at the same time without the user seeing this message. If you prefer "Ok Google" and other Google voice assisted processes then try disabling Huawei voice software first.
Go to settings and search "voice" then select "voice control" turn off all Huawei voice assisted processes.
Hopefully this helps.
I guess if I want to disable OK Google and use Huawei's voice assistant instead, I can be away from the evil Google. But what does Huawei voice assistant do? I only found "find my phone" and very few other functions. While from what I heard, in China where Google services are totally disabled, Huawei's voice assistant can do a lot more things. Where are they?
Turning off the Huiwei voice facilities does not work. Still get same error.
To get rid of the box you have to turn off "ok Google" detection from any screen.
If it it turns itself back on (a Google bug) you have to delete the voice model.
To use the assistant you'll have to hold down the home button.
The interactor box is just another big of many that Huawei hasn't bothered patching. Huawei clearly doesn't care. Last time buying a device from them.
SolarisSixth said:
To get rid of the box you have to turn off "ok Google" detection from any screen.
If it it turns itself back on (a Google bug) you have to delete the voice model.
To use the assistant you'll have to hold down the home button.
The interactor box is just another big of many that Huawei hasn't bothered patching. Huawei clearly doesn't care. Last time buying a device from them.
Click to expand...
Click to collapse
Yes. Get that you have to turn off OK Google.
The trouble is, I don't *want* to turn it off.
Very annoying bug for sure.
Sent from my FRD-L09 using Tapatalk
ckckckckck said:
Yes. Get that you have to turn off OK Google.
The trouble is, I don't *want* to turn it off.
Very annoying bug for sure.
Click to expand...
Click to collapse
I totally agree, but that's what we get for giving Huawei money, clearly they don't care.
I know it's not supposed to work from a locked phone, but I can't get it to work with the screen on even. Any clues what could be wrong? I do have the bxactions app installed and using the Bixby button for Google now, but I doubt think that's the culprit. I've also postponed the first tmobile system update but it worked when I first got the phone. Suggestions?
Sent from my SM-G955U using Tapatalk
Mine suddenly stopped working too. It could be the recent google app update that broke it, I remember getting that update. I retrained my voice again and so far so good.
Same problem here. Restarting seems to fix mine for awhile but something is causing it to glitch out and stop working.
Edit: seems to stop working whenever I open the camera, then it's stuffed until reboot.
After reinstalling google now working fine
Haven't had any issues with mine, even after the last update. Was using one of the Bye Bixby apps and had the button remapped to flashlight but uninstalled it due to the horrible lag the app produced.
It seems to be a problem with power saving mode. The mic stops working after turning on the power saver mode. Restarting the phone will F fix the problem.
prithivraj said:
It seems to be a problem with power saving mode. The mic stops working after turning on the power saver mode. Restarting the phone will F fix the problem.
Click to expand...
Click to collapse
I do not use power saving mode and still does not work with screen off
Sent from my SM-G955W using Tapatalk
Techvir said:
I do not use power saving mode and still does not work with screen off
Click to expand...
Click to collapse
Sorry . I am not aware of what you are experiencing. I haven't tried that. But while turning on and turning off power saving mode disables ok google detection.
prithivraj said:
Sorry . I am not aware of what you are experiencing. I haven't tried that. But while turning on and turning off power saving mode disables ok google detection.
Click to expand...
Click to collapse
Do u have it working with screen off and no charger connected?
Sent from my SM-G955W using Tapatalk
Techvir said:
Do u have it working with screen off and no charger connected?
Click to expand...
Click to collapse
No. Ok google doesn't work until lock screen is displayed.
is there any update to this?
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?
OK Google not working? Fix:
If you set up "trusted devices" to keep your phone unlocked, that is what stops "ok google" from working. Its been that way since the Galaxy S6. Don't know why they don't fix it?! Go to Settings/Lock Screen and Security/Smart Lock/Trusted Devices. Remove your Trusted Devices and it will work again.
amyjofarrey said:
If you set up "trusted devices" to keep your phone unlocked, that is what stops "ok google" from working. Its been that way since the Galaxy S6. Don't know why they don't fix it?! Go to Settings/Lock Screen and Security/Smart Lock/Trusted Devices. Remove your Trusted Devices and it will work again.
Click to expand...
Click to collapse
Will this make ok Google work when screen is off?
You still have to press the power or home button to wake your device, and then it will unlock it with the "ok google" voice command instead of using the iris, fingerprint, password, pattern, etc.
In my case, Google doesnt work holding the home button for search
Enviado desde mi SM-G955F mediante Tapatalk
Mine works when I retrai the voice model.. but if I use bixby voice it never works again until I retrain... I wonder if the two are conflicting each other. Samsung is probably purposely sabatoging Google assistant. To push bixby. I've only had this issue since the release of bixby voice
I had this problem for a couple of weeks and it was bugging the hell out of me.
Ok Google would work, but it would not speak back to me, just bring up search results.
For me the problem was in languages.
I'm in the UK and no matter how many times I set the language to English as default, the damn phone would constantly show Settings>Google>Search>Voice: as "English (South Africa)"
But in Settings>Google>Search>Search Language it would show as what it should be, which is "English (UK)"
Anyway, basically what I did was clear cache and data in apps tab, then set my S8 Plus as pictured below.....but obviously choose your own language and make sure BOTH show the same language....default and the other. (see pics)
Also click 'Ok Google detection' and select 'Retrain voice model' (after the cache wipe etc of course and after you made sure both screens say same language.
Select Say 'ok google' any time.
plus, I selected trusted voice, so also unlock screen too.
if your settings look like mine in the screenshots.....should work.
Matt
---------- Post added at 06:36 PM ---------- Previous post was at 06:31 PM ----------
Also, go to settings>Accessibility>Text-to-speech and make sure Default language is the same as on the other screens.
That's what sorted it all for me anyway....
Ok Google works fine for me as long as the phone isn't being charged. If it's being charged, it is as if my mic is disabled.
Sent from my SM-G955U1 using Tapatalk
Here are some quick things to try that have helped me:
1) Restart your phone, its likely that going into high-battery saving mode disables mic and a lot of settings.
2) Remove trusted devices.
3) Reinstall and Uninstall Google
Ok so this is really annoying. On my lg g6, the phone can be locked and screen off. I can say ok google without touching the phone and it will unlock and be ready for my voice command. I am not get my s8 to do that. Ok google only works after physically unlocked. Then when i can get to open with ok google my daily briefing will not work no matter how I ask for it.