Touch Screen Test

Run this test on the touchscreen that's misbehaving. The main mode maps missed taps, broken drag paths, weak edges, and areas that fail on a second pass. Ghost mode watches for input while the glass is untouched. The result records what this browser received; it cannot identify the failed part.

What is the best way to test a touch screen problem?

For most problems, the best touch screen test is the Touch Screen Test run on the affected device. Use it to find missed touches, dead zones, broken drag paths, and multi-touch issues. Use the Ghost Touch Test when the screen registers input you did not make.

For the most complete edge and corner check on a phone or tablet, use your browser’s Add to Home Screen option, open the page from the new home-screen icon, and then start the Touch Screen Test. This removes more browser chrome so you can reach closer to the true display edges. If you cannot add the page to your home screen, use the fullscreen control and treat the browser edges as not fully tested.

A fixed shadow, icon, or image that remains visible is not a touch result. Run the burn-in test to compare image retention and persistent OLED burn-in.

Before you assume the screen has failed

Remove conditions that can change touch input before comparing results. Change one condition at a time so you know what affected the next run.

How to run a complete touch screen test

Open the tester on the affected device and use a finger on the glass. Sweep the full surface once, then trace only the places that remained uncovered. The second pass matters because one missed cell may come from the way you moved; the same gap twice is more useful evidence.

What the first pass and gap check show

Check multi-touch with separate contacts

Place two fingers on different parts of the test area, then add more one at a time. Watch the live contact count and the individual paths. A contact that vanishes, merges with another, or stops moving is more informative than the count alone.

The report compares the most contacts seen during the run with the maximum reported through the browser. That comparison describes this browser session. It does not certify the digitizer’s factory specification or prove why a contact dropped.

Use fullscreen when browser controls hide an edge

Fullscreen exposes more of the browser viewport, which makes the outer rows and corners easier to reach. It does not make the sensor more accurate. Note whether a suspected edge passes only after entering fullscreen; the first run may simply have missed part of the available test area.

Test a stylus separately from finger input

A mouse or trackpad only previews the test. A passive stylus may behave like a finger, while an active pen can use hardware and software that finger input does not. If finger paths remain continuous but the pen skips, record that difference instead of calling the entire touchscreen defective.

Some browsers expose a pressure value for compatible pointer hardware. The value is browser-reported input, not a calibrated force measurement. A missing pressure value does not show that the touchscreen has failed.

How to test for ghost touch

Ghost touch is input reported while you are not touching the screen. Run the hands-off mode when the device taps, types, swipes, or drifts by itself. The test can record the unwanted contacts, but it cannot identify their cause from the browser alone.

Read a ghost touch result by repetition and location

One isolated contact is a weaker finding than a pattern that returns during another untouched run. Contacts concentrated near one area are different from contacts scattered around the screen, but location alone does not identify the damaged part or prove that hardware caused the input.

• Only while charging: Compare another compatible cable, charger, and outlet before blaming the screen.
• Only with a case or protector: Repeat with the accessory removed or reseated, if removal is safe.
• Only in one app: Compare the same area in the browser, system interface, and another app.
• Across clean, untouched runs: Save the result and arrange manufacturer or repair support if the device is becoming hard to control.

How to confirm a touch screen dead zone

A dead zone is an area where intended touch input does not reach the browser. Confirm it by tracing the same place twice. The shape and repeatability of the gap matter more than a single untouched cell.

Look for the same gap on both passes

A connected strip or patch that remains uncovered after a deliberate second pass is stronger evidence than scattered misses. Keep your grip, orientation, and path consistent during the comparison. Pressing harder or changing several conditions produces a different test.

Compare the screen with and without external pressure

Repeat the same edge or corner after removing a case or loose protector, if it is safe to remove. A gap that disappears after that change points to the accessory or its fit as part of the problem. A gap that remains does not identify the failed component, but it gives support or a repair provider a reproducible location to check.

What your touch screen test result means

The report describes the evidence collected during this browser session. Read the named result against the matching explanation below. None of the results identifies a failed component or decides warranty coverage.

Possible dead zone: the same area failed twice

The confirmation pass left a connected area uncovered in the same location. This is the strongest localized pattern the browser test reports. Repeat once with the screen clean, dry, unplugged, and free of external pressure before treating it as a persistent screen problem.

Next: save the result, note where the gap appears, and review the touchscreen dead-zone guide.

No repeat failure found: the second pass covered the gap

The test did not reproduce one fixed unresponsive area. That is reassuring for this run, but it does not prove that touch works in every app or condition. Repeat the test while recreating the original problem if the failure is intermittent.

Next: use touch ghost mode if the problem is unwanted input. Compare another app or a built-in diagnostic if touch fails outside the browser.

Retest the remaining gap: the result is inconclusive

A few cells remained uncovered, but they did not form a strong repeatable pattern. Trace that area again slowly in fullscreen. Keep the device still and do not press harder to force a different outcome.

