Hey fellow SHIELD owners,
I'm sure most of you have already experienced the issue: you put your SHIELD away, then come back later to turn it back on, only to find that the touch screen simply isn't responding.
Well, I found a (reliable) workaround.
For the more technically inclined, touch processing is partially done in userspace on the SHIELD. For that, a small service is running constantly in the background; it's called "rm_ts_server".
When I encountered the issue again I was a bit frustrated; I checked logcat, and then had a hunch: what if I kill rm_ts_server and let the system restart it. I did that and, yes, it worked! I had touch back, no need to reboot.
So how can you make this practicable now? I used Tasker. I added a profile for "Screen On", and a shell command task that simply kills rm_ts_server (it will restart itself immediately, giving you touch back).
If anyone has a different means for restarting the touch screen server please share!
I'm sure most of you have already experienced the issue: you put your SHIELD away, then come back later to turn it back on, only to find that the touch screen simply isn't responding.
Well, I found a (reliable) workaround.
For the more technically inclined, touch processing is partially done in userspace on the SHIELD. For that, a small service is running constantly in the background; it's called "rm_ts_server".
When I encountered the issue again I was a bit frustrated; I checked logcat, and then had a hunch: what if I kill rm_ts_server and let the system restart it. I did that and, yes, it worked! I had touch back, no need to reboot.
So how can you make this practicable now? I used Tasker. I added a profile for "Screen On", and a shell command task that simply kills rm_ts_server (it will restart itself immediately, giving you touch back).
If anyone has a different means for restarting the touch screen server please share!
Aucun commentaire:
Enregistrer un commentaire