Related
This thread has been created to share Undervolting Settings (UV).
Undervolting makes CPU/GPU/Modem to consume less power, thus extend battery life. This is allowed by flashing modified kernels that allow UV (Thanks to raspdeep's work). One can use Voltage Control to change settings (Thanks to xan).
Setting format is -x mV for a given CPU clock as used in xan's app: [1200Mhz] [1000Mhz] [800Mhz] [400Mhz] [200Mhz] [100Mhz]
What are your settings?
PS: Please edit your very first post with settings instead of reposting. Thank you!
Stable: 50 50 75 100 100 100
1200 max: 50
1000 max: 50
800 max: 75
I am currently running 50 50 50 75 100 100 with no stability problems. It has made 4 back-to-back quadrant runs and a couple days of general usage without any crashes so far.
Undervolting doesn't work well with my phone the same with overclocking. I can't undervolt 1000Mhz and above because it causes much stability issues here. I can only undervolt 100-800Mhz with settings < 100mV.
TheVisitorX said:
Undervolting doesn't work well with my phone the same with overclocking. I can't undervolt 1000Mhz and above because it causes much stability issues here. I can only undervolt 100-800Mhz with settings < 100mV.
Click to expand...
Click to collapse
My system hangs in sleep mode when I have setCPU or Superpower with sidekick on.
I have the max cpu capped at 800mhz using SetCpu.
Undervolted -50 for 800mhz 600 400 200 and 100 each.Phone was at 50% last night and 6 hours later it's dead.Battery was completely discharged.All i did was set everything at 50Mvs less.Correct ? i think i'm missing something.Do help.thanks.
hey guys
im new to oc and uv
im currenlty using ramads gb jvh with hardcores speedmod kernel
ive got tegraks ultimate app and have oc'd it to 1100 as anything above reboots my phone
everything else is the same as standard
i was wondering if anyone else can help me with what i should change
i have no clue,
so far
frequency 1100
core 1275mv
internel 1100
cpu level 1
frequency 800
core 1200
internel 1100
cpu level 2
frequency 400
core 1050
internal 1100
cpu level 3
frequency 200
core 950
internal 1100
cpu level 4
frequency 100
core 950
internal 1000
these values are all stock, i havent touched them
im wanting to know what i should change them to
thanks
forgot to add, my battery life is really bad, i use hsdpa and wifi frequently
i have cm7 #19 with the (latest) glitch v10b-VC kernel..no oc, bu uv
100mhz -50,200mhz -50,400mhz -50, 800mhz -25 and 1000mhz @stock
What is the negative effects of UV?
My current values starting at 1000mhz is:
-75
-100
-100
-125
-175
hackeron said:
What is the negative effects of UV?
My current values starting at 1000mhz is:
-75
-100
-100
-125
-175
Click to expand...
Click to collapse
Negative effects come in the form of stability issues and random reboots. Is doesn't physically damage the processor. By lowering the core voltage supplied to the CPU, you also decrease the noise margin for the CPU to properly differentiate between logic 1 and logic 0. This is why -75, for example, works for some and not for others because processors are not 100% identical. The obvious benefit UV is lower power consumption.
gtda said:
hey guys
im new to oc and uv
im currenlty using ramads gb jvh with hardcores speedmod kernel
ive got tegraks ultimate app and have oc'd it to 1100 as anything above reboots my phone
everything else is the same as standard
i was wondering if anyone else can help me with what i should change
i have no clue,
so far
frequency 1100
core 1275mv
internel 1100
cpu level 1
frequency 800
core 1200
internel 1100
cpu level 2
frequency 400
core 1050
internal 1100
cpu level 3
frequency 200
core 950
internal 1100
cpu level 4
frequency 100
core 950
internal 1000
these values are all stock, i havent touched them
im wanting to know what i should change them to
thanks
forgot to add, my battery life is really bad, i use hsdpa and wifi frequently
Click to expand...
Click to collapse
I'm also using Tegrak's overclock apk for some time now (from beginning) and it's really good!
Just lower the core voltage (start with cpu level 0) until it's unstable (random reboots), then add a few mv (+5) to make it stable again (no reboots). do this for every core frequency (only one at the time, so you know witch one is making the system unstable). I never touch the internal frequency... Undervolting will NOT damage your CPU (overclocking can if you're not carefull)
Don't be stupid testing just a few hours, test (stress test) for days. Only then you are sure it's stable
These are my settings:
(rock stable after a few weeks => playing asphalt6, running quadrant and smartbench hours a day for a few weeks,...)
cpu level 0
frequency 1000
core 1205mv (-70) => could get it stable at 1200 but had one reboot after one week, so I added +5
internel 1100
cpu level 1
frequency 800
core 1105 (-95) => could get it stable at 1100 but had one reboot after one week, so I added +5
internel 1100
cpu level 2
frequency 400
core 950 (-100)
internal 1100
cpu level 3
frequency 200
core 825 (-125)
internal 1100
cpu level 4
frequency 100
core 825 (-125)
internal 1100
Now I know what my lowest core voltage is, I can start overclocking (not for now).
I'm on stock deodexed JVP 2.3.4 with Hardcore (latest) Speedmod (partition EXT4), Tegrack Overclock Ultimate and Voodoo Control Plus (holy combo => Quadrant 2400+ (no OC, just UV) and wow, what a great battery life!
edit: yes, I need to update my signature
SamHaLeKe said:
cpu level 4
frequency 100
core 825 (-125)
internal 1100
Click to expand...
Click to collapse
^ Typo??????????
internal voltage @ 100Mhz is 1000mV by default, so you are overvolting.
kiwijunglist said:
^ Typo??????????
internal voltage @ 100Mhz is 1000mV by default, so you are overvolting.
Click to expand...
Click to collapse
Default value is 950mV on my phone according to pimpmycpu. According to SamHaLeKe's post, he's reducing his by -125 so 825mV is correct
I'm new to UV, and just experimenting. My current values are
1200 = -50mV
800 = -50mV
400 = -100mV
200 = -100mV
100 = -150mV
Seems ok so far, more aggressive cutting gave me reboots
$$$
The most i could get from my phone w/o stability issues
1500 - 50
1400 - 50
1300 - 50
1200 - 50
1000 - 50
800 - 75
400 - 100
200 - 125
100 - 150
Starting from 1000MHz, I'm using these values :
-50 [1000]
-75 [800]
-100 [400]
-125 [200]
-150 [100]
No stability issues since then !
Mine are;
1000 : 50
800 : 50
400 : 75
200 : 75
100 : 100
Works great for me
Sent from my GT-I9000 using Tapatalk
swaakx said:
Starting from 1000MHz, I'm using these values :
-50 [1000]
-75 [800]
-100 [400]
-125 [200]
-150 [100]
No stability issues since then !
Click to expand...
Click to collapse
i have the same!
my phone now cold as ice. and greatly stable
I'm a noob at this UV stuff but I'm quite interesting about that.
I tried with Control Freak, should I set first a low voltage on 100Mhz and try to stress the cpu only with this change on 100MHZ? or should I set all voltages and test?
thx for help
i'm on jvq darkyrom
using tegrak overclock ultimate
1200mhz 1255 (-20)
800mhz 1105 (-95)
400mhz 950 (-100)
200mhz 850 (-100)
100mhz 810 (-140)
Mhz vs Quadscore on [beta] desire hd2 #Update
hey here same interesting tests i did
if i locked my phone in power saving mode u get
CPU and Score
Mhz ScoreA CPU Mem IOps Linpack
256Mhz 900 1750 525 1600 11
384Mhz 1050 2580 618 2000 16
460Mhz 1350 3000 990 2600 19
500Mhz 1600 3250 1050 2800 20
768Mhz 2200 4600 1120 3500 29
1000Mhz 2500 5400 1120 4150 35.5
1200Mhz 2700 6200 1120 4380 40
maybe there could be another mode that will use
500mhz most of the time [for normal using or one app using Cpu]
and when playing or using heavy 1000Mhz
[Dev]
i see that memory score is not linear
maybe could fixed by our greatest devers
I hope u do understand that these results are total bullcrap.
The newest dual core chips dont even get 2.7k scores in that benchmark.
Something in the desire HD build farks up the scores simple as that.
If you look at the quadrant advanced score, you'll notice it only gets those scores because of the I/O score. The processor one is about the same or a little more than teh Nexux 2.2, so if you underclock to 500 mhz you may get a total of 1600, but your processor score will suck badly and your phone will lag and really suck.
Keep your max at 998 and your min at 245 and use smartass and you should be fine.
orangekid said:
If you look at the quadrant advanced score, you'll notice it only gets those scores because of the I/O score. The processor one is about the same or a little more than teh Nexux 2.2, so if you underclock to 500 mhz you may get a total of 1600mhz, but your processor score will suck badly and your phone will lag and really suck.
Keep your max at 998 and your min at 245 and use smartass and you should be fine.
Click to expand...
Click to collapse
Agree.
Sent from my HTC HD2
orangekid said:
Keep your max at 998 and your min at 245 and use smartass and you should be fine.
Click to expand...
Click to collapse
+1 for this.
My HD2 has been running smoothly with 245-998MHz smartass for weeks now, battery life has been great too.
i update it with more info check post1
i see that memory score is not linear
maybe could fixed by our greatest devers
Quadrant scores are useless. RUn it, then run it again, you'll get different results.
I don't use SetCPU at all, it's just not needed.
According to my Quad Test im getting a total of 2196 with 245-998mhz with smartass on SetCPU my CPU: 4450 Mem: 1127 I/O: 4716 2D: 273 3D: 412 Work that one out
I know many of us have been trying to put together a working set of voltage settings for OC'ed kernels that works.
I also know that all hardware is not created equally, so this thread is meant to help with those users trying this for the first time as well as give people playing around with the settings a place to keep their data.
Please post a response in this format:
Kernel:
Scheduler: (scheduler is the top left option in Voltage Control)
Batch: (the batch number is listed behind the battery)
OC/UV Settings:
1600 - 175
1500 - 175
etc
Please post any commentary on your settings in the bottom of your post.
If you get a shutdown or freeze because of your settings, please edit your post to put the new settings.
***Also, please do not fill up this thread with questions. I would like this to be a repository of OC/UV settings only.***
Mods, if this is not the appropriate forum for this information, I apologize.
Kernel: CogKernel 4
Scheduler: CFQ
Batch:1007
1200 - 50*
1120 - 50*
1000 - 0
900 - 100
800 - 100
600 - 100
400 - 100
200 - 100
100 - 100
*- previous setting of 175 crashed after several hours. now trying 50
You may also want to know what kernel and scheduler are being used. I've had issues (sleep of death) with bfq, but noop seems to be great.
kernel - SetiroN 1.4.7 1200
scheduler - noop
batch - 1007
1200 - 125
1000 - 125
800 - 125
400 - 125
200 - 125
100 - 125
ooh great idea, maybe also include the kernel you are using atm, and if possible the phone batch number?
SetiroN's 1.4.6
batch 10.11
Scheduler: noop
OC/UV settings
1200 - 125
1000 - 100
800 - 125
400 - 150
200 - 150
100 - 200
there is rare freezes on android.core with this setup, but its not a big problem, and battery life is really good so this is my usual setup
Kernel: CogKernel 4
Scheduler: CFQ
Batch: 1007
Voltage Settings:
1600
1500
1400 (-175)*
1300 (-175)
1200 (-150)
1120 (-150)
1000 (0)
900 (0)
800 (0)
600 (0)
400 (0)
200 (0)
100 (0)
* - current running and stable
SetiroN kernel 1.4.3
Scheduler: noop
Batch: 1007
OC/UV settings
1280 - 50
1000 - 50
800 - 75
400 - 100
200 - 100
100 - 125
Stable, no freezes, no charger death. Afraid to mess with it. I lose about 2% (total, not per hour) battery overnight (6-7 hours).
Kernel: CogKernel 4
Scheduler: CFQ
Batch: 1006 (is it old enough to be a classic?)
Voltage Settings:
*edit set 1300 to 150 (175 freezes, 125 freezes) and it seems to be working
1200 -100
1120 -100
1000 -100
900 -100
800 -100
600 -100
400 -100
200 -100
100 -100
1300 is running stable with above settings
1200 works with settings in black very stable
designgears said:
Kernel: CogKernel 4
Scheduler: CFQ
Batch: 1007
Voltage Settings:
1600
1500
1400 (-175)*
1300 (-175)
1200 (-150)
1120 (-150)
1000 (0)
900 (0)
800 (0)
600 (0)
400 (0)
200 (0)
100 (0)
* - current running and stable
Click to expand...
Click to collapse
what cpu??
Kernel: SetiroN 1.5.4 XT 1600MHz
Scheduler: BFQ
Batch: 1007
OC/UV Settings:
1600 - 75*
1552 - 75*
1504 - 0
1464 - 75*
1456 - 0
1400 - 0
1344 - 0
1288 - 50*
1200 - 50*
1000 - 0
800 - 0
400 - 0
200 - 0
100 - 0
*STABLE
godzulu said:
what cpu??
Click to expand...
Click to collapse
set at 1300 cpu
settings in signature. So far, so good
Hey great thread...one Q where to look for batch number??
Underneath your battery is the batch number.
Kernel: Setiron 1.4.3
Scheduler: NOOP
Batch: 1008
OC/UV Settings: 1280 - 25
1000 - 25
800 - 50
400 - 75
200 - 75
100 - 75
Updated voltage control app to get settings to stick on boot. Other than that no problems whatsoever and running stable and flawlessly.
What does the scheduler and batch number signify?
Edit: only asking because I know others will be asking the same thing
Sent from my SAMSUNG-SGH-I897 using XDA App
Kernel: Setiron 1.4.4
Scheduler: BFQ
OC/UV Settings:
1300 - 25
1000 - 50
800 - 75
400 - 100
200 - 100
100 - 100
Voltages stick on boot. Didn't have to make any changes to the generated script. All I did was mount system as R/w first and then save the voltages settings from the voltage app.
Very stable, no FCs since I flashed...about 4 days ago.
ninjuh said:
What does the scheduler and batch number signify?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Batch number signifies what batch your phone was created in. Much like Sony and Microsoft use numbers with their consoles to indicate what hardware may reside in the chassis or what time period they were manufactured under, mobile phones, or much any electronic device that is released in cycles, follows the same principle.
As for the scheduler, a scheduler in terms of processing is in lamens terms...Processes waiting to be executed in your memory are allocated to the CPU by the scheduler. It selects the next operation to get executed from the RAM, basically. Operating Systems are processes in themselves, so there has to be a medium to make sure the operating system and application processes play nicely together. That's not all there is to it, the scheduler means a lot for I/O[input/output] operations as well, but we're keeping it lamen.
In a nutshell, it's the middle aged Nanny that lives inside your processor. It makes sure everything is clean, runs time efficiently [nannies are usually paid by the hour], and it makes sure none of the kids rough-house or make a mess. Done.
By the way, OP says no questions. I answered it because I'm obviously one of the coolest, nicest guys around, but let's keep it to a minimum and stay on track!
Kernel: CogKernel4
Scheduler: CFQ
Batch: 1006
I set max at 1300 now, since 1400 froze, but ONLY on 3d intensive stuff.
1600, -0
1500, -0
1400, -175 when in use
1300, -150
1200, -100
1120, -75
1000, -50
joeybear23 said:
Kernel: CogKernel 4
Scheduler: CFQ
Batch:1007
1200 - 175
1120 - 150
1000 - 0
900 - 0
800 - 0
600 - 0
400 - 0
200 - 0
100 - 0
This is working for me, but I want to run it for a few days to see if I get any freezes, etc before moving up to higher speeds.
Click to expand...
Click to collapse
Ok....when I see things like this, I'm just...baffled.
A.) Why you only undervolt the very high frequencies that your phone rarely uses? You phone spends most of the time at lower frequencies. Open setCPU go to info, and check time in state. You'll have almost always a 10:1 ratio of time at 100MHz to 1000MHz. You save a lot more battery by undervolting the lower frequencies where your CPU spends more time.
B.) I'm really skeptical of undervolting by 150 and 175MHz at those frequencies. On *stock* voltages, I haven't seen anyone get past 100mV at 1000MHz, but you're -150 at 1120, and -1-freaking-75 at 1200MHz?! If the kernel you're using OVERVOLTS the frequencies (which laststufo had been doing as well) that's about the only way I could imagine you could appear to be undervolting by 175mV @ 1200MHz. Ie, xan's app (last I knew) calculated the UV by the stock voltage, so if the voltage was raised in the kernel, it would look like you're undervolting by 175 when it might only be 100 or 75. Something the whoever you got your kernel from should let people know so they can make informed decisions about whether or not they want to overvolt their CPU.
Kernel: CogKernel 4
Scheduler: CFQ
Batch:1007
1200 - 50
1120 - 50
1000 - 50
900 - 50
800 - 75
600 - 50
400 - 75
200 - 125
100 - 125
Kernel: CogKernel 4
Scheduler: Noop
Batch: 1008
1200 - 0
1120 - 0
1000 - 0
900 - 0
800 - 0
600 - 0
400 - 0
200 - 0
100 - 0
Seems stable. Anything over 1200 on the drop down list instantly freezes, though. :/ I can't see any of these devices running 1.6 anywhere near stable, tbh.
Kernel: glitterballs' CM reoriented
Scheduler: Noop
Batch: 1010
1200 - 100
1000 - 100
800 - 100
400 - 125
200 - 125
100 - 125
Is there a stable 1.3Ghz OC kernel because i tried FuguMod 2.2 BE but my phone overheated.
RafayelG said:
Is there a stable 1.3Ghz OC kernel because i tried FuguMod 2.2 BE but my phone overheated.
Click to expand...
Click to collapse
Except 2.2 FuguMod, No
Maybe you kept 1.3Ghz continously...
Try using OnDemand or Conservative Scaling and profiles of screen off and stuff..
dharamg3 said:
Except 2.2 FuguMod, No
Maybe you kept 1.3Ghz continously...
Try using OnDemand or Conservative Scaling and profiles of screen off and stuff..
Click to expand...
Click to collapse
i just saw one at Kyrillos' Rom Here changelog of V5.0 and 4.1 but i can't find them on Marcellusbe's thread
RafayelG said:
i just saw one at Kyrillos' Rom Here changelog of V5.0 and 4.1 but i can't find them on Marcellusbe's thread
Click to expand...
Click to collapse
Ohh...those 1300MHz are Alpha kernels and full of bugs..
I've tested it...and i tell you, you dont want those...
better to try using Profiles of SetCPU with 2.2BE
dharamg3 said:
Ohh...those 1300MHz are Alpha kernels and full of bugs..
I've tested it...and i tell you, you dont want those...
better to try using Profiles of SetCPU with 2.2BE
Click to expand...
Click to collapse
do you got any sugestions for profiles?
SetCPU:
1) Max: 1300 Min: 166 Scaling: Ondemand Set on Boot:Tick
2) Profiles: Enable
Battery < 50% Max:667 Min:166 Scaling: Ondemand Priority: 80
Screen Off Max:222 Min:166 Scaling: Ondemand Priorty: 100
Time(Set the time when you are usually asleep) Max: 333 Min: 166 Scaling: Ondemand Priority: 90
3) Advanced: Set on boot
Up Threshold: 90
PowerSave Bias: 400
dharamg3 said:
SetCPU:
1) Max: 1300 Min: 166 Scaling: Ondemand Set on Boot:Tick
2) Profiles: Enable
Battery < 50% Max:667 Min:166 Scaling: Ondemand Priority: 80
Screen Off Max:222 Min:166 Scaling: Ondemand Priorty: 100
Time(Set the time when you are usually asleep) Max: 333 Min: 166 Scaling: Ondemand Priority: 90
3) Advanced: Set on boot
Up Threshold: 90
PowerSave Bias: 400
Click to expand...
Click to collapse
trying it now will report tomorrow
Just thought I should share this info.. I've literally tried every combination of everything and after a few days I've settled for this combination..
Best of performance and battery life Ive ever used.
I've searched everything everywhere and this beats everything recommended.
rom: slimics 4.0
lcd density: 200
theme: cobalt
launcher: apex launcher pro
kernel: matr1x cfs 20.0
nstools settings
-----------------
io scheduler: sio
governor: smartassv2
min cpu: 100MHz
max cpu: 1300MHz
deep idle: on
default voltage
smartassv2 settings:
awake ideal freq: 400000 Hz
sleep ideal freq: 100000 Hz
sleep wakeup freq: 400000 Hz
min cpu load: 50 %
max cpu load: 85 %
ramp down step: 200000 Hz
ramp up step: 200000 Hz
down rate: 49000 us
up rate: 48000 us
well good for you, but every phone is different sooooooo dont hurt yourself patting your own back
Lots of people really digging slimics at the moment.
If I was to root I would try that rom for sure.
Sent from my Nexus S using XDA
ozkoidz said:
Just thought I should share this info.. I've literally tried every combination of everything and after a few days I've settled for this combination..
Best of performance and battery life Ive ever used.
I've searched everything everywhere and this beats everything recommended.
rom: slimics 4.0
lcd density: 200
theme: cobalt
launcher: apex launcher pro
kernel: matr1x cfs 20.0
nstools settings
-----------------
io scheduler: sio
governor: smartassv2
min cpu: 100MHz
max cpu: 1300MHz
deep idle: on
default voltage
smartassv2 settings:
awake ideal freq: 400000 Hz
sleep ideal freq: 100000 Hz
sleep wakeup freq: 400000 Hz
min cpu load: 50 %
max cpu load: 85 %
ramp down step: 200000 Hz
ramp up step: 200000 Hz
down rate: 49000 us
up rate: 48000 us
Click to expand...
Click to collapse
Cool story.
But smartassv2 != battery saving. It's a performance governor, not one meant to save battery.
So far I haven't found a ROM that's smoother or more responsive than... STOCK. I have to say this is the first time I am using the Stock ROM for sooo long. It's fast, responsive and it doesn't randomly reboot (uptime 1100+ hours).
+1 for Slim ROM!
It just keeps getting better and better.
Vs Nexus S 4G
polobunny said:
Cool story.
But smartassv2 != battery saving. It's a performance governor, not one meant to save battery.
Click to expand...
Click to collapse
Its battery saving with the smartassv2 settings I provided
ozkoidz said:
Its battery saving with the smartassv2 settings I provided
Click to expand...
Click to collapse
There's definitely better governors suited for battery savings though. Ondemand or conservative, for instance.
Lol. Just lol.
Sent from my Nexus S 4G using XDA
if youre only getting 8-9 hours with your setup - i dont think thats good at all....
ozkoidz said:
Just thought I should share this info.. I've literally tried every combination of everything and after a few days I've settled for this combination..
Best of performance and battery life Ive ever used.
I've searched everything everywhere and this beats everything recommended.
rom: slimics 4.0
lcd density: 200
theme: cobalt
launcher: apex launcher pro
kernel: matr1x cfs 20.0
nstools settings
-----------------
io scheduler: sio
governor: smartassv2
min cpu: 100MHz
max cpu: 1300MHz
deep idle: on
default voltage
smartassv2 settings:
awake ideal freq: 400000 Hz
sleep ideal freq: 100000 Hz
sleep wakeup freq: 400000 Hz
min cpu load: 50 %
max cpu load: 85 %
ramp down step: 200000 Hz
ramp up step: 200000 Hz
down rate: 49000 us
up rate: 48000 us
Click to expand...
Click to collapse
NOOP any better!!