Android 16 QPR1 tweaks unlock haptics, removes screen-off fingerprint unlock workaround on Pixel phones

Google’s new gift for Pixel users – the Android 16 QPR1 update – brings a ton of new improvements and fixes, including the Material 3 Expressive revamp. You can read all about it here. But it seems to have also brought some changes that have left some users feeling a bit annoyed.

The first bone of contention? The reworked unlock haptics that are hitting Pixel owners like a freight train. Some users on Reddit are up in arms about what they describe as intensely aggressive vibrations every time they unlock their phones. The feedback, which was previously subtle and pleasant, now feels like someone cranked the dial up to maximum intensity – whether you’re using fingerprint unlock, PIN, or pattern.

One frustrated user on a Pixel 8 described the sound as a “tinny/pink” noise that becomes unbearable within minutes. The worst part is that there’s no way to tone down the vibration intensity without killing all haptic feedback on your device, which means losing vibrations for calls, notifications, and alarms.

I’ll be honest though – I’m personally not bothered by this change at all. I hardly even noticed it to begin with, at least on a Pixel 7a. But clearly, some folks are finding it way too intense for their daily phone usage.

The second major gripe centers around a beloved workaround that’s now gone missing. Users who had previously enabled screen-off fingerprint unlock through an ADB command are discovering their trick no longer works. This feature allowed phones to detect fingerprints even when the display was completely dark – no need to tap the power button first.

The disappearance is particularly frustrating because Google had been testing official screen-off fingerprint unlock in earlier Android 16 betas. Users across different Pixel models, from the Pixel 7 Pro to the Pixel 9 Pro XL, are confirming the workaround has been completely removed. One user summed up the confusion perfectly: “I was pressing the power button to wake the screen but the whole time thinking ‘do I usually have to do this? Am I going mad?'”

Users seem to think that Google removed the feature due to battery drain concerns during beta testing, as the sensors need to stay more active to detect fingerprints on a dark screen. While the change might make sense from a power management perspective, it’s definitely a step backward for user convenience.

Android is all about options, so the least Google could have done was give us the option to choose for ourselves. I mean, even my “budget” Infinix GT 20 Pro offers the same functionality. So yes, Google has no excuse here.

For now, affected users are stuck waiting to see if Google addresses these concerns in future updates, or if they’ll need to adjust their habits around these new realities of Android 16 QPR1.