HNHacker News
TopNewBestAskShowJobs

HybridStatAnim8

257 karma · joined November 28, 2025

submissionscomments
HybridStatAnim8··on Volkswagen started blocking GrapheneOS users
Note that Fairphone does not provide software updates for anywhere near as long as they claim, and using a modern device with 7 years of support, such as a pixel or iphone, will be far better in the long term. Fairphone is basically e-waste out of the box.
HybridStatAnim8··on Volkswagen started blocking GrapheneOS users
The legal definition of the OS does not matter at all when considering the difference between failing to support something, and using a tool that explicitly stops something from working that otherwise works without issue. Play integrity is a tool which does not base any of its certification decisions in privacy or security, rather leverages it for anticompetitive reasons. This is known and trivially verifiable.

I do know what these terms mean in a legal context. I am claiming that play integrity is an anticompetitive and monopolistic tool, of which VW decided to use. I am not claiming VW is a monopoly. What you are claiming is their right to do, is not their right at all, and is illegal.

HybridStatAnim8··on GrapheneOS has been ported to Android 17
GrapheneOS is designed for everyone, including average users. It does not require a high threat model, and the features it provides are not only useful to people with high threat models.

Contrary to popular belief, exploitation of vulnerable devices is a lot more common, and a lot easier than people pretend it is. You dont need to be targeted either, mass exploitation can, has, and will occur.

LineageOS does not have privacy, security, or usability comparable to GrapheneOS. LineageOS is missing many important features and falls behind android updates. GrapheneOS will be the far better choice in all 3 of these categories.

The features GrapheneOS provides, such as the network permission, cannot be replicated with a firewall app. The network permission properly covers all forms of network access for an app, where firewall apps do not have the ability to prevent all network communication. They are leaky.

The AGNSS servers and proxies are very, very tiny aspects of what GrapheneOS provides. You would be losing out on many more high impact privacy, security, and usability features.

Root access and an unlocked bootloader are insecure, even for low threat models. These devices are vulnerable and should not be used for any sensitive data.

LineageOS is not the better choice for any privacy, security, or usability usecases relative to GrapheneOS.

HybridStatAnim8··on Volkswagen started blocking GrapheneOS users
GrapheneOS requires a locked bootloader and supports using deveice attestation via the generic attestation functionality in the Android Open Source Project.

Play integrity is an anticompetitive tool that ignores this, and artificially limits itself on GrapheneOS. It is not due to any incompatibility.

HybridStatAnim8··on Volkswagen started blocking GrapheneOS users
GrapheneOS is based on the Android Open Source Project and retains near perfect android app compatibility. It cannot call itself android for legal reasons, but the legal definition does not affect its app compatibility.

Tools such as play integrity are illegal. Using anticompetitive and monopolistic tools is not the right of application developers.

HybridStatAnim8··on Volkswagen started blocking GrapheneOS users
The basis of your argument, that users want these developers to support another platform, does not make sense, because GrapheneOS does not require apps add explicit support for it. GrapheneOS has 99% android app compatibility.

The issue is not that this application isnt tested on GOS, its that an anticompetitive, illegal tool is being used to ban non-certified OSs when these apps would work perfectly otherwise.

HybridStatAnim8··on Volkswagen started blocking GrapheneOS users
GrapheneOS maintains 99% android app compatibility. It does not require any additional funding or expenses to support GrapheneOS, and is actually more expensive to add these anticompetitive tools responsible for banning GrapheneOS.

GrapheneOS is also not responsible for bugs in this app. Any bug reports coming from GOS are likely to be from the hardening toggles, which uncover bugs in the app. This is the apps fault, and these bugs still exist on other OSs. It should be resolved for the benefit of all users.

HybridStatAnim8··on Volkswagen started blocking GrapheneOS users
The funny thing is, nothing needs to be done to support GOS. GOS has 99% android app compatibility. The issue isnt that GOS requires changes in the app to support it, rather, the tools they are using explicitly ban non-certified OSs.

Dont let their boilerplate responses fool you, tools like play integrity only serve to push anticompetitive practices. The claims about not being able to support GOS are nonsense, and all they did was break existing support.

HybridStatAnim8··on Volkswagen started blocking GrapheneOS users
GrapheneOS has an official partnership with a large OEM (Motorola), has near perfect app compatibility, is constantly improving upon user experience, and has been well known and regarded in the privsec community and by many trusted security experts. It appears to be gaining more mainstream awareness as a result.

