Apple doesn’t prevent other OEMs from selling phones.
Apple doesn’t prevent other OEMs from selling phones.
That... is pretty spun, especially with regard to the Microsoft comparison upthread to which I responded.
They aren't trying to restrict "other mobile OSs", they're specifically saying GrapheneOS, and in general any AOSP-derived system which is designed to interoperate with the GMS frameworks.
Like, even AOSP alone would be fine, c.f. Fire or Harmony which never got this attention. GrapheneOS is specifically in violation because it includes a feature to suck down and essentially "pirate" an unlicensed copy of the GMS suite, thus making the phone into the practical equivalent of a Pixel.
That is what Google objects to, because they sell GMS as a product and aren't interested in their downstream OEMs "giving it away" for free by bundling a third party product that doesn't license it.
Basically GrapheneOS, as it exists right now, just can't be shipped as a commercial product. There's no license for the magic stuff they claim to support.
GrapheneOS can be shipped as a commercial product and is going to be shipped as one on Motorola devices. It's only Motorola themselves which is unable to sell devices with it. Google's license doesn't say they can't provide official support for GrapheneOS and sell devices to other companies to sell GrapheneOS on those.
The approach to handling Google Mobile Services in GrapheneOS is entirely legal and Google has never raised any issue with it either with us or Motorola. We don't include it in GrapheneOS but rather only include a compatibility layer to make it run as a regular sandboxed app if users install it. We don't need to mirror it for the sandboxed Google Play feature to be usable. Mirroring freely available software is highly protected and no different from the many APK mirror sites. It's the Google Mobile Services licensing and Google's overall behavior with it egregiously violating antitrust laws which is illegal.
You're claiming providing a compatibility layer to run freely available software without privileged access it piracy. What we're doing is strongly protected under the law. Google's efforts to interfere with providing Android app compatibility elsewhere under the guise of a supposed security feature are going to have serious consequences for them. That's already coming in the EU and beyond. The bait and switch they've pulled with the Android Open Source Project and the coercive rules for their OEM partners is also going to have consequences beyond what it already has.
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.