Your Phone Is Tapping Itself
You set the phone face-up on the table. You walk away. You come back to find three apps open, a half-typed message sent to someone you haven't texted in months, and the volume cranked to maximum. Your finger was never near it. The phone just decided to do things.
This isn't software haunting you. It's capacitance, gone wrong.
The Invisible Grid Underneath Your Glass
Modern touchscreens work by measuring electrical charge. Beneath the glass sits a grid of transparent electrodes, usually made from indium tin oxide, arranged in rows and columns. Your finger, being full of water and salts, conducts electricity. When it hovers close to the screen, it disturbs the electrical field at that intersection point. The controller chip reads the disturbance, triangulates a coordinate, and passes it to the operating system as a touch event.
This is called projected capacitive sensing. It's elegant when everything is intact.
The grid only responds to conductors. Dry glass does nothing. A fingernail does almost nothing. A wet fingertip lights it up immediately. The whole system is calibrated around one assumption: the glass is a clean, uniform insulating layer between the electrode grid and whatever is touching it. Crack that glass, and the assumption collapses completely.
What a Crack Actually Does to the Signal
Think of the electrode grid as a milligram-precision scale. Now drop something heavy on one corner. The readings don't stop. They go wrong in ways that look entirely plausible.
A crack in the glass causes damage on several levels at once. First, it changes the dielectric properties of the insulating layer. Where the glass was a uniform barrier, there's now an air gap, or worse, a fracture that lets moisture in. Air and cracked silica carry different capacitance values than intact glass, so the controller chip sees unexpected charge readings at those coordinates and, because it's built to interpret charge disturbances as touch events, it does exactly that.
Second, cracks create edges. Sharp internal edges accumulate static charge, especially in dry environments, and a small static build-up along a fracture line looks electrically like a fingertip resting on the screen. The chip cannot tell the difference.
Third (and this one is genuinely insidious): fractured glass develops micro-conductive paths. Broken glass sometimes leaves a trail of partially conductive particles bridging the crack. That path acts like a low-grade conductor draped across the electrode grid, producing a persistent phantom contact that wanders slightly as temperature changes make the crack expand and contract.
Picture it in practice. A phone dropped face-down develops a spiderweb crack in the lower-right corner. That corner now generates phantom swipe gestures from right to left, consistently, every few seconds. The owner can't dismiss notifications because every attempt triggers the phantom swipe first. The display pixels are fine. No internal hardware was touched by the impact. The phone is, for practical purposes, unusable.
And the digitizer never broke. The glass did.
The Wet Screen Problem Is Slightly Different
Water is a conductor. Not a great one, but good enough to fool a capacitive grid.
A thin film of water on a screen doesn't affect one touch point. It bridges multiple electrode intersections simultaneously, so the controller chip suddenly sees dozens of contact coordinates at once, far more than any human hand could produce. Most phones carry ghost-touch filtering in their firmware, designed to reject obviously impossible inputs, but a continuous water film overwhelms that filter. The result is frantic, random phantom taps firing faster than the firmware can reject them.
Rain is the classic culprit. A few drops produce isolated phantom taps. A sustained drizzle on an exposed screen can lock the phone into a feedback loop where phantom taps open apps, which generate on-screen buttons, which the phantom taps then press, which opens more things. A warehouse worker named Mia once watched her phone call her manager three times in ten minutes while it sat face-up on a wet packing bench. Every time she ended the call and set the phone down, the water on the screen redialled.
The physics here is simpler than the crack scenario. Water is just doing what fingers do, except spread across a large area with absolutely no intention behind it.
What People Assume (And Why They're Wrong)
The common assumption is that phantom touches mean a failing digitizer, the touch-sensing layer itself. Sometimes that's true. But in crack and water cases, the digitizer is almost always working perfectly. It's reading the inputs it receives with complete accuracy. The inputs are just wrong.
This is not a minor distinction. It matters enormously for repair decisions.
If phantom touches are caused by a cracked outer glass layer, replacing only the glass rather than the full display assembly sometimes resolves the problem entirely. If the impact damaged the digitizer itself, you need the whole assembly. The diagnostic test is simple: phantom touches that appear only along the crack lines suggest the digitizer is fine. Phantom touches scattered randomly across the whole screen suggest the digitizer layer itself is compromised.
For water, the fix is drying, not replacement. A phone that phantom-touches in the rain and behaves perfectly once dry has a functional digitizer. One that keeps misbehaving after 24 hours in a dry environment probably has moisture inside the assembly, which is a slower-moving problem and a different repair conversation entirely.
So before you pay for a full display replacement: where are the phantom touches appearing?
The Number That Actually Tells You Something
Capacitive grids on modern phones typically refresh their touch readings between 60 and 240 times per second. Gaming phones push higher. At 120Hz touch sampling, the controller makes 120 independent decisions per second about whether a contact exists. A crack that produces a faint capacitive anomaly might only trigger a phantom read on 20 of those samples. That's still enough to register as a deliberate touch.
Higher refresh rates, counterintuitively, can make phantom touch problems worse on cracked screens. More samples means more opportunities to misread the anomaly.
Your screen isn't really a surface. It's a conversation between your body's electrical properties and a very fast, very literal-minded measurement system, one that has no concept of intent and only knows charge. Give it an unexpected source of charge, a crack, a raindrop, a fracture line full of static, and it will report a touch with complete confidence.
The phone isn't haunted. It's just too good at its job.