Database Develop

How does over-clocking my CPU work?

Whilst I am far from disappointed with the Samsung Galaxy Note's performance, it is hard to not feel slightly jealous (despite the Note's superiority thanks to such a large and beautiful screen) of the S3's quad-core processing power. However, I have seen plenty of people on here have over-clocked their processors, which naturally makes the device run quicker.
So, how exactly does over-clocking work? I know that I first have to root my phone, but what then? Is it possible to do on the stock ICS ROM/Kernel? Also, how does it effect battery life and will my phone still deep sleep and work with "Power Saving Mode" like normal? Also, how much can you safely over-clock to and, for those of you have done it, how has the performance been?

Yeah, you nees to be rooted. And then it depends on the kernel. If it comeswith built in overclocking you can use any app like set cpu, sytem tuner pro... to adjust the maximum frequency and if the kernel allows it the voltage too (might needs to be raised to keep your phone stable when overclocked). If there is no native overclocking and/ or the possibility to adapt your cpus voltage you can still use tegrak which works also with kernels without nativ oc/ voltage control.
Word of caution: Don't raise the voltage too much or you will fry your cpu.
Sent from my Galaxy Note running ICS

The sluggishness of gui is not dramatically decreased with overclocking, its coding, not cpu issues. Just check your cpu frequency with cooltool, most of the time max cpu is not even reached, indicative it also doesnt solve it should you raise it by overclocking
I'd rather suggest cm9, aokp, if you dont mind warrantee, they will dratically incruise user experience on performance area
Sent from my GT-N7000 using Tapatalk 2

Nexus 4 Undervolting

I've always been a big fan of undervolting. These are the lowest voltages I can get stable at these common speeds. I found I can underclock the Matr1x kernel further than some others I have tried for some unknown reason. How low have you been able to go? Also, what programs do you use to test stability? So far, I have been running Antutu test completion as a measure of stability. Any suggestions otherwise?
288MHz - 650mv
1.02Ghz - 800mv
1.51Ghz - 1000mv
ROM: Bionic AOSP V3
Kernel: Matr1x 6.5

Noob question~ Why do people undervolt?

WarToilet said:
Noob question~ Why do people undervolt?
Click to expand...
Click to collapse
To increase battery life,

The Long answer is that the CPU has a number of parameters where Clockspeed (MHz) and voltage (mV) are two. Clockspeed, well that is speed. Voltage is related to the amount of energy provided to the cpu, undervolting means that you feed the CPU less juice but demand that it runs at the same clocks. You are essentially starving the CPU,it uses less energy, but can become unstable if the voltage is insufficient to maintain operations. Manufactures always have extra voltage as a safety margin so power users can check their CPU bin (slow, normal, fast or faster) and lower voltages step by step until they crash the phone during a stress test, increase the voltage slightly and boom, your phone uses less battery power while being just as fast.

I undervolt to reduce heat. It makes a significant difference. The battery saving is minimal, but the temperature difference is VERY noticeable.

estallings15 said:
I undervolt to reduce heat. It makes a significant difference. The battery saving is minimal, but the temperature difference is VERY noticeable.
Click to expand...
Click to collapse
Took words from my mouth. This this and this. It reduces heat, which in turn reduces battery use. UV by itself doesn't save a lot of battery, it's the consequences of it. I'm normally not a fan of UV, but with current N4 sw/fw it NEEDS it. It's way too high.
Interesting observation. As of recently my phone jumps up by 3-5c from 37-38 hover. Never used to do it before, not until i got it up to 50c for about half an hour last week. Previously it would stay steadily at 37-38, now it spikes up now and again during use. What's interesting about is that once it goes over 40c battery use increases drastically. So i wonder if people that have really good battery life don't have phones that go over that temp often and vice versa.

I haven't played around with the values too much yet, just a -100mV across the board. This seems to work just fine, so I might experiment some more..
Using Franco test-r69 at the moment.
Sent from my Nexus 4 using xda premium

I undervolt to prevent heating like others say. My Antutu scores drop like a rock when I'm at stock clockspeeds mostly likely due to thermal throttling. Now I can run it repeatedly without having scores drop. It saves battery and runs faster while running games even for very short periods of time, so I am a big fan of undervolting. :good:

