Is anyone else having issues with the camera crashing with this update? I'm getting an error message saying "android.hardware.camera.provider@2.7-service-google has crashed" running on P7Pro with Build 2025012700
Edit:
I have some crash logs but am not sure where to send them.

    Rasta9 I restarted and it's working now, but do still have a log text I copied that I can share somewhere if needed.

        Sandboxed Google Play compatibility layer: add per-app Play Integrity menu in the per-app Settings configuration that's shown after an app uses the Play Integrity API
        Sandboxed Google Play compatibility layer: add per-app toggle for blocking using the Play Integrity API via the per-app Play Integrity menu as a workaround for apps which ban devices based on it but don't require providing it to their service yet
        Sandboxed Google Play compatibility layer: add shortcut to the per-app Play Integrity API menu for contacting the app developer by leaving a review through the Play Store page

        Where exactly can I find these controls?

        Sandboxed Google Play compatibility layer: allow blocking the Sandboxed Google Play is running notification

        No effect.

          IO app (italian gov ID) doesn't trig the "app is using Google Play Integrity API" notification when trying to access the features protected under that API. It still fails in the app, says: "your device is not supported". Also in the settings of IO there is not the new section like in Revolut for the new play integrity API per-app settings. The OS might be failing in catching when the app IO is attempting to use the play integrity API (or the app might be using something else to ban GrapheneOS, even though they clearly state they use play integrity API).

          Also something I fail to understand is why Revolut triggers the new play integrity API notification and the per-app settings even though they are using some other 3rd party SDK and not the integrity API?

            dc32f0cfe84def651e0e
            When an app uses Play integrity API, a gmscompat notification dialog comes up with 'More information' and 'Hide notification' options. Tapping 'More information' then brings you to the menue with the toggable options and app developer contact.

              Rasta9 for me secure camera crashes when using selfie mode, the OS reboot and then I'm found with a kernel crash notification, but this was happening already in previous update for me.

                  KeePassDX suddenly can't open database because not enough memory.

                    I'm experiencing what seems to be a regression either in this build or the previous, alpha-only build which I've not used (I'm on stable channel): Do Not Disturb schedules have no effect. My phone didn't enter DND when it should have, and rebooting the phone when a schedule is supposed to be in effect doesn't turn on DND either whereas in previous builds even if I manually disable DND and reboot when there's a schedule set it automatically turns DND back on and set on the schedule (so it'd turn off at the end of the schedule and not after a set time from reboot or permanently). Can anyone else confirm?

                      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-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.

                              GrapheneOS

                              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.

                                        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 😍