• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Possible fix for touch screen issue. ( updated )

Search This thread

showlyshah

Senior Member
Mar 10, 2011
1,100
954
kerala
Hello all.. so i started working again on hacks for android. I literally stopped it when i sold my sony xperia z5 premium and bought some samsung device.( It is literally no pleasure to work with all those s6 edge, s7 edge and note 5.. sorry samsung.. but your software is nothing but a nightmare for guys like me) .

I was desperate to buy a pixel 2 xl , waited so long to arrive at markets near me.. and when it arrived.. i grabbed one soon.. its a joy to hold this device.. well .. every happiness comes with some sorrows..

As soon as i got my pixel 2 xl, i unlocked the bootloader and rooted it in just 2 hours after i got it.. so.. even though this device is an awesome gadget to play with.. it have its own drawbacks at several things..

1) of course the infamous display issues.. ( lol.. those haters may wont even know what OLED( or pOLED) display does..

2) crackling of speakers ... Well i am not worried.. i know its something to do with the software.. and google or even we xda geniuses will fix it soon.. ( btw.. i am looking into some solutions)

3) touch screen sensitivity... Ya.. you heard it right.. this pannel have some touch issues.. may be most of you or some of you have noticed it now.. if you dont.. try a glass screen protector..


So while i was not able to fix the speaker issue by now ( my device is just 4 days old.. and i noticed it yesterday only, as i haven't even started using it with a sim card yet) , i possibly have a solution for touch sensitivity .. i just found it 10 minutes before creating this post. ( Thanks to some old knowledge for some sony hacks back in those days) ..

Way too boring talks?? Sorry.. i am basically a story teller type guy.. ok. No more stories.. lets get it done.

1) go to your favorite root file manager ..

2) go to - system / vendor/ usr / idc .

3) you will see a file named touchscreen.idc

4) open it with any text editor and remove all values from it and add these lines ( or replace with the attached file)

device.internal = 1
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.filter.level = 0
touch.size.calibration = diameter
touch.size.scale = 5
touch.size.bias = 5
touch.size.isSummed = 0
touch.gestureMode = pointer
touch.pressure.calibration = physical
touch.pressure.scale = 0.00000125
touch.distance.calibration = none
touch.distance.scale = 0
touch.gestureMode = spots
MultitouchSettleInterval = 0.1ms
MultitouchMinDistance = 0.5 px
TapInterval = 0.5 ms
TapSlop = 0.5 px
touch.orientation.calibration = none
touch.coverage.calibration = box

5) save the file with its previous permissions ( i use filemanager named xplore, which automatically saves it with previous permissions)

6) reboot your device.. and enjoy your super responsive touch screen..


Guys.. please let me know your experience.. for further goods and bads..

Thank you..


Oh.. btw.. i have a bonus knowledge to share too..

If you find your colour calibration ( or colourfulness!! ) Of your device is low even after googles " saturated mode" , you can adjust it in build.prop file.


1) go to - system / vendor

2) open build.prop file in your fave text editor.

3) find this line - " persist.sys.sf.color_saturation=1.1 "

4) change the value to " persist.sys.sf.color_saturation=1.5 " or so..

5) you can go all the way upto "persist.sys.sf.color_saturation=2" but not more..

6) save file with its previous permissions

7) reboot and enjoy you " Samsung'ish " display..

Nb:-

dont burn ur eyes with all those alien looking colours with value of 2.. just keep it under 1.5 or so... Guys.. keep it as pixel, why go for that samsung colours


Wishes..

All praise Lord Dinkan..
 

Attachments

  • touchscreen.zip
    788 bytes · Views: 1,318
Last edited:

crowsnestitsupport

Senior Member
Sep 16, 2015
557
233
31
Altoona, PA
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!

---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------

Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?
 
  • Like
Reactions: showlyshah

Badger50

Forum Moderator
Staff member
Feb 27, 2011
12,589
14,687
61
Kansas City
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!

---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------

Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?


Same here. Didn't survive the reboot.

That's kinda strange. I edited it with root explorer, rebooted, and the settings stuck! Definitely can tell the difference on my smart keyboard pro :good:
 

sharkie405

Senior Member
Dec 22, 2008
2,759
1,878
Earth
I didn't have general swipe issues, the only thing I had trouble with was swiping up on the lock screen to bring up the pin pad. Usually it took me two or three times before the pin pad would actually come up. In any event, I just tried your touch sensitivity suggestion, except that I just set it to .000125 (because I don't have a glass screen protector on it, and I didn't want it to be too sensitive), and that worked absolutely beautifully. I was just able to pull up the pin pad about 15 times in a row with absolutely no issues. Thank you so much!

If you can fix the crackling speaker sound, you'll be a god in my eyes! In my opinion, that is the only issue I have left with this phone.

