GrapheneOS version 2025050300 released

GrapheneOS

GrapheneOS version 2025050300 released:

https://grapheneos.org/releases#2025050300

See the linked release notes for a summary of the improvements over the previous release.

moonkidofdeauth

GrapheneOS this update seemed to break Android auto functionality, most likely due to the gms compat update if I had to guess. Android auto threw an illegal state exception/out of car life cycle error. What's the best course of action I should follow? All apps are up to date. The symptoms were Android auto repeatedly starting and crashing before basically giving up entirely. I did try uninstalling and reinstalling with no luck.

GraphiteOS

I'm not sure if it's related to this update, but could be. I think today my GrapheneOS tried to auto update itself, that's what it usually does. The phone got a little bit hot as well, that's also what normally happens. But after that my phone turned into a brick, the screen is black, and I can't boot, not into recovery even. It's just a brick now. Is this a known issue? Sorry I can't really provide any logs for diagnostics. We'll probably have to wait and see if more people have a similar issue.

It had enough battery, since I always charge it to 100% in the morning. Also, if I try to charge it now, nothing happens.

JustBeginnez

No problem with pixel 8a

Object_11

No problems with p9 fold. And seems battery drain is significant reduced.

GraphiteOS

I was able to fix the issue by holding down volume UP + power buttons, previously I was holding down the power DOWN button. So the wrong button. My phone is working fine now, the issue is related to the 2025042500 update, not this one.

aintonio77

GraphiteOS
I have the same problem and I just managed to revive my phone using the same button combination. Build number 2025042500

It is important for all of us to monitor how the devices behave in the future and inform the dev team and the community.

GrapheneOS

GraphiteOS It's very likely not related to the 2025042500 update. It's an upstream bug likely introduced in earlier the April monthly update or the quarterly Android 15 QPR2 update in March. We haven't narrowed down the cause.

manugraph

GraphiteOS this issue appeared for my P9 pro, too - but 3 months ago or so already. It seemed to work correctly, but the screen was all black after an update.
After a forced reboot it has not appeared since then again.

GraphiteOS

@aintonio77 There is apparently some kind of issue with Pixel 8 phones, and the display going black, so the phone is working, but the display is just black. Do you have Pixel 8 as well? I have Pixel 8.

whysofurious

GraphiteOS I had the same issue, phone was working, but the screen went black. In my case, this is what happened in case it's useful to someone else:

The phone autoupdated to 2025050300 and needed to reboot, however, the battery ran out before I could reboot. Plugging it to the power brick I could see the grapheneOS logo so I didn't worry and came back later. However, I was presented with a black screen and apparently to feedback from the phone (note that it was on DND night mode, so no vibration was expected).

I tried force-rebooting with a combination of power+volume up/down, but as soon as I was presented with the SIM pin, the screen faded to black before I could unlock it (no matter how fast I was), this happened at least 3 times.

What solved for me was to temporarily remove my sim, force-reboot the phone, unlock it, wait until it charged completely. I left it like that overnight (I wanted to sleep), and in the morning I plugged the sim back and was able to unlock that too. I also tried rebooting the device with the sim inside, and everything is working perfectly now.

If it's an upstream bug, it is really annoying, scared the hell out of me.

JoeAverage64

no issues with an P8 (here) neither with last nor previous update(s)

Thanks

P.S.
for P7a users and if unknown:
https://www.heise.de/en/news/Pixel-7a-Battery-problems-Google-offers-battery-replacement-or-goodwill-service-10361423.html

de0u

moonkidofdeauth Android auto threw an illegal state exception/out of car life cycle error. What's the best course of action I should follow?

It might well help to report the exact details of the error message (that's always better). Reporting version numbers is usually helpful too: GrapheneOS build number, Play version number, Android Auto version number. The make and model and year of the car could be useful.

GrapheneOS

moonkidofdeauth That's due to a connectivity issue, not something to do with the sandboxed Google Play compatibility layer.

Volen

Just my 2 cents: I have 2 P8 Pro devices and both suffered from this issue - the screen went black and the phone literally turned into a brick with no reaction on power button, connecting phone to charger / pc. I waited around an hour with no avail and was finally able to turn it on using either power up + power button or power down + power button. Made me sweat as I throught both phones died permanently.

aintonio77

Volen

My friend and I have absolutely the same problem. No crash report is generated, and sometimes it is very difficult and takes a long time to revive the phone. I would like to point out that his phone is only a few months old and everything was absolutely stable until he updated the device to release 2025042500. Since then, the mentioned problem, which matches your description, began to occur. I have a new phone, and the problem occurs on both the latest releases: 2025042500 and 2025050300.

Since no crash log is generated, I am asking if there is any other way we can determine what's happening and help?

GraphiteOS

I'm now updated to 2025050300, and it all went without issues. I think it's how GrapheneOS said, there is an upstream bug in Android itself, so not in GOS, but in Android itself. No one knows what causes it. I do wonder if it's possible to retrieve logs still, or are they deleted after reboot? Or maybe it's possible to get some logs while the screen turned black since it's still working at that point?

supertitan568

whysofurious
This is the solution. Thank you!!. I have the Google Pixel 8 and last night it auto updated too. This was the only thing that worked

J48fkze5fKFoENK7oRfn

whysofurious

Thankfully these kind of things seem to be rare (and usually simple enough to resolve), but it is why I eventually started reading release notes comments religiously before updating. Sometimes, I have things going on in life where losing access to my phone would have fairly significant consequences.

Volen

Its good we all know now that this is a software issue, not a hardware fault. Will be hopefully resolved by upstream devs in the future. Very worrying experience!