Android
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:
view the rest of the comments
Would this affect android-based OSes like lineageOS? Or can they patch something like that?
likely will affect them, but now that it's been disclosed will probably get patched immediately (but not by google).
It has been disclosed for a while…
yes, but were the vendors that provide lineage/eos/etc aware of the disclosure?
probably not.
On grapehene os and hasn't encountered mentioned bug.
I would honestly be surprised if the Grapheme network stack wasn't fully rewritten. So yeah, my money is this bug did not propagate to their codebase.
Any other android custom ROM I would be careful with, though...
Seems like they may have around this time
Yes to both?