Related
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
Upgraded my N5 to its Lollipop Factory Image, and setup Smart Lock to work with my Moto 360. I'm noticing that my N5 will still prompt me for a passcode half the time, even though my moto 360 shows it's still connected (I can even PROVE it's connected, by doing an "Ok Google" voice search). I even set up face unlock to give it another unlock method, and that didn't seem to increase the success rate for Smart Unlock. It seems that no matter what, smart unlock doesn't work for me a lot of the time. To be more specific, it seems like it doesn't work if I haven't used the phone in awhile. Once I put my passcode in, smart lock seems to work just fine for awhile, but eventually it will stop working again, forcing me to enter my passcode to jumpstart it again.
Anyone else experiencing this?
Yes, this seems to be what I'm experiencing as well.
Same here... really want this to work. I assumed it might be because I dirty flashed, are you running a clean install?
same here...
Same here with a nexus 9. Tried connecting it to a moto and to my nexus 5. The units ARE connected to the nexus9 but in smartlock they have status "not connected". After setting up it works until the units are out of reach for the first time....after that it is back to pincode
jt3 said:
Upgraded my N5 to its Lollipop Factory Image, and setup Smart Lock to work with my Moto 360. I'm noticing that my N5 will still prompt me for a passcode half the time, even though my moto 360 shows it's still connected (I can even PROVE it's connected, by doing an "Ok Google" voice search). I even set up face unlock to give it another unlock method, and that didn't seem to increase the success rate for Smart Unlock. It seems that no matter what, smart unlock doesn't work for me a lot of the time. To be more specific, it seems like it doesn't work if I haven't used the phone in awhile. Once I put my passcode in, smart lock seems to work just fine for awhile, but eventually it will stop working again, forcing me to enter my passcode to jumpstart it again.
Anyone else experiencing this?
Click to expand...
Click to collapse
got no problem at all since N5 is paired with my LG G watch.
Got problems making NFC tag work. I have a NFC sticker at home, i use it with this app https://play.google.com/store/apps/details?id=com.jwsoft.nfcactionlauncher&hl=en making toggle wifi when i enter home (wifi on) and when i walk out (wifi off). I tried to use the same tag for smart unlock, but it simply doesn't works. Tag writing seems to be ok but still have to enter the pin when i pass my phone over it. Should i use another tag?
Mine works but RARELY
Sent from my Nexus 5 using XDA Premium 4 mobile app
Well, I figured out my issue anyway. It seems it's Gravity Screen. I use it to turn off my screen when I put the phone in my pocket (and turn it back on when I take it out). Because of this, I rarely touch the power button anymore. Apparently, when Gravity Screen locks the device, it REALLY locks it, making it so that Smart Lock can't unlock it, and forcing you to enter a passcode. I've left a note in the dev's thread, asking for a fix, but for now, I had to disable that feature.
Now, Smart Lock is working almost all of the time. I still have the occasional need to enter a passcode (like after rebooting), but for the most part, this fixed my issue.
I guess the tl;dr of all this is to make sure you don't have any apps running that lock or power-off your screen. They may be interfering.
jt3 said:
Well, I figured out my issue anyway. It seems it's Gravity Screen. I use it to turn off my screen when I put the phone in my pocket (and turn it back on when I take it out). Because of this, I rarely touch the power button anymore. Apparently, when Gravity Screen locks the device, it REALLY locks it, making it so that Smart Lock can't unlock it, and forcing you to enter a passcode. I've left a note in the dev's thread, asking for a fix, but for now, I had to disable that feature.
Now, Smart Lock is working almost all of the time. I still have the occasional need to enter a passcode (like after rebooting), but for the most part, this fixed my issue.
I guess the tl;dr of all this is to make sure you don't have any apps running that lock or power-off your screen. They may be interfering.
Click to expand...
Click to collapse
I don't use Gravity Screen, but have it installed. Could that cause the problem? I'm currently on 5.1 Cataclysm on my Nexus 5.
I have added Moto 360 as a trusted device. The moment I add it i'm able to unlock without PIN. However, after a few minutes, although the watch is connected, smart lock doesn't seem to work. I had this issue on stock Android 5.0 (no root or bootloader unlock) also with a Sony bluetooth headphones!
My smart lock "trusted places" is not working. I am assuming it is associated with the recent update to the Google Play Services for the "on body detection."
My Google Play Services has been sucking up my battery usage when location services is on. Other users have been experiencing the same issues. Some fixes suggest turning the smart features off then back and another is reinstalling the Google play services (revert then update again.)
I side loaded my Google Play Services but it didn't fix the problem. I am still looking for a fix so trusted places will work.
Sent from my Nexus 5 using Tapatalk
chrisinsocalif said:
My smart lock "trusted places" is not working. I am assuming it is associated with the recent update to the Google Play Services for the "on body detection."
My Google Play Services has been sucking up my battery usage when location services is on. Other users have been experiencing the same issues. Some fixes suggest turning the smart features off then back and another is reinstalling the Google play services (revert then update again.)
I side loaded my Google Play Services but it didn't fix the problem. I am still looking for a fix so trusted places will work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Having absolutely the same problem. The "on body detection" feature works perfectly, howeve, the "trusted places" - almost never. I find myself entering my PIN at home every time I want to unlock the device, except for the times I slide it out of my pocket. If Google fixes these problems, Smart Lock would be my favourite feature!
I've pretty much given up on Smart Location Unlock. It's been broken for weeks now. I'm on CM12 and made profiles to disable pin/password/pattern when connected to my home Wi-Fi.
No idea why, but every option I can find to enable me to use the OK Google command when the phone is locked seems to be inactive and grayed out. Is there some mystery setting somewhere that needs to be active for it to work? I can "OK Google" fine when the phone is unlocked, just not when it's locked -- in that scenario, "OK Google" just brings up the lock screen and the assistant doesn't start until I manually unlock the phone. All the other Smart Lock features seem to work. Google app is the latest version. I can't think of any other apps that might be interfering. I'm baffled.
In Settings>Google>Search & Now>Voice -- the "OK Google Detection option is grayed out.
In Google App>Settings>Voice -- the "OK Google detection" option is grayed out.
In Settings>Security>Smart Lock>Trusted Voice -- the "Say OK Google any time" option is working, as is the "while driving" option. The "Trusted Voice" switch, however, is off and grayed out at all times, whatever the other switches are set at.
I do get an alert "Trusted Voice is part of 'OK Google' " when I go into Trusted Voice setup, but I've no idea what that means. It certainly doesn't mean OK Google is able to unlock my phone.
Anyone have any idea how I can get a Trusted Voice set up so I can actually unlock the phone by saying "OK Google"?
If you can't get here because option to press Ok Google Detection is greyed out maybe you installed mods or something modified the system somehow.
Sent from my sailfish using XDA Labs
No mods installed... I'm running stock Android, unrooted, but clearly something's not working right. I can get to those screens OK, but "OK Google detection" is grayed out and "trusted voice" is permanently grayed out, whether the first option is on or not
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I have the same issue, the only solution I have is to disable the ok Google option as you said.
xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I think problem should be addressed to Google first cause of Google now, or Huawei, second, cause the service is continuosly listening for "Ok google" activation, but it should stop or, better, stand-by, so the
microphone can be used by the concurrent app, when finished, service automatically restarted. This behaviour doesn't require any error or warning pop-up when happens.
Even I like to know, if anyone knows how to submit issues directly to Huawei/Honor.
Just started having the same issue with the latest Google app update, but I can't even disable the "Ok Google" detection. It just turns itself back on immediately. Here's a screencap of my dilemma:
https://gfycat.com/FancyTepidHornedviper
@Xichael: Tap on "Delete Voice Model" and you can turn it off permanently. This is, as far as I know, the only way other than deleting / deactivating the Google App or possibly tweaking certain permissions. Once you delete the voice model, the "Ok Google" should still work within the app or when long pressing the home button.
@xghost1 Yes, deactivating "Ok Google" on any screen by deleting the voice model is so far the only solution that works permanently. There is currently no way to have "Ok Google" everywhere while also not getting that error message. We'll just have to wait for a fix. I think this only applies to the current "Google Assistant" though. It might be possible to go back to an older version of "Google Now" where "Ok Google" on any screen still works while not getting that error.
Thanks, that solves it for me. I can live without "Ok Google", but that popup was intolerable.
xichael said:
Just started having the same issue with the latest Google app update, but I can't even disable the "Ok Google" detection. It just turns itself back on immediately. Here's a screencap of my dilemma:
https://gfycat.com/FancyTepidHornedviper
Click to expand...
Click to collapse
Remove your trained voice and then "Ok Google" detection on any screen will then turn off. That is the only way I found to disable it.
Sent from my FRD-L04 using Tapatalk
xghost1 said:
Recently after updating to Honor 5 I have been receiving this error whenever I try to use MIC on any app.
http://i.imgur.com/RSKzF3z.jpg
I searched it and I know that if I disable the optiong to "Ok Google" from anyscreen it will go away but I cannot believe that is the only option.
Has anyone found the same error or solution?
Is there any Huawei channel to submit this error?
Click to expand...
Click to collapse
I was having similar problem and it's gone after i denied permission for microphone...before it was turning itself and made me crazy...I hope it will help You with this issue
famanfwppc said:
I think problem should be addressed to Google first cause of Google now, or Huawei, second,
Click to expand...
Click to collapse
Other Nougat phones with OK Google active don't have this issue. So I'd say Huawei would be the first to be addressed.
It's hard to know who to blame on this one. When Googling, it looks like it's only a problem on Huawei devices. That said, when I try to disable all-screen OK Google detection, the setting won't stick and always reverts. That sounds like a Google issue. I had to delete the voice model.
Likely it's some combination of both.
I called the service hotline last week and they said it was the update to Google app that was screwing things up. For me it was creating a toast message in my camera app when I would record video or use voice activated shutter control for still pictures. He told me to revoke permissions in the Google app for the microphone, or revert to an older version of the app. I'm assuming pre Google Assistant. I haven't tried that option yet.
Turning off all-screen 'OK Google' detection is likely the best option, especially because you can map your Smart Key to Voice Search and get nearly the same functionality. The only impaired function is if you hands-free dock in your car, but even then I rarely use Assistant anyway in that setting.
Thank you all for your comments and replies.
For your information I was receiving this error even without Google Assistant, since I was using my phone with Portuguese language. I tried to reset and changed it to English, now I have Google Assistante working but the error still remains. So like it was already mentioned my best gues is to associate the problem with Google App and Huawei Software.
To be sure it would be good if anyone could test the issue on a Custom Rom.
Thanks
Go into Playstore and chose to uninstal Google app. It will roll back to a version before Google Assistant and your phone will act as normal, you just don't have assistant. I even noticed an issue prior to this while using Shazam to identify a song I was listening to.
Background processes
"com.google.android.googlequicksearchbox:interactor" is a common Android process.
Huawei is at fault for this bug.
I can confirm only Huawei handsets are experiencing this annoying bug.
Huawei also has their own voice assisted application/processes I.e. Quick calling. If you disable all Huawei voice assisted features, this most likely will solve the problem as well.
It seems Huawei voice assisted processes and Google voice assisted processes cannot be active at the same time without the user seeing this message. If you prefer "Ok Google" and other Google voice assisted processes then try disabling Huawei voice software first.
Go to settings and search "voice" then select "voice control" turn off all Huawei voice assisted processes.
Hopefully this helps.
I guess if I want to disable OK Google and use Huawei's voice assistant instead, I can be away from the evil Google. But what does Huawei voice assistant do? I only found "find my phone" and very few other functions. While from what I heard, in China where Google services are totally disabled, Huawei's voice assistant can do a lot more things. Where are they?
Turning off the Huiwei voice facilities does not work. Still get same error.
To get rid of the box you have to turn off "ok Google" detection from any screen.
If it it turns itself back on (a Google bug) you have to delete the voice model.
To use the assistant you'll have to hold down the home button.
The interactor box is just another big of many that Huawei hasn't bothered patching. Huawei clearly doesn't care. Last time buying a device from them.
SolarisSixth said:
To get rid of the box you have to turn off "ok Google" detection from any screen.
If it it turns itself back on (a Google bug) you have to delete the voice model.
To use the assistant you'll have to hold down the home button.
The interactor box is just another big of many that Huawei hasn't bothered patching. Huawei clearly doesn't care. Last time buying a device from them.
Click to expand...
Click to collapse
Yes. Get that you have to turn off OK Google.
The trouble is, I don't *want* to turn it off.
Very annoying bug for sure.
Sent from my FRD-L09 using Tapatalk
ckckckckck said:
Yes. Get that you have to turn off OK Google.
The trouble is, I don't *want* to turn it off.
Very annoying bug for sure.
Click to expand...
Click to collapse
I totally agree, but that's what we get for giving Huawei money, clearly they don't care.
Fix the 'Ok Google' command with screen off
Add the KnockOn or Double Tap to wake/sleep feature
Two things that have really annoyed me are:
1) not being able to use the 'Ok Google' command when the screen is off and not plugged in (I use tasker and a bunch autoapp plugins to do a bunch of commands)
2) I've fallen in love with the KnockOn or double tap feature (coming from an LG V20) to wake and turn off my screen.
This being said I think I have found a solution to them both. KnockOn - Screen On / Off by Jawomo
Steps:
1) Download and install the app from the play store.
2) Configure and set all of the app permissions
3) Supposedly it works from the homescreen and lockscreens to turn the display off but the only area I was able to get it to work was down in the quick launcher section to turn the screen off (I just removed the last icon to the far right). Basically it just puts up a completely black screen so it should not drain any battery from screen use.
4) I turned off the Always On Display (AOD) If you don't it does this little stutter while the AOD comes on and the KnockON covers it.
5) If you have 'Ok Google' to be always listening then now while the screen is off (or covered in a black screen as is the case here) you will still be launched into the Google Assistant.
Hope this helps. If I get time I'll try to make a video of this to explain it better.
It keeps the phone from sleeping so it should drain battery like crazy. I wasn't even able to get ok google to work even WHILE charging =( What's up with that.
You can sign up for Google and Google play services beta, and you will be able to use ok Google with screen off once the apps update to the beta versions
Why don't you use force press the home button to wake device??? Problem solved.
Use nova launcher and configure double touch anywhere on the home screen to lock the device. Another problem solved!
Btw, I do not use ok google so i can't solve that problem
Acoustichayes said:
You can sign up for Google and Google play services beta, and you will be able to use ok Google with screen off once the apps update to the beta versions
Click to expand...
Click to collapse
Thanks, I just subscribed for google play services beta, but how can i get google beta?
Never mind just found it, thanks again! I'll try it right now.
Update: Still doesn't work, unfortunately.