Find your state attorney general [1]. Write them a letter.
Calmly and dispassionately ask that they look into this from an antitrust perspective. Include a copy of this GrapheneOS thread.
GrapheneOS, on its side, should publish a template letter for every state. They should also consider releasing evidence for Google "repeatedly reaching out to OEMs to question whether they're working with us and threaten[ing] them" [2].
Also inform the European Commission and other anti-trust authorities.
Google is getting more and more authoritarian as far as Android development is concerned. It recently mandated that all Android apps should support foldables within 5 months and that you should include screenshots of your app running on a foldable. I'm not sure if screenshots of simulators are allowed but I'm not going to buy a $1500 foldable just to allay Google's wishes.
> something people should be bothering Ro Khanna about
Maybe. Because he's in Silicon Valley. Swalwell, Lieu, Correa and Lofgren–if you're in California–are better.
Short-term target is the Subcommittee on Antitrust, Commercial and Administrative Law [1]. They would then elevate to the powerful House Judiciary Committee [2].
That said, I can't imagine this is–or should be–a priority for the Congress over the next two years.
"The Sherman Antitrust Act[1] (26 Stat. 209, 15 U.S.C. §§ 1–7) is a United States antitrust law which prescribes the rule of free competition among those engaged in commerce and consequently prohibits unfair monopolies. It"
Source: "https://en.wikipedia.org/wiki/Sherman_Antitrust_Act"
Keep fighting the good fight. GrapheneOS has been a breath of fresh air the past several years and I really don't want to go back to manual rooting/debloating/hardening.
All these corporations a rushing all this locked down tech to push the mass surveillance state they are going to need when enough people wake up have had enough. Eventually the bill comes due.
I am on Murena /e/os on a Fairphone 6+ (https://www.fairphone.com/the-fairphone-gen-6) and it has been truly liberating. I haven't rooted my handsets in a number of years now thanks to locked bootloaders and payment contracts with carriers.
Now, I have virtually no google besides what I want (maps) and even this is just an app, not a system-level something with deep tendrils via google play services.
I don't mind having lost google messages (and rcs), tap to pay, or other things like that. I don't do a ton on my phone, but thanks to this, as well as firefox, kagi, root-level ad blockers and a few other things, it is very pleasant and my battery life is tremendous.
I won't use a phone that I can't really own and exert ownership over.
The sad thing is that they are always way behind on security updates. Old kernels, old firmware, old drivers, all full of known high/critical CVEs.
And then you are missing out on up to 1.5 years of fixes for non-major/critical vulnerabilities because they are still on Android 16 (only high/critical vulnerabilities are in ASBs).
To make all of this worse, Google recently only started releasing fixes for some high/critical vulnerabilities on the latest Android version (currently Android 17).
OEMs and Google somehow convinced people that having a recent ASB is enough, but it is only the tip of the iceberg.
I have virtually no google besides what I want (maps)
Well, except that /e/OS runs Google’s obfuscated DroidGuard binary in a privileged process to pass basic integrity. Yes, Google still has privileged access to your phone, unless you disable Play Integrity support in microG (which will break quite many apps). The even worse thing is that Google can send a unique DroidGuard blob just for you (since it is per request).
Moreover, /e/OS gives certain Google apps more privileges than the standard Android app sandbox (Google Maps being one of them).
Using it on a Fairphone eh? Well, you are also running proprietary Chinese TCL camera image processing blobs.
——
People who care about privacy and security do not use /e/OS. It is LineageOS with Murena’s cloud crap on top, along with a pile of hacks that weaken security and privacy.
Also, they are just very incompetent. E.g. Fairphone was hit by a bad bug where WiFi didn’t work on a lot of networks. When this was already known for months, Murena rolled out the same bug.
You're still forced to run microG right, or is there a way around it, I am not aware of, if you want to run google apps or apps you previously paid for in the google play store?
Yes, and your microG runs proprietary Google DroidGuard blobs in a privileged process. Unless you disable (basic) Play Integrity support in microG, but then a bunch of apps do not work.
Murena lies about being degoogled.
GrapheneOS solves this the correct way by providing support for sandboxes Google Play.
By the way, you should not run any Google apps on /e/OS because they give a bunch of Google apps higher privileges than the normal Android app sandbox.
Now, I'm even more motivated to install GrapheneOS, just to spite Google.
More seriously, it's an indication that GrapheneOS is large enough that Google considers it a potential threat. As the saying by Gandhi goes "First they ignore you, then they laugh at you, then they fight you, then you win'.
This makes me want to try GrapheneOS? Like maybe it's just general anti-competitive behavior, but part of me is whispering "what's Google so afraid of?"
Google's in a real hurry to lock down Android lately.
They already got once over trying to keep competing services out with their GMS agreements. Clearly, the only lesson they learned is "try harder."
I hope they get dismantled in court at least in EU for this bullshit. I'm sick and tired of vendors deciding what the users are and aren't allowed to do with their own devices.
This is not very detailed, there's the new threats against OEMs (I guess Motorola), but it's not clear if they also noticed new mechanisms (besides Play Integrity and pairip/automatic protection).
Pairip is being pushed to all apps though, I think four thirds of the ones I try to install have it.
It would be time for them to recognize that the Play Store and account requirements are bad things™, though.
For some reason a poster in the thread says that things will be better in February with the Democrats.
The new Congress is sworn in on January 3rd and, as graphene rightfully pointed out, it's more of the doj issue at the moment.
Congress could try to pass more laws for this, but there's already anti-monopoly laws in the books and they're not too proficient at passing laws that don't involve renaming post offices.
it seems like Google learned the no good deed goes unpunished lesson. given how Apple is free to lock down their hardware by never offering any options for any alternatives in the first place, Google now wants the same considerations.
GrapheneOS, on its side, should publish a template letter for every state. They should also consider releasing evidence for Google "repeatedly reaching out to OEMs to question whether they're working with us and threaten[ing] them" [2].
[1] https://www.naag.org/find-my-ag/
[2] https://grapheneos.social/@GrapheneOS/117645917131936200
Google is getting more and more authoritarian as far as Android development is concerned. It recently mandated that all Android apps should support foldables within 5 months and that you should include screenshots of your app running on a foldable. I'm not sure if screenshots of simulators are allowed but I'm not going to buy a $1500 foldable just to allay Google's wishes.
Maybe. Because he's in Silicon Valley. Swalwell, Lieu, Correa and Lofgren–if you're in California–are better.
Short-term target is the Subcommittee on Antitrust, Commercial and Administrative Law [1]. They would then elevate to the powerful House Judiciary Committee [2].
That said, I can't imagine this is–or should be–a priority for the Congress over the next two years.
[1] https://judiciary.house.gov/subcommittees/committee-judiciar...
[2] https://judiciary.house.gov/about/membership
"The Sherman Antitrust Act[1] (26 Stat. 209, 15 U.S.C. §§ 1–7) is a United States antitrust law which prescribes the rule of free competition among those engaged in commerce and consequently prohibits unfair monopolies. It" Source: "https://en.wikipedia.org/wiki/Sherman_Antitrust_Act"
Now, I have virtually no google besides what I want (maps) and even this is just an app, not a system-level something with deep tendrils via google play services.
I don't mind having lost google messages (and rcs), tap to pay, or other things like that. I don't do a ton on my phone, but thanks to this, as well as firefox, kagi, root-level ad blockers and a few other things, it is very pleasant and my battery life is tremendous.
I won't use a phone that I can't really own and exert ownership over.
And then you are missing out on up to 1.5 years of fixes for non-major/critical vulnerabilities because they are still on Android 16 (only high/critical vulnerabilities are in ASBs).
To make all of this worse, Google recently only started releasing fixes for some high/critical vulnerabilities on the latest Android version (currently Android 17).
OEMs and Google somehow convinced people that having a recent ASB is enough, but it is only the tip of the iceberg.
I have virtually no google besides what I want (maps)
Well, except that /e/OS runs Google’s obfuscated DroidGuard binary in a privileged process to pass basic integrity. Yes, Google still has privileged access to your phone, unless you disable Play Integrity support in microG (which will break quite many apps). The even worse thing is that Google can send a unique DroidGuard blob just for you (since it is per request).
Moreover, /e/OS gives certain Google apps more privileges than the standard Android app sandbox (Google Maps being one of them).
Using it on a Fairphone eh? Well, you are also running proprietary Chinese TCL camera image processing blobs.
——
People who care about privacy and security do not use /e/OS. It is LineageOS with Murena’s cloud crap on top, along with a pile of hacks that weaken security and privacy.
Also, they are just very incompetent. E.g. Fairphone was hit by a bad bug where WiFi didn’t work on a lot of networks. When this was already known for months, Murena rolled out the same bug.
You're still forced to run microG right, or is there a way around it, I am not aware of, if you want to run google apps or apps you previously paid for in the google play store?
Murena lies about being degoogled.
GrapheneOS solves this the correct way by providing support for sandboxes Google Play.
By the way, you should not run any Google apps on /e/OS because they give a bunch of Google apps higher privileges than the normal Android app sandbox.
Google is still running a business. A good business, actually.
https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
More seriously, it's an indication that GrapheneOS is large enough that Google considers it a potential threat. As the saying by Gandhi goes "First they ignore you, then they laugh at you, then they fight you, then you win'.
They already got once over trying to keep competing services out with their GMS agreements. Clearly, the only lesson they learned is "try harder."
I hope they get dismantled in court at least in EU for this bullshit. I'm sick and tired of vendors deciding what the users are and aren't allowed to do with their own devices.
They have two more months of zero Congressional oversight and two more years of a broken executive (but enraged Congress).
What I think they may be missing is the states.
Pairip is being pushed to all apps though, I think four thirds of the ones I try to install have it.
It would be time for them to recognize that the Play Store and account requirements are bad things™, though.
The new Congress is sworn in on January 3rd and, as graphene rightfully pointed out, it's more of the doj issue at the moment.
Congress could try to pass more laws for this, but there's already anti-monopoly laws in the books and they're not too proficient at passing laws that don't involve renaming post offices.
Fuckers.