GrapheneOS version 2025050300 released:
https://grapheneos.org/releases#2025050300
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
https://discuss.grapheneos.org/d/22203-grapheneos-version-2025050300-released
#GrapheneOS #privacy #security
@GrapheneOS@grapheneos.social 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.
@astroboy@fosstodon.org That’s extraordinarily unlikely and you’re likely misdiagnosing it.
OS updates are tested on each device model before reaching Alpha and go through both Alpha and Beta testing before Stable. This OS update hasn’t reached the Stable channel yet.
OS updates happen in the background and kick in after rebooting. There’s a toggle to automatically reboot after updates while idle in the System Updater settings but it’s disabled by default.
If an update fails to boot, it gets rolled back.
@GrapheneOS@grapheneos.social Thank you for the information. Yes, it looks as if it was installing an update, but it could be I’m completely wrong about it. I don’t have the toggle to auto reboot turned on.
@astroboy@fosstodon.org There’s a known upstream Android bug impacting 8th generation Pixels which can cause them to become unresponsive with a black or frozen screen. The device remains booted and functioning when that happens so trying to boot it isn’t going to work because it’s already turned on and still mostly functioning. You have to long press the power button to force the device off if you’ve encountered that issue. It might be a GPU bug introduced in Android 15 QPR2 but we haven’t determined it yet.
@GrapheneOS@grapheneos.social I tried to long press the power button, but nothing happens, also tried long pressing power + volume down buttons. Is there anywhere where I can read more about the display bug? Does it fix itself, after reboot? Somehow my phone is absolutely unresponsive.
@astroboy@fosstodon.org Hold power for a minute or longer.
Which device model do you have? Is it an 8th generation Pixel?
There’s something wrong with 8th generation Pixels since perhaps around Android 15 QPR2 in March 2025 which can cause the device to become unresponsive until forced off. It can be a problem to get it forcefully turned off. It appears to be some kind of upstream Android bug or Pixel firmware bug. We don’t know if it happens more often with GrapheneOS. The May update will hopefully fix it.
@GrapheneOS@grapheneos.social Yes! Pixel 8 is my device. Here is what I tried, and what has worked. Thank you for helping! https://fosstodon.org/@astroboy/114450411390638894
@GrapheneOS Apparently I was holding down the wrong buttons. I now hold down the power + volume UP button, and my phone is working! But after the Sim Card pincode screen appears, the whole screen goes black again. So maybe that is indeed that upstream bug you were talking about. But how to fix it?
@astroboy Try plugging the device into a wall charger and then turning it off completely. Hold volume down while it reboots so it boots into fastboot mode instead of the OS. While it’s plugged in and in fastboot mode, turn off the device from there and let it charge for a while. Then, see if it works properly after it has been charged for at least around 10 minutes.
@GrapheneOS@grapheneos.social Thank you! I will try this right now. You’re very helpful and kind.
@GrapheneOS Wait, I didn’t even need to try anything, it’s just working again! But I do see that it was caused by an update, because I see a message “App restart required”. The version I have now is 2025-04-25-00. So it was caused by another update, not this one. Thank you so much for your help anyways!
@astroboy That doesn’t mean it was caused by an update and it fact shows that it almost certainly wasn’t related. You had an update installed and waiting for you to reboot the device. The issue causing it to lock up with a black screen occurred on an old version of the OS prior to the 2025042500 release. When you forced it off and turned it on, you booted 2025042500 for the first time. That implies you weren’t on 2025042500 yet. If it had failed to boot repeatedly it’d have been rolled back.
deleted by creator