[Google Pixel 5 ROMs, Kernels, Recoveries, & Other ] aleph.mercury:
The edge lighting does work for me. IIRC I got mine to work after turning off and on again some of the other features associated with the notifications/display.

If you tell me which items in the kernel are the cause, I'll make note and try to include them in the next update which will be sometime after August 5th, when I expect Google to release the new source code/security patches.

I think you can replace the kernel with any one you please by using this tool:

GitHub - cfig/Android_boot_image_editor: Parsing and re-packing Android boot.img/vbmeta.img/payload.bin, supporting Android 15

Parsing and re-packing Android boot.img/vbmeta.img/payload.bin, supporting Android 15 - cfig/Android_boot_image_editor

github.com

and following these steps with for using that tool:

1) Clone that tool somewhere onto your computer. Copy the boot.img file to the same folder where that tool now resides. open a terminal and type:

./gradlew unpack

2) The will be a new folder under "build" called "unzip_boot".

Go there and replace the file called "kernel" (it does not have a file extension) with your own kernel. It is expecting a kernel of the ".lz4" type not the ".gz" type, so I don't think it will work for .Gz types. For example, your kernel might be called something like Image.lz4; rename it simply "kernel" when it is in the unzip_boot directory. If your kernel is called Image.gz, I don't think it will work. It's using a different compression algorithm.

Delete the folder in unzip_boot called "root."

You can also replace the ramdisk file you see in unzip_boot with the ramdisk from an already-patched-by-magisk-for-the-same-ROM-and-device-boot.img that you can extract following this same process that you would have completed before getting to this part of the walkthrough. To do this, patch the boot image using magisk like you would normally do. Pull this adjusted boot image onto your computer from /sdcard/Download like you would do to flash magisk. Take this boot.img, which magisk has renamed for you something like magisk-202310562484akjbjsdk.img and rename it "boot.img" and perform Step 1). The original ramdisk should be around 1.5MB and the Magisk version of it should be slightly bigger, around 2.0MB.. Rename this unzip_boot folder something different like magisk_unzip_boot. If you have already made an unzip_boot folder prior to trying to mess with this ramdisk part, rename that folder from unzip_boot to something like orig_unzip_boot.

Replace the ramdisk there (the 1.5MB one) with this magisk one (2.0MB). Delete this magisk_unzip_boot folder and rename the other one back to simply unzip_boot, from however you temporarily renamed it (it was suggested to rename it orig_unzip_boot here). Delete the boot.img file that was originally called something like magisk-2021545424947sdfdf.img. Make sure the boot.img file in the main folder is again the original one from earlier, the main one you started with in the first place.

Now, your unzip_boot folder should not contain a "root" folder, it SHOULD contain the new kernel you want, and you may or may not have replaces the ramdisk there with the magisk-adjusted one, thereby rooting your phone when you flash this.

Go to the terminal, you should still be in the same folder that your cloned your repo to, and the boot.img there needs to be the original one, not the magisk boot.img! If in doubt, just copy over again the boot.img from this ROM or from which ever one you've been working with on this ROM that has been successful for you. You should not be in the build folder or the unzip_boot folder.

3) Ok, now enter this into the terminal:

./gradlew pack

You should see some new files with boot in the name; I'd grab the one that is called boot.img.signed. rename it something like new_kernel_boot.img and flash it to your phone. The main thing here being you need to get rid of the word "signed" from the file. There's already a file called boot.img in this folder, that's your original one, so you can't rename it that in this folder.

Now you should have the kernel of your choice and also root if you replaced the ramdisk with the one from Magisk.

**I've always added the vbmeta.img file along with the initial step of decomposing my starting boot.img, I've also removed the vbmeta.img file when performing the magisk ramdisk extraction section, which again is optional for you. Finally, I've always re-included the vbmeta.img back in the final "pack" step. Im not 100% but when I do this I've always been able to root my phone on the stock google ROM and not had to disable verity or disable verification; my understanding is that this Android_boot_image_editor tool is smart enough to know how to reapply the original signatures. But again, I may be wrong about how this works, but by doing it with vbmeta.img included it won't break anything (from my personal experience doing this 100's of times, perhaps 1000's of times)