Database Develop

[GT-i9195][cm11] - [ROM](Feb.2016)&[kernel](ECOACTIVE & ECOPLUG)(OC/UV)(20151210)

[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.

[KERNEL][CM12.1][Linaro 4.9] EvoMix Kernel for CyanogenMod 12.1 based ROMs

This is a kernel for Cyanogen Mod 12.1, which is based on the EvoMix kernel by Alx31TLse, olivieer and SuperHanss (full credits to them). It is compiled by a Linaro 4.9.3 toolchain, which was optimized for Cortex A9 CPUs (thanks to Christopher83). It has a focus on stability, performance, endurance and overclock-ability (roughly in that order).
It uses the original ramdisk of the installed kernel (thanks to osm0sis), for maximum compatibly in the long run and instant adaptability to most source changes of CM. For now, it probably only works with the very latest unofficial CM12.1 built by qsnc (http://forum.xda-developers.com/showpost.php?p=58006383&postcount=1), due to the introduction of new sensor drivers! It should now works with other CM12.1 based ROMs, like crDroid and PAC, too. Please don't report bugs to qsnc, if you are using this kernel!
Features:
CPU: over/under-clock 1728MHz-192 MHz possible
governors: ondemand(plus), intelliactive, wheatley, ElementalX, ...
GPU: over/under-clock 487MHz-27MHz
governors: simple, performance, powersave, ondemand, conservative
File-systems: ext2/3/4, F2FS, exFAT, NTFS
Schedulers: noob, deadline, row, cfq, bfq, sio, fiops, zen, vr
intelli-plug hot-plugger and power saver (disable MPDecision first!)
Voltage Control (OC/UV)
Sound Control 3.x
poweramp controls (loudness enhancements)
screen colour tweaks
full NEON support
KSM support (Kernel Samepage Merging)
multicore power saver (recommended: enabled)
multirom compatibility
...
Performance: about 10% faster than original CM12.1-kernel with same settings, and some additional 20% speed by using maximum over-clocked frequencies (use at your own risk, every device is different!)
Configuration: Kernel Adiutor (https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor) or PerformanceControl 2.2.6 (http://forum.xda-developers.com/devdb/project/?id=600#downloads)
Install: just flash the attached zip with CyanogenMod Recovery, TWRP (http://forum.xda-developers.com/xpe...very-twrp-2-8-7-0-pollux-polluxwindy-t3187811) or CWM
Install a custom recovery first! The simple CyanogenMod Recovery, which comes with most ROMs, is pretty useless anyway..
Uninstall: re-flash the complete ROM (just re-flashing the original kernel is not enough!)
Sources: https://github.com/EvoMix/kernel_apq8064 (to obtain the defconfig: run "unpigz -cd /proc/config.gz")
Special thanks to Alx31TLse for his help and permission to post it!
Changelog:
2015-08-23:
rebuild using latest optimized Linaro 4.9.4 compiler by Christopher83
re-signed zip-file in order to make it compatible to file signature verification
refuses now to be installed by CyanogenMod Recovery
2015-06-13:
added Pollux version (use official nightly or recent unofficial build)
fixed bug in Sound Control's loudness enhancement, that only one speaker worked
removed inteli-active governor, due to random reboots
2015-05-31:
enhanced boot speed and file-system performance
buggy auto-hotplugger removed
reintroduction of CM's MPDecision (re-flash CM12.1 first, before installation!)
2015-05-28:
initial release
IF INSTALLATION FAILS: If the kernel installation is not working (i.e. installation takes less than 5 seconds and you don't see the new bootlogo), reflash latest ROM, reboot into recovery and try to install the kernel again!
XDA:DevDB Information
EvoMix Kernel for CyanogenMod 12.1, Kernel for the Sony Xperia Tablet Z
Contributors
BlackAfghan, Alx31TLse, olivieer and SuperHanss
Source Code: https://github.com/EvoMix/kernel_apq8064
Kernel Special Features: CM12.1 EvoMix kernel, compiled by a Linaro toolchain, which supports OC/OV, intelli-plug, Sound Control, NTFS, exFAT, F2FS, NEON, KSM, ...
Version Information
Status: Stable

Just installed latest unofficial CM12.1 built by qsnc and this kernel. Seems great so far! Boots a lot faster and kritika plays faster!
I'm trying the overcloacking with Kernel Adiutor set to 1728MHz, I've to 3C widgets installed to monitor temperature and such. Great job!

May seem a bit offtopic but how is the combination intelliplug-ondemandplus?
I think i get some lag with this but it may be a placebo

pangiotis24 said:
May seem a bit offtopic but how is the combination intelliplug-ondemandplus?
I think i get some lag with this but it may be a placebo
Click to expand...
Click to collapse
First, I also used this combination, but experienced some lag, too. It is not necessary to enable intelliplug and I'm not sure if it does any good, since hot-plugging is handled by auto_hotplug. Actually it is not even included in the original EvoMix kernel.
I'm now using only intelliactive, which seems to keep the frequencies low most of the time, while producing only minimal lag.
But maybe it is really a matter of believe..

Teella said:
I'm trying the overcloacking with Kernel Adiutor set to 1728MHz, I've to 3C widgets installed to monitor temperature and such. Great job!
Click to expand...
Click to collapse
The over-clocking capabilities of the EvoMix kernel are rather conservative. I personally use it with maximum CPU and GPU frequencies and even a general -50mV under-voltage, and it seems to be perfectly stable. But no guarantee, every device is different!

Thanks for Kernel !
Multirom Patch inclusive ?

phillipssat said:
Thanks for Kernel !
Multirom Patch inclusive ?
Click to expand...
Click to collapse
Yes, I think so. But please try it out and confirm if it works, since I have not tested it!

BlackAfghan said:
First, I also used this combination, but experienced some lag, too. It is not necessary to enable intelliplug and I'm not sure if it does any good, since hot-plugging is handled by auto_hotplug. Actually it is not even included in the original EvoMix kernel.
I'm now using only intelliactive, which seems to keep the frequencies low most of the time, while producing only minimal lag.
But maybe it is really a matter of believe..
Click to expand...
Click to collapse
Traced the cause.After some time with intelliplug+ondemandplus cores 2,3,4 are permanently disabled.Now i am on intelliactive.Very good so far

I've been using Wheatley and OC 1728 for couple days now. No lag, no heat issues, everything is just peachy!

Hi! Can I use this kernel on my sgp321 Pollux? Tried to flash but get error.

Pollux build will be released later...

New build in first post!
pangiotis24 said:
Traced the cause.After some time with intelliplug+ondemandplus cores 2,3,4 are permanently disabled.Now i am on intelliactive.Very good so far
Click to expand...
Click to collapse
Could you please retry it with the new version?
bgx said:
Hi! Can I use this kernel on my sgp321 Pollux? Tried to flash but get error.
Click to expand...
Click to collapse
If you, or anybody else, is able to re-flash the original CM12.1 kernel via fastboot (in case something goes wrong) and is willing to beta-test, write me a PM!

Yes its kexec patched, but we need to make tab z official to multirom app support, problem is...im running out of time, full time job, 10 months old baby ...kernel is time consumer, thanks to BlackAfgan to maintaining it.
More goodies to come
Tapatatrached from my Yuga

So apparently my tablet hates me. I can't get this kernel to actually flash for ****. I'm using the 5/27 CM 12.1 from the OP. Tried both versions of the kernel. It acts as if it flashes but is much too fast and the kernel version is the same. TWRP 2.8.5.0 from the OP link too.
EDIT: Nevermind I guess. Moved it to the root of the internal and renamed it to a shorter filename and it pushed it properly. No idea what was going on.

DarkStarr said:
So apparently my tablet hates me. I can't get this kernel to actually flash for ****. I'm using the 5/27 CM 12.1 from the OP. Tried both versions of the kernel. It acts as if it flashes but is much too fast and the kernel version is the same. TWRP 2.8.5.0 from the OP link too.
Click to expand...
Click to collapse
Try to format /system, reflash CM 12.1, reboot into recovery again, then flash the latest kernel, please.

Alx31 said:
Yes its kexec patched, but we need to make tab z official to multirom app support, problem is...im running out of time, full time job, 10 months old baby ...kernel is time consumer, thanks to BlackAfgan to maintaining it.
More goodies to come
Tapatatrached from my Yuga
Click to expand...
Click to collapse
Great! Thanks for your excellent work. I wish you all the best for your family! They are more important than any device..

BlackAfghan said:
Try to format /system, reflash CM 12.1, reboot into recovery again, then flash the latest kernel, please.
Click to expand...
Click to collapse
Yea I had done that. It only worked after moving it. I also renamed it at the same time so I dunno which fixed the issue.

DarkStarr said:
Yea I had done that. It only worked after moving it. I also renamed it at the same time so I dunno which fixed the issue.
Click to expand...
Click to collapse
I had the same problem, especially when I flashed an already flashed kernel. I never found the actual reason, but at one point it started to work perfectly all the time..
This is due the pretty complicated process of splitting the original kernel of and recreating the new one in real time, on the device. Normally the developer does this on his PC, and releases a directly flashable combination of the actual kernel and a custom ramdisk.
If other people have the same problem persistently, I may publish an conventional kernel. Please report!

Does this work on "[Rom][UB][5.1.x][SGP311]☆Dirty Unicorns v9.3☆ Unofficial +EvoMix Kernel" rom??

So i tested the latest version.I use intelliplug+intelliactive
No issues so far.Intelliplug is shutting down cores faster which will propably save some juice
Also feels a little colder than before when gaming(asphalt 8)

Very slow & laggy Nougat install

I upgraded my Touchpad to Latest version of Nougat yesterday.
However as soon as I started loading a few basic apps it started to not respond at all & ends up having to be continually rebooted. It's slightly better now but still has to be rebooted every so often & very often locks up for 30-60 seconds at a time.
I've checked all available space on storage & appears to be all correct with what was in the instructions, plus this was a clean install (the upgrade from kitkat was even worse!) & was done via TWRP with latest ROM, GAPPS etc. I'm aware Nougat is not the finished article but judging by other comments on the forum their experience is somewhat better than mine (using the TP right now us very frustrating).
This is being installed on a 32mb TP so storage isn't an issue at all. I've done a number of upgrades over the last few years but this is the first time I've run into these sort of problems.
Any help or suggestions would be greatly appreciated.
Thanks
Dellboy17

Exact same issue i am also facing.if somebody installed a fluidic rom means tell me ivwill also follow.

What's a fluidic ROM?

Dellboy17 said:
What's a fluidic ROM?
Click to expand...
Click to collapse
i think they mean 'one that operates in a fluid (smooth) manner'. i also have this problem on most n rom's i've tried, but addmittedly, my touchpad is near nand exhaustion. (and something about the N setups i've tried exacerbates it)

Evervolv 7.1.x lag fix
Dellboy17 said:
I upgraded my Touchpad to Latest version of Nougat yesterday.
However as soon as I started loading a few basic apps it started to not respond at all & ends up having to be continually rebooted. It's slightly better now but still has to be rebooted every so often & very often locks up for 30-60 seconds at a time.
I've checked all available space on storage & appears to be all correct with what was in the instructions, plus this was a clean install (the upgrade from kitkat was even worse!) & was done via TWRP with latest ROM, GAPPS etc. I'm aware Nougat is not the finished article but judging by other comments on the forum their experience is somewhat better than mine (using the TP right now us very frustrating).
This is being installed on a 32mb TP so storage isn't an issue at all. I've done a number of upgrades over the last few years but this is the first time I've run into these sort of problems.
Any help or suggestions would be greatly appreciated.
Thanks
Dellboy17
Click to expand...
Click to collapse
Sivabalan said:
Exact same issue i am also facing.if somebody installed a fluidic rom means tell me ivwill also follow.
Click to expand...
Click to collapse
speakxj7 said:
i think they mean 'one that operates in a fluid (smooth) manner'. i also have this problem on most n rom's i've tried, but addmittedly, my touchpad is near nand exhaustion. (and something about the N setups i've tried exacerbates it)
Click to expand...
Click to collapse
Hey guys install Shumash's SKZ Kernel and apply the following changes below, your user experience should drastically improve.
Extras: SKZ-OC Kernel recommended for Evervolv 7.1.x
[KERNEL]SKZ Overclock Kernel for Evervolv [1836KHz CPU/320MHz GPU]
Install notes:
-Install the SKZ-Kernel by flashing this zip file here through TWRP recovery
-Remove the Kernel by flashing a Evervolv ROM with TWRP recovery
-Enable Root permissions by flashing this Supersu v2.46 zip here with TWRP recovery
-You will need to update the Superuser binaries once your system boots.
-Install the Kernel Adiutor app to Overclock your CPU here
Recommended settings:
Note: These settings should fix the lag and touchscreen issues.
CPU
Set on boot = on
CPU Maximum Frequency = 1728MHz
CPU Minimum Frequency = 648MHz
CPU Governor = smartmax or dancedance
Schedule workqueues on awake CPUs to save power = enabled
CPU Hotplug
IntelliPlug = enabled
GPU
Apply on boot = on
GPU 2D Maximum Frequency = 266MHz
GPU 3D Maximum Frequency = 320MHz
GPU Governor = simple
I/O Scheduler
Scheduler = enabled
Scheduler = tripndroid
Kernel Samepage Merging
Kernel Samepage Merging = enabled
Low Memory Killer
Adaptive Low Memory Killer = enabled
Profile = aggressive
Misc
TCP Congestion Algorithm = sociopath

RolandDeschain79 said:
--SNIP--
[KERNEL]SKZ Overclock Kernel for Evervolv [1836KHz CPU/320MHz GPU]
--SNIP--
Click to expand...
Click to collapse
Note that while you can download the most current kernel from the links given, the thread is no longer being updated.

Devs Base note in the OP
shumash said:
Note that while you can download the most current kernel from the links given, the thread is no longer being updated.
Click to expand...
Click to collapse
Would it be possible to mention this in the OP of your old thread? Every time I add links to devs base the mods remove it here at XDA :silly:
Edit: Also worth mentioning that increasing the min CPU frequency to 600+ will help with the Evervolv lag issues.
Info about the move to Devs base for all those who haven't heard.

RolandDeschain79 said:
Would it be possible to mention this in the OP of your old thread? Every time I add links to devs base the mods remove it here at XDA :silly:
Edit: Also worth mentioning that increasing the min CPU frequency to 600+ will help with the Evervolv lag issues.
Info about the move to Devs base for all those who haven't heard.
Click to expand...
Click to collapse
wilco

speakxj7 said:
i think they mean 'one that operates in a fluid (smooth) manner'. i also have this problem on most n rom's i've tried, but addmittedly, my touchpad is near nand exhaustion. (and something about the N setups i've tried exacerbates it)
Click to expand...
Click to collapse
Yes correct!!
---------- Post added at 11:02 PM ---------- Previous post was at 10:57 PM ----------
RolandDeschain79 said:
Hey guys install Shumash's SKZ Kernel and apply the following changes below, your user experience should drastically improve.
Extras: SKZ-OC Kernel recommended for Evervolv 7.1.x
[KERNEL]SKZ Overclock Kernel for Evervolv [1836KHz CPU/320MHz GPU]
Install notes:
-Install the SKZ-Kernel by flashing this zip file here through TWRP recovery
-Remove the Kernel by flashing a Evervolv ROM with TWRP recovery
-Enable Root permissions by flashing this Supersu v2.46 zip here with TWRP recovery
-You will need to update the Superuser binaries once your system boots.
-Install the Kernel Adiutor app to Overclock your CPU here
Recommended settings:
Note: These settings should fix the lag and touchscreen issues.
CPU
Set on boot = on
CPU Maximum Frequency = 1728MHz
CPU Minimum Frequency = 648MHz
CPU Governor = smartmax or dancedance
Schedule workqueues on awake CPUs to save power = enabled
CPU Hotplug
IntelliPlug = enabled
GPU
Apply on boot = on
GPU 2D Maximum Frequency = 266MHz
GPU 3D Maximum Frequency = 320MHz
GPU Governor = simple
I/O Scheduler
Scheduler = enabled
Scheduler = tripndroid
Kernel Samepage Merging
Kernel Samepage Merging = enabled
Low Memory Killer
Adaptive Low Memory Killer = enabled
Profile = aggressive
Misc
TCP Congestion Algorithm = sociopath
Click to expand...
Click to collapse
Thanks buddy!! Actually fed up with the lag issue I have reverted to milaq's kikat 4.4.4. . Tonight will revert back to evervolv and will update here.
One doubt as the min cpu freq is 648 mhz will it not eat in to the battery??
Thanks,
Sivbal.

Sivabalan said:
Yes correct!!
---------- Post added at 11:02 PM ---------- Previous post was at 10:57 PM ----------
Thanks buddy!! Actually fed up with the lag issue I have reverted to milaq's kikat 4.4.4. . Tonight will revert back to evervolv and will update here.
One doubt as the min cpu freq is 648 mhz will it not eat in to the battery??
Thanks,
Sivbal.
Click to expand...
Click to collapse
Have flashed the latest test build and applied the above settings . its better now . will report after some days of usage.

Thanks for testing
Sivabalan said:
Have flashed the latest test build and applied the above settings . its better now . will report after some days of usage.
Click to expand...
Click to collapse
Thanks for testing it out and reporting back:highfive: I've found the battery drain is only slightly higher but fixing some of the lagging is worth the trade off.

RolandDeschain79 said:
Thanks for testing it out and reporting back:highfive: I've found the battery drain is only slightly higher but fixing some of the lagging is worth the trade off.
Click to expand...
Click to collapse
Also in toolbox if I disable aosp mode,the touchpad become very laggy and YouTube is not at all responding. But if we enbale aosp mode and disable all toolsbox functions...touchpad is useable.

Guys now after a long time I formatted my data and all the partitions then installed the evervolv 7.1.2 test build. Skz kernel overclocked to 1728. Also gpu overcolcked to 320. Kernel samepage killing enabled.cpu profile set to interactive. The rom is performing good. Please try.
Sent from my Touchpad using Tapatalk
---------- Post added at 09:56 AM ---------- Previous post was at 09:49 AM ----------
shumash said:
Note that while you can download the most current kernel from the links given, the thread is no longer being updated.
Click to expand...
Click to collapse
Guys now after a long time I formatted my data and all the partitions then installed the evervolv 7.1.2 test build. Skz kernel overclocked to 1728. Also gpu overcolcked to 320. Kernel samepage killing enabled.cpu profile set to interactive. The rom is performing good. Please try.
Sent from my Touchpad using Tapatalk

Is this much better than the Android 6 builds? The last decent one I had was JCSullins 5.1, my current 6.0.1 (22/08/2016) takes 2-3 longer to start up, is noticeably slow/laggy and has no USB OTG support. I notice that the Android 7 builds have no camera, Bluetooth and I need to overclock to have a good experience? I might go back to 5.1 again...

theronkinator said:
Is this much better than the Android 6 builds? The last decent one I had was JCSullins 5.1, my current 6.0.1 (22/08/2016) takes 2-3 longer to start up, is noticeably slow/laggy and has no USB OTG support. I notice that the Android 7 builds have no camera, Bluetooth and I need to overclock to have a good experience? I might go back to 5.1 again...
Click to expand...
Click to collapse
The newer evervolv builds have both working camera and Bluetooth but yes I'd recommend getting shumash's kernel and overclocking for the best experience. However if you're already using CM12 try updating to Milaqs latest builds here It might fix the issues you're having. I generally find Milaqs CM11 to be the most stable rom for your daily driver. Let me know how the newer builds of CM12 workout for you.

RolandDeschain79 said:
The newer evervolv builds have both working camera and Bluetooth but yes I'd recommend getting shumash's kernel and overclocking for the best experience. However if you're already using CM12 try updating to Milaqs latest builds here It might fix the issues you're having. I generally find Milaqs CM11 to be the most stable rom for your daily driver. Let me know how the newer builds of CM12 workout for you.
Click to expand...
Click to collapse
Thanks, I'm just deciding whether to go with JCSullins 12.1 from Jan 2016 or Milaq's 12.0 from Aug 2017. Tempted to go for 12.1 even though the actual rom is much older, I don't think much could have changed.

RolandDeschain79 said:
Hey guys install Shumash's SKZ Kernel and apply the following changes below, your user experience should drastically improve.
[...]
Misc
TCP Congestion Algorithm = sociopath
Click to expand...
Click to collapse
Thx a lot !! It saved my HPTP.
Yesterday i flashed the last evervolv, and looked for some improvements on xda-dev, and I saw your post. After flashing, I tried to apply these settings.
What a change !! The TouchPad is now usable.
My plan is to use it (with the touchstone) as a screen for my home automation. It was impossible, but now it seems to be responsive enough !
Thanks again.

[Kernel] Z2 Pro Kernel - GPU OC/ZEN/VOLTAGE/... - void5.4 Treble

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.

PEAK KERNEL by ProjectHiSi for HI3635

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.