Remix.run Logo
▲ Google is pushing OEMs against GrapheneOS and bootloader unlocking(grapheneos.social)
266 points by mraniki 2 hours ago | 62 comments
▲JumpCrisscross an hour ago | parent | next [-]

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].

[1] https://www.naag.org/find-my-ag/

[2] https://grapheneos.social/@GrapheneOS/117645917131936200

▲testtestmetest a minute ago | parent | next [-]

I dont mean to discourage people, but why do you think State Attorneys will care about this, its in their best interest to destroy privacy and they see Google as a partner when it comes to investigating and prosecuting crime.

▲hn_submit 43 minutes ago | parent | prev | next [-]

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.

▲microtonal 36 minutes ago | parent | next [-]

If you are an EU citizen, contact the DMA team.

https://digital-markets-act.ec.europa.eu/contact-us-eu-citiz...

Write a polite, well-reasoned letter. Focus on one issues at a time. Google Play Integrity is currently one of Google’s major gatekeeper abuses. Describe how it affects you in your daily life (eg not being able to use the IKEA Smarthome, Volkswagen, or some banking apps) and why it is anti-competitive.

Also contact your national anti-competition authorities.

▲mikae1 a minute ago | parent [-]

Fork Android. Isn't that the only long-term way forward? Create a coalition with e/OS and LineageOS.

Even if this battle is won by law, they're going to continue to make maintaining spinoffs increasingly difficult.

In Google's eyes, open source was good for Android adoption. Now it's a nuisance at best.

▲well_ackshually 10 minutes ago | parent | prev [-]

"support foldables" doesn't mean "have custom layouts for them", merely "don't attempt to prevent foldable users to use the app".

Every single Android app will, by default, support foldables. You have to ACTIVELY take steps to not support them. Sure, it might not look great, but you're not forced to make it look great.

You're also conflating two things: Android starting to ignore the screen orientation declaration in the manifest on some devices (which is the right thing to do), and play store (optional, although the main way people get apps) requiring you to not attempt to block foldables

And of course emulator screenshots are allowed lmao. There's so many more egregious things that Google is attempting with Android than "boohoo they're deprecating a terrible thing that allowed developers to be incompetent"

▲boredatoms an hour ago | parent | prev [-]

Its also something people should be bothering Ro Khanna about, given the area he represents

▲JumpCrisscross an hour ago | parent [-]

> something people should be bothering Ro Khanna about

Maybe–he is in 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 any time in the near term.

[1] https://judiciary.house.gov/subcommittees/committee-judiciar...

[2] https://judiciary.house.gov/about/membership

▲peri-cl 24 minutes ago | parent [-]

