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.
@GrapheneOS sounds like monopolistic behaviour.
we do have laws against that in the eu. did you raise a complaint with the eu dma team?
or the canadian competition bureau ?
@GrapheneOS What would stop them going after users for unauthorized use of Play Store?
@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?
This is going to lead to more boot loading,
As in booting people from the smartphone concept and loading up their lives with real things.
Smartphones, if I had to say, are, at their core, devices specialized at being a gate between our eyes and our actual experiences.
A gate that can, and has been, hijacked.
@GrapheneOS Saw this coming when the product exclusivity emerged - need drivers for all of the other devices..... 😮💨
@GrapheneOS
That is horrible.
And very ironic for a company who’s slogan at some point in the past was “Don’t be evil”
@GrapheneOS seems like a lawsuit in the making.
@GrapheneOS Hope u peeps persevere, ur my next o/s, if ur still around
@Ox1de We'll still be around. We plan to outlive Android.
@uriel We explained exactly how they're doing that in our thread. They're contacting OEMs trying to scare them into not working with us.
If Google wasn't a bad actor engaging in egregious violations of antitrust law, then they'd be happy to work with us and make their apps and services fully available as regular sandboxed apps on GrapheneOS. They would be happy to build sandboxed Google Play themselves instead of us doing it. They should want their apps and services everywhere, shouldn't they?
@uriel Google has played the same anti-competitive games against everyone in the space. They heavily worked to crush serious competition including Microsoft's entry in the space. They wield their monopolies as weapon to reinforce and expand each other. They'll stop people using YouTube in order to force them to use everything from Google. iOS only gets special treatment because it was already so established. They'd definitely try to kill it too if they had a more advantageous position over it.
@GrapheneOS What we need is a code repo hosted in the darklands, ie. not github or bitbucket etc, where people just start making tools to rip Google software (and I include Chrome, oh do I include Chrome) apart and completely deliberately violate all terms of service. It's got to the point we need to do this, it's just interfering in peoples' lives too much and the alternatives are underresourced.
@GrapheneOS
It's because GrapheneOS a better than google and google is hell bent on identity theft of all who use AOSP. Just Tom Clancy's Power Plays but in real life. I recommend Graphene to most people. GrapheneOS is what a phone OS should be. I tell people to delete their Google environments, accounts and request all data deletion (or, at least not be findable through google) through their request form.
@GrapheneOS Probably most of those pixel "features" are ai based shite. I wonder how much influence Google has with the Chinese makers - China clearly has Drumpf in their pocket.
@GrapheneOS, the community is on your side!
What, in your opinion, is the reason for this aggravation of the problem right now? Is it the growing number of users of GrapheneOS?
@GrapheneOS Use open source to build your fortress, then pull the ladder up behind you and start shooting at open source from behind the walls.
@GrapheneOS So, Google straight-up admitted to killing alt Android, right after MS announced new integrity requirements for Windows which could jeopardize Linux on the PC, surely that's just a coincidence....
Google is trying to convince OEM partners not to support [...] bootloader unlocking
Do we have proofs for that? If we can have strong arguments that the bootloader is part of Android OS, then it's covered by the the (european) DMA and likely the other countries' equivalent.
We can then use the DMA to require them to implement the possibility to open and to relock the bootloader using non-factory keys. If that's part of Google requirements for their compatibility certification, then all OEM would need to follow
@S1m It's factual information and not speculation. It has been directly communicated to us by multiple OEMs. Don't follow the logic of what you're saying about it though and how it could be used to force doing those things. There's realistically no way to force making secure devices or proper alternate OS support. We aren't interested in that since it would never result in a device we could support in practice. Trying to force it to happen is just not going to work.
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.