Database Develop

SetCPU

What are good settings for the CPU when the screen is off and others?
Sent from my HTC Liberty using XDA App

I use Screen On at 806mHz and Screen Off at the lowest setting, conservative profile. It works well.

Both minimum and maximum are set to 245 for screen off? I want both performance and battery. I have my regular CPU set to 787 and 245.

Did you just answer your own question?
I think battery and performance dont really go hand in hand. I have screen off 245.
Give a little, take a little.

I wouldn't recommend using set CPU, there is still conspiracy whether it drains the life of your phones processor or not. I am leaning towards the validity of this research. Of course this is your choice, but be warned.
Sent from my Liberty using XDA App

theROMinator said:
I wouldn't recommend using set CPU, there is still conspiracy whether it drains the life of your phones processor or not. I am leaning towards the validity of this research. Of course this is your choice, but be warned.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Huh? This is so easily testable. Leave your phone idle overnight without SetCPU, then with SetCPU set to underclock at 245, compare battery level in the morning. It is a basic law of physics that the power consumption of any switch is P=CV^2f, where C is the capacitance, V is the operating voltage and f is the operating frequency. Any CPU is a large collection of switches, lowering the operating frequency will always reduce power consumption unless the overhead of dynamic adjustment consumes more power.
Along the same logic if you overclock the CPU you WILL get more battery drain, guaranteed. As someone said earlier, power and performance are inversely related for any fixed configuration.

GroovyGeek said:
Huh? This is so easily testable. Leave your phone idle overnight without SetCPU, then with SetCPU set to underclock at 245, compare battery level in the morning. It is a basic law of physics that the power consumption of any switch is P=CV^2f, where C is the capacitance, V is the operating voltage and f is the operating frequency. Any CPU is a large collection of switches, lowering the operating frequency will always reduce power consumption unless the overhead of dynamic adjustment consumes more power.
Along the same logic if you overclock the CPU you WILL get more battery drain, guaranteed. As someone said earlier, power and performance are inversely related for any fixed configuration.
Click to expand...
Click to collapse
Well your name is definitely very fitting.

GroovyGeek said:
Huh? This is so easily testable. Leave your phone idle overnight without SetCPU, then with SetCPU set to underclock at 245, compare battery level in the morning. It is a basic law of physics that the power consumption of any switch is P=CV^2f, where C is the capacitance, V is the operating voltage and f is the operating frequency. Any CPU is a large collection of switches, lowering the operating frequency will always reduce power consumption unless the overhead of dynamic adjustment consumes more power.
Along the same logic if you overclock the CPU you WILL get more battery drain, guaranteed. As someone said earlier, power and performance are inversely related for any fixed configuration.
Click to expand...
Click to collapse
He said drain the life of the phones processor, not battery. I think he's saying shortening the life of the processor...I may be wrong.

did you guys also know they faked the moonlanding?
srsly though...set cpu is good stuff. if you think it drains the processors life, why not ask?

When you are not using your phone srt it to powersave 255 MHz and when you will use it. Set It to on demand 806 MHz
Sent from my Liberty using XDA App

[Q] OC/UV settings for battery life

hi guys,
does anyone have a tried and working UV values for best battery life? I don't want any more performance, so I'm not looking for OC, but perhaps any idea what UV stays stable?

Well, it's easy the higher you OC, the more it will drain your battery. As for UV, I can't tell because the voltages are different for every device, Rom and kernel...
Sent from my LG-Stone from the Prehistory...
Nahh... Just kidding!
CM 7.2 Koboltzz KANG
IronKernel 32MB

Usually undervolting -50mv for each speed will work for most devices, although its not recommended to decrease that much for speeds below 800mhz since it will affect your phone's wake up speed.
And tegra 2 cpu controller only supports minimum of 770mv, going anyway lower than this value will not have any effect.
My advice, try UV -25mv for 500mhz, and the rest above is -50mv. Some o2x can go -100mv, but you need to be lucky to own such device.
Cheers!

Mine is working perfectly on -75.
But when i go to -100, soemtime freezes device, so i use -75 regularly.

trying -50 across the board now, seems to run stable.
brw, how does lower voltage hurt the speed?

I can't really explain clearly since I do not know the technicals, but from what I read in xda, it will affect your speed, meaning 1.2ghz running at undervolted setting will not run the same as at stock voltage. Maybe its an efficiency issue, I do not know.
I thing that i experience, If you undervolt too much the few lowest clock steppings, you sometimes might not able to wake the phone from sleep because there is not enough power to wake it up.
I hope my explanation help you a little, and hopefully someone with more experience can give you a better explanation.

