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.
GrapheneOS
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] No, it's a production release going through the same process as every other release. Please read https://grapheneos.org/releases#about-the-releases. Releases never go directly to the Stable channel but rather get pushed out to Alpha, then Beta and then Stable. You choose how early you get it via the channel selection. There are not separate releases for Alpha and Beta, which is a misconception about how we do things.
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] A user has reported it works fine when configured correctly in Owner:
https://discuss.grapheneos.org/d/16820-urgent-sms-registration-is-broken-on-android-15/38
We know there are SMS/MMS regressions brought by Android 15 in secondary users which are not GrapheneOS specific.
@[email protected] @[email protected] Apple makes that fairly clear themselves by the fact they only backport a subset of the patches and don't really like acknowledging they're even still providing support since they want people to move on. You can find many sources for it by searching for it but whether those should be considered reliable is another story. We don't particularly see a reason to reference what someone else says particularly if they often get things wrong.
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.
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.
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] @[email protected] No, these devices don't receive proper security patches from day one. They get incomplete patches with significant delays, and years of delays for the full security patches.
With the example of Fairphone, they ship the Android Security Bulletin backports with a 1 or 2 month delay. They don't ship monthly or quarterly releases, so they miss all those patches. The yearly updates get shipped with at least 1 year of delay, so they can't ship the current monthly and quarterly releases without fixing that first. The delays get longer as the devices get older, until the point it's multiple years with the delays portrayed as providing longer support.
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.