[Updated] June update triggers screen wake-up lag on Pixel 2 devices
Update (July 26):
Google says Android P will finally fix the issue.
The problem was caused as a side effect of a fix introduced in June SMR in order to fix cases of bright flashes before entering Always On Display for displays on certain (isolated) devices (this was actually pointed out in comment #44 of public bug). The fix will be reverted in July SMR to address the slow unlock regression. A proper fix for the original issue which won’t cause slow unlock side effect will be available on P release.
Update (June 12):
Google has officially acknowledged the bug.
Update (June 7): As we already pointed out in our story, the change seems to be intentional.
It's funny to see all the blogs complaining about the Pixel 2 XL wake times. It's not a "bug" or side effect, it is an intentional change made by Google, as shown by the commit message.https://t.co/7M4uH1m5ZM
Blame LG's panel design :^)
— Nathan Chancellor (@nathanchance) June 5, 2018
Original story follows:
Not even a few hours after the June 2018 Android security update started rolling, Pixel 2 users started reporting a new issue – wake-up screen lags on unlocking the device.
— Akshay Agarwal (@akshayAgarw) June 5, 2018
Going by reports pouring on different help forums, on unlocking (or waking up) the screen either through the fingerprint scanner or the power button, there’s a lag of about 2-3 seconds. The problem can be clearly seen with AOD disabled, but it can also be reproduced with AOD enabled (through the following steps):
Go to the Home screen, then turn the screen off using the power button and immediately use the Fingerprint sensor to unlock the device (attempt should happen before AOD activate). You will note that it takes several seconds to unlock.
There already are two separate threads on Reddit discussing the screen wake-up lag problem:
Also a separate bug report has been submitted by the affected users on the company’s official issue tracking website. It’s worth mentioning that one of the users pointed out that the problem could be due to this code commit.
Though the problem is being reported by a limited number of users (as the June update just got live a few hours back and many are still to install it), we hope Google looks into the matter before the number of complaints blows up. Rest assured, we are keeping an active tab on the matter, and will update as and when any further development takes place.
Stay connected with us on Twitter (@PiunikaWeb) to hear about all related developments as and when they occur