19M from Germany

  • 1 Post
  • 254 Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle


  • But how is that significantly more secure than LineageOS? I have read through countless blog posts from GrapheneOS developers and have not yet encountered an explanation that is sufficiently convincing. Outside of additional security hardening, which is definitely a big pro, GrapheneOS doesn’t have many things that LineageOS doesn’t. LineageOS is fully FOSS and telemetry-free. They introduced the “Trust” control panel for managing all sorts of privacy and security matters. They have PIN scramble.

    The only major, obvious security vulnerability lies in the proprietary driver blobs from the device vendors / OEMs. But AFAIK Google Pixels also have those, right? So outside of doubtlessly valuable measures like restricting malicious reprogramming / access through the USB port, in what ways is GrapheneOS actually more secure than LineageOS?









  • Sorry for the downvote, but I see this take repeated here on Lemmy so often and it just makes no sense. This will not kill the FOSS app “ecosystem”. Nothing whatsoever changes for FOSS ROMs like LineageOS or GrapheneOS. And as long as there are FOSS operating systems, apps will be developed for them. If anything, this could drive mainstream adoption of free/libre Android forward, re-invigorating the scene through public outcry.

    And to the people who propose fully jumping ship from Android to “Linux phones” because of Google’s recent changes, you would only make the app support matter worse. As someone who daily drives both a phone with LineageOS and one with postmarketOS (mainline-ish Linux), mobile app support is endlessly worse on Linux than the fallout from Google’s developer registration could ever be. That is not to say that Linux phones will not eventually get to a point of reasonable maturity, but it is way too early and frankly utterly irrational to bury AOSP Android or needlessly hate on it.