The screen unresponsive fix i swear...

[Tilde88]

Obviously... YOU NEED ROOT... and you NEED NAND unlocked... And preffered a custom rom... and also SetCPU 1.6.0... VERSION IS CRITICAL... oh and buy it its only 2 bucks...

im on hardware 0002 idk about if this works 0003



Ok... go here

http://forum.xda-developers.com/showthread.php?t=695750

boot into fastboot (requires NAND unlocked)
adb reboot bootloader

then flash the overclock zimage with command
fastboot boot zImage_supersonic_oc-uv

mind you that the zimage needs to be in the folder with abd and also fastboot.exe... it souhld be packed already in the A SDK...
now... itll boot...
go to SetCPU... ...use autodetectDO NOT PUT IT at 1228...itll reboot cuz of the kernel panic...
put it at the second to last setting
voila... screen issue fixed
OMG ALL CREDIT GOES
to coolbho3000

once you reboot it will lose the zimage

[r.mauldin]

I read through 7 pages to see that it breaks wifi. It is still in demo/test phase of dev.
keep us posted.

[malibu_23]

how does this work?

[hawkyman]

Why would overclocking the processor fix a screen grounding issue? I think more proof is needed before people go overclocking their phones on a fluke one person experienced.

[zone23]

Originally Posted by hawkyman

Why would overclocking the processor fix a screen grounding issue? I think more proof is needed before people go overclocking their phones on a fluke one person experienced.

Just wondering were you read that it was proven to be a grounding issue? I'm not sold that it has anything to do with grounding.

[Lacrosse]

I think you guys are talking about different kinds of "unresponsive" the grounding issue is the cause of the screen not registering input or giving up mid-drag. The overclocking here fixes the laggy input, where the screen moves slower than your finger does and has a general delay for movement.