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

[Q] is it possible to increase RAM ?

is there any way to increase RAM amount for s5830i?

sauron.tdl said:
is there any way to increase RAM amount for s5830i?
Click to expand...
Click to collapse
NO the RAM cannot to increase however the usage of RAM can be decreased...

Swap
Sent from my GT-S5830i using xda app-developers app

You can use swap or compcache. The first one uses SD card space as RAM (obviously, it's much, much slower than the real RAM), compcache uses compression.
Google is your friend.

GermainZ said:
You can use swap or compcache. The first one uses SD card space as RAM (obviously, it's much, much slower than the real RAM), compcache uses compression.
Google is your friend.
Click to expand...
Click to collapse
does swap worth? I mean does it have a remarkable difference?

sauron.tdl said:
does swap worth? I mean does it have a remarkable difference?
Click to expand...
Click to collapse
Instead of having android killing your old apps when RAM is needed, their state will be moved to the SD card.
It will be loaded again in the main RAM (after killing/moving other stuff again) when you need it.
So basically, it's good if your, say, browser keeps closing its tabs as soon as you exit it, but it won't help gaming much.
In fact, it may even cause lag if an application's state is being copied to the SD instead of being killed while gaming (killing it is pretty fast; copying it, not so much, and will cause lag, especially on our low end device).

If you are looking for more memory to install apks, then you should take a look at this:
http://forum.xda-developers.com/showthread.php?t=1716124
Regards

Rasec2002 said:
If you are looking for more memory to install apks, then you should take a look at this:
http://forum.xda-developers.com/showthread.php?t=1716124
Regards
Click to expand...
Click to collapse
He meant to increase RAM and not internal memory....
DON'T USE THAT "CronMod-A2SD/D2EXT/INT2EXT" or you will end up losing your IMEI number if your are unlucky...

GermainZ said:
Instead of having android killing your old apps when RAM is needed, their state will be moved to the SD card.
It will be loaded again in the main RAM (after killing/moving other stuff again) when you need it.
So basically, it's good if your, say, browser keeps closing its tabs as soon as you exit it, but it won't help gaming much.
In fact, it may even cause lag if an application's state is being copied to the SD instead of being killed while gaming (killing it is pretty fast; copying it, not so much, and will cause lag, especially on our low end device).
Click to expand...
Click to collapse
is there any tutorial for doing this method? would you guide me? I have RazoDroiD v2.5 rom on my ace.
and another question, do you recommend MindCr Rom v2.1? I prefer more Space in RAM and stability.

sauron.tdl said:
is there any tutorial for doing this method? would you guide me? I have RazoDroiD v2.5 rom on my ace.
and another question, do you recommend MindCr Rom v2.1? I prefer more Space in RAM and stability.
Click to expand...
Click to collapse
Try this To increase RAM(Requires SD-card partition)...
http://forum.xda-developers.com/showpost.php?p=26220059&postcount=1

sauron.tdl said:
is there any tutorial for doing this method? would you guide me? I have RazoDroiD v2.5 rom on my ace.
and another question, do you recommend MindCr Rom v2.1? I prefer more Space in RAM and stability.
Click to expand...
Click to collapse
I recommned you MindCr Rom v2.3 is great.
Regards.
Enviado desde mi GT-S5830i usando Tapatalk 2

@mario320, I agree with you in 100 per cent. I've S5830i for few days, and tried almost all ROM revisions for this mobile, but MindCr Rom v2.3 is just what I was loking for. I removed some useless apps from ROM, added other ones, and now it fits me perfectly. So with a clear conscience I can recommend MindCr Rom v2.3

11/07 [UNOFFICIAL][PORT][STABLE][ODEX/DEODEX] Cyanogenmod 10.1 Maclaw Studio

This is cyanogenmod port from 10.1 maclawstudio.
Is stable and fast start in less than a minute, can be used daily.
CREDITS:
[email protected]
erikcas
rohan007
wayland_ace
androidarmv6
jellaxy team
google
samsung
cyanogenmod
alin.p
maclawstudio
MatrixDJ96(odex script)
PRO Tips:
*use Interactive with 68-768 MHz and SIOPlus I/O for good performance/battery balance
*If you want better stability, performance, battery life, you can do with this ODEX script: http://forum.xda-developers.com/showthread.php?t=2162413&highlight=odex
DOWNLOAD: http://www.mediafire.com/?rb1q6wt5o48ai69

changelog:
25/06/2013:
*first release
11/07/2013:
*update sources AOSP / CM
*badass kernel update to 1.9.2

Nice! Where can we find the changes of Maclaw Studios?

why include Alin kernel when its not support sd ext ??? there is about 80 mb of free on internal left, without sd ext, its useless...

[email protected] said:
This is cyanogenmod port from 10.1 maclawstudio.
Is stable and fast start in less than a minute, can be used daily.
CREDITS:
[email protected]
erikcas
rohan007
wayland_ace
androidarmv6
jellaxy team
google
samsung
cyanogenmod
alin.p
maclawstudio
PRO Tips:
*use Badass with 68-652 MHz and Deadline I/O for good performance/battery balance
DOWNLOAD: http://www.mediafire.com/?u22703kojpj2b5c
Click to expand...
Click to collapse
[email protected]: I want to ask you if you could port the AOSP JB (Jellybean 4.2.2 (AOSP) RC2) also from MaclawStudio. Do you not forcing anything, no ETA only if you have the time and inclination, you can try to port AOSP JB?

Nixoman said:
why include Alin kernel when its not support sd ext ??? there is about 80 mb of free on internal left, without sd ext, its useless...
Click to expand...
Click to collapse
Man, my kernel doesn't have any problem with sd-ext. Either the script you are using is the problem, either your sd-card is may not be properly partitioned. I'm using sd-ext on AOKP and used it on CM10.1 also along with my kernel. I did not touch the ext4 drivers, so no error should be expected. Please check your script or partitions before making such claims.

alin.p said:
Man, my kernel doesn't have any problem with sd-ext. Either the script you are using is the problem, either your sd-card is may not be properly partitioned. I'm using sd-ext on AOKP and used it on CM10.1 also along with my kernel. I did not touch the ext4 drivers, so no error should be expected. Please check your script or partitions before making such claims.
Click to expand...
Click to collapse
my claims are proven, im running all roms (cm7,cm9,cm10,cm10.1) with sd ext script intext+, all work fine...as soon as i flash your kernel, bootloops or stuck at boot...tried every procedure of flashing...nothing...im not flaming you, this is bug, thats it...and few more people reported this problem

Nixoman said:
my claims are proven, im running all roms (cm7,cm9,cm10,cm10.1) with sd ext script intext+, all work fine...as soon as i flash your kernel, bootloops or stuck at boot...tried every procedure of flashing...nothing...im not flaming you, this is bug, thats it...and few more people reported this problem
Click to expand...
Click to collapse
There are people that posted in my kernel thread saying the sd-ext works perfectly, and my partition works too, with the same kernel. This means the problem is on your part, like I said, the script, or the partitioning process you used. They are just incompatible with my kernel. But ext4 feature works. Please try to understand. I know it's not flame, but it's a false claim.
If sd-ext works with my kernel, even for one single user, it is clear that it's not kernel's fault.

The lockscreen seems to be cut from down. Look @millo1978

Venomstar said:
The lockscreen seems to be cut from down. Look @millo1978
Click to expand...
Click to collapse
In Androidarmv6 github there is the fix...
keyguard_glow_pad_view, keyguard_glow_pad_container, etc..., are correct in Androidarmv6 sources.
Maybe in MaclawStudio sources isn't so.

millo1978 said:
In Androidarmv6 github there is the fix...
keyguard_glow_pad_view, keyguard_glow_pad_container, etc..., are correct in Androidarmv6 sources.
Maybe in MaclawStudio sources isn't so.
Click to expand...
Click to collapse
Since Maclaw Studios only builds for MDPI phones, of course LDPI fix isn't included.

Nixoman said:
my claims are proven, im running all roms (cm7,cm9,cm10,cm10.1) with sd ext script intext+, all work fine...as soon as i flash your kernel, bootloops or stuck at boot...tried every procedure of flashing...nothing...im not flaming you, this is bug, thats it...and few more people reported this problem
Click to expand...
Click to collapse
proven ?? then what about this ?
alin.p's lenio rom with BadassKernel-AOKP with CronMod-INT2EXTV2+ script.

jayOOMjay said:
proven ?? then what about this ?
alin.p's lenio rom with BadassKernel-AOKP with CronMod-INT2EXTV2+ script.
Click to expand...
Click to collapse
you said yourself: AOKP!!!! i was talking about cm9!
NOTE: this argument started on CM9 MIUI thread
and one more thing...Why all of you try defending Alinp, when im not attacking him?? I simple post my opinion on his kernel about sd ext problem , that I HAVE, and already found solution for sd ext, its not a big deal...i just want to put to a his attention to know that there is a bug with that script on my device, and that never happened to me on any other rom with some other kernels...he and i had discussion, its over, pls do not post your arguments on this one...Nishanty help me a lot on this one, so i can use his perfect kernel with sd ext...

Nixoman said:
you said yourself: AOKP!!!! i was talking about cm9!
NOTE: this argument started on CM9 MIUI thread
.
Click to expand...
Click to collapse
okay man, I was just saying my opinion and you didn't specify the fault was with cm9. I dont know about cm9. but with AOKP and latest cm10.1 rc6, it works fine.

jayOOMjay said:
okay man, I was just saying my opinion and you didn't specify the fault was with cm9. I dont know about cm9. but with AOKP and latest cm10.1 rc6, it works fine.
Click to expand...
Click to collapse
even for cm10.1 and AOKP, i found s2e (moded) better in terms i dont have to move Swype and Whatsapp to sd card/sd ext, it can stay at internal, and its eliminate lag causing of start ups and in-app...
but, as we said: opinions differ
BTW: anyone tried this rom yet?! ))))))

Nixoman said:
even for cm10.1 and AOKP, i found s2e (moded) better in terms i dont have to move Swype and Whatsapp to sd card/sd ext, it can stay at internal, and its eliminate lag causing of start ups and in-app...
but, as we said: opinions differ
BTW: anyone tried this rom yet?! ))))))
Click to expand...
Click to collapse
I hope you know that moving only the apk of an app doesn't create lags in that app. The moving of data and dalvik creates lag because the system needs to constantly access that data from a fast NAND flash memory, not SD. That's why I prefer the old CronMod A2SD script. It moves only the apks.
You're right, this is not an argument. But it's better to let the other users know what's right for them. I can't pronounce myself about Cm9 sd-ext as I never tested that, but being the same Filesystem drivers, it should work.

new version

is not working >>>>stop on bootanmition >>
i can not speek english im arabic

+1
aswertya said:
is not working >>>>stop on bootanmition >>
i can not speek english im arabic
Click to expand...
Click to collapse
+1

sushil888 said:
+1
Click to expand...
Click to collapse
+2, for me stopped on boot animation too, fortunately this ROM isn't working :\ Running CWM, data + cache + dalvik wiped, coming from miniCM10, tried to reflash, nothing gets this ROM working so I doubt the problem is really on my side.

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

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: