Imagine if Verizon, AT&T, T-Mobile and Cox banded together for a showdown against the studios accusing them of liability? AT&T runs an NSA stronghold in Manhattan, they're not going to let their darlings go down in a teeny lawsuit like this. I really want to see this happening. Let them fight.

What else is everyone using to get music? Other than Soulseek.

Hi everybody,

I've been unable to make sense or gain better understanding of the Android update system, so I'm asking here.

Coming from the linux desktop, there's two main parts of the system: the kernel and the userland. I could simply update the kernel without updating userland and vice-versa.

But does it work the same way on Android? Why are we so dependent on OTA updates from the individual manufacturer? I understand that microcode is proprietary and can come only from the device manufacturer, but aren't kernel updates and userland decoupled from this (for devices which support project treble and GKI)? Can't I just run a different FOSS launcher, get the upstream GKI kernel and run it with the microcode offered by the manufacturer?

What consists of an Android "version"? Can't I just not update the microcode beyond what the manufacturer provides, and instead keep updating the kernel (by "kernel" I mean GKI and not the actual linux kernel) and userland and in essence keep updating my android version?

I'm probably missing some fundamental understanding of android here, which is why decided to ask here. Thanks for your help!

By now, most people in the custom ROM community must have already heard of KernelSU. I do think that it is worth the hype and is truly revolutionary, piggybacking on something I credit Google on (to some personal chagrin) - KMI.

The question I have is: when I attempt to install OTA updates to a device with KernelSU running as a Kernel module, will that affect KernelSU? Will I have to root again?