I'll hit the thanks button tomorrow, I'm all out of thanks for today. :(
Sent from my Pixel 2 XL using XDA Labs
 
Last edited:

showlyshah

Senior Member
Mar 10, 2011
1,100
954
kerala
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!

---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------

Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?


Same here. Didn't survive the reboot.


There is two system folder system and system_root..

Also there is a vendor folder outside system folder..

I dont know the system structure yet ( as i didn't disassemble the factory images yet ) .. so i dont know why this all confusing folder structure..


Btw.. i think you have looked into system_root folder or vendor folder outside system folder..


Make sure u go into system ( not system_root) and find the file..

System - vendor - usr - idc..


Or may be just your filemanager didn't saved the value??
 

Badger50

Forum Moderator
Staff member
Feb 27, 2011
12,589
14,687
61
Kansas City
I didn't have general swipe issues, the only thing I had trouble with was swiping up on the lock screen to bring up the pin pad. Usually it took me two or three times before the pin pad would actually come up. In any event, I just tried your touch sensitivity suggestion, except that I just set it to .000125 (because I don't have a glass screen protector on it, and I didn't want it to be too sensitive), and that worked absolutely beautifully. I was just able to pull up the pin pad about 15 times in a row with absolutely no issues. Thank you so much!

If you can fix the crackling speaker sound, you'll be a god in my eyes! In my opinion, that is the only issue I have left with this phone.

I'll hit the thanks button tomorrow, I'm all out of thanks for today. :(

Meh....just make him a special font package bro. That'll be some good thanks for sure! :good::cool:
 

Golf c

Senior Member
Jan 4, 2015
1,596
778
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!

---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------

Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?


Same here. Didn't survive the reboot.
Avb 2.0 dm verity has to be patched in the dtbo image in order to edit the vendor partition. The above fix will stick once the dtbo image is patched. Will not stick without the patch.

---------- Post added at 03:04 AM ---------- Previous post was at 03:01 AM ----------

Dtbo image causing this maybe? I'm using the unofficial magisk without patching the dtbo.
You got it. That's the problem
 
  • Like
Reactions: wolfeyes30

Badger50

Forum Moderator
Staff member
Feb 27, 2011
12,589
14,687
61
Kansas City
Avb 2.0 dm verity has to be patched in the dtbo image in order to edit the vendor partition. The above fix will stick once the dtbo image is patched. Will not stick without the patch.

---------- Post added at 03:04 AM ---------- Previous post was at 03:01 AM ----------


You got it. That's the problem

Hey Golfc, you seem to know this magisk stuff pretty well. I'm still using the 14.5 zip, but using the 5.5 app. As you can see by the pic, force encryption and the AVB thingy are checked off. Everything is working fine. Would that change if I flashed the 14.6 version?? Only reason I haven't is I don't want to mess up my V4A. Any insight is greatly appreciated :good:
 
Last edited:

wolfeyes30

Senior Member
Dec 12, 2010
832
448
NE OHIO
Google Pixel 4 XL
What's the correct way for me to get onboard with the official magisk with a patched dtbo?

I have twrp installed already and using custom kernel. Uninstall the unofficial magisk from magisk manager then flash stock boot image, flash stock dtbo image, flash custom kernel then flash official magisk?

Thanks

I'm sure I need to reflash twrp.zip somewhere during that process to keep from getting the stock recovery.
 

Golf c

Senior Member
Jan 4, 2015
1,596
778
Hey Golfc, you seem to know this magisk stuff pretty well. I'm still using the 14.5 zip, but using the 5.5 app. As you can see by the pic, force encryption and the AVB thingy are checked off. Everything is working fine. Would that change if I flashed the 14.6 version?? Only reason I haven't is I don't want to mess up my V4A. Any insight is greatly appreciated :good:
Are you still getting the internal storage corruption message on boot? Your dtbo image is still patched then. It will not change by updating to 14.6. The only way to change is to fastboot the stock dtbo image and flash 14.6. In your current situation, all you would have to do is flash stock dtbo image and 14.6 Your Viper will still work.
 

showlyshah

Senior Member
Mar 10, 2011
1,100
954
kerala
Root explorer doesn't save the change for some odd reason. I just tried xplore as well with no change. Once I reopen the file the value was back to stock.

I don't know what is the problem with your file manager bro.. i changed and checked it several times.. every single time it is working.. actually i have some more tweaks with touch.. i am experimenting some values.. so i put on each values and checking every single time..
 
  • Like
Reactions: Badger50

Badger50

Forum Moderator
Staff member
Feb 27, 2011
12,589
14,687
61
Kansas City
Are you still getting the internal storage corruption message on boot? Your dtbo image is still patched then. It will not change by updating to 14.6. The only way to change is to fastboot the stock dtbo image and flash 14.6. In your current situation, all you would have to do is flash stock dtbo image and 14.6 Your Viper will still work.

Thanks bud. Not sure about the V4A that Zackptg5 helped create. Been reading that magisk 14.6 is causing it not to work. Guess I'll find out. Thanks again :good:
 

Golf c

Senior Member
Jan 4, 2015
1,596
778
What's the correct way for me to get onboard with the official magisk with a patched dtbo?

I have twrp installed already and using custom kernel. Uninstall the unofficial magisk from magisk manager then flash stock boot image, flash stock dtbo image, flash custom kernel then flash official magisk?

Thanks

I'm sure I need to reflash twrp.zip somewhere during that process to keep from getting the stock recovery.
1. Fastboot stock dtbo image and stock boot image
2. Reboot Twrp recovery from bootloader screen
2. Flash Twrp, custom kernel and Magisk 14.6 in one session.

No need to uninstall anything. I also assume your custom kernel uses a Ak2 zip for flashing.
 
  • Like
Reactions: wolfeyes30

showlyshah

Senior Member
Mar 10, 2011
1,100
954
kerala
But i seriously doubt that the kernal configuration for touch screen calibration and the actual driver values of the touch screen drivers are some how miss matched.. the sensitivity is way too low at extreme bottom corners of the display ( both left and right bottom corners) .. but i have tweaked the values to give much better touch response than original. For now i think we can deal with the problem this way till google or some of us will come out with better solution.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 36
    Hello all.. so i started working again on hacks for android. I literally stopped it when i sold my sony xperia z5 premium and bought some samsung device.( It is literally no pleasure to work with all those s6 edge, s7 edge and note 5.. sorry samsung.. but your software is nothing but a nightmare for guys like me) .

    I was desperate to buy a pixel 2 xl , waited so long to arrive at markets near me.. and when it arrived.. i grabbed one soon.. its a joy to hold this device.. well .. every happiness comes with some sorrows..

    As soon as i got my pixel 2 xl, i unlocked the bootloader and rooted it in just 2 hours after i got it.. so.. even though this device is an awesome gadget to play with.. it have its own drawbacks at several things..

    1) of course the infamous display issues.. ( lol.. those haters may wont even know what OLED( or pOLED) display does..

    2) crackling of speakers ... Well i am not worried.. i know its something to do with the software.. and google or even we xda geniuses will fix it soon.. ( btw.. i am looking into some solutions)

    3) touch screen sensitivity... Ya.. you heard it right.. this pannel have some touch issues.. may be most of you or some of you have noticed it now.. if you dont.. try a glass screen protector..


    So while i was not able to fix the speaker issue by now ( my device is just 4 days old.. and i noticed it yesterday only, as i haven't even started using it with a sim card yet) , i possibly have a solution for touch sensitivity .. i just found it 10 minutes before creating this post. ( Thanks to some old knowledge for some sony hacks back in those days) ..

    Way too boring talks?? Sorry.. i am basically a story teller type guy.. ok. No more stories.. lets get it done.

    1) go to your favorite root file manager ..

    2) go to - system / vendor/ usr / idc .

    3) you will see a file named touchscreen.idc

    4) open it with any text editor and remove all values from it and add these lines ( or replace with the attached file)

    device.internal = 1
    touch.deviceType = touchScreen
    touch.orientationAware = 1
    touch.filter.level = 0
    touch.size.calibration = diameter
    touch.size.scale = 5
    touch.size.bias = 5
    touch.size.isSummed = 0
    touch.gestureMode = pointer
    touch.pressure.calibration = physical
    touch.pressure.scale = 0.00000125
    touch.distance.calibration = none
    touch.distance.scale = 0
    touch.gestureMode = spots
    MultitouchSettleInterval = 0.1ms
    MultitouchMinDistance = 0.5 px
    TapInterval = 0.5 ms
    TapSlop = 0.5 px
    touch.orientation.calibration = none
    touch.coverage.calibration = box

    5) save the file with its previous permissions ( i use filemanager named xplore, which automatically saves it with previous permissions)

    6) reboot your device.. and enjoy your super responsive touch screen..


    Guys.. please let me know your experience.. for further goods and bads..

    Thank you..


    Oh.. btw.. i have a bonus knowledge to share too..

    If you find your colour calibration ( or colourfulness!! ) Of your device is low even after googles " saturated mode" , you can adjust it in build.prop file.


    1) go to - system / vendor

    2) open build.prop file in your fave text editor.

    3) find this line - " persist.sys.sf.color_saturation=1.1 "

    4) change the value to " persist.sys.sf.color_saturation=1.5 " or so..

    5) you can go all the way upto "persist.sys.sf.color_saturation=2" but not more..

    6) save file with its previous permissions

    7) reboot and enjoy you " Samsung'ish " display..

    Nb:-

    dont burn ur eyes with all those alien looking colours with value of 2.. just keep it under 1.5 or so... Guys.. keep it as pixel, why go for that samsung colours


    Wishes..

    All praise Lord Dinkan..
    5
    for the proper multitouch fix that was recently pushed to google gerrit take a look here:

    https://forum.xda-developers.com/pi...i-touch-fix-8-1-devices-t3773150#post76119199

    I made it into a magisk module and a dedicated thread to be flashed easily.

    This solves the issue described here:

    https://issuetracker.google.com/issues/70344455
    5
    fyi - the lockscreen swiping issue is fixed via substratum overlay here:

    https://www.xda-developers.com/fix-lock-screen-swipe-gesture-issues-android-81-oreo/
    5
    values updated.

    guys use the improved values ( or use new file)

    updated 24/12/17 - 1.30AM