I'm having this issue too. It seems to randomly occur. I seem to have better luck fixing this temporarily by shutting it down instead of rebooting it but it is completely unpredictable. Pixel 9 as well.
Workaround for Android 15 QPR2 fingerprint firmware glitch on Pixel 9
VAULT It only appears to impact people on the non-Pro Pixel 9 and doesn't impact everyone. It is not GrapheneOS specific.
https://www.androidpolice.com/google-march-update-fingerprint-problems-pixel-users/
- Edited
GrapheneOS FWIW, I've been unable to fix the issue permanently. Every so often it goes away when I boot the phone back up and remains fixed until the next reboot, but I haven't been able to have it go away completely.
Gratify4840 Same here... returns on next startup...
Pixel 8 fingerprint can be used to unlock screen. The fingerprint for apps in personal profile need to be setup again. In the work profile its not possible to set up the fingerprint unlock for apps. I always recieve an error.
After many many times of reboots, sadly my fingerprint isn't back yet. Seems like i hit the jackpot.
tavianator
I ran these commands in fastboot mode and get following logs on both of them:
FAILED (remote: 'Unable to do OEM command Status(-8, EX_SERVICE_SPECIFIC): '1: Error Unknown OEM command'')
My fingerprint failed to but after rebooting many times (stopped counting on 16 times) it worked again, but the last reboot after it worked again my phone rebooted itself while I wanted to unlock my SIM.
Pixel 8 Graphene OS 2025030900
So far lock screen and personal profile work fine. Apps installed in work profile don't work, though they'll prompt for fingerprints, either nothing happens, or they give an error.
domnru Huh, that's strange. Hate to ask this but are you sure you spelled the command the same way I did? Thanks for trying it anyway!
lemmy June012006 That's a different upstream issue from this.
- Edited
Could my post (https://discuss.grapheneos.org/d/20779-keystore-problems-in-the-business-profile-of-gos) be related to this issue?
thegustavo Not likely, since this issue only affects Pixel 9s
- Edited
tavianator Did it again by copying the command, same result.
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
here_some_id device
$ adb reboot fastboot
$ fastboot oem udfps status
FAILED (remote: 'Unable to do OEM command Status(-8, EX_SERVICE_SPECIFIC): '1: Error Unknown OEM command'')
fastboot: error: Command failed
$ fastboot oem udfps get-cal-url
FAILED (remote: 'Unable to do OEM command Status(-8, EX_SERVICE_SPECIFIC): '1: Error Unknown OEM command'')
fastboot: error: Command failed
$ fastboot --version
fastboot version 35.0.2-android-tools
Installed as /usr/bin/fastboot
$ adb --version
Android Debug Bridge version 1.0.41
Version 35.0.2-android-tools
Installed as /usr/bin/adb
Running on Linux 6.13.6-hardened1-1-hardened (x86_64)
Meta:
Arch Linux fastboot version 35.0.2-android-tools
Bootloader version: ripcurrentpro-15.2-12817298
My fingerprint worked, after rebooting again it doesn't anymore.
The universally fix is not rebooting x amount of times.
I got a pixel 9. Shutdown and/or restarted about 7-8 times and then it worked. I had to go into settings to re-activate the fingerprint unlock. good luck.
- Edited
tavianator Here you can see a reddit user had the same problem using an Pixel 8.
thegustavo Maybe this has something to do with it. In this thread there is another Pixel 8 user.
Would love to see the output of
$adb logcat | grep -i -E "fingerprint|fpc"
while the error happens
Same here
So I lost the fingerprint reader after the update and after a dozen restarts I got it back.
Well, I lost it again two more times since then so I booted into recovery mode both times and I rebooted the system from the recovery menu and both times the fingerprint reader was active again in just one try.
Sooo, someone else give it a try and post if it works as well.
PS: If you don't know how to get into recovery mode Google it don't ask here :)
.
Recently I noticed a similar effect on my P9, could it be related as well? (https://discuss.grapheneos.org/d/20805-blackscreen-without-fiingerprint-option-gets-triggered-on-p9)
jimmycinla Booting from recovery mode made fingerprint reader active again for me as well.