#NOVA #Linux #Kernel #Munch
NOVA KERNEL - MUNCH (POCO F4)
[R4] 2024/06/21 - Stable
⚪ Channel | Discussion
⚪ Download
⚪ Changelog
⚪ Source
Credits :
-> EmanuelCN0 for base & help
-> Testers
Notes :
-> AOSP/MIUI/HyperOS Supported
-> KSU v0.9.5 & NonKSU Build Available
-> Inlined KProfile & KCAL
-> Read Changelog
(Set Kprofiles mode to 2 (Balance) or 3 (Performance) if you're not satisfied with the smoothness.)
NOVA KERNEL - MUNCH (POCO F4)
[R4] 2024/06/21 - Stable
⚪ Channel | Discussion
⚪ Download
⚪ Changelog
⚪ Source
Credits :
-> EmanuelCN0 for base & help
-> Testers
Notes :
-> AOSP/MIUI/HyperOS Supported
-> KSU v0.9.5 & NonKSU Build Available
-> Inlined KProfile & KCAL
-> Read Changelog
(Set Kprofiles mode to 2 (Balance) or 3 (Performance) if you're not satisfied with the smoothness.)
IMPORTANT NOTICE !
For people who faced random reboots, you probably have bad binned GPU since NOVA uses undervolted GPU nodes.
In short, your GPU cannot handle very low voltage and causes system freeze and random reboot. if you got bad binned GPU, you're unlucky.
The lower the voltage is, the lower power it will consume and less the heat it will generate, but not all GPU is capable to do it specially if it's bad binned.
READ THIS TO FIX IT
Upcoming NOVA release will use safe undervolt where bad binned GPU still be tolerated.
For people who faced random reboots, you probably have bad binned GPU since NOVA uses undervolted GPU nodes.
In short, your GPU cannot handle very low voltage and causes system freeze and random reboot. if you got bad binned GPU, you're unlucky.
The lower the voltage is, the lower power it will consume and less the heat it will generate, but not all GPU is capable to do it specially if it's bad binned.
READ THIS TO FIX IT
Upcoming NOVA release will use safe undervolt where bad binned GPU still be tolerated.
#NOVA #Linux #Kernel #Munch
NOVA KERNEL - MUNCH (POCO F4)
[R5] 2024/07/01 - Stable
⚪ Channel | Discussion
⚪ Download
⚪ Changelog
⚪ Source
(HyperOS support is now dropped. Booted and worked on HyperOS but i won't responsible for bugs)
Credits :
-> EmanuelCN0 for base & help
-> Testers
Notes :
-> AOSP/MIUI Supported.
-> KSU v0.9.5 & NonKSU Available.
-> KProfile & KCAL Supported.
-> ALWAYS Read Changelog.
-> Set Kprofiles to 3 if you're not satisfied with the smoothness.
NOVA KERNEL - MUNCH (POCO F4)
[R5] 2024/07/01 - Stable
⚪ Channel | Discussion
⚪ Download
⚪ Changelog
⚪ Source
(HyperOS support is now dropped. Booted and worked on HyperOS but i won't responsible for bugs)
Credits :
-> EmanuelCN0 for base & help
-> Testers
Notes :
-> AOSP/MIUI Supported.
-> KSU v0.9.5 & NonKSU Available.
-> KProfile & KCAL Supported.
-> ALWAYS Read Changelog.
-> Set Kprofiles to 3 if you're not satisfied with the smoothness.
Good news everyone,
Since i am using stock HyperOS, the kernel will support HyperOS as it should be.
My recent tests and case it's working good on HyperOS.
Since i am using stock HyperOS, the kernel will support HyperOS as it should be.
My recent tests and case it's working good on HyperOS.
If you want to test stable-beta builds, you can see HERE
This group is intended to share CI builds with latest changes. And some shitpost ?
This group is intended to share CI builds with latest changes. And some shitpost ?
In future updates, i will remove KernelSU and Non-KernelSU due to truncated-too-much variant. In short that every kernel will have KernelSU module built-in.
What about Magisk support ? Magisk can always still be used if you don't use KernelSU app. The only problem that sometimes user have used KernelSU in the past time, and forgotten to delete KernelSU app and it's leftovers under /data/adb/ksu.
So don't worry, i will prepare everything to make sure Magisk to be working even though the kernel already have KSU.
It will be either having a flashable KernelSU cleaner zip, or it will be inlined with the kernel installer to automatically clean KernelSU leftovers to make sure Magisk working properly.
What about Magisk support ? Magisk can always still be used if you don't use KernelSU app. The only problem that sometimes user have used KernelSU in the past time, and forgotten to delete KernelSU app and it's leftovers under /data/adb/ksu.
So don't worry, i will prepare everything to make sure Magisk to be working even though the kernel already have KSU.
It will be either having a flashable KernelSU cleaner zip, or it will be inlined with the kernel installer to automatically clean KernelSU leftovers to make sure Magisk working properly.
Project 113 | Updates
In future updates, i will remove KernelSU and Non-KernelSU due to truncated-too-much variant. In short that every kernel will have KernelSU module built-in. What about Magisk support ? Magisk can always still be used if you don't use KernelSU app. The only…
KernelSU,
Recently there's some issues where KernelSU causes system slowdowns and stutters in most scenarios, and i am looking forward to see the problem.
(i am suspicious with susfs that implemented to ksu)
As for now and future, the dev itself already discontinued KernelSU support for non-GKI kernel. Since we're not GKI, we will suffer from it unless someone bring the ksu updates or changes to non-GKI ksu.
I recommend to start moving back to Magisk for root solutions as for now. KernelSU will still be an option for my kernel releases
Recently there's some issues where KernelSU causes system slowdowns and stutters in most scenarios, and i am looking forward to see the problem.
(i am suspicious with susfs that implemented to ksu)
As for now and future, the dev itself already discontinued KernelSU support for non-GKI kernel. Since we're not GKI, we will suffer from it unless someone bring the ksu updates or changes to non-GKI ksu.
I recommend to start moving back to Magisk for root solutions as for now. KernelSU will still be an option for my kernel releases
Project 113 | Updates
KernelSU, Recently there's some issues where KernelSU causes system slowdowns and stutters in most scenarios, and i am looking forward to see the problem. (i am suspicious with susfs that implemented to ksu) As for now and future, the dev itself already…
Anyway this is confirmed by myself. Recently i always use KernelSU, and just for couple days earlier, my device have noticeable slowdowns. Even scrolling have noticeable stutters and it's affecting systemui.
I just switched to Magisk and it's all fixed. Even though Magisk is a hell shit to hide from detections like banking apps.
The main point is notMagisk = Gaming. KernelSU just broke something either the rom or something in the kernelspace.
And other proof that KernelSU is broken when running hackbench.
Everytime i tried to run hackbench, my device completely froze out and need to be force restarted. And surprisingly it was fixed by switching to Magisk.
I just switched to Magisk and it's all fixed. Even though Magisk is a hell shit to hide from detections like banking apps.
The main point is not
And other proof that KernelSU is broken when running hackbench.
Everytime i tried to run hackbench, my device completely froze out and need to be force restarted. And surprisingly it was fixed by switching to Magisk.
Project 113 | Updates
Photo
Okay, so this is my new discovery regarding Battery Health.
Recently i got issues where my phone suddenly death during overnight charging or when battery is going to full during the charge. The culprit came from bad battery and it causes voltage fluctuate, thus causing panic/blackscreen. Any battery health percentage either it's from FKM, Settings, Battery Monitoring, or whatever it is... It's not going to be fucking accurate.
The only way to predict and determine your battery health is by looking at the battery voltage nominal. If it's drops too much during heavy load, or phone dies when battery is low (10% or so), or the voltage is going over 4.45v when charging... Throw and buy new original battery ASAP, it might kill your PMIC.
Like in this example where the battery voltage shows 4.45v at 93%, which is not normal at all because 4.45v is the maximum tolerated voltage and full voltage must be around 4.35v. And then it goes up to 4.6v when plugged in, which is dangerous.
Recently i got issues where my phone suddenly death during overnight charging or when battery is going to full during the charge. The culprit came from bad battery and it causes voltage fluctuate, thus causing panic/blackscreen. Any battery health percentage either it's from FKM, Settings, Battery Monitoring, or whatever it is... It's not going to be fucking accurate.
The only way to predict and determine your battery health is by looking at the battery voltage nominal. If it's drops too much during heavy load, or phone dies when battery is low (10% or so), or the voltage is going over 4.45v when charging... Throw and buy new original battery ASAP, it might kill your PMIC.
Like in this example where the battery voltage shows 4.45v at 93%, which is not normal at all because 4.45v is the maximum tolerated voltage and full voltage must be around 4.35v. And then it goes up to 4.6v when plugged in, which is dangerous.
Kernel Naming Scheme Installation
Starting from R9 version
SIDELOADING KERNEL WILL SELECT INSTALLATION AS DEFAULT
Rename the kernel .zip file with arguments of :
Configure to utilize KernelSU, or not. Default is disabled.
Configure DTBO for MIUI/HyperOS.
Configure DTBO for AOSP as well as default.
Configure for efficient cpu frequency table. Default is the the normal cpu frequency table.
Example of the kernel name :
E404
(All default installation)
(Enables KernelSU)
(Enables MIUI support and KernelSU)
Starting from R9 version
SIDELOADING KERNEL WILL SELECT INSTALLATION AS DEFAULT
Rename the kernel .zip file with arguments of :
-KSU or -NOKSU or noneConfigure to utilize KernelSU, or not. Default is disabled.
-MIUI or -miuiConfigure DTBO for MIUI/HyperOS.
-AOSP or -aosp or noneConfigure DTBO for AOSP as well as default.
-EFFCPU or noneConfigure for efficient cpu frequency table. Default is the the normal cpu frequency table.
Example of the kernel name :
E404
-MUNCH.zip(All default installation)
E404-MUNCH-KSU.zip(Enables KernelSU)
E404-MUNCH-MIUI-KSU.zip(Enables MIUI support and KernelSU)
GPU Undervolt, Konabess
So i've found out something that probably not everyone already know about. As for now, GPU undervolt done by looking at this 2 aspects; no artifacts, no freezing. Those 2 things were the concern of going to the most lowest voltage possible to run.
Running on the lowest voltage with no artifacts or freezing might be a good thing. But there's something we are not aware whole this time. Microstutters.
Running too low voltage might cause device to have microstutters due to sudden spike of GPU power demand.
Let's take example of it :
- 150mhz @1 microvolt
- 205mhz @1 microvolt
- 330mhz @1 microvolt
This might sounds good since it run with no issues with the lowest voltage, but it cause microstutters. Don't run anything lower than RETENTION (@16), since it also might fasten the GPU aging.
So, i made a simple formula to have "safe" undervolt.
example:
683mhz @225, it will be 683mhz @241
Lowest threshold means the safest microvolts to run without having issues like artifacts or freezing, and then added by 16.
So i've found out something that probably not everyone already know about. As for now, GPU undervolt done by looking at this 2 aspects; no artifacts, no freezing. Those 2 things were the concern of going to the most lowest voltage possible to run.
Running on the lowest voltage with no artifacts or freezing might be a good thing. But there's something we are not aware whole this time. Microstutters.
Running too low voltage might cause device to have microstutters due to sudden spike of GPU power demand.
Let's take example of it :
- 150mhz @1 microvolt
- 205mhz @1 microvolt
- 330mhz @1 microvolt
This might sounds good since it run with no issues with the lowest voltage, but it cause microstutters. Don't run anything lower than RETENTION (@16), since it also might fasten the GPU aging.
So, i made a simple formula to have "safe" undervolt.
@lowest_threshold + @16example:
683mhz @225, it will be 683mhz @241
Lowest threshold means the safest microvolts to run without having issues like artifacts or freezing, and then added by 16.
Good December Everyone,
Development of the kernel is now paused for a while !
The reason is because i don't have any device to compile my sources anymore. I used to compile with my shared laptop, but now the keyboard is dead due to water damage (my brother spilled water on it).
So kindly wait until i got my own laptop, setting it up again with linux distro, etc etc and continues working on it. Thanks !
Development of the kernel is now paused for a while !
The reason is because i don't have any device to compile my sources anymore. I used to compile with my shared laptop, but now the keyboard is dead due to water damage (my brother spilled water on it).
So kindly wait until i got my own laptop, setting it up again with linux distro, etc etc and continues working on it. Thanks !