Undervolt to reduce power usage, think of the stock voltage as normally being more than is required, think of running for a bus yet you have 2 minutes why waste energy when you can walk and still make it .
Undervolt for less power usage and less heat produced meaning battery performance is better (cooler battery is a more efficient one) and performance is up as you avoid any thermal limits in place .
Great stuff undervolting, I have managed to get -150mV across the board ( 1.5ghz @ 1000mV) and 288mhz is 162.5mV .

I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2

italia0101 said:
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
The more the heat, the faster the battery drains. Since undervolting decreases heat, im sure it should increase battery life. Maybe not for browsing or calling, but playing a heavy 3D game.

is it normal that the higher the frequency the lower the voltage in setcpu?
screenshot: http://db.tt/k6r8c5oI
I'm quite new to nexus 4 undervolting, what's the average amount i can lower the voltages with? (i have a nominal CPU)
sent from my Nexus 4...

zakoo2 said:
how can you guys undervolt? is there an app for that? i bought Franco's kernel updater app, but there's no option to undervolt in there.
edit: just found an app called setcpu, is that it?
sent from my Nexus 4...
Click to expand...
Click to collapse
You can do it from franco kernel updater, from frequencies and voltages - voltages - cpu voltages
But i dont recommend you to undervolt if you dont know what you do.
Sent from my Nexus 4 using Tapatalk 2

aimcr7 said:
You can do it from franco kernel updater, from frequencies and voltages - voltages - cpu voltages
But i dont recommend you to undervolt if you dont know what you do.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I'm familiar with undervolting both on PC and on phone, but i had a Motorola defy before my nexus and undervolting there was a bit different.
sent from my Nexus 4...

zakoo2 said:
is it normal that the higher the frequency the lower the voltage in setcpu?
screenshot: http://db.tt/k6r8c5oI
I'm quite new to nexus 4 undervolting, what's the average amount i can lower the voltages with? (i have a nominal CPU)
sent from my Nexus 4...
Click to expand...
Click to collapse
How are you able to undervolt with SetCPU? I'm not seeing that option using CM10, and Harsh's kernel.

italia0101 said:
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Former nexus s user here, the reason nexus s didn't benefit in battery life much was that it only had 1 core, and used a higher nm manufacturing process, 65nm -> 28nm. Lower voltages in the 28nm means that it multiplies the heat/power savings more than a 65nm, and the 4 cores multiply the savings by up to 4.

FatalityBoyZahy said:
How are you able to undervolt with SetCPU? I'm not seeing that option using CM10, and Harsh's kernel.
Click to expand...
Click to collapse
don't know, it was just there. did you try to reboot after installing the app?
I'm on Franco's kernel btw.
sent from my Nexus 4...

Pls what are the right values for under volting Samsung captivate
Sent from my SGH-I897 using xda premium

I am new to this and my battery goes +40°C when I play simple games... I am running Franco's kernel r71 should I do UV? If so how much? Thanks in advance
Sent from my Nexus 4 using xda app-developers app

xtremer92 said:
Pls what are the right values for under volting Samsung captivate
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
this is the lg nexus 4 forum.
sent from my Nexus 4...

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.

CPU Binning and undervolt

