On my side I just rebooted the pixel 9 and issue happened a second time, the phone lost the fingerprint.
It looks like it can indeed randomly appear after reboot/restart.
Workaround for Android 15 QPR2 fingerprint firmware glitch on Pixel 9 (non-Pro)
Franco Has your fingerprint functionality returned since? I have attempted powering off/on to see if it returns like before and still no fingerprint reader.
I've rebooted more than ten times, including leaving it off for 20 minutes. No fix for my Pixel 9.
Franco ah, okay. Thank you for the reply. I will carry on trying. I will update the thread if I get it working again.
Mine is also gone after updating to the latest beta (Pixel 9). Has not (yet) returned following multiple power cycles and reboots.
Fingerprint functionality is back, after what must have been 25+ powering off and back on throughout today. I am not too sure what triggers a successful reboot for the fingerprint reader to work on next boot... So it looks like the fix does not persist across sessions, and the advice to power off once for it to return does not work (at least in my case).
- Edited
Pixel 9 here, behaving the same as in other reports - fingerprint reader gone after update, several reboots later it starts to work. I captured logcat output of the failed and working states, and this appears to be the point where things fall off the cliff:
Not working version:
D ActivityManagerTiming: OnBootPhase_1000_com.android.server.biometrics.sensors.fingerprint.FingerprintService
D FingerprintProvider/default: Adding AIDL configs
D BiometricService: No fingerprint authenticators registered.
W FingerprintService: Null provider for getEnrolledFingerprintsDeprecated, caller: android
D BiometricDeferredQueue: Fingerprint addPendingLockoutResetForUser: 0
W PackageManager: Skipping preparing app data for com.android.hardware.biometrics.fingerprint.virtual
D SystemServerTimingAsync: ssm.onUnlockingUser-0_com.android.server.biometrics.sensors.fingerprint.FingerprintService
D SystemServerTimingAsync: ssm.onUnlockedUser-0_com.android.server.biometrics.sensors.fingerprint.FingerprintServiceWorking version:
D ActivityManagerTiming: OnBootPhase_1000_com.android.server.biometrics.sensors.fingerprint.FingerprintService
D FingerprintProvider/default: Adding AIDL configs
D FingerprintProvider/default: Added: com.android.server.biometrics.sensors.fingerprint.aidl.Sensor@9afee62
D BiometricScheduler: [Added] {[0] com.android.server.biometrics.sensors.fingerprint.aidl.FingerprintInternalCleanupClient, proto=7, owner=android, cookie=0, requestId=-1, userId=0}, new queue size: 1
D BiometricScheduler: [Starting User] {[1] com.android.server.biometrics.sensors.fingerprint.aidl.FingerprintStartUserClient, proto=17, owner=android, cookie=0, requestId=-1, userId=0}
D FingerprintProvider/default: Daemon was null, reconnecting
D Sensor : New fingerprint session created for user: 0 with hal version: 3Not sure if it helps, but maybe it will provide some clue to developers.
Just after writing the above post, I disabled developer options and restarted. Fingerprint reader didn't work after reboot, requiring a few more (3 to be exact) to start working again. It looks like perhaps it is some race condition somewhere?
Pixel 9 Build 2025030800
The option was disabled for me as well. It was even gone in the Device unlock settings, so I couldn't enable it.
After shutting down the device, and waiting about 2 minutes (the time it took to read this thread) I turned the device back on and it worked again.
Imo, I think the issue may be more common.
- Edited
I have no problems with the fingerprint scanner on 2025030900 using my Pixel 6a, Pixel 7 and Pixel Tablet, everything seems okay with my 6th and 7th generation Pixels. (I don't have the other generations to test)
- Edited
Had the same issue on my Pixel 9, I just had to power off the device and waited for about five minutes until I turned the device back on, simple restarts didn't help. Now it's back and the option for fingerprint security reappeared in the settings menu
Pixel 9 Build: 2025030900
GrapheneOS My apple music app is somehow fucking with my fingerprint reader.... Sometimes it just disappears after some time having apple music open other times it won't do that. It drives me crazy... Running the latest GOS Version on a P8 Pro.
The main issue appears to be specific to the Pixel 9. It doesn't occur on the Pixel 9 Pro, Pixel 9 Pro XL or Pixel 9 Pro Fold.
GrapheneOS changed the title to Workaround for Android 15 QPR2 fingerprint firmware glitch on Pixel 9 (non-Pro) .
@GrapheneOS , you are mentioning that it is "a glitch occurring for certain Pixel 9 (non-Pro) users resulting in the fingerprint sensor not properly resetting itself after being updated"
If this issue persists for an extended period, do you think a complete reinstallation of GrapheneOS would resolve it permanently? The rationale is that a fresh installation would ensure the fingerprint sensor receives the correct firmware version from the start.
Currently, the issue is more of an annoyance than a major problem for me, but I'm asking in case it continues for weeks.
Franco if it helps, I have tried this and still had the problem. So I would hold fire on reinstalling GOS as it does not seem to fix the issue.
My Pixel 9 is affected by this and I can't seem to get the sensor to come back. I am getting this error from fastboot oem udfps status:
$ fastboot oem udfps status
(bootloader) invalid sentinel 0x0
FAILED (remote: 'failed to print status -7')
fastboot: error: Command failedThe calibration image URL is this, which gives a 404 error.
$ fastboot oem udfps get-cal-url
(bootloader) https://storage.googleapis.com/hardware-mfg-data-ext-sacal/d9010017100086.signed.cal
OKAY [ 0.001s]
Finished. Total time: 0.001sAny chance someone with a working Pixel 9 fingerprint scanner can try those commands and paste their output?
NO FINGERPRINT option...
Just flashed a new P9 and it installed build 2025030900 from the website installer... and on first boot there was NO option to install a F. P. unlock... and in the settings it simply isn't there... I wonder if this is effecting more than first thought...
VAULT
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.
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.