Since the update, GrapheneOS no longer recognizes the fingerprint sensor. I can only unlock the pixel with a password. Does this have to do with the bug in Android ASOP? (Pixel 9)
GrapheneOS version 2025030800 released
Finger print reader not working after powering off several times
- Edited
This update has caused bluetooth to repeatedly crash.
Log:
type: crash
osVersion: google/husky/husky:15/BP1A.250305.019/2025030800:user/release-keys
flags: dev options enabled
package: com.android.bluetooth:35, targetSdk 35
sharedUid: android.uid.bluetooth
process: com.android.bluetooth
processUptime: 285 + 493 ms
java.lang.IllegalArgumentException: Invalid Empty name
at android.os.Parcel.createExceptionOrNull(Parcel.java:3274)
at android.os.Parcel.createException(Parcel.java:3254)
at android.os.Parcel.readException(Parcel.java:3230)
at android.os.Parcel.readException(Parcel.java:3172)
at android.bluetooth.IBluetoothCallback$Stub$Proxy.onAdapterNameChange(IBluetoothCallback.java:177)
at com.android.bluetooth.btservice.AdapterService.updateAdapterNameInternal(AdapterService.java:1167)
at com.android.bluetooth.btservice.AdapterService.updateAdapterName(AdapterService.java:1156)
at com.android.bluetooth.btservice.AdapterProperties.adapterPropertyChangedCallbackInternal(AdapterProperties.java:840)
at com.android.bluetooth.btservice.AdapterProperties.lambda$adapterPropertyChangedCallback$0(AdapterProperties.java:816)
at com.android.bluetooth.btservice.AdapterProperties.$r8$lambda$mCFKluZ_CoKIr7RYSBs6MKnrcRg(AdapterProperties.java:0)
at com.android.bluetooth.btservice.AdapterProperties$$ExternalSyntheticLambda0.run(R8$$SyntheticClass:0)
at android.os.Handler.handleCallback(Handler.java:991)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loopOnce(Looper.java:232)
at android.os.Looper.loop(Looper.java:317)
at android.app.ActivityThread.main(ActivityThread.java:8973)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591)
at com.android.internal.os.ExecInit.main(ExecInit.java:50)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:369)
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.bluetooth.BluetoothManagerService$1.onAdapterNameChange(BluetoothManagerService.java:232)
at android.bluetooth.IBluetoothCallback$Stub.onTransact(IBluetoothCallback.java:118)
at android.os.Binder.execTransactInternal(Binder.java:1451)
at android.os.Binder.execTransact(Binder.java:1390)
co77 Try fully powering off the device (not a reboot) and powering it back on. If it still happens afterwards, we can investigate further. What do you have set as your device's host name in the Settings app? Did you set it to an empty value?
I did have my device name as just a space but I changed it after the crashes started occuring. However, I've powered my device on and off 3 times now and the issue still occurs.
Since the update, my device shows a red "You device is corrupt" warning. I didn't really understand what happened, I just rebooted my phone after the update. (Pixel 7a)
- Edited
co77 Try resetting Bluetooth & Wi-Fi settings via Settings > System > Reset. It's unfortunately not split up between the two so you have to clear both and add back your Wi-Fi networks. You could try using ADB to clear only Bluetooth data but we don't have time to figure out how to do that right now to give you a command. Using pm clear com.android.bluetooth may work but may not be enough.
lumzl That sounds like SSD data corruption. It should automatically roll back if it fails to boot several times regardless. Did it roll back and boot up the old version again?
- Edited
GrapheneOS No, it just showed "the device can't be trusted" and booted fine, but the integrity IDs are different, that's my main problem. here: https://imgur.com/a/oTm88JU . Sorry for such blurry photo, taken on an old phone.
lumzl That's very strange and quite concerning. It's hard to understand how it could boot if that's the case. Try booting into recovery and sideloading the latest update again. See https://grapheneos.org/usage#updates-sideloading for instructions. You can download it from the releases page. You could try sideloading a 2nd time if the 1st time doesn't work.
Thanks, its working again after clearing data using adb.
- Edited
GrapheneOS No, that didn't work either. It's really weird. I have sideloaded the system update twice, nothing changed(integrity IDs too). what can I try, factory reset? Thanks for your help!
- Edited
de0u it succeeds, but still outputs that image: https://imgur.com/a/oTm88JU . I tried different cables, networks, etc. Still nothing.
lumzl It's supposed to show that and the hash appears to match what it's supposed to be. See https://grapheneos.org/install/web#verified-boot-key-hash.
- Edited
Dear team and users,
for me the haptics on this version are really f'd up. Pixel 8 has one of the best vibration motor I ever used, and the haptics were perfect. Now, agree this update, I would describe them very "springy", with reverb, and unpleasant. Have you made some modifications or is it something that Google screwed?
Thank you.
Edit: I searched the forum, and it may be Google's fault: https://arstechnica.com/google/2025/03/bad-vibes-google-may-have-screwed-up-haptics-in-the-new-pixel-drop-update/
- Edited
de0u You're absolutely right. I stupidly thought that these two lines should be the same, even though there is only one, lol.
This is probably a hardware issue, and it has nothing to do with GrapheneOS. My device just died for no reason. I'll try flashing factory image anyway. Thanks for the help!
Here it is: https://imgur.com/a/eSq4GvM