@nprofile1q... @nprofile1q... @nprofile1q... Android doesn't require any downstream kernel patches and works fine with mainline Linux kernels. All of the kernel drivers for Android are typically open source. The issue of SoC vendors and other hardware vendors providing software support in the form of proprietary libraries and services such as the ARM Mali GPU library isn't specific to Android or caused by Android. Android having a standard hardware abstraction layer with sandboxing isn't a vendor concession.

@nprofile1q... @nprofile1q... @nprofile1q... Android follows upstream LTS more closely than Ubuntu. The person leading the work on the upstream LTS kernels (Greg KH) works for Google and maintains the GKI LTS branch for Google too. The upstream LTS kernels have Android as their main target. Pixel 6 moving to 5 years of support is why the kernel.org LTS kernels had support extended to 5 years. Pixels began moving to new LTS branches and moved to 7 years so upstream LTS dropped to 2 years. Is Ubuntu not Linux?

@nprofile1q... @nprofile1q... A major Android OEM contacted us in June 2025 and we're working with them as partners. They're improving a subset of their future devices to meet our requirements and provide official GrapheneOS support. An announcement about it is being made in March 2026 and the devices will be launched at some point in 2027.

In the meantime, there aren't non-Pixel devices we could use where we can provide strong privacy and security. We won't pretend otherwise to get more users with it.

@nprofile1q... @nprofile1q...

> Unfortunately i dont have the advanced knowledge to know who is right

Listen to privacy and security experts instead of the company marketing their products. Murena are selling phony privacy products and services with poor privacy and security.

> Grapheneos is for me also no option because, i dont want to give google my money by buying a google phone.

Pixels are currently the only devices meeting the update and security requirements. They can be bought as used devices.

@nprofile1q... @nprofile1q... @nprofile1q... You've repeatedly made inaccurate posts about GrapheneOS and our team including outright lying about us. You post aggressive responses to our replies which disparage us and try to portray us badly by framing what we've said in a negative light regardless of the fact that we've only posted an accurate technical comparison. You can't tolerate us defending ourselves and providing accurate information. You respond to that with aggression and toxicity. It's you who is toxic.

@nprofile1q... @nprofile1q... @nprofile1q...

> Why did you chose the word "atrocious"?

It's an accurate and important description of the state of desktop operating systems. No one should be under the impression that a traditional desktop OS is providing strong privacy or security.

> You don't find that aggressive?

No, it's an accurate technical statement about Windows, desktop Linux distributions and to a lesser extent macOS compared to iOS and AOSP.

Meanwhile, you're disparaging us with dishonest claims...

@nprofile1q... @nprofile1q... @nprofile1q... A plain Android system without modification in a fork is the Android Open Source Project. It provides a much higher level of privacy and security. LineageOS reduces privacy and security compared to that baseline but is still far more private and secure than traditional desktop Linux distributions.

Stock Pixel OS and every other OEM variant of Android are forks of AOSP just like GrapheneOS. AOSP is the reference implementation of Android and is the upstream project for it.

@nprofile1q... @nprofile1q... @nprofile1q... A plain Android system without modification in a fork is the Android Open Source Project. It provides a much higher level of privacy and security. LineageOS reduces privacy and security compared to that baseline but is still far more private and secure than traditional desktop Linux distributions.

Stock Pixel OS and every other OEM variant of Android are forks of AOSP just like GrapheneOS. They're not the standard or stock state of Android but rather OEM forks of it.

@nprofile1q... @nprofile1q... @nprofile1q... Neither open source or distribution packaging inherently provide privacy or security. It's not the case that people only use software from official repositories regardless.

Contrary to the common misconception, only using software from distribution repositories doesn't avoid trusting the upstream developers and doesn't address supply chain attacks. As an example, Debian shipped a backdoor in sshd after it was included in the xz project as part of the published sources.

@nprofile1q... @nprofile1q... @nprofile1q...

> This is exactly what people mean when they say that GrapheneOS people (and in particular this [official?] account in this case) are quite aggressive disparaging all the other ecosystems.

We posted a reply addressing misconceptions with accurate information. There was nothing in any way aggressive about what we posted. You're making dishonest claims about GrapheneOS and our team as you've done previously. It's you who being aggressive and causing us to defend ourselves.

@nprofile1q... @nprofile1q... @nprofile1q...

> This is exactly what people mean when they say that GrapheneOS people (and in particular this [official?] account in this case) are quite aggressive disparaging all the other ecosystems.

We posted a reply addressing misconceptions with accurate information. There was nothing in any way aggressive about what we posted. It's you who is disparaging GrapheneOS and our team. Ytou're lying about the GrapheneOS project and our team. It's you being aggressive and dishonest.

@nprofile1q... @nprofile1q... @nprofile1q...

> a Linux distro has a different threat model than an Android "distro".

Android distributions are Linux distributions. Desktop Linux distributions don't truly have a different threat model but provide much weaker privacy and security than the Android Open Source Project. They lack modern exploit protections, broad use of memory safe languages and a mandatory app sandbox. They only have very incomplete app sandboxing without a modern permission model available for it.