Dhollmen OMAP4_TI espresso kernel
Credits for Kernel Team and anyone else who has worked on this variant.
FEATURES:
Cpu starts boot at 1216 MHz.
Gpu starts boot at 384 MHz.
Undervolted.
Starts boot with 'interactive' as cpufreq governor.
Starts boot with 'deadline' as block scheduler.
CPU overclock selectable up to 1472 MHz. (see versions)
GPU overclock selectable up to 512 MHz. (see versions)
PowerVR SGX 540 modules built 'in',
Tweaked Init process (Slim 6 variant only)
Network CIFS support.
Reduced operating voltage by a notable percentage.
Added several optimizations to improve performance and reduce overhead.
VERSIONS:
EX version:
Uses 300, 600, 800, 1008 and 1216 MHz CPU frequencies.
Uses 307 and 384 MHz GPU frequencies.
OV version:
Uses 300, 600, 912, 1216, 1360 and 1472 MHz CPU frequencies.
Uses 307, 384 and 512 MHz GPU frequencies.
Rooted room needed to change the frecuencies.
ST_EX version: normal stock Slim 6.0 only
Uses 300, 600, 800, 1008 and 1216 MHz CPU frequencies.
Uses 307 and 384 MHz GPU frequencies.
Normal Slim 6 rom is not rooted, to appear certified in Google-Play. This version tries don't break that certification.
ST_OV version: normal stock Slim 6.0 only
Uses 300, 600, 912, 1216, 1360 and 1472 MHz CPU frequencies.
Uses 307, 384 and 512 MHz GPU frequencies.
Normal Slim 6 rom is not rooted, to appear certified in Google-Play. This version tries don't break that certification.
To change to high frequencies you need your rom rooted.
For all versions there is a specific variant for 7 inches models P31XX
Mention for nemes480 who has kindly put his time and his tablet at disposal to establish the best voltages for the 7-inch model.
Download Dhollmen 6 & Slim 6 releases
WARRANTY: You agree that this product is provided "as is" without any warranty, either expressed or implied, on its operation.
DISCLAIMER: You assumes at your SOLE RESPONSIBILITY and RISK all results produced by the "software" and/or instructions in this thread.
XDA:DevDB Information
Dhollmen kernel omap4, Kernel for the Samsung Galaxy Tab 2
Contributors
tuxafgmur
Source Code: https://github.com/Dhollmen/Kernel_omap4_ti_espresso
Kernel Special Features:
Version Information
Status: Beta
Beta Release Date: 2019-04-08
Created 2019-04-09
Last Updated 2019-04-13
.
Note:
The voltage settings that I have applied here, are different from those I used in my previous kernel.
For now, the date of the beginning of the thread, they have only been tested on my own tablet.
I have runned twice (in each and every one of the frequencies, CPU and GPU)
the Antutu stress tests and 3DMark OpenGL tests.
On the other hand, @nemes480 has carried out exhaustive tests to find the most suitable values for the 7-inch models.
Reserved
Nice work! I hope there will be nougat support too! ?
Edt: None of Ov, Ex and St versions works with Andi's Slim6 (P3110), black screen on boot! :/
nemes480 said:
Nice work! I hope there will be nougat support too! [emoji7]
Edt: None of Ov, Ex and St versions works with Andi's Slim6 (P3110), black screen on boot! :/
Click to expand...
Click to collapse
That's because some kernel changes are missing. We'll soon switch to newer DDK on our source. @Ziyan and @amaces put a lot of time, energy and afford into getting the new ddk running from 4.4 up to 7.1. Big thanks to both of them!
If there's special questions or something likes to be contributed back to us @tuxafgmur can contact me (even if my last email to him wasn't answered) or wait until needed changes are merged to Unlegacy Android.
Android-Andi said:
That's because some kernel changes are missing. We'll soon switch to newer DDK on our source. @Ziyan and @amaces put a lot of time, energy and afford into getting the new ddk running from 4.4 up to 7.1. Big thanks to both of them!
If there's special questions or something likes to be contributed back to us @tuxafgmur can contact me (even if my last email to him wasn't answered) or wait until needed changes are merged to Unlegacy Android.
Click to expand...
Click to collapse
I'm following development so I knew it there was kernel changes, but I thought tuxafgmur made this from that new source. Big thanks tuxafgmur!!! Interesting that the twrp recognize all espressowifi rom as p5110 or espressowifi10 insted of p3110 with both common and device specific twrp. (04.09.).
nemes480 said:
I'm following development so I knew it there was kernel changes, but I thought tuxafgmur made this from that new source. Does not matter, I tried with the dhollmen slim and everything was okey! Big thanks tuxafgmur!!! Interesting that the twrp recognize all espressowifi rom as p5110 or espressowifi10 insted of p3110 with both common and device specific twrp. (04.09.).
Click to expand...
Click to collapse
Yes he's using the common source (actually stable), but not those needed changes for newer DDK (will be merged soon in our stable trees, as there's no issues known yet).
About espressowifi/espresso3g:
All common ROMs use p5100 (espresso3g) or p5110 (espressowifi) fingerprint and build description to pass safetynet. You can edit your system/build.prop back to your device defaults, but it won't change anything in the end.
Edit:
Our kernel checks panel id which is passed by the bootloader and this way we know used variant. Variant is stored in sysfs which is used by audio hal for example.
To get an idea about it:
https://github.com/OMAP4-AOSP/andro...mmit/aad0f82e532dd991b4f2a74c0ee5f6d169d0ffdc
https://github.com/OMAP4-AOSP/andro...mmit/2268c59cbb81eec3bb7618f4cefc4913d32c4bef
https://github.com/OMAP4-AOSP/andro...mmit/dcb93bda2aa111c96b947d723aa63c132285f35f
https://github.com/OMAP4-AOSP/andro...mmit/b34632e91aafd20f811976f036a225b1e04fdadf
https://github.com/OMAP4-AOSP/andro...mmit/f4fc754bf9f78fe4f1e22ea1c2d75211a08f9514
https://github.com/OMAP4-AOSP/andro...mmit/30f92e10f9ade5a186dbad26a0aa09868506adc7
https://github.com/OMAP4-AOSP/andro...mmit/5e3bc1c436c5aea81462b4e47011effb3c349c4a
https://github.com/OMAP4-AOSP/andro...mmit/e5b79a5f15f717782bfe3f419b03914f3aeff09b
https://github.com/OMAP4-AOSP/andro...mmit/e41985f0dec3bb12cc99dd27ed9d757a3e6106c7
https://github.com/OMAP4-AOSP/andro...mmit/53df0adf88b7748ec19a9c727bee3675181b0dd0
https://github.com/OMAP4-AOSP/andro...mmit/17c5946b5312e5545e808e65b2e58ebd101c6d74
https://github.com/OMAP4-AOSP/andro...mmit/e3994e7d7a478bfbc7a1c99d7e6bcae83d0c0189
https://github.com/OMAP4-AOSP/andro...mmit/e9d2f3dbe2c8f66aeeabe453cbc18136b1ff72aa
https://github.com/OMAP4-AOSP/andro...mmit/294e7833340cf0da624124082cf288b8e2a02599
https://github.com/OMAP4-AOSP/andro...mmit/c10890e2659547085698866148ee37fa5757c37b
https://github.com/OMAP4-AOSP/andro...mmit/3531c0bbbf8e9d0aa04cee6ddca5528f141ac3aa
https://github.com/OMAP4-AOSP/andro...mmit/754db03e86448301e7af25b9be61c14aaab24847
More here if needed: https://github.com/OMAP4-AOSP/android_kernel_samsung_espresso/commits/history
Thanks tuxafgmur!
Finally we have options!
Will test and report here ASAP.
OBS: Think there is a mistaken info in OV build: "Uses 300, 600, 912, 1216, 1360 and 1272 MHz CPU frequencies." Should it be 1472 for the last frequency ?
galoneta said:
Thanks tuxafgmur!
Finally we have options!
Will test and report here ASAP.
OBS: Think there is a mistaken info in OV build: "Uses 300, 600, 912, 1216, 1360 and 1272 MHz CPU frequencies." Should it be 1472 for the last frequency ?
Click to expand...
Click to collapse
Yes, it is a mistake :good:
nemes480 said:
Nice work! I hope there will be nougat support too! ?
Edt: None of Ov, Ex and St versions works with Andi's Slim6 (P3110), black screen on boot! :/
Click to expand...
Click to collapse
Perhaps 7-inch models can not withstand such lower voltages.
If it is confirmed and nobody can boot from that mode, I'll have to do something about it.
For now, regarding the overclock, this kernel is a test version,
but I did not expect this kind of problems since, from my point of view, I have left margin enough to do boot at 1216 MHz.
My tablet can start at 1216 MHz with a lot less voltage.
I apologize for this issue. Thanks you for your feedback.
EDIT
Hi @nemes480
Can you install the below test kernel (with higher voltages) and tell me the result?
Thanks in advance.
Android-Andi said:
Yes he's using the common source (actually stable), but not those needed changes for newer DDK (will be merged soon in our stable trees, as there's no issues known yet).
Click to expand...
Click to collapse
Yes, i'm using the kernel forked from Slim repositories https://github.com/SlimRoms/kernel_ti_omap4 (as indicated in may github repo) to make an kernel to Slim 6 rom.
At this time, it's my only interest.
Regarding the rest of the post and all the links, suffice it to say that Ziyan took all the
work to unify the branches corresponding to the five Samsung Tab2 tablet models.
Mr tuxafgmur, reporting:
Using Twrp_Tab2-3.2.3.0.zip flashed in one step Slim-espressowifi-6.0.1-Dhollmen-20190331.zip + Dhollmen_Slim_Kernel_OV-20190408.zip = Everything runs fast and stable in my P5110.
Will test in P3110 ASAP and report here again. My friend has an P3100 and it is running your previous build too: It will be the next one to be tested!
Question: Would it be possible to release a 1520MHZ build as we had in previous Dhollmen Kernels: all my known galaxy 2 devices (P5110, P3110 and P3100) run fine at these speeds and the tablet behavior is far different from stock speeds! Maybe this would be the "ultimate" build as you can call it!
Dear tuxafgmur: If you need to test something else with these devices I have, please let me know!
Thanks again.
galoneta said:
Mr tuxafgmur, reporting:
Using Twrp_Tab2-3.2.3.0.zip flashed in one step Slim-espressowifi-6.0.1-Dhollmen-20190331.zip + Dhollmen_Slim_Kernel_OV-20190408.zip = Everything runs fast and stable in my P5110.
Will test in P3110 ASAP and report here again. My friend has an P3100 and it is running your previous build too: It will be the next one to be tested!
Question: Would it be possible to release a 1520MHZ build as we had in previous Dhollmen Kernels: all my known galaxy 2 devices (P5110, P3110 and P3100) run fine at these speeds and the tablet behavior is far different from stock speeds! Maybe this would be the "ultimate" build as you can call it!
Dear tuxafgmur: If you need to test something else with these devices I have, please let me know!
Thanks again.
Click to expand...
Click to collapse
What abour battery life? Right now I'm using Noob kernel at about 1200MHz and although OK, it seems not so snappier than stock kernel.
tuxafgmur said:
Perhaps 7-inch models can not withstand such lower voltages.
If it is confirmed and nobody can boot from that mode, I'll have to do something about it.
For now, regarding the overclock, this kernel is a test version,
but I did not expect this kind of problems since, from my point of view, I have left margin enough to do boot at 1216 MHz.
My tablet can start at 1216 MHz with a lot less voltage.
I apologize for this issue. Thanks you for your feedback.
EDIT
Hi @nemes480
Can you install the below test kernel (with higher voltages) and tell me the result?
Thanks in advance.
Click to expand...
Click to collapse
Succesfully booted up Dhollmen Slim6, with your attached kernel, and seems to be relieable! And @tuxafgmur you were right about too low voltage on 7". The device cannot finish boot (EX version I tried), drop back to reboot so process finish in bootloop.
If you need stress tests or else tell me!
Edit: EX verison booted up but, device reboot itself immediately.
barbe31 said:
What abour battery life? Right now I'm using Noob kernel at about 1200MHz and although OK, it seems not so snappier than stock kernel.
Click to expand...
Click to collapse
In the normal use of the tablet, you can't notice much difference between different kernels, only based on the speed sense.
Many processes don't run at high frequencies more than a few miliseconds (they don't even use them at all).
I have not seen Noob kernel patches (I don't know, even, if they are published) but the only "indicative" measurements can be done through synthetic tests, for example with the 3DMark or Antutu tests.
The battery's duration depends on a set of settings that go further than simply raising the frequency.
For example, Dhollmen kernel use almost less voltage at high frequencies than the "stock" kernel at normal frequencies, but the init process adds more settings (in my Rom's version)
nemes480 said:
Succesfully booted up Dhollmen Slim6, with your attached kernel, and seems to be relieable! And @tuxafgmur you were right about too low voltage on 7". The device cannot finish boot (EX version I tried), drop back to reboot so process finish in bootloop.
If you need stress tests or else tell me!
Edit: EX verison booted up but, device reboot itself immediately.
Click to expand...
Click to collapse
Thank you very much! :good:
I have spent a lot of time doing tests with different voltages for each of the possible frequencies.
As I indicated, at thread's beginning, I have passed twice the Antutu stress test and the OpenGL 3DMark test for each voltage change (going down little by little until the tablet restarted)
It's a very tedious process, but the only, to determine the best values.
If you want to do it, you can use Kernel Adiutor to make the voltage changes.
If so, then I would appreciate it if you could tell me the final values.
The problem here, is that you need a rooted ROM and, for the OV version, you need I upload another test OV kernel with high voltages to allow you to boot.
galoneta said:
Mr tuxafgmur, reporting:
Using Twrp_Tab2-3.2.3.0.zip flashed in one step Slim-espressowifi-6.0.1-Dhollmen-20190331.zip + Dhollmen_Slim_Kernel_OV-20190408.zip = Everything runs fast and stable in my P5110.
Will test in P3110 ASAP and report here again. My friend has an P3100 and it is running your previous build too: It will be the next one to be tested!
Question: Would it be possible to release a 1520MHZ build as we had in previous Dhollmen Kernels: all my known galaxy 2 devices (P5110, P3110 and P3100) run fine at these speeds and the tablet behavior is far different from stock speeds! Maybe this would be the "ultimate" build as you can call it!
Dear tuxafgmur: If you need to test something else with these devices I have, please let me know!.
Click to expand...
Click to collapse
I must admit that the CPU of these tablets has a lot of scaling margin, but you will have to recognize, too, that the difference in performance obtained at 1520 MHz is very small compared to the stress to which it is subjected.
Although any modification of the kernel to increase frequencies and voltage start from a common idea (very old and very tested) this time I have made a slightly different approach: achieve total stability with the minimum voltage and REALLY use the voltage determined for each frequency .
On the other hand, to obtain an adequate graphical yield, it is necessary to increase the frequency of the GPU up to 512 MHz, and here, an appreciable stress begins, since the GPU works at maximum or at minimum frequency, not using the intermediates at all.
I would prefer to wait for the opinions of some more people and reach a real consensus.
tuxafgmur said:
Thank you very much! :good:
I have spent a lot of time doing tests with different voltages for each of the possible frequencies.
As I indicated, at thread's beginning, I have passed twice the Antutu stress test and the OpenGL 3DMark test for each voltage change (going down little by little until the tablet restarted)
It's a very tedious process, but the only, to determine the best values.
If you want to do it, you can use Kernel Adiutor to make the voltage changes.
If so, then I would appreciate it if you could tell me the final values.
The problem is that you need a rooted ROM and, for the OV version, you need I upload another test OV kernel with high voltages to allow you to boot.
Click to expand...
Click to collapse
Not a problem, Im using root since my first phone. I have some experice. Im gladly help you out in this, so Im waiting for that OV version.
tuxafgmur said:
In the normal use of the tablet, you can't notice much difference between different kernels, only based on the speed sense.
Many processes don't run at high frequencies more than a few miliseconds (they don't even use them at all).
I have not seen Noob kernel patches (I don't know, even, if they are published) but the only "indicative" measurements can be done through synthetic tests, for example with the 3DMark or Antutu tests.
The battery's duration depends on a set of settings that go further than simply raising the frequency.
For example, Dhollmen kernel use almost less voltage at high frequencies than the "stock" kernel at normal frequencies, but the init process adds more settings (in my Rom's version)
Click to expand...
Click to collapse
Muchas gracias for your detailed explanation. Indeed everything under the hood is not so simple. I think of your work it as craftmanship.
I will try your rom+kernel and report as soon as possible.
Here are the kernel test files for Dhollmen Rom Slim 6
Only for testing best voltage levels in 7-inch models
If someone decides to try them, I hope can tell me the best values obtained.
Thanks in advance.
Related
Here is the method to OC 1.2G
- move to arch/arm/plat-s5pc11x and change next three files
: max8998+consumer.c, s5pc110-dvfs.c, s5pc110-clock.c
- And, change some parameters like,
1000000 --> 1200000
250 --> 300
1250 --> 1300
<in file max8998+consumer.c>
/* frequency, Mathced VDD ARM voltage , Matched VDD INT*/
#if 1
{1200000, 1300, 1100, 0},
static const unsigned int dvs_arm_voltage_set[][2] = {
{DVSARM1, 1300},
<in file s5pc110-dvfs.c>
/* frequency */
static struct cpufreq_frequency_table s5pc110_freq_table_1GHZ[] = {
{L0, 1200*1000},
<in file s5pc110-clock.c>
/*APLL_FOUT, MPLL_FOUT, ARMCLK, HCLK_DSYS*/
static const u32 s5p_sysout_clk_tab_1GHZ[][4] = {
// APLL:1000,ARMCLK:1000,HCLK_MSYS:200,MPLL:667,HCLK_DSYS:166,HCLK_PSYS:133,PCLK_MSYS:100,PCLK_DSYS:83,PCLK_PSYS:66
{1200* MHZ, 667 *MHZ, 1200 *MHZ, 166 *MHZ},
/*pms value table*/
/*APLL(m, p, s), MPLL(m, p, s)*/
static const u32 s5p_sys_clk_mps_tab_1GHZ[][6] = {
{300, 6, 1, 667, 12, 1},
Then compile to zImage and flash it with ODIN.
I will not upload my zImage file because it's for M110S.
If someone find best rates and ARM voltage for upper clock, leave it here.
THANK YOU..... now just have to wait for someone smarter then me to actually do it and post the file, lol.
For best battery life and less stress to CPU someone should try to find lowest VDD which supports high frequency.
Here is one I compiled. I didn't just change the 1ghz but added a the 1.2ghz as an extra speed.
This is COMPLETELY untested. I'm not really much of a coder.
This MAY brick your device. If you know how to unbrick a SGS that has been flashed with a bad kernel, then you can try it. This is VIBRANT only (as that's the code that I had on my laptop at the time.)
I am not responsible for any damages to your phone. Please, please, please, ONLY flash this if you know how to recover from a bad kernel.
ONLY CLICK HERE IF YOU READ AND AGREED WITH THE WARNING IN RED!!!
Why the hell would anyone want to overclock their phone?
If you just want to destroy the phone, dont do it. donate it instead.
Wonderful
I really miss the custum oc and undervolt kernels from my Nexus.
Good work !
emclondon said:
Why the hell would anyone want to overclock their phone?
If you just want to destroy the phone, dont do it. donate it instead.
Click to expand...
Click to collapse
who tells you the phone would be destroyed from OC? sure it really needs to be tested through stress tests and the first people to try will be endangered to brick, but normally the cpu is failing and freezing when it gets too hot. on the i7500 we have overclocking from 528mhz to 710mhz and most of the devices run fine with that. however some devices can only be clocked to 614mhz without freezing which is due their cpus are not that good quality, but never we had any user reporting a grilled cpu. however we have to be carefully with voltages (what actually causes cpu grilling) to not raise them to much.
ivanmmj said:
Here is one I compiled. I didn't just change the 1ghz but added a the 1.2ghz as an extra speed.
This is COMPLETELY untested. I'm not really much of a coder.
This MAY brick your device. If you know how to unbrick a SGS that has been flashed with a bad kernel, then you can try it. This is VIBRANT only (as that's the code that I had on my laptop at the time.)
I am not responsible for any damages to your phone. Please, please, please, ONLY flash this if you know how to recover from a bad kernel.
ONLY CLICK HERE IF YOU READ AND AGREED WITH THE WARNING IN RED!!!
Click to expand...
Click to collapse
your kernel is only 2.6mb in size while all the stock and other kernels are about 5mb. if i compile the kernel source myself i also get only about 2.6, any idea why? missing modules in the image maybe?
thank you!
edit: sorry for the off topic post...
jodue said:
your kernel is only 2.6mb in size while all the stock and other kernels are about 5mb. if i compile the kernel source myself i also get only about 2.6, any idea why? missing modules in the image maybe?
thank you!
edit: sorry for the off topic post...
Click to expand...
Click to collapse
You need initramfs
actuallly im more interested in saving battery life by underclocking and undervolting the phone. Is it possible also?
Or at least remain at 1Ghz but with voltage lowered.
If anyone found the best combination please share
My HTC Hero i OC all the time to 710Mhz no problems. It def got more "snappy".
To UC my Galaxy I use SetCPU. min 200 and max 400 when screen off.
Maybe I'll save som battery!?.
With screen on i use min 800 and max 1000.
Would be nice to run the Galaxy at 1.2Ghz.
Hi all! I'm in Europe, and I have a Galaxy S. I saw in the 4th post, that it's working only on Vibrant. I just wanna ask, it's working on Europe version Galaxy S?
Thanks, and great work
Development
Due to samsungs own dev team pretty much dominating ROM development, Kernals seem like a good place for the great minds at XDA to do what they do best! I really do hope that kernal development kicks off for the SGS as im used to haveing OC with UV on my N1 and really enjoyed the advantages these gave me. I hope someone with more tech knowledge can chuck together a OC Kernal for the SGS sometime soon ...
I don't need oc yet lol, this thing already flies, can't wait for froyo tho
jodue said:
your kernel is only 2.6mb in size while all the stock and other kernels are about 5mb. if i compile the kernel source myself i also get only about 2.6, any idea why? missing modules in the image maybe?
thank you!
edit: sorry for the off topic post...
Click to expand...
Click to collapse
As mentioned above, this is the kernel only, not the whole package. I didn't have time to set up the whole thing. I compiled that at 4 in the morning and was too tired to throw it all together. I've got a lot of work to do (irl) but maybe I'll get some more time later tomorrow to work on making something more flashable.
ivanmmj said:
As mentioned above, this is the kernel only, not the whole package. I didn't have time to set up the whole thing. I compiled that at 4 in the morning and was too tired to throw it all together. I've got a lot of work to do (irl) but maybe I'll get some more time later tomorrow to work on making something more flashable.
Click to expand...
Click to collapse
yeah, initramfs is not in your zImage ... after some reading i got it working with leshak's initramfs (http://github.com/leshak/i9000-leshak-initramfs). now i have a kernel which is about the right size (5.8 MB) i have't had time to flash it yet tho
This is really interesting - Imagining that one day it could be possible to overclock when gaming and hard multitasking and underclock/undervolt when needed to save battery!!
Im subscribing to this topic!
I've got a Vibrant Kernel up and running with initramfs and should be releasing it tonight. I'll add in more changes like OC/UV in the future.
justanothercrowd said:
I've got a Vibrant Kernel up and running with initramfs and should be releasing it tonight. I'll add in more changes like OC/UV in the future.
Click to expand...
Click to collapse
Is it easy to port to stock galaxy?
emclondon said:
Why the hell would anyone want to overclock their phone?
If you just want to destroy the phone, dont do it. donate it instead.
Click to expand...
Click to collapse
Hehe feel like laughing at you! I am overclocking almost all my devices (read - target all of them if I can) and I never had a device brick or cause any issue except for the temporary instability if I overdo it. This is how I test and use my hardware. Way to go. Once I learn how to compile these kernels, I will see what best speeds I could go before the phone becomes unstable.
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
[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.
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?
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.