Closed ttrobisch closed 8 years ago
Gladly to read that I'm not the only one with this problem. And probably nothing wrong with my phone. It's happens to me right now, when I'm charching phone. It happens with previous versions of cm13 too (don't remember if was always at recharching). After that error I always reboot phone, clean cache and dalvik. I don't know if that helps for while. But for few days I didn't have problems with touchscreen.
I have that problem too, in two variants:
should be fixed in the next builds.
Don't know if it's still important then, but the 20160224 image made matters much worse. In one day testing, I had to reboot almost every time when I wanted to use my phone.
the 20160224 introduced more problems (I found that out after I had already uploaded the build), but I have never had to reboot my device. Extract the attached file and push it to /system/priv-app/InputDisabler/. I haven't had any issues with it yet.
Thank you very much for fixing problems. I'm using version 20160224 for one day and I haven't any problems with touchscreen after locking device :D
The Touchscreen is infrequently not taking inputs if you turn the screen on. I got this issue with the aicp mm and cm13 Roms by you.