Touch Lab // Hands-Off Input Monitor
GHOST TOUCH TEST
Start the test, remove your hands during the countdown, and leave the touchscreen completely untouched for 15 seconds. Any new browser-reported touch contact during the monitoring window is logged with its screen position so phantom-touch symptoms can be repeated under controlled conditions.
LOCAL INPUTDetected touch coordinates remain in this page session and are not uploaded by the diagnostic.
How to run a ghost touch test
- Open the page on the touchscreen device that shows the problem.
- Clean/dry the screen and disconnect unusual accessories if you are comparing conditions.
- Optionally enter fullscreen, then press START HANDS-OFF TEST.
- During the 3-second countdown, move both hands completely away from the screen.
- Do not touch the display for the full 15-second monitor window. Any touch contact that starts during that period is logged.
- Repeat several runs, then compare charging versus battery power, with/without a screen protector, or another browser if relevant.
What counts as an incident
The diagnostic counts a new Pointer Event whose browser-reported pointerType is touch and whose pointerdown occurs after the hands-off monitoring phase begins.
A recorded incident means the browser received a touch contact while you said the screen was untouched. It does not prove which physical or software cause produced that contact.
Common causes to compare
Unwanted touch behavior can be associated with a damaged digitizer, moisture, dirt, a lifted or poor screen protector, a case pressing the edge, charging/electrical noise, heat, firmware/driver behavior or physical pressure on the panel.
Change one condition at a time so repeated results are easier to interpret.
Why repeat the test?
Intermittent ghost touches may not appear in a single 15-second sample. Multiple clean runs with zero incidents are more reassuring than one run, while repeated incidents in a similar physical region give stronger evidence of a reproducible symptom.
What the page cannot know
- Whether another object actually contacted the glass.
- Whether a case/protector or charger caused the event.
- Raw digitizer electrode state or electrical noise.
- Touch behavior outside the browser, such as the lock screen.
- Whether the event originated from firmware filtering rather than the physical panel.
Mouse and pen input
Mouse and stylus pointer events are ignored by the incident counter. The tool specifically counts browser events labeled as touch so desktop pointer movement does not create false ghost-touch incidents.
Ghost touch test FAQ
I got one incident. Is my digitizer broken?
Not necessarily. Repeat the hands-off test, clean/dry the display, and compare other conditions. Repeated incidents when nothing is touching the screen are stronger evidence.
Why is there a countdown?
It prevents the touch used to press Start from being counted as a ghost touch and gives you time to move your hands away.
Can charging cause ghost touches?
Power/grounding or charger-related behavior can be one comparison condition on some devices. Run the same test on battery and while charging, changing nothing else.
Does this upload the incident coordinates?
No. The coordinates are displayed and stored only in this page's current in-memory session.
Related touchscreen diagnostics