Why don't use latest Google one? kdragon is very old...Old one, use it for older devices like f1 as well as newer ones
Because it supports specific optimizations that google doesnt support and Im using it accross the devices I work for
Touch issues are random, but I've optimized the touch drivers and I included 2 touch firmwares that can be flashed from ngk app itself using a simple toggle. So should help. But it will always depend on your phone. Every x3pro behave differently.Will this kernel reduce ghost touches on poco x3pro? Can I flash it on rooted miui 12.5?
Yes on every release. As you can see from changelog both are .314
Good to know, i dont think they will come back if you usually notice them quicklyWorking just fine on my x3pro. Android 11, stock rooted MIUI 12.5.2. I just want to try if this would lessen the horrible ghost touches. After flashing, I just left it on Balanced mode and only tweaked the Touch firmware to use the 13.0.3 version. I did nothing else.
It has been 31 hours and counting and I have not experienced any ghost touch events as of yet. I would know if there is one because I enabled the "show taps" on the Dev Options to show visual feedback in case a ghost touch happens. I have not encountered one since enabling the firmware.
Looks promising! Would the ghost touches come back? I guess we'll see. Thank you for your excellent work, @Pierre2324.
Will post back if I ever encounter another ghost touch event.
Yes, no mode at all (no bootup tweaks) without magisk. Gpu max will be stock.Can I use Nogravity kernel without magisk? what mode will it use if i don't use magisk ? or will it still work without magisk?
In next update
You da man, brah !now it works, reinstall persist.img, re-flash non-gravity kernel over stock, but no longer flash miui.dtbo from non-gravity, just flash miui.dtbo from stock. It even stuck restarting at some point, because I suppose some kind of incompatibility between miui.dtbo no gravity and miui 14.0.3 global stock android 13. Now everything works correctly. I still need to do more tests.
You da man, brah !
I tried your method (I renamed the .img file of the dtbo supplied with NGK to .bk, so the installer wouldn't see it anymore) and dirty-flashed NGK without the dtbo : now it seems to work flawlessly on Xiaomi.EU14!
The only thing that you need to be very mindful of are third-party kernel or system manager apps (like 3C CPU Control, SmartPack Kernel Mgr, Greenify, etc.) and uninstall -or at least disable them- because having them enabled and running concurrently to the NGK app turns your device into a toaster oven (mine got up to 70°C before I managed to figure out what the problem was), and this drains your battery in an eyeblink and even with the phone hooked to the charger...![]()
Not really : I just had them reinstalled from APKs after a clean flash, but I haven't had enuff time to tweak them so they were still in their default/initial config.No reason for those apps to make the device heat up like this unless you tweak something wrong in them.
120hz is there. 30hz isnt because its useless and breaks some things in some romsHi. The core is good. But, that's why they don't want to add a screen from 30 to 120 Hz to this hertz core?![]()