Hey everyone. What is the service that controls handwriting to text recognition? Since rooting, that functionality is no longer working. I wanted to make sure I didnt inadvertantly freeze it in TBU.
Anyone?
Related
Hi everyone,
I have noticed hitting the mic button does not do anything on swype, but on the regular multitouch keyboard i can dictate messages using the microphone.
Does anyone else having this? I did root my phone and deleted some bloatware apps but don;t think it can cause this.
Is it turned on? I turned mine off and it doesn't do anything when I press on the microphone button.
needs vlingo crap
Found other posts that the swype provided by motorola is hard coded to use vlingo.
I imagine that this, like my other problems with my n4, is likely to be the result of my tinkering more than the phone itself... But seeing as I'm not terribly skilled, and I don't as much time as I'd like to fiddle around with my phone... I'm reaching out to the hive mind.
One of the problems thats annoying me the most right now is the voice to text button on the google keyboard. Namely it isn't doing anything. No error message, no change to the helpful microphone shaped circular button waiting to convert my dulcet tones into words... nothing.
To be honest I'm not entirely sure when this began, because its not a feature that I used frequently, unless alone in my car at a stoplight or something and I want to slam out a quick text. The mic still works fine, and gNow has no problem triggering and responding to me - it just seems as though the action is never triggered by the button.
I'm currently running KK, bootloader unlocked, rooted, xposed framework, gravity box, and a few other smaller modules (dictionary blacklist for example). Minimal rooted applications such as titanium and tasker, but nothing fancy is being done with them (didn't deepfreeze any system apps or set up any related tasks). The keyboard app is the google one with only small tweaks that are built in like the blue trail and shorter longpress time. I have offline voice to text set up, and this issue is present on wifi or network regardless.
Any tips? has anyone had this problem before? can anyone point me to a potential culprit or a way of finding one?
Can't find the predictive text in the settings. Do you guys have that feature?
Well, this is pretty weird behaviour, and I spent a number of roll-backs of my phone suffering from same one, until I found the root cause of it. Go into Settings->Accessibility, and scroll to the bottom section, Services. Whenever you have some app there marked as ON - your keyboard gets limited in functionality, dunno why. I have 2 apps there, and I disabled both of them, to have wider options for my keyboard.
Hope it helps.
creage said:
Well, this is pretty weird behaviour, and I spent a number of roll-backs of my phone suffering from same one, until I found the root cause of it. Go into Settings->Accessibility, and scroll to the bottom section, Services. Whenever you have some app there marked as ON - your keyboard gets limited in functionality, dunno why. I have 2 apps there, and I disabled both of them, to have wider options for my keyboard.
Hope it helps.
Click to expand...
Click to collapse
Wow, it worked. Thank you so much!
It seems like only some app will cause the problem. Optical Reader from Samsung will only disable my keyboard features, out of 6 apps.
UPDATE: I can now reorder my edge panels after disabling it.
OMG.. finally got my predictive text to work again. I turned off optical reader in accessibility and viola. It instantly returned!!! Thought I would never get it back!
Sent from my SM-T817W using Tapatalk
Using the stock keyboards voice input option defaults to Samsung Voice Input instead of Google... no problem right? I just go in and turn off the Samsung voice input and voila! google becomes the voice input! See image
Then with out warning or notifying, by the end of the day it is turned on again and becomes the default voice input for the keyboard..
And, right now it SUCKS, not even close! see the 2 screenshots.
any how is anyone else noticing this?
dave
Same here. I was able to solve it by using Package Disabler Pro and disabling Samsung voice input. It stays off that way.
This is not new. It's been the case for a few years now. I could never disable voice input or the Samsung keyboard.
Hi, so I bought the Adonit Snap stylus today and it's working okay. At least it doesn't have the friction capacitive styluses develop eventually.
However it does not register on the fingerprint reader at all. It that thing not the same kind of touch screen? It's pretty inconvenient because of course it also serve as the home button.
Otherwise writing with this thing on the GBoard is a real breeze.
Any idea on making it work with the fingerprint reader or working around the limitation otherwise?
I thought about remapping keys but all apps doing that need root or accessability services which I don't want to use because I want to be able to encrypt my device.