Pixel 10 pro flashlight burns its own lens, users report

A $999 phone should not barbecue itself. Yet Pixel 10 Pro owners on Reddit are posting close-ups of the LED housing: a black crater melted straight through the diffuser, edges curled like plastic wrap left on a stove.

The photos are hard to argue with

One user left the torch on inside a jacket pocket; another parked the XL face-down on a MacBook palm rest and later found a toasted crescent branded into the aluminum. The lens plastic did not warp—it vaporized, leaving a pinhole that stares back like a dead pixel you can never disable.

Google slipped a brightness slider into Android 16 QPR3, letting drivers crank the LED past the old ceiling. No causal link has been proven, but the timing smells. Thermal throttles are supposed to step in, dim the diode, shut it off. Evidently they nap on the job.

Not every dot is a burn

Plenty of posters panic over the tiny amber speck that is simply the emitter showing through the milky slab. The real damage is darker, irregular, a cigarette burn in a theater seat. Confuse the two and the story balloons into clickbait; know the difference and you still have a flagship that can auto-cremate.

The incident count remains low—under two dozen verified cases—but the failure mode is spectacular. Modern handsets treat the flashlight as an afterthought, a convenience feature exempt from the aggressive cooling budgets reserved for the SoC or the battery. Google’s engineers either miscalculated the LED’s continuous watt-second envelope or assumed users would never leave a pocket sun on long enough to matter. Users just proved otherwise.

Until Google issues a statement—or a silent thermal-config update—treat the torch like a match: useful, but extinguish it before you pocket the flame. A warranty swap will cover the scorch this time; the PR scorch may linger longer.