Database Users

[Q] [Opinions] Undervolt Settings.

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

CPU

I don't know if it is normal for my CPU speed to be so low, I know that it lowers to save battery but it is always so low and I can see the effects it has. Anyone else get something like this. (quadrant standard edition)

yes it's underclocking to use lower battery when not needed ,it's perfectly normal.
don't worry , it'll fire full throttle (1400 MHZ) when you run a game or something demanding.

Use cpuspy with it you can check the times that CPU spends on each frequency.
Sent from my GT-N7000 using Tapatalk 2

Thanks. I was a bit worried because on other devices I tested the processor was always at maximum.
Sent from my GT-N7000 using XDA

Did you at least readed it?
It says Minimum 200Mhz and Max 1400Mhz.
Its how note works. From 200Mhz to 1400Mhz. It scales the CPU speed from 200 to 1400Mhz when you need power.
It also can disable one of the two cores (CPU1 always) to save battery.

It also says that on the galaxy s 2 but that did not go below 1200MHz when i tested it so I was not sure.
Sent from my GT-N7000 using XDA

ZacDerbyshire said:
It also says that on the galaxy s 2 but that did not go below 1200MHz when i tested it so I was not sure.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Something was wrong with your GS2.

It says 500MHz because that's the current frequency it used when you took that screenshot. If it had said 1400MHz, then it would mean that it used all the power to take a screenshot, which wouldn't be normal.
The CPU isn't working at 1.4GHz 24/7. If it had done that, your battery would have lasted for 1 hour. It uses as much as it needs to, and if an app doesn't require much power, it won't use much power. Simple.

LordManhattan said:
It says 500MHz because that's the current frequency it used when you took that screenshot. If it had said 1400MHz, then it would mean that it used all the power to take a screenshot, which wouldn't be normal.
The CPU isn't working at 1.4GHz 24/7. If it had done that, your battery would have lasted for 1 hour. It uses as much as it needs to, and if an app doesn't require much power, it won't use much power. Simple.
Click to expand...
Click to collapse
use the force choke on him

Safe Undervolting

Hi, I've lowered all the figures by 100mv, but I notice no difference in my battery life. Is it safe to lower the figures more?
Sent from my Nexus 7 using xda premium

Define what you mean by "safe".
Higher core voltages are used at higher clock rates in order to preserve logic margin in the face of more power supply noise and tighter timing. So, undervolting by definition means you are giving up margin.
Whether your SoC happens to have a worst-case timing path which is "fast" or "slow" relative to other devices cannot be deduced by anyone here on XDA or even at Nvidia. About the best you can hope for is some "feel good reports" about what others do with undervolting and completely undisciplined "testing". But even that provides no information about your individual chip.
good luck

Thanks for your reply. By "safe" I mean without damaging my device. And yes, it would be interesting to hear some undervolting stories. I'd quite like to extend my battery life. Cheers!
Sent from my Nexus 7 using xda premium

I've been using my nexus 7 runing a AOKP pub build by mrRobinson and franco's r47 kernel. i've undervolted the entire board by 100mv it is runing pretty solid without any noticible lag or instability. Yet every chip is diferent and can or cannot this margin you'll have to test for your self. Just leave the option 'set on boot' unticked untill your sure that your device is capable of using those kind of voltages. And don't use very large steps. Just like overclocking in fact! Try it - it runs - get a little bit lower. If it crashes you shoukd be able to reboot the nexus and the settings you've changed reseted
Sent from my Nexus 7 using Tapatalk 2

antmasi said:
I've been using my nexus 7 runing a AOKP pub build by mrRobinson and franco's r47 kernel. i've undervolted the entire board by 100mv it is runing pretty solid without any noticible lag or instability. Yet every chip is diferent and can or cannot this margin you'll have to test for your self. Just leave the option 'set on boot' unticked untill your sure that your device is capable of using those kind of voltages. And don't use very large steps. Just like overclocking in fact! Try it - it runs - get a little bit lower. If it crashes you shoukd be able to reboot the nexus and the settings you've changed reseted
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! Have you noticed any improvement in battery life?
Sent from my Nexus 7 using xda premium

Been testing for 2 days now! Battery seems a little bit better yet maybe placebo! But i feel it does not get has hot as runing stock voltages! It was the main reason i did the undervolt!
Sent from my Nexus 7 using Tapatalk 2

