Google is sabotaging their OEM partners by making a growing number of features and updates exclusive to Pixels. At the same time, Google is trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking. They're also trying to harm GrapheneOS directly.
FIDO2 and passkeys can also be used without Google Play. We had a workaround to make it work with Google Play and could have worked around the other stuff too but it's nice they implemented this. Google's engineers are not the problem. Their business people are the problem.
Google's business side is actively trying to wipe out alternatives. Google Mobile Services licensing has many illegal terms aimed at preventing competition. That isn't enough for them. They're very directly trying to harm GrapheneOS in multiple ways and outright wipe it out.
The current situation is serious. We're very interested in talking to @AGToddBlanche and others in a position to take rapid action against Google's escalating anti-competitive behavior. They're taking increasingly extreme actions to wipe out alternatives and action is needed.
There have been multiple lawsuits by the US DoJ against Google for antitrust violations with Android. Those have barely touched on the most egregious criminal antitrust violations which are currently rapidly escalating. We're interested in talking to @TheJusticeDept about it.
We expect Google will begin bootloader locking Pixels, continue heavily pushing the illegal Play Integrity API and trying to make forks of AOSP non-viable. Many of their actions are clear violation of US criminal law. US antitrust law even includes prison time for individuals.
Recent actions by Google have made it clear they're actively at war against alternatives. Our community can help us get in touch with government prosecutors and regulators. We have the resources, support and tools to continue regardless of Google's actions but won't do nothing.
@GrapheneOS The EU already served Google a judgement because of several antritrust practices.
https://www.skadden.com/insights/publications/2026/07/google-android-the-final-chapter
@sojaded It doesn't seem to have accomplished anything. Google continues rapidly escalating multiple forms of attacks on alternatives and is specifically directly attacking the GrapheneOS project.
@sojaded The EU itself is encouraging using the Play Integrity API for multiple EU standards for banks. EU countries are adopting the Play Integrity API as part of their own apps. The primary purpose of the Play Integrity API is to enforce Google Mobile Services licensing by banning any hardware or OS which isn't licensing it. They're directly enforcing the licensing terms for GMS through using it. This is the main current viability issue for GrapheneOS and they've made it far worse.
@sojaded Google has more attacks on alternatives and also specifically GrapheneOS in progress beyond the Play Integrity API and related features such Play Store app protection which using multiple measures which result in blocking using alternative operating systems for apps enabling it.
These features do not provide any serious security protection and deliberately permit devices with a decade of missing security patches. They exist to protect and expand Google's monopolies.
@GrapheneOS yeah, just had my state's digital ID provider tell me they won't support GrapheneOS (Play Integrity) because they only support "standard operating systems" 😕
Small wonder. If I were working for #Google, that would be the most logical strategy.
I think the more interesting question is: Why did they provide you with the possibility to install another OS (#GrapheneOS) in the first place.
Other than that, it is appalling and exasperating.
And if the idea was to enter the military market, etc., what went wrong?
There are a lot of engineers at Google who support what we're building and have directly worked with us. People there have repeatedly helped us and even explicitly added support for GrapheneOS to Google software including supporting Vanadium for Play services FIDO2 and passkeys.