Rasta9 Rasta9 Please provide the crash log here or it to logs@grapheneos.org via email. It's likely an upstream bug we can't do anything about but it would helpful to take a look at it.
GrapheneOS version 2025012700 released
grapheneos-enthusiast Please provide the crash log.
grapheneos-enthusiast It's likely doing something else to detect GrapheneOS before it uses the Play Integrity API. Apps can do their own checks in addition to that. As far as we know, it does use the Play Integrity API but also other checks. We could work around the other checks but it wouldn't achieve anything for this app. Working around the other checks done by this app might get something else working but it's not really a good use of our limited resources.
- Edited
type: crash
osVersion: google/cheetah/cheetah:15/AP4A.250105.002/2025012700:user/release-keys
uid: 1000 (u:r:hal_camera_default:s0)
cmdline: /apex/com.google.pixel.camera.hal/bin/hw/android.hardware.camera.provider@2.7-service-google
processUptime: 0s
abortMessage: GraphRunner watchdog fired, Connectors with unsignaled frames: [shutter_notification->ae_shutter_notification], [shutter_notification->flicker_shutter_notification], [shutter_notification->hardware_pd_fullframe_shutter], [shutter_notification->hardware_pd_window_shutter], [shutter_notification->metadata2], [shutter_notification->previous_shutter_notification], [shutter_notification->shutter], [shutter_notification->shutter_notification], [shutter_notification->shutter_notification_for_deadlines], [shutter_notification->shutter_notification_for_vsync_updating], [shutter_notification->shutter_notification_process], [shutter_notification->shutter_notification_query], [shutter_notification->software_pd_fullframe_shutter], [shutter_notification->software_pd_window_shutter]; Running input groups: cam2_af:algorithm_group, cam2_sensor:group1
signal: 6 (SIGABRT), code -1 (SI_QUEUE)
threadName: WatchDog
backtrace:
/apex/com.android.runtime/lib64/bionic/libc.so (abort+156, pc 638fc)
/system/lib64/liblog.so (__android_log_default_aborter+12, pc 96dc)
/apex/com.google.pixel.camera.hal/lib64/libbase.so (android::base::LogMessage::~LogMessage()+520, pc 13a28)
/apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc e72f94)
/apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 537b18)
/apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 536520)
/apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 5363f0)
/apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+132, pc 75d34)
/apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc 66890)Rasta9 If it didn't start working again without a reboot, then this looks like a camera driver/firmware/hardware bug unrelated to GrapheneOS. If it didn't start working again without a reboot, chances are high that it's a firmware/hardware bug, although it could still be a driver bug where the driver caused the firmware/hardware to end up in a bad state.
GrapheneOS It did fix itself on a restart. The phone had just updated and restarted all apps to finalize the update when I tried to use it and encountered the issue.
Just received the update and everything works fine on my Picel 6.
Hello this update broke data in my main profile.
https://discuss.grapheneos.org/d/19523-vpn-doesnt-connect-over-data-after-uodate-to-20250127
gogomouse That's not version 2025012700 but rather a legacy extended support release based on a much older release of GrapheneOS.
Watermelon I'm no longer experiencing this issue. Probably was temporary.
GrapheneOS sorry I was wrong, the bill for T-Mobile didn't get paid. It was just a coincidence that it happened after the new build.
Pixel 8: working all well, thank you! I was even able to get an app working again by blocking Play Integrity API access 😍
fid02 I don't want to make it public forever. Since I am not aware of a DM feature here: Access the link with a link to Google Play Store but note that this link is only valid for 24 hours: https://kpaste.infomaniak.com/J91Ay69y-tEGD0m83yXVvwsQTc192ojM#7ijtb3tJazohAxQeLebAZb6ccMGYsu57RwwMFW13Dszd
fid02 All good :-)
KitsuneNoBaka No problem with KeepassDX here (P6a, 2nd user, without Google play), small database with keyfile and biometric unlock.
AgentM yes, I've tried to do this again and nothing wrong happens. Dunno why it was corrupted this one time.
Just purchased a pixel 8 and noticing that the vanadium password manager isn't saving any passwords. Anyone else having this issue?
Chasy81 Which mode do you have it set too? There's one mode for the default password manager and another mode for other password managers.