antmasi said:
Been testing for 2 days now! Battery seems a little bit better yet maybe placebo! But i feel it does not get has hot as runing stock voltages! It was the main reason i did the undervolt!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Placebo
Sent from my Nexus 7 using XDA Premium HD app

For what i've read that's the truth but if the frequencies set for the soc are getting less power shoudn't it draw less power from battery? 100mv its almost 10% of the stock voltages!
Sent from my Nexus 7 using Tapatalk 2

antmasi said:
For what i've read that's the truth but if the frequencies set for the soc are getting less power shoudn't it draw less power from battery? 100mv its almost 10% of the stock voltages!
Click to expand...
Click to collapse
For the SoC, whether it's leakage (V^2/R) or dynamic power dissipation (f*C*V^2), yes, you might expect let's say (0.9^2) = 81% battery use at the same operating frequencies.
OTOH, if 75% of the power drain normally is used by the LCD backlight (for instance in a "reading web pages" use case), then reducing the supply voltage will get you only 1/4 of that 20% savings - about a 5% improvement - because the power is being dissipated elsewhere. (Display, DRAM, 3G radio, WiFi radio, etc)

I agree with what you've pointed! In fact i've just taken out the undervolt because Inhad a reboot under heavy multitasking (torrent download, xbmc opened, chrome also downloading a smal file) i'm not certain that it was caused by the uv but it's possible. The Nexus started to lag and then froze completly! From time to tima i've the need of heavy multitask and it wasn't up to the task!
Sent from my Nexus 7 using Tapatalk 2

Annoying issue with core scaling...

I know many will probably just ignore this bug, but I can't because just knowing it's there is pestering. Anyway the GPU is not functioning properly ever since 4.2.2 . Its frequency isn't dynamic.
I would like if some volunteers with faux clock or another GPU reading app could confirm if they have the same issue on 4.2.2 .
Sent from my Nexus 4 using xda app-developers app

Default governor for GPU is ondemand, it's behaving properly.

meangreenie said:
Default governor for GPU is ondemand, it's behaving properly.
Click to expand...
Click to collapse
On demand doesn't entail a static frequency. Previously it would drop to 128 or 200 but now it sticks to 400... That is definitely not normal behavior for this governor. I only had faux clock open and I doubt that app would be GPU intensive.
And this is a problem for me because the the back is noticeably warmer than before despite me having a max of 1ghz and eco mode.
Sent from my Nexus 4 using xda app-developers app

Ah ok sorry, thought you meant it wasn't scaling through the frequencies on light loads.
Dunno may be it's using some kind of low power state instead, I'm using faux stock enhanced kernel and mine is cool at the back with just normal use, also getting great battery life.
Mine only gets hot with heavy gaming or by just browsing with 3g on.

meangreenie said:
Ah ok sorry, thought you meant it wasn't scaling through the frequencies on light loads.
Dunno may be it's using some kind of low power state instead, I'm using faux stock enhanced kernel and mine is cool at the back with just normal use, also getting great battery life.
Mine only gets hot with heavy gaming or by just browsing with 3g on.
Click to expand...
Click to collapse
My issue is that it sticks to 400 which is high state. The only time it changes is when I set it to 487, it'll switch between 487-->400 constantly. Something is triggering a load but these tests are on fresh installs. It's generating heat which isn't good for batteries, especially non removable.
All these issues with my nexus are seriously making me reconsider my purchase -_-
Sent from my Nexus 4 using xda app-developers app

Nexus 4 thermal throttling fix

The nexus 4 is definitely a great phone for a low price.But people are not buying this phone because of this THERMAL THROTTLING.so,people listen nexus 4 even runs smooth with thermal throttling going on.so, this fix is for people who just dont want thermal throttling.Before we start,this fix requires ROOT and a custom recovery.And a custom kernel needs to be flashed.so if you do any damage to your phone by doing this,I'm NOT RESPONSIBLE.
So first download the faux kernel for nexus 4(codename mako. if you see mako on faux website its for nexus 4) from here: Faux's website which i cannot post because im new to XDA. you can find it by googling for faux kernel website.I recommend the TBM kernels such as mako-jb-kernel 016 tbm which lets you overclock CPU to 1.83 Ghz.But theres also TBU kernels which support overclocking to 1.94 GHz.
Step 1 now download a faux kernel of your choice.
Step 2 paste the kernel to your mobile
Step 3 Boot into recovery mode
Step 4 Wipe cache
Step 5 Wipe dalvik cache
Step 6 Install .zip kernel
Step 7 Reboot your phone
Step 8 Now you have to buy the faux123 kernel enhancement program from play store(this app is from faux and this has intelli-thermal built in it)
Have fun.the faux app lets you select CPU frequencies also

