[APP][ROOT] Touch screen fixer

Jah_son

Member
Apr 21, 2015
41
10
0
It is not software. I got me a new OPO and switched the mainboards, because the new one had bad binning.
The screen is perfect now - This means it's definitely not software related.
What was the issue with the first one and how'd you figure switching boards might have helped?
 

kerheol

Member
Oct 3, 2010
46
9
0
Irony of the thing is my phone got replaced about 5 weeks ago.. Now experiencing the same issue... This is frustrating

---------- Post added at 07:35 AM ---------- Previous post was at 07:28 AM ----------

Can confirm: the touchscreen apk makes it way better, doesn't fix the issue entirely though
Do you mean One+ replaced your phone with a new but defective one?

Enviado desde mi A0001 mediante Tapatalk
 

Djaboloke

Member
Jul 4, 2013
26
1
0
Fluke or not?

Hello,

I was having the exact same very frustrating issue for a few weeks now, started after upgrading to the 12.1 nightly's. Mostly had it at its worst when it was warm outside and it had been in my pocket.
Althought the 08/05/2015 bacon nightly all of a sudden resolved the X axis issue (had it practically permanent) and no more ghost touches.

I'm hoping this is the end of that annoying issue, I'll keep you guyz posted.

Else I'll prolly give up and have it RMA'ed.

Give a shout if 08/05 nightly also fixed it for you :).
 

Jah_son

Member
Apr 21, 2015
41
10
0
Hello,

I was having the exact same very frustrating issue for a few weeks now, started after upgrading to the 12.1 nightly's. Mostly had it at its worst when it was warm outside and it had been in my pocket.
Althought the 08/05/2015 bacon nightly all of a sudden resolved the X axis issue (had it practically permanent) and no more ghost touches.

I'm hoping this is the end of that annoying issue, I'll keep you guyz posted.

Else I'll prolly give up and have it RMA'ed.

Give a shout if 08/05 nightly also fixed it for you :).
So it seems to be software based then? Latest firmware and latest AK solved my issues mostly......
 

Djaboloke

Member
Jul 4, 2013
26
1
0
Possibly

So it seems to be software based then? Latest firmware and latest AK solved my issues mostly......
It seems like it, since it started happening after the switch to 12.1N.

