Related
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
danlo said:
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
Click to expand...
Click to collapse
Were you using headphones that day? I've seen this issue, and I think it's an audio issue (software). When I had this issue, the speakers didn't work either.
Sent from my Nexus 5 using Tapatalk
I was using my Bluetooth headset but I've been using this pair since day 1. This just started happening yesterday.
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
TJCacher said:
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip!
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
I've had the same issue, but I can add that this is happening with games as well. Specifically, asphalt 8 causes this problem. Obviously, when I'm switching between apps, I wouldn't want to kill an ongoing game or song just to make the hotword work. The HC issue is annoying and I hope there's a fix to always keep it live no matter which apps are in the background...
shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
My hotword detection also suddenly doesn't work. I've toggled the option in google now settings, rebooted, cleared cache, turned off google music... nothing turns it back on.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
didn't help me. can't figure out what is going on. so frustrating.
---------- Post added at 11:12 PM ---------- Previous post was at 10:26 PM ----------
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
gaetawoo said:
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
Click to expand...
Click to collapse
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
TJCacher said:
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes I've talked to them, they know about it and are working on it, but that say it could be an OS issue.. that are trying to figure it out.
This happens to me at least couple times a day. Either Wi-Fi disconnect or a OK Google three I n a row consecutive search. Solution: kill the g search app it will automatically restart and you'll be gtg
Pebble whatsapp notifier causes this same problem. Unchecked it in accessibility and viola! Always listening again..
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
I have the same issue and none of that work for me, it gets stuck with real racing, i force the stop once and it started to work again but minutes later it was hallow again, please help
shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
Are you on stock? I thought this was a result of the new launcher in today's version of cm.
Sent from my Nexus 5 using XDA Premium 4 mobile app
xdapro said:
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
Click to expand...
Click to collapse
I love you dude or dudette I was going balled trying to figure this out, thanks a lot!
I found out that the hot word detection only works on the default launcher. If I add the google search widget on apex launcher, I get the search bar with a hollow mic, and hot word detection does not work.
If I use default launcher I got the full mic and hot word detection works.
Sent from my Nexus 5 using xda app-developers app
So it's happened 2-3 times now since I got the phone...all of the sudden voice input stops working. I can no-longer say OK Google to open it up, and even if I open it manually and hit the search button, it doesn't record any voice at all.
The weird thing is, I can still use voice input in any keyboard location (like in SMS or Chrome), but the basic functionality doesn't work.
Anyone else have this happen?
did you by any chance use third party launcher?
gd6noob said:
did you by any chance use third party launcher?
Click to expand...
Click to collapse
Nope, stock launcher. All options for Google Now are enabled, and it works great 90% of the time, but then it just...stops. Only way to get it working again is a restart.
Hi there. I also have this problem. I have narrowed it down to MX player or chrome video player (also same issue with headphones + video). When you play a few movies and exit MX player, "OK Google" will not respond to voice commands. The only fix is to reboot your phone. I have tested this today. I played a few movies after i made sure "OK Google" was working fine and sure enough, the feature stopped working immediately after i played a couple of movies. Sometimes it will not get affected, but most of the time MX player or the integrated Chrome video player will break this function. I would like someone else to confirm this, thanks.
ps; Just tested my theory again after a phone reboot and now it seems to work fine... I have no idea wtf is going on with this feature, but when it breaks, even the search bar stops working. The whole thing just stops functioning - speech , search just stops working.
hotleadsingerguy said:
So it's happened 2-3 times now since I got the phone...all of the sudden voice input stops working. I can no-longer say OK Google to open it up, and even if I open it manually and hit the search button, it doesn't record any voice at all.
The weird thing is, I can still use voice input in any keyboard location (like in SMS or Chrome), but the basic functionality doesn't work.
Anyone else have this happen?
Click to expand...
Click to collapse
update : i have Xperia Z2
in my case it's the opposite , lol
i have my OK Google working but my voice input not , unfortunatelly anyone can help me ? pls ?
ryan42680 said:
update : i have Xperia Z2
in my case it's the opposite , lol
i have my OK Google working but my voice input not , unfortunatelly anyone can help me ? pls ?
Click to expand...
Click to collapse
Sort of. I've had a few things happen like this in the past, and I've realized there's always been a reason (sometimes it's changing settings in Android Wear that pertain to Voice support, sometimes it's switching the voice stuff on on my iPhone 6, sometimes it's changing my Google password, etc...).
The way I've always been able to fix it is just to log out of Google Now and log back in. It says it'll lose things, but it doesn't at all. Takes ~15 seconds, and it's always fixed all of my voice issues, including the one listed above and the other one where it recognizes everything and opens the Google Search...but then everything is blank.
hey, thx i got google voice input working on apps and saying ok goole works but voice input isn't working when i'm in the search bar strange haha
UPDATE: try flashing another Official Rom, gd luck
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
Seeing as the OK Google from any screen is not currently working I have been trying to find a way to wake the device using S voice and having Tasker kill S voice and open Voice Search. I am a Tasker novice and am looking to see if anyone has any ideas. I am currently unrooted which I think may be why it is so unreliable.
I have made a profile that when S voice opens it is killed and Voice Search is opened. I also tried it with the Voice Input service opened. It works occasionally, maybe 1/10 times.
Any input is welcomed.
atvman77 said:
Seeing as the OK Google from any screen is not currently working I have been trying to find a way to wake the device using S voice and having Tasker kill S voice and open Voice Search. I am a Tasker novice and am looking to see if anyone has any ideas. I am currently unrooted which I think may be why it is so unreliable.
I have made a profile that when S voice opens it is killed and Voice Search is opened. I also tried it with the Voice Input service opened. It works occasionally, maybe 1/10 times.
Any input is welcomed.
Click to expand...
Click to collapse
I got OK google back after disabling anything to do with S Voice. I put the Google search widget on the top of each screen and now get OK google from every screen
As said in another post you can start Google now with s-voice without the need of tasker.
As S-Voice allows you to say something without waiting for it to listen you can say "<wakeupcommand> Start Google". I'm for example using "Galaxy Start Google". According to someone else you can also say "Galaxy Voice Search".
Both are starting Google Now and will listen to your voice without any button presses and even when the phone is locked.
whitepaw said:
As said in another post you can start Google now with s-voice without the need of tasker.
As S-Voice allows you to say something without waiting for it to listen you can say "<wakeupcommand> Start Google". I'm for example using "Galaxy Start Google". According to someone else you can also say "Galaxy Voice Search".
Both are starting Google Now and will listen to your voice without any button presses and even when the phone is locked.
Click to expand...
Click to collapse
Confirmed the galaxy voice search command works.
This is a great alternative until okay Google gets fixed. thank you so much!
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.)