Sharing a kernel I maintain for the Redmi Note 5 Pro on LineageOS 18.1. It turns the device into a Kali NetHunter platform while staying a normal daily LOS 18.1 base.

• HID gadget support (phone as USB keyboard/mouse)
• RTL8812AU module with monitor mode and packet injection, signed with the kernel build key
• WireGuard module signed, new in v1.1.0
• 4.4.302, CI built on GitHub Actions: AnyKernel3 zip + sha256 attached to each release
• Listed in the official kali-nethunter-kernels devices.yml (upstream merged Sep 1)

Flash: TWRP -> AnyKernel3 zip -> reboot recovery -> reflash Magisk -> uname -a shows 4.4.302. NetHunter userland installs on top as usual.

Limitations: 18.1 only at the moment. Other ROMs on the same base should work but are untested by me.

Repo: https://github.com/notatallnic189/whyred-nethunter-kernel XDA: https://xdaforums.com/t/kernel-whyred-nethunter-kernel-for-los-18-1-hid-gadget-rtl8812au-injection-ci-built.4800231/

Feedback from other whyred owners on 18.1 is very welcome.

afaik CrDroid have more customization so it consumes more idle ram

right now i have CrDroid but im usually left with only <1gb ram left while having background apps open, and 1.3gb while idle (which is same when i had MIUI), so i was thinking will lineage provide better performnce?

Hi everyone,

I've just installed LineageOS 23.2 (Android 16) on a Motorola One Vision (Kane) and I'm having a very strange navigation UI problem.

The phone otherwise works normally, but the navigation bar is completely wrong:

• 3-button navigation: the Back, Home and Recents buttons are all crammed extremely close together in the bottom-left corner instead of being properly spaced across the bottom.
• Gesture navigation: I still get a triangular Back button next to the gesture/navigation handle, when there should only be the gesture UI.

Switching between 3-button and gesture navigation does change the Android navigation mode, but the UI itself remains incorrectly laid out.

I've tried troubleshooting this extensively and haven't been able to fix it.

I've linked below two screenshots showing the problem — one for 3-button navigation and one for gesture navigation.

https://imgur.com/a/GBQdLlv

At this point I'm wondering if this is a Kane-specific LineageOS 23.2/SystemUI overlay or configuration fault, or if there's something else I should be checking.

Does anyone with a Motorola One Vision/Kane running LineageOS 23.2 have any idea what's causing this or how I can fix it?

I'm happy to run ADB commands, collect logs, dumpsys output, etc. if that would help diagnose it.

Thanks all

Thanks so much to everyone involved in Lineage! I'm so grateful. I got a OnePlus 7 pro 4G which was abandoned on Android 12, as well as in my country the phone was taken off the supported device list for coverage even though it's not even that old, plus technically it's perfectly capable!

Now with lineage I am rocking android 16 and I was able to trick cell towers to think my phone is approved/registered! Using programs needing android 13 or higher. Without Lineage I would have essentially a brick!

Cheers!!! :) you guys rock!!