[APP][ROOT] Touch screen fixer

Formhault · May 8, 2015 at 12:28 PM

maumaumau said:
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.

Funny. Going back to CM11S didn't fix it for me. And, as I previously said, I've been on X number of Android 5.x.x ROMs before this issue appeared.

I think I'll flash CM11S and update to CM12S to test that myself.

maumaumau · May 8, 2015 at 1:22 PM

Formhault said:
Funny. Going back to CM11S didn't fix it for me. And, as I previously said, I've been on X number of Android 5.x.x ROMs before this issue appeared.

I think I'll flash CM11S and update to CM12S to test that myself.

I have to correct myself. It is still there on CM12s, but it is not as bad as on CM12.1.
I also observed that the bad effect weakens, the faster you type (I use swiftkey).

Btw: did you also downgraded the firmware?

D4rkSoRRoW · May 8, 2015 at 2:43 PM

Formhault said:
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.

Higher is better. The SD801 is binned from 1 to 15, where 15 is the best. My new one was 4, my old one was 8. That's like 100mhz difference with the same mV

It does not have anything to do with the touchscreen issues tho

Formhault · May 8, 2015 at 4:13 PM

maumaumau said:
I have to correct myself. It is still there on CM12s, but it is not as bad as on CM12.1.
I also observed that the bad effect weakens, the faster you type (I use swiftkey).

Btw: did you also downgraded the firmware?

I have no idea what the firmware actually does on the OPO so I assumed the ROM flash changes it. Well, it does, in the CM12.1 nightlies.

I'll flash full CM11S. Erase all. With some AIO toolkit. Which would also flash the respective firmware. Then upgrade to CM12S.

But how the fudge can it be ROM related if everything worked fine for one month and all the sudden, one day, after not flashing ANYTHING for 3 days, it screws up?

*headbang*

---------- Post added at 06:13 PM ---------- Previous post was at 06:10 PM ----------

D4rkSoRRoW said:
Higher is better. The SD801 is binned from 1 to 15, where 15 is the best. My new one was 4, my old one was 8. That's like 100mhz difference with the same mV

It does not have anything to do with the touchscreen issues tho

Yeah, I know what CPU bin is. I just forgot what the values represent. So I remember it right : higher bin = lower voltage = less heat output = yay.

So, how do you check the binning?

Jah_son · May 8, 2015 at 6:13 PM

Formhault said:
I'll flash full CM11S. Erase all. With some AIO toolkit. Which would also flash the respective firmware. Then upgrade to CM12S.

This is what I've been wanting to know if anyone has tried as opposed to just a clean wipe. Why not see what happens with 11S first though before upgrading? I been looking at doing it myself but my laptop is down.......

Formhault · May 8, 2015 at 6:55 PM

Jah_son said:
This is what I've been wanting to know if anyone has tried as opposed to just a clean wipe. Why not see what happens with 11S first though before upgrading? I been looking at doing it myself but my laptop is down.......

I will be doing just that. Tomorrow late night, hopefully. Tinkering with my Android device has gone so low on my to-do list that I'm doing it in extra hours, so-to-say.

HWAM · Jan 17, 2015 37 8 0

Fridge

If you have the x-axis problem and you put the phone in the fridge for 10 minutes it's temporary solved. So it can't be a software problem. Above 25 degrees Celsius mine is giving x-axis problems.

Enea307 · May 9, 2015 at 7:46 PM

http://feedproxy.google.com/~r/AndroidPolice/~3/ebNR6lPft6c/story01.htm
Hope we have a fix soon.

Formhault · May 9, 2015 at 8:23 PM

HWAM said:
If you have the x-axis problem and you put the phone in the fridge for 10 minutes it's temporary solved. So it can't be a software problem. Above 25 degrees Celsius mine is giving x-axis problems.

Nope. It's not temperature dependent for me

rolear8 · May 10, 2015 at 12:37 AM

Djaboloke said:
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

Could you provide the link please friend.?

Sent from my A0001 using Tapatalk

D4rkSoRRoW · May 10, 2015 at 1:20 PM

Formhault said:
Yeah, I know what CPU bin is. I just forgot what the values represent. So I remember it right : higher bin = lower voltage = less heat output = yay.

So, how do you check the binning?

You find everything you need to know about the OPO binning and how to check it here: http://forum.xda-developers.com/oneplus-one/general/info-cpu-binning-concept-overclocking-t2817105

Don't forget to reboot the phone after installing the Terminal emu, else it won't work.

paise72 · Jun 8, 2011 39 9 28

Thanks man... It works great??

Sent from my A0001 using Tapatalk

Handaloo · May 11, 2015

How?

D4rkSoRRoW said:
**** that. It's a grounding problem with the hardware. The screen connector touches the metal frame.
I opened my phone today and tried to insulate it. And it freaking worked. My screen is back to perfection :good:

Can you advise how to do this? I'm more than willing to try that!

Sorry, ignore me. Should've read further.

Enea307 · May 11, 2015 at 6:30 PM

I have to fix this or I'm going to buy a new phone. Its so annoying this touch problem. (Euphoria Rom 03.05.2015 5.1.1 ) We need a solution. Plz help is needed.

---------- Post added at 07:30 PM ---------- Previous post was at 07:27 PM ----------

@paise72. What does work great for you?

Teo032 · May 11, 2015 at 8:09 PM

Thanks, this fixed the ghost touch/deadspots that happens randomly from time to time. Before I use to have to restart to fix the issue. Now it is a simple turn off display then turn on display.

casco1 · Jan 9, 2015 57 8 0

Just installed on euphoria OS. It seems amazing! Now it works great!

KenjiHannya · May 12, 2015 at 4:34 PM

OPO Display Patch

https://drive.google.com/file/d/0Bw8Ln2-hMxj3cHoxS29tZFJDT3c/view

Enviado de meu OnePlus One usando Tapatalk

abhi08638 · May 12, 2015 at 4:45 PM

KenjiHannya said:
OPO Display Patch

https://drive.google.com/file/d/0Bw8Ln2-hMxj3cHoxS29tZFJDT3c/view

Enviado de meu OnePlus One usando Tapatalk

That's just a full firmware reset

Sent from my A0001 using XDA Free mobile app

KenjiHannya · May 12, 2015 at 4:46 PM

abhi08638 said:
That's just a full firmware reset

Sent from my A0001 using XDA Free mobile app

Yes.

Enviado de meu OnePlus One usando Tapatalk

rolear8 · May 12, 2015

KenjiHannya said:
Yes.

Enviado de meu OnePlus One usando Tapatalk

When was this released? Does it work? Thanks

Sent from my A0001 using Tapatalk

[APP][ROOT] Touch screen fixer

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member