I have a Verizon S3, am rooted, and am running Hyperdrive RLS15 (based on Touchwiz 4.1.2). I am using the Google Keyboard that is downloaded from the Play Store.
For whatever reason, the Voice Typing Microphone key does NOT work. I press the button and NOTHING comes up. If I hold the button down long enough, "Input Options" come up (where I can fiddle with Google Keyboard's input settings). Yet, voice recognition works everywhere else (e.g. in Google Now or if I press "Quick Speech Reply" in Handcent SMS, my preferred texting app). I have searched up and down, left and right, and can't find a solution.
Google Voice Typing IS checkmarked/enabled in the Language and Input menu.
Everytime I try to disable (uncheck) Google Voice Typing in the Language and Input menu, the check box will check itself again after I exit and go back into the menu.
"Google" is correctly set as the Voice Recognizer, and "English (US)" is correctly set as the primary language.
I have already gone into TWRP and Wiped Cache/Dalvik Cache, along with "Fix Permissions." None of these seem to work.
I have always done a clean install of ROM's -- never do I dirty flash.
Both the stock Samsung keyboard and Swype keyboard are "frozen" via Titanium Backup. Freezing these keyboards fixed my voice typing issue last time it occured (about 5 days ago).
Is this perhaps a Touchwiz and/or Android 4.1.2 problem? I already asked about my woes in the Hyperdrive ROM thread but no one seems to have a solution. It's so odd...
Maybe this is related? There are instances when GPS shows as Enabled on the Notification Pulldown toolbar, but Standalone GPS in Location Services is unchecked. I try to Checkmark the box, but after I close out of the Location Services menu, it goes back to Uncheck.
Then there are OTHER instances where GPS toggle is disabled on the Notification toolbar (and pressing the toggle does absolutely nothing). I then go into Location Services > checkmark the Standalone GPS feature, but the Standalone GPS box is unchecked seconds after I go back into the menu.
Thus, if I'm ever in a need to quickly use Navigation, I can't fully rely on my phone to be available because Maps will complain about not having GPS enabled. A quick reboot will usually fix the issue, but it's quite an inconvenience if you're sitting in the car and are about to leave on a trip.
WTF? It makes me wonder if I have Permission issues somewhere that I can't seem to locate or pinpoint.
Just a quick addendum...
I've already read the Google Code thread - Posts #32 and #33 are relevant in that other users have the same issues. However, my Google Search apk is always up-to-date, and as I mentioned before, "English (US)" is already chosen.
I feel as if the Voice Input Typing button (on the Google Keyboard) stops working after I disconnect the phone from my car's bluetooth. I can't verify for sure since the Voice Input Typing key isn't working right now.
Again, the Voice Input Typing button is there. But when I hit it, it does nothing. Does anyone have any thoughts or input?
voice typing not working
turn the phone off.
worked for me.
Related
I've searched here, google, etc... and the solution still escapes me
How in the world do I launch Google voice search (rather than S Voice) via bluetooth when the phone is locked? This is for bluetooth dialing and navigating (push and hold BT headset call button, say "CALL ......" or "NAVIGATE TO ......."
I don't want to flash a new ROM for this, but I'm willing to consider it IF:
- Above function works
- GPS locks are just as fast as stock
- Stability is top notch
- Battery life is as good or better than stock
- UI must be smooth
Stock ROM is great!!! I'd hate to deviate, but I hate even more not being able to use the BT dialing (S Voice SUCKS and rarely works!!!)
I have to have my phone locked (exchange server rules for my employer email)... it's a good policy anyway.
I am currently Stock Rooted, bootloader locked (I can unlock if necessary)
I've seen suggestions to use the Bluetotth launcher app, which works, but not when phone is locked.
The stock ICS has this feature. I hate the Samsung forced S Voice without giving us the alternative to go back to the google apps (which is MUCH better).
I have no clue. How about random ideas?
Try clearing defaults for S Voice and Google Search in the App Manager
Check the settings in both apps (I'm fairly sure I saw an option regarding launching S Voice from the Home button in it's settings)
Try disabling/uninstalling S Voice
Sycobob said:
I have no clue. How about random ideas?
Try clearing defaults for S Voice and Google Search in the App Manager
Check the settings in both apps (I'm fairly sure I saw an option regarding launching S Voice from the Home button in it's settings)
Try disabling/uninstalling S Voice
Click to expand...
Click to collapse
I've frozen S Voice with Titanium Backup. All that did was completely remove any ability for voice dialing through bluetooth.
The settings you refered to is a good suggestion, but only disables the home button (pressing it twice) from launching S Voice
Google Voice Search has no usable settings and I'm unable to use it as a default rather than S Voice
Have you tried to disable S voice from the applications settings menu? Certain launchers will allow to to assign actions to buttons. Not sure if BT is included.
And don't call me Shirley.
bobloblaw1 said:
Have you tried to disable S voice from the applications settings menu? Certain launchers will allow to to assign actions to buttons. Not sure if BT is included.
And don't call me Shirley.
Click to expand...
Click to collapse
Freezing in titanium is the same as disabling in the applications menu.
I feel like i read somewhere that synergyROM had this feature of google now replacing s-voice when you froze it. Ill try to find what im talking about for you. Thats the only solution i can think of.
Sent from my SCH-I535 using xda app-developers 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
I just noticed that my phone will not recognize the "OK Google" Command. I've tried trainging it by saying "OK Google" 3 tims but even then, the phone does hear me. It will hear me and recognize my words ok if i press the microphone button first and then speak. Anyone else have the same issue?
brandypuff said:
I just noticed that my phone will not recognize the "OK Google" Command. I've tried trainging it by saying "OK Google" 3 tims but even then, the phone does hear me. It will hear me and recognize my words ok if i press the microphone button first and then speak. Anyone else have the same issue?
Click to expand...
Click to collapse
Nop, works for me even on BT. Maybe you have it disabled?
so what should I do? under the screen "OK Google" detection, it shows, From the Google App=on, but the other options are greyed out. When I turn on From Any Screen, it asks me to Just say OK Google three times, and it's listening, but it never recognizes my voice even if I say it 100 times. But, I can do a voice search OK in I manually click the google microphone button.
I have the same problem. Recently bought an Idol 3 5.5, and cannot get 'OK Google' to work. Any amount of 'OK Google' commands in different accents (and by different people) are useless. I can do voice search by clicking the microphone button on Google search app. Not sure what is the problem here. How do I make sure this feature is not disabled on my phone?
Same issue here as well. It "will" work if you open the Google App first. It then recognizes commands without having to select the microphone. But yes, without first opening the google app, it does not work.
you have to add english as primary language in google settings (beside the language you use). Works for me (i am from Europe). It also works from any screen.
There is something wrong with it on the Idol 3. If you boot into safe mode, you can enable it but only from safe mode. I did this and it workd for awhile but then something disabled it again. Very Frustrating. Unfortunately, I doubt we will get any fixes from Alcatel. BTW, to boot into safe mode, press the power button and then long press on either restart or power off. I can't remember which.
like i said it works well on my and many other devices, so you have to set it right.
DallasCZ said:
you have to add english as primary language in google settings (beside the language you use). Works for me (i am from Europe). It also works from any screen.
Click to expand...
Click to collapse
Yes, it works from any screen as long as you have "previously" opened the "Google App", and, it's still running in the background.
For instance, if I cycle my phones power, and come to the home screen, "Ok Google" will not work, it simply doesn't work. But, if I open the "Google App" after a reboot, and then go back to my home screen, or any screen, it will work. You have to open that "Google App" first, or it doesn't recognize any command, because it's not "listening" / running in the background. If I "close" all running apps, which you should be doing quite often, "Ok Google" will not work, until I again open that "Google App".
The phone should "Always" be listening (provided you want to use this feature), without the need to run the "Google App" first, but that's simply not the case. To me it's just poor implementation, because it forces you to always make sure the "Google App" is running, or hit the microphone. This shouldn't be necessary. It should just work from the moment the phone has booted up (again, if you want this feature), but it doesn't.
Better implementation would have been a "service" you either turn on, or off, under settings, so it's always running (from the moment the phones powered up), or it's not running.
I hope that's clear, and makes sense?
Makes sense that that's what happening to me as well. I recall it worked just fine previously. I wonder if the recent updates did something to that interface.
I'm having the same problem after doing a factory reset and reloading everything.
It was working fine before the reset and since it will only work if I've recently opened the Google app. I've checked all of the settings multiple times, uninstalled/reinstalled the Google app, and it's still occurring.
Has anyone found any possible solutions?
(Not sure if this is anyhow related, but before the reset the flip to mute and snooze gestures didn't work at all. Since the reset, they work perfectly.)
Hi,
Just got my unlocked Pixel 4a today. No custom roms or anything. Android 11. Build RQ1A.201205.008.
I'm a bit of a minimalist, and I went through the keyboard settings for messages (it had this little emoji bar thing that also did the predictive words I wanted to get rid of). Also in that bar was the microphone for voice to txt. When I shut off those unneeded options and turned the dedicated numerical row on, the microphone disappeared. I've tried resetting the options to the best of my memory, but it still isn't back to where it was, and the microphone is still gone.
There is another microphone in the preview box, but that is a tap-and-hold-to-send-a-recording microphone. Not what I'm looking for. That works.
I checked permissions, Gboard has permissions. I checked the keyboard settings, voice to text is enabled. Anyone know the 'magic combination' of options to get this back? I use it frequently!! I'd hate to have to reset-to-factory just to restore this one feature.
Thanks!
I finally found it after much headaches. It seems the voice to text microphone is part of the "suggestion strip" that is under "Text Correction". No idea why this isn't integrated into the keyboard as it's own icon as it's been in earlier versions of Android.
If anyone has any recommendations on how I can potentially make that integration and get rid of the suggestion strip, please let me know.
I tried to reproduce the missing voice2text mic that you reported and failed.
I went to Gboard settings > text correction then:
Disabled show suggestion strip
Disabled next-word suggestions
Disabled emoji suggestions
Disabled sticker suggestions
Going back to the keyboard, the suggestion strip/stickers/GIF/clipboard/settings and the mic were all gone.
I re-enabled all the above and the mic reappeared, along with the other stuff.
One thing you could try short of factory reset is to go to the App Info for the Gboard, force stop, and clear the cache. Relaunch the keyboard to see if it brought the mic back.
---
Looks like you resolved it. I think this design change was made a few cycles ago and am not aware of any way to re-integrate it. You could try SwiftKey to see if that has the feature you want.
I think installing a different keyboard can be helpful here. Have you tried to do it? To be honest, it was one of the most significant problems that made me change a model of my phone. I did have a Samsung Note, and the problem with the Gboard was repeating very often. I have been browsing different sites to find a solution, but was never successful in it. One day, one of my sisters visited me and took my phone while I was in the kitchen. She fixed the problem instantly, would you believe it? I came to the room and was surprised after she showed me it. She said she visited https://techplugged.com/5-best-solutions-to-fix-the-gboard-not-working-error/ and followed all the instructions given there. I have forgotten about the problems with Gboard for a long time, but there were other reasons for me to change my phone to the latest iPhone.
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.