Hi,
I saw BravoMotolora's article about CPU binning, and I thought that it would be great if we compare CPU bin and voltages.
It will be great to know the relationship between voltage and PVS number.
Please follow this procedure
1. Install a custom kernel that lets you do undervolt, e.g. franco.Kernel
2. Do what BravoMotolora said
3. Undervolt your N5 by 25MV
4. Run Antutu
Then, you might see your N5 rebooting or giving you a Antutu score.
If you get the score, go and try the procedure again
I got to -50MV with PVS1 N5.
Please post your results(undervolt that you did and your N5's PVS) here!

Can you not do this?

Do not do what? I mean most of guys here will do undervolt to save battery anyway so won't it be good to share some intel?
Sent from my Nexus 5 using XDA Premium HD app

I'm the same as OP... I have PVS 1 and the max I can UV is -50mV.

you do realize that many custom kernels set their voltages different than default/stock, and differ among themselves? for example, if you go -50mV less on using franco kernel, and go -50mV less using trinity kernel, it means nothing because their voltages differ to begin with. i mean you cant really compare each others voltages that way. you would need to write your voltages in real numbers, and cpu speed steps.

I honestly never saw a huge benefit in undervolting. It can also cause errors which lead to worse battery life.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app

johndrmr said:
I honestly never saw a huge benefit in undervolting. It can also cause errors which lead to worse battery life.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
Click to expand...
Click to collapse
agreed. i personally do better with underclocking, than with undervolting.

simms22 said:
agreed. i personally do better with underclocking, than with undervolting.
Click to expand...
Click to collapse
it's a lot easier to underclock 20% than to undervolt 10%, which approx. gives you the same active power savings. It's a lot safer too, if you don't have a spec sheet for the CPU handy.
underclocking does nothing to idle power (or leakage power) though

This phone does pretty well arlt idle I think. Can't imagine you would see much gain from UV.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app

klin1344 said:
I'm the same as OP... I have PVS 1 and the max I can UV is -50mV.
Click to expand...
Click to collapse
I have a PVS 2 and can undervotl -75mV accross the board and -87.5mV at 300Mhz.
So 2,26Ghz I can run at 0.975 Volt.
CM11 with Bricked Kernel.
Together with Sync off, Google hotword off and optimized automatic brightness I get constantly 5 - 5,5 hours screen on time with websurfing, mail and music stream.
Marcel

menting said:
it's a lot easier to underclock 20% than to undervolt 10%, which approx. gives you the same active power savings. It's a lot safer too, if you don't have a spec sheet for the CPU handy.
underclocking does nothing to idle power (or leakage power) though
Click to expand...
Click to collapse
Underclocking drops the performance of the phone, as the peak performance is not available when needed. Undervolting on the other hand gives you battery savings without affecting peak performance at all. If done too aggressively, it can make the phone unstable, but there is never any danger of hardware damage. The instability will at most cause errors, random reboot, or a freeze up. If this happens, you know you've pushed too far under, and you can bump voltage closer to stock after booting the phone back up. If running stably, undervolting is actually marginally better for your phone hardware than stock voltage because you are wasting less of the energy in heating up the chips and damaging them.

rajendra82 said:
Underclocking drops the performance of the phone, as the peak performance is not available when needed. Undervolting on the other hand gives you battery savings without affecting peak performance at all. If done too aggressively, it can make the phone unstable, but there is never any danger of hardware damage. The instability will at most cause errors, random reboot, or a freeze up. If this happens, you know you've pushed too far under, and you can bump voltage closer to stock after booting the phone back up. If running stably, undervolting is actually marginally better for your phone hardware than stock voltage because you are wasting less of the energy in heating up the chips and damaging them.
Click to expand...
Click to collapse
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.

simms22 said:
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
Click to expand...
Click to collapse
Sorry, but CPU underclocking means always a drop in CPU performance.
When you compensate this drop in your case by always having all four cores active you produce more heat with the active cores.
(and I estimate it will produce more heat/battery depletion than the original phone settings. (max 2,26Ghz and variable core usage)
When you argue that in general a normal user is not realizing a drop in performance due to underclocking...fine.
But it will always be a drop in performance.
Undervolting in opposite to underclocking produces no drop in performance but actually a rise in efficiency. (and thats what CPU/GPU development is all about).
Less heat, less battery depletion, same performance.
Why not taking advantage of that by undervolting?
Its free lunch.

simms22 said:
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
Click to expand...
Click to collapse
I agree with you here. 1036 mhz is a great CPU speed for running the device and most apps. Most games UC the CPU for better battery temp like in PPSSPP. Less temperature throttle and more stable frames per second.
Benchmarks are a difference story though but who cares about those. UC is lag free, and buttery smooth so why not?
Sent from my Nexus 5 using Tapatalk

zz_marcello said:
Sorry, but CPU underclocking means always a drop in CPU performance.
When you compensate this drop in your case by always having all four cores active you produce more heat with the active cores.
(and I estimate it will produce more heat/battery depletion than the original phone settings. (max 2,26Ghz and variable core usage)
When you argue that in general a normal user is not realizing a drop in performance due to underclocking...fine.
But it will always be a drop in performance.
Undervolting in opposite to underclocking produces no drop in performance but actually a rise in efficiency. (and thats what CPU/GPU development is all about).
Less heat, less battery depletion, same performance.
Why not taking advantage of that by undervolting?
Its free lunch.
Click to expand...
Click to collapse
again, sure, if youre benchmarking the performance will drop, yes. but if its something that the user doesnt see or feel, then its irrelevant.
no extra heat is produced. also, i get 5.5-7h screen on time with very heavy use. granted, i use the browser much more than i game, but thats what i use my device for mostly.
when needing the extra performance, or wanting to, i overclock. everybody uses their device differently, has differing needs. i would never say one way is better or worse than the other way.

simms22 said:
again, sure, if youre benchmarking the performance will drop, yes. but if its something that the user doesnt see or feel, then its irrelevant.
no extra heat is produced. also, i get 5.5-7h screen on time with very heavy use. granted, i use the browser much more than i game, but thats what i use my device for mostly.
when needing the extra performance, or wanting to, i overclock. everybody uses their device differently, has differing needs. i would never say one way is better or worse than the other way.
Click to expand...
Click to collapse
You can do everything you are already doing, but also undervolt, and your battery life will increase, without affecting your performance. Your performance will be different than my performance (because I don't underclock), however imperceptible as it may be. So undervolting is still better than not undervolting, even for you.

Using EX kernel 3.27, underclocked to 1.5Ghz, undervolted to "700 min" and using "stock" thermal throttling setting. Rock solid and it barely even gets warm now. Responsiveness and performance is only a touch worse than stock; the only places I really notice any performance reduction is in intensive games and app install times. Battery life is massively improved.

Undervolting vs Underclocking vs Hotplugging for battery life

Can anyone explain to me what is better?
I know that underclocking reduces cpu frequency, which means lower temperatures and also better battery, but performance is worse, so it takes longer to complete tasks...but if it takes longer to complete tasks, it means it will also have screen on for a longer time right?so it saves power from the cpu, but keeping the screen on for that extra time also means it will consume extra power right?
About undervolting, is it better to undervolt or to underclock when it comes to battery life?i know that with undervolting there is less heat produced because of the reduced voltages. From what i have read (i dont know if it is correct) the power consumption is given by this equation: P = f*c*(V^2) where f is frequency, c is capacitance and v is voltage. It makes sense that reducing voltage means less heat, but if i reduce CPU frequency it also produces less heat because it reduces power. Most of the time i read that underclock is better for battery because it uses less power, but like i said earlier, it takes longer to complete tasks and in result i have to keep the screen on for a longer time.
About hotplugging, i have seen some users with good battery life screenshots, and mentioning that they disabled hotplugging, because they said that turning cores on and off also wastes energy. So is it better to hotplug or not?
would really like to get some answers because i know nothing about this..I also know that i could test each setting and and see which is better, but i dont use my phone the same way everyday so its kind of hard to determine...

Short version and after extending testing (2 cores max, -175Uv, underclocking at 1000 or 1300mHz) with different kernels and always on stock Rom,
the result was that there was no noticeable difference at the battery life with a normal setup of using of 4 cores at normal max freq of 1512mhz.
A custom kernel in comparison to the stock kernel makes more sense cause of the optimization they offer for performance and battery life.
Unleashed from Onda v957m on TDT

RASTAVIPER said:
Short version and after extending testing (2 cores max, -175Uv, underclocking at 1000 or 1300mHz) with different kernels and always on stock Rom,
the result was that there was no noticeable difference at the battery life with a normal setup of using of 4 cores at normal max freq of 1512mhz.
A custom kernel in comparison to the stock kernel makes more sense cause of the optimization they offer for performance and battery life.
Unleashed from Onda v957m on TDT
Click to expand...
Click to collapse
nice to have some feedback from someone that tested=p. what about hotplugging? Today i disabled hotplugging and had always 4 cores on and it does not seem to be wasting more battery than with hotplugging enabled

These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4

n2d551 said:
These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4
Click to expand...
Click to collapse
Also lot of discussion about Uv here
http://forum.xda-developers.com/showthread.php?t=2137034
Unleashed from Onda v957m on TDT

n2d551 said:
These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4
Click to expand...
Click to collapse
totally forgot about bedalus experiments!i had a Nexus S at the time and saw that post, but back then i didnt mess around with anything on my phone so i completely forgot=p.thanks!
The only thing he doesnt adress is hotplugging(the Nexus S was single core so he couldnt even if wanted=p). Anyone care to shed some light on hotplugging?is it really worth it or there are minimal gains?

migueldbr said:
totally forgot about bedalus experiments!i had a Nexus S at the time and saw that post, but back then i didnt mess around with anything on my phone so i completely forgot=p.thanks!
The only thing he doesnt adress is hotplugging(the Nexus S was single core so he couldnt even if wanted=p). Anyone care to shed some light on hotplugging?is it really worth it or there are minimal gains?
Click to expand...
Click to collapse
There are different hotplugging methods.
The stock one as a boost feature, as soon as u touch the screen ur decvice goes to dual core 1026mhz for a couple seconds even if the load is super low.
Custom kernels have many variants on the hotplugging "style". Most of them dont have the touch boost included to save battery (but u can have the same kind of touch boost enabled by the governor, ex: franco kernel). Others simply advise u to turn off hotplugging == less calculation of the load to decide if the device needs to plug it or not + no waiting time to get the performance boost of many cores online (since all 4 are already online) + somewhat more heat since all cores are allways draining battery.
Im no expert and i hope all i said is right, at leats its what i know.
What i personally look for is:
Min core 1
Max cores 4
No touch boost (no heat while u are simply texting via sms on 2G with data and wifi OFF)
sent from my diabetic Nexus 4 (too many KitKats).

C4SCA said:
There are different hotplugging methods.
The stock one as a boost feature, as soon as u touch the screen ur decvice goes to dual core 1026mhz for a couple seconds even if the load is super low.
Custom kernels have many variants on the hotplugging "style". Most of them dont have the touch boost included to save battery (but u can have the same kind of touch boost enabled by the governor, ex: franco kernel). Others simply advise u to turn off hotplugging == less calculation of the load to decide if the device needs to plug it or not + no waiting time to get the performance boost of many cores online (since all 4 are already online) + somewhat more heat since all cores are allways draining battery.
Im no expert and i hope all i said is right, at leats its what i know.
What i personally look for is:
Min core 1
Max cores 4
No touch boost (no heat while u are simply texting via sms on 2G with data and wifi OFF)
sent from my diabetic Nexus 4 (too many KitKats).
Click to expand...
Click to collapse
actually touch boost and hotplugging are different things...touch boost is a feature where as soon as you touch the screen, the cpu ramps up the frequency to the specified touch boost frequency. Hotplugging is a different thing, where cores of the cpu are turned on and off when the phone does not need them to be on all at the same time. I know that touch boost drains more battery, but i dont know about hotplugging...would like to see some tests/benchmarks, but i dont think there are any...

migueldbr said:
actually touch boost and hotplugging are different things...touch boost is a feature where as soon as you touch the screen, the cpu ramps up the frequency to the specified touch boost frequency. Hotplugging is a different thing, where cores of the cpu are turned on and off when the phone does not need them to be on all at the same time. I know that touch boost drains more battery, but i dont know about hotplugging...would like to see some tests/benchmarks, but i dont think there are any...
Click to expand...
Click to collapse
Different things but on stock kernel touch boost is implemented on the hotplug and not the governor.
Any difference btw 4 cores online or hotplugging must minor, and have draw backs on heat wich affects the battery capacity.
Eventhough u can say that hotplugging may drain an amount of battery to plug and unplug cores, i would say its minor.
Talk to @simms22 , he is the "trinity kernel guy", four cores online is a must for him
sent from my diabetic Nexus 4 (too many KitKats).

From my experience, under clocking as well as running a 2 core setup doesn't change anything for the better. Most times for the worst due to a worse user experience.
Undervolting is something that, solely from the physical side, cannot make things worse (unless you under clock too much). Undervolting will make your CPU cores use less current. Less current running through an electric circuit always means less heat, too.
To put it simple:
If my regular voltage at 384mhz is 950mv and I lower the voltage to 800mv and after testing it proves to run stable my device now uses 150mv less on that frequency.
Sent from my Nexus 4 using XDA Free mobile app

Oxious119 said:
From my experience, under clocking as well as running a 2 core setup doesn't change anything for the better. Most times for the worst due to a worse user experience.
Undervolting is something that, solely from the physical side, cannot make things worse (unless you under clock too much). Undervolting will make your CPU cores use less current. Less current running through an electric circuit always means less heat, too.
To put it simple:
If my regular voltage at 384mhz is 950mv and I lower the voltage to 800mv and after testing it proves to run stable my device now uses 150mv less on that frequency.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
no matter what you do , its still going to be a mediocre battery life , best leave it as it is because the way nexus 4 is designed its still going to be getting annoyingly warm on games

Well, from my own experience undervolting definetly reduced heat and made the battery last longer. Don't expect 2 hours more sot, though. Its most notably while the device is idle.
Sent from my Nexus 4 using XDA Free mobile app

nice man
very helpful...

Help pls..
Can any1 help me undervolting Unleashed kernel.. providing tips or the link ll be vry helpfull..