@GrapheneOS@grapheneos.social @elly
-
@fun @domi @elly @mei For the devices we're working on with our OEM partner, we plan to move to new LTS branches similar to Pixels but perhaps faster than they do.
Android officially supports 6.12 for devices launched with or upgraded to Android 16 but Pixels are cautious due to how many regressions there are in new kernel versions. Pixel 10 launched at the end of 2025 using 6.6 and that indicates they're going to move older devices to 6.6 soon. It's essentially mandatory to move yearly now.
@fun @domi @elly @mei Greg KH is the main one maintaining the kernel.org LTS branches and also the Android GKI LTS branches based on those which have additional backported features and the driver ABI stability approach we don't think makes much sense. Pixels use the same latest kernel source tree to build the drivers and update them together anyway. They split it with ABI stability so vendors can update kernel image / base modules separately but no OEM is actually doing that as far as we know.
-
@fun @domi @elly @mei Greg KH is the main one maintaining the kernel.org LTS branches and also the Android GKI LTS branches based on those which have additional backported features and the driver ABI stability approach we don't think makes much sense. Pixels use the same latest kernel source tree to build the drivers and update them together anyway. They split it with ABI stability so vendors can update kernel image / base modules separately but no OEM is actually doing that as far as we know.
@GrapheneOS @domi @elly @mei I think trying to mainline things as much as possible could greatly help you in this, then you have only few patches to carry downstream and rebasing becomes easier
