@[email protected] It would still be end-of-life from lack of development or releases for the firmware and drivers even if it was fully open source. It wouldn’t be possible for us to take over development of everything and we don’t receive the security issue reports for it. Additionally, building firmware updates requires the signing keys for that and we don’t have those so having the sources doesn’t allow us to build firmware updates in general. The signing is important for security for a lot of firmware.

@[email protected] It has nothing to do with Pixels specifically and applies to all other hardware whether or not it runs Android. There are no devices where we wouldn’t need ongoing support for firmware updates and development of the drivers and other device support code.

This release is now available in Alpha:

https://grapheneos.org/releases#devices

It won’t go past Alpha because we want to fix a few of the minor reported issues before it reaches Beta and then Stable. We should have another release much later today.

@[email protected] Pixel 5 has been end-of-life since December 2023 after the last update in November 2023. It hasn’t received driver and firmware updates since then. We provided what we could with very limited resources available for insecure devices via the Pixel 5a still being supported, but the Pixel 4a (5G) and Pixel 5 had significant regressions with each quarterly release we had to work around. A15 would cause enormous problems and we don’t need to port it to 15 to keep it working for another year.

@[email protected] It won’t be ported to Android 15 because it would require a lot of our resources while creating a lot of regressions for Pixel 5 users. It would take a long time for it to become stable with Android 15 since it has no official support for it and would need a bunch of hacks to make it work. We’d need to switch to using a prebuilt vendor.img built from Android 14 QPR3 and combine that with Android 15. It’d theoretically work but in practice lots of bugs and lots of work.

GmsCompatConfig is the text-based configuration for the GrapheneOS sandboxed Google Play compatibility layer. It provides a large portion of the compatibility shims and sets the maximum supported versions for Play services and the Play Store.

@[email protected] Resolves an issue causing reporting old crashes after reboot which were already reported. It was an upstream Android bug causing it.

GmsCompatConfig is the text-based configuration for the GrapheneOS sandboxed Google Play compatibility layer. It provides a large portion of the compatibility shims and sets the maximum supported versions for Play services and the Play Store.

Forum discussion thread:

https://discuss.grapheneos.org/d/16257-gmscompatconfig-version-140-released

GmsCompatConfig is the text-based configuration for the GrapheneOS sandboxed Google Play compatibility layer. It provides a large portion of the compatibility shims and sets the maximum supported versions for Play services and the Play Store.