Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! 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:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
I have absolutely zore faith AOSP is long for this world. The GrapheneOS folks need to find a way off yesterday
The beauty of open source is that Google can't take it back. The worst they can do is close source their own future development. Meanwhile, the community can fork the last open source release of AOSP. Look at what open source devs did with Audacity, for example.
The real fly in the ointment here is Google already did with device trees and driver binaries for Pixel phones; no longer sharing these with AOSP will have a very chilling effect on custom ROM developers who must now reverse engineer needed configs and drivers.
I’ll worried for GrapheneOS because I know the dev doesn’t really want to implement QoL improvements or design updates, so we’re currently only relying on Google's good will with AOSP for that, and we can’t expect much I’m afraid
Don’t get me wrong, GOS is good and all, but some nice features are bugged or getting killed. It might be worth delaying casual updates to fix those
Now we have a new threat: no more third party stores. At this point iOS would even be better, at least there’s some very limited sideloading