using -25mv ate 1.1ghz and 1ghz, -50mv at 800 Mhz, and -100mhz (750Mhz so its 770mhz because hardware limitations) on all other frequencies!

-50 mv is the limit for the device don't use below -50mv. but it dependes on your device. mine cannot UV it always gives me SOD i think my hardware phone is crap

antec123 said:
-50 mv is the limit for the device don't use below -50mv. but it dependes on your device. mine cannot UV it always gives me SOD i think my hardware phone is crap
Click to expand...
Click to collapse
When did you buy your phone?
I have one of the 10 first phones sold in Sweden and I cannot undervolt mine at all.
Just wondering if there's any correlation between manufacturing time and UVability (yeah I just made that word up).
// Stefan

I run with 1100.. good compromise between speed and battery life i think

So does oc kill the phones life?

Simple question.
My freq now is 633 mhz..still will it shorten the life of my cpu???
Or higher freq and I mean not just for gaming,for everyday use.
Its mainly cuz of 360 launcher.
You need some higher freq to get the smooth look.
So???

Well, I've been using Overclock since the Day overclock came out..
And i have no damn problems .. CPU is still working Great!
And just to let ye know its clocked on 768 MHz ;D
Just overclock it Dude..
Your x8 will be Okay
But if u kept using it for long periods..
it might endanger Your CPU
Also be careful not to fall into a bootloop .. uncheck the Set on Boot option ..
check if it's working alright on 768 .. then check the Set on boot..
I have GDXv22 with [email protected] . .

Medo2 said:
Simple question.
My freq now is 633 mhz..still will it shorten the life of my cpu???
Or higher freq and I mean not just for gaming,for everyday use.
Its mainly cuz of 360 launcher.
You need some higher freq to get the smooth look.
So???
Click to expand...
Click to collapse
Overclocking by 33MHz isn't dangerous, that's very mild.
In General - the more you overclock from the specified values (in case of the X8: 600MHz) the more heat you produce and the more you push the chip to the bleeding edge.
In short: Every integrated circuit has some headroom for overclock as the manufacturer specifies the clock rate at an safe value and not at the very bleeding edge where variances in the chip making process could lead to too high yields because they don't run stable with the clock frequency. In general you don't do your electronics a favor when pushing it too far. 700MHz+ will surely shorten the life span of your phone, how much would need to be seen as there's no real long-term experience.

Wow thanks guys.
You see after some thinkig it aint the cpu freq that is slow.
I set my low freq when in sleep on 245 so the phone is slow on waking up.
When you set it on high the phone will respond better!

like PC, when overclock it may reduce processor life

any clock reduces the life of your cpu. the higher the clock rate less life cpu

Overclocking the Nexus 4 - Benchmark of application load time = BIG difference

A lot of people say that overclocking the Nexus 4 is useless as it's so fast to begin with, but that turns out to be false, yes, it's useless for making e.g. games run smoother, as they all already do, but it's very useful for reducing loading times, and it turns out that the % of time saved is close to the % of increased clock speed.
My setup: Nexus 4, franco.Kernel updater v9.3.3, Franco Kernel #666, Jelly Bean 4.2.2 JDQ39, Governor Interactive. Angry pigs HD 1.1.0 app loading. Fresh reboot for each speed. I did three measurements for each clock speed and left voltages at Franco's defaults. I would suggest looking into the undervolting threads to figure out how low you can go with voltages, undervolting is good underclocking is usually not.
1026 Mhz 1025mV default Franco
15.4s
15.9s
15.7s
1512 MHz 1150 mV default Franco
11.5s
11.3s
11.3s
1620 MHz 1175mV default Franco
11.1s
10.6s
10.6s
1674 MHz 1175mV default Franco
10.3s
10.6s
10.7s
1728 MHz 1200mV default Franco
10.5s
10.3s
10.3s
Conclusion
12.5% faster clock speed = 8.85% faster load time, which means increasing clock speed is 70% effective at reducing load time going from 1512 Mhz and upwards.
40% faster clock speed = 35% faster load time, meaning that people who think running their device at 1026 Mhz is as good as 1512 Mhz are wrong. Nearly doubling clock speed nearly halfens load time.
The reduction in loading time is reduced a bit as you reach higher frequencies, but it's still 70% effective so every extra Mhz helps cut down the wait. Overclocking the Nexus 4 is meaningless in terms of increasing smoothness IN APP, but meaningful in reducing load times significantly and in increasing the responsiveness of your system.

