The Pixel 6 has a fingerprint glitch that may not recognize your biometric lock if the phone has a dead battery

Google’s Pixel 6 has been one of the most anticipated smartphones in the Android ecosystem, but has been marred by a plethora of issues and issues since its launch. The latest one, which was reported by the founder of Android Police and APK Pure Artem Rusakovsky, concerns the fingerprint sensor on the smartphone. According to reports, if the Pixel 6 smartphone suddenly turns off, then the sensor not only cannot register new add-ons, but it may not even recognize already registered fingerprints on the device.

A reddit thread on the subject suggests that this may be the result of a recent security update that resulted in a glitch. A user report documenting the issue states: “The fingerprint scanner on my Pixel 6 pro was working fine until last night when my battery ran out. Plugging it in to charge and entering my pin code once, I noticed that the fingerprint scanner icon was no longer displayed on the screen. Now I have to enter a pin code every time I want to unlock the device.”

He further adds: “Going into settings, I noticed that the fingerprint profile is no longer there. Tried to set it up and it goes through fingerprint capture, but after it completes, the message appears: Enrollment not completed. Fingerprint registration does not work. Try again or use a different finger. Tried all the same. Tried my wife’s finger, same thing. I also installed the fingerprint calibration from Google.

This isn’t the first issue the Pixel 6 has had with its fingerprint sensor. According to reports, many users have complained that their Pixel 6 smartphones are too slow to recognize fingerprints. However, Google has since said that this is not a software glitch, but a hardware feature where the fingerprint algorithms have “enhanced security”- and as a result it takes longer to authenticate the biometrics before unlocking the phone.

Following the above Reddit post, many users complained about this issue. Google has not yet officially acknowledged this or provided a remedy, but given that this is clearly a software glitch, Google will likely fix it in the near future.