Related
First off, I would like to apologize in advance in case a thread like this exist and I can't find it.. :/ (Search is down, tried Googling) also, if anyone believes this to be in the wrong forum.
ANYWAYS! This is intended to be a preference/opinions thread centering around your OC/UC and Undervolt settings. Feel free to post your current set-up in Voltage Control (or any app of the like) and what Kernel you are running! I wanted to start this to get an idea of what everyone else is setting their UV and CPU clocks to, and possibly give a few of them a try on my own device. :]
Personally all of my clock speeds are at their defaults except for 1000Mhz @ 1200mV. (-75mV). I am also rocking Genocide v1.0 and getting a decent 30hrs of battery life with pretty moderate use.
Post away!
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
kennyglass123 said:
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
Click to expand...
Click to collapse
I believe that would be my point however.. curious as to what other people are running as far as cpu and voltage is concerned. Their success and failures. What people can get away with and remain stable. I, and others, could then try their setup (taking precautions of course; ie Nandroid backup.) And see what we get. Who knows, maybe I might adapt a set up that runs better on my device than my current one.
Sent from my SPH-D700 using XDA Premium App
Yes, every phone is different, but that is just more of a reason to collect data - perhaps a baseline can be established, which would be helpful in determining if a particular phone is messed up or just at the low end of the scale. Right now it is hard to determine if a particular phone's troubles are caused by low quality or by damaged hardware.
I keep all voltages at stock, and don't use any OC - my phone runs fine as is, and the battery life actually seemed worse with UV (and my screen felt hot with the screen UV).
Sent from my SPH-D700 using XDA App
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
xopher.hunter said:
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
Click to expand...
Click to collapse
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
I can only use Genocide kernel to get 1.3ghz at stock voltage with since all the other choices are uv'd. My last two Epics were able to handle uv'd 1.4ghz by 50mV but I'm not really complaining as I think this is a new phone they gave me and not a refurb. I currently have 100-400 uv'd by 100mV, 600-1000 uv'd by 75mV and 1300 at stock.
My phone can handle 1.4 Ghz but only with the stock voltages. If I try to touch it even by 25mV it locks up.
Who all has enabled the 100Mhz step? I noticed when I did my phone went into Deep Sleep a lot less by a noticeable amount. Staying at 100Mhz a lot.
Always interesting to hear about all this theory behind the reasons for undervolting OC and UC, then to hear about the issues (at times extreme) some have. I would also like to know who uses the 100 step and if it is noticeably better on battery life than the 200? Unfortunately I am missing out on it if I am. Still running Genocide here, but with 1.0 at -50mv 800 @ -50 and 600 @ -25. Very stable and still at 30+ battery life. Having 1.0 down 75 made me nervous. although I hear people dropping it down -100mv successfully.
Sent from my SPH-D700 using XDA Premium App
Good tip about "aggressive UnderVolting"...didn't know that actually drains your battery more. Might explain why 6 hours into my day, my battery is down to 30% already!!! I had it set at 1120Mhz UV to 1175mV (Stock = 1300)...
So now I'm going to try 1200Mhz only UV by 50...see what my battery life is after this!
Custodian said:
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Can you explain how this is so? Is this based on any actual research, experimentation, or online documentation, or is this just your own opinion?
Unless your undervolt causes the CPU to hang (I've seen mine start to warm up when it's hung, until a battery pull), I don't understand how providing less voltage to the cpu will cause it to drain the battery faster.
If you change the voltage settings please don't blame the rom developers when you phone bricks...
Sent from Bonsai 7.1.3.1
I'm running Twilight Zone v 1.1.1 RC1-Hajime Taisho, Vision kernel v 1.2
SetCpu-1.450 max
-1.450 min
Quadrant-2377
Linpack-20.577
Voltage Control-1.450
Uv -100
Quadrant-2346
Linpack-21.495
I ran SetCpu, benchmarks, ran VC, benchmarks..... This Epic runs super fast, with no FC's or any other problems at all. I'm currently using VC with the uv-100. As far as excessive battery use, I have Mugen 3200 mah battery. This battery lasts all day in heavy use with no problem.
Sent from my SPH-D700 using XDA Premium App
Hello guys. I just want to take information that there are many tweaks to overclock galaxy s3 to max 1.8 ghz. If we set to maximum overclocking then is there any risk for damage hardware? Because 2 months before i had nokia n8 & i set this device to overclock & it damaged all board,now its totally destroyed. According to my point of view,sometime i think that nokia n8 has only 680 ghz & due to overclock it run on higher clock speed & so that due to low processor it could not manage or handle the higher clock speed & it ran on heavy clock speed continuesly then overload of processor it got damaged. It is my fear for s3. And i think for s3 that it has higher processor with 1.4 ghz,if i set it to 1.8 ghz then there is no risk bcoz of there are cpu governor. With this,the s3 does not run continues on 1.8 ghz higher speed, governor takes control over the cpu to run on higher clock speed according to their high usage like 200 ghz, 500ghz, 800 ghz, 1.4ghz & so on. So i think i can overclock my galaxy s3 with kernel but I'm still confused & I'm not expert. So plz suggest me to do overclock without any damage fear. Thanx a lot.
If you don't know what you are doing, then don't do it!
Sent from my GT-I9300 using xda app-developers app
sfjuocekr said:
If you don't know what you are doing, then don't do it!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If i don't but you know then u can tell me about any risk.
NOTHING is without risk, but a good place to start is just to install the latest Siyah S3 Kernel and run it it at 1.6ghz for the CPU and default settings for the GPU. I tried running my CPU at 1.7 and 1.8 and the it wasn't 100% stable and the temps were to high for my liking. Be moderate in your settings and you shouln't encounter any issues.
http://www.gokhanmoral.com/ latest version is 1.7rc1
That will give you a good performance bump with the minimum of risk (in my opinion).
Other than that installing a bloatware free ROM will also give a nice bump. I personally run Omega V29 with the above 1.6 overclock settings and it lightning fast. :good:
There is always a risk involved in overclocking.
1.8ghz isn't stable for most people but 1.7 is quite stable.
How well your device handles overclocking depends on the quality of the chip you got.
This is down to the manufacturing process, you may get a good chip from the middle of the wafer or a not so good one from nearer the edge.
if you want to reduce heat them you should undervolt the CPU, less current means less heat.
Obviously it isn't good for the hardware in the long run but that's what you gotta take into account when you overclock, I've overclocked every phone I've ever had and haven't had any problems but YMMV.
Sent from my Nexus 7 using xda premium
nodstuff said:
There is always a risk involved in overclocking.
1.8ghz isn't stable for most people but 1.7 is quite stable.
How well your device handles overclocking depends on the quality of the chip you got.
This is down to the manufacturing process, you may get a good chip from the middle of the wafer or a not so good one from nearer the edge.
if you want to reduce heat them you should undervolt the CPU, less current means less heat.
Obviously it isn't good for the hardware in the long run but that's what you gotta take into account when you overclock, I've overclocked every phone I've ever had and haven't had any problems but YMMV.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
could u plz tell me that what is the process of undervolt if i undervolt the cpu then it is related to only heat or performence also?
If you use siyah kernel then in the stweaks app that comes with it you can choose how much you want to undervolt.
I suggest starting with -25mv or -50mv and check stability.
I use -100mv without problems but like in said earlier YMMV.
It doesn't give a performance boost per se, but less heat in the chip will mean that it doesn't hit the temperature throttle threshold as easily and that means more performance.
The CPU will begin to throttle (limit clock speed) at around 75c until the temp drops and the CPU is allowed to run at max clock speed again.
Usually you will only hit the temp throttle threshold under very heavy loads, for example repeated benchmarks.
Sent from my GT-I9300 using xda premium
mrjoy said:
Hello guys. I just want to take information that there are many tweaks to overclock galaxy s3 to max 1.8 ghz. If we set to maximum overclocking then is there any risk for damage hardware? Because 2 months before i had nokia n8 & i set this device to overclock & it damaged all board,now its totally destroyed. According to my point of view,sometime i think that nokia n8 has only 680 ghz & due to overclock it run on higher clock speed & so that due to low processor it could not manage or handle the higher clock speed & it ran on heavy clock speed continuesly then overload of processor it got damaged. It is my fear for s3. And i think for s3 that it has higher processor with 1.4 ghz,if i set it to 1.8 ghz then there is no risk bcoz of there are cpu governor. With this,the s3 does not run continues on 1.8 ghz higher speed, governor takes control over the cpu to run on higher clock speed according to their high usage like 200 ghz, 500ghz, 800 ghz, 1.4ghz & so on. So i think i can overclock my galaxy s3 with kernel but I'm still confused & I'm not expert. So plz suggest me to do overclock without any damage fear. Thanx a lot.
Click to expand...
Click to collapse
1.7ghz should be alright for a 32nm chip like the exynos 4412 on our s3. HTC has had their One S (with a 45 nm chip) clocked at 1.7 ghz. The lower the nanoneter, the more ambitious you can be with clock speeds. Try 1.6 or 1.7 ghz with default voltage settings and see how that goes
Sent from my GT-I9300 using Tapatalk 2
nodstuff said:
If you use siyah kernel then in the stweaks app that comes with it you can choose how much you want to undervolt.
I suggest starting with -25mv or -50mv and check stability.
I use -100mv without problems but like in said earlier YMMV.
It doesn't give a performance boost per se, but less heat in the chip will mean that it doesn't hit the temperature throttle threshold as easily and that means more performance.
The CPU will begin to throttle (limit clock speed) at around 75c until the temp drops and the CPU is allowed to run at max clock speed again.
Usually you will only hit the temp throttle threshold under very heavy loads, for example repeated benchmarks.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
You are using -100 undervolt, that mean its high current & mean if i select 25 to 50 then its less current than 100??? & is there any battery improvement if i select less current mean less heat.?
I am using -100mv, as in minus 100mv, 100mv less than stock.
Less current is less heat and *maybe* battery savings.
-100mv is less current than -50mv.
Sent from my GT-I9300 using xda premium
nodstuff said:
I am using -100mv, as in minus 100mv, 100mv less than stock.
Less current is less heat and *maybe* battery savings.
-100mv is less current than -50mv.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I am new to all this just one question, will over clocking drain the battery quicker?
andmax66 said:
I am new to all this just one question, will over clocking drain the battery quicker?
Click to expand...
Click to collapse
Yes atleast while it's using the higher clock speeds.
Sent from my GT-I9300 using xda premium
What's a good kernel for overclocking for the stock I9300 running ICS (don't have the JB yet)? Will the latest Siyah work?
DenethorLenwion said:
What's a good kernel for overclocking for the stock I9300 running ICS (don't have the JB yet)? Will the latest Siyah work?
Click to expand...
Click to collapse
siyah, its most beginner friendly wih stweaks (for ICS you should check 1.5 version if its still obtainable, however should be)
Sent from my GT-I9300 using xda app-developers app
Antutu and Quadrant, all are just bull****. Just to see their manipulated scores, overclocking does not make any sense.
At ground level, applications do not run anything faster as overclocking alone does not work here. Even if you get milli milli milli second improvement which is just nothing against damage of CPU.
Got it?? now start using your phone as it should be and made for.
Before overclocking you should ask yourself Why you want to overclock. If it's because the phone have some lags there is other(safer) way to solve this problem. Honestly I overclock mine for a while (just because I'm a tester) but the S3 is fast enough for everything. You should see my S3. The app drawer appears (almost) instantaneously. Any games play smoothly etc...
On this phone overclocking is possible but useless. If you want to learn how to overclock just to learn how, search in the stickies for the overclocking guide.
I have tried overclocking and undervolting for the last week now and I can say that overclocking has not made any visible difference to my S3. Overclocking seems to be a nice option to have, but the S3 does not need it. Undervolting on the other hand reduces lag considerably when playing games for long periods. Usually my S3 started to get laggy after about 1 hour of Asphalt, but now it does not get laggy at all. I have undervolted by (-)125.
Hope that helps.
When I play pokemon black 2 on nds4droid without overclocking it gives me 20 to 30 fps and when I overclock it to 1.7 GHz i get 28 to 35 fps
Sent from my GT-I9300 using xda premium
Firstly you need a kernel supporting overclocking... Secondly its fine if u wanna play around with your device... Lastly I would suggest u to overclock it to 1704 MHz max (avoiding any boot loops )....
I would recommend Siyah 1.9.1 (as your Kernel) and "Noop" as your I/O Scheduler... In case ure using Siyah as your Kernel, try using "Lulzactiveq" as your governer...
Furthermore u can tweak the governer if u want more juice out of it....
Try it.....
Sent from my GT-I9300 (Hassan Khalid Malik) using xda premium
---------- Post added at 10:50 PM ---------- Previous post was at 10:41 PM ----------
Mr Faeces said:
I have tried overclocking and undervolting for the last week now and I can say that overclocking has not made any visible difference to my S3. Overclocking seems to be a nice option to have, but the S3 does not need it. Undervolting on the other hand reduces lag considerably when playing games for long periods. Usually my S3 started to get laggy after about 1 hour of Asphalt, but now it does not get laggy at all. I have undervolted by (-)125.
Hope that helps.
Click to expand...
Click to collapse
Lag can be reduced by tweaking your governer and some other settings... U don't have to underclock it...
Sent from my GT-I9300 (Hassan Khalid Malik) using xda premium
I have tried overclocking to1600, and although Quadrant stats are higher, I did not notice any difference in normal usage. I am a general usage text and phone calls and email user. Minimal game playing. I stick to 1400 now and everything seems just the same!!
At the moment I am running Sotmax rom and boeffla kernel.
Hope this helps.
Never messed with these settings before and couldn't find anything with a search so if someone could explain for me to easily understand please
How do go_hispeed_load and hispeed_freq work exactly (what do they do)? I'd love to learn so I can start messing with these settings
Thanks everyone.
Sent from my Nexus 4 using xda premium
I think go_hispeed_load is the value that the CPU load has to reach before it ramps up to the Max CPU speed set. I think hispeed_freq is the clock speed used mainly before the load set in go_hispeed_load is reached I think.
I'm running Franco #22 and I've set
go_hispeed_load to 918 and hispeed_freq to 75 butter smooth running code fire x ROM and Max CPU to 1216
Sent from my Nexus 4 using xda premium
samwebbo1990 said:
I think go_hispeed_load is the value that the CPU load has to reach before it ramps up to the Max CPU speed set. I think hispeed_freq is the clock speed used mainly before the load set in go_hispeed_load is reached I think.
I'm running Franco #22 and I've set
go_hispeed_load to 918 and hispeed_freq to 75 butter smooth running code fire x ROM and Max CPU to 1216
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ah, that gives me a better understanding. So the phone will be running in the hispeed_freq before it reaches the load where it has to ramp up some more to handle the task, right? Can you explain to me how load works? Like how do you calculate how the load number adds up? (to your 75 for example)
Ngo93 said:
Ah, that gives me a better understanding. So the phone will be running in the hispeed_freq before it reaches the load where it has to ramp up some more to handle the task, right? Can you explain to me how load works? Like how do you calculate how the load number adds up? (to your 75 for example)
Click to expand...
Click to collapse
Yeah that's right. I'm not too sure the load value scale to be honest but Franco recommended 70 and a lot of users are stating that 75 is good (and in theory should save more battery life as you will use the higher frequencies less often). So its up to you
Sent from my Nexus 4 using xda premium
samwebbo1990 said:
Yeah that's right. I'm not too sure the load value scale to be honest but Franco recommended 70 and a lot of users are stating that 75 is good (and in theory should save more battery life as you will use the higher frequencies less often). So its up to you
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for your input, always learning something new everyday
So in essence a lower hispeed_freq is better to conserve battery as is a higher go_hispeed_load? And then just to find a good balance between the two to maintain smoothness, correct?
Ngo93 said:
Thanks for your input, always learning something new everyday
So in essence a lower hispeed_freq is better to conserve battery as is a higher go_hispeed_load? And then just to find a good balance between the two to maintain smoothness, correct?
Click to expand...
Click to collapse
I think any lower than 918 might be too laggy, I would suggest to stick to 918/75 for smoothness and good battery life. A bit off topic but I'm using these settings with code fire x ROM and I am getting unbelievable battery life (and this is not just me). I'm currently on track for over 6 hours screen on time!
Sent from my Nexus 4 using xda premium
samwebbo1990 said:
I think any lower than 918 might be too laggy, I would suggest to stick to 918/75 for smoothness and good battery life. A bit off topic but I'm using these settings with code fire x ROM and I am getting unbelievable battery life (and this is not just me). I'm currently on track for over 6 hours screen on time!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Wow that's nice! I hear a lot about that ROM too, I am sure to give it a spin in the future
Time to start tweaking some settings ^_^
read this thread about governor and all things related.
http://forum.xda-developers.com/showthread.php?t=1369817
i have franco kernel at hispeed freq at 810 and load at 60 max freq is at 1134mhz
i thought the load is in percentage ?, if i have it higher at that clock there is a delay in performance,
I used to get about 2 hrs 25 minutes SOT with:
3g, 50% brightness, 1.2ghz, 2 cores, - 175 uv, interactive (hispeed at 702mhz)
Now I've got 2 hrs (30% battery left) with th following:
3g, 50 brightness, 4 cores, 1.5ghz, - 175uv, Wheatley governor.
Why am I getting better battery using more power?
I'm also getting amazing performance.
Thanks!
Sent from my PAC powered Matr1x fueled monster NEXUS 4
It MAY be this:
First test with 2 cores maybe used the full 1.2Ghz for a long time.
Second test with 4 cores maybe just used 1Ghz(just an example).
And the second test there is another govenour set...
Correct me if i'm wrong.
Sent from my Nexus 4 using xda app-developers app
failly said:
It MAY be this:
First test with 2 cores maybe used the full 1.2Ghz for a long time.
Second test with 4 cores maybe just used 1Ghz(just an example).
And the second test there is another govenour set...
Correct me if i'm wrong.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I checked the frequency usage in trickster, on 2 cores 702 was uses the most, 1.2ghz was barely used.
On 4 cores, 1.5 is used quite a lot.
Also, Wheatley is a performance governor, with decent battery, I think interactive is the same . But Wheatley gives better performance.
Sent from my PAC powered AKFAUX fueled monster NEXUS 4
okmijnlp said:
I checked the frequency usage in trickster, on 2 cores 702 was uses the most, 1.2ghz was barely used.
On 4 cores, 1.5 is used quite a lot.
Also, Wheatley is a performance governor, with decent battery, I think interactive is the same . But Wheatley gives better performance.
Sent from my PAC powered AKFAUX fueled monster NEXUS 4
Click to expand...
Click to collapse
Thanks for clearing it up!
Hmm well I wouldn't know any other explanation!
Sent from my Nexus 4 using xda app-developers app
Race to idle.
Same reason why LTE can use less power than 3g/2g in certain situations. Same goes for underclocking. (Yes, underclocking can actually decrease the battery life)
Basically, you draw more power but finish the task more quickly. Therefore you have higher peak power usage, but it will go back down more quickly resulting in lower overall power consumption.
For example: you need 10 seconds for a task while draining 100mA/h on the first setup.
On the second one, it only takes 5 seconds to finish, but uses 150mA/h.
Overall, the first way had lower peak currents but drained more power overall than the second.
Hello!
I heard about the term "UnderVolting" and I heard it would give me better battery life.
I want to do it but I have few questions before.
1. Is undervolting affects the CPU , GPU or Battery?
2. Can It damage the device?
3. Can it decrease the device performance?
Thanks!
Wassupdog said:
Hello!
I heard about the term "UnderVolting" and I heard it would give me better battery life.
I want to do it but I have few questions before.
1. Is undervolting affects the CPU , GPU or Battery?
2. Can It damage the device?
3. Can it decrease the device performance?
Thanks!
Click to expand...
Click to collapse
1. It effects the cpu. When you undervolt you are reducing the amount of power that is supplied to the cpu depending on what speed the cpu is running at.
2. It is unlikely to damage the device physically but if you undervolt too far the cpu can start failing actions resulting in corruption, but the most common symptom is that it will reboot itself if you go too low.
3. Undervolting can reduce performance but going down -100 mv across the board is usually stable for most.
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
1. It effects the cpu. When you undervolt you are reducing the amount of power that is supplied to the cpu depending on what speed the cpu is running at.
2. It is unlikely to damage the device physically but if you undervolt too far the cpu can start failing actions resulting in corruption, but the most common symptom is that it will reboot itself if you go too low.
3. Undervolting can reduce performance but going down -100 mv across the board is usually stable for most.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks!
Is it recommended to undervolt?
I just want a better battery and around the same performance as it now.
You are confusing undervolt with underclock. UC is a proven way to increase battery, but it directly makes the CPU run slower. UV will make the CPU/GPU/RAM receive less milivolts, and it will only increase battery, and not decrease performance. The thing with UV is that if the CPU at any given time does not get enough power, it can't perform a given task, and your phone will reboot.
Sent from my LG-P760 using xda app-developers app
In a nutshell UV will not destroy your phone and is it recommended? If you are in xda then you know the risks or at least should read up on the risks. I would say 90% of the custom kernels are undervolted out the box and yes its a great help. I have been UV, UC and sometimes even OC for years now with no negative effects. Give it a shot and if you are worried start slow like -25.
Try mathkids kernel(JSS roms only) which is undervolted -100 and if you read the thread its never been an issue for anyone. I have heard that UV may cause some issues with Maps locking fast
Dr.Molestratus said:
You are confusing undervolt with underclock. UC is a proven way to increase battery, but it directly makes the CPU run slower. UV will make the CPU/GPU/RAM receive less milivolts, and it will only increase battery, and not decrease performance. The thing with UV is that if the CPU at any given time does not get enough power, it can't perform a given task, and your phone will reboot.
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
I'm not Confusing undervolt with underclock.
Undervolting can and does reduce performance if you go too far. (Not far enough to cause reboots)
Underclocking is not a proven way to increase battery, in fact it's quite controversial.
It's called race to idle.
Pretty much all processors have great power savings at idle speeds.
By lowering the clock speed common tasks and background processes take longer to perform. Thus keeping the cpu at a higher clock rate (using more mv) for longer and overall using more battery than what it would have done at a higher speed.
From my own tests -150 mv undervolt resulted in slower and sometimes even laggy performance. -100 is great
Underclocking to 1ghz shortened my average daily battery life by nearly 2 hrs compared to running at stock 1.5
Say what you like about stats but these are the results I found from actual usage
Sent from my Nexus 4 using xda app-developers app
UV will reduce how hot your phone gets.. and if your phone gets too hot thermal throttling will reduce the cpu speed.. and thus if u UV it will reduce thermal throttling and will increase performance..
Thanks to everyone !