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
Get a Pixel and install GrapheneOS on it. It is super easy these days, you can do it using just a Chromium based web browser. And don't worry there is no chance you will brick your device.
I believe we need to consider a more sustainable alternative, as GrapheneOS may not be viable for the long term.
Why? They are working on an non Pixel Phone.
Android itself without the proprietary crap added to it by Google is open source and will continue being so long it keeps using the Linux kernel. This is not going to change as the Linux kernel is licensed under GPL, and if you link against GPL licensed code your own code also has to be licensed under GPL.
The problem GrapheneOS has is not with AOSP going away, but with Google not publishing the device tree for their Pixel devices like they used to, making it impossible to unlock the bootloader, and generally making harder to develop a custom ROM for their devices.
The GrapheneOS team is currently working with an OEM to develop a phone that comes with GrapheneOS from the factory. If that happens and we no longer have to rely on Google hardware for installing it then the problem is solved.
They're quite close to Pixel 10 support despite the lack of device trees, the biggest problem is if Google decide to completely block bootloader unlocking with future pixels. Hopefully by that time their OEM phone will be out
never heard of a web based os install before, sounds interesting but i still really don't like the idea of instantly voiding the warranty of a €100+ device.
You are not voiding any warranty. You can very easily revert back to stock if you need to.