What.
Sent from my Nexus 4 using Tapatalk 4 Beta

With his enhancement app yes you can control throttling but the problem is that because the phones CPU is getting way too hot, so increasing the throttle threshold or limit basically makes it so when your gaming, it makes things smoother however your CPU is burning faster.
Sent from my Nexus 4 using xda app-developers app

what is qualcomm's default throttling temperatures?

notbrodie said:
what is qualcomm's default throttling temperatures?
Click to expand...
Click to collapse
it throttles to 1.3 or sometimes to 1.2 ghz when temp is 37C and to 1.1 ghz when temp is 39C

XxLostSoulxX said:
With his enhancement app yes you can control throttling but the problem is that because the phones CPU is getting way too hot, so increasing the throttle threshold or limit basically makes it so when your gaming, it makes things smoother however your CPU is burning faster.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No it has a thermal manager which controls the heat.if it heats up it automatically turns off 1 or 2 cores so that means 2 cores wil still run normally but the other 2 cores will shutdown.
Understood??

NexusMobileGamer said:
No it has a thermal manager which controls the heat.if it heats up it automatically turns off 1 or 2 cores so that means 2 cores wil still run normally but the other 2 cores will shutdown.
Understood??
Click to expand...
Click to collapse
No **** why do you think it's turning off the cores? Because it's getting to hot
Sent from my Nexus 4 using xda app-developers app

meh.. you have root? disable throttling then, both battery and cpu throttle, then go on enjoying your device.

simms22 said:
meh.. you have root? disable throttling then, both battery and cpu throttle, then go on enjoying your device.
Click to expand...
Click to collapse
Meh then have a fried CPU over time itll kill it from getting way to damn hot.
Sent from my Nexus 4 using xda app-developers app

XxLostSoulxX said:
Meh then have a fried CPU over time itll kill it from getting way to damn hot.
Sent from my Nexus 4 using a app-developers app
Click to expand...
Click to collapse
i always turn off throttling, on every device i own(ed). they all live long lives, and are the best performers around(for their model). they never ever got damaged because of it, and im an extrely heavy user. my n4 has had all throttling disabled since jan 14th, and its still going strong. the difference is that i never complain that my phone turns down cpu speed, or does my phones performance get slowed down.

Just so you know
simms22 said:
i always turn off throttling, on every device i own(ed). they all live long lives, and are the best performers around(for their model). they never ever got damaged because of it, and im an extrely heavy user. my n4 has had all throttling disabled since jan 14th, and its still going strong. the difference is that i never complain that my phone turns down cpu speed, or does my phones performance get slowed down.
Click to expand...
Click to collapse
I agree with you.And who dont agree with me,just know that your CPU will not be burned.Cause Fauxclock has a thermal manager of its own named intelli thermal.

NexusMobileGamer said:
I agree with you.And who dont agree with me,just know that your CPU will not be burned.Cause Fauxclock has a thermal manager of its own named intelli thermal.
Click to expand...
Click to collapse
Yes, but if you disable it to have maximum performance clearly you're not throwing s*** , which in turn in the long run may burn your CPU
Sent from my Nexus 4 using xda app-developers app

XxLostSoulxX said:
Yes, but if you disable it to have maximum performance clearly you're not throwing s*** , which in turn in the long run may burn your CPU
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The nexus 4 throttling is caused by the battery reaching a certain temperature not the CPU. It's poor design/cooling system causes heat to build up which raises the temperature of the battery. Once it reaches a low 37 degrees the cpu/gpu are downclocked even if they are well within their limits.

spix123 said:
The nexus 4 throttling is caused by the battery reaching a certain temperature not the CPU. It's poor design/cooling system causes heat to build up which raises the temperature of the battery. Once it reaches a low 37 degrees the cpu/gpu are downclocked even if they are well within their limits.
Click to expand...
Click to collapse
the n4 has a battery temp throttle AND a cpu temp throttle.
i generally disable both the battery and cpu temp throttles, but leave both safety temps as is. for those that say "oh, the extra heat will eventually ruin the phone".. the temp doesnt get any hotter than it does when you normally use your phone, the difference is that you dont get throttled. and even if there was extra heat because of, im not planning on having my phone for the amount of time that the extra heat will take to ruin the phone(years).