GrapheneOS version 2023042900 released

GrapheneOS

GrapheneOS version 2023042900 released: https://grapheneos.org/releases#2023042900.

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

supersonic

GrapheneOS why disable UWB by default?

de0u

This release is likely available immediately to devices set to use the Alpha channel. If the release works well for Alpha users, it is likely to be released in a day or two for devices set to use the Beta channel; if that goes well it will likely be released to the Stable channel soon after. You can see which channel your device is set to use via "Settings", "System", "System update".

Note that downgrade protection means that if you switch channels to try out a new release you won't be able to switch back to the older GrapheneOS if you don't like the release you got via a faster channel. Neither switching release channels nor sideloading an older OTA image will work, so the earlier-access channels may be best for second devices or adventurous individuals.

Please note that I do not speak for the GrapheneOS project. I am mentioning this because recently there have been some "When will my device get this new release?" posts, and also some "How do I go back?" posts.

Graphite

de0u
Seems like an easy misunderstanding to avoid by not using past tense "released" which many people would assume is already released to their channel. Just call it a "release".

de0u

Graphite But people do ask "Why hasn't my device received it?", "How can I get it?", and, sometimes, "How can I go back?". I think a brief blurb could make several things clearer for anybody who reads a release announcement. So I took a stab at one!

treequell

supersonic Attack surface reduction. Most people don't use it, and if it's needed it can be enabled and will still work.

Blastoidea

If it isn’t inappropriate, I’ll sign onto changing “released” to “release” on the announcement.

I think it clarifies without changing the meaning, although I suspect this could trigger an endless and circular debate.

Blastoidea

Just got it.

Pixel 5, Stable channel.

ridiculousties

I got this update about 6 hours ago on my Pixel 5a.

I didn't pay attention to what the phone was doing while it was updating, and just let it do its thing for about 10 mins. Well, after those 10 mins passed, I checked the phone - and saw the Black Screen of Death.

Luckily, at that point the phone at least responded to button presses and charging. If I held down the power button, there was a short vibration, and when charging the phone the usual tune would play. My PC would recognize my Pixel, but it couldn't mount it. The screen stayed black, always.
I tried all of the usual "solutions" to BSoD listed on Google's forums. None of them did anything at all.
At some point, the phone stopped responding to any button presses and my PC stopped recognising it.

Anyone else experiencing this?

Of course a BSoD on Pixel phones isn't unusual at all. Most likely this is just a coincidence, and the bricking was caused by Pixel's crappy manufacturing rather than the update.

Relaks

ridiculousties
What have you tried so far? Did you try the suggestions from this article? https://www.ifixit.com/Wiki/Google_Pixel_Unresponsive_Black_Screen
(I'm assuming that device wipe is only a last resort).

ridiculousties

Relaks
I tried pretty much every suggestion I could find, including the ones listed in the article you sent. I didn't do a screen replacement, though (and likely won't, since it would be just more cost-efficient to buy a new Pixel).
As I said already, the screen always stayed black, and at some point the phone went full-brick and stopped emitting all vibrations and sounds.
A device wipe wouldn't be too catastrophic, tbh - I'm not so foolish as to store critical data exclusively on my phone. But again, my phone is a complete brick right now, so wiping the system by booting into fastboot is pretty much impossible.

Since nobody has reported similar issues here, I'm guessing there's no correlation to the update. My brick phone problem probably doesn't belong on GrapheneOS forums then.