Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: !android@lemdro.id
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
view the rest of the comments
Graphene is only leading in security updates if you choose to run their closed source builds. Otherwise the difference in security updates between open source Graphene, Calyx and Lineage (can't speak to other Roms, have no experience with them) is usually days.
Closed source builds? Isn't the point of GOS is that it's hardened and OSS?
Google made changes to the AOSP release cycle last year. This change took AOSP from an open source project where every commit was visible, to more of a source available "here is a tar ball with squished commits so you can't say we violated the license" once every 6 months sort of deal.
Due to those changes, AOSP forks are faced with 2 options. Stay fully FOSS, reverse engineer each tarball drop for figuring out what each new commit was for and adapting that into your codebase, or the Graphene approach of partnering with an OEM (Motorola) to gain access to embargoed AOSP code, and maintaining 2 codebases (Graphene FOSS, and the Graphene embargoed version).
Graphene is trying to maintain their security goals even if it means the end user can not completely compile the most secure version of their OS on their hardware.
Lineage, Calyx, and Lineage forks l4mg, /e/OS and iodeOS are (whether by choice or by the fact collaborating with an OEM is a difficult pain in the ass) taking the first route.
You can use GrapheneOS's open source update channel, but you miss out on some security updates.
Ive always felt every android fork has its place, just the same way every linux distro does. They all serve a different purpose.
Source available still allows them to vett the code, but just not know how Google got there, so not closed source, but not truly open. Did I understand correctly?
Yeah thats pretty much the gist of it
How do you get the closed source varient? I have never seen anything about this from graphene
https://discuss.grapheneos.org/d/27068-grapheneos-security-preview-releases
It should've asked you if you wanted to switch update channels a few months back.
Thanks I wasn't aware of this