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
If you have a Bluetooth headset, and you try to use to with LG's HORRIBLE voice assistant, it recognizes your commands about 1% of the time; totally not acceptable.
On other phones, Google Now comes up when you activate voice command; on this phone, I have tried EVERYTHING, but I can't get the LG voice command to not be the default action when I activate a voice command.
Has any one found a way to change this, either with other software, or by making some system changes?
On kitkat, on T Mobile, using a Plantronics Voyage Edge
Thanks!
I simply swipe up from the bottom and use Google Now. You probably can't change LG's voice assistant to use Google Now's speech engine.
Visa Declined said:
I simply swipe up from the bottom and use Google Now. You probably can't change LG's voice assistant to use Google Now's speech engine.
Click to expand...
Click to collapse
There MAY be a way to do it kind of like how you can change the voice of Google Nav from the standard one to like Darth Vader and whatnot. Idk if anyone has attempted this BUT it might be worth a shot. maybe the actual application can be modified to reroute to Google Now instead of the base LG application. i might poke around to see what i can find
thanks; there are a couple of apps in the play store that used to do this for me with my HTC One Maxx, but they dont do anything for this phone; there are about 5 or 6 files that are related to LG's horrible "voice mate" app, but, with no way to restore my 4.4 rom if deleting any important files screws things up, I am hesitant to start deleting system files.
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.
Hello all, I am coming here because my limited Android knowledge and Google search has failed me. I am trying to make a voice activated Google Maps GPS for my father to use while trucking. He specifically asked for Google Maps because he uses it on his phone and knows the voice commands, but the phone screen is too small and a new law that just went into effect in my state makes it illegal for him to have anything in his hands. For a trucker, that violation could cause him to lose his CDL. SO I am trying to help him out with this.
NOTE: there is no Truck/headunit interface in this deal; simply the tablet acting as the Android Auto command point. The device has wireless data connection.
The hardware:
Galaxy Tab A 2016 7" 32-bit architecture
SM-T280
Lollipop 5.1.1
Kernel version 3.10.65-12484970
Google version - 10.92.10.21.arm
Google play services - 19.8.31
Google play store - 18.3.24-all [0] [PR] 288734092
Android Auto version - 4.9.594933-release (Sideloaded)
With that setup, Android Auto works, is stable. However, it is unable to do any voice commands. For example, if I say 'OK Google, open maps' it simply responds that is does not know how to help with that command yet. On My galaxy Note 8, this exact command works fine. I am wondering what service or item I need to sideload to force these commands to work. I am not averse to Rooting and ROM'ing if it is absolutely stable and as close to OEM as possible. I am trying to make this tablet GPS setup as seamless for him as possible, I will be using an app task launcher for when the device wakes up or boots, it will automatically launch into Android Auto for him.
Please, any advice or options would help. I was thinking to try and sideload/force everything to match my phone, but the tablet is 32 bit, and the phone is 64 bit so almost nothing can be matched due to architecture.
Interesting. My Tab S4 will not let me run Android Auto (tells me device is not compatible), but I was trying to AA into my Subaru head unit. My impression is tablets, or at least Samsung tablets, are not well supported in AA, either through intention or neglect. That said, does he really need AA? Can the tablet be set to never screen off if plugged in and he just run google maps straight-up on the tablet, using voice?
Note10.1Dude said:
Interesting. My Tab S4 will not let me run Android Auto (tells me device is not compatible), but I was trying to AA into my Subaru head unit. My impression is tablets, or at least Samsung tablets, are not well supported in AA, either through intention or neglect. That said, does he really need AA? Can the tablet be set to never screen off if plugged in and he just run google maps straight-up on the tablet, using voice?
Click to expand...
Click to collapse
That's another idea I am going to try now. I think I can have Google Assistant and Maps launch at boot, and then google assistant might allow him to use voice commands such as 'navigate to xyz address' or so I am reading on Google Website. I am also experimenting with tethering widgets to make turning the data connection on and off easy for him when he pops in the truck. Plus downloading offline maps to the device as well, but I am wondering if there is voice navigation when offline.
I have exactly the same problem. I use a Lenovo Tab A7-10F with Android 5.0.
I installed the latest Google App, Google TTS and Maps (all 3 requirements for starting AA). AA v.4.5.592853 is working fine, but the assistant function in it not. It always answers "I don't know how to help with... navigate to New York" or similar. The same problem happens when using Maps directly.
Whereas when opening the Google App and ask something there works fine. F.e. I can start maps navigation with "Navigate to New York" or set an alert or similar.
cj182 said:
I have exactly the same problem. I use a Lenovo Tab A7-10F with Android 5.0.
I installed the latest Google App, Google TTS and Maps (all 3 requirements for starting AA). *link* is working fine, but the assistant function in it not. It always answers "I don't know how to help with... navigate to New York" or similar. The same problem happens when using Maps directly.
Whereas when opening the Google App and ask something there works fine. F.e. I can start maps navigation with "Navigate to New York" or set an alert or similar.
Click to expand...
Click to collapse
Hey CJ, I haven't tested this in the hands of my father yet, but the solution I have been testing in my own car is I have Google Assistant and Maps launch at startup/unlock. Then, I have the google assistant voice matched so that it recognizes my voice and can be used at any time while the tablet is on. I then say 'OK google; Navigate to XYZ address' and it will open maps, set the navigation and begin in right away. This seems like the best solution I've come to in order to get around the stupid limitation on the AA voice command not working. I also downloaded the offline maps so that navigation will work even with weak cellular data signal.
So far that setup has been working. I had it tethered via Wifi Hotspot. I plan on finding a widget that will work for turning his wifi on and off so he doesn't have to navigate through Settings or worry about sliding down on his small screen when he is driving truck to activate. I have Android Pie on my phone and it seems like all the widgets for this stopped working after 8.0, so I can't test the viability of this tethering widget until I get his phone in front of me.
One thing to note; depending on the performance of your tablet, the autolaunch of Maps and Google Assistant on startup can be slow and cause errors. In one case I started using Google Assistant too fast and it just said 'something went wrong' and closed out. I rebooted and waited an extra minute and then it worked fine. This is on a Galaxy Tab A (2016) which is some very basic hardware compared to many other tablets.
I'll reply to this once I get this in my tech-challenged fathers hands and see how it works out for him.
Hi XTwarrior! Thanks for your answer.
Ok, I will probability also go this way and just use Maps with voice commands without AA.
Unfortunately I can't install Assistant on my tablet (Tab 2 A7-10F) due to Android 5.0 limitation, but the Google App works. With Google and Maps I still can use voice commands like " Ok google navigate to XYZ" and maps opens with navigation. But what is (mostly) not working is to further ask details during navigation such as:
when do I arrive?
Help
Exit Navigation
etc. They all are answered with "not sure how to help with [command repeated]..."
But strangely that works
How's traffic ahead?
Here is another nice trick described in this video : you could modify your Tablet such that it boots automatically when a charger is connected (i.e. starting the car) and shut down automatically after 20 sec of no charging connection (with a task of AutomateIt).
XTwarrior1985 said:
Hey CJ, I haven't tested this in the hands of my father yet, but the solution I have been testing in my own car is I have Google Assistant and Maps launch at startup/unlock. Then, I have the google assistant voice matched so that it recognizes my voice and can be used at any time while the tablet is on. I then say 'OK google; Navigate to XYZ address' and it will open maps, set the navigation and begin in right away. This seems like the best solution I've come to in order to get around the stupid limitation on the AA voice command not working. I also downloaded the offline maps so that navigation will work even with weak cellular data signal.
So far that setup has been working. I had it tethered via Wifi Hotspot. I plan on finding a widget that will work for turning his wifi on and off so he doesn't have to navigate through Settings or worry about sliding down on his small screen when he is driving truck to activate. I have Android Pie on my phone and it seems like all the widgets for this stopped working after 8.0, so I can't test the viability of this tethering widget until I get his phone in front of me.
One thing to note; depending on the performance of your tablet, the autolaunch of Maps and Google Assistant on startup can be slow and cause errors. In one case I started using Google Assistant too fast and it just said 'something went wrong' and closed out. I rebooted and waited an extra minute and then it worked fine. This is on a Galaxy Tab A (2016) which is some very basic hardware compared to many other tablets.
I'll reply to this once I get this in my tech-challenged fathers hands and see how it works out for him.
Click to expand...
Click to collapse
Is there a way to make Google assistant work on Vivo X90 pro plus? I installed it and activated it, and made it the default assistant but it's not working.
I believe, and someone can correct me if I'm wrong, Google assistant only works by making it a widget, pressing the button, then speaking. Saying "hello google" doesn't work on any chinese device afaik
I tried this but it's not performing any tasks.
In the settings I get this message, and I am not sure if I missed something.
Continued conversation also doesn't work. Without it assistant is useless
extremecarver said:
Continued conversation also doesn't work. Without it assistant is useless
Click to expand...
Click to collapse
Sorry I didn't get it.
you cannot talk with google assistant. Each time you will have to say the full command.
E.g.
hey google, how is the weather in London
Answer... XYZ
and how will be the weather tomorrow
will not work. Therefore you can also not use it inside an app. You cannot say:
hey google: please open google maps
... google maps opening
.. I want to ride my bike to picadilly circus
Without continued conversation first google would not listen.
Second you cannot communicate with the assitant and would instead need to do like:
hey google: please open google maps and navigate me by bike to picadilly circus
Google assistant may understand it in one command - but it cannot ask back.
Hence -- Google assistant is a piece of trash on the X90 PP because it doesn't understand anything and will not ask for better indications or pick up on previous commands.
Also that way you cannot really use it inside an app. So you're left with asking questions and getting answers and nothing else. No conversation.
Thank you got it. So separate commands but not continuous conversation.
Single commands. Not separate. You always start at Zero.