yashsingh1/xdaforums huggingface dataset:
[G4 General] joshuadjohnson22:
A couple things would have to line up perfectly for this to happen... and it still would be questionable:

1. Partitions would have to be exact

2. It would have to be compatible with the kernel (hopefully the fix is not in the kernel cuz unless the hardware is identical we will have to use ours)

I'm not dev so this is just what I understand, if these things aren't right it may result it bootloop, force closes or security errors. Hopefully [MENTION=316800]diedemus[/MENTION] can get a return to stock set up, if that works we may have a shot. He may even be willing to try it out since he seems to know what he is doing.
[G4 General] kaiowas82:
the 10d rom fixed all my issues with touchscreen... h815eu here
[G4 General] joshuadjohnson22:
Great, glad that more updates work. Can you register more than 6 touches at a time without the freak out?
[G4 General] Mr.Miyagi555:
These missed taps is probably the most digusting thing about this phone. I dont understand how QA could have missed this problem.

Another thing i seen in a thread and verified myself was the max processor speed my phone uses is 1.4 ghz on bbs. Can someone else confirm this too?

---------- Post added at 08:54 AM ---------- Previous post was at 08:52 AM ----------

After i random freak bootloop i dont want to put xposed or tweak the build prop yet. It doesnt seem likely that we are going to see some update from lg for this screen issue? I know its most likely hardware but couldnt they tweak the software to soften the blow?
[G4 General] asce1992:
I'm on v10c (815) and i have the same problem..max 6 fingers.. I hope LG will make new release for our phone..
[G4 General] kaiowas82:
honestly, i don't know and i don't care much... i think in 10 years of smart phones i never needed to use 6 or more fingers on the screen at once.... all i had was swipes registered as taps, that's gone and I'm happy
[G4 General] joshuadjohnson22:
right but it is not about having more than 6 fingers, if your phone freaks out then the touch is not 100% fixed on the phone. It is simply the easiest way to tell if it is resolved. If it glitches out at or after 6 you know it may be improved but not resolved. When plugged into the charger we have no issues but off the charger it goes wack.
[G4 General] xgerryx:
upon testing mine, after adding the suggested text to the build.prop and doing the su command with -10, -50, -80, -100, it still goes all whacky after the 7th touch. So it only registers 6. Ideas? I'm rooted and definitely did not take the OTA people are talking about. I'm also on the VZW variant 11A.
[G4 General] vegetaleb:
Hello, bought my G4 yesterday and I really liked this phone,I don't have touchscreen problems for knock or double tap to wake, nor while swiping from a menu to another. Though I had some missed swiped down status bar to see the notifications and eqs, same for a couple missed touch on the navigation icons.

I did a test in the service menu called draw touch test, and the crazy results are that all 4 borders of the screen with about 3mm are not registering light and fast swipes, I had to do slow and harder swipes to be registered. So is that making my screen counted as having the same problem or it's a screen choice by LG? I remember a website publishing the same results with s6 screens, borders have much less sensitivity. So should I ask for a replacement or it's normal on all G4? Would the 10f posted in this forum will help?

---------- Post added at 11:48 PM ---------- Previous post was at 11:37 PM ----------

Oh I forgot to mention I have a tempered glass on the screen, could it be the culprit?
[G4 General] joshuadjohnson22:
It seems like you have the same issue we all have. I would wait for the update to resolve your issue. You have 12 month warranty to send your phone back if it really has a defect so I wouldn't be overly concerned. The issue happens irregardless of a screen protector (plastic or tempered) so I will wait. I am hoping someone will eventually turn the 10f update into a rom for all but so far I haven't seen it. If your device matches the ones who have the 10f au you may be able to flash that but I'd read about it before flashing anything. You may want to install one of the multi touch apps to see if it goes crazy after 6 fingers are on the screen, this will confirm you have the issue. I use antutu app just open it and click "screen test" -> multi-touch test. Make sure it is not plugged in and sitting on the table and start placing all your fingers down one by one and see if they go crazy after 6

