Direct answer
For the Google Pixel 10, one app/region, moisture, protector/case, charger interference and display hardware should be separated. First, remove charger/case/protector for a dry-room test.
What this covers
- Google Pixel 10 (2025 Pixel 10; confirm hardware model in Settings)
- Current Pixel family; modem, Tensor generation, biometric features and Android eligibility vary by exact model and region.
- The specific fault this record addresses: screen or touch input is not working correctly
What it does not cover
- ×The same symptom on a different Google product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
A screen protector or case interfering
What separates it Touch is unreliable at the edges, or a thick protector was fitted recently. Edge gestures are the first thing to suffer, and a lifted protector traps air that the digitiser reads through.
How to confirm Remove the protector and case and retest the same gestures. This is quick, free, and accounts for a lot of 'the edges stopped working'.
- 2
Moisture, grease or sweat on the glass
What separates it Touches register in the wrong place, or the screen behaves as though something is touching it. Water bridges the capacitive field and the digitiser reads it as a finger.
How to confirm Dry the screen and your hands thoroughly and retest. Phantom touches in a bathroom or in rain are usually this and nothing else.
- 3
The phone has been dropped
What separates it A dead strip, an area that does not respond, or touches landing offset — starting after an impact, with or without visible glass damage. A digitiser can separate from the display without the glass cracking.
How to confirm Map the unresponsive area by dragging a finger slowly across the whole screen. A consistent region is physical; a wandering one is not.
- 4
The phone is too hot or too cold
What separates it Touch degrades in a hot car or in a hard frost and recovers indoors. Both the display and the digitiser have an operating range.
How to confirm Bring it to room temperature and retest before concluding anything.
- 5
A software freeze rather than a touch fault
What separates it The screen is showing something and ignoring everything, including buttons. The phone has stopped responding, not stopped sensing.
How to confirm Force-restart. A phone that responds afterwards had a software freeze, which is a completely different problem from a digitiser fault.
- 6
One app rather than the whole phone
What separates it Touch fails inside a particular app and works everywhere else. An app can capture or mishandle input without the system being affected.
How to confirm Test the same gestures on the home screen and in settings. Working there exonerates the hardware entirely.
- 7
A charger injecting noise into the digitiser
What separates it Phantom touches or erratic behaviour only while charging, particularly on cheap or unearthed adapters. The digitiser is sensitive to electrical noise.
How to confirm Unplug and retest, then test on a different adapter. This is a real and frequently missed cause.
- 8
An accessibility or display setting changed
What separates it Touches need to be held longer than expected, or gestures behave differently, with no impact and no app pattern. Touch accommodations and gesture settings do exactly this.
How to confirm Review the accessibility touch settings. These get enabled accidentally and are hard to guess at.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Whether the image itself is wrong, or the image is perfect and touch is not. Display and digitiser are two different components and this question separates them.
- A map of where touch fails, made by dragging slowly across the whole screen — a consistent region means something different from scattered failures.
- Whether it fails everywhere or only inside one app.
- Whether it fails only while charging, and on which adapter.
- Whether the phone has been dropped, and whether there is any visible damage — including none.
- The temperature, and whether it recovers indoors.
- Whether a screen protector or case is fitted, and when it was fitted.
Separate the display from the digitiser
ReversibleWrong pixels, lines or dead areas in the image are a display fault. A perfect image that ignores or misplaces touches is a digitiser fault. They are two components stacked together, they fail independently, and every step below depends on knowing which one you have.
Force-restart before anything else
ReversibleA phone that has frozen shows a static image and ignores every input, which is indistinguishable from a dead touchscreen until you restart it. This is fast, safe, and it rules out the single most recoverable cause.
Remove the screen protector and case
ReversibleEdge gestures suffer first, and a lifted protector traps air that the digitiser reads through. This costs nothing and it accounts for a large share of complaints that the edges have stopped responding.
Dry the screen and your hands
ReversibleWater bridges the capacitive field and the digitiser reads it as a finger, which produces both missed touches and phantom ones. Erratic behaviour in a bathroom, in rain, or with damp hands is usually only this.
Map the failure by dragging slowly across the whole screen
ReversibleA consistently unresponsive band or region is physical damage — a digitiser can separate from the display without the glass cracking. Failures that wander are not physical, and that distinction decides whether this is a repair or a settings problem.
Test the same gestures in another app and on the home screen
ReversibleTouch failing inside one app and working elsewhere exonerates the hardware completely. An app can capture or mishandle input without any system-level fault, and no amount of hardware troubleshooting will help.
Unplug the charger and retest
ReversibleA cheap or unearthed adapter can inject enough electrical noise to produce phantom touches, and the symptom appears only while charging. This is real, frequently missed, and testing a different adapter settles it.
Review the accessibility touch settings
ReversibleTouch accommodations, hold durations and gesture settings do exactly what a failing digitiser appears to do, and they get enabled accidentally. They are impossible to guess at from the symptom, so they have to be checked deliberately.
Bring the phone to room temperature
ReversibleBoth the display and the digitiser have an operating range, and touch genuinely degrades in a hot car or a hard frost. Judging a screen while the phone is outside that range measures the temperature, not the screen.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- 2025 Pixel 10; confirm hardware model in Settings. Current Pixel family; modem, Tensor generation, biometric features and Android eligibility vary by exact model and region.
- Display
- 6.3-inch Actua display, 20:9, 1080 x 2424 OLED at 422 PPI, Smooth Display 60–120Hz, Corning Gorilla Glass Victus 2. Note the refresh floor: this model runs 60–120Hz, not the 1–120Hz LTPO of the Pro models, so it cannot drop as low when idle — which is a real, if small, battery difference between them.
- Brightness
- Up to 2000 nits (HDR) and up to 3000 nits peak, with a contrast ratio above 2,000,000:1. Brightness is among the largest discretionary battery costs on any phone, so heavy outdoor use at peak costs real runtime here rather than indicating a fault.
- Battery
- Typical 4970mAh (minimum 4835mAh), rated by Google at 24+ hours, or up to 100 hours with Extreme Battery Saver. Compare your own runtime against that 24-hour figure and your own history rather than against a Pro model.
- Charging
- Fast charging to about 55% in around 30 minutes using a 30W USB-C PPS charger or higher, sold separately. The adapter is the variable people miss — a lower-output adapter or a laptop port falls well short of that figure, which is the usual reason charging seems far slower than advertised.
- Wireless charging
- Pixelsnap wireless charging, Qi2-certified, up to 15W. Qi2 uses magnets for alignment, so a thick case, a metal plate or a card between phone and charger defeats it entirely while cable charging carries on working.
- Memory and storage
- 128GB or 256GB, both with 12GB RAM. The RAM figure matters for one specific symptom: apps reloading from scratch when you switch back to them is memory pressure rather than crashing.
- Processor
- Google Tensor G5 with a Titan M2 security coprocessor. The chip generation is what governs how long this model keeps receiving Android and security updates.
- Cameras
- Triple rear system: 48MP Quad PD wide (ƒ/1.70, 82° field of view, 1/2" sensor), 13MP ultrawide (ƒ/2.2, 120° field of view, 1/3.1" sensor), and a 10.8MP Dual PD 5x telephoto, with Super Zoom up to 20x and optical quality at 0.6x, 1x, 5x and 10x.
- Google's own specification
- Google publishes the full specification at store.google.com/product/pixel_10_specs. Where any figure above matters to a decision, that page is the authority and this one is not.
- Symptom boundary
- This record covers Google Pixel 10 when it screen or touch input is not working correctly. A different symptom on the same hardware, or this symptom on a different Google product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !There is a consistent dead region, an offset that does not move, or visible damage — the digitiser has failed and it is a repair.
- !The image itself is wrong: lines, discolouration, dead pixels or a spreading dark area. That is the display, and a spreading area gets worse.
- !Touch failed after liquid exposure, which frequently progresses even after the phone appears to dry out.
- !The screen is lifting at an edge, which is the battery swelling underneath it — a stop condition.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Google Pixel Help publishes this as "Fix touch & response issues on your Pixel screen". Google's article for exactly this symptom. Probed 2026-08-23 14:37, before the help-centre crawl tripped Google's rate limit: title-verified. What that article does not carry is the model boundary — it is written for a product line, and 2025 Pixel 10; confirm hardware model in Settings is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
How long should the Pixel 10 battery last?+
Google rates it at 24+ hours, or up to 100 hours with Extreme Battery Saver, on a typical 4970mAh cell. Judge your runtime against that figure and your own history rather than against a Pro model, whose battery and display behave differently.
How fast does the Pixel 10 charge?+
Google rates it at about 55% in around 30 minutes, using a 30W USB-C PPS charger or higher — sold separately. The adapter is the variable people miss: a lower-output adapter or a laptop port falls well short, which is the usual explanation for charging that seems far slower than advertised.
Does the Pixel 10 support magnetic wireless charging?+
Yes — Pixelsnap wireless charging, Qi2-certified, up to 15W. Because Qi2 aligns magnetically, a thick case, a metal mount plate or a card in the case defeats it entirely, while cable charging carries on working perfectly. That is the first thing to check if wireless charging stops.
What is the Pixel 10 screen refresh rate?+
Smooth Display at 60–120Hz. Worth knowing that this is not the 1–120Hz LTPO panel used in the Pro models — it cannot drop as low when the screen is idle, which is a small but genuine difference in standby battery behaviour between the two.
How bright is the Pixel 10 screen?+
Up to 2000 nits in HDR and up to 3000 nits peak. Poor outdoor readability below that is normally the ambient light rather than a display fault — and sustained use at peak brightness is one of the largest single battery costs on the phone.
How much can the Pixel 10 zoom?+
Super Zoom up to 20x, with optical quality at 0.6x, 1x, 5x and 10x from a 10.8MP 5x telephoto. A close-up that will not focus at the long end is normally the telephoto's minimum focus distance rather than a fault — repeating the shot at 1x confirms it.
How much RAM does the Pixel 10 have?+
12GB, with either 128GB or 256GB of storage. RAM is the figure that explains apps reloading from scratch when you switch back to them — that is memory pressure rather than the apps crashing, and a restart clears it.
The screen is frozen and nothing works.+
Force-restart it first. A frozen phone shows a static image and ignores every input, which is indistinguishable from a failed touchscreen until you restart. If it responds afterwards, you had a software freeze, which is an entirely different problem from a digitiser fault.
The edges of the screen stopped responding.+
Take the case and screen protector off and retest. Edge gestures are the first thing a thick protector or a case lip interferes with, and a protector that has lifted slightly traps air the digitiser has to read through. This is free to rule out.
It registers touches in the wrong place when my hands are wet.+
Water bridges the capacitive field and the digitiser reads it as a finger. That produces both phantom touches and missed ones, and it is not a fault — dry the screen and your hands and it goes away. Wet-hand behaviour in a bathroom is this almost every time.
Part of the screen does not respond at all.+
Drag a finger slowly across the whole screen and map exactly where it fails. A consistent band or region is physical damage — and a digitiser can separate from the display in a drop without the glass cracking, so no visible damage does not rule it out.
It only misbehaves while charging.+
Try a different adapter. A cheap or unearthed charger can inject enough electrical noise into the digitiser to cause phantom touches, and the symptom appears only while plugged in. It is a real cause and an easy one to miss.
Touch is fine everywhere except in one app.+
Then the hardware is fine. An app can capture or mishandle input without any system-level fault, so the investigation belongs with that app — update it, clear its data, or reinstall it. Nothing done to the screen will change it.
The screen went strange after I dropped it.+
Establish which layer. A wrong image is the display; a perfect image that ignores touch is the digitiser. Both can fail from an impact with no visible glass damage, and both are repairs rather than configuration.
I have to press harder than I used to.+
Check the accessibility touch settings before assuming hardware. Touch accommodations and hold durations produce exactly this and are enabled accidentally more often than people expect — they are impossible to infer from the symptom.
The screen is lifting at one corner.+
That is the battery swelling underneath it, not a screen problem. Stop charging the phone, do not press the screen back down, and treat it as a stop condition regardless of how well the touchscreen otherwise works.
Does this answer apply to every Google model?+
No. It is scoped to 2025 Pixel 10; confirm hardware model in Settings. Current Pixel family; modem, Tensor generation, biometric features and Android eligibility vary by exact model and region.
What should I record before troubleshooting touchscreen or screen not responding?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing touchscreen, screen not responding. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Stop for lifted display, swelling, cracks, heat or liquid exposure.
Answer for the exact device and software version shown above.