Alright, below this, I will include an almost full guide to setting up STweaks (for those who do not want to use the provided profiles)
The CPU section contains the frequencies and voltages that you want to run at.
200mHz is the minimum speed, 1800mHz is the maximum speed. You can change these to affect your overall performance or battery life. Mine is currently set to 200mHz minimum, 1800mHz maximum. I have seen no hit on battery life at all (might be miniscule.)
Now for the voltages.. Each and every person will have a different set of voltages, as every CPU will be a little bit different. You can manually set your frequency to a certain level, use a CPU stress testing app (stability test) and drop the voltage by SMALL increments until you start to lose stability (system crashes, app force closes, etc.) I usually go UP one voltage step over the borderline stable voltage. I will post my voltages, but take caution, as my voltages are set pretty low compared to stock values on the kernel.
1800mHz - set to 1200000 uV or 1.2 volts.
1704mHz - set to 1175000 uV or 1.175 volts.
1600mHz - set to 1112500 uV or 1.1125 volts.
1500mHz - set to 1100000 uV or 1.1 volts.
1400mHz - set to 1062500 uV or 1.0625 volts.
1300mHz - set to 1025000 uV or 1.025 volts.
1200mHz - set to 1000000 uV or 1 volt.
1100mHz - set to 975000 uV or 0.975 volts.
1000mHz - set to 962500 uV or 0.9625 volts.
900mHz - set to 937500 uV or 0.9375 volts.
800mHz - set to 912500 uV or 0.9125 volts.
700mHz - set to 887500 uV or 0.8875 volts.
600mHz - set to 862500 uV or 0.8625 volts.
500mHz - set to 837500 uV or 0.8375 volts.
400mHz - set to 812500 uV or 0.8125 volts.
300mHz - set to 800000 uV or 0.8 volts.
200mHz - set to 787500 uV or 0.7875 volts. * BE CAREFUL WITH THIS ONE, it can cause your device to lock up when the screen is off, and need a battery pull if the voltage is too low.
CPU Scaling Section - this controls how your device will turn up the speed when it needs to.
Governor - This contols how the device will respond overall (power management, sleep, etc.) I will keep mine set to the Pegasusq governor unless I am running a benchmark, in that case, use perfomance (which locks the device to full speed and all 4 cores online)
Sampling Rate - how often the device will 'think' about changing the CPU speed. I have mine set to 15000 uS (15 milliseconds) so it is more responsive.
Sampling Down Factor - This enables you to create 'lag' when the device is at full speed, so it doesn't jump down frequencies when you don't want it to. I leave mine at default 1 sample, because I see no need for this.
Up Threshold - When a core hits this % utilization at a set frequency, then it will scale up to the next frequency. I have mine set to 96%, so the device will scale up slower and more reliably (keep in mind it makes this decision every 15 milliseconds.)
Down Differential - When the device scales down, (drops frequency) it must get below this % utilization to scale down ( UP THRESHOLD minus DOWN DIFFERENTIAL ) I have mine set to 5%, so it drops frequency at or below 91% utilization.
Frequency for Responsiveness - This helps keep the device smooth at lower frequency, and when the frequency is below the set spot, it will use a DIFFERENT up threshold so the device scales up faster and doesn't lag. My frequency setting is 500mHz, and the up threshold for it is set at 70%.
Frequency for Fast Down - this sets the frequency at which the device can use aggressive down scaling, much like the opposite of frequency for responsiveness. I have mine set to 1400mHz, and the up threshold is set to 98%, so the device only scales up if it really needs to.
Frequency Step - This applies to the Fast Down setting, and whenever the device gets above 98% utilization, then it will increase the frequency by a SET percentage of the maximum frequency. So if you set 10%, and are have 1800mHz max, it will increase to the closest step that adds 180mHz. I have mine set to 6%, so it increases by 108mHz.
The up threshold and frequency step decrease confuse me for this, but I have the up threshold set to 2%, and the frequency step set to 3%.
I didn't touch the flexrate settings, as everything else should control this area.
CPU Hotplug - This section will control how the device turns its cores on and off.
CPU Up Rate - How many samples you want to take until a core decides to turn on. (Sampling rate times your setting) I have mine set to 12, so if the conditions are correct, it takes 180 milliseconds to turn a core on.
CPU Down Rate - How many samples you want to take until a core decides to turn off. (Same thing as CPU up rate) Mine is set to 10, so it takes 150 milliseconds to turn off a core if it isn't being used.
Core Upbring Count - How many cores you want to bring online when the conditions are right. Mine is set to 1, I'm sure more will increase performance and hurt battery life.
Configuration Overrides - These can set you device to always have a certain amount of cores online, I don't use them (leave at 0.)
Hotplug Conditionals - These perameters are set to control when the cores turn on and off. Below are MY values
Hotplug 1 Core to ONLINE (make 2 cores online) - 600mHz
Hotplug 2 Cores to OFFLINE (make 1 core online) - 500mHz
Hotplug 2 Cores to ONLINE (make 3 cores online) - 700mHz
Hotplug 3 Cores to OFFLINE (make 2 cores online) - 600mHz
Hotplug 3 Cores to ONLINE (make 4 cores online) - 800mHz
Hotplug 4 Cores to OFFLINE (make 3 cores online) - 700mHz
The rest of this section, I left at DEFAULT values, because I did not understand them.
GPU - This section controls the frequencies and voltages of your GPU.
Maximum Frequency - How high you want your GPU to clock to, mine is set to 733mHz.
Minimum Frequency - How low you want your GPU to clock to, mine is set to 108mHz.
Up Threshold - Like the CPU setting, the percentage of utilization you achieve before the GPU scales up. Mine is set to 90%.
Down Differential - When you want your GPU to scale down lower, (Up threshold minus down differential.) Mine is set to 10%, so when the GPU hits 80% utilization on a speed, it drops to a lower frequency.
Utilization Timeout - Basically is the sampling speed of the GPU (how fast you want it to make decisions to change speed.) Mine is set to 25 milliseconds.
Voltages - Test these the same way as the CPU, get a GPU stress testing app, and set a certain frequency. When you see artifacts or glitches on your screen, then the voltages are too low. Below are MY values.
54mHz - 825mV
108mHz - 875mV
160mHz - 950mV
266mHz - 975mV
350mHz - 1050mV
440mHz - 1100mV
533mHz - 1125mV
640mHz - 1150mV
733mHz - 1175mV
800mHz - 1200mV (This clock speed proved to be slightly unstable at 1175mV, though still usable)
I/O section - These values/settings control how your device writes/reads things from the SD card, or internal storage.
I left both of my storage schedulers at ROW but you can change them and play around. I believe that deadline is the best for overall performance, but can be unstable sometimes.
I/O Read Ahead - These control the cache file on the internal/external storage. I have my internal set to 1536kB, and external set to 2048kB, because those values gave me overall good write/read speeds.
Dynamic Fsync - From what I know, this helps keep the data from being corrupted by creating a buffer between data being written and the storage. Correct me if I'm wrong. I kept it enabled.
The entire audio section is pretty self explanatory, and I'm getting tired of typing all of this, so if you need help, PM me or comment.
Again, take this entire post with caution. What works with my device, may make yours unstable. I only provided mine to give you a baseline, my values offer good performance and battery life anyways. Feel free to correct any of my errors by PM or comment, and I will gladly change my post to accommodate for my errors.
Here's my more performance oriented settings. Averages 19500 on Antutu, and 7400 on Quadrant Standard (Advanced version adds 1000 to score) This doesn't lag at all between screens, animations, etc. The only lag I've seen is when my apps rarely crash.
CPU Max - 1800mHz
CPU Min - 200mHz
Voltages from OP
Pegasusq governor
Sampling Rate - 15000uS
Sampling Down Factor - 1
Up Threshold - 90%
Down Differential - 10%
Frequency for Responsiveness - 600mHz
Up Threshold @ Min Freq - 60%
Frequency at Fast Down - 1400mHz
Up Threshold at Fast Down - 94%
Frequency Step - 25%
Up Threshold Differential - 5%
Frequency Step Decrease - 10%
Flexrate Enabled - 700mHz, 10000uS
CPU Up Rate - 8 samples
CPU Down Rate - 10 samples
Core Upbring Count - 1
*Default Configuration Overrides*
1 Core to Online - 300mHz
2 Cores to Offline - 200mHz
2 Cores to Online - 400mHz
3 Cores to Offline - 300mHz
3 Cores to Online - 500mHz
4 Cores to Offline - 400mHz
*Runqueue Depths*
1 Core to Online - 155
2 Cores to Offline - 155
2 Cores to Online - 250
3 Cores to Offline - 250
3 Cores to Online - 340
4 Cores to Offline - 340
CPU Online Load Bias - 2 cores
CPU Online Bias Up Threshold - 50%
CPU Online Bias Down Threshold - 30%
GPU Max - 733mHz
GPU Min - 160mHz
Up Threshold - 85%
Down Differential - 5%
Utilization Timeout - 25ms
Voltages from OP
Internal/SD Card Schedulers - SIO
Internal/SD Card Read Ahead - 2048kB
Dynamic FSync - Enabled
Hi,
how can I be sure the cpu hoptplug section is turned on?
gannjunior said:
Hi,
how can I be sure the cpu hoptplug section is turned on?
Click to expand...
Click to collapse
The governor, Pegasusq, does the hotplugging. So it's on by default when selecting it. I don't know if it applies to Performance too.
EDIT: Please share the performance oriented profile! What do you mean you need help posting it? You should have reserved another post. But I'm definitely interested!
Thanks for the info OP.
DroidOnRoids said:
The governor, Pegasusq, does the hotplugging. So it's on by default when selecting it. I don't know if it applies to Performance too.
EDIT: Please share the performance oriented profile! What do you mean you need help posting it? You should have reserved another post. But I'm definitely interested!
Click to expand...
Click to collapse
I don't know how to create a flashable zip. I can just post the settings later.
I left my phone unplugged overnight, only lost 2% battery. So it's good with battery too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I605 using xda premium
Here ya go: [GUIDE] How to make a cwm recovery flashable zip
DroidOnRoids said:
Here ya go: [GUIDE] How to make a cwm recovery flashable zip
Click to expand...
Click to collapse
Thanks. I'll set one up as soon as I get my new computer (Monday) I'll just post my settings in the 2nd comment.
Sent from my SCH-I605 using xda premium
ChaoticWeaponry said:
Thanks. I'll set one up as soon as I get my new computer (Monday) I'll just post my settings in the 2nd comment.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
I appreciate the performance settings! Really notice a difference!
I'm just going to bump this. People should take a look at this! You did a really good job with it!
Ive been using your Performance profileall week and loving it! Great work
I have also had very good luck with the OPs settings.
I didn't think my phone would even handle voltage settings this low, but it's been perfectly stable for the past 2 days.
ChaoticWeaponry said:
Here's my more performance oriented settings. Averages 19500 on Antutu, and 7400 on Quadrant Standard (Advanced version adds 1000 to score) This doesn't lag at all between screens, animations, etc. The only lag I've seen is when my apps rarely crash.
CPU Max - 1800mHz
CPU Min - 200mHz
Voltages from OP
Pegasusq governor
Sampling Rate - 15000uS
Sampling Down Factor - 1
Up Threshold - 90%
Down Differential - 10%
Frequency for Responsiveness - 600mHz
Up Threshold @ Min Freq - 60%
Frequency at Fast Down - 1400mHz
Up Threshold at Fast Down - 94%
Frequency Step - 25%
Up Threshold Differential - 5%
Frequency Step Decrease - 10%
Flexrate Enabled - 700mHz, 10000uS
CPU Up Rate - 8 samples
CPU Down Rate - 10 samples
Core Upbring Count - 1
*Default Configuration Overrides*
1 Core to Online - 300mHz
2 Cores to Offline - 200mHz
2 Cores to Online - 400mHz
3 Cores to Offline - 300mHz
3 Cores to Online - 500mHz
4 Cores to Offline - 400mHz
*Runqueue Depths*
1 Core to Online - 155
2 Cores to Offline - 155
2 Cores to Online - 250
3 Cores to Offline - 250
3 Cores to Online - 340
4 Cores to Offline - 340
CPU Online Load Bias - 2 cores
CPU Online Bias Up Threshold - 50%
CPU Online Bias Down Threshold - 30%
GPU Max - 733mHz
GPU Min - 160mHz
Up Threshold - 85%
Down Differential - 5%
Utilization Timeout - 25ms
Voltages from OP
Internal/SD Card Schedulers - SIO
Internal/SD Card Read Ahead - 2048kB
Dynamic FSync - Enabled
Click to expand...
Click to collapse
Are your settings similar to any of the flashable profiles listed under Perseus kernel?
GermanGuy said:
Are your settings similar to any of the flashable profiles listed under Perseus kernel?
Click to expand...
Click to collapse
Somewhat. I edited most of the settings.
Sent from my SCH-I605 using xda premium
This gave me the perfect reason to use multi window, no wonder why this phone doesn't have a dedicated recents button!! Looking forward to testing this.
Sent from my SCH-I605 using Tapatalk 2
jsminnis said:
This gave me the perfect reason to use multi window, no wonder why this phone doesn't have a dedicated recents button!! Looking forward to testing this.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Omg bro lmao I just noticed what you meant about the multi window wow I totally forgot about that lmao I just finished setting up these settings but my dumb ass wrote all those settings from the OP to 2 pieces of paper wow what a retarded move I just pulled ha ha ha.
Sent from my SPH-L900 using Tapatalk 2
yellowman82 said:
Omg bro lmao I just noticed what you meant about the multi window wow I totally forgot about that lmao I just finished setting up these settings but my dumb ass wrote all those settings from the OP to 2 pieces of paper wow what a retarded move I just pulled ha ha ha.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Lmao, i dreamed of situations like these when I knew I was getting this phone.
Anyway, about the settings. I recommend not setting on boot till you've had the screen of for awhile. I got a boot loop, most likely from the voltage settings so I will play with those some more.
Tip: If you get a bootloop, instead of pulling the battery just wait for when the phone restarts then press and hold vol up, home and power to go to recovery. I do this rather than taking the back off and risking breaking the little clips like I did on my nexus.
Sent from my SCH-I605 using Tapatalk 2
jsminnis said:
Lmao, i dreamed of situations like these when I knew I was getting this phone.
Anyway, about the settings. I recommend not setting on boot till you've had the screen of for awhile. I got a boot loop, most likely from the voltage settings so I will play with those some more.
Tip: If you get a bootloop, instead of pulling the battery just wait for when the phone restarts then press and hold vol up, home and power to go to recovery. I do this rather than taking the back off and risking breaking the little clips like I did on my nexus.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the tip but instead of a bootloop my phone just frozed so I had to do a battery pull and about the voltages you have to increase back up a bit when playing with them right?
Sent from my SPH-L900 using Tapatalk 2
yellowman82 said:
Thanks for the tip but instead of a bootloop my phone just frozed so I had to do a battery pull and about the voltages you have to increase back up a bit when playing with them right?
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Yes. Crashes are usually from too low of voltages. Go up a step or two from my settings.
Sent from my SCH-I605 using xda premium
thanks for the tweak using it now, very fast.
Related
i'm using SetCPU:
governor: conservative
freq range: 200-1,200 mhz
undervolted
have tried various kernels (ninphetamine, speedmod, ragemod - current, mirage) and roms (cognition, solarflare, and leomar -current)
one thing in common is that it in doesn't keep the freq at the minimum for a longer period. even after an 8 hour idle time at night, my phone's at 30% on the 200 mhz, and at about 35% at the 800 mhz.
anyone with the same problem?
i'm using only the setCPU widget and no other downloaded/installed apk's which run in the background (i.e. ATK, etc)
The phone will clock up as and when required, this is normal, it won't stick to the lowest unless you clamp the scaling down, also the phone will clock up on touch inputs to keep things smooth.
Sent from my GT-I9100 using xda premium
thanks!
+1
poch_1421 said:
i'm using SetCPU:
governor: conservative
freq range: 200-1,200 mhz
undervolted
have tried various kernels (ninphetamine, speedmod, ragemod - current, mirage) and roms (cognition, solarflare, and leomar -current)
one thing in common is that it in doesn't keep the freq at the minimum for a longer period. even after an 8 hour idle time at night, my phone's at 30% on the 200 mhz, and at about 35% at the 800 mhz.
anyone with the same problem?
i'm using only the setCPU widget and no other downloaded/installed apk's which run in the background (i.e. ATK, etc)
Click to expand...
Click to collapse
Aren't you using a Screen Off profile...? A powersave bias value could also help
Hey guys!
I was wondering if anyone can give me some info on the differences between the governors with doomkernel and the schedulers.
Thanks!
Cheers,
This was posted by DooMLoRD, i just copied the post not all governors are there:
2. Governors In the Linux Kernel ================================
2.1 Performance ------------------------------
The CPUfreq governor "performance" sets the CPU statically to the highest frequency within the borders of scaling_min_freq and scaling_max_freq.
2.2 Powersave ----------------------------
The CPUfreq governor "powersave" sets the CPU statically to the lowest frequency within the borders of scaling_min_freq and scaling_max_freq.
2.3 Userspace ----------------------------
The CPUfreq governor "userspace" allows the user, or any userspace program running with UID "root", to set the CPU to a specific frequency by making a sysfs file "scaling_setspeed" available in the CPU-device directory.
2.4 Ondemand ---------------------------
The CPUfreq governor "ondemand" sets the CPU depending on the current usage. To do this the CPU must have the capability to switch the frequency very quickly. There are a number of sysfs file accessible parameters:
sampling_rate: measured in uS (10^-6 seconds), this is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of around '10000' or more.
show_sampling_rate_(min|max): the minimum and maximum sampling rates available that you may set 'sampling_rate' to.
up_threshold: defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then decide that the CPU frequency needs to be increased.
ignore_nice_load: this parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilisation' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation. This is useful if you are running a CPU intensive calculation on your laptop that you do not care how long it takes to complete as you can 'nice' it and prevent it from taking part in the deciding process of whether to increase your CPU frequency.
2.5 Conservative -------------------------------
The CPUfreq governor "conservative", much like the "ondemand" governor, sets the CPU depending on the current usage. It differs in behaviour in that it gracefully increases and decreases the CPU speed rather than jumping to max speed the moment there is any load on the CPU. This behaviour more suitable in a battery powered environment. The governor is tweaked in the same manner as the "ondemand" governor through sysfs with the addition of:
freq_step: this describes what percentage steps the cpu freq should be increased and decreased smoothly by. By default the cpu frequency will increase in 5% chunks of your maximum cpu frequency. You can change this value to anywhere between 0 and 100 where '0' will effectively lock your CPU at a speed regardless of its load whilst '100' will, in theory, make it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand" governor but for the opposite direction. For example when set to its default value of '20' it means that if the CPU usage needs to be below 20% between samples to have the frequency decreased.
2.6 Interactive ------------------------------
The CPUfreq governor "interactive" is designed for low latency, interactive workloads. This governor sets the CPU speed depending on usage, similar to "ondemand" and "conservative" governors. However there is no polling, or 'sample_rate' required to scale the CPU up.
Sampling CPU load every X ms can lead to under powering the CPU for X ms, leading to dropped framerate, stuttering UI etc..
Scaling the CPU up is done when coming out of idle, and like "ondemand" scaling up will always go to MAX, then step down based off of cpu load.
There is only one tuneable value for this governor:
min_sample_time: The ammount of time the CPU must spend (in uS) at the current frequency before scaling DOWN. This is done to more accurately determine the cpu workload and the best speed for that workload. The default is 50ms.
2.7 MinMax ------------------------------
The CPUfreq governor "maxmin" tries to minimize the frequency jumps by limiting the selected frequencies to only two frequencies: either the min or the max frequency of the current policy. The frequency is raised or lowered according to the current load and the 'up_threshold' and 'down_threshold'.
Its parameters and implementation are similar to that of conservative.
It does not have the freq_step parameter as it jumps right from min to max and vice-versa.
The sampling_down_factor, unlike conservative, will count the minimal number of samplings since the last time we saw the 'up_threshold' load on the CPU. Hence it is set to higher default and acts as a limiter not to do too many frequency jumps without hurting the performance.
Thanks sorry, didnt see it for some reason. Ignore my questions.
Cheers,
oppiee said:
Thanks sorry, didnt see it for some reason. Ignore my questions.
Cheers,
Click to expand...
Click to collapse
One thing to note pal. All chipsets have different tolerances so whereas interactive works best for me, it may not be good for u. Just test em and use CPU spy/ ur own judgement to c which suits ur phone best.
Sent from my X10i using XDA App
Yup I am currently fiddling around with the different settings. The main thing I want to accomplish is not to have lag when im scrolling and opening up basic apps such as dialer and browser. I dont really play games. I hate the fact that the phone lags up sometimes. So far Its ok, but getting some WLOD on super high freq.
Any suggestions?
oppiee said:
Yup I am currently fiddling around with the different settings. The main thing I want to accomplish is not to have lag when im scrolling and opening up basic apps such as dialer and browser. I dont really play games. I hate the fact that the phone lags up sometimes. So far Its ok, but getting some WLOD on super high freq.
Any suggestions?
Click to expand...
Click to collapse
Can u post a screenshot of CPU tuner or whatever u use of freqs u use? Also are u using doomkernel fs version as I think some handsets can't even boot up oc kernel.
Sent from my X10i using XDA App
Any good programs to take screen shots? I am using the highest OC kernel by DL, and using doomkernel wolfbreak V7b6.
Not mean to sound patronising pal but just type screen shot into android market theres plenty
Edit: ur phone prob can't handle the overclock. Read the kernel thread it says this pal.
Sent from my X10i using XDA App
Oh i think there might has been some misunderstanding. My phone is running fine, just doing some testing. at 1.229 Mhz I tend to get WLODs, using minmax with SIO.
At 1.114 and 245, using min max with SIO. everything is fine so far. I just thought you wanted to know for your own purposes.
Cheers
Sorry buddy I misunderstood
Sent from my X10i using XDA App
thers some missing from the top
lagfree
scary
brazilianwax
savaged zen
what do theese do
also whats the best settings from all of them from your opinion
I have:
Brazilianwax
Smoothass
Lagfree
Smartassv2
SavagedZen
Scary
Smartass
Minmax
Interactivex
Interactive
Conservative
Userspace
Powersave
OnDemand
Performance.
Not used them all but lagfree is (as suggested free from lag & smooth. Brazilianwax didnt work for me very laggy. Scary was quite good also, along with interactive. Not really tested the others enough to pass comment to be honest
Ok I'm hoping this post sticks, because no one has this listed anywhere it seems. I have compiled a list of commonly recognized cpu governors and frequencies that the EVO 3D processor and different kernels recognize. The max frequency depends on the kernel you flashed.
Ok so the Evo 3D processor only changes in intervals of 54 so I
researched. No one seems to have a guide on the net that gives those
numbers. The OC Daemon on ViperRom tells you all your options when
you go into terminal to change it, and it also gives you all the
processor governor options too. Where as with MeanRom and Anthrax
Kernel it gives you the minimum and maximum but shows nothing
inbetween, both with governors and frequencies.
starting with minimum:
192000
216000
270000
324000
378000
432000
486000
540000
594000
648000
702000
756000
810000
864000
918000
972000
1026000
1080000
1134000
1188000 Stock max, not quite 1.2 Ghz
1242000 A true 1.2 Ghz
1296000
1350000
1404000
1458000
1512000
1566000
1620000
1674000
1728000 Zedomax says this is most stable max freq. for him on ViperRom
1782000
1836000
1890000
1944000 Only read of one person having stability with this
Governor settings:
Ondemand - when you need it
Powersave - obviously
Conservative - straight forward
Interactive - sounds cut and dry
Performance - I guess hardcore gaming
Userspace - not sure what this one does
Auto - Uses kernel to determine
The userspace governer is basically a legacy thing (see: http://www.thinkwiki.org/wiki/How_to_make_use_of_Dynamic_Frequency_Scaling) that allows you or an application/module that resides in userspace to manually adjust the CPU frequency.
This can be used in an android world by allowing an app to modify the CPU frequency without relying on root access, if I remember correctly. It's basically useless though since I don't think any applications aside from maybe setcpu would use such a feature since most applications automatically assume you aren't rooted thus are using the typical default cpu governor.
Good post.
umm.. i think this is in the wrong spot??? maybe im wrong?? should be in the general...
evod3 said:
umm.. i think this is in the wrong spot??? maybe im wrong?? should be in the general...
Click to expand...
Click to collapse
Then how do I move it? Honest question. This is my first true post/thread that I started.
It's just when I go looking for answers for my phone I go directly to the CDMA section. Only after I can't find my answer there do I branch out and search the whole site. I usually dont think of the EVO 3D as a GSM phone. I mean generally speaking the EVO 3D is more on sprint than any other network world wide.
Other than that does anyone else have the problem of not being able to change voltages? I mean the SetCPU app shows it as a tab but when you purchase and download it there's no tab for votages. I dont wanna pay for another app and not have what it advertises. I emailed the devs of setcpu and never heard back. so I feel like I waisted my money on the dern thing.
I want to be able to truely undervolt and overclock my cpu for power saving reasons. Come on. My stock battery life was like 4 hours, 5 tops, with moderate use. ViperRom changed that to 18+ with moderate use. Now Im using MeanRom with the Anthrax kernel, overclocked to 1.3 GHz and im getting a little more than 36 hours with moderate use.
I'm betting with undervolting we could get a lot more battery life.
SketchyStunts said:
You can run viperROM.....it comes with the Tiamat kernel & has vipercontrol/vipermod baked in & can undervolt your heart out. I believe the it come with voltages -100 from stock. Had mine -125 & the most stable ROM i've ran yet.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24325646
This is from another thread I found earlier. Not sure what is meant buy -100. Is that mV V MV or what?
stephangardner said:
Then how do I move it? Honest question. This is my first true post/thread that I started.
It's just when I go looking for answers for my phone I go directly to the CDMA section. Only after I can't find my answer there do I branch out and search the whole site. I usually dont think of the EVO 3D as a GSM phone. I mean generally speaking the EVO 3D is more on sprint than any other network world wide.
Other than that does anyone else have the problem of not being able to change voltages? I mean the SetCPU app shows it as a tab but when you purchase and download it there's no tab for votages. I dont wanna pay for another app and not have what it advertises. I emailed the devs of setcpu and never heard back. so I feel like I waisted my money on the dern thing.
I want to be able to truely undervolt and overclock my cpu for power saving reasons. Come on. My stock battery life was like 4 hours, 5 tops, with moderate use. ViperRom changed that to 18+ with moderate use. Now Im using MeanRom with the Anthrax kernel, overclocked to 1.3 GHz and im getting a little more than 36 hours with moderate use.
I'm betting with undervolting we could get a lot more battery life.
http://forum.xda-developers.com/showthread.php?p=24325646
This is from another thread I found earlier. Not sure what is meant buy -100. Is that mV V MV or what?
Click to expand...
Click to collapse
That was from awile back when I had the EVO 4g & used vipermod to undervolt on AOSP. I used to get insane battery life. Miss that. Lol
Wait, maybe not can't remember. Stuck in 1x hell at the moment so can't check the link. Grrrrrr
Sent from my PG86100 using xda premium
I disagree. Because this has to do with frequency clocking, I'd say this is very much good to have stuck here.
Perhaps adding further information about undervolting would be even better?
LiquidSolstice said:
I disagree. Because this has to do with frequency clocking, I'd say this is very much good to have stuck here.
Perhaps adding further information about undervolting would be even better?
Click to expand...
Click to collapse
I hope we get some more insight.
I rooted for the sole purpose of getting better battery life. I read about undervolting, overclocking and underclocking to save battery. Then I find I can't change voltages like I thought. I know its out there just gotta get the right dev to respond to this thread.
Sent from my PG86100 using xda premium
stephangardner said:
I hope we get some more insight.
I rooted for the sole purpose of getting better battery life. I read about undervolting, overclocking and underclocking to save battery. Then I find I can't change voltages like I thought. I know its out there just gotta get the right dev to respond to this thread.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Best of luck to you, I'm sure many will thank you for this
stephangardner said:
. Then I find I can't change voltages like I thought..
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
What rom are you running? in system tuner pro click the "cpu" button you'll come to the screen where you set clock speeds, at the very top is a tab labled "voltage" hit that and there you can set your voltages. be careful though some phones dont play well with some setting, thats why i dont preset voltages in my ROM.
Originally Posted by stephangardner
. Then I find I can't change voltages like I thought..
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
What rom are you running? in system tuner pro click the "cpu" button you'll come to the screen where you set clock speeds, at the very top is a tab labled "voltage" hit that and there you can set your voltages. be careful though some phones dont play well with some setting, thats why i dont preset voltages in my ROM.
Click to expand...
Click to collapse
+1 for System Tuner Pro, love that app! I, too, hope this thread sticks cause I've been looking for PRECISELY this info to no avail recently!
Subscribed! Howdy folks!
Relevant to Dev. This stays here....
Nice work getting this here, OP.
Here is a great thread with a TON of useful information about kernels, govenors,I/O schedulers, kernel modules and a lot more... Very informative.
http://forum.xda-developers.com/showthread.php?t=1369817
Sent from my PG86100 using Tapatalk 2 Beta-5
steal25 said:
What rom are you running?
Click to expand...
Click to collapse
First Rom was viperRom then I added the rc remix kernel. Second Rom was the meanRom then a few hours later added the anthrax kernel
Sent from my PG86100 using xda premium
droidphile said:
1. GOVERNORS
I) MANUAL:
These are the 18 governors we're talking about.
1) Ondemand 2) Ondemandx 3) Conservative 4) Interactive 5) Interactivex 6) Lulzactive 7) Smartass 8) SmartassV2 9) Intellidemand 10) Lazy 11) Lagfree 12) Lionheart 13) LionheartX 14) Brazilianwax 15) SavagedZen 16) Userspacce 17) Powersave 18) Performance
1) Ondemand: Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. (You can change this behavior using smooth scaling parameters, refer Siyah tweaks at the end of 3rd post.) Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question. So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle. Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings. One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval. The instant requirement can response quickly to workload change, but it does not usually reflect workload real CPU usage requirement in a small longer time and it possibly causes frequently change between highest and lowest frequency.
2) Ondemandx: Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
3) Conservative: A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle. Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency. The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization. For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.
4) Interactive: Can be considered a faster ondemand. So more snappier, less battery. Interactive is designed for latency-sensitive, interactive workloads. Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle. The governor has the following advantages: 1) More consistent ramping, because existing governors do their CPU load sampling in a workqueue context, but interactive governor does this in a timer context, which gives more consistent CPU load sampling. 2) Higher priority for CPU frequency increase, thus giving the remaining tasks the CPU performance benefit, unlike existing governors which schedule ramp-up work to occur after your performance starved tasks have completed. Interactive It's an intelligent Ondemand because of stability optimizations. Why?? Sampling the CPU load every X ms (like Ondemand) can lead to under-powering the CPU for X ms, leading to dropped frames, stuttering UI, etc. Instead of sampling the CPU at a specified rate, the interactive governor will check whether to scale the CPU frequency up soon after coming out of idle. When the CPU comes out of idle, a timer is configured to fire within 1-2 ticks. If the CPU is very busy between exiting idle and when the timer fires, then we assume the CPU is underpowered and ramp to max frequency.
5) Interactivex: This is an Interactive governor with a wake profile. More battery friendly than interactive.
6) Lulzactive: This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites. Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency. New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down. When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down. Example: Consider inc_cpu_load=70 pump_up_step=2 pump_down_step=1 If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800. If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
7) Smartass: Result of Erasmux rewriting the complete code of interactive governor. Main goal is to optimize battery life without comprising performance. Still, not as battery friendly as smartassV2 since screen-on minimum frequency is greater than frequencies used during screen-off. Smartass would jump up to highest frequency too often as well.
8) SmartassV2: Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
9) Intellidemand: Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors ) To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.
10) Lazy: This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.
11) Lagfree: Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
12) Lionheart: Lionheart is a conservative-based governor which is based on samsung's update3 source. Tweaks comes from 1) Knzo 2) Morfic. The original idea comes from Netarchy. See here. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks: sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe). up_threshold:60 down_threshold:30 freq_step:5 Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
13) LionheartX LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.
14) Brazilianwax: Similar to smartassV2. More aggressive ramping, so more performance, less battery.
15) SavagedZen: Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.
16) Userspace: Instead of automatically determining frequencies, lets user set frequencies.
17) Powersave: Locks max frequency to min frequency. Can not be used as a screen-on or even screen-off (if scaling min frequency is too low).
18) Performance: Sets min frequency as max frequency. Use this while benchmarking!
So, Governors can be categorized into 3/4 on a high level: 1.a) Ondemand Based: Works on "ramp-up on high load" principle. CPU busy-time is taken into consideration for scaling decisions. Members: Ondemand, OndemandX, Intellidemand, Lazy, Lagfree. 1.b) Conservative Based: Members: Conservative, Lionheart, LionheartX 2) Interactive Based: Works on "make scaling decision when CPU comes out of idle-loop" principle. Members: Interactive, InteractiveX, Lulzactive, Smartass, SmartassV2, Brazilianwax, SavagedZen. 3) Weird Category: Members: Userspace, Powersave, Performance.
Click to expand...
Click to collapse
Good explanations as to what the OP was trying to relay.
gunfromsako said:
Here is a great thread with a TON of useful information about kernels, govenors,I/O schedulers, kernel modules and a lot more... Very informative.
http://forum.xda-developers.com/showthread.php?t=1369817
Click to expand...
Click to collapse
I'll have to read this one when I'm on a computer. Way to much info for the app.
steal25 said:
in system tuner pro click the "cpu" button you'll come to the screen where you set clock speeds, at the very top is a tab labled "voltage" hit that and there you can set your voltages.
Click to expand...
Click to collapse
Brownie points for this guy. Downloaded that app now and loving it. I'm gonna start with a 10 mV decrease on all voltages then do like 2 mV increments till I have issues then I'll report back.
dimebagdan65 said:
+1 for System Tuner Pro, love that app!
Click to expand...
Click to collapse
+2
By the way guys and gals does anyone else here have dyslexia? I didn't think I could get into all this because of it but I find it kinda soothing. Like working on cars helps with my ADHD. I feel like Jessie from The Fast And The Furious. Ha ha
Sent from my PG86100 using xda premium
oohaylima said:
Good explanations as to what the OP was trying to relay.
Click to expand...
Click to collapse
Same post I linked right above you...
I wipe till it bleeds...
gunfromsako said:
Same post I linked right above you...
I wipe till it bleeds...
Click to expand...
Click to collapse
I know. All I did was quote the author of the section that pertains to the governor in which the OP was trying to break down in the beginning.
I'm a big fan of keeping things under one thread for easy fluidity of related information.
gunfromsako said:
Same post I linked right above you...
I wipe till it bleeds...
Click to expand...
Click to collapse
Oh... my... GOD! I friggin love your sig! My sides hurt! I'm totally with ya! Never want problems? Always start with a clean slate! Duh... ^_^
I always keep my phone undervolted -50mv @ 1.5GHz intellanthrax. That's the farthest I can go without problems.
sent from America...F__k Yeah!
Comin again to save the motherf**kin day yeah!
Only one question... Rockin out or ballad style? XD
I was wondering what CPU layout all of you guys are using. This including governor I/O and voltages. I have been experimenting but I'm not used to dual-core or having so many options. Let me know what you all think!
I like battery life, but I also have an extended battery and two spares, so there can be a little leeway for performance sake. I would like the phone to be able to play music with the screen off, but it seems I'm either clocking too high (gets warm often) or Pandora is using a lot of resource.
Thanks guys!
Sent From The PACMan Lair using Tapatalk 4 Beta On My Rezound.
tmanschuette said:
I was wondering what CPU layout all of you guys are using. This including governor I/O and voltages. I have been experimenting but I'm not used to dual-core or having so many options. Let me know what you all think!
I like battery life, but I also have an extended battery and two spares, so there can be a little leeway for performance sake. I would like the phone to be able to play music with the screen off, but it seems I'm either clocking too high (gets warm often) or Pandora is using a lot of resource.
Thanks guys!
Sent From The PACMan Lair using Tapatalk 4 Beta On My Rezound.
Click to expand...
Click to collapse
For a balance between batterylife and performance, I use wheatley on the first core, and lionheart on the second core. I/O scheduler is ROW.
I undervolt across the board by -50mV. First core UC to 1350 MHz, second core OC to 1620 MHz.
If you don't care about battery life, Lionheart both cores is probably gonna be very nice for you.
Also, for a rock solid, reliable governor, Intellidemand is pretty good.
I'll give it a try and see. What are your minimums?
Sent From The PACMan Lair using Tapatalk 4 Beta On My Rezound.
which program have you used to set the different govs to different cores?
My minimum is 384 MHz both cores. I use Kernel Tuner to adjust my settings, but some people have reported problems with KT. Other options might be Trickstermod or Android Tuner.
i dont like android tuner, never seems to stick, i use trickstermod but KT ive heard some mixed things i want to try it
I use kernel tuner. Never tried the other two, but I also haven't had any of the issues others are having with ROMs hotboots or the like.
Sent From The PACMan Lair using Tapatalk 4 Beta On My Rezound.
i use kernel tuner/Snuzzo Kernel 3.5.1 at the time of this post/Unofficial Cm 10.1 Rom currently being built by Flyhalf
Heres my current ultimate setup lol, been running it for a few months. its completely stable
CPU0: Min 384 - Max 1350 - Lulzactive
CPU1: Min 384 - Max 1728 - DanceDance
Mp-Decision i changed the idle frequency to 384Mhz, that's the only option i touched in there.
Misc Tweaks:
Capacitive Buttons Blacklight: 30%
Fast Charge: On
Vsync: On (Having the Gpu processing extra FPS can drain battery, Lol on a phone its nothing but possibly can help)
Usb OTG: OFF (doesn't charge\access Sdcard when plugged into PC and i dont have a OTG cable)
Color Depth: 24
IO Scheduler: Sio (i also like Noop, look up which ones you like best) (sio is more performance and noop is balance)
Sdcard Cache: 4096
And in kernel Tuner hit the menu button on ur phone thats on the right of the little home button and select "Swap"and click activate Swap and set the Swappiness to 100 and click set Swappiness
Now on to Undervolting. ive benched over and over to find a super low and stable setting.
192 - 700mV
310 - 712mV
384 - 712mV
432 - 750mV
486 - 750mV
540 - 775mV
594 - 775mV
684 - 800mV
702 - 800mV
756 - 825mV
810 - 862mV
864 - 887mV
918 - 887mV
972 - 912mV
1026 - 912mV
1080 - 937mV
1134 - 937mV
1188 - 962mV
1242 - 987mV
1296 - 1012mV
1350 - 1037mV
1404 - 1062mV
1458 - 1062mV
1512 - 1125mV
1566 - 1137mV
1620 - 1162mV
1674 - 1187mV
1728 - 1212mV
If you decide to use my undervolt table THAN PLEASE MAKE SURE BEFORE you punch in the undervolt that you do a nandroid backup, your phone may act differently than mine. the table is pushing the line lol they can possibly be lowerd in some spots by i highly doubt it, you'll most likely boot loop if you try and lower it
lol and make sure you put in the right values. Writing those down and triple checking them was a little hard
Also i have a screen brightness table to if you want it.
--Delete-- Wrong thread
Searched a lot of posts but cannot find any useful post (-25 mv or -50 mv) for LG G2 so decided to make my own UNDERVOLTING TABLE
Why undervolting is important?
With rising freq needs more voltage and more voltage makes device hot
If tempature stays a little bit lower and not rising fastly device will be use high frequencies with low tempatures(according to old frequency tempature)
It can stays old tempature with high frequency!
It means more smooth user interface and less laggy gaming performance
(not lower tempature on high pressure but lower when regular use)
Under high pressure (gaming or benchmak test) device frozed so I rised voltage a little bit for stability.
v 4 BETA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Applied with dorimanx kernel v4.6
I will be honest with you; it's not efficient undervolting table because of heating (Waiting for next kernel or use v4..2 with v3 undervolting table)
Adjusted for performance profile and as you can see 1.04 GHz is nearly undervolted -5 mV.
You can change % and build your own undervoltage table.
Kernel settings
MASTER CORE
4 x Intellimm
Touch boost: DISABLED
CPU Freq: 2.5 (or optionally 2.4)
Max screen off freq: 1.04 GHz
THERMAL CONTROLS
CPU Temp Control: Intelligent temp control only
Temp Pull Timer: 200 ms
Hotplug Thermal CPU Control: Enabled
Max Online CPU's: ALL CORES ON
INTELLI CORE MAX HEAT: 76
See frequencies real time with Trepn Profiler and CPU tempature
Found a tool to undervoltage instead of 2 applications
Download Kernel Toolkit from google play
Here is how you can set voltages
v 3
Tested for 2 days (Dorimanx kernel v4.2)
v2 not freezing but rebooting so changed undervoltage values about %5 for safety.
Update: Tested a lot of combinations but v3 is the best for now.
Added 2.4 GHz for performance, you can use optionally but I recommanded using 2.4 GHz It makes phone very smooth without heating and draining battery. Use yellow mV table when you apply.
Recommended Kernel Settings
4 x intellimm
Touchboost: Disabled
CPU TEMP CONTROL: Intelligent Temp Control Only
Hotplug thermal control: Enabled
Max Online CPUS : Core 0,1,2 (3 cores)
Hotplug Driver: Intelligent Hot Plug
v 2
Used percentage instead of iteration.
After hours testing table v2 more stable, gives more performance and less laggy
Under high load on cpu with gaming CPU stays 68-71 C and can't see any "big" lag just micro lags (tested with Real Racing 3 and Sky Force)
Cores stays 1.5 GHz on Sky Force and 1.2 GHz on Real Racing 3
Changed Max Online CPUS 2 to 3
Tried also 4 cores but best is 3 for smoth
v 1
Finding the correct value is hard for a first timer here is values:
Tested for 3 days some voltages mekes device laggy or frozen (Tested with Trepn Profiler for frozen Cpu frequencies)
Tested with LG G2 D802 (v1.2) Dorimanx lollipop kernel (v 4.2)
Most setting fits with your phone with these settings
But what happens if you want to make your own UNDERVOLTAGE TABLE ?!
There are two situations:
1. Mostly frozen on while you set the voltage so we know which freq needs more voltage
2. Sudden freze and you don't know which freq causes? Use Trepn Profiler; it shows every time which cpu core on which freq
If your device frozen you can know (or you can suspect) (Makes a little bit laggy. At highest tempature cores will be stay same frequency and you can close trepn and see not lagging results while testing)
Let me know how it works for your device :fingers-crossed:
I've found that -40mv was the best for me. Except on the lower speeds, in which I went just a little bit lower. I put everything -40 across the board and then I'd bring the 300MHz down to 0.7v and the two frequencies higher would be slightly higher than 0.7v. Sometimes I'll even set the 2nd step to the same as the first. The furthest I'd go with lowering values even further is the 4th step.
If you want clarification, I can give it to you. Oh, keep in mind, my CPU was given a bin rating of 4, so I'm a bit better off than average. http://forum.xda-developers.com/showthread.php?t=2489998
tehbigbug said:
I've found that -40mv was the best for me. Except on the lower speeds, in which I went just a little bit lower. I put everything -40 across the board and then I'd bring the 300MHz down to 0.7v and the two frequencies higher would be slightly higher than 0.7v. Sometimes I'll even set the 2nd step to the same as the first. The furthest I'd go with lowering values even further is the 4th step.
If you want clarification, I can give it to you. Oh, keep in mind, my CPU was given a bin rating of 4, so I'm a bit better off than average. http://forum.xda-developers.com/showthread.php?t=2489998
Click to expand...
Click to collapse
I know every device has different processor but I don't know that kinf of classification Thanks
Mine PVS bin 2 and speed rating 2.3 GHz
Step-by-step undervolting good idea I did it firstly then I make an iteration Really obsessed I know.
Most default values makes graph linear so I follow this way and find max and min frequency voltages then found values between these voltage values.
Tested on high pressure and adjust a little bit.
Hi,
thanks for pushing the kernel and phone tuning even further.
My phone is PVS bin 2 too.
I tried a more simple approach. I had "A1 CPU Tool" installed already and checked the most used frequencies. So I started modifying those in the first place (-25mv)
I am curious if it will have any day by day measurable effect.
And last but not least, if the phone will remain stable.
Sent from my LG-D802 using XDA Free mobile app
silent_silver said:
Hi,
thanks for pushing the kernel and phone tuning even further.
My phone is PVS bin 2 too.
I tried a more simple approach. I had "A1 CPU Tool" installed already and checked the most used frequencies. So I started modifying those in the first place (-25mv)
I am curious if it will have any day by day measurable effect.
And last but not least, if the phone will remain stable.
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
Trepn Profiler shows real time while you testing the undervolting settings when device frozen it helps to find which frequency
If A1 CPU Tool usable then use it but I recommanded If you follow my way
Testing testing testing and already had 2 freze [Solved with v2]
If I can lock on a frequency I will test all of them and compare "CPU load"
Thanks for this! So far it's stable for me, and especially the Phone is not that warm now
tryman87 said:
Thanks for this! So far it's stable for me, and especially the Phone is not that warm now
Click to expand...
Click to collapse
When screen off more reduced tempature but while gaming will be heating the same
Check out v3, it would be more stable
lynxrz said:
When screen off more reduced tempature but while gaming will be heating the same
Check out v3, it would be more stable
Click to expand...
Click to collapse
I'm a bit confused with the v3 graph, which one should i follow? There's the yellow, green and brown.
tryman87 said:
I'm a bit confused with the v3 graph, which one should i follow? There's the yellow, green and brown.
Click to expand...
Click to collapse
Follow yellow one, forgot to note down
I'm adding to post now.
Thanks for your attention
nice guide!!
i found out that my CPU can stay stable at -45-40mvs
i did some manual undervolting such as 300mhz at 700mv
on the other hand at 1200-1700mhz range i kept the -45mv undervolt as i had some freezes with -50mvs (still a work in progress)
kernel:dorimanx 4.2 ,default profile ,no touchboost ,ondemand guvernor
CPU bin: 3
testing done with:vellamo / day to day usage + trepn profiler
No need for lame programs with Dorimanx kernel. Here is 4.4.2 example:
Code:
[B]# get vdd table:[/B]
cat /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[B]# we can decrease all values...[/B]
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[B] # ... or just one value we need:[/B]
echo "2419200 975000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
And 5.0.2 example:
Code:
[B]# get vdd table:[/B]
cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
[B]# we can recalibrate all settings here from min to max frequencies...[/B]
echo "750 760 770 780 790 800 810 820 840 860 880 900 920 950 1000 1020 1060 1090 1120" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
After some testing you just add modded values to init.d script. Profit!
GK_222 said:
No need for lame programs with Dorimanx kernel. Here is example:
Code:
[B]# get vdd table:[/B]
cat /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[B]# we can decrease all values...[/B]
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[B] # ... or just one value we need:[/B]
echo "2419200 975000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
After some testing you just add modded values to init.d script. Profit!
Click to expand...
Click to collapse
If I can build a init.d script I'll add this (probably in next version) thanks for info :good:
bogdy5 said:
nice guide!!
i found out that my CPU can stay stable at -45-40mvs
i did some manual undervolting such as 300mhz at 700mv
on the other hand at 1200-1700mhz range i kept the -45mv undervolt as i had some freezes with -50mvs (still a work in progress)
kernel:dorimanx 4.2 ,default profile ,no touchboost ,ondemand guvernor
CPU bin: 3
testing done with:vellamo / day to day usage + trepn profiler
Click to expand...
Click to collapse
Thanks
Try to change % in v4 Freq table
Usage of cpu depends on your governor and carefully watch cores frequencies, yes ALL of them in the same time
Mostly high frequencies not used because of heating and these frequencies has more flexible undervoltages BUT sometimes high frequencies cause freze at cold stuations (mostly seen while waking up the device) so using % helps a lot.