Welcome to the family :)
[G4 General] vegetaleb:
The thing is that I bought my G4 from grey market, I have only 1 week for returning it, it's weird I have no problem with missing touch,swipe but on the status bar and sometimes with navigation bar. I never had any problem with double tap to wake or sleep or knock to wake. So it's either the cheap Chinese noname tempered glass messing with my screen borders or LG chose a bad digitizer , meaning a hardware problem. BTW plugging the charger won't change my borders problem. I will take off the tempered glass to see if it will solve it.
[G4 General] asce1992:
Please, Can you also confirm the fix making a new test with antutu app? :) i'm on v10c (H815 european version) and after 6 fingers the screen starts "flashing".. If i do the same test on power no problem ( all 10 fingers)!

I want only know if v10f fix all the problems! Thank you :)
[G4 General] vegetaleb:
Taking ou the tempered glass fixed my status bar sliding down as well as navigation panel buttons, now 99% of the time it's working, I will do the antutu test later but all I can say is that I have nothing to complain now in real usage. I just need to make the battery percentage icon bigger in statusbar, it's stupid that with all this screen state it's smaller than on the m9!!
[G4 General] joshuadjohnson22:
Easy fix with root and/or xposed ☺ . Good to hear!
[G4 General] Daemos:
It's strange MS7 has stated that there is no change between 10D and 10F

see: http://xdaforums.com/g4/development/h815-eu-l-p-t-sea-twn-t3176195/page11#post62533124

However, I am trying to get clarification, he may be just talking about the system partition, and the fix could be in the kernel.

There were multiple touchscreen issues with the oneplus one, and the fix was in changing the drivers in the kernel.
[G4 General] shag_on_e:
Hey guys I wanted to update you with some new info I've found. My mother has the G3 which has had no problem until recently after taking the latest system update. Now she is having the exact same touch screen issues we are on the G4. I'll re-post later with the exact update version, and tests with her phone, but this is a good sign, in my opinion, since obviously it is a software problem on hers, it may be for us also.
[G4 General] vegetaleb:
I did the antutu test, I could get up to 8 but I didn't try it seriously with more as I am at the swimming pool lol. One or 2 of the circles were flashing in the end but I think it's how the test behaves. The screen is very usable outdoor under the sun BTW :)
[G4 General] nussie:
The only reason I rooted my G4, and it makes a huge difference! Double tap to wake working every time so far, and display test registers all taps.
[G4 General] mrjasenr:
I switched to a 3rd party launcher until LG gets their head out of their asses. Zero touch problems now.
[G4 General] asce1992:
So you have our same problem! :D in charge there is no flashing!

[MENTION=2000075]nussie[/MENTION] which version of firmware?
[G4 General] laurasaurisrex:
I got all 10 touches on the charger, off the charger, and off the charger with and without Battery Saver turned on. I never seemed to have a multi touch issue. Mine is touch lag. I use Battery Saver 24/7 now, which fixes it. I have a Verizon G4 on 10b.
[G4 General] vegetaleb:
Did the test again, without charger it took 10 fingers and no flashing
[G4 General] joshuadjohnson22:
What software version do you have
[G4 General] vegetaleb:
10c H815 NDL
[G4 General] mrxjhsnx:
Strange, that seems to smooth out my touch lag too
[G4 General] Johnny Broccoli:
I've found the outdoor in the sun visibility to be pretty bad with this phone myself. If I don't have it at 95%+ it is hardly even usable. My old Nexus 5 performed better in the sun.
[G4 General] nussie:
Hey, it's the H-815P - South African version, with firmware V10a-ZAF-XX. Touch misses was horrible before the editing of the build.prop, most especially on the double tap to wake.
[G4 General] nyt:
Flashed the new N firmware for the h811. I'm not seeing any touch issues.
[G4 General] DsturbD:
Off topic real quick but can you still do the oem unlock in the Developers Options on 10n?
[G4 General] nyt:
looks like it
[G4 General] Daemos:
Thank you for the update!

