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
Comment on No, you don't need a 'very bespoke AOSP' to turn your phone into a Rabbit R1 — here's proof
Kolanaki@yiffit.net 6 months agoWhat 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.
madscience@lemmy.world 6 months ago
balder1991@lemmy.world 6 months ago
I’m not entirely sure because I’m not very knowledgeable about CPUs, but it seems this is a problem with ARM architectures snd their lack of standardization, isn’t it?
madscience@lemmy.world 6 months ago
There’s nothing like uefi between the os and the hardware
MargotRobbie@lemmy.world 6 months ago
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.