please tell me for saving the battery and still maintaining a little smoothness
the settings to use
i use faux123 kernel.. i just need the voltage,cpu clock n governer settings

so overclocking makes things faster.. really? who would have thunk. and you just found this out?

my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.

zakoo2 said:
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
Click to expand...
Click to collapse
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100

alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.

So, a 50% increase in clock cycles pushes the performance by a bit.
Who would've thought...?

well that's normal, overclocking = more power draining, more speed; just like with CPU or ram on pc, no rocket science here.

alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
OC? Don't you mean Downclocking or Undervolting?

sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **

gohan040 said:
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
Click to expand...
Click to collapse
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?

sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
It REALLY depends. I'd say most day-to-day usage, an overclock can actually help save battery by 'racing' to sleep (hurry up, finish, drop to deep sleep on cpu AND radio). I think being on 3g makes it even more pronounced because you're letting the radio drop back down to a lower power state as well as the CPU. So if you need to quickly open an email attachment, and cpu is the limiter, it can help it finish, get off the network, and back to idle state faster and save some battery. Now if you go on running benchmarks instead where you just keep throwing more work at it that's a seriously different story. There is also a point of diminishing returns (usually 1 or 2 steps before the absolute limit, in our case about 1670mhz) but in general, a moderate overclock can help.

sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
I agree with u, but remember its a theory.. U finish faster so the time it uses more power is less....
^^Look at the post above me, he got a good example^^
The best of both worlds (if your phone is capable to do this) is when u UV and OC. U would use less power on a higher frequency. Win-win in theory.
But I know what u mean and its hard to believe, but I think that's what @alan1901 wanted to say.
a pigeon delivered this message.... ** your welcome **

If you are lucky, you can overclock using STOCK voltage for the maximum clock.
IE, i see many undervolting their phones by alot. I would just try 1150mV (default voltage for 1.5ghz) for your highest speed (OC as high as you can with this voltage), which means you are not using more power, but still making your phone faster.
Haven't tried on mine, but say 1.6-1.7ghz should be possible with 1150mV for a few at least.

No, 50% OC is not = 50% reduced load time
Let me summarize:
OVERCLOCKING > UNDERCLOCKING FOR THE AVERAGE (POWER) USER
You load a lot of apps, you don't play games or watch videos for hours, productivity is your focus. Depending on use you could save probably 1 - 6 hours a year (see assumptions below). Battery gains won't be significant, but spending less time with the LCD/Wifi etc on could give you some gains as the CPU is one of the lower power drain components.
UNDERCLOCKING > OVERCLOCKING FOR THE 3D GAMER
You spent a lot of time playing CPU intensive games, keeping the CPU cores at max clock speed for extended periods of time. In that case you could get some battery life gains at the cost of responsiveness and app loading times - your call.
IN MORE DETAIL
-------------------------------------------------------------------------------------
UNDERCLOCKING + UNDERVOLTING PROs/CONs
+ Reduces CPU temperature, if that matters to you.
+ IF keeping the CPU at max clock speed for extended periods of time, a lower max voltage could give you enough extra battery life to negate the time lost waiting for apps to load - your call.
- Increased load times - even on the Nexus 4 a lot of apps take > 10 seconds to launch, and don't forget in-app load times, reboots etc.
- No significant battery saving in most cases, potential for loss (if doing a lot of app loading you could even get worse battery life as the screen, wifi etc has to stay on for longer, and the screen is the main battery drain).
- Time spent finding stable voltages.
OVERCLOCKING PROs and CONs
+ Potential small battery life gain, as your device spends less time with the screen/wifi etc ON.
++ SAVES YOU TIME. I'm estimating 1 - 5 hours a year depending on usage.
- Times spent finding stable voltages and clock speeds.
-/- Apps does not RUN smoother.
Why 50% CPU does not = 50% reduced load time and why you test things
---------------------------------------------------------------------------------------------------------------------
It'd be more like 40-30% depending on relative clock speed. I did a simple test as we did NOT know that app loading was mainly CPU limited, could have been memory. And If load times didn't go down there wouldn't be ANY reason to OC and underclocking would be a good idea.
Assumptions behind an estimated 1 - 6 hours saved a year by overclocking
---------------------------------------------------------------------------------------------------------------------
Say that you're on average waiting 4 minutes a day waiting for apps to load, rebooting your phone, waiting for web pages to load, waiting for in-app content to load etc.
Overclocking can cut down that wait time up to 10%, that's nearly 1/2 a minute saved every day, 3 1/2 minutes a week, 3 hours a year. This means you can get a good return on the time it took you to overclock your device, assuming you'll keep it for a couple of years. So if that's the case, why not do it? You'll save some time and you'll enjoy using your device a bit more.
Currently I'm OCd at max 1674 Mhz @ 1225mV, otherwise using default Franco voltages and interactive governor. Stable and very snappy Might be able to reduce voltage and retain stability but this is fine.