When it's hardware, it shouldn't be fixed with a reboot... Unless its something power related imho (but the screen is never fully of with a reboot I think, don't qoute me on this :silly:)

As long as I'm not getting the issue again I'm staying on this nightly and not changing anything untill a major update or a bugfix is needed in my particular case :p
 

Jah_son

Member
Apr 21, 2015
41
10
0
It seems like it, since it started happening after the switch to 12.1N.

When it's hardware, it shouldn't be fixed with a reboot... Unless its something power related imho (but the screen is never fully of with a reboot I think, don't qoute me on this :silly:)

As long as I'm not getting the issue again I'm staying on this nightly and not changing anything untill a major update or a bugfix is needed in my particular case :p
By the way, I just tried the nightly.......it's a solid step! No ghost swipes, and if any? 5 percentile.....

I was thinking about selling and getting a Note 4 but I love this phone more, and I've own a Note before
 

Formhault

Senior Member
Jun 10, 2011
11,517
4,581
253
Bucharest
Hello,

I was having the exact same very frustrating issue for a few weeks now, started after upgrading to the 12.1 nightly's. Mostly had it at its worst when it was warm outside and it had been in my pocket.
Althought the 08/05/2015 bacon nightly all of a sudden resolved the X axis issue (had it practically permanent) and no more ghost touches.

I'm hoping this is the end of that annoying issue, I'll keep you guyz posted.

Else I'll prolly give up and have it RMA'ed.

Give a shout if 08/05 nightly also fixed it for you :).
It seems like it, since it started happening after the switch to 12.1N.

When it's hardware, it shouldn't be fixed with a reboot... Unless its something power related imho (but the screen is never fully of with a reboot I think, don't qoute me on this :silly:)

As long as I'm not getting the issue again I'm staying on this nightly and not changing anything untill a major update or a bugfix is needed in my particular case :p
The issue started to occur on my phone all the sudden, after being 3 days on Resurrection Remix (I used to switch ROMs a lot)... all I changed right then was the kernel, MAYBE. But I was the only one reporting the issue, so... yeah... I'm not so sure this is software related. If it is, it definitely isn't 100% :\

Anyway, just flashed the latest CM12.1 nightly (8/05, that is) and... yeah, no improvement :) :crying:

---------- Post added at 11:01 AM ---------- Previous post was at 11:00 AM ----------

By the way, I just tried the nightly.......it's a solid step! No ghost swipes, and if any? 5 percentile.....
Can you test this and see if it still happens?
 

Jah_son

Member
Apr 21, 2015
41
10
0
Can you test this and see if it still happens?
YAMTT? I didn't stick with the 12.1 nightly, I only tried it see if it would solve the issue and it did, imagine it with AK.

I restored my 11S crdroid since I need xposed and prefer not having the "mobile radio active" issue, but I suppose I could give it a try to see the YAMTT response.......the x-axis test is sporadic on my current rom

I was on Remix and had this issue, Temasek gave me for better results. Why not try his latest 5.1.1? You'll never know........try SwiftKey too without swipe input
 
Last edited:

Jah_son

Member
Apr 21, 2015
41
10
0
Tested it with YAMTT and multitouch 2

There is a very very tiny wiggle (but not as in the clip). And the X-axis issue is gone for me now on both apps. I can overlap the lines withouth them dissapearing.
And this is with latest nightly bacon right? Great news :highfive:
 

D4rkSoRRoW

Senior Member
Dec 8, 2009
1,655
255
0
St. Gallen
What was the issue with the first one and how'd you figure switching boards might have helped?
My first OPO started to be unresponsive after 10months. Typing was a horror. Sometimes I couldn't even use a part of the screen.
I bought a new one, because I don't want to RMA ****.
The new one had no problems with the screen, everything was good. Except the bad CPU binning, which really pissed me off, so I decided to switch the motherboards, with the old one.

Screen is now working fine with my old mobo. It has to be a hardware problem with the old screen.
Switching the mobo was just my decision as I hate bad binned CPUs getting hot and stuff.
 

Formhault

Senior Member
Jun 10, 2011
11,517
4,581
253
Bucharest
My first OPO started to be unresponsive after 10months. Typing was a horror. Sometimes I couldn't even use a part of the screen.
I bought a new one, because I don't want to RMA ****.
The new one had no problems with the screen, everything was good. Except the bad CPU binning, which really pissed me off, so I decided to switch the motherboards, with the old one.

Screen is now working fine with my old mobo. It has to be a hardware problem with the old screen.
Switching the mobo was just my decision as I hate bad binned CPUs getting hot and stuff.
Bad binned CPU? You mean your CPU bin was high or low? Which is bad, lol. I used to know, but 2013 was a long time ago.

And its back.... :crying::crying:

Friggin phone!
Yeah, as I said...

Well, good thing is now I don't seem to need the Touch Fixer app anymore. I mean with or without it, the same "little" problem remains : X axis, you know. Which is bareable... at least until I get this phone open / manage to sell it...

---------- Post added at 01:23 PM ---------- Previous post was at 01:21 PM ----------

I was on Remix and had this issue, Temasek gave me for better results. Why not try his latest 5.1.1? You'll never know........try SwiftKey too without swipe input
I used AICP, Resurrection Remix, Euphoria 5.0.2 and 5.1.1, CM12.1 and CM11S. Same problem.

I don't use SwiftKey anymore. Am using the AOSP keyboard right now. I used to be a SwiftKey junkie, but gave up ~3 weeks ago, thinking it's the actual keyboard that's causing the issues. Wrong, of course. But I kept on using the AOSP keyboard, lol.

So yeah. Chances of this being software related are very, very minimal.
 

Djaboloke

Member
Jul 4, 2013
26
1
0
Bad binned CPU? You mean your CPU bin was high or low? Which is bad, lol. I used to know, but 2013 was a long time ago.



Yeah, as I said...

Well, good thing is now I don't seem to need the Touch Fixer app anymore. I mean with or without it, the same "little" problem remains : X axis, you know. Which is bareable... at least until I get this phone open / manage to sell it...

---------- Post added at 01:23 PM ---------- Previous post was at 01:21 PM ----------



I used AICP, Resurrection Remix, Euphoria 5.0.2 and 5.1.1, CM12.1 and CM11S. Same problem.

I don't use SwiftKey anymore. Am using the AOSP keyboard right now. I used to be a SwiftKey junkie, but gave up ~3 weeks ago, thinking it's the actual keyboard that's causing the issues. Wrong, of course. But I kept on using the AOSP keyboard, lol.

So yeah. Chances of this being software related are very, very minimal.
Back to OPO it goes! :(:mad:
 

AcmE85

Senior Member
Jan 19, 2012
2,928
3,691
203
All these roms and kernels nowadays (lollipop) are based on the same touchpanel firmware (inside the kernel)
which was updated last on January 8th. Even stock Cyanogen OS 12 uses this one.
There is no way that a different kernel or rom fixes the issues.
 

maumaumau

Senior Member
Dec 19, 2010
110
15
0
All these roms and kernels nowadays (lollipop) are based on the same touchpanel firmware (inside the kernel)
which was updated last on January 8th. Even stock Cyanogen OS 12 uses this one.
There is no way that a different kernel or rom fixes the issues.
It is indeed a ROM (or Kernel or CM?) issue. I've used the early und unofficial builds of CM12.1 (well at least Lollipop 5.1) and had no issues at all. The opposite was the case: everything worked and I percieved the system like 10 times faster than CM11S.

In the last 2 days I installed and tested the old unofficial builds and everything worked again (especially the ones before the 31st of march).

Then again I also tested the lastet CM11s build and at least the touchscreen worked million times better than the one of the latest CM12.1 builds. I updated then to CM12s and for me it is the best solution, because it works like it should.

I'll wait for the official COS versions. I'm a former Nexus user (from the One to the 5 I had everything except the S) and its horrible that the current betas are this broken.
 

AcmE85

Senior Member
Jan 19, 2012
2,928
3,691
203
Keep on testing...
I see you have no idea about the software side behind all this.
Glad it works for you though. :)