For the new touch screen fixes, do we run those along side the older build.prop fixes you had posted before? It seems like some of the parameters would be repeated and have conflicting values with each other if both in the file and in build.prop

Secondly: It's strange that the LG g4 runs better with low entropy rather than high, as people were finding on other devices that a higher entropy = less lag. If we do not have an init.d folder do we just make one and then make a new file with this code inside:

echo 16 > /proc/sys/kernel/random/read_wakeup_threshold
echo 16 > /proc/sys/kernel/random/write_wakeup_threshold

and then link it to busybox using your code? Does the file inside the init.d need to have a specific extension or file name?
[G4 General] xgerryx:
I also did not have that folder inside the idc folder. I made one and added text to it. But I'm not sure if this is right. Also, just for those of us that don't deal with terminal very much and stuff, maybe someone could give a quick summary of steps to encompass the newer methods. The touch issues persist for me. Making a very dismal experience.
[G4 General] mcnick0495:
What I would prefer is that someone who has touch issues on a model with a custom recovery, to flash another ROM and see if the issue persists.

Because my LG rep told me it's software and a fix is in the works, I'm gonna believe that there is no hardware issue. And hopefully because of this, a custom ROM will fix the issue. I'm just waiting for an exploit like BUMP! for the G3 to come around.

But back to topic, I notice that my issues get worse throughout the day. When my phone comes off the charger once fully charged, the touch issues are very minimal, and for a while too. But a couple hours later the issues will get worse and stay worse for the rest of the day.

I'm a little uneasy with getting into the updated section of the OP, so unless we get a step-by-step guide on what to do exactly I'm gonna hold off on that for now.
[G4 General] nussie:
Still on the build.prop fix, but the issue unfortunately seems to come and go. Initially I thought it was sorted.
[G4 General] chriskwarren:
Folks are reporting the in Canadian thread on here that the latest 10f update for our models fixes the issue.
[G4 General] nussie:
I get 8 touches registered with antutu, 9th makes it go crazy. I then thought the screen brightness might have an influence, but 100% vs the lowest gives the same results. Still my experience is definitely better with the build.prop edit. V10a-ZAF
[G4 General] xgerryx:
Is this worth taking the OTA and rerooting? Or is that not even possible on VZW?
[G4 General] Johnny Broccoli:
Sounds like the OTA isn't even available for most carriers and countries.
[G4 General] chubbrock:
I'm also curious, do we just do the new file modification by itself or in conjunction with the build prop edits?
[G4 General] shag_on_e:
I created the .idc file and placed it in /system/usr/idc and there is still some touch issues, but it seems like certain areas of the screen are not affected than others. I notice most of my touch problems in game play. So now that there is OTA releases "fixing" the touch issues, is there any way to find and pull the changes from those builds?
[G4 General] chubbrock:
[MENTION=6847891]shbang[/MENTION] do we do both the build.prop edit and the new idc edit together, or just the new idc edit by itself
[G4 General] nussie:
Update: I unrooted my H815P, v10a-ZAF then OTA'd to version 10e-06/07/2015. 10 touches with antutu flawlessly, no facebook accidental taps instead of swipes, and so far double tap to wake works everytime. I haven't made any changes to my build.prop or created a .idc file. Under the manual screen test, still some missed taps though, but I haven't experienced it under real world conditions. Will report back after a day or so of usage. Hopefully I don't have to return the phone, since I really like it.
[G4 General] Johnny Broccoli:
Nice. Really looking forward to hearing U.S. variants will be receiving that update though.
[G4 General] mcnick0495:
I want to share what I found, considering it has helped a bit with the issue. The missed taps and all still happen, just not as often before I made these changes.

WARNING, do not adjust values that you are unsure of. Setting any of the following values lower than default will cause touchscreen issues.

You will (obviously) need root.

I downloaded Kernel Adiutor from the Play Store (link: https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor), and changed a couple values pertaining to the CPU. Here's what I did and how you can try it out too:

