any suggestions?
many feedbacks now are annoyed with getting low ram..
resulting lower performance of cm7...
hehe..thanks..
low ram=faster app lauching. that is good
huh?
im having about 70mb free ram..
it goes robotic..haha
What are you running on you ace?
Get the V6 supercharger script by zepplin of course
Set CPU min and max to 800 Mhz
Also set CPU gov to 'performance'
Actually default settings are good enough
My settings: V6Supercharged, compache disabled, JIT enabled, surface dithering disabled, purguing of assets enabled, VM heap size 48m
Related
Just wanted to start a thread to see what you guys use for advanced CPU settings. Do you OC (and how much)? What governor do you use? Do you have JIT enabled? If so, what's your VM heap size? Do you use compcache? And most importantly, what differences have you noticed by trying different settings?
Right now I'm OCing to 245/710 on GSB 1.2 with no JIT or compcache and using the smartass governor, and my phone is running better than it has in a long time. I tried GSB with JIT and compcache and noticed a definite slow down.
If you're not using JIT, you're not getting any benefit that I can see of having a 2.2+ ROM. My Linpack scores go up about 50 to 75% when I turn on JIT.
Most of the time, I have the clock set at 604/245, with a screen off at 528/245. For the Froyo/GB ROMs, I always have JIT, compcache at default, vm heap at default, governor at smartass.
For Eclair ROMs (running Zanfur's kernel) I generally have the same clocks, ondemand governor, no JIT. Sometimes I set the minimum at 19.2 on Zanfur's kernel and it still seems to run fine - it tends to depend on how fast the battery burns.
GSB 1.2
Min 245
Max 604 - 768 depending on usage
Gov. Interactive
Compcache off
JIT on
VM heap 24MB
Surface dithering off
Lock home in memory off
Lock messaging off
Also been using xtr's cache2cache.
Sent from my GSBv1.2 using XDA App
GSB 1.3
Min 245
Max 748
Gov. On Demand
Compcache 10%
JIT on
VM heap 32MB
Surface dithering off
Lock home in memory off
Lock messaging off
Noticed a slow down running Compcache at 18%(default). If my battery starts getting low, I'll change my max to 528.
with GSB 1.3
Min 245
Max 710
Gov. On Demand
Compcache 26%
JIT On
VM heap 32MB
Surface dithering off
Lock home in memory on
Lock messaging off
I am using XTR's Cache2Cache script which helps me maximize my space seeing as I have a massive amount of apps installed (107) and my caches are very high. I'm running at around 30-34MB free space. If I didn't use Cache2Cache i'd be at 0-5MB free and i'd have all kinds of memory issues. =-) XTR rocks!
I dont get any lag, not yet at least. home screen doesn't reload either.
Izeltokatl said:
lock home in memory on
Lock messaging off
I am using XTR's Cache2Cache script which helps me maximize my space seeing as I have a massive amount of apps installed (107) and my caches are very high. I'm running at around 30-34MB free space. If I didn't use Cache2Cache i'd be at 0-5MB free and i'd have all kinds of memory issues. =-) XTR rocks!
I dont get any lag, not yet at least. home screen doesn't reload either.
Click to expand...
Click to collapse
I've been getting that homescreen reload thing, too. I assume saving the "lock home in memory" fixes that?
oceanminded said:
Just wanted to start a thread to see what you guys use for advanced CPU settings. Do you OC (and how much)? What governor do you use? Do you have JIT enabled? If so, what's your VM heap size? Do you use compcache? And most importantly, what differences have you noticed by trying different settings?
Right now I'm OCing to 245/710 on GSB 1.2 with no JIT or compcache and using the smartass governor, and my phone is running better than it has in a long time. I tried GSB with JIT and compcache and noticed a definite slow down.
Click to expand...
Click to collapse
245/748 gsb 1.4 JIT enabled compcache at 26% performance no slowdown that i noticed.
EDIT: Autokiller at Ultimate and the majority of my user apps on the SD card only ones with widgets and those that dont work on SD card on internal. Memory normally stays at about 40-50
i am using GSB 1.6 running setCPU at 748max and 240min and it is completely stable. It has had no noticeable effect on battery life.
Is anyone having issues w overclocking to 806 w interactive. Running tazz froyo gb and siedio
stk, I have issues overclocking to 806 period.
JIT should be on with any 2.2+ device.
Compcache off, our cpu is too weak to do any extra work like that.
VM heap size at 16, where it garners top performance.
Sleep profile: 19min, 480max
powersave bia, 40
up threshold 98
wakes up just fine
Testing Criteria
Quadrant Standard Version 1.17
(IMPORTANT - v1.17 shows an inaccurate quadrant score 100 less than it should be! So, if your are using version 1.17 (latest version), add +100 to your score! =)
Floyo 4.0
Enabled surface dithering
768mhz overclocked (Perfectly stable)
JIT disabled
VM Heap size: 32m
SCORE: 1153 + 100 (v1.17) = 1253
Make sure when you test your device, overclock to 768mhz so we can get a fair quadrant score comparison!
Post & share your scores & settings or any extra tweaks you may have used to get a highher quadrant score =)
1049
Floyo v4
Jit disabled
Vm heapsize 34
Clocked at 768mHz
How did you get it so high??
sent from Xperia X10 Mini Pro
royalbloodvi said:
Testing Criteria
Quadrant Standard
Floyo 4.0
768mhz overclocked (Perfectly stable)
JIT disabled
VM Heap size: 32m
SCORE: 1153
Make sure when you test your device, overclock to 768mhz so we can get a fair quadrant score comparison!
Post & share your scores & settings or any extra tweaks you may have used to get a highher quadrant score =)
Click to expand...
Click to collapse
Hello this morning, i've installed floyo v4 but setcpu show me that i'm at 600Mhz? How can i get 7xx Mhz
?? Thank you
awcabdou said:
Hello this morning, i've installed floyo v4 but setcpu show me that i'm at 600Mhz? How can i get 7xx Mhz
?? Thank you
Click to expand...
Click to collapse
Install the tweaks in the thread "Tweaks for Cm6 & CM7" and install by xrecovery. Before that, make sure you have setcpu. After you install the tweak, go back into setcpu and you can raise it to 768mhz, repost your score soon =)
darrie1 said:
1049
Floyo v4
Jit disabled
Vm heapsize 34
Clocked at 768mHz
How did you get it so high??
sent from Xperia X10 Mini Pro
Click to expand...
Click to collapse
Hmm, nothing much I have changed, maybe because I unticked 'lock messaging in memory?' try that =p
Hmmm...what does the 'surface dithering' thingy do?It is recommended to be turned off at the 3rd post of the floyo rom.Anyways...
Floyo v4
SetCPU:122min 768max
Surface dithering: off
JIT disabled
VM Heap size: 34m
Using quadrant advanced(don't know if that makes any difference)
And tadaaaaa:1266 score
With surface dithering on,i got 1332.Weird...
Paremeters as you said but heap size 34
1354
Ive tried again,but now my score is out of screen lol. Lcd density is 120. Am i the only one who has this?
sent from Xperia X10 Mini Pro
Quadrant Standard
1. Floyo 3.6
2. Enabled surface dithering
3. 768mhz overclocked
4. JIT disabled
5. VM Heap size: 32m
SCORE: 1111
Quadrant Standard
1. Floyo v4
2. Enabled surface dithering
3. 768mhz overclocked
4. JIT disabled
5. VM Heap size: ?? (How can I know this one?)
SCORE: 1255
seems that v4 get a lil boost, but is it stabil?
royalbloodvi said:
Install the tweaks in the thread "Tweaks for Cm6 & CM7" and install by xrecovery. Before that, make sure you have setcpu. After you install the tweak, go back into setcpu and you can raise it to 768mhz, repost your score soon =)
Click to expand...
Click to collapse
I would not install that because you will modify few tweaks from owain. Try the thread Overclock cm6, thats only to insmod overclock module and works fine.
Hum, tried to take a screen shot of the results but can't find a program that works without distorting the image.
1- Floyo 4.0
2- Disabled surface dithering
3- 768mhz overclocked
4 - JIT disabled
5 - VM Heap size: Whatever is default on floyo 4.0
Result: 1307
galaningenieros said:
I would not install that because you will modify few tweaks from owain. Try the thread Overclock cm6, thats only to insmod overclock module and works fine.
Click to expand...
Click to collapse
owain's wifi tweak is from the same guy. sdcard tweak can be changed at performance settings as well. only thing thats changed is density.. should be alrite..
oh and in first post, i meant disable surface not enabled. corrected =)
Quadrant standard
1. Floyo: 4.0
2. 768 Mhz overclocked
3 JIT disabled
4. VM heapsize 32
Score 1302
Quadrant standart
VM heapsize 32
768 mhz overclock
JIT disabled
surface dithering disabled
Froyo 4.0
I can't see my result LOL it's out of screen
But i can say what is more whan 1000
After second try to run Quadrant full bench i had reboot
Sorry for my bad english
galaningenieros said:
I would not install that because you will modify few tweaks from owain. Try the thread Overclock cm6, thats only to insmod overclock module and works fine.
Click to expand...
Click to collapse
This will not make any damage, or fck anything, if you dont believe me, ask owain
royalbloodvi said:
owain's wifi tweak is from the same guy. sdcard tweak can be changed at performance settings as well. only thing thats changed is density.. should be alrite..
oh and in first post, i meant disable surface not enabled. corrected =)
Click to expand...
Click to collapse
Thats totally right, and pls dont call me "same guy"
PD: kidding
Quadrant Standard
Floyo 4.0
Disabled surface dithering
729mhz overclocked
JIT disabled
VM Heap size: 34m
Score 1249
If i overclock beyond 729 it goes into a reboot loop
this thread is worthless without a catch ... and without putting the quadrant version either ... 1.1.6 gives the best results in 1.1.7 ... and change the outcome of standard (free) to pay ...
Floyo v4 twaked
729 mhz
WM 32
Jit enable
1255 points
Hi,
I was wondering what are the best overall performance settings for the Galaxy S2
Currently I have these settings:
-CPU: On Demand
Min: 200
Max: 1200
Jit Enabled
Surface Dithering OFF
16bit transparency ON
Purging of Assets OFF
I was wondering if I should turn on surface dithering and purging of assets? Also what are the best CPU settings, and what is VM Heap size?
-J
HP Touchpad AnTuTu Benchmark v7.1.0
The ROM: (Only the ROM is install and the stand alone AnTuTu Benchmark v7.1.0 apk )
du_tenderloin-v12.5.1-20180920-1118-RC.zip
The extra Kernel:
SKZ-tenderloin-kernel-DU-Linaro_10_02_2018.zip
Du Original: Score 14542
scaling_max_freq
1512000
scaling_min_freq
648000
Governor: Interactive
zRAM 128M
gpu_available_frequencies
266667000 228571000 200000000 177778000 (No other options,defaults will be use on all test)
All the optimization changes are done in the Ramdisk and repack for a new boot image:
The “performance” governor will be use in all the following test:
Both cpu cores will be working at the highest frequency all the time.
Du Maximum frequency allow: Score 16827
scaling_max_freq
1782000
scaling_min_freq
648000
zRAM 128M
Each zRAM size setting is done in the (fstab.tenderloin) file in Ramdisk, new boot image created for each test.(I know it can be change inside Android Terminal )
Testing zRAM size performance: Score 16773
No zRAM 0
zRAM 1 Gigabyte: Score 16898
zRAM 1.5 Gigabyte: Score 16696
zRAM 2 Gigabytes: Score 16907
zRAM 3 Gigabytes: Score 16563
The maximum allow zRAM size is 3 Gigabytes, if more is created it will show as zero size in Android. The system works perfectly fine with 3g.
From doing the test with DU Kernel, the best results is with a 2g zRAM, the following will be to test the SKZ Kernel at maximum frequency with default zRAM and 2g.
SKZ_Kernel Maximum freqency: Score 17127
scaling_max_freq
1836000
scaling_min_freq
192000
zRAM 128M
GPU are set to maximum 3d 320000000 2d 266667000
zRAM 2 Gigabytes 17257
Technically it does not make any sense that a 1 Gigabytes of RAM device with 2 Gigabytes of zRAM performs better. But that was my curiosity of doing all the benchmark. When I made the changes to a 3g zRAM, I notice faster browsing, video loading and playing, then wanted to find out if it made a difference and the optimal size for the zRAM.
The maximum temperature for the CPU at 1890mHz both cores running all time was 63 Celsius which is 145 Fahrenheit.
I have screen shots of all the benchmark with more details.
Thanks. How do you root your TP to change values ? SuperSU ?
To make system read and write
https://forum.xda-developers.com/hp-touchpad/development/make-root-permanet-read-write-to-t3846567
To set CPU settings at boot.
https://forum.xda-developers.com/hp-touchpad/development/set-maximum-cpu-frequency-android-rom-t3850492
If need it to be change after boot inside Android terminal, then superSu is need it.
Nothing needs to be done if using ADB, to make CPU changes.
Interesting.
HP_TOUCHPAD said:
HP Touchpad AnTuTu Benchmark v7.1.0
The ROM: (Only the ROM is install and the stand alone AnTuTu Benchmark v7.1.0 apk )
du_tenderloin-v12.5.1-20180920-1118-RC.zip
The extra Kernel:
SKZ-tenderloin-kernel-DU-Linaro_10_02_2018.zip
Du Original: Score 14542
scaling_max_freq
1512000
scaling_min_freq
648000
Governor: Interactive
zRAM 128M
gpu_available_frequencies
266667000 228571000 200000000 177778000 (No other options,defaults will be use on all test)
All the optimization changes are done in the Ramdisk and repack for a new boot image:
The “performance” governor will be use in all the following test:
Both cpu cores will be working at the highest frequency all the time.
Du Maximum frequency allow: Score 16827
scaling_max_freq
1782000
scaling_min_freq
648000
zRAM 128M
Each zRAM size setting is done in the (fstab.tenderloin) file in Ramdisk, new boot image created for each test.(I know it can be change inside Android Terminal )
Testing zRAM size performance: Score 16773
No zRAM 0
zRAM 1 Gigabyte: Score 16898
zRAM 1.5 Gigabyte: Score 16696
zRAM 2 Gigabytes: Score 16907
zRAM 3 Gigabytes: Score 16563
The maximum allow zRAM size is 3 Gigabytes, if more is created it will show as zero size in Android. The system works perfectly fine with 3g.
From doing the test with DU Kernel, the best results is with a 2g zRAM, the following will be to test the SKZ Kernel at maximum frequency with default zRAM and 2g.
SKZ_Kernel Maximum freqency: Score 17127
scaling_max_freq
1836000
scaling_min_freq
192000
zRAM 128M
GPU are set to maximum 3d 320000000 2d 266667000
zRAM 2 Gigabytes 17257
Technically it does not make any sense that a 1 Gigabytes of RAM device with 2 Gigabytes of zRAM performs better. But that was my curiosity of doing all the benchmark. When I made the changes to a 3g zRAM, I notice faster browsing, video loading and playing, then wanted to find out if it made a difference and the optimal size for the zRAM.
The maximum temperature for the CPU at 1890mHz both cores running all time was 63 Celsius which is 145 Fahrenheit.
I have screen shots of all the benchmark with more details.
Click to expand...
Click to collapse
> I am wondering if this is a downloadable process or a inside replacement? I am a Novice, just currious and learning.. I have a 16 gig tp.. two others I got to de brick, or replace batt.. but this sounds interesting,
I tried downloading it and using DoubleStuffs toolbox to install it, I guessing that is wrong. it won't show in the SD card my question is how do I install it?
There is no hardware replacement or modification that can be done internally to the Touchpad.
All changes, tweaks or modifications are done using software.
If the tablet battery is not charge, then make sure you have a "Genuine HP charger that came with it" or the wireless charger.
Then plug it to charge, when you see the led lights blinking from side to side, let it charge for until it turns on. It can take very long time, could be a couple of days.
Happy learning all the information you need is on this Forum!
AnTuTu Benchmark is an app to test only performance, it will not change or make any modifications.
There are so many questions asked over and over again about how to configure the kernel for a desired outcome..... max performance, best battery holdup, fix freezing etc.
I will post this for those who did not attend school just for the bus ride or playtime. All dumb questions ignored so if I don't respond, you asked a dumb question or made a dumb comment.
We have a choice of 1 custom kernel (Eureka) that can be comprehensively tweaked thanks to many of the settings being moved into the DTB partition. Currently, there are 20 versions of the DTB image that can be selected on kernel installation - 10 enforcing and 10 permissive with 10 different mixes of cpu and gpu frequencies to suit most needs. The default sets everything to maximum and is the cause of the majority of freezing / crashing on an A205 phone that has a lower quality SoC than the other A series compatible phones. Most will end up using DTB2 to fix instability but even this might not be enough. You then have to consider a lower frequency DTB which lessens the attractiveness of using this custom kernel. Why not make your own flavor of DTB that can more accurately reflect what you can run on your specific SoC? Here's how:
Open up the Eureka Kenel zip file in whatever zip extractor you use.
Extract DTB2.img from the zip file (either permissive or enforcing version depending on what your chosen ROM needs)
Now open DTB2.img using a hex editor
Now look at the following which is a list of addresses (in hex), what the value at this address is defining and a list of possible settings. Frequencies are in MHz and the hex code to set it is the frequency in kHz example: 343MHz is 343000kHz, 053BD8 is hex for 343000.
GPU:
5CA5 GPU max freq
5CB5 GPU boost freq
5CC7 GPU boost %load
Possible freqs (MHz):
343 053BD8
450 06DDD0
545 0850E8
676 0A50A0
845 0CE4C8
1001 0F4628
1100 10C8E0
1200 124F80
1300 13D620
CPU smalls:
71B1 CPU min freq
71C1 CPU min freq
71D1 CPU max freq
71E1 CPU max freq
71F1 CPU boost freq
Possible freqs (MHz):
208 032C80
343 053BD8
449 06D9E8
546 0854D0
676 0A50A0
757 0B8D08
839 0CCD58
902 0DC370
1014 0F78F0
1144 1174C0
1248 130B00
1352 14A140
1482 169D10
1586 183350
1690 19C990
1794 1B5030
CPU bigs:
73B9 CPU min freq
73C9 CPU min freq
73D9 CPU max freq
73E9 CPU max freq
73F9 CPU boost freq
Possible freqs (MHz):
208 032C80
312 04C2C0
520 07EF40
728 0B1BC0
936 0E4840
1144 1174C0
1352 14A140
1560 17CDC0
1664 196400
1768 1AFA40
1872 1C9080
1976 1E26C0
2080 1FBD00
2184 215340
2288 22E980
First thing: The default min freq of 208MHz does not save any more battery than setting this to 343MHz (for small cpus) and 312MHz for bigs.
Next thing: The A205 more than likely will become unstable at anything above 2080MHz for the big cpus but can probably cope with 1794MHz on the small cpus. Each SoC is slightly different so you must test what your phone can handle, not what someone else's phone can do!
Next: It is highly unlikely that your A205 will be stable with the GPU maxxing out at 1300MHz. You will not be aware of this until the gpu governor actually cranks the gpu up to that frequency i.e. you can remain oblivious to it for some time and incorrectly assume something else is causing freezes / crashes / glitching.
Next: There are many more settings in the DTB relating to boost frequencies on various input conditions i.e. screen touches, keyboard clicks, mouse clicks etc. Most of these are set to peak at 1144MHz which seems quite reasonable so I have not sought to specifically identify and edit these.
Edit: So here are the input boost frequencies: (address, name, function, freqs)
I assume the first addresses in each block are for BIGS and the 2nd lot are for SMALLS. It seems to work well to set all the BIG freqs to 936 and all the SMALLS to 839 since there is an abundance of upward boosting from other sources such as the Governor and Exynos specific drivers.
50B1 key1 IKEY 1144
5181 key2 ITOUCHKEY 1144
5255 5259 525D 5285 5289 528D key3 ITOUCH 1144 1144 936 839 839 839
5369 536D 5391 5395key4 IMULTITOUCH 1144 936 839 839
545D 5461 5485 5489 key5 IKEYBOARD 1144 936 839 839
554D 5551 5575 5579 key6 IMOUSE 1144 936 839 839
5641 5669 key7 IMOUSE WHEEL 1144 839
5735 5739 575D 5761 key8 IPEN HOVER 1144 936 839 839
5821 5825 5849 584D key9 IPEN 1560 936 839 839
58E5 key10 IKEY_TWO 1872
Recommendations:
Min Freqs:
Set GPU to 343MHz, small CPUs to 343MHz and big CPUs to 312MHz. This is the maximum power saving you will get and offer minimal lag as the frequencies scale up to meet demand.
Set the GPU max freq to 845MHz while you are establishing what is stable for the CPUs.
Set GPU boost to 545 or 676MHz (depending on your compromise between battery and performance)
Set GPU boost load trigger level from the stock 75% down to 50~60%. Again depending on your compromise between battery and performance. Lowering this setting has a significant impact on reducing perceived lag so the stock setting was probably far to high.
Set big CPU max freq down to 2080MHz. This solves most crashing that is due to the cpu being overclocked too far.
Set small CPU max freq to 1794MHz unless your SoC proves to be unstable at this.
Set the CPU boost freqs to something quite low (around 700~900MHz). There are other boosts that override this basic CPU boost freq so you will almost never see it.
Note: If you want maximum battery savings, setting the max freqs lower seems like a logical thing to do but it is not! If you halve the cpu freqs, you double the amount of time they must remain on but you do not halve the power consumption so you end up consuming more power....
Make the changes and save the DTB.img file and flash it in recovery to DTB partition and reboot.
Install hKtweaks_v2.2.2 or your favorite kernel tweaker that can deal with Exynos SoCs (not many can)
Take a look at the cpu and gpu settings to confirm that your edited DTB file is producing the expected results i.e. min and max freqs agree with what you set.
You are done!
Err..... only kidding there is more to do.
Now back to the issue of the GPU max freq. In hKtweaks you can override the settings inherited from the DTB (within the limits set by the DTB). The max GPU freq is also associated with a core voltage. Lowering the voltages will make the GPU run cooler (use less power) but also it will not overclock as far as if the voltage is higher. Here is the dangerous bit - you can increase the voltage to make it overclock higher but cause it to overheat quicker which will make it throttle back to a lower freq. There is also an error in the DTB: Look at the settings for throttling the frequency back at certain temps. Set GPU LEVEL 3 Throttling Freq to 343MHz to fix the error.
Have a play with the GPU settings in hKtweaks without setting Apply on boot so if you set something that crashes the phone, it will revert to normal on a reboot. When you are positive you have the best GPU settings. then set Apply on boot.
Now you are done!
Err..... not quite, there is more.
O.K, assuming you have your custom DTB set up exactly how you want it, it is time to look at some important settings available through hKTweaks.
Firstly we will look at the CPU Governor selection. Interactive is the stock setting and if you watch what the CPU cores are doing with no background activities (kill all unnecessary apps), you will see the frequencies will be dancing around without settling down to the minimum freqs. This is partly due to a dodgy implementation of this governor by Samsung and also the excessive amount of invisible running services that allow Samsung and Google to plunder your personal data in realtime.
Touch the screen, scoll the screen etc. and you will see the various CPU boost features adding to the overall freqs.
The Eureka kernel has extra CPU Governors added - not all function correctly... be warned. Some Governors apply to all CPUs (big and small) and can't be configured separately. Some Governors can have separate configurations for big and smalls.
The way this works is whatever is set for cpu0 is applied to all smalls (cpu0~5) and whatever is set for cpu6 is set for all bigs (cpu6~7).
In a root filemanager, take a look at /sys/devices/system/cpu/cpufreq If you see a folder with the Governor's name, the Governor is applied to all cpus big and small with the same settings. If the Governor does not have a folder here, look in policy0 and policy6 folders. If the Governor has folders in there, the Governor can have separate settings for big and smalls. This is determined by however the Governor was set up at the kernel level.
I can't tell you what Governor is best for your usage patterns - I have already warned you that some are borked so all you can do is try them all while watching their behavior. until you find one that works for you.
Let's use Smartmax as an example. It is not aware of bigs and smalls so any settings are applied to all cpus. If you set this Governor for both big and small cpus, changing the settings in big will change the settings in small as well. The default settings will automatically pick up on the settings you made in your DTB. The remaining settings are not bad as they are but can be improved on.
Try it out, set Smatmax as the governor both both big and small and observe the cpu freqs on idle and when touching / wiggling the screen. You should see it scale up rapidly and scale down to min freqs much better than Interactive was doing. Have a play with other settings if you want - I tend to speed up the ramp down rate and increase the ramp down step to make the cpus return to min freq quicker (for battery saving). Once you have experimented with Smartmax, have a play with the remaining Governors to see if there is anything you like. Something I learnt from a previous phone with a MTK octa core SoC is that there is no power penalty for readily scaling the cpus up to a (sensible) maximum freq. This gives the phone a fast, lag free feel that everyone wants and the cpu will complete its tasks faster so it can return to idle faster. A foolish overclock freq will burn more power - usually when the core voltage is cranked up stupidly high to get the overclock - bad for phone, bad for battery! A bad Governor setup will chew battery if it doesn't pull the frequencies back to idle at low loads but view this in light of the amount of background services you are running. MyAndroidTools is an excellent app to view and take control of pesky services.
The GPU also has a choice of Governors but I recommend sticking with the default Interactive. You get to choose the GPU Highspeed freq and load and both of these settings can be embedded in your DTB. Play with the freq / voltage tables at your own risk!
More to come....
Latest additions:
HMP Settings:
689C 0000020C up threshold
68AC 000000D6 down threshold
68BC 000000FE semiboost_up_threshold
68CC 000000A3 semiboost_down_threshold
68DC 02625A00 bootboost-duration us
68EC 0000001E down_compensation_timeout mS
68FC 0016E360 down_compensation_high_freq uS
690C 000F4240 down_compensation_mid_freq uS
691C 000C3500 down_compensation_low_freq uS
A final note:
If you want to know which CPU, GPU governors are best and what the difference is between them, there is loads of information already gathered on this topic. Most of it is quite dated but still relevant. Here is a good starting point:
[REF][GUIDE]Saber's guide on CPU governors, I/O schedulers and more!
Collective guide of CPU governors, I/O schedulers and other kernel variables I present to you a wonderful collection of descriptions, comparisons and graphs of common kernel variables. Before continuing on the wonderful journey of Linux kernel...
forum.xda-developers.com
There is a lot of misunderstanding on Eureka Kernel and ROM forums around the issue of memory management - LMK, Virtual Memory etc. Many users want something for nothing like running every known Samsung, Google and Social Media app in the background on a A12.1 or 13 ROM on a phone with 3GB RAM.
The basics of virtual memory have not changed - set ZRAM to no more than 50% of the available memory and set ZSWAP Memory pool to no more than 30%. Swappiness is best at 100% and vfs_cache_pressure set to 50. These settings are the favorite targets for abuse in tweaks offered by people of little knowledge.
Once you have your virtual memory sorted and have made smart decisions on what services/apps you are going to allow to self start on boot and hide in the background, it is a simple case of looking at the free memory to figure out how many more apps can run before killing occurs. It should surprise no-one when it occurs..... blame yourself, not the kernel, not the ROM, but your decisions on what you run and how you configure the phone.......