Damage symptoms

Screen Damage Symptoms: Start With What You See

Start here when you can describe what the screen is doing but do not yet know why. Compare the closest symptom first, then move into the most likely cause.

  • Start with what you can see
  • Plain-English symptom checks
  • Clear next steps when the cause is still unclear

Maintained by

Jacob Dymond

Founder and Editor

Content updated: April 14, 2026

Choose the right symptom guide

Match what you see to the closest row and open the linked guide.

What you see

A black patch, dark area, or spreading spot under the screen

Likely issue
Usually points toward internal pressure damage, liquid intrusion, or heat-stressed layers rather than a single dead pixel.
Mistaken for
Often confused with a dead pixel, dirt, or a screen protector bubble.

What you see

Lines that showed up after pressure, a squeeze, or a flex event

Likely issue
Lines that begin after physical stress are much more likely to be panel damage than a random software issue.
Mistaken for
Often confused with driver problems, GPU issues, or hinge-angle quirks.

What you see

Touch acting on its own, drifting, or firing random taps

Likely issue
Digitizer instability after damage can lock you out or make the device unsafe to control.
Mistaken for
Often dismissed as lag, a temporary touch bug, or safe to keep using.

What you see

One strip, corner, or section of the touchscreen no longer responds

Likely issue
Local touch failure often means physical screen damage even when part of the display still looks normal.
Mistaken for
Often confused with dirt, a case edge, or a minor annoyance.

What symptom guides can and cannot prove

Use these to classify visible damage. They do not replace hands-on inspection or policy decisions.

Route type

Symptom pattern matching

When it fits
The visible pattern is clearer than the event history behind the damage.
Stop rule
Stop comparing symptoms once one guide clearly fits and the next safe move is obvious.
Cannot prove
Exact failure layer (digitizer vs panel vs cable) without hands-on inspection.

Route type

Cause narrowing after a symptom match

When it fits
You identified the visible pattern and now need pressure, water, or heat context.
Stop rule
Stop at cause guides once the next step is backup, evidence, or service—not more theory.
Cannot prove
Which cause triggered the symptom if the device history is unreliable.

Route type

Urgent touch instability (ghost touch or dead zones)

When it fits
Touch is erratic, unsafe, or one area no longer responds while access still matters.
Stop rule
Do not keep stress-testing when backup or safer access should come first.
Cannot prove
Whether touch will recover without replacing the panel or digitizer stack.

Route type

When to stop comparing symptoms

When it fits
The device, your data, or your claim matters more than naming the damage perfectly.
Stop rule
Move to action pages or cause guides instead of endless symptom checking.
Cannot prove
Warranty approval, repair quotes, or how long the panel stays usable.

What to do after you identify the symptom

Move into cause guides, tests, or urgent action paths once the visible pattern is clear.

After you identify

Pressure or flex event is the strongest explanation

What it means
Bruising, lines after squeeze, or lid-pressure fits a pressure damage story.
Next step
Open the pressure damage guide to narrow the internal failure pattern.

After you identify

Liquid exposure or staged worsening is plausible

What it means
Spills, rain, condensation, or delayed failure often track water damage.
Next step
Open the water damage guide before the panel is pushed further.

After you identify

Heat, sun, or thermal load preceded the symptom

What it means
Dim zones, discoloration, or touch drift after heat point toward thermal stress.
Next step
Open the heat damage guide to compare the likely failure mode.

After you identify

Screen is stable enough for controlled evidence

What it means
The device is readable enough to test without creating extra risk.
Next step
Run the matching screen test to capture repeatable evidence.

After you identify

You need backup or evidence before the pattern changes

What it means
Access, data, or warranty proof may matter more than further symptom comparison.
Next step
Open the action path that protects what you need first.

After you identify

You need photos or files before touch or display fails further

What it means
Ghost touch, spreading bruises, or liquid exposure can close the backup window fast.
Next step
Back up or document before the visible pattern changes.

FAQ

Symptom FAQs

Answers on pattern matching, safe next moves, and when to stop comparing symptoms.