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.
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.
Fork Android. Isn't that the only long-term way forward? Create a coalition with e/OS and LineageOS. Better start building something lasting now than waiting.
Even if this battle is won by law, they're going to continue to make maintaining spinoffs increasingly difficult. Pressure law makers to make sure not only duopoly apps are supported for e-governance software. Banking should follow.
In Google's eyes, open source was good for Android adoption. Now it's a nuisance at best.
Unless you can commit to fully support the full independently of Google, for ever, I am not sure just forking Android is a good idea.
The main point of Android right now are the apps that exist for it, the rest of it (graphics system, driver architecture, even system updates) is mediocre to shit level.
I think a much better option is to take mobile or even desktop Linux distro and make sure it has robust upstream support for the mobile hardware you care of. At the same time, work on Android emulation layer like Waydroid, to work as good as possible.
This way you have a long term sustainable hardware support model (sharing the effort with all other Linux distro communities) while still supporting the Android apps people care about.
This has been successfully by Valve for Windows games and apps on top of a regular Linux distro. And Jolla does the same for Android apps on Linux devices.
I wouldn't say "nuked" is the right word in this case. Considering how /e/OS's founder has attacked GrapheneOS, we wouldn't want to work with him, would we?
I'm not sure why you'd think we have issues with LineageOS.
I dont think theres ill will between LineageOS and GrapheneOS. They are just focusing on different areas (strict security guarantees vs wide device compatibility).
eOS markets itself as secure while being insecure and their CEO personally attacks GrapheneOS and GOS users (he said that only pedos and spies need good security) regularly. They also dont contribute back to generic AOSP development while GOS and LOS do.
"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"
If all apps support foldables by default why should I have to submit screenshots of my app running on a foldable? This is clearly authoritarian behavior: we make you do it because we can!
I support the notion that Android developers should put in some periodic effort to keep their apps in the Play Store, but the hoops they're now forcing you to jump through are getting downright ridiculous.
Yes, it's annoying, but opening the emulator and taking a few screenshots (or telling your agent to do so) isn't that hard. Google also isn't de-listing apps that don't provide screenshots, they're just not promoting them and you'll have to add screenshots with your next update.
Like GP said the basic requirement that applies to all apps is more or less just "the app fills the screen without black bars". For normal apps using Compose or Views that'll be the case unless you've done something very odd. This requirement is mainly about games and such that render directly with OpenGL/Vulkan and might assume a fixed aspect ratio.
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.
Google can be fined for its conduct, and for rather considerable sums. Winning a legal battle against a megacorp, and bringing in a few hundred million dollars to the state seems like a line in the attorney's resume that's worth an effort.
Have you ever known a prosecutor, they're particularly evil type of person, and very sociopathic. They are able to go sleep every night without a single bit of anxiety about all the humans they locked in cages that week like animals.
They are people who had a choice to use their expertise and education to make a ton of money and help people or destory lives and make far less money and they chose the latter. They are not your ally.
Its of course not as binary as I make it out to be, and people have to be prosecuted, but it takes a special type of person to dedicate their lives to doing it. Those types of people, atleast in America, are not really concerned with holding corporations accountable. They also are not concerned about making money for their state, or money generally. If they cared about money at all they wouldnt be a prosecutor.
To make things easier for folks could you cite what specific law you feel is likely being violated and how? It'd be much more effective if citizens can say X violates Y because Z rather than "you should look into <company> because <of a rant on some organization's forum>."
> 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.
This was the year for me, and developer verification was the hill. I started moving all my important emails, images, etc off Google. I can't do it all or all at once, but I made a new email account and started moving things.
I bought a new phone, GrapheneOS is on it now. I started moving things there one by one.
I got a home server and started self hosting my images and my docs.
You don't need to "do it all" just do some, it feels great.
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.
I wish they would lead with evidence and sources for the claims they're making.
Why would any OEM go on the record and put themselves in the crosshairs of Google? Why would GrapheneOS out them and burn their relationship with an OEM?
I think them just telling is the best they can do and what we have to work with.
Not sure why we shouldn't believe them. All of Google's behavior is pointing in this direction, Play Integrity, witholding QPR1 and QPR3, delaying the QPR2 source release... twice, GMS-based reCAPTCHA, removing Pixel device trees from AOSP, the list goes on and on.
I believe it, Google has already been found guilty of the exact sames actions against CyanogenMod and paid a fine in the EU about it.
In reality, the moat of both Google and Apple to keep the duopoly out of a third actor isn't that large (and even less so in the age of LLMs where anything can run on anything) so that's why they suppport artificial limitations on the hardware.
GrapheneOS is especially problematic for Google as normally they use "it's for security" as an argument, which is a bit hard to use when the OS is more secure than their own.
People likely share this information and ask not to mention their names or employers' names to avoid retaliation. What we need is proper tech journalism, but we don't have it, so GrapheneOS and others have to fight for themselves.
"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"
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.
But the original retail price is high, which results in lower relative demand, which entails a smaller number of used units in circulation, which works against the "everyone should be using Graphene" premise.
Our team has been pretty upfront from the beginning that the first device was going to be a flagship. There are plans to support more devices in the future, devices that I'd expect will be cheaper.
If you crunch the numbers, it's a far better device than the equivalent Pixel 11 for just a little more. I'll quote the X account:
> Signature 27 is $1599 vs. Pixel 11 Pro XL at $1299. Signature 27 has much better cameras, well beyond 2x higher GPU performance, at least 50% higher single threaded CPU performance, at least 70% higher multithreaded performance, much better radios and 37% higher battery capacity.
GrapheneOS doesn't make hardware, so it's not really up to us. If an OEM makes a device that has those hardware features and meets the requirements, then the device can be supported.
You are not getting a phone with any security at that price point. They do not have a secure element (only TrustZone), so they are vulnerable against side-channel attacks, etc.
OEMs for those phones are also not going to do or provide monthly firmware, driver, or kernel tree updates.
Pixel 9a regularly go for 350 Euro here and can be had second hand for 200-250 Euro or so. That counts as a cheap phone to me, especially for one that has a secure element, MTE, and monthly driver firmware updates. Of course, it’s all in the eye of the beholder.
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.
The thread says: "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."
What is the issue with FIDO2/Passkeys on Graphene or Android devices and why woudl it require Google services? Asking as someone who uses passkeys only via Proton Pass as a browser extension on multiple systems - why does it need deep system integration?
It's incredibly unfortunate Motorola's phones won't ship with GOS pre-installed. I feel now might be the last moment to push GOS into the mainstream. In a year or two it might be too late already...
We really need to be in a place where there's enough GOS users that any restrictions will cause problems for a significant portion of Android users. For now restrictions are imposed almost exclusively by banks, but I expect the situation to get much worse, judging by Google's actions
There's also the possibility of people caring, but not caring enough. There are already too many barriers to switching to a degoogled AOSP build, see people complaining about banking apps. They could switch banks, or just live without internet banking altogether, but they don't care enough.
If we want a future where people are free to choose their own OS, and I do, then we should work on keeping the switching process barrier-free instead of soothing ourselves with truisms like "there will always be a way", which amounts to telling people "you didn't sacrifice enough".
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.
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.
> require hardware-generated, cryptographic proof of the client running the latest, patched-up version of a locked-down operating system
Surprisingly, "latest, patched-up version" is not actually in that list (in relation to the core operating system (which was randomly compiled by the manufacturer once and depending on the device, may never be updated), google's applications have to be updated of course)
> the latest, patched-up version of a locked-down operating system
I don’t believe that: I’ve not seen them causing any trouble for people with devices years behind, and I don’t think they can really do anything about it for at least another decade, because almost everyone’s support cycles are ridiculous. Major OEMs continue to sell several-year-old versions of flagship phones with less than three years of support remaining, and budget phones more than a year out of support already!
If you also take into account the activity of AI companies which is creating a desperate need for anti-bot protections, I really can't see a future without this fracture.
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?
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].
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. Something similar to PS4 and PS5 jailbreaks.
Not sure if it was written with an LLM, but even if it is, it puts together all the relevant bits of information with links.
As far as I understand, you need a Boot ROM compromise, since it'd allow you to run a modified 'secure world' boot loader. A compromised Boot ROM is a double-edged sword though, since it can also be used by attackers/law enforcement to compromise your phone.
So in the end the viable path is not attacks of boot ROMs (they'd better be secure), but friendly OEMs that support alternative systems (like Motorola is doing with their Signature 27).
LLMs can hack into a device but they can't keep a secret. For garbage IoT-tier crap, Claude can absolutely get into your device that you own. But for devices where the vendor has the economic desire to actually maintain effective control over your device you need to be able to stockpile bugs to retain access even after a patch. This is the same sort of "theoretically impossible but plausibly doable" logic that gives us the CIA's NOBUS policy - i.e. "security vulnerabilities only we know about because it's a pain in the ass to find them".
What an LLM does to this is make NOBUS actually impossible, because anyone can spend $200/mo on a Claude pro plan and get actually novel vulnerabilities out of it. Great if you're worried about the CIA, terrible if you want to steal general purpose computing from a device vendor. What is actually happening is that bugs are getting leaked by prompt kiddies and patched before viable exploit chains can be made for them.
I mean, think about it: Google is one of the biggest users of AI. You don't think they aren't going to be burning tokens - which they have access to at cost - on finding vulns before you can exploit them?
> I mean, think about it: Google is one of the biggest users of AI. You don't think they aren't going to be burning tokens - which they have access to at cost - on finding vulns before you can exploit them?
For Google I do believe they will manage to follow the new LLM security pace, as for Qualcomm and OEMs, I highly doubt so.
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.
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.
Waydroid throws Android's security/sandboxing model under the bus. Also, will run into the same problems, like you cannot pass Play Integrity meeting strong/device integrity.
Linux phones will have all of the issues with none of the benefits.
I wouldn't say they have none of the benefits considering you can use them to do whatever you want because they are just normal Linux computers. If I could run Linux on modern phone hardware I wouldn't need a PC at all since you could just dock them into a display+keyboard.
You can run Linux on Android phones that have an SoC that supports non-protected VMs (like e.g. Pixel). Since Android 17 even Wayland apps are supported. Android also has a desktop mode nowadays, so you can plug in a monitor and have a desktop.
Sure, it is not perfect yet, but it's a much easier target than bringing up desktop Linux to the level of finesse (both UX and e.g. power management) of AOSP.
So, Android, in other words. That's Linux for cell phones built properly. The problem isn't Android here, but Google's extensions, or, more precisely, apps that use or enforce those extensions.
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.
This stuff is bleeding into the small embedded stuff I work on. And I can tell what they are trying to do.
The development path they are setting up is the unit you're debugging has a crypto units with a secret key that can be programmed once and isn't accessible. The bootloader uses that crypto engine to validate the firmware.
Right now you're the one that can set it if you want. But in the future the company you work for, the OS vendor, or the manufacturer will set the key and flash the bootloader.
When that happens you'll need a connection to their servers to sign the firmware you are developing. And when they terminate your access you won't be able to flash new firmware.
Either getting a lot of flagging (Google employees?) or it set off the voting ring detector (e.g. getting visited from a link someone posted somewhere).
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.
> 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)
Though I am not sure if they ever got sandboxing working with SafetyNet/Play Integrity (the thread and linked issue seems to indicate that they did not want to support it).
What's the point? If you look at the big picture, microG doesn't offer much in terms of privacy (from what I understand it is (has?) been leaky with things like location, so that's a privacy flaw), but is way less secure and offers far worse app compatibility.
It also doesn't make sense to use microG if you look at the big picture because it's only there for apps that rely on Google Play Services because they contain Google libraries.
Why would GrapheneOS, a project with limited resources, officially support microG when there's a far better option?
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.
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.
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 do 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.
You either give money to Google, or to China (or to Sony, but they don't seem to want my money). You just have to pick the lesser evil, and I don't think picking China is an obviously worse choice.
Not picking Google means you can't use GrapheneOS, and at that point what's the better choice? Proprietary vendor firmware? /e/OS? LineageOS? Random image from XDA Developers?
This point is soon going to be moot, since Motorola will support GrapheneOS on select models.
By they way, my point was not about giving money to China, but running Chinese software. The same is partially going to be true if you run /e/OS, because they reuse the same driver/firmware trees, etc.
Besides that Fairphones have terrible security. No Secure Enclave (which eg the iPhone had since the 5s!). They only update drivers and driver firmware for their latest model every 6-12 months or so (older models have ancient, unpatched kernels and drivers).
These things matter, see e.g.: https://calif.io/research/oempocalypse or the latest Cellebrite report, where pretty much every Android phone can be read out, most even before BFU, except GrapheneOS.
So I was pointing out that you are trading not giving money to Google for far less security and thus privacy (only one exfil away from losing a lot of very personal data).
In a thread about GrapheneOS, microG isn't a really good suggestion. GrapheneOS's compatibility layer allowing users to install Google Play and Google Play Services without privileged permissions is more private, secure, and provides better app compatibility.
Privacy: microG's leaks and failure to implement other checks and there's arguably no real gain in privacy since the Sandboxed Google Play approach means Google Play Services and Store don't have privileged permissions.
Security: microG needs privileged permissions to work properly and can also download Google binaries and runs them in that privileged context, depending on settings
App compatibility: It's an incomplete reimplementation. Even microG's GitHub says as much.
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'.
Completely unrelated but in my country there was an unhinged politician who created like fifteen parties throughout his career and somebody made a meme listing all of them and going like "first they laugh at you, then they laugh at you, then they laugh at you, then they laugh at you...". Funnily, once the wider far-right political movement got rid of him, they actually gained traction.
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?"
Is there any evidence hidden in that thread about this supposed push, or is it all just marketing by claiming victimhood? (Effective marketing, clearly, so can't blame them for engaging in it).
There is simply no way Google is "specifically targeting GrapheneOS". It's the mad men elevator scene; nobody at Google with any kind of decision making power on phone strategy spends a minute a year thinking about GrapheneOS.
What evidence are you looking for? If the project started sharing screenshots of private conversations, do you think OEMs will continue to share this kind of information?
If you're suggesting Google might have a backdoor in those chips, then that really doesn't make sense. Why would they shoot themselves in the foot? If they had done such a thing, many people would know and would have to keep it secret. If the secret got out or if anyone found the backdoor, then game over for Google's good security reputation. Google doesn't need a backdoor anyway because Google Play Services on OSes licensing GMS has crazy privileges anyway. Of course that's not the case on GrapheneOS, though.
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.
I bet it is due to AI. There is a market for distilation of models, and just imagine you could freely install a crowd-sourced tool that would send your AI questions/responses to a competitor for distilation of frontier models.
Right now any frontier provider must make sure no one creates (public) databases of prompts/answers as it is a death thread to the ones training the models.
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.
graphene is doing a hail mary attempt to ROM there way into possition as a major player with there worst of both worlds 'appledroid', and need to put some hardware skin in the game while building a real os.
this can be done!, and there are several earnest efforts happening now, but graphene is a dead end by bieng built entirely on guggle ware.
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.
Feeding the beast.... until it bites you again and again. Google is akin to those pampered cats that pawslap their owners when they sleep, because why not. As an added plus The Pixel looks like a lobotomized industrian designer's creation.
Google thanks GrapheneOS for years of helping them sell Pixels to idiots who mistakenly believe Android is open or that buying from Google leads to privacy.
As per usual, once again, Google's fake openness has fooled people into wasting developer resources on doomed forks instead of developing a real competitor.
I find your description of our users highly inappropriate.
Pixels have been the only devices that meet the project's requirements. Some of the requirements are security requirements, which are necessary for strong privacy.
And you seem to be confused about what the thread was about. What was said doesn't mean that our users' Pixels are suddenly less private or secure.
GrapheneOS is actually in a very good place right now. Sharing these updates early benefits us, our users, and the public. There was already a conversation going about developer verification, which was totally overblown, but this is something else entirely.
This is what we got when we openly let Google kill off the developer-focused Nexus line for the consumer-oriented Pixel line.
We were never the Pixel customer. We were only Nexus customers, only so far as Google handed us shiny toys and let us play around until they decided they wanted to wall it off at Pixel to hand it over to the normies.
Google thanks GrapheneOS for years of helping them sell Pixels to idiots who mistakenly believe Android is open
Until little over a year ago, Pixel device trees were part of AOSP. Google were releasing sources to AOSP on an ongoing basis. It is only over the last 1-1.5 year that Google really started closing down Pixel and AOSP.
The moment this started happening, GrapheneOS stated trying to find other OEMs to work with.
The only thing is I think GrapheneOS have been actively looking for hardware partners even before this. They haven't had major successes until recently though.
Google has been bullying OEMs who dared to ship forks or ROMs for as long as Android has existed. The strategy has changed in the last year, because the MADA was ruled as illegal, taking most of the "secret agreement with OEMs" strategy off the table.
Android has never been open. There are just people who knew about the MADA ten years ago, and people who are finally finding out now.
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.
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
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.
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.
Fork Android. Isn't that the only long-term way forward? Create a coalition with e/OS and LineageOS. Better start building something lasting now than waiting.
Even if this battle is won by law, they're going to continue to make maintaining spinoffs increasingly difficult. Pressure law makers to make sure not only duopoly apps are supported for e-governance software. Banking should follow.
In Google's eyes, open source was good for Android adoption. Now it's a nuisance at best.
Unless you can commit to fully support the full independently of Google, for ever, I am not sure just forking Android is a good idea.
The main point of Android right now are the apps that exist for it, the rest of it (graphics system, driver architecture, even system updates) is mediocre to shit level.
I think a much better option is to take mobile or even desktop Linux distro and make sure it has robust upstream support for the mobile hardware you care of. At the same time, work on Android emulation layer like Waydroid, to work as good as possible.
This way you have a long term sustainable hardware support model (sharing the effort with all other Linux distro communities) while still supporting the Android apps people care about.
This has been successfully by Valve for Windows games and apps on top of a regular Linux distro. And Jolla does the same for Android apps on Linux devices.
> Create a coalition with e/OS and LineageOS.
I'm pretty sure Graphene nuked that bridge years ago.
I wouldn't say "nuked" is the right word in this case. Considering how /e/OS's founder has attacked GrapheneOS, we wouldn't want to work with him, would we?
I'm not sure why you'd think we have issues with LineageOS.
I dont think theres ill will between LineageOS and GrapheneOS. They are just focusing on different areas (strict security guarantees vs wide device compatibility).
eOS markets itself as secure while being insecure and their CEO personally attacks GrapheneOS and GOS users (he said that only pedos and spies need good security) regularly. They also dont contribute back to generic AOSP development while GOS and LOS do.
>Fork Android
What do you think GrapheneOS is? Arguably it's more of a fork than LineageOS and e/OS
Why would simulators not be allowed? How would they even know?
"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"
If all apps support foldables by default why should I have to submit screenshots of my app running on a foldable? This is clearly authoritarian behavior: we make you do it because we can!
I support the notion that Android developers should put in some periodic effort to keep their apps in the Play Store, but the hoops they're now forcing you to jump through are getting downright ridiculous.
Yes, it's annoying, but opening the emulator and taking a few screenshots (or telling your agent to do so) isn't that hard. Google also isn't de-listing apps that don't provide screenshots, they're just not promoting them and you'll have to add screenshots with your next update.
Like GP said the basic requirement that applies to all apps is more or less just "the app fills the screen without black bars". For normal apps using Compose or Views that'll be the case unless you've done something very odd. This requirement is mainly about games and such that render directly with OpenGL/Vulkan and might assume a fixed aspect ratio.
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.
Google can be fined for its conduct, and for rather considerable sums. Winning a legal battle against a megacorp, and bringing in a few hundred million dollars to the state seems like a line in the attorney's resume that's worth an effort.
Have you ever known a prosecutor, they're particularly evil type of person, and very sociopathic. They are able to go sleep every night without a single bit of anxiety about all the humans they locked in cages that week like animals.
They are people who had a choice to use their expertise and education to make a ton of money and help people or destory lives and make far less money and they chose the latter. They are not your ally.
Its of course not as binary as I make it out to be, and people have to be prosecuted, but it takes a special type of person to dedicate their lives to doing it. Those types of people, atleast in America, are not really concerned with holding corporations accountable. They also are not concerned about making money for their state, or money generally. If they cared about money at all they wouldnt be a prosecutor.
To make things easier for folks could you cite what specific law you feel is likely being violated and how? It'd be much more effective if citizens can say X violates Y because Z rather than "you should look into <company> because <of a rant on some organization's forum>."
Its also something people should be bothering Ro Khanna about, given the area he represents
> 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
Too busy bribing voters
This was the year for me, and developer verification was the hill. I started moving all my important emails, images, etc off Google. I can't do it all or all at once, but I made a new email account and started moving things.
I bought a new phone, GrapheneOS is on it now. I started moving things there one by one.
I got a home server and started self hosting my images and my docs.
You don't need to "do it all" just do some, it feels great.
May I ask where you moved your email to? I'm in a similar position.
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.
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.
I wish they would lead with evidence and sources for the claims they're making.
Why would any OEM go on the record and put themselves in the crosshairs of Google? Why would GrapheneOS out them and burn their relationship with an OEM?
I think them just telling is the best they can do and what we have to work with.
Not sure why we shouldn't believe them. All of Google's behavior is pointing in this direction, Play Integrity, witholding QPR1 and QPR3, delaying the QPR2 source release... twice, GMS-based reCAPTCHA, removing Pixel device trees from AOSP, the list goes on and on.
I believe it, Google has already been found guilty of the exact sames actions against CyanogenMod and paid a fine in the EU about it.
In reality, the moat of both Google and Apple to keep the duopoly out of a third actor isn't that large (and even less so in the age of LLMs where anything can run on anything) so that's why they suppport artificial limitations on the hardware.
GrapheneOS is especially problematic for Google as normally they use "it's for security" as an argument, which is a bit hard to use when the OS is more secure than their own.
> I believe it, Google has already been found guilty of the exact sames actions against CyanogenMod and paid a fine in the EU about it.
I believe they needed to provide actual evidence in that case.
People likely share this information and ask not to mention their names or employers' names to avoid retaliation. What we need is proper tech journalism, but we don't have it, so GrapheneOS and others have to fight for themselves.
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"
> Pixels allow boot loader unlocking
Until Google decides otherwise.
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.
Same. Motorola apparently has some official GrapheneOs supported phones coming in 2027.
People DeGoogle-ing has obviously scared Google I think.
The last Google thing in my life is my pixel and it will be the last.
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..).
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.
No Titan chip though right ?
But the Signature 27 does have a secure element (from NXP). It's one of the requirements for supporting GrapheneOS.
https://grapheneos.social/@GrapheneOS/117570889454162312
Google should not be allowed to control android.
Everyone should run GrapheneOS.
We need cheap phones supporting it
You don't have to buy a new phone. A used Pixel can be pretty cheap
The older the phone, the sooner it can no longer receive updates even if the hardware does magically last forever.
Pixels have 6 years of support. You can get a used Pixel from 1-2 generations ago and still use it for longer than many new non-pixel phones.
But the original retail price is high, which results in lower relative demand, which entails a smaller number of used units in circulation, which works against the "everyone should be using Graphene" premise.
Our team has been pretty upfront from the beginning that the first device was going to be a flagship. There are plans to support more devices in the future, devices that I'd expect will be cheaper.
If you crunch the numbers, it's a far better device than the equivalent Pixel 11 for just a little more. I'll quote the X account:
> Signature 27 is $1599 vs. Pixel 11 Pro XL at $1299. Signature 27 has much better cameras, well beyond 2x higher GPU performance, at least 50% higher single threaded CPU performance, at least 70% higher multithreaded performance, much better radios and 37% higher battery capacity.
But I wasn't saying the pixel was more expensive than it's worth, nor did I mention the Moto...
No it doesn't. If it were the norm the situation would be quite different.
Not just cheap. Replaceable batteries, audio jack, SD card; there are plenty of reasons to want other hardware.
GrapheneOS doesn't make hardware, so it's not really up to us. If an OEM makes a device that has those hardware features and meets the requirements, then the device can be supported.
GrapheneOS continuously refuse to lower their requirements which would allow to support more devices. Even GSI builds are explicitly frown upon.
Cheap phones like the Pixel 9a or 10a?
That said, hope support trickles down the Motorola line-up pretty quickly.
Are you calling the Pixel 9a and 10a cheap? Even refurbished, the 9a is twice the price of plenty of perfectly good new phones.
The Pixel 10a is 410€ brand new on Amazon - how cheap do you think it should be?
I’m not saying how cheap that specific phone should be, but rather that it’s not in the “cheap” category.
I splurged on my last phone, spending the equivalent of about €100. (“Not splurging” would have around €70.) It’s perfectly good.
You are not getting a phone with any security at that price point. They do not have a secure element (only TrustZone), so they are vulnerable against side-channel attacks, etc.
OEMs for those phones are also not going to do or provide monthly firmware, driver, or kernel tree updates.
Pixel 9a regularly go for 350 Euro here and can be had second hand for 200-250 Euro or so. That counts as a cheap phone to me, especially for one that has a secure element, MTE, and monthly driver firmware updates. Of course, it’s all in the eye of the beholder.
Moto Gs can go for $200 (direct from Motorola)
Or Lineage, Calyx or eOS. Let's not create another monoculture.
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.
The thread says: "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."
What is the issue with FIDO2/Passkeys on Graphene or Android devices and why woudl it require Google services? Asking as someone who uses passkeys only via Proton Pass as a browser extension on multiple systems - why does it need deep system integration?
It's incredibly unfortunate Motorola's phones won't ship with GOS pre-installed. I feel now might be the last moment to push GOS into the mainstream. In a year or two it might be too late already...
We really need to be in a place where there's enough GOS users that any restrictions will cause problems for a significant portion of Android users. For now restrictions are imposed almost exclusively by banks, but I expect the situation to get much worse, judging by Google's actions
> Push into mainstream, might be too late already...
People need to care. If people care, there will always be a way.
There's also the possibility of people caring, but not caring enough. There are already too many barriers to switching to a degoogled AOSP build, see people complaining about banking apps. They could switch banks, or just live without internet banking altogether, but they don't care enough.
If we want a future where people are free to choose their own OS, and I do, then we should work on keeping the switching process barrier-free instead of soothing ourselves with truisms like "there will always be a way", which amounts to telling people "you didn't sacrifice enough".
This just reinforces what many have been saying for a while. We need at least a third option [1].
[1] https://blog.ovalerio.net/archives/3359
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.
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...
> require hardware-generated, cryptographic proof of the client running the latest, patched-up version of a locked-down operating system
Surprisingly, "latest, patched-up version" is not actually in that list (in relation to the core operating system (which was randomly compiled by the manufacturer once and depending on the device, may never be updated), google's applications have to be updated of course)
> the latest, patched-up version of a locked-down operating system
I don’t believe that: I’ve not seen them causing any trouble for people with devices years behind, and I don’t think they can really do anything about it for at least another decade, because almost everyone’s support cycles are ridiculous. Major OEMs continue to sell several-year-old versions of flagship phones with less than three years of support remaining, and budget phones more than a year out of support already!
If you also take into account the activity of AI companies which is creating a desperate need for anti-bot protections, I really can't see a future without this fracture.
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?
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...
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. Something similar to PS4 and PS5 jailbreaks.
There was recently a good post about this:
https://osservatorionessuno.org/blog/2026/05/demystifying-ph...
Not sure if it was written with an LLM, but even if it is, it puts together all the relevant bits of information with links.
As far as I understand, you need a Boot ROM compromise, since it'd allow you to run a modified 'secure world' boot loader. A compromised Boot ROM is a double-edged sword though, since it can also be used by attackers/law enforcement to compromise your phone.
So in the end the viable path is not attacks of boot ROMs (they'd better be secure), but friendly OEMs that support alternative systems (like Motorola is doing with their Signature 27).
LLMs can hack into a device but they can't keep a secret. For garbage IoT-tier crap, Claude can absolutely get into your device that you own. But for devices where the vendor has the economic desire to actually maintain effective control over your device you need to be able to stockpile bugs to retain access even after a patch. This is the same sort of "theoretically impossible but plausibly doable" logic that gives us the CIA's NOBUS policy - i.e. "security vulnerabilities only we know about because it's a pain in the ass to find them".
What an LLM does to this is make NOBUS actually impossible, because anyone can spend $200/mo on a Claude pro plan and get actually novel vulnerabilities out of it. Great if you're worried about the CIA, terrible if you want to steal general purpose computing from a device vendor. What is actually happening is that bugs are getting leaked by prompt kiddies and patched before viable exploit chains can be made for them.
I mean, think about it: Google is one of the biggest users of AI. You don't think they aren't going to be burning tokens - which they have access to at cost - on finding vulns before you can exploit them?
> I mean, think about it: Google is one of the biggest users of AI. You don't think they aren't going to be burning tokens - which they have access to at cost - on finding vulns before you can exploit them?
For Google I do believe they will manage to follow the new LLM security pace, as for Qualcomm and OEMs, I highly doubt so.
which is the only kind of device graphene will ever support :p
Best is we need Linux Phone
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.
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.
Waydroid throws Android's security/sandboxing model under the bus. Also, will run into the same problems, like you cannot pass Play Integrity meeting strong/device integrity.
Linux phones will have all of the issues with none of the benefits.
I wouldn't say they have none of the benefits considering you can use them to do whatever you want because they are just normal Linux computers. If I could run Linux on modern phone hardware I wouldn't need a PC at all since you could just dock them into a display+keyboard.
You can run Linux on Android phones that have an SoC that supports non-protected VMs (like e.g. Pixel). Since Android 17 even Wayland apps are supported. Android also has a desktop mode nowadays, so you can plug in a monitor and have a desktop.
Sure, it is not perfect yet, but it's a much easier target than bringing up desktop Linux to the level of finesse (both UX and e.g. power management) of AOSP.
I wish Linux phone OS supported Android style navigation.
So, Android, in other words. That's Linux for cell phones built properly. The problem isn't Android here, but Google's extensions, or, more precisely, apps that use or enforce those extensions.
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.
This stuff is bleeding into the small embedded stuff I work on. And I can tell what they are trying to do.
The development path they are setting up is the unit you're debugging has a crypto units with a secret key that can be programmed once and isn't accessible. The bootloader uses that crypto engine to validate the firmware.
Right now you're the one that can set it if you want. But in the future the company you work for, the OS vendor, or the manufacturer will set the key and flash the bootloader.
When that happens you'll need a connection to their servers to sign the firmware you are developing. And when they terminate your access you won't be able to flash new firmware.
I guess we're going to need the EU to support right of choice on devices.
The EU will probably not support anything they cannot surveil.
This post ranked #2 about an hour ago. Now it's #45. How does that happen?
Either getting a lot of flagging (Google employees?) or it set off the voting ring detector (e.g. getting visited from a link someone posted somewhere).
https://hnrankings.com/50570479/
From 2 to 39 within five minutes only happens one way.
probably because its nothing burger news
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.
> 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)
That is really an excellent question and I don’t know the answer. Maybe they want to sell the ‘degoogled’ dream?
I guess, but then I'd expect the same sandbox could run microG
Yes, DivestOS had sandboxed microG:
https://discuss.privacyguides.net/t/divestos-unprivileged-mi...
Though I am not sure if they ever got sandboxing working with SafetyNet/Play Integrity (the thread and linked issue seems to indicate that they did not want to support it).
What's the point? If you look at the big picture, microG doesn't offer much in terms of privacy (from what I understand it is (has?) been leaky with things like location, so that's a privacy flaw), but is way less secure and offers far worse app compatibility.
It also doesn't make sense to use microG if you look at the big picture because it's only there for apps that rely on Google Play Services because they contain Google libraries.
Why would GrapheneOS, a project with limited resources, officially support microG when there's a far better option?
Why would GrapheneOS, a project with limited resources, officially support microG when there's a far better option?
I think they meant: why don't projects like /e/OS sandbox microG?
Oh! You might be right. I'm too used to people using the wrong wording in the community, so I might have assumed the wrong thing.
For the same reason Mozilla took an extra decade or whatever to do single-site process isolation - their users don’t seem to mind it missing.
More charitably: other stuff is deemed more important.
Like supporting phones that retailed for $49 in 2012.
Fine, awesome even, but: wildly different project core competencies and incentive structure.
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?
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.
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.
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 do 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.
You either give money to Google, or to China (or to Sony, but they don't seem to want my money). You just have to pick the lesser evil, and I don't think picking China is an obviously worse choice.
Not picking Google means you can't use GrapheneOS, and at that point what's the better choice? Proprietary vendor firmware? /e/OS? LineageOS? Random image from XDA Developers?
This point is soon going to be moot, since Motorola will support GrapheneOS on select models.
By they way, my point was not about giving money to China, but running Chinese software. The same is partially going to be true if you run /e/OS, because they reuse the same driver/firmware trees, etc.
Besides that Fairphones have terrible security. No Secure Enclave (which eg the iPhone had since the 5s!). They only update drivers and driver firmware for their latest model every 6-12 months or so (older models have ancient, unpatched kernels and drivers).
These things matter, see e.g.: https://calif.io/research/oempocalypse or the latest Cellebrite report, where pretty much every Android phone can be read out, most even before BFU, except GrapheneOS.
So I was pointing out that you are trading not giving money to Google for far less security and thus privacy (only one exfil away from losing a lot of very personal data).
> 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.
GMS needs to be ArtCrafted.
Ypu should look into microg
In a thread about GrapheneOS, microG isn't a really good suggestion. GrapheneOS's compatibility layer allowing users to install Google Play and Google Play Services without privileged permissions is more private, secure, and provides better app compatibility.
Privacy: microG's leaks and failure to implement other checks and there's arguably no real gain in privacy since the Sandboxed Google Play approach means Google Play Services and Store don't have privileged permissions.
Security: microG needs privileged permissions to work properly and can also download Google binaries and runs them in that privileged context, depending on settings
App compatibility: It's an incomplete reimplementation. Even microG's GitHub says as much.
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'.
Completely unrelated but in my country there was an unhinged politician who created like fifteen parties throughout his career and somebody made a meme listing all of them and going like "first they laugh at you, then they laugh at you, then they laugh at you, then they laugh at you...". Funnily, once the wider far-right political movement got rid of him, they actually gained traction.
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?"
Is there any evidence hidden in that thread about this supposed push, or is it all just marketing by claiming victimhood? (Effective marketing, clearly, so can't blame them for engaging in it).
There is simply no way Google is "specifically targeting GrapheneOS". It's the mad men elevator scene; nobody at Google with any kind of decision making power on phone strategy spends a minute a year thinking about GrapheneOS.
What evidence are you looking for? If the project started sharing screenshots of private conversations, do you think OEMs will continue to share this kind of information?
Hopefully those Titan chips are actually secure and Graphene looking into all these things more doesn't discover something else.....
If you're suggesting Google might have a backdoor in those chips, then that really doesn't make sense. Why would they shoot themselves in the foot? If they had done such a thing, many people would know and would have to keep it secret. If the secret got out or if anyone found the backdoor, then game over for Google's good security reputation. Google doesn't need a backdoor anyway because Google Play Services on OSes licensing GMS has crazy privileges anyway. Of course that's not the case on GrapheneOS, though.
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.
I bet it is due to AI. There is a market for distilation of models, and just imagine you could freely install a crowd-sourced tool that would send your AI questions/responses to a competitor for distilation of frontier models.
Right now any frontier provider must make sure no one creates (public) databases of prompts/answers as it is a death thread to the ones training the models.
This doesn't make any sense though...
You could do this with the antigravity CLI or WebUI, an attested android device doesn't help.
Can you elaborate? I never heard of antigravity, and WebUI.
> 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.
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.
yeah, I meant four fifths...
What happened to don't be evil?
Don't; be evil.
Not being evil is so 2018.
It's really hard for me to take the GrapheneOS folk seriously considering how rude they are to literally everyone.
graphene is doing a hail mary attempt to ROM there way into possition as a major player with there worst of both worlds 'appledroid', and need to put some hardware skin in the game while building a real os. this can be done!, and there are several earnest efforts happening now, but graphene is a dead end by bieng built entirely on guggle ware.
> graphene is a dead end by bieng built entirely on guggle ware
GrapheneOS has an official partnership with Motorola now, so Google hardware won't be required for the new phones they're supporting
Or you mean it's a dead end for building on the AOSP software itself?
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.
Feeding the beast.... until it bites you again and again. Google is akin to those pampered cats that pawslap their owners when they sleep, because why not. As an added plus The Pixel looks like a lobotomized industrian designer's creation.
Google thanks GrapheneOS for years of helping them sell Pixels to idiots who mistakenly believe Android is open or that buying from Google leads to privacy.
As per usual, once again, Google's fake openness has fooled people into wasting developer resources on doomed forks instead of developing a real competitor.
> idiots
I find your description of our users highly inappropriate.
Pixels have been the only devices that meet the project's requirements. Some of the requirements are security requirements, which are necessary for strong privacy.
And you seem to be confused about what the thread was about. What was said doesn't mean that our users' Pixels are suddenly less private or secure.
GrapheneOS is actually in a very good place right now. Sharing these updates early benefits us, our users, and the public. There was already a conversation going about developer verification, which was totally overblown, but this is something else entirely.
This is what we got when we openly let Google kill off the developer-focused Nexus line for the consumer-oriented Pixel line.
We were never the Pixel customer. We were only Nexus customers, only so far as Google handed us shiny toys and let us play around until they decided they wanted to wall it off at Pixel to hand it over to the normies.
Google thanks GrapheneOS for years of helping them sell Pixels to idiots who mistakenly believe Android is open
Until little over a year ago, Pixel device trees were part of AOSP. Google were releasing sources to AOSP on an ongoing basis. It is only over the last 1-1.5 year that Google really started closing down Pixel and AOSP.
The moment this started happening, GrapheneOS stated trying to find other OEMs to work with.
Weird to blame GrapheneOS here...
The only thing is I think GrapheneOS have been actively looking for hardware partners even before this. They haven't had major successes until recently though.
Google has been bullying OEMs who dared to ship forks or ROMs for as long as Android has existed. The strategy has changed in the last year, because the MADA was ruled as illegal, taking most of the "secret agreement with OEMs" strategy off the table.
Android has never been open. There are just people who knew about the MADA ten years ago, and people who are finally finding out now.
Ah, I was wondering why Google seemed to be accelerating.
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/
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.
well it was bad for IBM but Microsoft had a monopoly. Same dynamics here.
Google gives Android for "free" but makes money on the services around it. Take away the services and they have no reason to develop Android.
Fits with their opt-out AI training. Even in Germany.
Fuckers.
Utterly unsurprised
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.
Are we supposed to believe that the embrace in "embrace, extend, extinguish" is a good deed or what?