Skip to main content
removed dead app links
Source Link
Andrew T.
  • 16.5k
  • 10
  • 76
  • 127

Sounds like your original problem is not specific to Android, and you're making this an XY problem.

What you should really do is unhook the touchscreen cable, and that solves it for all 3 operating systems.

On the laptops I've worked on, the ribbon cables for the screen are detachable from both ends: behind the LCD panel, and on the motherboard. Find out which is easiest to get to on your laptop by searching for disassembly videos, or just by removing screws until you get to it.

If this is an Android-specific problem for you, you'll want to take a look at /dev/input/event0 and event1 and event2 and so on.

Figure out which event corresponds to your touchscreen by using the getevent -i command from a shell terminal to read the descriptions, and getevent without the -i to track all inputs, touches, accelerometer movements, etc. in live action to narrow down which event is touchscreen. I have not verified this, but you might be able to disable the culprit driver by changing permissions on the eventXXXXX file to read-only with a root file browser.

I also just found an app that seems promising: Touch Blocker - Google Play
But I'm 99% sure that will prevent using the mouse as well.

Sounds like your original problem is not specific to Android, and you're making this an XY problem.

What you should really do is unhook the touchscreen cable, and that solves it for all 3 operating systems.

On the laptops I've worked on, the ribbon cables for the screen are detachable from both ends: behind the LCD panel, and on the motherboard. Find out which is easiest to get to on your laptop by searching for disassembly videos, or just by removing screws until you get to it.

If this is an Android-specific problem for you, you'll want to take a look at /dev/input/event0 and event1 and event2 and so on.

Figure out which event corresponds to your touchscreen by using the getevent -i command from a shell terminal to read the descriptions, and getevent without the -i to track all inputs, touches, accelerometer movements, etc. in live action to narrow down which event is touchscreen. I have not verified this, but you might be able to disable the culprit driver by changing permissions on the eventXXXXX file to read-only with a root file browser.

I also just found an app that seems promising: Touch Blocker - Google Play
But I'm 99% sure that will prevent using the mouse as well.

Sounds like your original problem is not specific to Android, and you're making this an XY problem.

What you should really do is unhook the touchscreen cable, and that solves it for all 3 operating systems.

On the laptops I've worked on, the ribbon cables for the screen are detachable from both ends: behind the LCD panel, and on the motherboard. Find out which is easiest to get to on your laptop by searching for disassembly videos, or just by removing screws until you get to it.

If this is an Android-specific problem for you, you'll want to take a look at /dev/input/event0 and event1 and event2 and so on.

Figure out which event corresponds to your touchscreen by using the getevent -i command from a shell terminal to read the descriptions, and getevent without the -i to track all inputs, touches, accelerometer movements, etc. in live action to narrow down which event is touchscreen. I have not verified this, but you might be able to disable the culprit driver by changing permissions on the eventXXXXX file to read-only with a root file browser.

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

Sounds like your original problem is not specific to Android, and you're making this an XY problemXY problem.

What you should really do is unhook the touchscreen cable, and that solves it for all 3 operating systems.

On the laptops I've worked on, the ribbon cables for the screen are detachable from both ends: behind the LCD panel, and on the motherboard. Find out which is easiest to get to on your laptop by searching for disassembly videos, or just by removing screws until you get to it.

If this is an Android-specific problem for you, you'll want to take a look at /dev/input/event0 and event1 and event2 and so on.

Figure out which event corresponds to your touchscreen by using the getevent -i command from a shell terminal to read the descriptions, and getevent without the -i to track all inputs, touches, accelerometer movements, etc. in live action to narrow down which event is touchscreen. I have not verified this, but you might be able to disable the culprit driver by changing permissions on the eventXXXXX file to read-only with a root file browser.

I also just found an app that seems promising: Touch Blocker - Google Play
But I'm 99% sure that will prevent using the mouse as well.

Sounds like your original problem is not specific to Android, and you're making this an XY problem.

What you should really do is unhook the touchscreen cable, and that solves it for all 3 operating systems.

On the laptops I've worked on, the ribbon cables for the screen are detachable from both ends: behind the LCD panel, and on the motherboard. Find out which is easiest to get to on your laptop by searching for disassembly videos, or just by removing screws until you get to it.

If this is an Android-specific problem for you, you'll want to take a look at /dev/input/event0 and event1 and event2 and so on.

