Database Develop

vorkKernel-OC/UV Kernel for CM[20111105]

Hi. The following kernel is presented to you by
vorkKernel Team:
- kiljacken
- Benee​
Click to expand...
Click to collapse
This kernel is for Cyanogenmod and Miui. *Could* be incompatible with latest kangs or nightlies (after a kernel update from CM team). No support for stock or mcr...
It's incompatible with MIUI and CM Builds before #177
New vorkKernel Twitter Bot: Here
First I want to make clear that all credit goes to aremcee/arcee/rmcc (man so many nicks ). He did an awesome job with the kernel.
I just tweaked it a little bit to my needs.
Features:
uv/oc support. OC up to 1,5GHz (With E-Peen version)
AVP/System/RAM/GPU OC with E-Peen version
1,2 Ghz for batt safe version.
Special tweaked (working!) Performance and Powersave Govenors which don't lock the freq to one level (they choose between 3-4 Freq steps)
It's even possible to set max/min clock via setcpu or CMSettings!
Voodoo sound. Thanks supercurio! So awesome
Default IO-Sched is Deadline with a special flash storage tweak
Slub allocator
tweaked CFS cpu sched (Low latency)
compiled with a tweaked toolchain (base linaro gcc - optimized for tegra2)
VFP optimizations (vfpv3-d16) and overall compiler optimizations
flags! (more below in the flag section)
A App for easy downloading and configuring. Credits to kiljacken!
Click to expand...
Click to collapse
The standard part:
I'm not responsible for melted phones or something like that...
The camera is unstable with E-Peen mode (due to AVP OC). After a reboot it needs to stabilize a few minutes (so you break it with every reboot again). Same for Bluetooth. Please don't report a problem regarding this. It's known and can't be fixed.​
Click to expand...
Click to collapse
And the source code here.
Download (Market)
Credits to kiljacken for this awesome app! You need OI File Manager for the app (Comes with CM)!
(and if you refuse to use the app - or the app is refusing to work with you: here)
Only change something, if you want to enable OC - No need to touch anything else (like govenors, schedulers)​
What are flags and how can I use them?
I recommend to use the App kiljacken made, because it's super easy for you guys. If you not want to use the app *sadpanda* then you can click this link. This is the file the app is fetching to generate the UI.
The layout is following:
Available for following device/Element style (more below)/the flag you need to add/Flag name in App/Description for general Flag/Choice name in app/actual value you need to add after flag name
If the last two points are added you first enter the flag name and than the value. For example: density230
You connect the flags with a: -
Example: -camera-ring ...
The script is configured to detect flags after vorkKernel-VERSIONNUMBER. So you can add some flags after this.
Element style
c = Checkbox
l = List you can choose things from
e = you can enter your own value​
Click to expand...
Click to collapse
Error Reporting Guide
Start with rebooting, if that doesn't help, reflash CM and then the kernel, and check again. If you're using the updater app (make sure you have the latest version), use the error report function (and describe what you're problem is). If you're not using the app, then post what flags you are using, along with what your problem is.​
Click to expand...
Click to collapse
Additionally I just want to point out that I'm not doing this as a fulltime job, so don't expect daily updates or something like that. I will try to fix a problem as fast as possible but in some cases it can take a while.
If you want to support me you can sign up on dropbox via my referral link or just push this nice thanks button .. If you want to donate you can donate to aremcee/arcee/rmcc something. I'm learning C and linux and vorkKernel is my learning project and it is a hobby for me. Anyway if you still want to support a poor student, I have a link in my signature
Thanks to:
arcee + the whole CM Team
morfic for all the avp oc tweaks and other stuff
thalamus (for saving me going crazy with the toolchain )
Erasmux
All guys that made pull request and contributed in any possible way
Donators to our project (app or kiljacken's donate link)
the android community
and a very big thanks to b3ndech0 for his buildbox.

Thanks, this is very much appreciated

This kernel is amazing! Nice work with the filename flags. It's brilliant! This way we don't have to have the same setup, but can enjoy both CM7 and the kernel.

sibbor said:
I'll try this kernel later. Will wait for CM7 getting more optimized for our devices first. 2000 Quadrant scores out of the box just don't cut it - I don't want to overclock to 1.4 GHz just to reach speeds of MCR FR14 ;-)
Planning on including any changes from kholk?
Click to expand...
Click to collapse
More things will be in it soon. And Quadrant doesn't matter. CM feels better in normal use (except a few problems but it is a really good starting point).

Benee said:
More things will be in it soon. And Quadrant doesn't matter. CM feels better in normal use (except a few problems but it is a really good starting point).
Click to expand...
Click to collapse
Yes I know it doesn't really matter. Although, generally speaking, higher scores means the software is more optimized to the hardware; framework, kernel and/or drivers.
CM7 should be able to smash the performance out of the LG stock ROM without problem...
Thanks for you kernel additions! Subscribed to this thread now so I can follow your progress.

is this kernel for a stock rom?
thanks

sibbor said:
Yes I know it doesn't really matter. Although, generally speaking, higher scores means the software is more optimized to the hardware; framework, kernel and/or drivers.
CM7 should be able to smash the performance out of the LG stock ROM without problem...
Thanks for you kernel additions! Subscribed to this thread now so I can follow your progress.
Click to expand...
Click to collapse
Nah. You can boost quadrant to oblivion via data2ext for example on desire/nexus but it didn't helped in real life performance. The sql sync disable doesn't help with real usage, but boost quadrant etc. So many things which doesn't improve real usage, boost quadrant. Like deleting your /system (pro move...).
But yeah in some parts you are right and optimizing drivers boost it too + help real use performance, so I will do this too.
vekkio said:
is this kernel for a stock rom?
thanks
Click to expand...
Click to collapse
Really? Just read the title: vorkKernel-OC/UV Kernel for CM. For Cyanogenmod. Not stock...

seems the IO from quadrant score still low, is it same sqlite hack with paul that one?

emprize said:
seems the IO from quadrant score still low, is it same sqlite hack with paul that one?
Click to expand...
Click to collapse
yup. patched cm, then compiled this and added it to update.zip.

vekkio said:
is this kernel for a stock rom?
thanks
Click to expand...
Click to collapse
Haaahaa yeah u flash away hahahahha
EDIT:- No only joking
DONT PEOPLE READ

ok, flash this kernal and using cm7 oc to 1.4, quadrant get 31xx
edit : fail to exec smartbench

Benee any chance you could add the OC support to the CM settings?
Sent from my LG O2X CM7 Nightly

svceon said:
Benee any chance you could add the OC support to the CM settings?
Sent from my LG O2X CM7 Nightly
Click to expand...
Click to collapse
Yep but this would break pimp my cpu support and I think pimp my cpu is the better deal. A easy user interface with undervolting support. Awesome! .. so no I won't add it to cm settings

Awesome OC in CM7 makes it even better

I know I'm going to get flamed for this but how do you o/c once you have flashed the kernel? when i open setCPU its already at the max 1g when i go to the CM settings there's no frequencies to select in the cpu management option
is it different on the tegra chips as opposed to qualacom?

sibbor said:
Planning on including any changes from kholk?
Click to expand...
Click to collapse
Ok if I understand the changelog from kholk correct, most of the changes are already included (don't know exactly because he didn't copied the commit names and sums the function up). One commit isn't in it because it introduced the graphic glitches. vfp3-d16 support and compiler optimization will be added with next update. Then most things are in it.

spences10 said:
I know I'm going to get flamed for this but how do you o/c once you have flashed the kernel? when i open setCPU its already at the max 1g when i go to the CM settings there's no frequencies to select in the cpu management option
is it different on the tegra chips as opposed to qualacom?
Click to expand...
Click to collapse
Is stated in the OP:
So I compiled it with uv/oc support via pimp my cpu.
Click to expand...
Click to collapse
Pimp My CPU can be downloaded from here: http://forum.xda-developers.com/showthread.php?t=1018411

spences10 said:
I know I'm going to get flamed for this but how do you o/c once you have flashed the kernel? when i open setCPU its already at the max 1g when i go to the CM settings there's no frequencies to select in the cpu management option
is it different on the tegra chips as opposed to qualacom?
Click to expand...
Click to collapse
Nah no flaming . You need pimp my cpu for it. Cpasjute did some kernel hacks to enable oc and add a uv function. That means you can undervolt without compiling the kernel again. Unfortunatly it isn't compatible with setcpu..

The kernel seems ok; I tried OC till 1200 with 50-100 UV (depending on OC).
What's very good with CM7 (and this kernel) is battery life, 30-40% more compared with Modaco ROM (till FR14).
Anybody have tried higher frequencies (1300-1400)?
Thanks a lot.

lukemo said:
The kernel seems ok; I tried OC till 1200 with 50-100 UV (depending on OC).
What's very good with CM7 (and this kernel) is battery life, 30-40% more compared with Modaco ROM (till FR14).
Anybody have tried higher frequencies (1300-1400)?
Thanks a lot.
Click to expand...
Click to collapse
I have been using this all day running 1300Mhz @ 1200mV - normal use with wifi on - 84% battery left after ap. 12 hours

[Kernel] Battery saver kernel

Update
Here is an easier solution that doesn't require flashing.
Please use this for any new ROMs from now on.
Old solution ONLY FOR 5.10.8 and 5.10.16
This is a stock miui kernel from 5.10.8, with modified ramdisk to limit CPU frequency.
This is a test I made for myself to see how much it helps in battery time to limit the CPU. I'm sharing this, because others might be interested in it.
You need to have MIUI 5.10.8 or 5.10.16. Older versions are not fully compatible. (Vibration not working)
So, finally we have custom kernels?
No, the proper kernel source is not available yet, the kernel image is still untouched.
Will there be new versions?
Probably, as there are other possible ramdisk tweaks that can achieve better battery life.
How much this can help?
I didn't have the time for a long test yet, I hope there are some users here who are willing to compare the results with the factory kernel.
But I can make some points:
This won't help much with standby time, as the frequency there is already much more limited.
This will help the most in situations where the CPU is the biggest drainer, like games.
Is this going to slow down my phone?
Theoretically, it will be slower. However in real life usage, I can't tell the difference.
Why wouldn't you just use an app like SetCPU?
None of those apps I tried have worked.
Can this be done without flashing a new kernel?
Yes, you only have to update the frequency in KHz in /proc/cpufreq/cpufreq_limited_max_freq_by_user.
For example (with root privileges):
Code:
echo '1500000' > /proc/cpufreq/cpufreq_limited_max_freq_by_user
However, this will reset after a reboot.
The attached file can be flashed under recoveries. TWRP tested.
Or you can extract the boot.img, and flash it in fastboot.
xm_kernel.zip will limit the CPU at 1.5GHz.
xm_kernel_1200 will do 1.2GHz.
Version 2 will do the trick Ched666 suggested, thus reducing the time spent at maxfreq.
Version 3 will not disable the touch boost, instead it will replace perfservscntbl.txt with boost to 1183MHz and 2 cores.

Reserved

Looking forward results and tests.

Flashed on 5.9.24
Work perfect. Only one problem... Vibro is gone Both Incall and feedback

Bakumatsu said:
Flashed on 5.9.24
Work perfect. Only one problem... Vibro is gone Both Incall and feedback
Click to expand...
Click to collapse
Thanks for the heads-up. You probably need 5.10.8 for that to work.

I know. I just a flashagolic

ill be testing this later..nice work buddy

Test on miui 5.10.8, it works!
And later manually change value to 1200000, works without lag. But after reboot maxfreq reset to 1500000.
Can you make the same kernel, but with maxfreq 1200000?

Xmister said:
No, the proper kernel source is not available yet, the kernel image is still untouched.
Click to expand...
Click to collapse
isn't this the kernel source code: https://github.com/BalcanGSM/MediaTek-HelioX10-Kernel

avenant said:
isn't this the kernel source code: https://github.com/BalcanGSM/MediaTek-HelioX10-Kernel
Click to expand...
Click to collapse
That is just a basic MediaTek source, it's missing drivers and configuration for our device.

I think it is more easy to control the value by implement init.d on our device.

Xmister said:
What is this?
This is a stock miui kernel from 5.10.8, with modified ramdisk to limit CPU frequency at 1.5GHz.
This is a test I made for myself to see how much it helps in battery time to limit the CPU. I'm sharing this, because others might be interested in it.
You need to have MIUI 5.10.8. Older versions are not fully compatible. (Vibration not working)
So, finally we have custom kernels?
No, the proper kernel source is not available yet, the kernel image is still untouched.
Will there be new versions?
Probably, as there are other possible ramdisk tweaks that can achieve better battery life.
How much this can help?
I didn't have the time for a long test yet, I hope there are some users here who are willing to compare the results with the factory kernel.
But I can make some points:
This won't help much with standby time, as the frequency there is already much more limited.
This will help the most in situations where the CPU is the biggest drainer, like games.
Is this going to slow down my phone?
Theoretically, it will be slower. However in real life usage, I can't tell the difference.
Why wouldn't you just use an app like SetCPU?
None of those apps I tried have worked.
Can this be done without flashing a new kernel?
Yes, you only have to update the frequency in KHz in /proc/cpufreq/cpufreq_limited_max_freq_by_user.
For example (with root privileges):
Code:
echo '1500000' > /proc/cpufreq/cpufreq_limited_max_freq_by_user
However, this will reset after a reboot.
The attached file can be flashed under recoveries. TWRP tested.
Or you can extract the boot.img, and flash it in fastboot.
Click to expand...
Click to collapse
it show to be on maximum speed on cpu spy...why?

Jo-san said:
it show to be on maximum speed on cpu spy...why?
Click to expand...
Click to collapse
Maybe the flash wasn't successful,or you flashed over something.
This is mine, the 29 sec is during boot, until it activates.

Ched666 said:
Test on miui 5.10.8, it works!
And later manually change value to 1200000, works without lag. But after reboot maxfreq reset to 1500000.
Can you make the same kernel, but with maxfreq 1200000?
Click to expand...
Click to collapse
OP updated with 1.2GHz kernel

Xmister you really do a great job. I renember I used your kernel when my phone was still HTC one x and then I changed to use iPhone 5s ,6, and dropped few weeks ago. And then I am back to android envirnoment and still flashing your modded kernel. Many thanks for your contribution.
And BTW, I think the 1200 kHz really help in get away from the battery draining problems.

4pda users found interesting thing... When touch a screen, frequency increases to maximum.
But if write 0 to the /proc/cpufreq/cpufreq_limited_by_hevc and set read only permissions, this bug disappears. And no maximum freq when touch a screen.
I tried it, and phone is much less heat, and works at a reduced freqs.
ADD: make mod to xm_kernel 1,5 GHz with this tweak

Ched666 said:
4pda users found interesting thing... When touch a screen, frequency increases to maximum.
But if write 0 to the /proc/cpufreq/cpufreq_limited_by_hevc and set read only permissions, this bug disappears. And no maximum freq when touch a screen.
I tried it, and phone is much less heat, and works at a reduced freqs.
Click to expand...
Click to collapse
This seems working too.
OP updated with V2 kernels that do this automatically.

Xmister said:
This seems working too.
OP updated with V2 kernels that do this automatically.
Click to expand...
Click to collapse
Also made modification ))

No need to touch cpufreq_limited_by_hevc.
If you want to control the touch_boost, try this way.
Find the file in system/etc/perfservscntbl.txt
CMD_SET_CPU_CORE, SCN_APP_TOUCH is to control how many cores when touch boost.
CMD_SET_CPU_FREQ, SCN_APP_TOUCH is to set the value when touch boost.
Save after modify and reboot your device.
By @Ched6666 's way is totally disable touch_boost

v2 is compatible with 5.10.16 release?

Q&A - Helium kernel

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:

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.