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
Every device requires a maintainer, someone who builds Lineage specifically for that device.
On top of that most of these OEMs don’t provide device firmware drivers publicly (camera, modem, speakers, etc), so the maintainer has to either use a generic driver (which typically sucks), or reverse engineer something more suitable.
It’s just a time and effort thing. As with all open source projects it relies on the community to volunteer their time for the benefit of others.
No OEM to my knowledge provides BLOBs publicly.
LineageOS instead extracts these from the official ROM.
RE and/or shimming only need to happen when those BLOBs become incompatible with newer versions of Android.
The actual task of a maintainer is to configure the rather generic AOSP/LOS to work with the device's specifics and integrate device-specific components.
For a few simpler examples, it must be configured which of a device's SIM slots (if any) are eSIMs, which brightness values the device's light sensor is expected to return, where the device has a fingerprint sensor (if it has one), the dimensions of the notch cutout and many other such things.
both google and Sony provide firmware blobs publicly, not sure about others.