*IMPORTANT NOTE*
Only for users who are in Official A11 MIUI ROM and want to improve performance
1. Remove tons (136 Bloatware Apps) of bloatware running in background freeing lot of resources aka remove excess load on CPU,GPU,Mem,Ram and Modem making MIUI user experience smooth.
2. Xiaomi Redmi Note 11 have a system SOC frequency limitation apps like Power keeper,Battery Management and Jyose limit 90 Hz and CPU+GPU freq on certain 3rd Party apps proced by /system/vendor/lib/gameoptimaization,adaplaunch,appsoptimaizationlibs not only that Xiaomi artificially limited CPU hispeed _freq on highspeed_load 85 both for A73 and A53 Cores rather then setting high_speed_load 75 for high speed frequency also the Boost frequency of CPU is limited to 1.73 GHz and 1.51 GHz rather then 2.40 GHz and 1.90 GHz even kernel force fast charge is set to zero.
(SO IT ELEMINATES ALL THE ABOVE MENTIONED ARTIFICIAL LIMITATION)
3. Enables High Performance Mode For aw87xx_SND_soc and Balanced the LR spks for indian MIUI users only
4.Enables Fast Charging.
5.Many more if u used u will know it better.
6.Bring back miui animation.
7.Set min clock-speed from 0.3 to 2.4 GHz on A73 and 0.3 to 1.9 GHz on A53 insted of 1.01 to 2.4 GHz on A73 and 1.1 to 1.9 GHz on A53
Note MIUI Camera, MIUI Gallery will be removed so use Gcam and Google Photos insted.
Flash both files via magisk reboot and enjoy
*I am not responsible for anything use at your own risk*
the thing we need the most is kernel, then all the problems will be solved ... maybe
My Persona said:
the thing we need the most is kernel, then all the problems will be solved ... maybe
Click to expand...
Click to collapse
yeah but the kernel already support those that i mentioned using init.sh to set those values
does ur tweaks support AOSP rom ? i'm using Project Blaze rom and wonder if my phone can flash these
the support is limited to miui roms only *already mentioned in the thread*
Im stuck on Android screen after flashing these mods, also after disabling them my status bar padding broke
Phreek- said:
Im stuck on Android screen after flashing these mods, also after disabling them my status bar padding broke
Click to expand...
Click to collapse
you must be using another module that are conflicting with the files or customized miui rom.
I have Raven 7.5 rom. i tried disabling any kernel/tweaking modules but it still bootloops
Phreek- said:
I have Raven 7.5 rom. i tried disabling any kernel/tweaking modules but it still bootloops
Click to expand...
Click to collapse
ohh u must be miui official rom
Is there a way i can make this work on a custom rom ? With overlays for example
Phreek- said:
Is there a way i can make this work on a custom rom ? With overlays for example
Click to expand...
Click to collapse
no dop but soon realsing A12 n A13 compatible custom rom patches
miui official 13.0.2.0 android 12 not working......stuck on android logo no other modules
edit: worked on android 11 official miui
QUALCOMM LEAKED SOURCE 🎃 said:
no dop but soon realsing A12 n A13 compatible custom rom patches
Click to expand...
Click to collapse
Camera app shouldn't be removed because till date I've not found a GCam that can shot videos
QUALCOMM LEAKED SOURCE 🎃 said:
no dop but soon realsing A12 n A13 compatible custom rom patches
Click to expand...
Click to collapse
If these patches are not supported with newer Android versions you should mention it in op
Can you make a mod for stereo speaker to sound equally
QUALCOMM LEAKED SOURCE 🎃 said:
*IMPORTANT NOTE*
Only for users who are in MIUI ROM and want to improve performance
1. Remove tons (136 Bloatware Apps) of bloatware running in background freeing lot of resources aka remove excess load on CPU,GPU,Mem,Ram and Modem making MIUI user experience smooth.
2. Xiaomi Redmi Note 11 have a system SOC frequency limitation apps like Power keeper,Battery Management and Jyose limit 90 Hz and CPU+GPU freq on certain 3rd Party apps proced by /system/vendor/lib/gameoptimaization,adaplaunch,appsoptimaizationlibs not only that Xiaomi artificially limited CPU hispeed _freq on highspeed_load 85 both for A73 and A53 Cores rather then setting high_speed_load 75 for high speed frequency also the Boost frequency of CPU is limited to 1.73 GHz and 1.51 GHz rather then 2.40 GHz and 1.90 GHz even kernel force fast charge is set to zero.
(SO IT ELEMINATES ALL THE ABOVE MENTIONED ARTIFICIAL LIMITATION)
3. Enables High Performance Mode For aw87xx_SND_soc and Balanced the LR spks for indian MIUI users only
4.Enables Fast Charging.
5.Many more if u used u will know it better.
6.Bring back miui animation.
7.Set min clock-speed from 0.3 to 2.4 GHz on A73 and 0.3 to 1.9 GHz on A53 insted of 1.01 to 2.4 GHz on A73 and 1.1 to 1.9 GHz on A53
Note MIUI Camera, MIUI Gallery will be removed so use Gcam and Google Photos insted.
Flash both files via magisk reboot and enjoy
*I am not responsible for anything use at your own risk*
Click to expand...
Click to collapse
Bro I have tried this, the problem is not showing my UI (blank screen) and recent apps. Is there any solution
Karthikbiary said:
Bro I have tried this, the problem is not showing my UI (blank screen) and recent apps. Is there any solution
Click to expand...
Click to collapse
u must be in a11 official miui rom
Adi_777 said:
Can you make a mod for stereo speaker to sound equally
Click to expand...
Click to collapse
why not releasing it by today keep tracking on xda forum for Redmi Note 11 updates
QUALCOMM LEAKED SOURCE 🎃 said:
u must be in a11 official miui rom
Click to expand...
Click to collapse
...i have tried in a11 only (eu rom)
Karthikbiary said:
...i have tried in a11 only (eu rom)
Click to expand...
Click to collapse
other modules are conflicting it with ig
QUALCOMM LEAKED SOURCE 🎃 said:
other modules are conflicting it with ig
Click to expand...
Click to collapse
No there no other modules so can u tell in which rom u have tried this module
Karthikbiary said:
No there no other modules so can u tell in which rom u have tried this module
Click to expand...
Click to collapse
miui 13.0.8 based on a11 RGCINXM
Related
[GT-i9195][cm11] - [ROM](Feb.2016)&[kernel](ECOACTIVE & ECOPLUG)(OC/UV)(20151210)
This is a GT-I9195 CM11 kernel highly optimized to best possible performance and energy efficiency.
It may work on Slim (confirmed), AICP (confirmed) and Carbon Rom (confirmed) as well.
It will not work on any Samsung Stock based ROM.
- built from latest avalable CM sources
- CPU OC: 1998 Mhz (light: 1782 MHz) (default and max.)
- reworked freq- tables (unique 108 MHz-steps) for fast scaling
- CPU UV: -50mv (light: -25mv) (default, adjustable)
- GPU OC: freq steps changed to 192-400-608 MHz (light: 192-400-554 MHz)
- L2 OC/UV for extra performance (stock setting is a bottleneck, especially with OC)
- improved bus scaling
- RAM UV
- adjusted msm_thermal to prevent too much thermal throttling under heavy load
- added new "ECOACTIVE" governor and set as default
- added new "ECOPLUG" hotplug driver and set as default
- added FIOPS IO Scheduler and set as default
- added some more commonly used IO schedulers
- added fast random (and enabled via init.d)
- built with official gcc 4.8 with -O3 flags
"ECOACTIVE" is the ultimate governor for lag free performance and good battery life at the same time. It's based on interactive governor. It has a special input gain including the menu, home and back buttons. Separate input gain, fullspeed and eco/screen off phases minimize the use of high frequencys whithout slowing down the device noticably. The upscaling is more agressive during the input phase (default 1s). In the following fullspeed phase (default 10s, set to 0 for unlimited) full performance is allowed. The third phase is configured for battery saving usage while reading, watching videos, music listening or when the screen is off. This ensures maximum responsiveness and best gamig experience along with best possible battery life when reading, listening to music etc.
"ECOPLUG" is an alternative hotplug driver based on AutoSMP. It works much snappier on our device than the stock msm-mpdecision. On default setting second core is down when screen is off.
Everything is fully "pretweaked".
Flash from recovery, enyoy... no need to adjust anything via init.d or app.
Dont flash this kernel if you don't know how to fix problems after flashing !
Make a backup before flashing this kernel !
The hardware parameters are adapted near to the limits of my phone. This means this kernel will not work if your devices hardware cannot handle the OC/UV.
If you are lucky you run the fastest kernel available for your phone
If your phone doesn't run with the "lombartz kernel" you may try the "lombartz light kernel" with less agressive OC/UV.
My latest pure CM11 ROM build (Feb. 2016):
https://drive.google.com/open?id=0B-1RyGtdRvCwWEVfc0ZhTTRzdXc
If you use Xposed framework you need to flash XposedFix after ROM.
regards,
lombartz
...updated.
this kernel is amazing but i have a problem when i connect the smartphone at bluetooth radio. In this case my smartphone freeze and always reboot.
sorry for my english
Hi, thanks for yor feedback Have you already checked if you have the same problem with the last official CM11 kernel from 20150105 ?
regards,
lombartz
edit: tested with my laptop as bluetooth- speaker with no problems. My actual Version is heavily tweaked at the Moment but nothing changed with audio or bluetooth.
Anyone else with bluetooth- playback issues out there ?
edit: found a possible reason for the problem. hope it's fixed in new version (see OP)
Thank you for this. Any chance to include f2fs into the kernel?
bongster said:
Thank you for this. Any chance to include f2fs into the kernel?
Click to expand...
Click to collapse
It's already included, I tested it just now with my actual Version via USB OTG a d could read and write. It should also work with the 20150212 Version.
regards,
lombartz
lombartz said:
It's already included, I tested it just now with my actual Version via USB OTG a d could read and write. It should also work with the 20150212 Version.
regards,
lombartz
Click to expand...
Click to collapse
Strange. My data and cache partition are f2fs and with the f4ktion cm11 kernel all is working well, but after installation of your kernel I'm stuck at the boot logo.
bongster said:
Strange. My data and cache partition are f2fs and with the f4ktion cm11 kernel all is working well, but after installation of your kernel I'm stuck at the boot logo.
Click to expand...
Click to collapse
Here is a Version without OC/UV or other tweaks but with all CM Updates. Its about 20% slower than the tweaked Version but more actual than the V20150212.
If this one boots your phone doesn't like my OC/UV settings...
lombartz said:
Here is a Version without OC/UV or other tweaks but with all CM Updates. Its about 20% slower than the tweaked Version but more actual than the V20150212.
If this one boots your phone doesn't like my OC/UV settings...
Click to expand...
Click to collapse
Thank you very much! I will test it and report back! If I understand it right, f2fs support is also in stock cm11 kernel?
I never tried it...
bongster said:
Thank you very much! I will test it and report back! If I understand it right, f2fs support is also in stock cm11 kernel?
I never tried it...
Click to expand...
Click to collapse
Yes.
lombartz said:
Yes.
Click to expand...
Click to collapse
No luck. I also tried flashing the latest cm11 nightly with no luck.
If I remember right I've tried the stock kernel some time ago only formatting the cache partition and this didn't work either.
20150212 working nice with latest Carbon 4.4.4
can you please add option to underclock min CPU to 162/270 MHz?
spixy said:
20150212 working nice with latest Carbon 4.4.4
can you please add option to underclock min CPU to 162/270 MHz?
Click to expand...
Click to collapse
This is a technically useless placebo feature and doesn' t save any energy.
The HFPLL has to be used to get the lower frequencys and this will eat the saved energy.
br,
lombartz
bongster said:
No luck. I also tried flashing the latest cm11 nightly with no luck.
If I remember right I've tried the stock kernel some time ago only formatting the cache partition and this didn't work either.
Click to expand...
Click to collapse
Hmm, the reason is the fstab.qcom, /cache and /data is expexted to be ext4.
Can be changed but I dont know how to allow both fs at the moment.
lombartz said:
This is a technically useless placebo feature and doesn' t save any energy.
The HFPLL has to be used to get the lower frequencys and this will eat the saved energy.
br,
lombartz
Click to expand...
Click to collapse
hi, I dont know what HFPLL is (some high frequency PLL), but I trust you
but still, is more battery efficient to hold wakelock with 162MHz than with 384, no? (see my previous post)
But on theother hand, 50mW diference between 162 and 384 MHz isnt realy so large...
spixy said:
hi, I dont know what HFPLL is (some high frequency PLL), but I trust you
but still, is more battery efficient to hold wakelock with 162MHz than with 384, no? (see my previous post)
But on theother hand, 50mW diference between 162 and 384 MHz isnt realy so large...
Click to expand...
Click to collapse
I suppose you mean 50 mV ? The lower UV limit is reached at about 384 MHz anyway.
Youre right with hfpll. Only at 384 MHz the CPU runs with pll8.
If you undervolt @ 384 manually as much as possible you will find that you cannot go noticeably lower if you clock down further.
At the Moment I am testing other tweaks that should be more effective an give some extra performance.
bongster said:
No luck. I also tried flashing the latest cm11 nightly with no luck.
If I remember right I've tried the stock kernel some time ago only formatting the cache partition and this didn't work either.
Click to expand...
Click to collapse
If you like to you can test this. But please make a full backup before because i did not test it myself. I don't want to reformat my phone for f2fs at the moment.
If it boots you are a tester for all the new changes ...
This Version will not run with ext4 /cache and /data partitions.
lombartz said:
If you like to you can test this. But please make a full backup before because i did not test it myself. I don't want to reformat my phone for f2fs at the moment.
If it boots you are a tester for all the new changes ...
This Version will not run with ext4 /cache and /data partitions.
Click to expand...
Click to collapse
Thank you very much!
After app optimisation the phone reboots and after the reboot it hangs at the Samsung logo. Only recovering the old boot image helps. Don't know if the oc is the reason.
Update:
I've tried oc with f4ction kernel and had also a reboot. I guess my CPU is not the best.
bongster said:
Thank you very much!
After app optimisation the phone reboots and after the reboot it hangs at the Samsung logo. Only recovering the old boot image helps. Don't know if the oc is the reason.
Update:
I've tried oc with f4ction kernel and had also a reboot. I guess my CPU is not the best.
Click to expand...
Click to collapse
I am sorry. Should not publish something I did not test myself...
What OC Values did you use with f4ction ?
lombartz said:
I am sorry. Should not publish something I did not test myself...
What OC Values did you use with f4ction ?
Click to expand...
Click to collapse
No problem. I'm aware of the issues that can happen.
Normally I use f4ction as it is with 50uv. For the test I oc'ed to 1998mhz.
This is the Q&A thread for Helium.
You don't know where to post something? This schema will help you.
Questions about the kernel (Does it have ****?) > here
Problems you faced, and/or their solutions > here
Weird problems I could be able to solve > the development thread
Things I should read/know > the development thread
Questions that can be answered by any user (not only by me) > here
Miscellaneous posts > here
In a nutshell, if you have to post something that I have to read, post it in the development thread, otherwise use this thread.
I will not read this thread at all. Or maybe I'll check it every now and then
Mention me if I should read something.
Testing helium in temasek, for now all working right and cpu freq. goes to 1728Mhz. Very similar to last stock cm kernel but with usb fast charging :good:
I have a question @tommons (or sombody): Why do you include KSM? In Tangerine kernel it made the device laggy, increasing the power consumption due to the continous work of cpu cores and soon many of us saw that this feature wasn't good to our Xperia Sp. I always leave it off and better overall performance is achieved.
In init.d options of Kernel adiutor we can see the entry 01tangerine. Delete this entry is the same that going to /system/etc/init.d? I suppose that is.
BTW, great work and thanks for your dev time.
Alvichone said:
Testing helium in temasek, for now all working right and cpu freq. goes to 1728Mhz. Very similar to last stock cm kernel but with usb fast charging :good:
I have a question @tommons (or sombody): Why do you include KSM? In Tangerine kernel it made the device laggy, increasing the power consumption due to the continous work of cpu cores and soon many of us saw that this feature wasn't good to our Xperia Sp. I always leave it off and better overall performance is achieved.
In init.d options of Kernel adiutor we can see the entry 01tangerine. Delete this entry is the same that going to /system/etc/init.d? I suppose that is.
BTW, great work and thanks for your dev time.
Click to expand...
Click to collapse
KSM (in v2, UKSM) is there as an option. Nobody forces you to use it It uses more power but the result is a better RAM management.
Yes you can delete 01tangerine from Kernel Adiutor too.
Trying v2 with carbon 5.1.1 seems everything OK..good work man ;D
Sent from my Xperia SP using Tapatalk
Waiting eagerly to have it fully working on CM13.. Please @Tomoms hurry up :silly:
MizoSome said:
Waiting eagerly to have it fully working on CM13.. Please @Tomoms hurry up :silly:
Click to expand...
Click to collapse
Wait more or less 70 hours and you'll have it
I have tangerine 9.1 and CM12.1 on my device. Which steps i need to follow in order to have Helium?
Overclocking?
Can you build a overclocking option from this Kernel, In Tangerine Kernel my Cellphone is stucked on 1444 MHz on all gorvenors, Can you do it? A Overclocking to 1.94 GHz or more ?
pilger said:
I have tangerine 9.1 and CM12.1 on my device. Which steps i need to follow in order to have Helium?
Click to expand...
Click to collapse
Flash the stock boot.img of your CM build (if you have CM+Addons, it would be better if you flashed the boot.img of the Addons you have installed on your device), enter TWRP, install Helium.
Or, in an easier way, next time you update your CM nightly flash Helium instead of Tangerine!
JhonesMillionBR said:
Can you build a overclocking option from this Kernel, In Tangerine Kernel my Cellphone is stucked on 1444 MHz on all gorvenors, Can you do it? A Overclocking to 1.94 GHz or more ?
Click to expand...
Click to collapse
Overclock needs some work and I'm very busy at the moment. Frequency fixes will come very very soon. In the mean time you can flash v2.1, which hasn't got any issues with frequencies.
@Tomoms I am not able to install v2.2 on cm 12.1 using twrp it says unpacking kernel and nothing happens I have to hard reboot.anyone know how to solve this?
Helium Kernel v3
On Helium Kernel v3 the frequency is stucked on 1458 MHz on both cores on all gorvenors and I/O Schedulers.. :crying: :crying:
Image Link: http://tinypic.com/r/vcv2ft/9
JhonesMillionBR said:
On Helium Kernel v3 the frequency is stucked on 1458 MHz on both cores on all gorvenors and I/O Schedulers.. :crying: :crying:
Image Link: http://tinypic.com/r/vcv2ft/9
Click to expand...
Click to collapse
Good! Well, actually that's bad, but I expected it. Will fix ASAP (that is, unfortunately for you, on Sunday/Monday).
Use v2.1, it doesn't have problems.
For the others: I remind you that this doesn't mean v3 is buggy. This bug appears only on certain devices confused and mine is one of the "lucky" ones. So the best thing to do is to try v3 and see if you're lucky or unlucky. Hopefully, the bug will be fixed with v3.1.
JhonesMillionBR said:
On Helium Kernel v3 the frequency is stucked on 1458 MHz on both cores on all gorvenors and I/O Schedulers.. :crying: :crying:
Image Link: http://tinypic.com/r/vcv2ft/9
Click to expand...
Click to collapse
Same here
Sent from my Xperia SP using Tapatalk
Tomoms said:
Good! Well, actually that's bad, but I expected it. Will fix ASAP (that is, unfortunately for you, on Sunday/Monday).
Use v2.1, it doesn't have problems.
For the others: I remind you that this doesn't mean v3 is buggy. This bug appears only on certain devices confused and mine is one of the "lucky" ones. So the best thing to do is to try v3 and see if you're lucky or unlucky. Hopefully, the bug will be fixed with v3.1.
Click to expand...
Click to collapse
It will be that the kernel comes out today ? I'm anxious
JhonesMillionBR said:
It will be that the kernel comes out today ? I'm anxious
Click to expand...
Click to collapse
It's out
Helium Kernel v3.1
Tomoms said:
It's out
Click to expand...
Click to collapse
CPU frequency table finally fixed? Needs testing.
Test: Yes, All gorvernors and I/O Schedulers is working with 1944 MHz, Tested!
Thank you, Tomoms
Is TRIM support planned? I think that it is essential for device with such slow flash memory.
As for now I'm using heavily customized Tangerine 9.2 + last Xenon HD which gives great performance, but has issues (inaccurate GPS, big lag after locking the screen, touchscreen not working couple times a week and a few more). Tested latest CM12.1 + Helium 3.1 for few hours and it looks promising, but feels slower than much more bloated Xenon HD + Tk9.2 (used since September) possibly due lack of TRIM support.
michuroztocz said:
Is TRIM support planned? I think that it is essential for device with such slow flash memory.
As for now I'm using heavily customized Tangerine 9.2 + last Xenon HD which gives great performance, but has issues (inaccurate GPS, big lag after locking the screen, touchscreen not working couple times a week and a few more). Tested latest CM12.1 + Helium 3.1 for few hours and it looks promising, but feels slower than much more bloated Xenon HD + Tk9.2 (used since September) possibly due lack of TRIM support.
Click to expand...
Click to collapse
You can use the command line utility called fstrim or mount the partitions with the "discard" option. The latter way is more difficult because it requires unpacking the kernel, the ramdisk, and then repacking everything.
Swap crashing problem is resolved in v3.2?
Tomoms said:
You can use the command line utility called fstrim or mount the partitions with the "discard" option. The latter way is more difficult because it requires unpacking the kernel, the ramdisk, and then repacking everything.
Click to expand...
Click to collapse
I think that it was my mistake - I cannot remember if I enabled root before issuing TRIM - shame on me
I am using Trimmer utility and running it resulted in instant execution without returning trimmed size in gigabytes pointing that either root was not enabled or TRIM was not supported. Judging by your reply I can assume that TRIM is supported so I think that I'll make second attempt to CM12.1 when touchscreen issue is fixed* or CM13 when camera will be working.
* I just read that @Adrian DC fixes has been merged in 3.2! I will check that kernel as soon as I can! :angel:
Here's my release of a slightly modified kernel for Zuk Z2 Pro. It's all somewhat basic, but still, maybe someone is interested.
void3.5(oc): Old AEX4.5 Android 7.1 Nougat
void5.1bat is only for AEX 5.3.
void5(oc/ocx) for AEX 5.4 <= 0411
void5ocx-mracar: Special version for Cosmicos and RR before full treble (before April 18)
For AEX 5.4-0418 and similar full-treble vendor-partition-enabled ROMs (RR working!) use void5.4.
max GPU frequency raised from 624Mhz to 653MHz (710 for ocx-Edition)
Actually I wouldn't consider this as an overclock because 653Mhz is default for Snapdragon 821, which also has Adreno 530 GPU. Yields around +2-3k in Antutu 3D score, if you're not hitting temp throttling. For that, I've included a modified thermal-engine.conf, which simply makes sense because the default limits are ridiculously low imo. There is no danger involved anyway because there are additional kernel/hardware mechanisms in place to prevent serious overheating. In fact, thermal-engine.conf can be empty (like on RR), but I'd say it's a good idea to keep it in place and prevent the phone from getting uncomfortably hot to touch. It does get warm now though!
Westwood+ TCP congestion algorithm (default)
Supposedly superior for moblie devices, but well, who knows. This had to be benchmarked and profiled in great detail, which is a difficult thing to do. I've made it default anyway, mainly because it seems to be popular and I cannot notice any negatives so far.
Zen I/O scheduler (from dorimanx OP3T kernel)
As above, hard to quantify. But I don't like CFS/BFQ for mobile devices and am in fact leaning towards Deadline, which is also included. Kernel defaults to ZEN nevertheless, but note that this is probably overwritten by the ROM's custom startup scripts. Check with kernel tools like "Kernel Adiutor" and change to Zen if you want to give it a try.
(But beware of Kernel Adiutor - it doesn't quit cleanly and hogs cpu, at least sometimes. Check with some task manager app like "System Panel" and kill it!)
F2FS enabled (untested!)
People seem to be keen on F2FS, so I thought, why not include it. Note that AEX builds from 0825 onwards also have this by default. Untested, because I don't have any F2FS partitions. Might try it in the future though - certainly makes sense.
Cleanup kernel config / Optimize build options
Remove unecessary kernel config options, optimize build, silence debug syslog output.
Ignore specific min CPU frequency request from userspace
Well, yes, totally stupid. But I couldn't find any other way to "disable" AOSP CPU-boost on touchscreen interaction (or whatever it is called). I don't like this feature - we have input boost in the kernel for that. Trying to control CPU freqs from userspace is just no good idea imo.
(Actually... I'd suggest disabling kernel's input boost also. CPUs are fast, even the small cores, and there shouldn't be any noticable lag. And if so, tune/optimize scheduler and/or governor instead.)
This change certainly helps with battery life, but how much exactly... I don't know.
Voltage Control (from optimumpr)
Added voltage control through sysfs interface (/sys/devices/system/cpu/cpuX/cpufreq/UV_mV_table). Use for example Kernel Adiutor to tweak, but beware, undervolting _together_ with overclocking does not play well on this device.
Overclock-Xtreme-Edition (ocx)
CPU is raised to 1.80/2.32 GHz and GPU to 710 MHz (!). Bus speeds are also slightly increased and performance should be a bit better than what the small increase in pure CPU-speed might suggest.
Note that the ocx-kernel is really borderline and certainly depending on the specific phone. If it doesn't boot, blue-led-of-death, and/or random apps are crashing, just use the normal oc-edition. The difference is not that big and battery life of ocx is somewhat worse. This is just for fun!
Underclocked aka battery-optimized edition (bat)
CPU underclocked to 1.4/1.92 per default, GPU 510Mhz. Underclocks can be disabled on runtime, enabling 1.67/2.23 CPU and 653 MHz GPU, which is still oc'd compared to stock, but lower than ocx. To disable underclock:
Code:
echo 0 > /sys/module/msm_performance/parameters/void_underfreq
Big thanks to all involved kernel devs and especially davidevinavil for maintaining Z2 Pro for AEX. :good:
UPDATE 20180418 - void5.4bat - void5.4ocx - AEX/RR full treble with vendor partition
UPDATE 20180402 - void5.1bat Underclocked - AEX 5.3 only!
UPDATE 20180324 - void5oc - void5ocx
UPDATE 20170916 - void3.5 - void3.5oc - For AEX 4.5
3.3 adds a more extensive "tuning"-script, located in /system/etc/void_tuning.sh. This is executed after boot and activates the default profile qpwr. Here's a list of the available profiles with a short description:
qpwr: Goal is congesting tasks on the silver cores, kicking in the bigger cluster only when more capacity is needed. All this with focus on prolonged battery life. (default)
qperf: Somewhat similar to qpwr, but with focus on performance. Freqs ramp up faster and schedulers generally act more "quickly". You can use this for benchmarks, should give the best results, but in real life usage I think the benefits are really non-existent.
qmix: No, this is _not_ intended to strike a balance between pwr/perf. Instead, the idea is to distribute the load evenly across all cores, effectively keeping freqs on a lower level on average. I'm not sure yet how this turns out with regards to battery life, but on SD820/821 it might be a valid strategy. You know, power requirements for the golden and silver cores are about equal for any given freq and both are (nearly) equally efficient. A point against this strategy might be, at least in theory, that esp. the golden cores are more frequently prevented to enter deep sleep states, even during light usage. But well, I'm not sure how big the impact on battery life really is and whether the non-linear power characteristic of these cores make up for it. I am running/testing qmix myself right now...
Currently this is not working. Still trying to figure out how to run the script automatically on boot for these 8.1 ROMs. Ideas?
My suggestion as of now is to run the script manually. There might be some apps helping with that. /system/etc/void_tuning.sh. Just execute it.
BACKUP YOUR DEVICE BEFORE FLASHING THIS PACKAGE! (use latest TWRP for Oreo ROMs!)
I CANNOT GURANTEE IT WILL WORK UNDER ALL CIRCUMSTANCES, ESPECIALLY WITH PREVIOUSLY MODIFIED BOOTPARTITIONS / RAMDISKS / WHATEVER !!!
Kernel source: https://github.com/virtvoid/android_kernel_zuk_msm8996-1
Kernel source: https://github.com/virtvoid/android_kernel_zuk_msm8996-5
---
Other things worth mentioning:
o void5.4ocx Antutu 7.0.6 score on an idle AEX5.4-1704 system is expected to be around 172k, +- 2k. If not, then there's something hogging cpu. Try a reboot, let it settle down and/or check with some task manager app if you still cannot reach these scores.
CHANGELOG
20180418 void5.4ocx - void5.4bat
o Full Treble with vendor partition
o ocx-edition + bat-edition
o switched to cosmedd's kernel base (latest caf updates)
20180324 void5oc - void5ocx
o Linaro GCC 7.2.1
o oc-edition + ocx-edition
o DD3Boh kernel base
20170916 void3.5 - void3.5oc
o Linaro GCC 6.4.1
o Normal + OC-edition
o lots of small patches, mainly battery-related (see Github)
20170905 void3.3
o Hopefully fix camera slomo issue
o more extensive void_tuning.sh script
o drop series 1/2 kernels for now
20170830 void3.2
o Enable Qualcomm HMP scheduler
o some scheduler tuning (/system/etc/void_tuning.sh)
o Enable cpu overclocking as default
20170827 void1.2 - void2.2 - void3.1
o void1.2: Based on AEX kernel 0810 (and prior?)
o void2.2: Based on CallMESuper kernel from AEX 0820, completely different source
o void3.1: Based on AEX kernel 0825, which is somewhat of a rollback/remake/enhancement of 0810, afaict.
o update each branch to latest version
o Voltage Control
20170826 void2.1
o Tone down kcal default saturation a bit
o Linaro GCC 5.4.1 toolchain
o Optimized CFLAGS
o Add (back) a few config options
20170824 void2
o initial release
Thank you ! I already flashed it and it's working perfectly on AEX last version.
I'm thinking to keep your kernel definitively.
Bryandu13 said:
Thank you ! I already flashed it and it's working perfectly on AEX last version.
I'm thinking to keep your kernel definitively.
Click to expand...
Click to collapse
Thanks, great to hear. Have you tried enabling CPU overclocking?
void23 said:
Thanks, great to hear. Have you tried enabling CPU overclocking?
Click to expand...
Click to collapse
Yeah, It's the 1st thing I did and it's working normally
Envoyé de mon Z2 Pro en utilisant Tapatalk
Downloading, I want test it on RR 5.8.3 F2FS data and cache!
Ninnix96 said:
Downloading, I want test it on RR 5.8.3 F2FS data and cache!
Click to expand...
Click to collapse
Great, that's interesting. Tell us your findings!
void23 said:
Great, that's interesting. Tell us your findings!
Click to expand...
Click to collapse
bootloop , thanks for your work, I hope to test a new version soon!
Ninnix96 said:
bootloop , thanks for your work, I hope to test a new version soon!
Click to expand...
Click to collapse
Hmm...
I don't have any experience with F2FS partitions, but I'm going to try booting RR 8.5.3 with this kernel later...
void23 said:
Hmm...
I don't have any experience with F2FS partitions, but I'm going to try booting RR 8.5.3 with this kernel later...
Click to expand...
Click to collapse
The only version work with F2FS is 5.8.3 of 26/6
I can report that it works well with lineage-14.1-20170803-UNOFFICIAL so far.
No boot loop or other issues.
Ninnix96 said:
The only version work with F2FS is 5.8.3 of 26/6
Click to expand...
Click to collapse
Ok, I've just checked with 5.8.4, no F2FS partition, boots up fine. So it either has to do with F2FS partitions, and/or this specific 26/6 version of RR.
But testing this is a good opportunity to give F2FS a try. Give me a few days...
void23 said:
Ok, I've just checked with 5.8.4, no F2FS partition, boots up fine. So it either has to do with F2FS partitions, and/or this specific 26/6 version of RR.
But testing this is a good opportunity to give F2FS a try. Give me a few days...
Click to expand...
Click to collapse
No hurry you've done too much
@void23
Thanks for the excellent work. First time antutu crossed the 160k mark with ur kernel.
@void23
One issue though, camera is force closing. Have tried stock cam on AEX, Moto camera, PMS next mod camera and camera zoom FX. All FC.
Anyway to revert to AEX or another kernel short of flashing full ROM?
sanjay0501 said:
@void23
One issue though, camera is force closing. Have tried stock cam on AEX, Moto camera, PMS next mod camera and camera zoom FX. All FC.
Anyway to revert to AEX or another kernel short of flashing full ROM?
Click to expand...
Click to collapse
Just flash ROM again.
But in my case on AEX there is no problem.
Envoyé de mon Z2 Pro en utilisant Tapatalk
Bryandu13 said:
Just flash ROM again.
But in my case on AEX there is no problem.
Envoyé de mon Z2 Pro en utilisant Tapatalk
Click to expand...
Click to collapse
Dirty flashed AEX 2407 after dalvik and cache wipe again and then flashed void kernel, still camera FC
Now flashed AEX without void kernel and camera working.
Maybe some issues with my apps so will try a clean flash and see. Have been having frequent issues with battery drain also recently with AEX 4.5 2010 so flashed back to 2407 which seems to suit my phone better.
sanjay0501 said:
Dirty flashed AEX 2407 after dalvik and cache wipe again and then flashed void kernel, still camera FC
Now flashed AEX without void kernel and camera working.
Maybe some issues with my apps so will try a clean flash and see. Have been having frequent issues with battery drain also recently with AEX 4.5 2010 so flashed back to 2407 which seems to suit my phone better.
Click to expand...
Click to collapse
Sorry to hear about your camera FC'ing. For me, standard AEX cam and cameranextmod7 both are working flawlessly, so I can only suspect it has to do something with your specific AEX installation. A clean reflash of AEX 0820 should solve the issue.
I noticed I got worse pictures with CNMv7 after flashing this; re-flashed ROM without kernel, and now CNM is giving me great shots again.
In all other aspects, the kernel delivered. Scores were 20000-30000 higher than standard AEX.
Thanks for your efforts, working without problem!!!
Antutu 2nd run after reboot...Excellent scores, no OC.
The ProjectHiSi team with members @spirtix, @T1mb3 and @erayrafet presents you PEAK KERNEL for all devices using the HiSilicon HI3635 platform, e.g. Huawei P8, Honor 7 and more, running CyanogenMod 13, LineageOS 13 and LineageOS 14.1 (EMUI support is coming soon).
Features
Linux Kernel 3.10.108
Boeffla wakelock blocker
Improved headphone volume output
BFQ, FIOPS, Maple and ZEN I/O schedulers
OPTDEMAND and BLU_ACTIVE CPU governors
GPU_SCENE_AWARE governor
More GPU and DDR governors available
Fsync can be toggled on and off
ZRAM and KSM are disabled for better battery life
F2FS
Init.d support
EX Kernel Manager or Kernel Adiutor are recommended for management
Installation & Downloads
Get the latest PEAK build on GitHub: https://github.com/ProjectHiSi/android_kernel_huawei_hi3635/releases
Install the peak-xxx.zip file using TWRP or EX Kernel Manager
XDA:DevDB Information
PEAK KERNEL, Kernel for the Huawei P8
Contributors
erayrafet, T1mb3, spirtix, nexolight, AD2076, Speedo.thc, surdu_petru, haky 86, JBolho
Source Code: [url]https://github.com/ProjectHiSi/android_kernel_huawei_hi3635[/URL]
Status: Beta
Current Beta Version: 0.4
Beta Release Date: 2018-09-02
Created 2018-09-01
Last Updated 2018-09-10
Version 0.4 is up for testing.
What's new?
- OPTDEMAND and BLU_ACTIVE CPU governors
- GPU_SCENE_AWARE governor
- FIOPS and ZEN I/O schedulers
- More volume boost - needs testing
- Workque Power Efficiency on
https://github.com/ProjectHiSi/android_kernel_huawei_hi3635/releases
Version 0.5 is going to come with:
- Optimized MAPLE and GPU_SCENE_AWARE
- Fsync toggled
- General optimizations
Wait for the release.
https://github.com/ProjectHiSi/android_kernel_huawei_hi3635/releases
Hej, thanks for your work!!
I installed your kernel but noticed a faster battery drain. Maybe a point for your next release
Edit: btw, under your posted link is actually no 0.5 version available ?
Is there allready EMUI support? Will it work on P8MAX?
Hirs_E_Fruit said:
Is there allready EMUI support? Will it work on P8MAX?
Click to expand...
Click to collapse
No EMUI support for now.
I guess, it won't work on P8 Max because there isn't a Lineage OS ROM for it.
erayrafet said:
No EMUI support for now.
I guess, it won't work on P8 Max because there isn't a Lineage OS ROM for it.
Click to expand...
Click to collapse
But if there will be EMUI support it should work since its the same SoC?
Hirs_E_Fruit said:
But if there will be EMUI support it should work since its the same SoC?
Click to expand...
Click to collapse
There are plans for it, but I can't say anything concrete for now.
any ETAs of the next version? Its been a dozen days..
thank all devs for your amazing works, you guys are the only reason im still holding this antique device
Hi,
Thank you for this kernel. I have a question, i'm using Huawei P8 and how can i change cpu and gpu settings? I use Ex Kernel Manager but all settings are grayed out Or it's not possible to overclock cpu and gpu?
Hellah said:
Hi,
Thank you for this kernel. I have a question, i'm using Huawei P8 and how can i change cpu and gpu settings? I use Ex Kernel Manager but all settings are grayed out Or it's not possible to overclock cpu and gpu?
Click to expand...
Click to collapse
Do you have root access? Also, no overclocking here.
erayrafet said:
Do you have root access? Also, no overclocking here.
Click to expand...
Click to collapse
Yep, i do. Also i installed CM 13 and thought i will be able to overclock cpu or atleast change cpu profile to make phone a little faster but there is no performance option in setting nor i can change anything under EX Kernel Manager
EDIT: Ha, okay, false information. My phone is not rooted or at least not rooted properly, that's what root check apps say. So hm... i dunno what to do. Could it be because my phone is not properly rooted?
EDIT2: Okay, i solved this thing. Had to install supersu once more to make it work properly. Now under EX Kernel Manager i can change powersave and performance values but again, how to make it to work because cpu profile is still interactive and i dunno where and how to change it
Hellah said:
Yep, i do. Also i installed CM 13 and thought i will be able to overclock cpu or atleast change cpu profile to make phone a little faster but there is no performance option in setting nor i can change anything under EX Kernel Manager
EDIT: Ha, okay, false information. My phone is not rooted or at least not rooted properly, that's what root check apps say. So hm... i dunno what to do. Could it be because my phone is not properly rooted?
EDIT2: Okay, i solved this thing. Had to install supersu once more to make it work properly. Now under EX Kernel Manager i can change powersave and performance values but again, how to make it to work because cpu profile is still interactive and i dunno where and how to change it
Click to expand...
Click to collapse
From the side menu go to the CPU section. There you will have options for governors and CPU frequencies.
Looks like i had to reboot my phone to make advanced settings in EX Kernel Manager to work. Now i see everything. Gonna test it now.
Thank you so much for your help!
hi~ I've been using peak kernel for weeks and I'd say it's stable and great.
The wifi bonding feature seems not working. I don't know if I had misunderstand it,but wouldn't the wifi speed be 144Mbps?The current speed is still 72mbps.
Besides, the frequency of the little cluster is almost always 1516mhz/1209mhz and never runs at 403mhz.
Btw, the current released version is still 0.4 not 0.5 as OP.
Thank you all devs!:good:
TensorLake said:
hi~ I've been using peak kernel for weeks and I'd say it's stable and great.
The wifi bonding feature seems not working. I don't know if I had misunderstand it,but wouldn't the wifi speed be 144Mbps?The current speed is still 72mbps.
Besides, the frequency of the little cluster is almost always 1516mhz/1209mhz and never runs at 403mhz.
Btw, the current released version is still 0.4 not 0.5 as OP.
Thank you all devs!:good:
Click to expand...
Click to collapse
You can't force the phone to use 40 MHz networks. But you can do it from your router settings instead. Also, v0.5 was in testing, but we haven't released it yet. It seemed to be stable, so I will publish it soon.
I did successfully installed LineageOS for P8 on my P8 Max. It boots okay, graphics and touch screen are working. But WiFi and cellular are not. Is it related to kernel driver settings or the android firmware?
is there a way to install the official kernel?
Regards
Stefano
wes93 said:
is there a way to install the official kernel?
Regards
Stefano
Click to expand...
Click to collapse
Recover your backup (only boot)
Or flash stock boot.img (what ever rom you use)
T1mb3 said:
Recover your backup (only boot)
Or flash stock boot.img (what ever rom you use)
Click to expand...
Click to collapse
Thanks a Lot.
Hello,
I started making kernel builds again.
CHECK BELOW FOR IMPORTANT INFORMATION!
YOU MUST USE MIUI Q FIRMWARE PACKAGE FOR THIS KERNEL TO WORK. OTHERWISE YOU'LL END UP IN FASTBOOT MODE FOREVER.
Camera won't work on a lot of ROMs due to imcompatible camera drivers in the kernel. This kernel uses a patch for MIUI Stable 11.0.4 release, which introduced updated camera blobs back in Android Pie. Double check, whether your ROM uses these blobs. MIUI Q uses different blobs too, thus won't work until Xiaomi releases it's kernel source code.
FLASH THIS BEFORE FLASHING MY KERNEL. I UPLOADED FIRMWARE PACKAGE FOR YOUR CONVENIECE!
DOWNLOAD LINK FOR MIUI Q FIRMWARE PACKAGE
Flashing procedure is standard - through recovery. Magisk is optional, only if you want root.
*big thanks to rama982 for possible insights and some help from his side*
*nathanchance for android-linux stable and helping upstream our kernels*
*franciscofranco for commits that made our phone happier and snappier*
*sultanxda for his beastly development in Android scene and ridiculous understandment in kernels in general*
*also thanks to osm0sis for Anykernel3. Without this, flashing kernels would be a harder process to do*
XDA:DevDB Information
JellyKernelAlpha, Kernel for the Xiaomi Redmi Note 7
Contributors
airidosas252, rama982, nathanchance, Qualcomm, Code Aurora Forums, osm0sis, other developers
Source Code: https://github.com/airidosas252/Xiaomi_Kernel_OpenSource
Kernel Special Features: Stability, latest kernel sources
Version Information
Status: Testing
Created 2019-11-22
Last Updated 2020-02-01
DOWNLOAD LINK FOR GITHUB RELEASES
Due to different kernel base, older releases are irrelevant from now on.
UPDATE: I added a link for MIUI Q firmware package in the OP. Check it out and remember to flash it first before flashing my kernel. Thanks.
-------------------------------CHANGELOG------------------------------
Jelly Kernel Alpha 1.1.1 Hotfix
ALSA: pcm: Add missing copy ops check before clearing buffer (bootloop after voip videocall should be gone now)
-----------------------------------------------------------------------------------------
Jelly Kernel Alpha 1.1 beta release
IMPORTANT INFO! Camera won't work on a lot of ROMs due to imcompatible camera drivers in the kernel. This kernel uses a patch for MIUI Stable 11.0.4 release, which introduced updated camera blobs back in Android Pie. Double check, whether your ROM uses these blobs. MIUI Q uses different blobs, thus won't work until Xiaomi releases it's kernel source code.
If this kernel is not booting for you (going straight to fastboot mode), you need to use MIUI Q firmware package.
Changelog:
*Bringup for Clang 10 and it's now compiled with Clang 10
*Using LZ4 compression for zRAM
*Forcefully load modules (this should fix Wi-Fi problems on various ROMs)
*Rapid GC for F2FS filesystem
*Added fsync and crc check switches
*kgsl fixes and optimizations included
*Introduce additional NEON accelerated arm64 routines
*cfq io scheduler fixes and optimizations
*Tick rate increased to 300HZ for improved responsiveness
*CPU mask affinity set to 4 cores for improved efficiency
*Enabled F2FS filesystem support with encryption
*F2FS fixes
*Increased slmk's aggression rate to 192MB per app kill
*Enabled Dolby DS2 audio standard
*And more I don't really remember, check commit history for more detailed changes
-----------------------------------------------------------------------------------------
Jelly Kernel Alpha 1.0 beta release (don't use this release, it's deprecated)
*Complete rebase on jasmine's Q tag.
*Linux 4.4.211
*Adrenoboost enabled and set on low parameter
*Workqueques reworked for better responsiveness and lower power consumption
*Small UV for both CPU and GPU
*CPU Bitmasking
*DTB debloat (reduced kernel's footprint)
*LA.UM.8.2.r2-00600-sdm660.0 CAF tag
*Using older Wi-Fi CAF tag for better down/up speeds
And more stuff I don't remember.
-----------------------------------------------------------------------------------------
DISCLAIMER:
-There will be 1-3 kernel builds per week, unless there's nothing I can improve, then builds will be as is.
-Anyone, who has tested it already, give me some feedback in the comments.
-If you get freezes, crashes, restarts, write me up with a attached dmesg, log, anything, that can give me a clue what's wrong. Thanks. Happy JellyKernel'ing ^^
Where is the download link?
Zulwiczek1983 said:
Where is the download link?
Click to expand...
Click to collapse
Use the browser - there's a section DOWNLOADS above the thread. There you will find my kernel build. Cheers.
Zulwiczek1983 said:
Where is the download link?
Click to expand...
Click to collapse
Here, for short: https://forum.xda-developers.com/devdb/project/dl/?id=32079
NEW BUILD IS AVAILABLE NOW!
Check higher posts for download link. Happy flashing!
airidosas252 said:
NEW BUILD IS AVAILABLE NOW!
Check higher posts for download link. Happy flashing!
Click to expand...
Click to collapse
Does it support Kcal? Regards :good:
rubentkato77 said:
Does it support Kcal? Regards :good:
Click to expand...
Click to collapse
Yes it does. Look up using kernel manager.
airidosas252 said:
Yes it does. Look up using kernel manager.
Click to expand...
Click to collapse
Thnk you, will flash to test :good:
Is the any chance to get the turbo frequencies on the GPU?
I read that on some other page I can't remember where, can you please why that supposed frequency is not on the stock kernels, does it take to much energy?
tekkaman7 said:
I read that on some other page I can't remember where, can you please why that supposed frequency is not on the stock kernels, does it take to much energy?
Click to expand...
Click to collapse
I believe Qcom left off this frequency just because CPU is already close to some of their flagship SOCs in terms of CPU performance.
Everything in the source code is left done, you just need to modify a code a bit and you have higher frequency. If you want to go any higher, you would need to modify the code a lot more. Tried it and gave up on that.
It could be anything, really.
Moreover, you don't see too many phones using this exact SOC.
P.S. Funny thing though, this OC feels like placebo effect, like CPU is running faster but it's really not.
Think about it, when sdm660 came out, it was between SD821 and SD835 in terms of CPU performance. GPU is more or less the same as Adreno 430.
Gonna release new kernel build soon.
Still working out some quirks I come up every once in the while.
Stay tuned for news. Good day.
airidosas252 said:
Gonna release new kernel build soon.
Still working out some quirks I come up every once in the while.
Stay tuned for news. Good day.
Click to expand...
Click to collapse
Thanks for your work, we will waiting :good:
NEW KERNEL BUILD AVAILABLE NOW!
As usual, check main page for a download link. Happy flashing!
airidosas252 said:
NEW KERNEL BUILD AVAILABLE NOW!
As usual, check main page for a download link. Happy flashing!
Click to expand...
Click to collapse
thank you, downloading. :good:
Overclocked? Using Evira for now on MIUI 11 Pie, but Evira is outdated..... Can't support Android 10
So, hope can have Overclocked kernel support Android 10
xiaomi.lim said:
Overclocked? Using Evira for now on MIUI 11 Pie, but Evira is outdated..... Can't support Android 10
So, hope can have Overclocked kernel support Android 10
Click to expand...
Click to collapse
Yep, it's overclocked and it's for Android 10.
I've seen people running this with MIUI too.
airidosas252 said:
Yep, it's overclocked and it's for Android 10.
I've seen people running this with MIUI too.
Click to expand...
Click to collapse
Overclocked to ? 2.46GHz?
xiaomi.lim said:
Overclocked to ? 2.46GHz?
Click to expand...
Click to collapse
Yes, but I don't think I'll keep the OC for much longer. I really don't see the benefit of it.
Phone is already really fast and snappy.
I did a build with stock clocks and compared it to the OC one. And here's the surprise - there isn't almost any difference.
I fixed several known issues which bugged me a lot and those seem to remedy all of the problems I had.
Moreover, I hate overbloated kernels with features I don't use. I like being clean and compact.
Hi, the sound control (for speaker, earpiece and headphones) available or do you plan to add it in future? They get pretty handy really. I do appreciate keeping the kernel without much bloat though. : D