Symptom Hub
Use the symptoms hub when you know what the display is doing but not what caused it. Start with the visible pattern, compare the strongest symptom paths, and move into the right damage mechanism before you guess.
Symptoms first
You do not need to know yet whether the cause was pressure, water, or heat. If you can describe the screen behavior clearly, start here and use the routes below to match the pattern before you guess at the cause.
This hub is the right place if you are looking at:
A black patch, dark area, or spreading spot
Use this hub when the screen shows a visible change you can point to right away.
Lines that showed up after pressure or a flex event
Start with the pattern before you decide whether pressure, moisture, or something else is behind it.
Touch acting on its own or becoming hard to control
Erratic touch, ghost taps, or drifting input belong here before you jump into repair guesses.
One part of the touchscreen no longer responding
Dead strips, corners, or keyboard areas are symptom-first problems before they are cause-first problems.
If the bigger problem is backup, access, or documenting the damage before it changes, stop here and switch to the action paths.
Primary symptom routes
The clearest visible patterns deserve the largest footprint. Supporting symptom routes stay available, but they should not compete with the strongest first moves.
Visible pattern
Use this when the screen shows a localized dark patch, black area, or spreading spot under the display.
Usually points toward internal pressure damage, liquid intrusion, or heat-stressed layers rather than a simple browser issue.
Visible pattern
Use this when vertical or horizontal lines appeared after a squeeze, twist, or lid-pressure event.
Good starting point when the user knows something physical happened but the exact internal failure is still unclear.
Visible pattern
Use this when the display still lights up but touch begins firing on its own or behaving erratically.
Useful when you need to separate digitizer instability from broader panel failure and decide whether backup comes first.
Visible pattern
Use this when one strip or block of the display stops responding while the rest still works.
Helps users decide whether they are dealing with localized hardware damage, a cover-layer problem, or a route that needs service.
Mechanism bridges
Once the symptom route makes the likely cause clearer, move into pressure, water, or heat. Use tests as a utility tool, not a competing branch.
Likely cause
Use this when a squeeze, flex event, bag pressure, or closed-lid accident is the strongest explanation once the symptom is clearer.
Likely cause
Use this when spill history, condensation, or staged worsening makes moisture the stronger branch.
Likely cause
Use this when the symptom appeared after direct sun, trapped heat, or another stronger thermal event.
Utility route
Use tests when the device is still usable enough to capture evidence before you commit to a damage branch.
Decision guardrails
Symptoms help sort the evidence. They should not trap the user in endless scrolling once access, evidence, or safe handling becomes the bigger issue.
Keep the next move clearer than the taxonomy.
Next move
Use these routes to improve the decision, not to keep comparing cards after the next safe move is already clear.
Reviewed and maintained by Jacob Dymond
Founder, ScreenDetect
Last reviewed 2026-04-09
ScreenDetect maintains this hub as a symptom-first routing page. The goal is to help users identify what the screen is doing, narrow the strongest mechanism, and move into action before uncertainty turns into preventable loss.
Source basis