this post was submitted on 06 Apr 2026
74 points (96.2% liked)

Android

33799 readers
115 users here now

DROID DOES

Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] statelesz@slrpnk.net 6 points 21 hours ago (1 children)

Having read the comments I still see two major isssues with this:

  1. This looks like an almost-as-secure-as-GrapheneOS fork, therefore creating a (false) sense of security, because..
  2. GrapheneOS's security is based on secure hardware (Pixel's Titan chip) to verify the software. Only having software security without the underlying secure hardware is kind of pointless or at least well.. a false sense of security.
[โ€“] statelesz@slrpnk.net 6 points 21 hours ago

This is actually quite a good read and pinpoints the issue. (Sorry for the Reddit-link though.) https://www.reddit.com/r/GrapheneOS/comments/1s8q534/response_to_a_post_about_grapheneos_on_another/