grapheneos

8 ms·

91.
by grapheneos 1mo ago
Yes, AOSP includes a lot of GPLv2 code and we use GPLv2 licensing ourselves including for our Vanadium browser project. We don't want GrapheneOS to be more restrictively licensed than the Linux kernel and AOSP so we avoid GPLv3 code bu
92.
by grapheneos 1mo ago
We're going to be forking one of them (ReFra). We want to make extensive changes and have a different vision for it than the upstream project. For example, we don't want it to have integration into services. There's plenty of
93.
by grapheneos 1mo ago
We've done months of work on overhauling the Messaging app. It has been done in incremental portions with code review for each. It often goes back and forth several times before it gets merged. Why not look at the quite open developmen
94.
by grapheneos 1mo ago
RCS is important because it provides end-to-end encryption (E2EE) for contacts with Google Messages and iOS. That means having E2EE for the vast majority of smartphone users since Google Messages is the standard GMS Android carrier-based me
95.
by grapheneos 1mo ago
It's important for us to provide out-of-the-box end-to-end encrypted (E2EE) messaging for contacts on Google Messages and iOS. Both Google Messages and iOS provide RCS with end-to-end encryption via Messaging Layer Security (MLS). Goog
96.
by grapheneos 1mo ago
Waydroid can't run nearly as many Android apps as AOSP on bare metal or especially GrapheneOS with the compatibility features it provides. It's an approach with far more limited compatibility. Waydroid has very poor privacy and se
97.
by grapheneos 1mo ago
Saying it's going to be released later today means to the Alpha channel. GrapheneOS and each of our apps have Alpha, Beta and Stable channels. Every Stable channel release made it through Alpha and Beta channel testing. We don't e
98.
by grapheneos 1mo ago
Our port of Messaging to Compose was clearly not vibe coded as both the parent comment and yours are wrongly portraying it. Experienced developers have been working on overhauling the app for months with a lot of back and forth code review
99.
by grapheneos 1mo ago
Our code quality standards are very high. Vibe coding is not capable of meeting those standards. The details of how things get written and improved to meet our standards is up to individual developers. We don't have a policy against de
100.
by grapheneos 1mo ago
We're definitely not churning out code with AI models. There's no vibe coding going on in GrapheneOS. We're carefully writing and reviewing code as we've always done. We now have additional tools to assist with it. The m
101.
by grapheneos 1mo ago
Your response doesn't address what we said. You linked to a page showing LineageOS had a release in August 2026 which does not show it has shipped all the recent standard Android and Pixel security patches, which it hasn't done. T
102.
by grapheneos 1mo ago
That doesn't come across as steelmanning our position at all but rather the opposite. It omits the most important points. Providing app accessible root in the OS greatly reduces security without people ever using it. It gives root acce
103.
by grapheneos 1mo ago
Devices are sold with GrapheneOS installed. Installing it with the web installer is very easy and safe so that's the recommendation for nearly everyone.
104.
by grapheneos 1mo ago
Fairphone 5 and earlier also have end-of-life Linux kernel branches without security support. Fairphone's more recent devices are headed to the same situation. In practice, the same thing happens with other components beyond the Linux
105.
by grapheneos 1mo ago
It's inaccurate information. Qualcomm is willing to provide 8 years of support from SoC platform launch. Android also fully supports using a newer userspace on top of an outdated device support platform. Treble provided a very good imp
106.
by grapheneos 1mo ago
Android 17 is required for full Android security updates. Only a subset of patches are backported to older versions and that's decreasing. Android 17 is also required for the latest and greatest privacy/security protections which
107.
by grapheneos 1mo ago
Android Security Bulletins are a list of the High and Critical severity patches backported to older Android versions. At the time a bulletin is published, the patches have been available to OEMs to ship for 2-4 months. Fairphone is nearly a
108.
by grapheneos 1mo ago
> There are also rumors that Google will soon stop fixing vulnerabilities in not-actual versions that were discovered by Google in LLM-driven vulnerability discovery. These are not rumors. It's an official announcement from Google t
109.
by grapheneos 1mo ago
Android 17 is required for full Android security updates. Only a subset of patches are backported to older versions and that's decreasing. Android 17 is also required for the latest and greatest privacy/security protections which
110.
by grapheneos 1mo ago
Android 17 is required for full Android security updates. Only a subset of patches are backported to older versions and that's decreasing. Android 17 is also required for the latest and greatest privacy/security protections which
111.
by grapheneos 1mo ago
The quote wasn't talking about personal security from governments and corporations. You're warping the meaning into a situation where it doesn't fit at all. Fairphones are closed source hardware with closed source firmware an
112.
by grapheneos 1mo ago
> It would be fine to run /e/OS or LineageOS on a Pixel Both /e/ and LineageOS lag far behind on current security updates on a Pixel. Neither is based on Android 17 yet which was released in June 2026. Neither has the
113.
by grapheneos 1mo ago
Fairphones are closed source hardware with closed source firmware and closed source userspace drivers. Fairphones are less open than Pixels, not more open. It isn't truly known how a Fairphone compares to an iPhone or Pixel when it com
114.
by grapheneos 1mo ago
That's highly inaccurate information. MTE is included on a large number of smartphones beyond Pixels. It's heavily integrated into iOS on the iPhone 17 as their Memory Integration Enforcement feature. MTE enables massive security
115.
by grapheneos 1mo ago
The majority of our added exploit protections are based on hardware security features and that will only be increasing over time. MTE, PAC, BTI, hardware-based blocking of USB connections/data and far more are hardware features used to
116.
by grapheneos 1mo ago
Fairphones are missing many of the required features and don't provide reasonable updates. An incomplete port of GrapheneOS won't provide decent security for users. It won't have decent encryption for the vast majority of use
117.
by grapheneos 1mo ago
GrapheneOS requires MTE for any newly added devices. Pixel 6 and Pixel 7 series devices do not meet the current requirements. Pixel 8 and later are the devices meeting the full requirements. Devices are supported until end-of-life rather th
118.
by grapheneos 1mo ago
An incomplete port of GrapheneOS to Fairphones will be missing many of the core security features and won't have reasonable security updates. Fairphones are nowhere close to reasonably secure devices. Most people expect to have decent
119.
by grapheneos 1mo ago
Linux is a kernel. Embedded, server and mobile Linux distributions without glibc, gcc, GNU coreutils, systemd, D-Bus, Wayland, Pipewire, etc. are Linux too. Linux is not a specific desktop software stack that's largely used on FreeBSD
120.
by grapheneos 1mo ago
Fairphone's updates are definitely much worse than recent Samsung flagships. It's the other way around to an extreme. Samsung does monthly security patches for their flagships and includes a large subset of security preview patche

More ›