289
No, you don't need a 'very bespoke AOSP' to turn your phone into a Rabbit R1 — here's proof
(www.androidauthority.com)
this post was submitted on 04 May 2024
289 points (95.6% liked)
Technology
59495 readers
3050 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What about custom ROMs like Lineage? The only thing holding it back from working on every phone is that many phones have blocks to prevent installing a custom ROM in the first place. Could be just like windows in that it has every driver for every piece of hardware in the package, just bloating it unnecessarily.
The manufacturer has to release the phone's kernel source code before any custom ROM development can happen for the phone most of the time for that reason.
There is a reason that GrapheneOS only works on a couple of Pixel phones.
Google specifically designed the Android kernel so that the driver are excluded, unlike the normal Linux or Windows kernel, because, long story short, Qualcomm did not want it to happen.
Every device had it's own device tree and kernel with custom driver's, binary blinds, and system software. All of it runs beside the closed source modern os
I’m not entirely sure because I’m not very knowledgeable about CPUs, but it seems this is largely a problem with ARM architectures and their lack of standardization, isn’t it?
There's nothing like uefi between the os and the hardware