Ghost touch contacts seen: the browser logged untouched input

The browser received contacts during the hands-off window. Repeat the check after drying the screen and disconnecting accessories. A second controlled run shows whether the behavior persists; it still cannot tell you whether the cause is the screen assembly, electrical interference, software, moisture, or external pressure.

Next: compare the pattern with the ghost touch problem guide if the behavior began after a drop, pressure, or visible damage.

One pass or a mouse preview is not a touch result

One pass only identifies areas to recheck. Mouse and trackpad input can preview the interface but never touches the digitizer. Finish the confirmation pass on the affected touchscreen before interpreting the report.

What this browser test can and cannot measure

The page receives events exposed by the browser. It can map where those events occurred and whether a pattern repeated. It cannot inspect the electronics beneath the glass or observe touch behavior outside this page.

Touch latency and sampling rate need different tools

A smooth path does not measure the delay between physical contact and the device’s response. Browsers may combine several movement updates into one event, and frame rendering adds another timing layer. This test does not report hardware latency or raw digitizer sampling rate in milliseconds or hertz.

If a game feels delayed while coverage remains complete, compare the behavior inside the affected game and use device-specific diagnostics or documented specifications. That is a different problem from a fixed area that never registers.

Touch screen test codes and manufacturer diagnostics

There is no universal touchscreen test code. Samsung, Google, and Xiaomi document different routes, while Apple does not publish an equivalent touch-test dialer code. Menus and codes can still vary by model, region, carrier, and software version.

The Pixel code opens the broader Repair Diagnostics App; Google does not describe it as a dedicated touch-grid code. Apple Diagnostics Mode is likewise a repair workflow, not an iPhone equivalent of Samsung’s Touch grid. Avoid third-party secret-code lists that do not identify a current manufacturer source.

How to test different touchscreen devices

Run the browser test on the affected surface in every case. The useful follow-up depends on the device because manufacturer diagnostics, settings, and system-level checks differ.

iPhone and iPad

Use a finger for the main coverage pass and test Apple Pencil or another stylus separately. Apple does not publish a consumer touch-test dialer code. Diagnostics Mode supports its Self Service Repair process, so it should not be treated as a substitute for this coverage test. If the browser result is clean but taps or swipes fail elsewhere, check Touch Accommodations and follow Apple’s touch troubleshooting.

Android phones and tablets

Repeat the same physical path after restarting. If the problem persists, compare Safe mode or the manufacturer’s diagnostic app when available. A failure confined to one downloaded app is different from the same area failing in the browser, system interface, and built-in diagnostics.

Samsung Galaxy

Samsung Members is the primary documented route: open Diagnostics, choose Phone diagnostics, then Touch screen. On supported Galaxy models, *#0*# may also open a hardware menu with a Touch grid. The code is not available on every model, carrier, region, or software configuration.

Google Pixel

Google documents *#*#7287#*#* for opening the Pixel Repair Diagnostics App on supported devices. It is a broader repair diagnostic, not a documented shortcut to a touch grid. Pixel 9, Pixel 9 Pro, and Pixel 9 Pro XL also have Touch diagnostics under Display & touch. Do not assume that settings route exists on another Pixel model.

Xiaomi

Xiaomi documents *#*#6484#*#* for hardware detection on supported devices. Select Touch screen test, then draw across the display and look for broken paths or marks that appear away from the finger. Availability can vary by model, region, and software version; the source reviewed does not establish the same route for every Redmi or POCO device.

Windows, Surface, and touchscreen monitors

For Surface, Microsoft’s UEFI touch test can help separate Windows behavior from a problem that remains outside the operating system. In Windows, check updates and confirm that the HID-compliant touchscreen is enabled. An external touch monitor usually sends touch data through USB, so inspect that connection separately from the video cable.

How to document a touchscreen problem

Save the result after a repeatable failure, then record the conditions that produced it. A screenshot is more useful when another person can understand what was tested and what changed between runs.

A saved result documents browser-level behavior. It does not guarantee a warranty decision. For a fuller record, use the warranty and support documentation checklist before making permanent changes.

Should you retest, troubleshoot, or arrange repair?

Base the next action on repeatability and context. Stop repeating the same browser test once the result is stable; another identical pass will not identify the internal cause.

If touch is becoming hard to control, back up the device while access remains. Visible damage, liquid exposure, a lifting screen, unusual heat, or a failed repair needs device-specific safety and service guidance before more testing.

When the behavior is stable and documented, compare repairing versus replacing the screen or review whether the broken display can be repaired.

Sources and testing limits

The test records pointer input exposed to this page. It does not access raw digitizer hardware, other apps, the lock screen, repair records, or warranty systems. Result language was checked against the current implementation so observations remain separate from possible causes.

Manufacturer guidance supports the device-specific troubleshooting and diagnostic routes. Browser documentation supports the limits around coalesced movement events, reported touch-point capacity, and pressure values. Sources were reviewed on the dates shown below.