1. Open the app, open the hamburger menu and select "CPU".

2. Scroll down until you get to the "CPU Boost" category.

3. There are two values you're going to change here.

A. Input Interval: Default is 40ms, I changed mine to 150ms

B. Input Boost Frequency Core 1: Default is 1248MHz, I changed mine to 1440MHz

4. Be sure that "Apply on boot" is checked at the very top of the screen.

For those here who know a little bit more about these values, and others surrounding the CPU itself, I'd recommend messing with these settings as opposed to adding system-level files to the device which could cause a boot loop if not done correctly.
[G4 General] G41LAH:
Lost noob

Call me a noob, but could you be so kind as to upload the file that needs to be edited? Im afraid of bricking my phone again(bricked when rooting:(). I read the first post scratching my head, and I feel more comfortable running flashfire or just replacing the file, a guide would be nice. Forgive me if I offended anyone, just being cautious. Im on ls991 if it matters.
[G4 General] chubbrock:
Which variant is this for? Do you need an unlocked bootloader? Will this work on the VS986?
[G4 General] DsturbD:
This works pretty darn good. I have no other changes from this thread applied and did this in kernel auditor and it vastly improves touch. I also applied the same settings to the first 2 (Interval and Sync Threshold) will keep an eye on temp and battery drain. Nice find!

This should work on any variant as long as you have root
[G4 General] xgerryx:
So with the .idc file created and the code we had previously used in the build.prop file pasted into it, my touch issues seem to have been reduced dramatically.

So as a quick step by step for people who found the other posts a bit hazy:

Using ES Explorer I navigated to Device>System>usr.

Once in usr there will only be 2 files there. You need to create a 3rd file called "touch_dev.idc"

Once you created this file you need to open it in order to edit and add text.

Tap the new file, hit text>ES Note Editor

Once inside you can paste the touch and touch related sections we have been working with in this thread.

Not sure if rebooting is necessary but you might as well.

As a side note, I did leave a redundant version of this at the end of my build.prop. Prob not needed but I'm leaving it for now.

Hope this helps someone.

Screens for reference sake
[G4 General] chubbrock:
Confirmed working on verizon rooted VS986! Does make a big difference!
[G4 General] G41LAH:
Wow that was simple, thanks!

This works for me too! Only thing is, I can't get "apply changes at boot" to stick. I get a message that says changes applied, but when I check they're at default values.
[G4 General] mcnick0495:
If you back out of CPU settings and go back in, they should show as what you set them to. But, when you reboot, they do go back to default (mine does the same thing too). Not sure if its a bug with the app or something else.
[G4 General] DsturbD:
you're right, mine does that too, but the other 2 that i changed stay after a reboot (Interval and Sync Threshold). but touch still seems to be better, dt2w is far better than it used to be
[G4 General] rickmatic:
[MENTION=4111023]xgerryx[/MENTION] should we set permission to rw,r,r or not necessary?
[G4 General] xgerryx:
I honestly didn't touch permissions.
[G4 General] rickmatic:
From what I understand with kernel auditor you need to have a saved profile to apply changes at boot.

1. Make changes

2. hit menu.... scroll down to profile...

3. create a profile with current settings. I selected CPU only. Save.

my profile applied at boot. Hopefully that helps someone.
[G4 General] DsturbD:
that didnt work for me :(
[G4 General] pc2828:
Working for me, might be because I installed Universal Init.d and enabled Init.d support?
[G4 General] chriskwarren:
New 10f update seems to have fixed the touchscreen issues on my Bell Canada variant.
[G4 General] konradsa:
Starting to think more and more it's an issue with the CPU not ramping up fast enough in combination with some software glitch. Those of your that are rooted and still have this issue, can you try the following please and report back?

- Download Kernel Adiutor https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CB4QFjAAahUKEwithMSAmIHJAhUCNT4KHVtRAhs&url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.grarak.kerneladiutor&usg=AFQjCNFAjmieBTFxAFQ1EX0ve0qEk4ghTg&sig2=2wRFVLTicLGRlY7sk4NqPQ

- Go to Kernel - CPU screen

- Change CPU governor to "performance" for LITTLE

This will prevent the little cluster from ramping down. Keep in mind that this will probably hit your battery pretty hard, so don't keep it enabled all the time. But if this change manages to alleviate the issue, so governor tweaks may help.
[G4 General] Cedlad:
hai, i've edited my build.prop and managed to boot but every while i get random reboots, this is what i pasted at the end of my file :

touch.deviceType = touchScreen

touch.orientationAware = 1

touch.size.calibration = diameter

touch.size.scale = 1

touch.size.bias = 0

touch.size.isSummed = 0

touch.pressure.calibration = physical

touch.pressure.scale = 0.001

touch.orientation.calibration = none

touch.distance.calibration = none

touch.distance.scale = 0

touch.coverage.calibration = box

touch.gestureMode = spots

MultitouchSettleInterval = 1ms

MultitouchMinDistance = 1px
[G4 General] malnash52@gmail.com:
Delete the tweaks I'm assuming these are touch sensitivity tweaks
[G4 General] matildecorp:
I am having a KnockOn issue. And trying to fix it I have discovered some strange behaviour of my phone.

While unlocked is working perfect, no missed touches or any problem with swyping. When locked the lockon feature doesn´t work (actually it works, sometimes knocking 7-10 times with 3-4 fingers... is a deep sleeper)

Testing the multitouch screen with the app Miltiotouch test, is working flawlessly. Testing the multitouch with the internal tester (Hidden Menu) is giving a round 1/3 of missed touches.

I am not specialist on this but I guess that the internal test tool work in a level that is closer to the hardware than the app... I don´t understand what the hell is going on!!! I must be wrong in something!!!

Then I am not sure if this twak could work, or if anything could work, or if maybe is something simpler!!!!

I have rooted and installed Imperium ROM v13 after the issue appeared... same result...

Any clue, suggestion, guideline???

EDIT: After installing IMPERIUM ROM I am having randomly missed touches. Sometimes no missed touches, sometimes 1/3...

I have checked with the Touch Draw Test -Manual from the hidden menu that appears dialing *#546368#*815# and have that missed touches. If I try the hidden menu with the app Shortcut Master (com.lge.hiddenmenu.HWDeviceTest.TouchScreen) I don´t get any missed touch with any test.

So now, I can only guess that is the proximity sensor... but the test works fine... so... I am lost.
[G4 General] Shihabus Sakib Rad:
I tried this on my samsung a30 Bliss Rom. may be it is working or placebo effect, i don't don't know
[G4 General] Ed15121998:
Please add for touchscreen type "mms_ts" Samsung Galaxy A50 Exynos 9610
[G4 General] otanger:
changed everything does anyone know where the touch settings are ??? I have a problem with the slop it only registers after dragging a certain distance with the pen it's horrible
[G4 General] davy917:
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.
[G4 General] *justintime*:
Thanks great example of the placebo effect then. [emoji3]
[G4 General] RidinNerdy:
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...
[G4 General] *justintime*:
I don't know I still do think that tap to wake responds better.
[G4 General] 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!
[G4 General] mcnick0495:
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.
[G4 General] RidinNerdy:
Yes can someone post a proper screenshot?

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

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

Thanks in advance!

Ps: yes, i rebooted to take effect
[G4 General] Animatorman:
Nope, needs to be exactly like the OP
[G4 General] sparksj3:
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.
[G4 General] 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.
[G4 General] RidinNerdy:
This didn't do anything either

I dont understand whats going on... Still misses touches
[G4 General] 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.
[G4 General] Harmtan2:
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.
[G4 General] mrwinkle:
Here is mine and it seems to be working.
[G4 General] Harmtan2:
This has made knock code usable. Previously I couldn't use it at all. So thank you OP!