- Some Pixel owners are reporting Android 16 lock-screen issues
- They say the screen can be laggy and unresponsive
- So far, Google hasn’t issued any official advice about the issue
The official Android 16 rollout got underway last month, with the best Pixel phones first in line for the update – but it appears that the software is causing lock-screen issues for a significant number of Pixel owners.
A variety of problems have been reported, as per 9to5Google. These include the lock screen not waking up when tapped, and not responding to a press of the power button, as well as fingerprint ID issues and extreme variations in brightness.
“I’ve been experiencing a significant and frustrating delay when trying to wake my phone,” writes one user on the Pixel Phone Help forums. “I often have to press multiple times before the phone finally reacts. This issue is occurring one to two times daily.”
For that particular user, there was a fix: booting into Safe Mode (see here) and then rebooting normally. If you’re experiencing something similar then that fix is worth a try – but even with a possible workaround available, it’s not something Google will be pleased to see.
Trouble waking up
“Has anyone else noticed issues where the screen does not wake up when tapping the screen or trying to use lift to wake?” asks another user on Reddit. “Also pressing the power button has a long delay waking up the screen.”
That user reports that their issues are with a Pixel 9 Pro XL, and that the problem has been logged with Google. If you are having difficulties with Android 16, the Google Help portal is a good starting point for getting some assistance.
As yet, Google hasn’t said anything officially about the issues – perhaps because the bugs being reported are so numerous and so varied. The types of problems being mentioned are the sort that could well be fixed with a future Android 16 software update.
It’s tricky to assess how widespread these issues are right now – they’re definitely affecting some Pixel users, but not all Pixel users. Even if only a small number of people are hit though, it’s disappointing that we’re still seeing bugs like this after several months of beta testing.
Read the full article here