zakoo2 said:
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
Click to expand...
Click to collapse
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
I said little OC. Example. Stock cpu clock is 1000mhz and 1000mv. Now, you OC your phone to 1200,1300mhz without changing voltage, or by increasing it a little bit(+25, +50mv, to make phone stable), it will use higher cpu frequency with the same voltage like on lower frequency or with a little higher voltage. So it would finish tasks faster, going to idle faster without getting any heat and give you more battery. On my nexus s and galaxy s3, galaxy s2, i tested it, and it helped (about 30min more screen on time for me). But if you play games a lot and doing some heavy tasks then underclock and undervolt are best for you. But on that beast of phone, i woldnt underclock it beyond 1.2, 1.3, not sure what frequencies are there. If you UC that phone a lot, you can easyly go with some weaker phone.
Sent from SpeedMachine i9100

is there any kernel that can overclock with 4.3?

Andre_Vitto said:
is there any kernel that can overclock with 4.3?
Click to expand...
Click to collapse
yes, most of them. some even overclock up to 2052mhz :victory:

simms22 said:
yes, most of them. some even overclock up to 2052mhz :victory:
Click to expand...
Click to collapse
like?

Check the Development sections.
This thread makes my head hurt.

What's your undervolt?

I've been playing with the undervolt limit of this phone and it seems to have a large amount of play. Obviously every processor is unique so some of your S6's have a lower tolerance for undervolting. I'm using Hacker v11 with Synapse and I can get my A53 cluster @ 1.5 GHz down to 1000mV though I feel it can go lower. I have the A53 underclocked to 1.2 GHz @ 900mV for now and the A57 running 2 processors @ 1.4GHz and sitting at 825mV (just flashed v11 so Synapse reset the values and I've yet to UV the A57 much). Aside from benchmarking with various apps I notice no lag or slow downs running at the lower clocks and using only 6 cores.
My GPU is OC'd to 852MHz but I haven't UV'd it yet. Before v11 I had it at 856.25mV and still stable. HPM and various busses are going to be UV'd again and they seem to take it very well. I'll update this, hopefully later this evening, with more UV values.
I'd like to put our data together and figure out an average UV this phone can take and also see some more extreme values as well. It should be a good starting reference for anyone wanting to get longer life out of their battery along with the phone itself. While we're at it I'd lie to get some lower limits for the clocks and number of cores while still maintaining a smooth experience.
A53 (Hacker v11, starting w/ highest freq.)
1056
1012
962
918
875
843
806
781
750
725
693
675
650
631
625
A57 (Same as above)
1081
1065
1043
1012
981
943
912
875
943
818
800
775
750
731
718
693
675
662
650
643
637
631
GPU
887
831
787
743
718
675
668
Memory Bus(Lowest to highest)
575
575
581
593
593
600
650
675
725
743
768
800
831
Internal Bus(Lowest to highest)
637
637
643
675
712
737
737
743
743
750
793
800
Image Signal Processor(Lowest to highest)
650
650
700
737
806
These are what I'm using right now. I plan to take them down even more in the near future (I already have on some). Of course dropping the power doesn't count for much if the CPU is running too many cycles to finish a task so I'll be messing with the amount of cores and frequency as well.

I recently was running 7 clicks (which on Hackerkernel in Synapse I think is 6.25mv per click) on the Big cores and 6 clicks on the little ones. I also tapped each step in the gpu and busses down 3 clicks and undervolted the GPU too, at about -3 clicks as well. Seemed pretty stable.

