[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Yes, a flashable zip could be done, but first I want to be sure that everything is working fine even on LOS, I don't want to ship something half broken on other ROMs

Glad that works! Fake defconfig it's used on all custom kernels, otherwise Android will show that silly popup every boot, Termux devs suggest to use the real defconfig during the kernel bringup for an easier implementation of all the required features, but that's all. I will upload the new kernel every release, and can be flashed for both standard and Plus version, if you don't see the new kernel when a new release is out send me a message here or on Github, my memory sometimes sucks :)

Don't do this, in particular way on mobile devices using EAS. Powersave and Performance governor are old (updated last time 11 years ago in our kernel), and on mobile devices both of them are complete crap. Both governors works basically in the same way: powersave use everytime the lowest CPU frequency available, and Performance gov do the same thing with the higher freq available. On mobile devices this is completely wrong. You are lucky because some power hints are still working (some of them will be broken because works in conjunction with EAS) otherwise you'll end up with a device using only the lower frequencies, making it completely unusable (imagine open a huge app like GCAM with big and LITTLE cores stuck at min freq, you will be old before the app is fully open, and probably dead before the image is processed :) ) Additionally power governor is completely unaware about power consumption in various CPU steps, and the assumption "lower freq used" = "less power used" is also terribly wrong, especially when screen is off. My Grus with PE during the night in 5 hrs with my kernel reach 98.5% of deep sleep time with everything enabled (and PE is terrible compared to LOS from this point of view, because Pixel goodies have a great cost in terms of used RAM/CPU/background running processes, but I love them, i'm aware of that and I will stay on PE until the devs will work on this awesome ROM), because EAS tries to set the best freq needed for the task and puts the device in deep sleep again. Example: task "A" requires 10 seconds to be executed at 300 Mhz on LITTLE cores, but can be executed in 3 secs at 1516 Mhz and 2 secs at 1708 Mhz. Powersave governor doesn' care about anything, and stays at 300 Mhz. At that point your deep sleep is broken. Then, in order to avoid a terrible battery drain you are forced to start to block background processes, causing another drawback: the process you killed/frozen because power save mode force the deep sleep must be executed at certain point, most probably when you turn the screen on, at this point you must start the process again if it has been killed, wasting battery when the screen is on. EAS knows that task "A" must be executed, and if it's properly configured knows the power consumption needed for 1516 and 1708 Mhz steps, and decide the correct freq that must be applied . This is a really really basic example, the way how scheduler decide what's better between the 2 freqs cannot be explained here in a few words, if you are interested I suggest to take a look at EAS Documentation, but basically it tries to predicts the power consumption needed for a specific task and choose the best lower freq to use to execute the task in an acceptable way. My kernel probably performs better in your case only because I've removed all the tracing/debugging features and a lot of completely unuseful stuffs for a production devices, you have less tasks running and less overhead, but Powersave gov will seriously break things on all kernels and in all mobile devices :)

If something happened is probably related to LOS ROM but unrelated to device tree/kernel, in these months only things merged on LOS DT are the changes that breaks proximity sensor and the security patches, nothing else that could change power consumption, and my kernel include the latest security patches merged on LOS, i'm sure they are safe, and I don't think is related to AOSP QPR3 sources because I have no problem at all on PE and no one reported strange battery behaviour. But if you were using PowerSave gov there's also the possibility that something in QPR3 make thing worse with that governor, after all no one cares about it, and no one should use it :)

Try this:

1 - Remove your custom changes on kernel conf and battery saver stuffs

2 - Flash LOS ROM (no need to wipe data, but this will remove all files you pushed and clean every change made to system and vendor)

3 - After the boot, enable adb, start a root shell and mount system and vendor as writable (do it while Android is running, not in recovery mode like you did previously). No need to use Magisk, the root shell is already available on userdebug builds, but on LOS must be manually enabled in developer options

adb root
adb shell mount -o rw,remount /vendor
adb shell mount -o rw,remount /

4 - push the files

5 - Reboot in fastboot mode and flash the kernel

If everything works fine and you decide to use it as daily feel absolutely free to redistribute it, no problem at all for me :)

IMPORTANT: I've uploaded the updated PE Standard version for people that use it:

Pixel Experience 13 Standard