grapheneos

6 ms·

61.
by grapheneos 1mo ago
Fairphone provides very poor updates much worse than iPhone, Pixel, Samsung flagship or many other devices. They lag far behind partial backports of security patches to older releases of Android. They lag a year or more behind full security
62.
by grapheneos 1mo ago
Qualcomm provides 8 years of support from platform launch. Android versions are not locked to kernel versions. In general, new Android versions do not require new kernel versions. In practice, all kernel drivers are open source including fo
63.
by grapheneos 1mo ago
That's not true. AOSP has a functional keyboard and Dialer app. There are also many third party apps for both available. Linux does not mean glibc, systemd, Bash, GNU coreutils, Wayland/X11, Pulseaudio/Pipewire, etc. Android
64.
by grapheneos 1mo ago
/e/ does have services collecting data on their users which isn't disclosed including user tracking via unique identifiers in the update client. They also spent years sending user speech data to OpenAI without informing users
65.
by grapheneos 1mo ago
GrapheneOS provides massive privacy and security benefits to regular people. That was always important to regular people due to regular devices being nowhere close to good enough to protect people well enough against common threads to their
66.
by grapheneos 1mo ago
Qualcomm provides 8 years of support from platform launch. OEMs/ODMs need to choose to pay for it. Fairphone doesn't ship proper updates from the beginning due to lagging months behind on incomplete backports and years behind on c
67.
by grapheneos 1mo ago
> demand that even firmware level binaries are open sourced. The hardware and firmware for those devices is closed source. It's strange to claim users demand something which is not the case. GrapheneOS users want open source hardwar
68.
by grapheneos 1mo ago
No, we're not talking about packaging software in our app repository (App Store) but rather software being included in GrapheneOS. If any GPLv3 software is included in GrapheneOS then that places more restrictions on how it can be used
69.
by grapheneos 1mo ago
iPhones and Pixels have similar replacement parts available and much longer term support. It's harder to replace components but the phones last longer due to better hardware and updates.
70.
by grapheneos 1mo ago
Here's our response to what you've pasted in response to multiple of our replies: https://news.ycombinator.com/item?id=49599645
71.
by grapheneos 1mo ago
This is trolling and it's appropriate for it to be flagged: > But I guess most of the low-hanging fruit has been solved by the mainstream OS, so a new OS has to take all of the dirty work no one else would touch in order to be relev
72.
by grapheneos 1mo ago
We've explained we're using a GrapheneOS project account due to libelous personal attacks, stalking and harassment towards our founder and other team members. Hacker News has many past threads filled with libelous personal attacks
73.
by grapheneos 1mo ago
GrapheneOS does include GPLv2 code both via AOSP and our own but not GPLv3. We want GrapheneOS to have no additional restrictions beyond AOSP. AOSP uses GPLv2 but not GPLv3. We do need to be careful with GPLv2 due to license incompatibiliti
74.
by grapheneos 1mo ago
You've made multiple comments disparaging GrapheneOS because of two minor features it provides. Both features are fully legal for GrapheneOS to include. Both are legal to use as long as people follow applicable laws. Both our regular c
75.
by grapheneos 1mo ago
RCS provides far better support for group chats, many small feature improvements and end-to-end encryption (E2EE) via Messaging Layer Security (MLS). E2EE for talking to GMS Android and iOS users without them needing to install another app
76.
by grapheneos 1mo ago
That's a huge downgrade for privacy, security, usability, battery life and compatibility with apps. GrapheneOS is Linux too. Linux doesn't mean glibc and systemd. Linux is unfortunately not a great base for an OS focused on privac
77.
by grapheneos 1mo ago
Android is an open source Linux distribution for smartphones. It doesn't have to be used with Google Mobile Services. AOSP is far more private, secure, usable and compatible with a far broader amount of apps. Why wouldn't we use t
78.
by grapheneos 1mo ago
No, that's a widespread misconception. Google Play services is nearly entirely APIs for using Google services. It hasn't replaced AOSP functionality and the AOSP APIs are still there. If you want to avoid Google services then ther
79.
by grapheneos 1mo ago
There's a separate thread about our secure clipboard feature: https://bsky.app/profile/grapheneos.org/post/3muupuvlfbs2v We posted it right after the Messaging app thread but they're separate topics
80.
by grapheneos 1mo ago
That's available in userdebug builds of GrapheneOS via ADB. A userdebug build can be done with ro.adb.secure=1 to keep the ADB authentication model intact which is disabled in userdebug builds by default for early boot debugging.
81.
by grapheneos 1mo ago
One of the parties involved in a call recording it is not surveillance. It's comparable to having chat logs for text messaging. Contrary to what you've claimed, vast majority of US states have one party consent for call recording.
82.
by grapheneos 1mo ago
We spent months working on this and certainly didn't vibe code it. We do use LLMs but primarily for code review and boilerplate. We're now including a lot more tests partly thanks to it being less of a pain. Our quality standards
83.
by grapheneos 1mo ago
Our plan is to fork ReFra and drastically change it. We have a different scope and requirements for it. ReFra will still be useful for people who want features we don't plan to provide. We've considered trying to do it as an ongoi
84.
by grapheneos 1mo ago
RCS is a modern replacement for SMS/MMS with end-to-end encryption (E2EE) support via MLS. We have SMS/MMS so we need RCS to replace those. Similarly, carrier-based calls are there and should get replaced with a newer standard wit
85.
by grapheneos 1mo ago
That's one of the reasons we care about it for GrapheneOS. It also provides end-to-end encryption between Android and iOS via Messaging Layer Security (MLS) which is clearly very important for us. GrapheneOS users needing to use Google
86.
by grapheneos 1mo ago
RCS provides properly working group chats and end-to-end encryption with iOS and GMS Android users without having to succeed at convincing people to use Signal instead.
87.
by grapheneos 1mo ago
Immich doesn't use the FUTO license because they acquired it and it was already under a copyleft open source license.
88.
by grapheneos 1mo ago
https://news.ycombinator.com/item?id=49593405
89.
by grapheneos 1mo ago
We've collaborated with many Google engineers working on Android. Many of their engineers, security researchers and even people in management positions follow us on social media. One person who describes themselves as an AOSP engineer
90.
by grapheneos 1mo ago
OS components don't need to have compatible licenses if they're separate from each other. The Linux kernel is GPLv2-only which forbids GPLv3 licensing. That doesn't mean GPLv3 code can't be used in a Linux-based OS. We u

More ›