[G4 General] porc1:
How would a keyboard update fix it? Swipes are being interpreted as taps, which isn't a problem when using a keyboard. (I want my taps to be taps, yes! That works!)

---------- Post added at 03:07 AM ---------- Previous post was at 02:47 AM ----------

Sorry I'm late to the fun, but I just learned of this thread. I bought my G4 the day it came out from Best Buy. It is the H810, AT&T version. It was working perfectly until about 10 days ago when I woke up to discover a system update had been pushed to it. I've tried all the suggested fixes, even factory reset; nothing helped. There have been a couple brief periods a few hours long where the problem 100% goes away, only to reappear just as bad as it ever was.

I don't see a problem with "missing" taps. It seems to get nearly everything, with the possible exception of that knock feature to wake it. It misses knocks every so often, even from day one, but I wasn't sure what was going on and I didn't worry about it. That had been my only problem.

What I do have is that attempts to swipe are randomly interpreted as taps, so it navigates into links or forum posts, opens up Facebook posts, clicks Like on Facebook posts I actually would be embarrassed to like, etc. I'm pretty sure this is a software problem.

I can't detect any sensitivity problem with the screen, or any issue registering touches. I installed both Multitouch Test and ScreenTouch Test, and also used the built in Quick Memo. Everything was PERFECT there. No missed touches, no matter how light or brief. I spent a good amount of time pecking and swiping the screen in Multitouch Test, at all places on the screen. All was well, every time.

So, I then experimented with where I saw the problems, most notably Facebook and Tapatalk as they require lots of scrolling by swiping. In FB, I was on purposely concentrating on trying to begin a swipe at the location of a Comment button; if a swipe is interpreted as a tap, it would go into that post.

Anyway, here is what happens when it works: I touch the Comment button and keep my finger down; the button becomes gray because it knows a finger is pressing it, but the button does not commit to the action yet; it waits and sees. If I release my finger without having moved it, it knows this is a tap and it then goes into the FB comments. If I instead start swiping my finger away from the comment button, the comment button un-grays and the button is not accidentally pressed. It begins the scrolling operation.

Here is what happens when it doesn't work: I place my finger onto the comment button, and instantaneously it goes into the comments as if I had completed the button press. It is so fast that the button doesn't even have time to become gray; it just goes wham, right into the comments while my finger is still on the screen. This will happen both for light touches and for firm and really hard presses. I don't have any weird personal issues going on here where my skin has lost capacitance or something. Any type of touch does it. And no, I'm not accidentally lifting my finger up for an instant and then putting it back down. It's correct, and plenty firm.

For about 12 hours, this was working for me after I tried Screen Booster app. But, then it stopped working and I have not been able to get it back into a working state with that app again.

All this tells me it is a software problem. Something in their implementation is not bothering to wait for my finger to either move or lift back up before it decides the touch is a tap or not. Does anyone know of a secret way to affect some internal settings on how it determines when a touch is a tap or not? e.g. on Windows, I can set the double click speed for a mouse. On Android, I want to tell it to not conclude it is a tap unless my finger is released for 2/10th of a second.

Any suggestions would be much appreciated! I'm very pissed that I bought this thing. At the same time I bought this, I bought my wife a G2 for just $175 and it is working perfectly. And, it is nearly identical to the G4. I am severely regretting buying this expensive very buggy G4.