Possible Fix For Touchscreen Issues/Misses (Updated 08/29)

[davy917]

Just edit with es file Explorer.

And get the build.prop in the system folder. Not the other one.

FYI the way you have it written, the last line in the first touch section is being commented out. The part after the closed parentheses needs to be on a new line.

Sent from my LG-H811 using Tapatalk

 

[*justintime*]

FYI the way you have it written, the last line in the first touch section is being commented out. The part after the closed parentheses needs to be on a new line.

Sent from my LG-H811 using Tapatalk

Thanks great example of the placebo effect then. [emoji3]

 

[RidinNerdy]

Thanks great example of the placebo effect then. [emoji3]

Thanks... See what i mean... I wish the OP would be a lil more instructional for dumb newbies like me ?
half of us probably think its in effect and we probably put it in wrong... Because i dont feel the difference...


Sent from my LG-H811 using Tapatalk

 

[*justintime*]

I don't know I still do think that tap to wake responds better.

 

[RidinNerdy]

I don't know I still do think that tap to wake responds better.

?

Sent from my LG-H811 using Tapatalk

 

[sparksj3]

FWIW, I've never had any results from the other fixes posted. My test is always to open Facebook or Twitter and start scrolling. Usually, while scrolling, any number of posts will open or "like" buttons get clicked. So far, its been a pretty reliable test to see if any results are real or just placebo.

After adding these lines to build.prop, Facebook scrolling and Twitter scrolling work fine. I've only been using for a few hours, but as yet, I've had no accidental clicks while scrolling.

Thanks, OP!

 

[mcnick0495]

FWIW, I've never had any results from the other fixes posted. My test is always to open Facebook or Twitter and start scrolling. Usually, while scrolling, any number of posts will open or "like" buttons get clicked. So far, its been a pretty reliable test to see if any results are real or just placebo.

After adding these lines to build.prop, Facebook scrolling and Twitter scrolling work fine. I've only been using for a few hours, but as yet, I've had no accidental clicks while scrolling.

Thanks, OP!

No booting problems? And how did you go about putting it in your build.prop? Was it a simple copy/paste in the very end of the file? Or was there something extra needed?

I haven't gone as far as to adding text to the build.prop before, so I want to be sure its done right.

 

[RidinNerdy]

No booting problems? And how did you go about putting it in your build.prop? Was it a simple copy/paste in the very end of the file? Or was there something extra needed?

I haven't gone as far as to adding text to the build.prop before, so I want to be sure its done right.

Yes can someone post a proper screenshot?

Sent from my LG-H811 using Tapatalk

---------- Post added at 05:14 PM ---------- Previous post was at 05:01 PM ----------

FYI the way you have it written, the last line in the first touch section is being commented out. The part after the closed parentheses needs to be on a new line.

Sent from my LG-H811 using Tapatalk

Is this the correct way? Because i feel no difference...

Thanks in advance!

Ps: yes, i rebooted to take effect

Sent from my LG-H811 using Tapatalk

 

[Animatorman]

Nope, needs to be exactly like the OP

 

[sparksj3]

No booting problems? And how did you go about putting it in your build.prop? Was it a simple copy/paste in the very end of the file? Or was there something extra needed?

I haven't gone as far as to adding text to the build.prop before, so I want to be sure its done right.

I used ES File Explorer with the Root Explorer option enabled. I just opened up the build.prop in /system/ and pasted the "touch" and "touch related" sections to the very end of the build.prop. Make certain that the line breaks are exactly as shown in OP (those won't copy over from the clipboard), and eliminate any extra spaces that might crop up during the copy/paste. Then, save and reboot.

 

[uly609]

I emailed my self a copy of my build.prop. Then edited on a windows machine using NotePad++. Copied and pasted from the OP. Then sent back to myself and renamed the unedited version build.prop.bak and replaced with the new one. also make sure permissions are set to 644 or rw-r--r-- or you could have a bootloop.

 

[RidinNerdy]

Nope, needs to be exactly like the OP

This didn't do anything either

I dont understand whats going on... Still misses touches

Sent from my LG-H811 using Tapatalk

 

[Animatorman]

Yeah, I'm not saying it cures the problem but in order for it to even possibly work it has to be exact. My opinion is it seems to sometimes help but I can still reproduce very specific problems.

 

[Harmtan2]

This didn't do anything either

I dont understand whats going on... Still misses touches

You've got the last line of the first set wrong. The stuff after the parenthesis, needs to be a new line. It doesn't cure the problem altogether, but has made it a better experience. Less scrolls being registered as taps on Facebook.
Sent from my LG-H811 using Tapatalk



Sent from my LG-H811 using XDA Free mobile app

 

[mrwinkle]

Here is mine and it seems to be working.

 

[Harmtan2]

This has made knock code usable. Previously I couldn't use it at all. So thank you OP!

Sent from my LG-H811 using XDA Free mobile app

 

[Mr.Miyagi555]

Did anyone try out the OP's Nexus* 4 touch settings in the build.prop? and what is the #xTreme G4 TWEAKS i see in some of these build.props?

i was googling LG G4 build.props and came across this from pocketnow.

Another tweak that’s no longer used the way it was previously has to do with windowsmgr. Modern builds of Android lock the “smoothness” to 60fps. The FPS multiplied by 1.5 gives you the recommended value of this setting. Many sources still suggest setting this to 300 or even higher to help make things look “smoother”. That’s no longer the case, so setting this value above 90 (60 * 1.5) will likely result in higher processing demands with no visible improvement – and will probably slow you down.

windowsmgr.max_events_per_sec=90

Is there any validity to this? The OP has this line of code in the ##### touch related ##### section.

 

[Animatorman]

They're settings from a Nexus 4 and I'm using them now.

 

[chrisokaly]

I can say this definitely does SOMETHING.... Prior to the mod, the app "Yet Another Multi Touch Test" would crap out after 6 touches. Now i can get it to register all 10.

Will have to monitor if there is any effect on battery life, but so far, big time +1

 

[AegisValour]

I can say this definitely does SOMETHING.... Prior to the mod, the app "Yet Another Multi Touch Test" would crap out after 6 touches. Now i can get it to register all 10.

Will have to monitor if there is any effect on battery life, but so far, big time +1

**** man, I'm failing at 6 as well. My device is not rooted as I was considering sending it back for warranty. Please let us know after some testing. I mostly want to know if the swipes registering as taps still occur as frequently if at all.