Google has a fix upcoming for Pixel 7 and other devices rebooting after lockscreen crash

Pixel phone owners dealing with frustrating random reboots might soon get some relief. Reports have surfaced over the past few weeks detailing an issue where devices, particularly the Pixel 7 series, crash and restart unexpectedly, often when waking the phone or interacting with the lockscreen.

The problem seems to have gained prominence following recent software updates, including the March 2025 security patch for some users and Android 16 beta builds for others. Affected users describe the screen turning black or flickering when they press the power button to wake the device, followed by a sudden reboot moments later. For many, this turned their phones into unreliable gadgets, making simple tasks difficult.

One user (User 14228079728973044940) even shared a video highlighting the issue. Check it out below:

On Google’s community forums, users shared their experiences and frustrations. User 2422766428037584405, who initially reported the issue on a Pixel 7 after the March update, found a temporary workaround by enabling the “Always show time and info” setting, otherwise known as the Always-On Display (AOD). However, this wasn’t a universal fix, and it came with drawbacks, like causing reboots during calls when the proximity sensor turned the screen off. Other users on Google’s Issue Tracker noted the opposite, finding that disabling AOD stopped the crashes.

The situation left many users scrambling for solutions, trying safe mode, repair mode, and even factory resets, which unfortunately seemed to worsen the problem for some, occasionally leading to bootloops or bricked devices. One user, ChrisNI, expressed the sentiment felt by many, stating, “My phone is becoming borderline unusable with the constant reboots.” The issue wasn’t isolated to just the Pixel 7, with reports also mentioning Pixel 6a, 6 Pro, 7 Pro, and even Pixel 9 Pro devices running beta software.

Now, there’s positive news. A comment from a Google employee on the official Issue Tracker page dedicated to this problem confirms the company is aware of the situation. More importantly, the comment, posted on April 2, 2025, states, “We have a fix rolling out in an upcoming release.”

While there’s no specific ETA mentioned, I think it’s fair to assume that the upcoming April update should address the problem. That said, if you’re facing the same bug, then let me know if it affects you on the Android 16 beta or the stable Android 15 channel.