You can't get a license for GMS if you want to make money shipping devices that allow users to run unlicensed GMS. You can make all the money you want shipping AOSP devices that don't/can't run GMS. We both agree on that much, right?
You can't get a license for GMS if you want to make money shipping devices that allow users to run unlicensed GMS. You can make all the money you want shipping AOSP devices that don't/can't run GMS. We both agree on that much, right?
Google has license terms for Google Mobile Services forbidding their OEM partners from selling devices with forks of AOSP which are not certified by Google. The certification process doesn't permit GrapheneOS. It would require removing many of the privacy/security features and would create unacceptable delays for updates. Their certification process does permit our sandboxed Google Play feature and has no rules against it. We could obtain certification for an OS with sandboxed Google Play but without many of our other features. It would have significant delays for updates similar to how all regular Android OEMs cannot ship an update without weeks of delay.
Google is not allowed their OEM partners to sell unlimited amounts of devices with GrapheneOS or any other AOSP-based OS not certified by Google. They're only willing to permit it at a small scale. It has nothing to do with sandboxed Google Play. Google knows it's illegal and unenforceable in court but they're using it to intimidate OEMs into going along with what they want.
We don't include Google Mobile Services in GrapheneOS and are not violating the license. Google has repeatedly helped us improve sandboxed Google Play. Google added GrapheneOS and Vanadium support for FIDO2 and passkeyhs to Play services which allowed us to remove our workarounds for it. They aren't putting any significant effort into avoiding regressions with it but definitely aren't intentionally breaking it. We have a testing and release channel process for sandboxed Google Play since it's not officially supported.