A handful of Pixel 10 Pro XL and Pixel 8a owners say their phones stopped accepting a correct pattern or PIN after installing this month’s Pixel update, leaving them locked out of devices they had unlocked the same way for months. Google has not issued a public statement about the bug, though Android Authority’s reporting found the company quietly messaging affected users directly in the Reddit threads where they first posted.
The two failure modes look different on the surface but land in the same place. One is a pattern the screen simply refuses to recognize; the other is a PIN that appears to lock the phone out after a single keystroke.
Pattern unlock goes dead, PIN entry misfires after one digit
On the Pixel 10 Pro XL, the reported symptom is a pattern-recognition failure: the touchscreen registers the swipe, but the unlock logic behind it does not accept a pattern the owner has used correctly for months. On the Pixel 8a, the complaint runs differently — entering a single digit of a correct PIN triggers a “too many attempts” lockout message, as though the phone had already logged several failed tries from just the first keystroke. One Pixel owner titled a post on Google’s own support forum with the same complaint in plain terms: “The PIN code doesn’t work after installing the update.”
Neither failure resembles a forgotten credential. Both owners describe entering a pattern or PIN they know is correct and watching the phone reject or misread it anyway, which is the detail that separates this from ordinary user error and points instead at something broken in how the lock screen itself processes input after the update. A phone that occasionally mistypes a swipe is a known, tolerable annoyance; a phone that rejects a correct credential outright, every time, is a different category of failure, since it leaves no reliable way back in short of wiping the device.
A factory reset was the only fix that worked
The troubleshooting steps people tried first were the obvious ones: rebooting into safe mode, cleaning the screen, restarting the device, even connecting a mouse to rule out a touchscreen digitizer problem. None of it restored normal unlock behavior for the Pixel 10 Pro XL owner Android Authority spoke with. A full factory reset, wiping the device and switching to PIN-based authentication afterward, was the only method that got the phone unlocked again.
Not everyone reached for that option. A second affected owner instead waited out the lockout timer that PIN entry had triggered, choosing lost time over lost data. Google’s own unlock-troubleshooting page treats erasure as the standard path for a phone that will not unlock at all, walking through a remote wipe via Google Play on another device or a manual reset using the phone’s power and volume buttons — the same trade-off between data and access that both affected owners ended up navigating on their own.
No public statement, and a bulletin that stays silent on it
Google’s silence on the bug is not total — Android Authority’s reporting describes the company reaching out directly to some of the Reddit posters describing the problem — but there has been no public acknowledgment, no support-page known-issue entry, and no fix timeline attached to either device. The September 2026 Pixel Update Bulletin, the document Google publishes each month listing every security fix in that cycle, lists exactly one authentication-adjacent item: a pair of elevation-of-privilege flaws in the Goodix fingerprint hardware and a related biometric information-disclosure issue. Nothing in the bulletin describes a pattern- or PIN-recognition defect, which means the bug either was not caught before the update shipped or was not judged significant enough to document alongside the vulnerabilities Google did disclose.
A matching thread on Google’s Pixel Community forum shows the complaint reaching the company’s own support channel independently of Reddit, meaning affected owners flagged the problem in at least two separate venues Google monitors. The update itself traces back to the September 2026 Pixel Drop, which Google’s own announcement frames around VIP contact widgets, expanded scam detection, and Pixel Watch gestures — a features-and-polish release with nothing in its official changelog suggesting a change to lock-screen authentication logic at all.
How far the bug has actually spread
By Android Authority’s account, the reporter’s own Pixel 6a kept unlocking normally throughout, and the pattern of reports so far points to a narrow slice of Pixel 10 Pro XL and Pixel 8a units rather than a fleet-wide failure. That narrowness is also why the bug is easy for a company the size of Google to under-prioritize: a defect that locks a small number of people out of their own phones generates urgent, personal reports on Reddit and community forums, but not yet the volume that forces a dated, public acknowledgment the way a security bulletin entry would. For the owners already affected, that leaves private outreach through a Reddit thread as the only signal, so far, that Google is working the problem at all.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
More from Morning Overview
- Early electric-car owners are hitting battery and screen failures no one warned them about
- A magnitude 5.3 quake struck off the Oregon coast this week
- Amazon’s Prime refunds are rising to $200 as millions more customers become eligible
- A handful of car engines are so tough mechanics say they almost never wear out