benjmiester said:
I recently was running 7 clicks (which on Hackerkernel in Synapse I think is 6.25mv per click) on the Big cores and 6 clicks on the little ones. I also tapped each step in the gpu and busses down 3 clicks and undervolted the GPU too, at about -3 clicks as well. Seemed pretty stable.
Click to expand...
Click to collapse
The only thing I'm not sure about is the "Apollo HPM voltage margin" and it's exact function. I assume it's the max amount hardware performance monitor will allow the CPU/busses to be undervolted when it feels the demand on the CPU vs. it's clock is below a threshold. I'm sure I'm totally wrong though lol. So I'm going with 1 tick above the 25000 default (31250).
Have you ran a stress test with your setup or just put it through the daily motions to check for stability?

KCRic said:
The only thing I'm not sure about is the "Apollo HPM voltage margin" and it's exact function. I assume it's the max amount hardware performance monitor will allow the CPU/busses to be undervolted when it feels the demand on the CPU vs. it's clock is below a threshold. I'm sure I'm totally wrong though lol. So I'm going with 1 tick above the 25000 default (31250).
Have you ran a stress test with your setup or just put it through the daily motions to check for stability?
Click to expand...
Click to collapse
I think you're probably right. I don't know much about it myself but that sounds like a solid guess to me. I haven't done any major testing other than yeah just daily use and see if it reboots. I couldn't ever get any.ore than about 6 or 7 increments under on either cpu. I read that the big cores need about 25mv more than the little ones to be stable.
Oddly, I got to a point the other day where I realized that i just barely can't make it through 2 full days so I might as well max performance and just accept charging every night even though I usually have 40 to 50% left, but the stanbdy is always so bad that I end up starting the second day with only 40% or less and thus can't make the whole day. Anyway, so I switch from underclocked with less aggressive govs to max clock and more aggressive govs and I think battery life is oddly better now somehow and standby seems unchanged.

benjmiester said:
I think you're probably right. I don't know much about it myself but that sounds like a solid guess to me. I haven't done any major testing other than yeah just daily use and see if it reboots. I couldn't ever get any.ore than about 6 or 7 increments under on either cpu. I read that the big cores need about 25mv more than the little ones to be stable.
Oddly, I got to a point the other day where I realized that i just barely can't make it through 2 full days so I might as well max performance and just accept charging every night even though I usually have 40 to 50% left, but the stanbdy is always so bad that I end up starting the second day with only 40% or less and thus can't make the whole day. Anyway, so I switch from underclocked with less aggressive govs to max clock and more aggressive govs and I think battery life is oddly better now somehow and standby seems unchanged.
Click to expand...
Click to collapse
While it seems odd there's a reason that moving to a higher clock setting can improve battery life though it seems counter intuitive. If you have a task that needs to be done, it's going to request time on the processor. The amount of cycles it takes to complete it will be longer at a lower frequency vs. a higher one. So while it's working at a higher clock rate and drawing more power per cycle its getting the job done much more quickly and overall uses less power. This is the same reason having multiple cores gives us longer battery life. Of course the OS, apps, and phones capabilities have also became more demanding so we don't notice it as much anymore. The trick is finding the lowest frequency we can operate at without diminishing noticeable performance and not increasing the clock cycles needed for tasks by very much. Underclocking can help with this as well if dropping the clock rate by a significant margin isn't feasible.

KCRic said:
While it seems odd there's a reason that moving to a higher clock setting can improve battery life though it seems counter intuitive. If you have a task that needs to be done, it's going to request time on the processor. The amount of cycles it takes to complete it will be longer at a lower frequency vs. a higher one. So while it's working at a higher clock rate and drawing more power per cycle its getting the job done much more quickly and overall uses less power. This is the same reason having multiple cores gives us longer battery life. Of course the OS, apps, and phones capabilities have also became more demanding so we don't notice it as much anymore. The trick is finding the lowest frequency we can operate at without diminishing noticeable performance and not increasing the clock cycles needed for tasks by very much. Underclocking can help with this as well if dropping the clock rate by a significant margin isn't feasible.
Click to expand...
Click to collapse
It is very interesting. I'm now backing off max clock, one increment at a time on both core sets to see where they meet. So far just down to 1500 little and 2000 on the big. Seems to be pretty good.

Hey, kinda late to the party but I recently got an s6 and starting to mess around with undervolting... Problem is I don't know where to start. Where do I get synapse? I'm not familiar with synapse but I did use kernel adiutor in the past.
I'm using this ROM:
https://forum.xda-developers.com/galaxy-s6/development/rom-galaxy-s6-stock-debloated-t3812822
Along with this kernel:
https://forum.xda-developers.com/tm...oc-uc-twsited-kernel-7-0-t-w8-f-flat-t3652139
Any help is appreciated. ?