[8.1] [Magisk Module] Multi-Touch Fix for 8.1 Devices

Search This thread

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,900
20,177
Hello guys and girls,

As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.

The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455

There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.

To visualize the issue refer to the following videos:

https://youtu.be/wgYN5GwIgIc

https://youtu.be/2Vv584tvVyg

https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be

This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.

This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.


So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.

The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606

Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.

For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.

I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.

The download is here:
https://www.androidfilehost.com/?fid=890129502657595755


A few disclaimers here.

1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
It seems devices with oos on 8.1 ( op5/t) cannot use this mod.
AOSP and LOS roms should be okay.

2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.

3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.


Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07
 
Last edited:

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,900
20,177
This causes a bootloop on P DP1.

Thanks for the report.
can anyone confirm this?

In the meantime i removed the p tag from the thread title.


Could be That there are additional changes in p that make this libs unusable and only workable on 8.1.

Unfortunately there is afaik no complete source for p yet. So I can’t compile them specifically for p.
 
Last edited:
  • Like
Reactions: iaTa

ReapinDevil

Senior Member
Sep 24, 2013
71
7
I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks
 

Attachments

  • Screenshot_20180404-182022.png
    Screenshot_20180404-182022.png
    146.1 KB · Views: 976

sixohtew

Senior Member
Jul 17, 2012
390
891
phoenix
I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,900
20,177
I can't replicate this problem, but good to know that there's a fix if I ever experience it.


I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch

I also thought at first I didn’t have this issue at all.

But once I triggered it accidentally I experienced it many times. Maybe I just learnt what to look for.

Another fun thing is. A friend of mine also got the pixel XL 2 and I could reproduce it right away on his locked phone which is stock 8.1.

I can also trigger it on my pixel C tablet.
 

otonieru

Senior Member
May 7, 2011
3,493
2,235
Djakarta
Kudos to you,

Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,

Now it all fixed.

The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.

And considering am using full cover glass protector. This is amazing work !
 

Attachments

  • Screenshot_20180404-231242.png
    Screenshot_20180404-231242.png
    150.2 KB · Views: 313
  • Screenshot_20180404-231533.png
    Screenshot_20180404-231533.png
    53.9 KB · Views: 311

Schroeder09

Senior Member
Nov 6, 2017
835
123
I've experienced lack of touch response quite often. It's weird and seemingly random. I just flashed this on 8.1 with magisk. I don't have any results yet, but based on what everyone else is saying, this is a solid fix. Thanks for your work!

Do we have to worry about removing this in the future if google updates fix the issue too? Will this being on the system cause conflicts and issues?
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,900
20,177
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the Autor.
That’s just xda bring xda. :D

I had this problem a few times when updating the OP for a new release. Sometimes the OP won’t update at all...
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,900
20,177
Kudos to you,

Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,

Now it all fixed.

The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.

And considering am using full cover glass protector. This is amazing work !

Glad it works out for you!

Enjoy your phone :cowboy:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 36
    Hello guys and girls,

    As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.

    The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
    An issue got created here: https://issuetracker.google.com/issues/70344455

    There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.

    To visualize the issue refer to the following videos:

    https://youtu.be/wgYN5GwIgIc

    https://youtu.be/2Vv584tvVyg

    https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be

    This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
    I´m no gamer but I noticed the issue on the google foto app.

    This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.


    So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
    That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.

    The fix is on google gerrit currently under review here:
    https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
    https://android-review.googlesource.com/c/platform/frameworks/native/+/640606

    Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.

    For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.

    I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.

    The download is here:
    https://www.androidfilehost.com/?fid=890129502657595755


    A few disclaimers here.

    1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
    It seems devices with oos on 8.1 ( op5/t) cannot use this mod.
    AOSP and LOS roms should be okay.

    2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.

    3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.


    Donations:
    Donations are not mandatory but very welcome.
    If you like my work: http://paypal.me/freak07
    4
    @calebcabob
    @Myself5
    @BDogg718
    @sixohtew
    @nitin.chobhe
    @auras76

    you may want to look at this and include it in your april releases.

    If not users can just make use of the magisk module.
    3
    So no need for this mod anymore? Lol
    Depends. If you’re on google rom with may patch there is no need.

    If you’re custom rom already merged the fix there’s also no need :)
    Just check out the rom’s github and search for the repo android framwork native. There you will see if the commit described in the op is inlcuded.
    2
    Kudos to you,

    Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,

    Now it all fixed.

    The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.

    And considering am using full cover glass protector. This is amazing work !

    Glad it works out for you!

    Enjoy your phone :cowboy:
    2
    Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!
    Same with me on google fotos!

    Glad it’s fixed for you.