(Swalwell's district is represented by Aisha Wahab now).

▲nzeid 2 hours ago | parent | prev | next [-]

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.

▲acd 38 minutes ago | parent | prev | next [-]

Strange since Pixels allow boot loader unlocking.

"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"

▲skeledrew 20 minutes ago | parent [-]

> Pixels allow boot loader unlocking

Until Google decides otherwise.

▲paweladamczuk 12 minutes ago | parent | prev | next [-]

I wish they would lead with evidence and sources for the claims they're making. As it stands, it looks to me like ragebait marketing.

I support what people at GrapheneOS do but I don't appreciate their recent communication style.

▲drnick1 an hour ago | parent | prev | next [-]

My 10a will be the last Pixel I buy if the bootloader of future editions can't be unlocked. I'll jump ship to Motorola.

▲Helmut10001 34 minutes ago | parent | next [-]

Yes, this was also my consideration - I think the time of open Pixels is over and it is time for a third party to step in (Motorola.. maybe..).

▲ozlikethewizard 30 minutes ago | parent | prev [-]

And honestly I think this is a good thing. The easiest method to degoogling being dependent on owning google hardware was always a timebomb. Ideal world all phones would have properly relockable bootloaders, but if there was only going to be one device I think I am happy its not going to be a google one in the future. Purchasing a pixel still supports their bottom line st the end of the day, even if the sole reason for it is to escape google.

▲latentsea an hour ago | parent | prev | next [-]

Everyone should run GrapheneOS.

▲madduci 40 minutes ago | parent | next [-]

We need cheap phones supporting it

▲flexagoon 32 minutes ago | parent | next [-]

You don't have to buy a new phone. A used Pixel can be pretty cheap

▲microtonal 33 minutes ago | parent | prev [-]

Cheap phones like the Pixel 9a or 10a?

That said, hope support trickles down the Motorola line-up pretty quickly.

▲dingaling 23 minutes ago | parent | prev [-]

Or Lineage, Calyx or eOS. Let's not create another monoculture.

▲Leonard_of_Q 10 minutes ago | parent [-]

So, really, a viable AOSP since all of these - GrapheneOS included - are based on it. AOSP, unlockable bootloaders and documentation or driver source code so hardware can be supported.

▲Quothling 15 minutes ago | parent | prev | next [-]

I guess we're going to need the EU to support right of choice on devices.

▲YuechenLi 32 minutes ago | parent | prev | next [-]

With LLMs, unless you use a more extreme version of Samsung style hardware fuse, there really isn't anything that Google can do to prevent bootloader unlocking from a technical standpoint since all it really takes is one bug in the kernel for the bootloader to be unlocked.

▲m132 23 minutes ago | parent | next [-]

If getting to run your own code is all that matters--possibly. Google is doing much more to crack down on custom software. See the recent rollout of the GMS-based Captcha [1] and Play Integrity [2].

Essentially, Google is actively trying to fracture the Internet into 2 halves: one anything can access, and another that'll require hardware-generated, cryptographic proof of the client running the latest, patched-up version of a locked-down operating system. The goal is clearly to lock anybody who manages to break into their own devices out of the latter. Some banks and even the official EU wallet [3] are already exclusively on that other side.

[1] https://support.google.com/recaptcha/answer/16609652

[2] https://developer.android.com/google/play/integrity/overview

[3] https://github.com/eu-digital-identity-wallet/eudi-doc-archi...

▲grishka 4 minutes ago | parent | prev | next [-]

Not really. For a while now, Android devices have had a hypervisor running in a "trusted execution environment", which is at a permission level above the actual Android kernel. This is where all the bullshit "security" and remote attestation code runs. You never get to unlock this, a regular bootloader unlock only lets you boot an unsigned kernel with the TEE knowing that you've done it and snitching on you. That's the whole reason SafetyNet is so hard to bypass these days. And of course, this is also the part that manages the bootloader lock state.

So at most, with a kernel exploit, you're going to get a temporary root, and you don't get to modify the system partition because the system will refuse to boot the next time because there are integrity checks.

▲tgma 26 minutes ago | parent | prev | next [-]

I am not as familiar with the Android security model as I am with iOS; how does OS kernel related to bootloader unlock on Android? Don't you need a bootloader exploit?

▲m132 16 minutes ago | parent [-]

Most devices won't let you unlock [1]--you're going to need a kernel or early boot code exploit to run your code with EL1+ privileges. For the minority that does, you usually follow the standard process [2].

[1] https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame...

[2] https://source.android.com/docs/core/architecture/bootloader...

▲throawayonthe 2 minutes ago | parent | prev [-]

which is the only kind of device graphene will ever support :p

▲pjmlp 6 minutes ago | parent | prev | next [-]

> Google is sabotaging their OEM partners by making a growing number of features and updates exclusive to Pixels.

Good luck on them, I will never buy a Pixel anyway.

▲mzhaase 19 minutes ago | parent | prev | next [-]

Google should not be allowed to control android.

▲trinsic2 an hour ago | parent | prev | next [-]

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.

▲jaypatelani an hour ago | parent | prev | next [-]

Best is we need Linux Phone

▲skeledrew 21 minutes ago | parent | next [-]

The ecosystem is far too tiny to make this practical for daily driving. Though also without people trying to use it for daily driving, the ecosystem won't move in any significant way. Classic chicken-egg problem.

▲ta8903 6 minutes ago | parent [-]

I have never used a linux phone but I doubt it, waydroid and PWAs would get you almost everything you need. But last I checked phones (or SOCs) capable of running linux are too old to run anything efficiently.

▲silon42 33 minutes ago | parent | prev [-]

I wish Linux phone OS supported Android style navigation.

▲pachouli-please 2 hours ago | parent | prev | next [-]

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.

▲microtonal an hour ago | parent | next [-]

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.

▲yjftsjthsd-h 33 minutes ago | parent [-]

> 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).

