this post was submitted on 03 May 2025
2 points (100.0% liked)

Privacy

0 readers
20 users here now

Everything about privacy (the confidentiality pillar of security) -- but not restricted to infosec. Offline privacy is also relevant here.

founded 2 years ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] GrapheneOS@grapheneos.social 0 points 1 day ago (5 children)

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

[–] astroboy@fosstodon.org 1 points 1 day ago (4 children)

@GrapheneOS@grapheneos.social Thank you! I will try this right now. You're very helpful and kind.

[–] astroboy@fosstodon.org 0 points 1 day ago (3 children)

@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!

[–] GrapheneOS@grapheneos.social 0 points 1 day ago (1 children)

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

[–] GrapheneOS@grapheneos.social 1 points 1 day ago (1 children)

@astroboy@fosstodon.org The issue you experienced has been reported by a dozen other Pixel 8 users recently and isn't related to any of our recent updates. It has possibly been an issue since Android 15 QPR2 in March or possibly only since the April monthly update. It's not known what's causing it and no one has provided any logs showing any crashes or anything else that's helpful, likely because people can't really do much with the device once it happens. This means we don't know much about the cause.

[–] astroboy@fosstodon.org 1 points 1 day ago

@GrapheneOS@grapheneos.social Yes, I understand now. Thank you for helping.

load more comments (1 replies)
load more comments (1 replies)
load more comments (1 replies)