Google's September Pixel Drop reached Pixel 6 through Pixel 10 devices starting September 15, 2026, rolling out in waves over the following week. It was a routine security and bug-fix update — no new features, just fixes for things like Bluetooth failing to turn on, camera crashes, and choppy frame rates during gaming. Buried in that same list of fixes, per Google's own release notes, was a repair for lock screen text getting cut off. Ten days later, a different lock screen problem showed up in its place: some of the phones that installed the update can no longer unlock at all.
What some Pixel owners are seeing instead
Reports collected on Reddit and Google's own support forums describe two versions of the same failure. On a pattern lock, the line being drawn vanishes after the second dot, breaking the gesture before it registers. On a PIN, some owners say the phone accepts input before they've finished typing, locking them out on a code that was never actually complete. Android Authority tracked reports from Pixel 10 Pro XL and Pixel 8a owners as of September 25; other outlets added the Pixel 8 Pro to that list. It isn't universal — one Pixel 6a owner on the same update reported no issue at all — and nobody outside Google has said what share of updated phones are affected, or why some models show it and others don't.
The failure reported so far is specific to pattern and PIN entry. Nobody has reported fingerprint or face unlock breaking alongside it, so if your phone has a biometric method set up as a backup, it should keep working independently of whatever is going wrong with typed and drawn input — though nobody outside Google has said why one unlock method would be affected and the others wouldn't.
Google's response so far
As of September 25, Google had not issued a public statement or shipped an emergency patch. What it has done is reach out directly to people posting about the bug in community threads and ask for diagnostic logs — the standard first step before a fix ships, not a fix by itself. There's no confirmed timeline yet, and no public confirmation of what in the September build is actually causing it. You can check which security patch your phone is running under Settings, System, System update; if you're already on the September build and haven't hit the symptom, there's nothing extra to do beyond the caution worth applying to any update.
What to do if your Pixel does this
If you're currently locked out, a hard restart — holding power and volume down together — has worked for some owners without erasing anything. Deliberately triggering the "too many attempts" lockout timer, by entering a wrong code repeatedly until the phone forces a timed pause, has also worked as an unintended workaround for a few people. A factory reset restores access too, but it wipes the phone, so treat it as the last option rather than the first, and only after the other two have failed. If you haven't been locked out, there's nothing to install yet — whatever patch Google ships will arrive as an ordinary software update, the same way the buggy one did, and there's no separate app or setting that fixes this ahead of that.
This is the second launch-month software regression from a major phone maker in as many weeks. Apple confirmed its own reboot bug on the iPhone 18 Pro just days earlier, with a fix scheduled for the week of September 28. Neither case says anything about the hardware underneath — both are bugs introduced by an update meant to fix other things, which is the ordinary risk of shipping monthly patches to millions of phones at once. It also means neither company's track record this month is a reason to delay installing the next patch when it arrives; the fix for this kind of bug comes the same way the bug did.
Samsung's update month wasn't any smoother: One UI 9's rollout schedule moved twice in a week before the software itself reached phones ahead of any date Samsung had actually published. None of these problems fix each other, but the pattern holds across three companies at once — check what your phone is actually running before trusting what a company said it would be running, because this month, an update log has told the truth more often than a press release.
Last updated September 26, 2026