Oh, and Android 17 has been released so there is hype for that.

HybridStatAnim8··on Volkswagen started blocking GrapheneOS users
It is far more likely that it is due to scams and grifts that pretend to be GrapheneOS, associated with GrapheneOS, or based on GrapheneOS, rather than GrapheneOS itself. Criminals tend to be not that bright.
HybridStatAnim8··on GrapheneOS has been ported to Android 17
No, them supporting e/OS corroborates the claim that their goal is not privacy or security.
HybridStatAnim8··on GrapheneOS has been ported to Android 17
Android similarly supports, and in fact uses, "proper" Linux. Android and its forks are Linux distributions. You can use a mainline kernel in Android just fine.
HybridStatAnim8··on GrapheneOS has been ported to Android 17
It is not ridiculous at all. GrapheneOS is not going to compromise the privacy and security of their users for the sake of spite for one specific company. It would be immature and irresponsible to make important choices based on spite rather than objectivity.

Motorola has stepped up to meet the baseline requirements for GrapheneOS support, and we should get Motorola devices with official GrapheneOS support next year.

HybridStatAnim8··on GrapheneOS has been ported to Android 17
GrapheneOS does not depend on all of the features of pixel phones. The baseline requirements GrapheneOS has are generic, they are not built upon or tied to what pixel phones provide. Pixels actually exceed the baseline rather than barely meeting them.

Other OEMs can make devices that meet the requirements, and Motorola is doing just that. We should get Motorola devices with official GrapheneOS support next year.

HybridStatAnim8··on GrapheneOS has been ported to Android 17
GrapheneOS is not going to compromise on hardware security for the sake of spiting one specific company. GrapheneOS supports all viable platforms, and right now that is the pixel lineup. Additional device support requires OEMs step up their game, and so far, only Motorola is up to the task, and we should get Motorola devices with official GrapheneOS support next year.

There is nothing crazy about doing something properly.

HybridStatAnim8··on GrapheneOS has been ported to Android 17
Yes. GrapheneOS maintains 99% app compatibility, and the 1% that is lacking is due to apps using incredibly misguided and nonsensical "antiabuse" mechanisms.

GrapheneOS is often better for testing apps due to it being trivial to test with and without google services, most of the hardening options can be used for debugging and provide a crash log to determine what failed, and there is an easily accessible log viewer available in app info.

HybridStatAnim8··on GrapheneOS has been ported to Android 17
From what I recall, you need to enable exploit protection compatibility mode for that app, and it should work just fine.
HybridStatAnim8··on GrapheneOS fixes Android VPN leak Google refused to patch
GrapheneOS is more simple and vanilla than CalyxOS. GrapheneOS puts substantial effort into seamless/passive privacy and security features, as well as maintaining feature parity with the Android Open Source Project and with Googles stock Pixel operating system.

CalyxOS is not a private or secure operating system. They have added several 3rd party apps and services, which includes several 3rd party connections. On top of this, several of these services are given problematic, privileged access.

A notable example of this is Android Auto. CalyxOS grants substantial privileged access to this component by default, while GrapheneOS sandboxes it, and exposes 4 opt-in toggles for privileged access. The user may granularly decide what privileged access they wish to grant.

HybridStatAnim8··on GrapheneOS fixes Android VPN leak Google refused to patch
GrapheneOS inherits the user interface of the Android Open Source Project, which is what Pixels stock operating system uses, along with many other OEM forks of android.

GrapheneOSs App Store is present to fulfil the role of the first party appstore that AOSP requires. It also serves to provide updates to first party apps out-of-band, and mirror apps for various case-by-case reasons.

Accrescent is mirrored due to it having a focus on privacy and security. It is currently in alpha and app submissions are closed. They will be open Soon:tm:.

Google play is mirrored for app compatibility with apps that require google play, and for access to the playstore.

The GrapheneOS community favors Obtanium due to its ability to fetch developer-signed apps from places like Github. Fdroid signs and builds nearly every app on the main repository with outdated build infrastructure and poor moderation.

GrapheneOSs security model inherits and builds upon the AOSP security model.

