So I just got a Moto X. Out of the box, Google Now hotword detection ("Ok Google") worked perfectly both in Google Now and in the Google Now launcher that I sideloaded. Then, hotword detection randomly turned off. If I uninstall and reinstall updates to the Google Search app, hotword is temporarily fixed, but it won't last more than a day until it turns off again. This happens whether or not Motorola's own Touchless Controls are enabled or disabled.
It seems like some other app is causing it to turn off since a third-party hotword detection app wouldn't work, either, but I've hardly installed any apps since I just got it.
Also, I've already tried the most common suggestions such as ensuring that my voice input language is English (US) and making sure than no Accessibility options are enabled.
Any help to get back hotword detection would be greatly appreciated!
The newest Google search update broke hotword. The only way to keep it working for now is to uninstall the update and not install it again until possibly the next update.
Do you know what the latest version of Google Search is that still supports hotwords so I can grab an apk? When I revert back to the factory version of Google Search, it breaks the Google Now Launcher.
Also, any idea why hotwords would work for a while and then randomly stop. This has happened several times, all while I've had the same version of Search.
Uninstall back to 3.1. Make your changes then install 3.2, this is where Hotword Detection is still there but not selectable and Ok Google works. Now install 3.3, Hotword is no longer there but Ok Google still works. Don't install 3.4, you loose both.
Worked for me twice, I accidentally hit Update All and got 3.4 back, had to start over. I've been back on 3.3 for a week or so and Ok Google still works.
I uninstalled to 3.1 (factory version), and did get hotword back, but I couldn't use the Google Now Launcher. Installed 3.2 and still had hotword, but still not Google Now Launcher. Finally, I installed 3.3, I still had hotword, and the Google Now Launcher worked. But a few hours later, hotword got disabled again.
It doesn't seem like the problem is tied to a version. I've gotten hotword to work with 3.4, but it becomes disabled after a little while of use.
micahmo said:
I uninstalled to 3.1 (factory version), and did get hotword back, but I couldn't use the Google Now Launcher. Installed 3.2 and still had hotword, but still not Google Now Launcher. Finally, I installed 3.3, I still had hotword, and the Google Now Launcher worked. But a few hours later, hotword got disabled again.
It doesn't seem like the problem is tied to a version. I've gotten hotword to work with 3.4, but it becomes disabled after a little while of use.
Click to expand...
Click to collapse
In previous versions of Google search, you could say "Okay Google" instead of "Okay Google Now" to activate the hotword when you had the Google app open? I just recently bought the phone and it came already with the newest version of Google Now installed.
I don't think you've ever been able to say "Ok Google Now" as a hotword to activate voice search in the Google app. "Ok Google Now" is Motorola's keyword for its Touchless Controls. Touchless Controls have always worked for me, but when I'm in the Google app (or in the Google Now launcher that I sideloaded), I prefer to use Google's own hotword, "Ok Google" to activate voice search.
Out of the box, my phone also came with the latest version of Google Now installed, and hotword worked out of the box, but for some reason it became disabled. Any time I uninstall and reinstall Google Search (or even clear data), hotword is restored temporarily, but then becomes disabled again after a while.
Did you leave Touchless Control untrained? I didn't disable it but it is untrained at the moment. My phone is a Developers Edition, unlocked and rooted, if that helps any.
I was able to use the Google Now Launcher on 3.2, maybe it is the version of the Launcher? Mine is 1.0.16.1154249 and I did side load it. I haven't
had any trouble with the hotword detection reverting to off as long as I say on 3.3.
Various threads in different forums say different things about this to being a Chrome problem to a Google Search problem to Motorola disabling it
on purpose so the it doesn't interfere with Touchless Control. I guess I'll have to see what happens when Search 3.5 comes out.
At the moment, I don't have a car so the parking feature doesn't have a relevance for me but setting a timer would be kind of useful.
If is is an accident, it would be nice it it were fixed quickly. If it is on purpose, I really wish someone would re evaluate the policy of not allowing a
function on a device that I purchased and would like to make the decision for my self. Just my opinion.
I do hope you find your solution. I came from a Galaxy Nexus and I have been really liking this phone so far as it is as close to the stock that the
GNex was.
SoloDB said:
Did you leave Touchless Control untrained? I didn't disable it but it is untrained at the moment. My phone is a Developers Edition, unlocked and rooted, if that helps any.
Click to expand...
Click to collapse
No, I did train Touchless Control. I could try disabling it and then re-enabling it without training it, but I don't see how that would fix anything. I actually like using Touchless Control for when the phone is out of my reach (which is exactly what it's for), but it's kinda slow and doesn't always respond. Ideally, I'd like to use both Touchless Controls and Google's hotword.
My phone is the unlocked T-Mobile version and unrooted. I don't know if that makes a difference.
I was able to use the Google Now Launcher on 3.2, maybe it is the version of the Launcher? Mine is 1.0.16.1154249 and I did side load it.
Click to expand...
Click to collapse
My launcher version is 1.0.9.1039417, but I grabbed an APK of the same version you have and it still didn't work with Google Search 3.2.
Anyway, maybe an update to Google Search or Touchless Controls will fix it eventually.
According to Moto, the disabled this as it conflicts with Touchless Controls. I think that's BS, but whatever.
I was having a conversation with my fiancé earlier and Google Now popped up when I said "Ok, you" in conversation. I appreciated Google's sentiment.
Sent from my Moto X
natezire71 said:
According to Moto, the disabled this as it conflicts with Touchless Controls.
Click to expand...
Click to collapse
TBH, this is the most likely explanation, since, no matter what version of Search I use, hotword works for a little while and then gets disabled. I even installed a third-party hotword-listening app, and it was disabled immediately. Really hope Moto rethinks this.
micahmo said:
TBH, this is the most likely explanation, since, no matter what version of Search I use, hotword works for a little while and then gets disabled. I even installed a third-party hotword-listening app, and it was disabled immediately. Really hope Moto rethinks this.
Click to expand...
Click to collapse
I've raised this issue multiple times over on the Motorola Forums. The Forum Manager there told me that's what Motorola told him. It's unfortunate.
natezire71 said:
I've raised this issue multiple times over on the Motorola Forums. The Forum Manager there told me that's what Motorola told him. It's unfortunate.
Click to expand...
Click to collapse
It sounded like he was going to bring it up and submit a report on the issue, using the conversation in the Motorola forums as a basis. It'd be nice if that led to hotword being re-enabled but who knows. Sounds like some software update is on the way, at least for t-mobile; maybe that will help. Wishful thinking...
Maybe 4.4.3 but who knows.
Google Now Hotword
If your phone is rooted, I think I have a solution for you. It's been working on my phone for about a day now. I don't think I have enough posts in to do any links, but if you go to Droid Life and read the article under "Google Makes “Ok Google” System-wide Hotword Detection Official" the is a link in the comments to a utility called UnLeashTheGoogle. Follow the instructions to get the Google Now stuff working. There is an added step however, look for hotword_blacklisted_devices and change the XT1060 to anything else, I used XT1000. I also went as far as disabling the Touchless Control app so that it wouldn't interfere with the Google Now functions.
All of you that use Touchless Control, great, it is a neat feature, but I prefer to use a more Nexus like feel. To each his own.
SoloDB, that would be a great solution if I were rooted. It's almost tempting enough, although I don't feel like wiping my device at this point.
It's sad that even with the rollout of Google Now's always listening feature, it's still disabled on the Moto X. And it's obviously intentional since the device is blacklisted.
micahmo said:
SoloDB, that would be a great solution if I were rooted. It's almost tempting enough, although I don't feel like wiping my device at this point.
It's sad that even with the rollout of Google Now's always listening feature, it's still disabled on the Moto X. And it's obviously intentional since the device is blacklisted.
Click to expand...
Click to collapse
You can root using pie via the moto x toolkit without wiping anything. I just did this the other day, but I deleted everything from the blacklist section.
The only issue I'm having now is always listening via Bluetooth in my car (2013 Honda crz hands free link non-nav). It worked flawlessly with my galaxy nexus.
Yes, unfortunately you have to have root. The utility needs root and before I found UnleashTheGoogle I edited the Google Search app pref file to
alter the blacklist which got Ok Google working in the first place, I needed root for that as well being the folder is in the System area. The utility
got everything enabled as well.
I know there are security issues having a rooted phone, but I learned in the Galaxy Nexus days how valuable it is to have a bit more control of
the phone to do the kind of stuff you'd like to do other than what Verizon and, in the case of the Moto X, the manufacturer would "prefer" you to do. The Developers Edition of
Moto X really has made the transition away from the old Galaxy Nexus really easy.
I wish I could root but my work email policies check for that.
Sent from my XT1053 using Tapatalk
txaggies07 said:
I wish I could root but my work email policies check for that.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Would this help? http://repo.xposed.info/module/com.phantasm.xposed.gfesecuritypatcher
How is Google now for this? I read about moto voice...but what if I want to use strictly Google now, is this possible? Also, while the phone is locked/screen off is it possible to say 'okay google' and have it activate?
dman777 said:
How is Google now for this? I read about moto voice...but what if I want to use strictly Google now, is this possible? Also, while the phone is locked/screen off is it possible to say 'okay google' and have it activate?
Click to expand...
Click to collapse
With the exception of actual Moto Assist commands everything is pipped over to Google Now.
So if I use my activation phrase and say a Moto command such as: "What's up" that will stay on the phone and tell me about appointments and messages that I received. However if I say something outside of the listed commands like: "how far is the moon away from the Earth" it will tell me that it's opening Google and I will get the answer from Google.
As for using the standard "okay Google". I tried setting that up as my phrase. The phone complained that there wasn't enough syllables. So I just went with the suggested: Okay Google Now.
And yes, it works with the screen off. I've had it mostly work even while in my coat. Though it wasn't 100%. But to it's credit. I have a pretty thick leather coat and the phone screen is always facing me.
Also a drawback (for me at least) is sometimes I don't hear the little chime that lets me know that it's waiting for a command. So I end up saying the phrase twice thinking that it didn't hear me and then I will hear that it's searching Google.
I think it uses Google Now API
It sure seems to me that moto voice is actually using google now. I installed bluetooth launch (but didn't need to use it, other than to remove Voice Dialer as the default bluetooth button launch). Then when pushing the bluetooth button I could launch my choice of Moto Voice or Google Now. The Ok Google does work with this phone. But Moto Voice lets you change the phrase. Moto Voice will simply launch Google Now when any question you ask is a search.
The problem with Moto Voice is that it is much, much slower than just going to Google Now to begin with. I'm hoping that Motorola will kill off Moto Voice with the Android 5.0 update and simply use Google Now directly.
Hi everybody
Until a couple of days ago, I was able to use voice commands in Android Auto without the need for Google Assistant. Now it seems that Google has made some changes that force me to use assistant if I want to use voice commands.
Is there a way I can work around this? There's no way I am giving Google permission to use my web and app activity or my location history. It's not necessary for voice to work since it worked perfectly without these permissions in the past.
Any ideas? Is reverting back to an older version of AA an option?
I have this same issue. At one point I got around it by changing my country of origin to a country where they haven't yet implemented android assistant (giving the voice an Australian like accent), but i eventually gave up and went back to USA without assistant. I am also curious if there is any way around it
Same here, Android Auto was working fine before Google Assistant was introduced, with plain voice search, and it was super useful to just say OK Google, Play something on Spotify, or OK Google, Go to address this and that. Now the only thing we get back from Google is "When it's safe, you'll first need to tap on the notification". No way I'm turning on Web, Location, Device and Voice History.
Has anybody found a solution to this? Google Assistant requires full access to just about everything Google in order to operate.
I don't want to give Google my entire search access just to use Android Auto.
There was a work-around where you could set your language to US Virgin Islands or something (Where google assistant wasn't live yet), but in the end I decided to not use the microphone in Android Auto anymore