I also have a 5a and the mobile network is unavailable. I've tried various things like switching back to LTE only. Nothing works so far (for more than a couple of minutes anyway). This happened immediately after this update was applied.

    other8026 Pending the next release, can I roll back to the previous release (2024090400) to have a functional phone until the next version fixes the issue?

        Can confirm that phone/text messaging abilities get shot yesterday/this morning after the recent update on 5 and 5a's. I've installed grapheneOS on 100's of phones over the past 2 years (absolutely love you guys and the work you do) and it seems this is now a chronic issue with customers emailing me all morning. Have a few 6, 6a, 7 pro devices that work just fine after the update, but the 5's seem to be an issue... as outlined. Spent nearly 2 hours with carrier technical support and after trying everything imaginable, finally re-flashed the OS, and the same issue happens. Have pulled the SIM card to a different device and it works fine in other devices. So this appears isolated to the device itself and happened right after the update.

          MARK37 Also pulled other functioning SIMs into the Pixel 5 and the SIM will not work on the 5.

            MARK37 yes, many people with 5th generation Pixels are experiencing issues, issues that weren't caught during testing. A new release to undo the related changes is coming soon.

                GrapheneOS updated this morning on Pixel 5 and now calls and texts don't work on Verizon. Internet seems to work but spotty. Anyone else having this issue?

                    Pixel 8, So Far So Good, So What! Thank you for the consistent hard work.

                    Dumdum Downgrade protection for OS updates and for verified is are important standard Android security features, not something specific to GrapheneOS. Downgrade protection for app updates is also a standard Android security feature, but it doesn't have verified boot for system updates. The section you're quoting is about GrapheneOS extending verified boot to system app updates.

                        GrapheneOS The section you're quoting is about GrapheneOS extending verified boot to system app updates.

                        Good to know. I am aware that downgrade protection is standard for Android though. I have a habit of using the website as a first reference, and that section was the first thing I saw that mentions downgrade protection.

                          other8026 Thank you for this good news. I cannot make or receive any calls with Pixel 5 now after the recent update. Looking forward to the new release with undos.

                            Yes thank you all very much for thr incredible OS and dev support, it's nice to be able to have an excuse not to answer my phone now. ;)

                            GrapheneOS Yes. Using the official Wireguard app. Never had any issues with this before.

                            EDIT: Latest Alpha fixed it, thanks!

                              GrapheneOS Hello. I am one of those who have been affected by the latest GOS update on Pixel 5a.

                              I am unable to make calls and all incoming calls go directly to voice mail. Making any call results on an abrupt Call Ended. No tone, no ring. Just shown the active call blue screen. Call Ended and hangup sound.
                              Carrier does support VoLTE and never had issues till making calls with LTE Only.

                              First time that the whole calling system stops working in such a way that rebooting, pulling/reinserting the SIM card had not fixed.

                              EDIT: I did called carrier thinking it was their problem. They could not help me. After a while what I was told was to contact the phone's manufacturer and have the phone unlocked. This makes no sense to me Pixel 5a is a carrier unlocked phone and this phone since day one has was activated and has always been used with the same carrier. SM.
                              I guess the "locked" they see has to do with whatever GOS change is affecting the Pixel 5a.