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
Hi guys, i have a question. Is there any way to stop Google play services auto updates? I ask, because suddenly my battery drain problem on kit kat came back, and lookin i found that Google ps was on versión 5.x, so i uninstalled updates an left it on versión 4.x, and everything came back to normal.
settngs/apps/all apps , google playstore service... go to manage n clear all data... den uninstall...den disapble
Then he won't have Google Play services at all. It's not what he's asking for.
OP - no, unfortunately there is no way to stop it from auto-updating. However, if you clean the data as I wrote here - you might get lucky and not have any drain with version 5.x. I have it and it's fine.
Jack_R1 said:
Then he won't have Google Play services at all. It's not what he's asking for.
OP - no, unfortunately there is no way to stop it from auto-updating. However, if you clean the data as I wrote here - you might get lucky and not have any drain with version 5.x. I have it and it's fine.
Click to expand...
Click to collapse
Thanks man, i'll try that
Wakelock Termination....
There is only one way perfectly working for me so far with all updates for Google play services....
Install Xposed Framework
Install Wakelock Terminator Wakelock Terminator on Play Store
Activate it in Xposed
Open the Wakelock Terminator and look for google play services
Activate Wakelock Terminator for Google Play Services (In free version only 1 can be added to wakelock).
Add these values in the Filter for Google Play Services
NlpCollectorWakeLock NlpWakeLock CheckinService NetworkLocationLocator
Restart.... You can even check it in app and running menu in settings that you would only see 1 process running for play services and it won't be keeping your CPU awake..... Check it using Wakelock Detector....
Go ahead and give it a try and enjoy.... :good:
Share this info if this helps you..... Let as many people know about it.....
Press Thanks if I helped....
camileind said:
Hi guys, i have a question. Is there any way to stop Google play services auto updates? I ask, because suddenly my battery drain problem on kit kat came back, and lookin i found that Google ps was on versión 5.x, so i uninstalled updates an left it on versión 4.x, and everything came back to normal.
Click to expand...
Click to collapse
Yes there is the way to do it...your device must be rooted...there is an app...here on xda... called LBE security master..in settings there is an option to stop automatically installed software...device still download updated app but LBE stops installation..50 times in 3 days...don't dowload Lbe from play store cos app is in Chinese language. There is one here on xda translated...V5.3.7506 works for me...i an on kitkat 4.4.2
medovici said:
Yes there is the way to do it...your device must be rooted...there is an app...here on xda... called LBE security master..in settings there is an option to stop automatically installed software...device still download updated app but LBE stops installation..50 times in 3 days...don't dowload Lbe from play store cos app is in Chinese language. There is one here on xda translated...V5.3.7506 works for me...i an on kitkat 4.4.2
Click to expand...
Click to collapse
I don't see any setting at all???
medovici said:
Yes there is the way to do it...your device must be rooted...there is an app...here on xda... called LBE security master..in settings there is an option to stop automatically installed software...device still download updated app but LBE stops installation..50 times in 3 days...don't dowload Lbe from play store cos app is in Chinese language. There is one here on xda translated...V5.3.7506 works for me...i an on kitkat 4.4.2
Click to expand...
Click to collapse
nikhilkaushik said:
There is only one way perfectly working for me so far with all updates for Google play services....
Install Xposed Framework
Install Wakelock Terminator Wakelock Terminator on Play Store
Activate it in Xposed
Open the Wakelock Terminator and look for google play services
Activate Wakelock Terminator for Google Play Services (In free version only 1 can be added to wakelock).
Add these values in the Filter for Google Play Services
NlpCollectorWakeLock NlpWakeLock CheckinService NetworkLocationLocator
Restart.... You can even check it in app and running menu in settings that you would only see 1 process running for play services and it won't be keeping your CPU awake..... Check it using Wakelock Detector....
Go ahead and give it a try and enjoy.... :good:
Share this info if this helps you..... Let as many people know about it.....
Press Thanks if I helped....
Click to expand...
Click to collapse
It is not working. Google Play Services still updates.
Upgrade your ROM to 4.4.4
evrycard said:
It is not working. Google Play Services still updates.
Click to expand...
Click to collapse
Sony has ultimately resolved this problem. Simple solution, upgrade to 4.4.4....
I am using it since long and don't find any issues....:good:
nikhilkaushik said:
Sony has ultimately resolved this problem. Simple solution, upgrade to 4.4.4....
I am using it since long and don't find any issues....:good:
Click to expand...
Click to collapse
I think with the advent of Google Play Services 6.5.99 (or perhaps a bit earlier) the auto-update issue has become a problem again.
According to my recent observations Google Play Services 6.5.99 performs periodic location pings (every 15min) or so. With my settings ("Device only" location mode, but "Location reporting" and "Location history" turned "Off"), it is using GPS and thus unnecessarily drains the battery.
I don't see the problem with Google Play Services 6.1.05 so I'd rather wish Google would not auto-update Google Play Services.
Call me a newbie (I'm fine with that because I am as far as Android is concerned) but I find it outrageous that Google can update a core component on my phone without my consent, introducing phone issues, sub-par performance, or undesired behaviour at their whim. An opt-out facility for the auto-updates would be the least one would expect.
The Google Play Store allows one to opt out of automatic updates to downloaded applications so why isn't this setting not consulted when it comes to "Google Play Services"? I realise that probably no one here knows the answer, but I found it very hard to find a place to actually provide Google with feedback regarding "Google Play Services".
TomKay said:
According to my recent observations Google Play Services 6.5.99 performs periodic location pings (every 15min) or so. With my settings ("Device only" location mode, but "Location reporting" and "Location history" turned "Off"), it is using GPS and thus unnecessarily drains the battery.
I don't see the problem with Google Play Services 6.1.05 so I'd rather wish Google would not auto-update Google Play Services.
Click to expand...
Click to collapse
I ve faced the same isse with the repeated gps activities since the last update from the play Services.
But i think the cause of this phenomenon is the Google search! Ive disabled the google search app, and now I dont have this strange gps requests!
wihushae said:
I ve faced the same isse with the repeated gps activities since the last update from the play Services.
Click to expand...
Click to collapse
Thanks heaps for confirming.
I wasn't sure whether my (stock) system got messed up somehow.
I wonder why there hasn't been more of an outcry over the new location pinging behaviour. I find it unacceptable and can only believe it is due to a bug rather than intended.
I hope that future versions of "Google Play Services" will behave differently and found it frustrating that I couldn't locate a forum where Google developers would be listening to "Google Service Play" concerns. I made a post in a "Google Search" thread at a Google forum (not allowed to link to it yet) but I'm afraid it is off-topic there.
wihushae said:
But i think the cause of this phenomenon is the Google search! Ive disabled the google search app, and now I dont have this strange gps requests!
Click to expand...
Click to collapse
I first believed "Google Search" to be the culprit as well because disabling it got rid of the location pings.
However, that only worked once and later attempts to kill the pings by disabling "Google Search" were unsuccessful. Perhaps you should check once in a while whether the pings are coming back because it appears to me that it really is "Google Play Services" and it is just being triggered by various sources.
Also, being able to initiate a google search by just wiping up the home button, is a rather crucial feature to me. Disabling "Google Search" would force me to fire up a browser instead which would be a lot more cumbersome. Given that a different version of "Google Play Services" does not perform the pings even while "Google Search" is available, I'd say one should attempt to tackle the problem by addressing "Google Play Services" not "Google Search".
BTW, I opted out of "Google Now" just to make sure that there aren't any location based cards that request location updates.
Try to use navigation from watch, sits at calculating route, then i get a "check phone to continue". Nothing is brought up on phone. I have reset watch, reinstalled google maps, checked all my location settings, nothing that i have done has fixed this issue. Any ideas?
Navigation not working
Yes, I am experiencing the same thing. Anyone have a fix?
I have also read that people are having same issue with the moto 360. Thats a good thing its not hardware related.
It Works..
I managed to get it to work.. On your Phone go to Apps Manager.. Look for Google Maps.. Uninstall Updates.. This feature doesnt seem to be working with Maps 9.xx.. It has to be Maps 8.xx... then run Google Maps on your phone once.. Make sure you navigate at least once as there are some pop up notifications on the phone the first time you navigate with maps.. The watch does not know what to do handle pop up.. Once you have navigated at least once try launching it from your watch.. Let me know if this works for you.
Talking with android wear support, i will post back with any news
amresh89, that did work. I passed that info onto wear support.
Downgraded to Maps 8, created a route / directions and then closed Maps. Tried on watch and it tries to route and the closes.
UPDATE : Restarted phone and it then worked.
Jeff
Yes this is a known issue with google maps 9.4. which doesn't seem to be updated in many regions. Fix is to uninstall updates, download google maps 9.5.1 from this link: http://www.apkmirror.com/apk/google-inc/maps/maps-9-5-1-android-apk-download/. Always healthy to restart your phone and smartwatch then resync the apps. This should resolve the issue.
Hope it helps.
Update Maps, works now. 9.5.x
Maybe I'm going mad but I'm sure when I first used my Urbane there was a Google Maps app. However now Maps isn't in the app list. The only way I can get it up is to trigger a set of directions thorough "OK Google" . Does anyone have maps show in the list? (I.e next to Weather, Alarm, Settings, Google, Play Music etc)
No maps app here too.
Same here, but here's how I fixed it.
I uninstalled and reinstalled Google Maps. Then I resynced apps on my Android Wear app. I appeared as an option a min later!
I had to do the same thing with Google Music
Thanks. I tried uninstalling, and then reinstalling and resyncing, no luck.
I'm also missing other apps (I think) does Whatsapp, Ubur or Shasam have apps for wear? Hard to tell if I missing them or they just don't have a way to launch on the watch....
You need the latest version of maps and android wear. I removed the watch from android wear, reset the watch, paired them again, it worked. Also got an update that up to now it had been saying did not exist and a few other oddities fixed. I'm not sure why I didn't do this before, I suppose because I'm used to it being a bit of a chore to reset a rom on the phone and I need to recalibrate my thinking for the watch/android wear. It only takes a minute to get the reset going, check back in about 15 minutes to pair with phone, check back in after a while and its done. Knowing what I know now I'll likely do this every so often just to see what new apps will be pushed to the watch and if it will pick up an update.