Figure out which event corresponds to your touchscreen by using the getevent -i command from a shell terminal to read the descriptions, and getevent without the -i to track all inputs, touches, accelerometer movements, etc. in live action to narrow down which event is touchscreen. I have not verified this, but you might be able to disable the culprit driver by changing permissions on the eventXXXXX file to read-only with a root file browser.

I also just found an app that seems promising: Touch Blocker - Google Play
But I'm 99% sure that will prevent using the mouse as well.

Sounds like your original problem is not specific to Android, and you're making this an XY problem.

What you should really do is unhook the touchscreen cable, and that solves it for all 3 operating systems.

On the laptops I've worked on, the ribbon cables for the screen are detachable from both ends: behind the LCD panel, and on the motherboard. Find out which is easiest to get to on your laptop by searching for disassembly videos, or just by removing screws until you get to it.

If this is an Android-specific problem for you, you'll want to take a look at /dev/input/event0 and event1 and event2 and so on.

Figure out which event corresponds to your touchscreen by using the getevent -i command from a shell terminal to read the descriptions, and getevent without the -i to track all inputs, touches, accelerometer movements, etc. in live action to narrow down which event is touchscreen. I have not verified this, but you might be able to disable the culprit driver by changing permissions on the eventXXXXX file to read-only with a root file browser.

I also just found an app that seems promising: Touch Blocker - Google Play
But I'm 99% sure that will prevent using the mouse as well.

added 228 characters in body
Source Link
Aaron Gillion
  • 1.6k
  • 3
  • 13
  • 21

Sounds like your original problem is not specific to Android, and you're making this an XY problem.

What you should really do is unhook the touchscreen cable, and that solves it for all 3 operating systems.

On the laptops I've worked on, the ribbon cables for the screen are detachable from both ends: behind the LCD panel, and on the motherboard. Find out which is easiest to get to on your laptop by searching for disassembly videos, or just by removing screws until you get to it.

If this isis an Android-specific problem for you, you'll want to take a look at /dev/input/event0 and event1 and event2 and so on.

Figure out which event corresponds to your touchscreen by using the getevent -i command from a shell terminal to read the descriptions, and getevent without the -i to track all inputs, touches, accelerometer movements, etc. in live action to narrow down which event is touchscreen. I have not verified this, but you might be able to disable the culprit driver by changing permissions on the eventXXXXX file to read-only with a root file browser.

I also just found an app that seems promising: Touch Blocker - Google Play
But I'm 99% sure that will prevent using the mouse as well.

Sounds like your original problem is not specific to Android, and you're making this an XY problem.

What you should really do is unhook the touchscreen cable, and that solves it for all 3 operating systems.

On the laptops I've worked on, the ribbon cables for the screen are detachable from both ends: behind the LCD panel, and on the motherboard. Find out which is easiest to get to on your laptop by searching for disassembly videos, or just by removing screws until you get to it.

If this is an Android-specific problem for you, you'll want to take a look at /dev/input/event0 and event1 and event2 and so on.

Figure out which event corresponds to your touchscreen by using the getevent -i command from a shell terminal to read the descriptions, and getevent without the -i to track all inputs, touches, accelerometer movements, etc. in live action to narrow down which event is touchscreen. I have not verified this, but you might be able to disable the culprit driver by changing permissions on the eventXXXXX file to read-only with a root file browser.

Sounds like your original problem is not specific to Android, and you're making this an XY problem.

What you should really do is unhook the touchscreen cable, and that solves it for all 3 operating systems.

On the laptops I've worked on, the ribbon cables for the screen are detachable from both ends: behind the LCD panel, and on the motherboard. Find out which is easiest to get to on your laptop by searching for disassembly videos, or just by removing screws until you get to it.

If this is an Android-specific problem for you, you'll want to take a look at /dev/input/event0 and event1 and event2 and so on.

Figure out which event corresponds to your touchscreen by using the getevent -i command from a shell terminal to read the descriptions, and getevent without the -i to track all inputs, touches, accelerometer movements, etc. in live action to narrow down which event is touchscreen. I have not verified this, but you might be able to disable the culprit driver by changing permissions on the eventXXXXX file to read-only with a root file browser.

I also just found an app that seems promising: Touch Blocker - Google Play
But I'm 99% sure that will prevent using the mouse as well.

Source Link
Aaron Gillion
  • 1.6k
  • 3
  • 13
  • 21
Loading