Yes only oss
Yes only oss
Hi Laptapper,Newest kewl kernel
Changelog:
• Memory management changes
(TLB & mmap/mremap backport from mainline)
• Scheduler related changes
What charging board? bq2597x or ln8000?Hello, forgive me for this noob question, what is the best kernel for me? I'm using PixelOS 12.1 and is facing battery drain issue. Also, how can I properly install or update the current kernel of my device? Thank you
Hi Laptapper,
I root and run custom ROMs since 2012 but actually never used a custom kernel.
As I received a second sweet that has ln8000 I am researching the subject
![]()
Xiaomi Redmi Note 10 Pro, charger ln8000 and custom ROMs
I use Xiaomi sweet since mid-2022. I never used MIUI. Unlocked the bootloader, flashed vanilla ArrowOS 12L and rooted the whole thing. All worked flawlessly. A few days ago I ordered a second device. Then learned about the touchscreen not...forum.xda-developers.com
Do I keep the device that has ln8000 or return it as not worth the hassle?
What is the state of affairs now?
It's all quite new to me (Xiaomi sensor lottery, not working touch, charging support, custom kernels...) and a steep learning curve.
I just planned to use vanilla (degoogled) Lineage OS on it.
Thanks!
Thanks for the reassuring message. I will keep it then. Would you spoil it for me and say if the vanilla Lineage OS, Arrow OS or /e/OS will work?I've got ln8000 and all is fine if the kernel or ROM supports this board. Otherwise the charging speed is slow
Pulkits lineage 20 is working quite good with the newest kewl.Thanks for the reassuring message. I will keep it then. Would you spoil it for me and say if the vanilla Lineage OS, Arrow OS or /e/OS will work?
Is the ln8000 thing only responsible for fast charging not working or also a cause of problems like: self-discharging, battery drain, and deep sleep?I've got ln8000 and all is fine if the kernel or ROM supports this board. Otherwise the charging speed is slow
In my opinion only charging speedIs the ln8000 thing only responsible for fast charging not working or also a cause of problems like: self-discharging, battery drain, and deep sleep?
Can I use this if my phone is BQ variant?Newest kewl kernel
Changelog:
• Memory management changes
(TLB & mmap/mremap backport from mainline)
• Scheduler related changes
I don't think so
As it Looks like Sleepy kernel is no longer supporting SWEET (as per a post in Telegram), I've compiled the code with the last set of changes as of Feb 22, 2023.
The following changes/issues were made/addressed from the original code:
- ZRam set back to 2GB (it was increased to 3GB starting Scarlet Witch build)
- Fixed incorrect colours when using 120hz (issue in XXX build)
Notes for anyone who uses this:
- This is only for OSS
- Choose the file with ln8000 if your device has that charger
- This includes some updates and fixes from the last official XXX build
- I'm not liable for any issues/damage to your device
Unfortunately I don't think there is much more I can do as I'm largely just compiling the last code commits by the developer of Sleepy. The original developer made code changes post the XXX release, but did not compile and release a new version. I'm mostly filling in that gap as well as addressing the major issue with the incorrect colours.I've checked your mod of sleepy xxx some days but it isn't stable and good as the original. May you can check why?
Because in sleepy xxx is the color problem (it's not a big problem but in low light the display looks a bit irritating)
The bb of sleepy xxx and also charging speed is the best for me......
Thanks for your work!
May I know what toolchain you used to compile sleepy kernel?Unfortunately I don't think there is much more I can do as I'm largely just compiling the last code commits by the developer of Sleepy. The original developer made code changes post the XXX release, but did not compile and release a new version. I'm mostly filling in that gap as well as addressing the major issue with the incorrect colours.
Could you still go in detail what is unstable though in case the issue is obvious? I've been using my version for nearly a month now and I actually find it more stable than the last official XXX release. I can't comment on the charging speed as it seems our phones have different chips (I'm on bq and you're ln8000) and it seems the same for me.
I'm using Proton Clang
Is this one that I need to flash for an LN8000 device?Newest aghisna kernel
OSS and MIUI
If OSS like lineage yes.
Decided to try LOS first: https://forum.xda-developers.com/t/...3-oss-lineageos-20-0-vanilla-version.4566057/
the flashing instructions can be found over on that respective thread where @Laptapper has made a detailed step by step set of steps to follow at the end of the first postDecided to try LOS first: https://forum.xda-developers.com/t/...3-oss-lineageos-20-0-vanilla-version.4566057/
especially since there is one with MicroG. There is an FW13/14 recommendation and the mobile I have is still on FW12. When do I flash the firmware V13.0.17.0.SKFEUXM? Before the ROM or after it? Thanks.
EDIT. Does it mean Cherish support ln800o out of the box?
For me with lineage 20 it works good.
Bq and ln8000 are different types of charger fw
This Kernel is for the Redmi Note 10 Pro/Max (sweet)
• Upstreamed to 4.14.292
• Merged CLO tag LA.UM.9.1.r1-12200-SMxxx0.QSSI13.0
• Brought back MGLRU
• Switched back to UClamp
• Fixed an issue where deep sleep gets f..ked after charging
Notes:
• This is for OSS vendor based ROMs
• ROMs by @neobuddy89 or @bmwtheseries are not supported
Regarding the passing safety net, Google recently pushed an update that made it so that cts would require the correct device fingerprint to match before it passed. Meaning, custom roms with Pixel spoofing, or roms that use Pixel 6 Pro, Pixel XL to spoof the device to unlock exclusive pixel features can not pass safetynet. This has been a big issue recently, and many people are complaining about the push (possibly shifting to the new integrity api). So really, the issue is not with the addition of kernelsu. In fact, KernelSU (ksu) is a kernel-based root and no app can touch that, only another root (aka magisk) can, meaning that it can intercept (hide) itself from any app that calls su binary so it is well-hidden by default, at least as of now.I've tried the Aghisna kernel, but my phone doesn't pass SafetyNet with it. I assume it has something to do with that kernelSu stuff someone mentioned?
Anyway, current sleepy works fine.