HybridStatAnim8··on GrapheneOS fixes Android VPN leak Google refused to patch
No, GrapheneOS adheres to the same support period that the OEM provides. End of life devices are insecure and should not be used. Only the OEM can provide the firmware updates necessary for proper support, because the firmware images are signed by the OEM/component manufacturers. All GrapheneOS can do is push the updated firmware.

GrapheneOS has a requirement of a 5-7 year support window from an OEM.

HybridStatAnim8··on GrapheneOS fixes Android VPN leak Google refused to patch
An 8 series device or higher is recommended. Getting new from non-carrier stores or google store is reliable.

Used is a gamble due to improper OEM unlocking practices, so make sure it has a good return policy and try to verify OEM unlocking is accessible if you purchase used.

HybridStatAnim8··on GrapheneOS fixes Android VPN leak Google refused to patch
OEM/carrier locking tends to only happen in the US. Many carriers permit unlocking after the contract has concluded, but Verizon has always blocked it. Used devices also run the risk of being improperly unlocked and making OEM unlocking remain unavailable. (Used devices may also be Verizon devices.)
HybridStatAnim8··on GrapheneOS fixes Android VPN leak Google refused to patch
OEM/carrier locking tends to only happen in the US. Many carriers permit unlocking after the contract has concluded, but Verizon has always blocked it. Used devices also run the risk of being improperly unlocked and making OEM unlocking remain unavailable. (Used devices may also be Verizon devices.)
HybridStatAnim8··on GrapheneOS fixes Android VPN leak Google refused to patch
Motorola devices with GrapheneOS support will arrive in 2027 or later, not 2026. Likely, the 2027 Signature, Razr fold, and Razr flip, will meet GOSs hardware security requirements.
HybridStatAnim8··on Original GrapheneOS responses to WIRED fact checker
I would not use those words to describe the approach they take. They make the effort to speak neutrally and objectively, but the issues they are making light of are often exactly as extreme and common as they describe. Many people have voiced appreciation that they decide against a "corporate-speak" approach. The GrapheneOS accounts are meant to be accounts that let project members speak to users, rather than take on a corporate appearance.
HybridStatAnim8··on Original GrapheneOS responses to WIRED fact checker
People can accidentally be spreading attacks with loaded/presumptuous statements even when their intentions are pure. Unfortunately, pure intentions can still cause harm that needs to be countered.

Take your reply as an example, the GrapheneOS accounts are managed by multiple people, so the fixation on one specific project member may not even be accurate to the discussion. Having ones character attacked is immensely harmful on its own, but being attacked for something one may not even be doing is also immensely harmful.

The unfortunate reality is that people tend to believe the first thing they read, and without something countering it, will roll with it, intentionally or otherwise. So countering misinfo efficiently and quickly is vital.

HybridStatAnim8··on Original GrapheneOS responses to WIRED fact checker
I must emphasise I am not associated with GrapheneOS.
HybridStatAnim8··on Original GrapheneOS responses to WIRED fact checker
I am a GrapheneOS user and community member, and I am active in the chat rooms. I made this account to assist with misinformation.

As for how such a thing would not be possible;

-GrapheneOS updates do not trust the network, so any compromise of update servers for OS and app updates would not be able to push malicious updates. Only those who hold the signing keys are capable of pushing updates that will be accepted.

-Multiple people review the code that gets included in the OS. There is not one point of failure when it comes to social engineering.

-GOS supports reproducible builds, so the code that is published can be verified to be the code that is built for the official builds.

So in other words, you would need to convince multiple people who are consciously protecting against this, and who have a proven track record of burning the keys if the privacy and security of their users are in jeopardy. On top of that, you need to conceal this from every developer, moderator, and community member who would raise the alarm at the slightest indication of compromise.

HybridStatAnim8··on Original GrapheneOS responses to WIRED fact checker
I have been a GrapheneOS user for several years, and I choose to dedicate my time supporting the project. Supporting an open source project is not 'astroturfing'.

I am an active chatroom member, and many people see me there on a regular basis. I choose to volunteer my time, and am not paid or compensated in any form.

HybridStatAnim8··on Original GrapheneOS responses to WIRED fact checker
I gathered you were being facetious, but I do not appreciate being called a sockpuppet.

I am a GOS community member and I have been for several years. I am active in the GrapheneOS chatrooms, and I choose to volunteer my time assisting others.

← PreviousPage 5 of 7Next →