Google is pushing OEMs against GrapheneOS and bootloader unlocking
grapheneos.socialFuckers.
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'.
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.
You're still forced to run microG right, or is there a way around it, I am not aware of, if you want to run google apps or apps you previously paid for in the google play store?
Murena lies about being degoogled.
GrapheneOS solves this the correct way by providing support for sandboxes Google Play.
By the way, you should not run any Google apps on /e/OS because they give a bunch of Google apps higher privileges than the normal Android app sandbox.
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.
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.
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?
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).
It's a shame to hear about Fairphone's update cadence, but judging by the phones people usually buy and use, they seem to be fine with making this security trade-off. It's fine to show people how much more secure GrapheneOS is, but the baseline is random Xiaomi/Samsung phones, not Graphene.
Sure, Motorola will likely be a good non-Google choice. But their one phone with GrapheneOS support so far is very expensive. So it will again only be an option for a tiny segment of the market.
Fairphones don't keep up with crucial privacy and security updates. They lag 1-2 months behind bare minimum incomplete backports to older releases from the start. The delay gets much longer over time. They lag years behind on complete patches which require keeping up with major Android releases. Android doesn't even backport all of the High and Critical severity patches anymore. It hasn't backported any of the Low and Moderate severity patches for years. Many Moderate severity patches are quite important privacy holes.
They're providing bare minimum patches for the Android Security Bulletins which don't cover hundreds of severe vulnerabilities for the Linux kernel. Fairphone 5 and earlier have an end-of-life Linux kernel branch so those essentially aren't getting any of these. Google barely lists any in the Android Security Bulletins. Google want OEMs to ship LTS updates and move to new LTS branches but aren't requiring it or including it in the patch level. Android Security Bulletins are deliberately incredibly incomplete to make it easier for OEMs to give the appearance of keeping up with the privacy and security patches. It's a deliberate decision to make a lot of the Android ecosystem look a lot less bad than it is.
The vast majority of people buying those devices don't realize they're missing years of crucial privacy and security patches/protections including ending up with an end-of-life Linux kernel without updates. They're not making an informed decision because they're misled about what's being provided by Fairphone's marketing. Fairphone claims to provide great long term updates but doesn't actually do it.
/e/ makes the privacy and security situation on Fairphones much worse. It drastically rolls back both privacy and security compared to AOSP. It has many of their own invasive services and heavily uses Google services by default anyway. It downloads and runs Google Play code with privileged access by default anyway. /e/ and Murena repeatedly claim hardened devices mainly benefit criminals and pedophiles as part of trying to steer people away from GrapheneOS to their products. It isn't a legitimate privacy project or product.
We posted more information about that here with links to far more:
https://news.ycombinator.com/item?id=50578396
> But their one phone with GrapheneOS support so far is very expensive.
There will be other supported devices at lower price points. The first device is a flagship since it's the first one where they provide all of the essential security features and the required privacy/security updates.
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.
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)
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).
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?
I think they meant: why don't projects like /e/OS sandbox microG?
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.
/e/ is a very problematic fork of LineageOS very poor privacy and atrocious security. People would be far better off using standard LineageOS one of the better supported devices. An iPhone is far more private and drastically more secure than Murena products.
/e/ lacks crucial standard privacy and security patches. It fails to ship users standard Android, Chromium and Linux patches without enormous delays. It barely provides updates to the Linux kernel, drivers and firmware at all.
/e/ also doesn't provide important standard privacy or security protections. It lags years behind on providing the current generation protections and disables many of the most important ones. An operating system failing to protect against known privacy weaknesses does not have reasonable privacy. Lack of reasonable security also means any privacy protections can be easily bypassed.
/e/ includes their own privacy invasive services and sends user data to third parties. They spent years sending user speech data to OpenAI without obtaining consent and falsely claimed the data was anonymized when challenged over it. Despite how it's marketed, it includes many Google services with privileged integration into the OS. They have their own privacy invasive services including user tracking with unique identifiers in their update client.
/e/ and their for-profit company Murena have repeatedly pushed anti-privacy talking points from authoritarians claiming devices with strong privacy and security are for criminals and pedophiles. They've heavily targeted GrapheneOS this way making the outrageous claim that the userbase are mainly criminals and that it mainly benefits criminals. Here are 2 examples where Gaël Duval says this himself about privacy/security hardened devices in general, but there are many more examples:
https://x.com/GrapheneOS/status/2040887784253141142
https://clubic.com/actualite-604786-murena-e-os-interview.ht...
/e/ makes it far easier to remotely take over devices, violate user privacy from apps and bypass encryption to extract all the data from a device. These are exactly the kinds of devices authoritarians opposed to privacy and security want people to be using. These devices are much less private and drastically less secure than iPhones but are duping people into paying them for it with false marketing. They're regressing privacy and security instead of advancing it.
More information:
https://discuss.grapheneos.org/d/24134-devices-lacking-stand...
https://eylenburg.github.io/android_comparison.htm
https://codeberg.org/divested-mobile/divestos-website/raw/co...
https://community.e.foundation/t/voice-to-text-feature-using...
They already got once over trying to keep competing services out with their GMS agreements. Clearly, the only lesson they learned is "try harder."
I hope they get dismantled in court at least in EU for this bullshit. I'm sick and tired of vendors deciding what the users are and aren't allowed to do with their own devices.
They have two more months of zero Congressional oversight and two more years of a broken executive (but enraged Congress).
What I think they may be missing is the states.
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.
You could do this with the antigravity CLI or WebUI, an attested android device doesn't help.
"WebUI" is just the website interface Google serves the models over (AKA their version of "chatgpt.com") [1]. You say you're a fullstack dev, I'm assuming you mean Gemini's WebUI specifically and not the concept of a WebUI.
The reason I mentioned both is they work on MacOS, Windows, and Linux devices without any form of attestation, so you could easily pipe the antigravity output into a distillation tool, or install a custom userscript in the browser with the WebUI for the same effect.
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.
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.
The future of Big Computer is looking grim, and eventually we may have to make do with salvage, hobbyist parts, and grey market imports.
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.
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
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...
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.
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.
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.
I'm pretty sure Graphene nuked that bridge years ago.
I'm not sure why you'd think we have issues with LineageOS.
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.
What do you think GrapheneOS is? Arguably it's more of a fork than LineageOS and e/OS
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.
No, you can also switch to GNU-like Linux phones (Librem 5 and Pinephone).
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"
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.
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.
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.
That said, hope support trickles down the Motorola line-up pretty quickly.
I splurged on my last phone, spending the equivalent of about €100. (“Not splurging” would have around €70.) It’s perfectly good.
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.
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.
> Even GSI builds are explicitly frown upon.
I wouldn't say "frowned upon." GSIs cannot support all of the features and are also less private and secure.
Users can decide to make their own OS based on GrapheneOS but with lesser requirements as a tradeoff between wider compatibility and less privacy.
In fact, they are so free to do it, they really did it. There is no shortage of GSI-based forks of GrapheneOS lacking lots of hardware-exclusive features cheap phones more than likely aren't capable of supporting anyways.
> Google is sabotaging their OEM partners by making a growing number of features and updates exclusive to Pixels. At the same time, Google is trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking.
Also, corpos are akin to change their mind.
We don't know the procedure of bootloader unlocking on Signature 27. Will it be the same semi-automatic process as with Pixels? Or will users be required to create an account and wait? This question used to be asked many times, but GOS team keep silence.
>It should be similar than Pixels and perhaps without the internet requirement. Details will definitely be made available.
https://news.ycombinator.com/item?id=50385320 05/11/2026
>OEM unlocking toggle will work similarly to Pixels but might not require internet access as Pixels do.
https://shitter.thepixora.com/GrapheneOS/status/211018384724... 14/10/2026
>It will be easy to unlock and install without any hassle involved.
https://shitter.thepixora.com/GrapheneOS/status/211014519535... 13/10/2026
So, whom should I believe: the manufacturer or GOS team?
You seem to be missing the point. The point of GrapheneOS isn't supporting tons of devices, it's to build a private OS.
Other requirements, such as the 7 year OEM update mandate, don't just exist for security but also for longevity and avoiding e-waste, etc. Modern smartphone hardware is powerful enough to still be useful 7 years later, so customers should really be able to use their devices for that long. This means receiving full driver, HAL, and firmware updates from the manufacturer.
GSI builds may work for other Android forks that don't care about the kernel, but GrapheneOS makes significant changes to the kernel, such as enabling the hardware tag-based Kernel Address Sanitizer (KASAN/HWASan) (which isn't enabled by default, even on devices that have the hardware), zero-on-free, as well as enabling BTI and SCS. This only works with a custom kernel, so it's incompatible with GSIs.
Solution was to buy separate audio player. Not ideal to carry multiple devices, but it changes music consumption and force me to properly tag and build music archive.
At the time it came out, it wasn't cheap.
By cheap I mean, inexpensive at the time they come to the market
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.
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.
Google is scared to death of non-Google Android being a viable option for OEMs, and it's using the same playbook Microsoft did with PC manufacturers who considered selling PCs with anything other than Windows.
Google is still running a business. A good business, actually.
https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
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.
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.
Linux phones will have all of the issues with none of the benefits.
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.
"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"
Until Google decides otherwise.
I literally just went thru this hassle trying to locate a Pixel 10 Pro Fold on EBay that could be unlocked. I ended up returning at least one because someone tried to resell a device they hadn't already finished paying off , and the only way I could figure out that was the reason was dumping the ADB logs and combing thru them when the unlocking failed.
[1] https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame...
[2] https://source.android.com/docs/core/architecture/bootloader...
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...
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!
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)
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.
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).
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?
For Google I do believe they will manage to follow the new LLM security pace, as for Qualcomm and OEMs, I highly doubt so.
I support what people at GrapheneOS do but I don't appreciate their recent communication style.
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.
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 they needed to provide actual evidence in that case.
Good luck on them, I will never buy a Pixel anyway.
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.
For email, I first went with Proton mail but I found the UX and performance, not to my taste. Moved to Fastmail in 2024 and have been so so happy since.
Only wish more mail clients supported JMAP.
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.
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...
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.
That's inaccurate, I recently built an Android TV x86 system using the Lineage sources (a fork of AOSP), so it's definitely open. It also works extremely well, despite not including any Google dependencies.
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.
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.
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
People need to care. If people care, there will always be a way.
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".
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?
The struggle is potentially to do with how poorly designed Google Play are were maybe they don't act as a true generic provider for this feature (as understood by Android) but somehow take the long route of intercepting generic API access via its typical high privileges to actually provide the feature. If you think this is insane, there is anecdotal evidence to suggest design patterns this poor, in that Google Play are known to send less telemetry in GrapheneOS[0]... except there is little reason for them to collect much less data here since many things they could ever report on don't need high privileges to be accessed, at all.
[0] https://www.praveentechworld.com/research/degoogle-telemetry...
From 2 to 39 within five minutes only happens one way.
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.
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?
Well, I have another Android phone for bank and government apps but this phone doesn't leave the house.
What is the reader supposed to make of these "annnouncements" that lack any details
“An OS so secure/private that Google is trying to prevent you from using it”.
For a certain kind of person this will push them into trying it when they wouldn’t have before. Google should look into the Streisand Effect!
With F-Droid and friends, you can download and update pretty much any app you want (outside of the financial mafia s/w, for which you can still use the browser).
It seems like maybe it's time for GrapheneOS to switch support to a different phone h/w vendor, or at least add another vendor as an option.
Maybe a merger with LineageOS could help facilitate this.
It seems we're really at a cross roads for computing in general.
An example would be serving email as a small organization. The big players have been making it more artificially difficult for small servers for years now. The clear motive is to eliminate small email servers from the internet.
Getting a license from SnedGrid, MailChimp, or any one of many other bulk mail delivery services, allows sending hundreds of thousands of unsolicited email per day, all guaranteed to be delivered. Whereas a small mail server delivering a few hundred emails per day can have outgoing mail rejected for lack of "reputation". Its a clear effort towards monopoly dominance, it does nothing to fight spam.
Also in recent news have been stories about how the data center build out is leading to an effort to end home and local computing. Make every computer outside a data center a thin client, with all actual computing done by "big companies" in the cloudy cloud.
The lock down of mobile computing, i.e. cell phones, is just another component to this,
The general public has never given a shit about this, and is happy to be led by the pied piper down the rosy path.
The real question is will tech developers and other astute users care, and fight back?
Several other comments here talk about the lock down in embedded system development already underway. Will flashing an embedded processor soon require firmware be signed by a key issued by the silicon manufacturer?
What is a Hacker, much less one's news, once all compute is within a goggle or microsoft or meta data center?