Hi guys,
I am experiencing the following problem on my LG G2 D802 with Swype German Keyboard layout:
Sometimes (about 20% of the time) when I am starting a word on the left hand side (letters q,w,a,s for example), I am getting "stuck" on the respective letter and can't continue to swype. Trying again won't help either, so I can only type in the letters/words. Strangely enough, that only happens if I am starting a word. If I am starting somewhere else on the keyboard and swype to the left hand side to use those letters, all works fine.
Closing the app and launching it again (e.g. "restarting swype"?) seems to resolve that issue sometimes.
Did anyone notice that bug or has any solution? It's really annoying. I have been using swype for years and am a big fan, but only ran into this issue since using the LG G2. With my HTC Desire HD, I've never seen that issue.
I am on stock 4.4.2, no root. This issue occured in 4.2.2 as well!
Thanks in advance for your help!
Anyone?
Related
Hi,
I've just updated to 4.4.2 and my screen is acting crazy, when I touch in one point the screen reacts in a bigger area somewhere else. For example it presses all three bottom buttons at the same time, while i aim totally different area ;/
Any one has/had the same issue ?
While I don't have the exact same issue as you, I do have some random ghost touches and gestures being"interrupted" so to speak. It's pretty annoying cleaning the screen up a bit and lock/unlock it kind of goes away temporarily only to return. I had this issue with stock 4.2.2 as well though. For whatever reason I don't exhibit the same issues on aosp based Roms. I know others have had issues with touch as well with varying degrees. Perhaps the touch screen driver in the stock kernels just don't like me. Lol. Sorry nothing that really helps but take it fwiw. Yours sounds pretty extreme. Did you have any issues with it prior to the update?
Sent from my LG-D800 using Tapatalk
So both me and my Gf have the Moto G4 Plus. For about 4 weeks now we're both having the same issue where the onscreen keyboard stops working while texting and you just have to minimize the keyboard and bring it back for it to start working again.
Her phone is only about 6 weeks old but I got mine just after launch. I've done a factory reset on mine already and the issue is still there. So any tips or tricks anyone can suggest?
I'm using the stock messenger app and the stock keyboard on both phones, just an FYI
I can confirm this bug with Gboard.
It didn't happen when it was just Google keyboard. Sometimes, the glide to type and auto correct also stops working.
Sent from my Moto G (4) using Tapatalk
I have the same issue on stock rooted marshmallow, and my wife has the same problem on 100% stock unrooted. Hopefully Google will fix it soon. The problem does not occur with other keyboards.
Confirmed on stock g4+, random bug
I have two moto G4 Plus, both are stock and demonstrating the same issue. I've had it happen in my email, but 90% of the time it is while texting. Also happens with two other kboard apps, not just Gboard.
I've read some reviewers complaining about this problem in some reviews of the Yotaphone 2 around the web, but couldn't find anything related in this forum, so...
Is anyone here having problems with the keyboard lagging while typing text? As if the device didn't have enough power to process the character hittings and ends up queuing and eventually missing some of them. I've been using the default Google Keyboard, but this problem is regardless of the keyboard application I use, and is just driving me crazy.
I'm still on Kitkat as it is my favorite Android, but it's so frustrating typing on this device I am really thinking of upgrading just to see this issue gone. Has anyone already experienced these lags? Can anyone confirm that this has been addressed on Lollipop?
The problem is RAM related. Chheck wich application use more RAM in your device and try uninstalling them.
Turns out it is not RAM or processor related, it is a touch sensitivity issue. Actually, according to people responding to the reviewers mentioned, it is not even an issue, but a feature, as it was apparently meant for glove usage (Russian smartphone, makes sense).
And I find it to be the case. If I take care to lift the finger enough from the screen between character hittings, the "problem" goes away.
So....looks like the solution is to tweak the screen sensitivity somehow, or to learn how to live with that once knowing what causes it.
Just to report some findings:
My device was running the RU 4.4.3 firmware when I was coming across this problem. Now with the EU 4.4.3 version, this overly sensitive touch is gone.
So this "glove mode" is definitely something from the russian firmwares.
i have no problem with batter drain and so on after upgrading to nougat since the first day i bought this phone.
but i have a problem with the touchscreen. lets say for example i was using unified remote, and im using the mouse and keyboard feature to control my cursor on my laptop. but i noticed that when i try to move the cursor even when my finger doesnt move a muscle, the cursor on my laptop are like stuttering or vibrating should i say. its like my finger is vibrating on my touchscreen but its not, my finger doesnt even move.
is this a hardware issues? or just a common nougat issue?
my z3 is rooted, unlocked bootloader and still on 1701.8, upgrading it to 1701.13 might probably fix this issue.
this is a minor issue and doesnt conflict with my everyday use, but it bugs me sometimes lol.
Yeah, I've noticed the same thing. I haven't found any fix for it yet.
Just picked up an Android version, touch pad... Is it just mine or are they all wonky like this? Random vibrations, half the time it thinks I'm clicking something, scrolling is just ridiculous.. This can't be how it was designed, is it?
The trackpad shouldn't be behaving like that. I was describing the YB (on MacRumors of all places) and how well it worked but another member complained about the same symptoms that you described. Their issues were resolved by updating to Nougat. I suggest doing that if you haven't already. If the problem persists after that, try a factory reset.