The one thing your phone should never fail at is opening. Google’s September Pixel Drop is reportedly doing exactly that — locking some Pixel owners out of their own devices.
The update arrived with the usual goodies: an improved VIP contacts widget, stronger scam detection, and the Pause Point feature for older models. But since installing it, owners across the Pixel 6 through Pixel 10 lineups have reported that their lock screens have gone rogue.
The Pattern That Never Finishes
According to GSMArena, the trouble surfaced on Reddit, where a Pixel 10 Pro XL owner said the phone wouldn’t even let them finish drawing their unlock pattern. The screen reset before they could connect the second dot.
Another Pixel 10 Pro XL owner in the same thread hit the same wall and got lucky: holding the Power and Volume Down buttons for a hard restart brought the phone back to life. The original poster wasn’t so fortunate. After every workaround failed, the only way back in was a factory reset — the nuclear option that wipes anything not already backed up.
It’s Not Just One Phone — or One Unlock Method
A Pixel 8a owner in a separate thread reported a “wrong PIN” error after typing just the first digit. A Pixel 8 Pro owner described the identical symptom. So this isn’t a pattern-lock problem or a 10 Pro XL problem. It’s a lock-screen problem.
The common thread across the reports: the lock screen appears to be accepting input too eagerly, cutting off PIN or pattern entry before the user has finished typing or tracing. Android doesn’t even allow one-digit PINs or one-segment patterns, so treating half-finished input as a failed attempt is an unmistakable software bug.
It compounds from there. Repeated failed unlock attempts trigger Android’s standard lockout timer, which means affected users get to stare at a countdown before they can even try again — on a phone that may never accept the correct input anyway.
What to Try If You’re Stuck
If your Pixel is already affected, the one workaround that has worked is the hard restart: hold Power and Volume Down together until the phone reboots. It fixed the issue for at least one owner, though not for everyone.
And if you haven’t installed the September Pixel Drop yet, Wirefly — which picked up the same reports — echoes the sensible advice: hold off until Google ships a fix. There’s no confirmed timeline for one yet.
Google’s official PixelCommunity support account has seen the Reddit threads and reached out to affected users directly, which suggests the company is aware of the problem. But it has not issued a public statement, confirmed a general defect, or promised a patch date.
Why this matters
A phone that won’t unlock isn’t a glitch. It’s a brick with your photos inside. And this is the second time in a single week that a flagship has shipped a broken basic: Apple’s iPhone 18 Pro Face ID bug was crashing and rebooting phones until the company promised a fix within days. Now it’s Google’s turn — except Google hasn’t promised a fix at all, just support-team DMs on Reddit.
There’s a second red flag buried in the same reports. GSMArena also notes that owners of Pixel 6, 7, 8, 9, and 10 phones are complaining the update made their devices noticeably laggy. A feature drop that slows phones down and locks some users out entirely cuts at the one thing Pixel loyalists have always counted on: software you can trust more than anyone else’s.
Google hasn’t said how widespread the lock-screen bug is, and the reports so far describe a subset of users rather than every Pixel on the update. But “subset” is cold comfort when the failure mode is losing access to your own device. Back up your phone, and sit this update out until Google says more.
Meanwhile in Mobiles: Apple’s own unlock fiasco — iPhone 18 Pro Face ID Bug Is Crashing and Rebooting Phones.
