This release is only on Alpha channel right now.
You're probably not on this release
Your issue is probably better served by this thread:
https://discuss.grapheneos.org/d/20636-workaround-for-android-15-qpr2-fingerprint-firmware-glitch-on-pixel-9-non-pro/
t1c yes I could possibly write bash scripts while waiting for a bus or on a beach.. I really doubt i will ever do this.. too small.
Daniel89 It's https://discuss.grapheneos.org/d/20636-workaround-for-android-15-qpr2-fingerprint-firmware-glitch-on-pixel-9-non-pro, not something related to this release specifically.
GrapheneOS Fingerprint is gone AFTER UPGRADING from 2025030900 to 2025031300.
The "Turn off Bluetooth automatically" feature is still broken for me in this release as I described here:
https://discuss.grapheneos.org/d/20685-turn-off-bluetooth-automatically-feature-stopped-working
Daniel89 It's unrelated to the update. It's the issue described in https://discuss.grapheneos.org/d/20636-workaround-for-android-15-qpr2-fingerprint-firmware-glitch-on-pixel-9-non-pro which occurs after reboots.
GrapheneOS We've fixed this and will be starting the official builds for a new release soon.
GrapheneOS installed 2025030900 and fingerprint is working again.
GrapheneOS does "GUI support" mean Xorg support? If so...holy fuck Android, THANK YOU
Daniel89 It's unrelated to these updates. Read https://discuss.grapheneos.org/d/20636-workaround-for-android-15-qpr2-fingerprint-firmware-glitch-on-pixel-9-non-pro. You can find many news stories about the Pixel 9 fingerprint issues with Android 15 QPR2 if you look for it. It's near entirely specific to the non-Pro Pixel 9 and is not because of GrapheneOS or updates. For some users, it sometimes fails to work at boot and is resolved by rebooting one or more times. Powering off instead of rebooting can also work better.
Updated, still confused on how GUI or audio on the terminal app is supposed to work. Speaker-test and startx still fail
raccoondad Maybe its Wayland with wireplumber? ;)
raccoondad source enable_display and run chromium --ozone-platform=wayland to use the basic Weston setup they have there. If you want to use GPU acceleration, the last 2 lines of enable_display need to be commented out and you need to create linux/virglrenderer as a file in the profile you're using the Terminal app to tell it to enable VirGL which it will show as a toast after being force stopped and launched again. You can also use your own GUI setup but that's how to use the one they have set up with working VirGL support.
