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
Not sure if there is a thread on this already or not but I have gotten Google assistant to work with the exception of '' OK Google '' voice prompt.
https://youtu.be/53AE3YB4SqU
Should I post a tutorial?
It was fairly simple. Root and Xposed version 81 are required.
Yes, please.
That'll be helpful. For some reason it's not enabled even after installing AndroidN-ify exposed module on mine. I guess I need an updated Google App for that, not sure though. Looking forward to your tutorial
joseste4 said:
Not sure if there is a thread on this already or not but I have gotten Google assistant to work with the exception of '' OK Google '' voice prompt.
https://youtu.be/53AE3YB4SqU
Should I post a tutorial?
It was fairly simple. Root and Xposed version 81 are required.
Click to expand...
Click to collapse
You can get it working with the "Ok Google" prompt as well, but you give up Moto Voice.
Turn off Moto Voice and the Assistant Xposed Mod
Reboot phone
Google App -> Settings -> Voice -> "Ok Google" Detection
Set up "Ok Google" detection
Turn the Assistant Xposed Mod back on
Reboot phone
Launch the assistant with "Ok Google" and it will walk you through the process for voice detection again.
A couple notes:
If you don't turn the Xposed Mod off, selecting Ok Google settings will crash the app, and it needs to be set up at least once.
If you don't turn off Moto Voice, it will use Google Now instead of the Assistant when you use voice activation.
Wingdom said:
You can get it working with the "Ok Google" prompt as well, but you give up Moto Voice.
Turn off Moto Voice and the Assistant Xposed Mod
Reboot phone
Google App -> Settings -> Voice -> "Ok Google" Detection
Set up "Ok Google" detection
Turn the Assistant Xposed Mod back on
Reboot phone
Launch the assistant with "Ok Google" and it will walk you through the process for voice detection again.
A couple notes:
If you don't turn the Xposed Mod off, selecting Ok Google settings will crash the app, and it needs to be set up at least once.
If you don't turn off Moto Voice, it will use Google Now instead of the Assistant when you use voice activation.
Click to expand...
Click to collapse
My XDA search fu is week tonight. Can you point me to link so I can install Xposed. Thanks RS
rescueswimmer said:
My XDA search fu is week tonight. Can you point me to link so I can install Xposed. Thanks RS
Click to expand...
Click to collapse
The Material Xposed Installer is probably the easiest way to do it, if you're already rooted and have TWRP installed.
Wingdom said:
The Material Xposed Installer is probably the easiest way to do it, if you're already rooted and have TWRP installed.
Click to expand...
Click to collapse
Thanks was able to find it and install it. Thanks again. Now working on Google Assistant Do you have a link on where to start for that.
Wingdom said:
You can get it working with the "Ok Google" prompt as well, but you give up Moto Voice.
Turn off Moto Voice and the Assistant Xposed Mod
Reboot phone
Google App -> Settings -> Voice -> "Ok Google" Detection
Set up "Ok Google" detection
Turn the Assistant Xposed Mod back on
Reboot phone
Launch the assistant with "Ok Google" and it will walk you through the process for voice detection again.
A couple notes:
If you don't turn the Xposed Mod off, selecting Ok Google settings will crash the app, and it needs to be set up at least once.
If you don't turn off Moto Voice, it will use Google Now instead of the Assistant when you use voice activation.
Click to expand...
Click to collapse
Did all of those. Google assistant even comes up when I say 'Ok Google' now. But every time it goes into training mode. And the Google app still crashes when I go into 'Ok Google detection' menu. Any idea why it's so? Do I also have to update my Play services app?
Aodrulez said:
Did all of those. Google assistant even comes up when I say 'Ok Google' now. But every time it goes into training mode. And the Google app still crashes when I go into 'Ok Google detection' menu. Any idea why it's so? Do I also have to update my Play services app?
Click to expand...
Click to collapse
It is a known issue and I think it hasn't been solved yet.
Android N-ify nightlies xposed module besides the assistant brings more Nougat goodies. https://ci.paphonb.xyz/jenkins/job/AndroidN-ify/ http://forum.xda-developers.com/xposed/modules/xposed-android-n-ify-features-t3345091
Google Assistant on Nougat, Xposed not needed. Get Assistant - Root app on the Play store. It changes your build.prop for you as well as backing the old one up and tells you what to do from there. Only thing is whenever you use the "Okay Google" and assistant opens it keeps going back to the setting to train your voice. Like it isn't saving it but it will recognize your voice once you press "Do it later". Another way around is I long press my home button, assistant opens, then you can talk. Once the assistant is already open "Okay Google" works just fine.
This is running on AICP 12.1 Nightlies (Nougat)
Aodrulez said:
Did all of those. Google assistant even comes up when I say 'Ok Google' now. But every time it goes into training mode. And the Google app still crashes when I go into 'Ok Google detection' menu. Any idea why it's so? Do I also have to update my Play services app?
Click to expand...
Click to collapse
There's an app on play store called ChopAssistant that fix this issue, I use and works, check out
Isley Matias said:
There's an app on play store called ChopAssistant that fix this issue, I use and works, check out
Click to expand...
Click to collapse
Thank you Much appreciated
Anyone get this to work with the screen off and not plugged in with the charger?
joseste4 said:
Not sure if there is a thread on this already or not but I have gotten Google assistant to work with the exception of '' OK Google '' voice prompt.
https://youtu.be/53AE3YB4SqU
Should I post a tutorial?
It was fairly simple. Root and Xposed version 81 are required.
Click to expand...
Click to collapse
I have version 87 installed with assistant module and everything works including OK google hotword.
chromatica86 said:
I have version 87 installed with assistant module and everything works including OK google hotword.
Click to expand...
Click to collapse
Yeah I'm with you on that, I'm using TruePureXMM v2.9 with GravityBox, Android N-ify & Assistant Enabler and after setting up Ok Google voice detection in the Google App / Settings, and then again once within the Assistant when it first opened... It's not having 1 issue at all and isn't asking to retrain, even after a reboot and works perfectly with both Ok Google and long-pressing the home button. Outstanding!!!
I noticed on the new Google beta app 6.10.33.21 that Google assistant no longer needs chop assistant on any custom nougat Roms. The retain voice bug is gone! Happy day!
strafer69 said:
I noticed on the new Google beta app 6.10.33.21 that Google assistant no longer needs chop assistant on any custom nougat Roms. The retain voice bug is gone! Happy day!
Click to expand...
Click to collapse
Awesome!
Thanks for the tip.
strafer69 said:
I noticed on the new Google beta app 6.10.33.21 that Google assistant no longer needs chop assistant on any custom nougat Roms. The retain voice bug is gone! Happy day!
Click to expand...
Click to collapse
emimbs said:
Awesome!
Thanks for the tip.
Click to expand...
Click to collapse
Just confirmed that it is also working on my Nexus 6. Once the Google beta app is installed the retrain issue is resolved. Nexus 6 is stock rooted with assistant.
My Google assistant is now showing "can't reach Google at the moment" getting the same issue on my Nexus 6. Google now works but the assistant just quit working. Anyone else having this issue?
now that google assistant is rolling out to all devices, which is better for stock, our moto voice or the google 1?
Hello forum.
After hearing that with Xposed I was able to get Google assistant I was ecstatic. I was going to mainly use it in my vehicle for voice commands without being tied to the Google app. However, when downloading the modded Xposed module of Android N-Ify and the Google Beta app It sort of worked. When double tapping the home button I was greeted with Google search, when I said "Ok Google" android assistant prompts me to train my voice. After training my voice it goes to home screen and nothing else happens. When I go back and say "Ok Google" in the google app it prompts me to retrain my voice again. Confused, I went into the Google settings and under voice -> "Ok Google" detection it is switched off. When uninstalling the Xposed module I am able to use "Ok Google" from only the Google app itself and the Ok Google is ticked and says only from the Google app. Not sure if I am doing something wrong or my ROM is not allowing me to use it.
Relevant information:
Device: Samsung Galaxy Note 4
Provider: T-Mobile
ROM: AICP for the Galaxy Note 4, T-Mobile variant.
Thanks!
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.
Will the google Assistant work on the honor magic2?
hafensmint said:
Will the google Assistant work on the honor magic2?
Click to expand...
Click to collapse
Probably not till they release a Global Version.
hafensmint said:
Will the google Assistant work on the honor magic2?
Click to expand...
Click to collapse
I got the phone right now, seems like the app itself works but I can't enable "Access with Voice Match" to say "OK Google" from any screen, not sure why.
Although I can still say "OK Google" on the app itself.
I believe for that you need a different launcher which at this point isn't possible unfortunately.
Please if anybody got any success with enabling the "Access with Voice Match" for Google Assistant, let us know.
Cause I was using Google Assistant alot with my previous phone(while driving etc.) and now I have to press it each time.