Ok guys so the question has been asked a couple of times on XDA and there is still no viable solution. Maybe a Nexus section would be better to post and work on this.
I'm wondering if there is a solution or workaround to disable the built-in Google Voice Dialer that is launched from the lock screen when pressing the action button on a bluetooth.
When the phone is unlocked the action button on the Bluetooth typically launches Google Now, which is perfect. BUT I want to be able to Launch Google Now from the lock-screen using the Bluetooth action button, and NOT the crappy Google Voice Dialer.
The closest thing I've seen that allows this to be done so far is: Bluetooth Launch.apk from the PlayStore.
BUT this app has one major flaw.. when the headset button action is changed to com.google.android.googlequicksearchbox.VoiceSearchActivity, which is what is required to launch Google Now, the phone never sleeps/locks.
If this action>assign could be written and still allow the phone to sleep and lock, it would be ideal.
I was hoping that there would be an Xposed module to disable to Google Voice Dialer, but this has not been created as of yet.
Any help would be much appreciated and thanks will be given.
Get rom toolbox pro and take it out or freeze it. Simples
Ten min cutoff app.
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
This has just started a couple of days ago. I'll be using my phone and spot that the location icon at the top of the screen has come on, then when I look at my watch the Google assistant is open asking what I want. I have OK Google switched off so how can this be?
Me too. I have a Michael Kors Grayson.
I switched voice commands off in the Google app on my phone. The Google assistant still works on my watch. Whatever caused this bug came in the latest version of the Google app on my phone.
Any chance you are accidentally pushing the power/menu button on the watch? On mine a long press of that button brings up the assistant (even if the OK Google voice activation is off)
Since yesterday I have a seemingly unresolvable issue with the Assistant on my Pixel 3. Running Android 10 and been using swedish as the main language for a while (the issue is the same with english btw).
Stuff like setting timers, alarms, making calls, sending texts and playing music have worked fine for a long time.
Right before things went wrong I got an error message about no Google account being associated to the Assistant. I reverted it to my Google account and figured everything was fine.
Then later the Assistant started failing, and in particular to do these tasks:
- set timers
- set alarms
- make calls
- send texts.
When I try these I'm only met with the three grey pulsating dots, and no audio response or text confirmation.
Stuff that it still does, though, are:
- play music via Spotify, Google Play Music
- tell me the weather
The strange thing though is that if I set Assistant to be used without an account, it works! Also if I create a brand new test Google account, it manages those basic tasks that have stopped working on my regular Google account.
So, on Android 10, security update april 5th.
I've been trying to resolve this for 24hrs now, and frustration is growing. I've:
- tried to clear cache/data for the Google app
- inactivated it, rebooted, activated, updated
- tried the beta Google app
- tried various old versions from apkmirror -- from march, earlier in april (at a time when my Assistant was working)
- rebooted in Safe mode -- here it uses the old Assistant interface! and it actually works, but it's the clunky old one!
- checked permissions for the Google app/Clock/Telephone app/Messages -- everything seems to be enabled?
- gone through my settings for my Google account: web and app activity, location history and so on is Enabled. Personlig ads also on.
Another weird thing is that sometimes it actually seems to set a timer, but no confirmation and no notification visible. Also nothing is shown in the Clock app. But a timer beeps after five minutes -- only sometimes! Weird.
Now when I was experimenting with this I tried to set a timer, then opened the Clock app and of course, no timer was running. I then got one of those blue notification fields at the bottom, saying I can use the Assistant to set timers, alarms etc. I touched it and got an Assistant popup saying "It's not possible to reach Google right now" (translated)... Hmmm!
As you can tell, this is very weird. I would appreciate any pointers and suggestions! Thanks in advance
So this is what a typical response looks like:
https://photos.app.goo.gl/PaMGfYxAUSqAoMpZ6
And in Your Activity, it says I set a timer and got a response, but that is is simply untrue!
https://photos.app.goo.gl/VGmrP1G4KU9HE66C8
(I switched to english temporarily to try to illustrate).
So, for every one of those attempts absolutely no resonse except for the pulsating dots was shown in Assistant! :/
So strange.
I zeroed my phone completely again, and set it up with my regular Google account but WITHOUT copying apps and settings. Assistant STILL WON'T DO BASIC TASKS LIKE TIMERS.
I zeroed it again and instead made a brand new Google account: Assistant immediately performs those basic tasks.
I really need some help here, please.
OK, so I went back and disabled all the data & privacy settings in Assistant, and now it can set a timer. But beyond that it's quite useless as it can't get access to make calls or do texts etc. So I gradually enabled setting by setting, and I've concluded that the "Web & App Activity" toggle breaks my Assistant somehow. It doesn't matter if I check or uncheck the "Include Chrome history..." or "Include voice and audio recordings" boxes, if the main toggle is on my Assistant hits some kind of wall with timers, texts and calls. Beyond this I can't understand what I can do to influence this?!
Does anyone know a way to make Google assistant voice typing work?
I got stuck with gboard saying multilingual typing and no longer can enable assistant typing even though the options are turned on.
It keeps defaulting to regular voice typing. I don't want to wipe my phone just to get this stupid busted feature working. I had to do that last time this bug happened to me.
Edit: I just reset the cache and data in Google, Gboard, and set all Google voice and Google Assistant settings to one language. I also set my activity controls to one language as well. Anywhere a language was set on Google account side or within the phone settings seem to do the trick. Google makes this a insane setup to figure out.