Something I've wondered: Graphene, AIUI, fixes this by sandboxing Google Play Services so it has no more access than any app. Given the huge obvious advantages, and that their code is open source, why do others not reuse that code to do the same? (Honestly, I'm a bit surprised that there aren't a bunch of ROMs using GOS as their upstream)

▲microtonal 19 minutes ago | parent [-]

That is really an excellent question and I don’t know the answer. Maybe they want to sell the ‘degoogled’ dream?

▲yjftsjthsd-h 6 minutes ago | parent [-]

I guess, but then I'd expect the same sandbox could run microG

▲N-Krause an hour ago | parent | prev [-]

High five, me too!

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?

▲microtonal an hour ago | parent [-]

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.

▲N-Krause 34 minutes ago | parent [-]

Would love to use GrapheneOS. But I won't buy a Pixel phone just to use Graphene and Graphene has issues beeing run on other OEMs so...

About microG: I don't run any Google apps, even though there are no real competitors for Google maps, so sometimes I have to resort to gmaps in the browser. But also getting rid of all paid apps from Google play is a real pain, often there isn't any alternative.

▲microtonal 26 minutes ago | parent [-]

If you have Play Integrity enabled in microG, then you are running something worse than Google apps, the obfuscated DroidGuard blobs in a privileged process. Yes, they can collect all kinds of data from a privileged process without sandboxing. Again. Seriously, don’t use /e/OS (if this is not enough of a reason, they are also way behind on security updates, no Android Security Bulletins alone do not say much).

I understand people don’t want to give money to Google by buying a Pixel (though Motorola’s alternative will be out soon). But buying a Fairphone is a weird choice then. It’s mostly a Chinese phone and not in the sense of “but nearly all phones are made in China”.

Fairphone is a phone that is developed by a Chinese ODM and the Fairphone software is maintained by the same Chinese ODM, including binary blobs. Even though they try to more development now, as far as I can see, Fairphone itself has mostly been a marketing/PR company.

—-

I fell for the Fairphone + /e/OS privacy/degoogling story and got that combo at some point. But then I started investigating the OS image and found out what kind of tire fire the whole thing is.

▲khriss 2 hours ago | parent | prev | next [-]

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'.

▲restlessforge an hour ago | parent | prev | next [-]

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?"

▲ACCount39 an hour ago | parent | prev | next [-]

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.

▲JumpCrisscross an hour ago | parent [-]

> Google's in a real hurry to lock down Android lately

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.

▲skeledrew an hour ago | parent | prev | next [-]

GMS needs to be ArtCrafted.

▲stop50 24 minutes ago | parent [-]

Ypu should look into microg

▲g-b-r an hour ago | parent | prev | next [-]

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.

▲DeathArrow an hour ago | parent | prev | next [-]

What happened to don't be evil?

▲mijowi 14 minutes ago | parent | next [-]

Not being evil is so 2018.

▲mook an hour ago | parent | prev [-]

Don't; be evil.

▲karel-3d an hour ago | parent | prev | next [-]

This is a business decision clearly.

Google is still running a business. A good business, actually.

https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/

▲leonidasrup 30 minutes ago | parent [-]

Google can do this because they have effectively a duopoly, with Apple, in the domain of operating systems for mobile phones.

We would have been in the same position for PCs if it was according to IBM. Only PC clones changed the situation.

https://en.wikipedia.org/wiki/Pc_clone

But monopoly, or oligopoly, is good for the business of Google. Look at the market value of Google, vs market value of IBM.

▲readthenotes1 an hour ago | parent | prev | next [-]

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.

▲tommyfalco 2 hours ago | parent | prev | next [-]

Utterly unsurprised

▲GuestFAUniverse 2 hours ago | parent | prev | next [-]

Fits with their opt-out AI training. Even in Germany.

Fuckers.

▲teravor 2 hours ago | parent | prev [-]

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.

▲mindslight 2 hours ago | parent [-]

Are we supposed to believe that the embrace in "embrace, extend, extinguish" is a good deed or what?