[deleted] Just to make that clear in case you're referring to the part in the changelog about a potential future gallery app replacing AOSP Gallery. That isn't yet in GrapheneOS. It's talking about what the future plan is.

      matchboxbananasynergy Any hint about what existing gallery might be integrated into GrapheneOS ? The same one that is proposed by Accrescent ?...

        For the gallery app to be replaced in GrapheneOS, it would need to meet very specific criteria such as implementing all the necessary intents to be the system gallery app.

        If I had to guess (I have no official info on this), it would likely have to be a gallery app made in-house, rather than adopting an existing one.

        After updating, I got a bootloop resulting in this screen (likely a result of repeated unsuccessful boot):

        google/bluejay/bluejay
13/TQ3A.23605.012/2023061400
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset

        (Typed manually, please excuse any typos.)

        What can do I now, except factory data reset? Is it a good idea to flash the previous release (2023060700)? I guess downgrade prevention isn't active there, but I am not sure.

        EDIT: After several unsuccessful tries, the device has booted successfully. I was trying to power it down (so it doesn't consume battery) by holding the power button for a long time. This did not what I expected, but the phone has finally booted.

          Another update*: It seems that the phone has downgraded to previous version (probably due to A/B scheme). Isn't it what is expected to happen instead of the try again / factory reset menu? Also, the phone is trying to install the update again.

          *) cannot edit the previous post

          I haven't updated yet and this morning I got the same bootloop. I restarted my phone about 15 times and was finally able to get in. Something seems off

            If you're having issues booting the latest Beta / Alpha release, we need more details. We need to know which device model you were using and whether you had any modifications to the OS. Updates are only supported with an unmodified official release of GrapheneOS and you should have the bootloader locked for verifying OS integrity.

            @spl4tt You have a previous post implying that you have a modified OS:

            https://discuss.grapheneos.org/d/2275-will-gos-and-root-related-issues/17

            Is this still the case? That would explain why it's not working.

            @v6ak @DoctorGo If you've modified the OS, we need to know that.

              were any modifications (modding,rooting,etc) made to the OS?

              GrapheneOS

              • My device is Pixel 6a. (Bought in Germany.)
              • Bootloader is locked (verified the hash shown on boot), no root or other modification like that.
              • Free space is currently a bit tight: just 5.51 GB free.

                  v6ak

                  DoctorGo
                  How far does the OS boot after update before failing? Does it get to GrapheneOS logo or to the "Optimizing apps" screen?

                        v6ak Please try freeing up a bit more space if possible. It would be good to know if that helps.

                        • v6ak replied to this.

                            muhomorr It's more of a timing issue. The first time I didn't unlock the sim and it rebooted. When I noticed that I tried to log in as fast as I could. Got past the sim lock and halfway through the password and it would keep rebooting then telling me it was corrupted/couldn't load OS and to factory reset. I just kept restarting it and punching in the passwords as fast as I could. After around 15 tries I got passed the master password and it fired up. Very scary on a day I'm flying to the other side of the country. Glad I didn't factory reset. Anyone having trouble try over and over.

                                We built a release with a possible solution for the Pixel 7 but were unable to get feedback on it. We could build that for other devices if people with that booting issue are willing to test it, but you'll need to explicitly tell us that you want to help with testing a solution.