Hi Guys!
Just made this thread to let people share their favorite governor and overclock settings for our beloved Xperia S in a way we can have both performance and good battery life.
Feel free to share!
Right now I'm using the Interactive governor and don't have my XPS overclocked.
Got the CPU set to Min: 192 and Max: 540 when screen off.
I can easily get 30 hours with one full charge.
Sent with my Sony Xperia S using a little bit of KA magic.
I use Conservative Governor with tweaks inspired in the Lionheart governor
Kernel SSpeed 5.1 Stock Frequency
Min Clock: 192
Max Clock: 1566
Governor: Conservative
Scheduler: Noop
[setCPU Governor Settings]
Sampling Rate: 200000
Sampling Down Factor: 1
Up Threshold: 55
Down Threshold: 15
Ignore Nice Load: 0
Freq Step: 5
The governor becomes a really agressive one, ramping fast, and downing only when CPU isn't needed anymore. Frequency seek is the most frequent possible for Conservative (every 0.2 seconds). This tweaks turn the Phone in a more agressive OnDemand with tendencies to stay in the lowest clock possible, thanks to Conservative nature.
In addiction with CPU Sleep (Google Play App) i can have a hotplug feature when the screen is off. (It only works nice with stock based kernels).
I'm Testing Freq Step 10 at the moment.
How long does your battery last with these exact settings?
Sent with my Sony Xperia S using a little bit of KA magic.
ROM=cm9 fxp 133
Kernel=Pure ICS
Clock speeds
max=1.4Ghz
min=0.2Ghz
Govenor=Hotplug
JoelChrist_ said:
How long does your battery last with these exact settings?
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
Never meassured it. But i will do, but i think it will not last a lot, since im a heavy user
darksherko said:
ROM=cm9 fxp 133
Kernel=Pure ICS
Clock speeds
max=1.4Ghz
min=0.2Ghz
Govenor=Hotplug
Click to expand...
Click to collapse
Do you have a long battery life on the hotplug governor?
Sent with my Sony Xperia S using a little bit of KA magic.
JoelChrist_ said:
Right now I'm using the Interactive governor and don't have my XPS overclocked.
Got the CPU set to Min: 192 and Max: 540 when screen off.
I can easily get 30 hours with one full charge.
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
Cool, how do I do that?
JoelChrist_ said:
Right now I'm using the Interactive governor and don't have my XPS overclocked.
Got the CPU set to Min: 192 and Max: 540 when screen off.
I can easily get 30 hours with one full charge.
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
how are people getting such great battery life? must have everything turned off all the time and never use the phone?
mine is on stock kernel rooted and using setcpu to keep cpu down some.
it using on demmand/deadline max 1026max 192min, except when srceen is off or battery below 25%, when it goes down to 486max 192min.
does using a custom kernel really make that much difference.
if i turn everything oaff (data/sync etc) o still only get a max of around 18-20 hours, even if it's sat idle. if i leave data on sync on but sat idle it will last upto 16 hours, and if i actually use the phone it will last anything from 8 to 12 hours.
battery life is really a major issue i'm finding, even with cpu values lowered, and with unused system apps, like battery saver etc frozen with titanium backup.
i don't want to remove apps that i actually use, like the timescape syncing, weather widgets, etc.....because at the end of the day, there is no point in having a phone with "smart" features, then disabling them to get 3 days "use" out of it....but honestly, having to charge it evry single night, and if i use the phone at all during the day, having to charge it mid-way is far from ideal....
brunodmjr said:
I use Conservative Governor with tweaks inspired in the Lionheart governor
Kernel SSpeed 5.1 Stock Frequency
Min Clock: 192
Max Clock: 1566
Governor: Conservative
Scheduler: Noop
[setCPU Governor Settings]
Sampling Rate: 200000
Sampling Down Factor: 1
Up Threshold: 55
Down Threshold: 15
Ignore Nice Load: 0
Freq Step: 5
The governor becomes a really agressive one, ramping fast, and downing only when CPU isn't needed anymore. Frequency seek is the most frequent possible for Conservative (every 0.2 seconds). This tweaks turn the Phone in a more agressive OnDemand with tendencies to stay in the lowest clock possible, thanks to Conservative nature.
In addiction with CPU Sleep (Google Play App) i can have a hotplug feature when the screen is off. (It only works nice with stock based kernels).
I'm Testing Freq Step 10 at the moment.
Click to expand...
Click to collapse
This setup is turned to performance or battery (while actually using the phone).?
Sent from my LT26i with Tapatalk 2
I use the conservative governor with a min frequency of 384mhz and depending on what I'm using the phone for, either 1.24ghz or upto 1.67ghz. Have noticed an obvious increase in battery life, probably around 20%. Using stock ICS with KA SSpeed kernel 5.1.
Sent from my LT26i using xda app-developers app
brunodmjr said:
I use Conservative Governor with tweaks inspired in the Lionheart governor
Kernel SSpeed 5.1 Stock Frequency
Min Clock: 192
Max Clock: 1566
Governor: Conservative
Scheduler: Noop
[setCPU Governor Settings]
Sampling Rate: 200000
Sampling Down Factor: 1
Up Threshold: 55
Down Threshold: 15
Ignore Nice Load: 0
Freq Step: 5
The governor becomes a really agressive one, ramping fast, and downing only when CPU isn't needed anymore. Frequency seek is the most frequent possible for Conservative (every 0.2 seconds). This tweaks turn the Phone in a more agressive OnDemand with tendencies to stay in the lowest clock possible, thanks to Conservative nature.
In addiction with CPU Sleep (Google Play App) i can have a hotplug feature when the screen is off. (It only works nice with stock based kernels).
I'm Testing Freq Step 10 at the moment.
Click to expand...
Click to collapse
I don't know what you did bro, but with this setup (except for the governor, which I'm using pegasusq) made my phone fly. The lights animation on the AnTuTu Benchmark (I just do a synthetic to see what I get) had a peak of 75 fps, and then stabilized in 65 fps.
{
"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"
}
Kernel : Advanced Stock Kernel
Min Clock: 384
Max Clock: 1026
Governor: Ondemand
Scheduler: Noop
Screen Off
Min Clock : 192
Max Clock : 384
Governer : Powersave
Getting up to 46 hours with this setup + CPU Sleeper
Related
Can u guys share ur set CPU profile. I need profiles with great performance and less battery consumption. My profile is as followed :-
Charging AC/full 748 Max 480 min
Screen off 245 max 122 min
Performance n battery don't come together ..... I use ondemand 729/425 ... nothing different for screen off .... works really smooth n decent battery also
Sent from my LG-P500 using XDA App
But I Also need to manage my batteries...
My setup's kinda similar to yours,
480/720 ~ on demand ~ when charging/full
Otherwise 240/320 when screen is off. BTW How long does yours last?
Hey !
That's for me :
Charging/full : 729 - 245 / ondemand
Screen off : 320 - 245 / conservative
Battery < 40 : 600 - 245 / ondemand
Battery < 20 : 480 - 245 / conservative
I don't have many profiles, just 1.
245min / 748max
Battery's life is kinda good, usually I have to recharge one time a day. It's not a problem for me.
Toshir0 said:
Hey !
That's for me :
Charging/full : 729 - 245 / ondemand
Screen off : 320 - 245 / conservative
Battery < 40 : 600 - 245 / ondemand
Battery < 20 : 480 - 245 / conservative
Click to expand...
Click to collapse
I even used battery less than profile but it slows the phone too much....
Well It also depends on which ROM you have on your phone.
Mik_os CM7 port actually EATS the battery and It runs out of juice in less than 24 hours with a normal usage. A bit better with devoid v5, but I feel like openOptimus is the best one out of the three.
I use only one profile: battery < 101% @ 729/122 smartass
great advice so i must be changing my rom as soon as andy releases his new build!
729 max 480 min smartass
I use:
Main 729 max 320 min smartass
Charging 600 max 245 min ondemand
Battery < 40% 600 max 245 min conservative
Battery < 25% 480 max 122 min conservative
I used to keep a screen lock profile at 245 max but my phone lagged while receiving calls when the screen was locked and sometimes while playing music.
I use devoid.franco and
729/480 interactive
Screen off: 600/240 ondemand
What is that of smartass? My SetCpu havent got that mode :/
have someone got a guide or something that explain each mode (ondemand, interactive...)
Using stock ROM.
Normal: 729 max, 245 min, conservative
Charging: 768 max, 245 min, ondemand
Battery < 20%: 600 max, 122 min, conservatve
Battery life greatly depends on my usage. But, generally, I come home after classes (where I use it for internet, music, games etc.) with 30-40% battery left.
Javi V12 said:
I use devoid.franco and
729/480 interactive
Screen off: 600/240 ondemand
What is that of smartass? My SetCpu havent got that mode :/
have someone got a guide or something that explain each mode (ondemand, interactive...)
Click to expand...
Click to collapse
i wish if some one had a guide on it but optimus users like u and me are recommended to use ondemand (no i am not a noob).
Devil_Dude said:
i wish if some one had a guide on it but optimus users like u and me are recommended to use ondemand (no i am not a noob).
Click to expand...
Click to collapse
Look at this
http://forum.xda-developers.com/showpost.php?p=9272248&postcount=1
i got dis man
Program for controlling CPU frequency on Android in order to increase productivity or increase battery life.
Of the features worth noting customizable profiles.
Description of modes:
* Interactive - an interactive mode, driving frequency of the CPU in real time, almost always at full productivity.
* Smartass - a regime based on Interactive. Has a more rapid decline in frequency in a simple, but also lowers the frequency to a minimum at a turned off screen.
* Conservative - operates at a very low incidence of possible CPU and increases incrementally, as needed.
* Userspace - allows you to change the frequency of the CPU, either manually or dynamically, at the discretion of the software.
* Powersave - reduces the frequency of the CPU to the lowest possible level.
* Ondemand - operates at a very low incidence of possible CPU and increases the maximum reaches values of CPU usage - 100%.
* Performance - sets the maximum frequency of the CPU, not allowed to change frequency downward.
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
Disclaimer; This does not damage your phone at all or fry/mess up your cpu. On the contrary, it helps it by not running at full capacity all the time resulting in less stress and increased battery.
This method works universally for any Android phone you're using. But you'll need ROOT for Set CPU.
IMPORTANT: The newer versions of SetCPU might prevent your phone from entering deep sleep. Download version 2.24 from the following link which is the one with no problems and completely works 100%.
http://forum.xda-developers.com/showthread.php?t=505419
The Ace sucks in battery life. We all know that. And on 3G? Don't even mention it. But here's a fix, ever tried Under clocking instead of Over clocking?
Someone brought it up on a thread a couple of days ago and I have to spread the word, that works wonders. Got my Ace running on 245 min and 806 max and a different Screen Off profile. And now from the morning till 6PM in the afternoon, its just 61% AND recorded a 7 minute video/took pictures.
Battery was the only issue I had with my Ace. But now that its fixed, I love it
When screen is on:
MAX 806
MIN 245
Ondemand governor (This governor bumps up to max when needed but spends most time on the min freq. Best battery saver.)
When screen is off:
MAX 320
MIN 122
This way, you have a beast quick phone when you're using it, and the best battery saver when you're not!
This is what CPU spy should look like when you're done:
{
"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"
}
NOTE: Turn off Autosync from the settings. It's only used to sync your gmail and contacts and such. You can manually sync when you add a new contact and since I don't use gmail, I refresh manually whenever I do. 3G is the worst battery killer so this will help a lot.
SetCPU: http://forum.xda-developers.com/showthread.php?t=505419
Specific instructions for those that can't get it to work!:
On SetCPU:
Click Add profile
Where it says Profile, select it and tap "Screen Off"
Set the frequencies you want in use while screen is off (If you want just one frecuency, put both sliders on the same number)
Set priority (in case you have other profiles, otherwise don't bother)
Select governor (Won't really matter since cpu is gonna be running at 1 frecuency)
Tap save
Go back to Profiles tab at the top, then tap Enable at the top left to make the profiles work.
For a list of most governors detailed; check out this thread! http://forum.xda-developers.com/showthread.php?t=1242323
To check if its all working, install CPU spy from the market:
https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5idmFsb3Nlay5jcHVzcHkiXQ..
Battery Calibration
1. Turn your phone off
2. Leave charging over night
3. Turn it on
4. Leave it charging for half an hour
5. Download this app https://play.google.com/store/apps/details?id=com.nema.batterycalibration&feature=search_result
6. Open it and press calibrate battery
7. Discharge your phone down to 0% during the day
8. Charge back up to 100% NON-STOP.
This is to make sure you're using your battery at 100%. Only do this after you flash a new rom.
The worst battery killer is 3G itself. No matter how much you try to optimize battery and underclock, if you have 3G on, you're gonna have a bad time. MAKE SURE Autosync is disabled.
Thanks to QNBT for the AutoSync off and new profile settings hint!
gotta try this one. hope this works!
Hey dude I may try that tip, but I wanted to know about the governor that you are using, is that one a battery saver?, and what about chainfire 3d? you said that you dont use heavy apps and as far as I know that one is for heavy gaming isnt it?
ps. I recommend you install Vturbo 8.5 by gadgetcheck since I didnt see it on your signature, it really works
tyraelasd said:
Hey dude I may try that tip, but I wanted to know about the governor that you are using, is that one a battery saver?, and what about chainfire 3d? you said that you dont use heavy apps and as far as I know that one is for heavy gaming isnt it?
ps. I recommend you install Vturbo 8.5 by gadgetcheck since I didnt see it on your signature, it really works
Click to expand...
Click to collapse
Yeah, I'm not using heavy apps now but I do like some gaming now and then. When I do game, I crank up the processor back to normal but I rarely do. And I use Smartass governor, not really sure if its a battery saver but its working great.
And yeah, I think I had turbo 8.5. But for now, my ace runs perfectly fine so I don't really need other scripts or optimizers
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.” The availability
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Thanks for the tip, works for me
Im trying smartass governor but I noticed that the battery got really hot for some unknown reason :/, and I I got back to ondemand it becomes normal. Any idea?
I would rather use SetCPu becouse a need automatic changes since I play a lot ;P
I have no idea. My phone's working fine. I keep switching between interactive and smartass. Can't really tell which one works better xD
Sent from my GT-S5830 using XDA App
Ooohhh I see. Thanks for the governor definitions. Keeping Smartass then
Sent from my GT-S5830 using XDA App
i had battery issues (only lasts for a day), after applying this, another day was introduced for my SGA. LOL clicked the thanks button! cheers!
tomy2590 said:
i had battery issues (only lasts for a day), after applying this, another day was introduced for my SGA. LOL clicked the thanks button! cheers!
Click to expand...
Click to collapse
Haha good to know it doesn't only work for me. I clocked it down lower to 320 since I'm barely using it now. Love my ace
SuperAce609 said:
Haha good to know it doesn't only work for me. I clocked it down lower to 320 since I'm barely using it now. Love my ace
Click to expand...
Click to collapse
Hahaa... I know why...
Because you using What ROM? What Tweaks/script? like me too.. Hehehe..
Thank for sharing that setting... I'm really love my SGA now..
arip30 said:
Hahaa... I know why...
Because you using What ROM? What Tweaks/script? like me too.. Hehehe..
Thank for sharing that setting... I'm really love my SGA now..
Click to expand...
Click to collapse
This rom actually has a pretty bad battery life. But makes up for it with speed and stability. I'm only using the LagFree V2 script and thinking about adding TurboBoost but I'm not sure if they can work together.
SuperAce609 said:
This rom actually has a pretty bad battery life. But makes up for it with speed and stability. I'm only using the LagFree V2 script and thinking about adding TurboBoost but I'm not sure if they can work together.
Click to expand...
Click to collapse
I already using both.. I'thing its can work together.. But i'm not to sure cause am only using lest then 1 week..
For me, i want to using a smoth n fast.. i don't care about the battery live cause i can charge or use my secondary/spare battery..
________________________________
Please push thank button for me.. TQ..
arip30 said:
I already using both.. I'thing its can work together.. But i'm not to sure cause am only using lest then 1 week..
For me, i want to using a smoth n fast.. i don't care about the battery live cause i can charge or use my secondary/spare battery..
________________________________
Please push thank button for me.. TQ..
Click to expand...
Click to collapse
Well, just in case you miss your spare battery at home or something, check out the edit I just made on the thread.
Will make your spare battery look like wasted money xD
Using CPUtuner now. Free and works perfectly. I dont think i need smartass governor, since it offers separate screenoff profile, where i can set everything i want, including services on/off.
knall said:
Using CPUtuner now. Free and works perfectly. I dont think i need smartass governor, since it offers separate screenoff profile, where i can set everything i want, including services on/off.
Click to expand...
Click to collapse
Lol, okay. SetCPU is also free (on XDA). But whatever works for you is fine. My fix is just running CPU at minimum as soon as the screen is off and switch profiles when the screen is on. That way you'll always have battery to use when you want to and not use up battery when you're not using the phone.
rjyama said:
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.” The availability
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Thanks for the tip, works for me
Click to expand...
Click to collapse
Thanks for the explanation, man...it was very useful
My setting
Profile: screen off
Min 122
Max 122
Governor: powersave
Profile: battery
101%
Min 122
Max 806
Governor: conservative
pyronia said:
My setting
Profile: screen off
Min 122
Max 122
Governor: powersave
Profile: battery
101%
Min 122
Max 806
Governor: conservative
Click to expand...
Click to collapse
I REALLY don't recommend leaving it at 122 minimum. I tried it today and had a lot of lag attacks. Though the battery saving is incredible, but at the cost of a lot of performance. Like taking a call, it'll lag like hell. Had a lot of missed calls today just because of that issue.
But if it works for you, then have fun!
SuperAce609 said:
I REALLY don't recommend leaving it at 122 minimum. I tried it today and had a lot of lag attacks. Though the battery saving is incredible, but at the cost of a lot of performance. Like taking a call, it'll lag like hell. Had a lot of missed calls today just because of that issue.
But if it works for you, then have fun!
Click to expand...
Click to collapse
Yeah, I noticed that a few weeks back, couldn't even answer so much it was laggy. You can set in phone call 245mhz and priority higher than screen off and it resolves that issue.
I use cyanogenmod performance for setting the clock with 245mhz min now, I don't have any wakelocks so the processor is always off (deep sleep) when the screen is off, at the same time I don't have the wake lag issue since its not running at 122mhz when it wakes.
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.
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.