Hey all,
Recently installed Sultan's CM12.1, with PICO Gapps. I am missing something I use a lot, which is voice-to-text texting. As in, I press the microphone button on my keyboard and begin speaking, and the words appear as I;m talking. As it stands, only a small window with a microphone pops up, listens to my whole message, then bings away and places what it thinks I said into the text box. Which app am I missing?
(It also does not appear under the IME switcher, and usually does-- haven't used PICO prior to this flash.)
Related
I have Cyanogen's 4.2.3.1 installed with the 2.0 Maps application and Navigation works correctly for me.
Since I installed Navigation I am getting a huge "Double tap to answer" button that pops up on my screen when a call comes in.
A) It seems to have shortened the amount of time my phone rings before sending to voicemail
B) The double tap is flaky
C) It looks like ****
I have searched Google and the forums to see if this was an issue people had but can only find people talking about the in-call unlock screen.
Does anyone know why this is happening and how to stop it?
answered in your other thread.
Hi all, been lurking for a while but thought I would finally post up.
Having an issue with my Nexus S on stock ROM v2.3.3. It isn't the same issues with the keyboard disappearing etc but it is an issue with the keyboard not inputting text when I type.
If I am typing a SMS reply to someone on my phone and I pause for a few seconds (to talk to someone for example) then I try to continue typing, the keyboard acts like its typing but does not actually type anything else into the message. The only fix I have managed to discover is exit the SMS so that a draft gets saved then once I go back into the message it works again.
Don't know if that is a clear enough description but if anyone else has any suggestions or even a fix for it then it would be greatly appreciated
Thanks
Yeah I have that too sometimes. What also happens to me about every week is, that the smiley sections' and the (particularly important for me since I'm from Austria and using the German keyboard ü-ö-ä) special buttons and symbols' pop up extension (hard to describe, but I mean the thing that pops up when you put your finger on the expandable tile for like 2 second and which let's you select the unusual symbols from a list) simply will not pop up. So it would make it impossible for me to choose from the pre-created smileys etc.
I have found out that changing your input method to another keyboard (I use SwiftKey in these cases) and then changing it back Android keyboard make the problems disappear. But they seem to come back regularly and I haven't found out what causes them to appear...
Any help?
Hello,
Problem #1: Voice Actions and Voice Dialing are not accurate, especially in French. Plus, I drive around a lot so this is significant (read: safety and fines).
Solution I have so far: installed Nuance VSuite 3.2 extracted from some Motorola phone as per http://forum.xda-developers.com/showthread.php?t=943688
The recognition works beautifully, but...
Problem #2: I can start the app with my Bluetooth headset's button, but only if the screen is on (the phone can still be locked). If the screen is off and I press the button, I'll hear the headset's speaker turn on, then off shortly after. The screen also flickers in a similar fashion. Only when I press the Power button on the phone will the app launch...
So my question: is there a solution to this delayed start/screen flicker?
Things I've tried/checked already:
-As of writing this, there are no voice recognition apps whatsoever on the market in French. (And few in English, but that's not really an option here.)
-There are phones with VSuiteApp 4.x instead of 3.2, but my attempts at making those versions work have not been successful yet. (I have: Motorola Droid X and Samsung Fascinate both stock and deodexed) The best I've managed was for those apps to start and disappear immediately. Force close didn't work?! I'm not sure if my problems are due to the app having been created for an older version of Android or missing framework files...
Thanks in advance,
Darkshado
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.
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.