Hey today I got my phone out of my pocket, and it was rebooted and after unlocking it said it had a kernel crash and gave me a crash report. Does anyone else had a kernel problem with the new update? And now is my question a crash could be a hint for some exploit, but the crash report is long and complicated, and I don't understand much there so I really can't analyze it. I would love to post the crash report here, but there a probably much info about my phone which I don't want to publicly post here, but it's too long to censor it all, and I probably wouldn't even find everything I should censor. So now my question: do many people got this crash, and it's just a bug or is there something I should look for in the crash report which could be a hint for an exploit. I Never had a kernel crash, that's my I'm a bit scared/confused.

Thank you all <3

    5 days later

    I got the same report after updating today. Following

    Mine too. I'm running stable version on Pixel 7. I restarted my phone a few times and it wouldn't stop coming up. It had the message Kernel corrupted, with a big log. I have just tried again restarting a few times and it's not coming up now... didn't save the log.

    After updating to latest stable release Pixel 7. Message saying Kerenel corrupted with log file. Restarted a few times still coming up. Tried again a couple of hours later and now it's not coming up. I didn't save the log.

    I just updated my pixel 7 and it went to restart and said no OS could be found I restarted it a few times it and finally came back online and I got an update failed. Gonna wait to backup my stuff before I update again.

    6 days later

    Same thing just happened to me today on my pixel 5, prior to crashing I noticed the phone refused to charge when plugged in, seems to be working again now.

      GrapheneOS recently added user-facing crash reporting. It's enabled by default for certain kinds of crashes. It's currently a bit too noisy and detects things like forced reboots via holding power as kernel crashes, etc. Android doesn't report these kinds of things to users. We decided it made sense to do that because we can't have automatic crash reporting like Play services does with these logs for privacy reasons. If it leads to people being as you say scared/confused, we'll likely have to remove it and consider another way to get this information in a way that respects privacy like having users providing it from a user-facing report.

        OnlyQuickQuestions "my question a crash could be a hint for some exploit"

        A crash is a crash, while it could in theory be possible, I wouldn't worry to much. Kernel panics happen from time to time, everything from hardware failure to just a very rare bug.

        However, never had one happen on a Pixel device, only my desktops kernel...

        Paracelsus
        i dont know if it's updated or not but i watched
        my turn itself on watched it do so on the coffe table but there could be higher forces at work here who knows. and yesterday i'm listening to podcasts
        on antennae pod and it would shut off every minute and i'd have to turn it back on..... and i've noticed on my 6a i've had to shut off the audio permission on the window screen.... numerous times i thin the 6a is bugged, i have a 7a on the way gawd

        GrapheneOS I like the idea of giving the user the crash report but maybe, a massage like yours as a disclaimer would be good. Because for me and the other in this thread here, was it probably the first time seeing a message like this, so a little explanation before the report would be nice. But if you find another good way, go for it.