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 a 6. My device is not modified.
DoctorGo How much free data do you have available?
GrapheneOS 78.75 free
v6ak Please try freeing up a bit more space if possible. It would be good to know if that helps.
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.
GrapheneOS Yes, I'm still rooted, and I understand that you won't support this. But seeing that others with no modified OS have the same issue tells me that it's probably not that.
Also, flashing the new release without the patched boot.img has the same issue, but I didn't lock my bootloader.
I can surely test the fixed build on my p7p, of course without the patched boot.img, to see if it runs.
spl4tt Yes, I'm still rooted, and I understand that you won't support this. But seeing that others with no modified OS have the same issue tells me that it's probably not that.
As a reader of the forum, who is interested in knowing how widespread an issue like this might be, it would be nice to know what fraction of reporters are running unlocked bootloaders, rooted devices, unofficial builds, forks, etc. So it might be supportive for people running something other than an official GrapheneOS build to say so in reports (arguably each time). Empirically it seems as if in this case that would have saved the moderators/developers some time figuring out how to weigh this particular report (and this sounds like the sort of issue that it would be good to be figured out sooner rather than later).
muhomorr I got GrapheneOS logo, which was being shown for a long time. (Didn't measure, just subjective…) Then, the boot got aborted. (Not sure if this was the case of all the boot attempts. The first reboot was more like 1. reboot, 2. do something else without watching the screen, 3. see the error screen.)
GrapheneOS
Retrying, again with 2023061400. Before update:
I just touched Reboot from the notification.
Now, the phone is installing an update (probably 2023061402).
1402 works, with and without patched boot.img. It's now on the optimizing app screen, which will take a while.
Thank you for the amazing work GrapheneOS team.
I've just successfully finished the upgrade (including reboot and Optimizing app X/Y phase) to 2023061402 on my Pixel 6a. Free space has increased to 31.20 GB, but this might be caused by finished update, as we no longer need to keep old version of system and old AOTs for apps.
This update has also brought me 5G in Czech Republic.
