nexus 4 touch screen not reacting any more

[macwwt]

On my Nexus4 the same problem, I have full version of Touch Control, previously Stock android now Paranoid 3.5 and the same problem, enable TC and after couple of minutes my lock screen is freeze. How to reproduce? Flash Paranoid 3.5 rom install TC lock your screen and wait five minutes.

[Killar]

offtopic sorry but
Since the latest Alpha Paranoidandroid version 3.55
has a new Kernel within, touch control doesnt run anymore.
Can you fix it ? Thank you

[ananthonline]

I'm having the same problem as the OP. Stock 4.2.2 - everything was working great till the update a couple of days ago to 1.6i. I've been seeing random screen freezes and a "stuck" ghost touch. The phone itself works fine, even receiving calls but with no way to pick up. I will upload a logcat if you wish.

[Quicksand10]

I'm having the same problem, plus the issue when phone calls randomly disable the module.

I'm currently running the latest stable Franco.Kernel with the full version of Touch Control. I'm on rooted stock firmware (with ClockworkMod recovery). I had the same problem while using the stock modified kernel.

Thanks for your time and effort, ponury! It's very appreciated.

[westdene]

Im runnign latest paranoid alpha and touch does not work at all. I was using the paid version and now I have no touch app working. Any idea on when you are going to fix it?
Thnx

[tomvalve]

To westdene:
Your kernel is not compatible with PGM application. You must change kernel.

[ponury]

PA kernel is now supported with 1.7 version of TC.

[Quicksand10]

Unfortunately I ran into this problem just now, a couple of hours after updating to the latest version.

[ponury]

Uninstall, reboot install that's the only way to update the app.

[Haomuch]

I am using the lasted 1.7 touch control and Franco kernel r146 with stock rom. It does work better than previous build but the screen still goes freeze randomly and the notification bar always dropped down when unlocking the screen. It seems that the touch screen will produce incorrect position at the first time right after the screen was swipe to wake. That will not happen if the screen is unlocked by the button.