- Some pixeleers report Android 16 Lock Screen Questions
- They say the screen may be delayed and not responding
- So far, Google has not issued any official advice on the question
The official Android 16-Escape started last month with the best Pixel phones first in line for the update-but it seems that the software is causing problems with lock screen for a significant number of pixeleers.
A number of problems have been reported according to 9to5Google. These include the lock screen that does not wake up when tapped, and do not respond to a pressure on the power button, as well as problems with fingerprints id and extreme variations in brightness.
“I have experienced a significant and frustrating delay when I try to wake my phone,” writes a user at Pixel phone relief forums. “I often have to press several times before the phone finally responds. This problem occurs once or twice a day.”
For the specific user, there was a solution: Start -up in safe mode (see here) and then reboot normally. If you experience something similar, the correction is worth trying – but even with a possible solution available, it is not something Google will be happy to see.
Trouble waking up
“Have anyone else noticed problems where the screen doesn’t wake up when you press the screen or try to use lift to wake up?” asks another user at Reddit. “Ticking the on / off button has a long delay that wakes up on the screen.”
This user reports that their problems are with a Pixel 9 Pro XL and that the problem is logged with Google. If you have difficulties with Android 16, Google Help Portal is a good starting point for help.
Yet, Google has not said anything officially about the problems – perhaps because the errors reported are so many and so varied. The types of problems mentioned are the kind that could be corrected with a future Android 16 Software Update.
It is difficult to assess how widespread these problems are right now – they certainly affect some pixel users, but not all pixel users. Although only a small number of people are affected, it is disappointing that we still see bugs like this after several months of beta test.
