Closed davebuk closed 11 years ago
This is a tough one, since it depends entirely on external binaries which we have no control over.
The best we can do is trying to figure out what happens, and if something doesn't work, try to guess from the data at hand what fails, and adapt the ROM/gapps to see if your change tickled the binary in the way it needed to be tickled.
Basically lots of work.
And for me, 4.2.2 gesture-typing is not really a priority, because I tried it on my Galaxy Nexus and it was extremely inferior compared to SwiftKey (which I've already paid for), so even on my Galaxy Nexus I've decided not to use it, because it was just too much work correcting the bad/inappropriate suggestions and interpretations of my gestures.
If someone can provide a pull-request/patch or good leads for how this can be fixed, I'm all open ears, but until that happens, chances are this is just one of those things which wont get fixed.
I can understand your reasoning and it would be a low priority fix. I do use it on my Nexus 4, but only because its there, it works really well.
Is there a possibility to leave this issue open for a possible future fix and make as a possible enhancement?
Whoever comes around with a potential solution has my attention. I just doubt, even if I had the time, I would be able to fix it. So not sure how much sense it makes to leave it open either. That way you are signalling to people skimming the issue-list that it's getting worked with, when it's not.
And closed issues can always be reopened. I'm not sure what's the best approach here.
I'm happy for you to close it. It would be nice to have working but no where near an essential fix.
Tim says it can't be done: http://forum.xda-developers.com/showthread.php?p=38914273
I trust Tim. Closed :)
Agreed. ;-)
SWYPE (http://www.swype.com/) works very well as an alternative.
SwiftKey is my favourite replacement-keyboard, but yes, there are definitely options to the Google-one. I honestly found that to have very inferior prediction anyway so I'm not using it, even on my Galaxy Nexus.
Just to wrap up, the new Google Keyboard, released on the Play store, fully works with this ROM since June 2013.
Thanks. Retagged issue and added it as a known workaround.
I believe this is possibly a problem with all non nexus 4.2.2 ROMs, but can the gesture typing with full on screen keyboard functions be fixed at some point?
Workaround available: Install Google Keyboard from Play Store