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
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)
Ezekeel has created the ability for user control of cpu overclock and bus/gpu overclock. He has also made it possible to change the cpu and internal voltages, so that this can be done without sacrificing stability. Several awesome kernel developers have implemented his work. Thanks to all of you.
I have seen kernel development threads degenerate into "help me with my voltages" threads. No more!
Please post:
- Your kernel and version/date.
- Your live_oc value.
- Your dvsarm (cpu voltage) values.
- Your dvsint (internal voltage) values.
You can vote for settings you have found to be stable by thanking that post.
Default cpu / bus clock speeds
Trinity teuv:
5 steps:
100 200 400 800 880 MHz;
bus: 220 MHz
Trinity T144:
5 steps:
100 400 800 1000 1440 MHz;
bus: 240 MHz
franco:
5 steps:
100 200 400 800 1000 MHz
bus: 200 MHz
Please post the frequencies for your kernel of choice, so we can make this list complete.
Reserved for bacon.
PM simms if you want chocolate on it.
good idea!
btw, reserved for chocolate covered bacon. Mmm..
Reserved for:
Spank me Ezekeel!
I'll start:
Kernel: Always my latest kernels
live_oc: 110
dsvarm (cpu voltage): 1250, 1155, 1000, 900, 900
dsvint (internal voltage): stock
is it possible that my nexus dislike liveoc.
no matter which kernel (matrix/franco) + rom (markvis/superosr) combo i am on, 110% and 20 - 30ov
will freeze the phone
currently on
kernel: franco.kernel 0611
live_oc: 100
voltage: stock
Kernel: Franco 06november bfs
live_oc: 120
dsvarm (cpu voltage): 1285, 1190, 960, 835, 800
dsvint (internal voltage): stock
Sent from my Nexus S using Tapatalk
Go Go
250~1G freq with 250 bus/GPU speed! Cool~
- kernel and version/date : franco.Kernel 11/6
- live_oc value :125
(max freq :800 / min freq : 200)
- dsvarm (cpu voltage) values : 1250 1250 1080 950 950
- dsvint (internal voltage) values : 1100 1130 1130 1130 1000
#!/system/bin/sh
echo "1250 1250 1080 950 950" > /sys/class/misc/customvoltage/arm_volt
echo "1100 1130 1130 1130 1000" > /sys/class/misc/customvoltage/int_volt
echo "800000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "125" > /sys/class/misc/liveoc/oc_value
Click to expand...
Click to collapse
Kernel: Franco 06november bfs
live_oc: 110
Min_freq: 440
Max_freq:1100
dsvarm (cpu voltage): 1210, 1160, 1010, 900, 900
dsvint (internal voltage): stock
What's a good max arm volt to liveoc 110 on franco's 06
Ill go with stock on the ones I can control with set cpu
Cool update on nstools! Now can adjust voltages,that's why I ask lol...
Sent from my I9020T NSCOLLAB + FRANCO'S 06 BEAST LIVEOC 105
Kernel:Franco 6NOV CFS
LiveOC:110
dsvarm:1275 1200 925 800 775
The above settings seems to be stable on my phone but
may someone please teach me what to do when OC failure?
(I know how to clear CMOS on computers but don't know much on phones)
I use both NSTools and SetCPU to get LiveOC value of 120 and hang, after restart, the NSTools autoload 120 and hang again, it hang before I get access into the NSTools to change the value, what should I do?
---------- Post added at 03:12 PM ---------- Previous post was at 02:58 PM ----------
LKNim said:
Kernel:Franco 6NOV CFS
LiveOC:110
dsvarm:1275 1200 925 800 775
The above settings seems to be stable on my phone but
may someone please teach me what to do when OC failure?
(I know how to clear CMOS on computers but don't know much on phones)
I use both NSTools and SetCPU to get LiveOC value of 120 and hang, after restart, the NSTools autoload 120 and hang again, it hang before I get access into the NSTools to change the value, what should I do?
Click to expand...
Click to collapse
I got it solved by a brainless method
1.Flash TEUV kernel which doesn't support liveOC
2.Clear the data of NSTools
3.Back to franco kernel
4.Done
It's useful for those don't know much about command and init.d such as me
franciscofranco said:
I'll start:
Kernel: Always my latest kernels
live_oc: 110
dsvarm (cpu voltage): 1250, 1155, 1000, 900, 900
dsvint (internal voltage): stock
Click to expand...
Click to collapse
get reboot with this settings..
strange...
al_madd said:
get reboot with this settings..
strange...
Click to expand...
Click to collapse
It's not strange, you may understand this if you have overclocked your PC.
Different CPUs need different voltages to maintain stability.
You may try this
1275 1200 or even higher
There is no best voltage for every CPUs, you need to find it out yourself.
In my case
1100MHz need 1275mV
1000MHz need 1200mV
880MHz still need 1200mV...
800MHz need 1125mV
LKNim said:
It's not strange, you may understand this if you have overclocked your PC.
Different CPUs need different voltages to maintain stability.
You may try this
1275 1200 or even higher
There is no best voltage for every CPUs, you need to find it out yourself.
In my case
1100MHz need 1275mV
1000MHz need 1200mV
880MHz still need 1200mV...
800MHz need 1125mV
Click to expand...
Click to collapse
I think I am confused with stock voltage for internal voltage...
this one??
Nexus S stock voltages
1000mhz: 1250 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 950 mV
100mhz: 950 mV
Or this one??
1000mhz : 1100mV
800mhz :1100mV
400mhz :1100mV
200mhz :1100mV
because when change my intenal voltage with stock voltage....immediately hang and after that reboot
100mhz :1000mV
al_madd said:
get reboot with this settings..
strange...
Click to expand...
Click to collapse
with this settings i have no reboot
al_madd said:
with this internal voltage right???
Nexus S stock voltages
1000mhz: 1250 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 950 mV
100mhz: 950 mV
Click to expand...
Click to collapse
Isn't it 1250 1200 1050 950 950 the arm voltage
Stock int voltages are 1100 1100 1100 1100 1000
(I got these via NSTools before any changes)
With stock int voltages my phone works well
My settings for reference, NOW(STOCK)
Freq 1100(1000) 880(800) 440(400) 220(200) 110(100)
Arm 1275(1250) 1200(1200) 925(1050) 800(950) 775(950)
Int 1050(1100) 1050(1100) 1050(1100) 1050(1100) 900(1000)
It's better try it yourself, values copied from the others may not suit for you
LKNim said:
Isn't it 1250 1200 1050 950 950 the arm voltage
Stock int voltages are 1100 1100 1100 1100 1000
(I got these via NSTools before any changes)
With stock int voltages my phone works well
My settings for reference, NOW(STOCK)
Freq 1100(1000) 880(800) 440(400) 220(200) 110(100)
Arm 1275(1250) 1200(1200) 925(1050) 800(950) 775(950)
Int 1050(1100) 1050(1100) 1050(1100) 1050(1100) 900(1000)
It's better try it yourself, values copied from the others may not suit for you
Click to expand...
Click to collapse
Oh...sorry..because everyone says internal voltage using stock..I thought these value 1250 1200 1050 950 950...sorry..
yes..with 1100 1100 1100 1100 1000...My phone have no problems at all..thanx...
when i change the voltages in terminal emulator:
echo "1250 1200 1000 950 950" > /sys/class/misc/customvoltage/arm_volt
does the voltage change take place instantly or do i need to reboot?
Changes are instant. Rebooting will only reset you to stock values, if you don't have an init.d script for them.
You can check your changes after an echo by typing the following in Terminal:
Code:
cat /sys/class/misc/customvoltage/arm_volt
Hi @all,
everyone is invited to post
1. ROM
2. Kernel
3. Kernel settings
4. UV settings
independently of ROM or Kernel used.
It might be a good starting point to compare other user´s experience.
Before using the settings postet in this thread please keep in mind that each device is different. Good settings for device A might produce freezes on device B.
So share your and enjoy other´s experience´s ...
here are my stable settings:
ROM: CheckROM RevoHD v6
Kernel: N.E.A.K. 1.4x
CPU Gorvernor: conservative (with all tweaks over CWM recovery enabled)
I/O Sched: sio
200 Mhz - 1200 Mhz
Voltages:
100 Mhz - 850 mV (... can´t go lower for testing with voltage control )
200 Mhz - 850 mV (... can´t go lower for testing with voltage control )
500 Mhz - 875 mV
800 Mhz - 975 mV
1000 Mhz - 1075 mV
1200 Mhz - 1175 mv
GPU settings:
Low: 133 Mhz - 800 mV
High: 133 Mhz - 800 mV
I am not a gamer and this settings are solid stable for my device. I use the phone mainly for (heavy) phone call´s (I know its old fashion ) and @home for surfing via WIFI. I enable my mobile data connection only when I need it.
This setting´s give me 3 - 4 days battery life.
I use lulzactive governor and vr I/O sched before and I feel NO difference in performance compared with the above settings (regarding scrolling through menus, starting apps ...), but the above settings gives me better battery.
Regards
Antonio
Update: I have to mention that I have the 2000 mAh Samsung battery.
OROM: Stock 2.3.5
Kernel: N.E.A.K 1.3.3.x
Voltage controls: All default.
100-800mhz
Lulzactive, VR
I usually get 1 & a half days battery, with an average of 7 hours screen time. The phone still runs beautifully while playing games and such so I have no problems in that category.
Edit:
Wifi on 80% of the time, a few hours of XDA. Skype on 100% while wifi is on. A few hours of games (dolphin, mc3, cut the rope, etc.), hours of Internet browsing, etc.
Sent from my GT-I9100 using XDA
A last note:
Posting your settings and your battery charge cycle, please also mention the way you using your phone during the day to make your post more comparable ...
have fun
Voltages
Using Checkrom V6, lulzactive gov. NEAK Kernel
1200mhz @ 1150mV
1000 @ 1050
800 @ 975
500 @ 875
200 @ 850
100 @ 825 (min freq is 200mhz anyway, so this freq is not used at all)
Rock solid, never a kernel panic/crash
My battery last 2 days with push Exchange connectivity, gmail pushing too, some gaming (no more than 1h x day), 1h voice calls x day, normal texting activity (30-50 daily text messages) and automatic brightness customized to be darker than default.
Battery last longer if you do not let fully discharge it (plug it at night if you can, no matter the charge left).
@Floodland
I usually don´t let the battery go down below 15% - 20%, then I start a new charge ... I break this rule only in case on an emergency when no charger is near by me
I´ll try your 1000 MHz and 1200 MHz voltage setting´s, will post back if they work on my phone
ROM:Custom Made DXKL3
Kernel:SiyahKernel 2.6.13
Governor:SIO,ondemand
Voltages:
100 Mhz - 800 mV
200 Mhz - 850 mV
500 Mhz - 900 mV (default)
800 Mhz - 950 mV
1000 Mhz - 1050 mV
1200 Mhz - 1150 mv
1400 Mhz - 1250 mV
1600 Mhz - 1350 mV
GPU settings:
1: 133 Mhz - 800 mV
2: 266 Mhz - 950 mV
3: 400 Mhz - 1100mV
battery life around 2 days with light usage, 8 hours for heavy usage.
at present 44% after 32 hours, with 2:15 hours display on, wifi on, 3G off
ROM: All GB ROMs
KERNEL: Siyah, NEAK and Redpill
SCHEDULER: Usually I keep it unchaged
GOVERNOR: ondemand or conservative
FREQUENCY: 200MHz- 800 or 1000 or 1200MHz
UV:
-CPU
200MHz - 800 mV
500MHz - 850 mV
800MHz - 950 mV
1000MHz-1050mV
1200MHz-1150 mV
FYI, I always use this cpu uv settings from 6 months ago -- since the first time I got my SGS2 undervolted while using ninphetamine kernel, to be exact. It always stable on my SGS2.
GPU:
133 MHz - 800 MHz
267 MHz - 950 MHz
Sent from my GT-I9100 using xda premium
New voltages ...
Hi @all,
here are my settings after new tests. The stability was testet by three sequential cycles of the N.E.A.K tester in each (fix) frequency:
100 Mhz - 850 mV
200 Mhz - 850 mV
500 Mhz - 850 mV
800 Mhz - 950 mV
1000 Mhz - 1050 mV
1200 Mhz - 1150 mv
Will test in next bettery cycle if they are stable in daily use, and report. Fell quite secure cause i´m not a heavy user...
Will test the settings starting tomorrow with the new N.E.A.K 1.4.1x kernel (simone told in his thread that the kernel should be released this afternoon).
ROM: Fatal1ty Extreme Edition (XWLA4)
Kernel: Red Pill 1.3
CPU Gorvernor: conservative
I/O Sched: sio
200 Mhz - 1200 Mhz
Voltages:
100 Mhz - 825 mV (Stable but not in use as it tends to lag a bit)
200 Mhz - 825 mV
500 Mhz - 875 mV
800 Mhz - 950 mV
1000 Mhz - 1025 mV
1200 Mhz - 1125 mv
1400 Mhz - 1225 mv (Stable but not in use as don't need it)
1500 Mhz - 1350 mv (Stable but not in use as don't need it)
GPU settings:
Low: 114 Mhz - 800 mV
High: 267 Mhz - 950 mV
I have 2 Exchange accounts on push, Gmail Push, hotmail every hour, and moderate use. Screen time Usually between 2-4 hours. Used to get 2 days, but getting epic wakelocks from google services since the Google Play update. so im trying work that out. at the moment of about 14 hours i have 2hours screen time and 34% battery left.
Red pill rules
ROM: Checkrom revo hd V6 (XWLA4)
Kernel: Red Pill 1.3
CPU Gorvernor: Hyper
I/O Sched: N/A
200 Mhz - 1200 Mhz
Voltages:
100 Mhz - 900 mV
200 Mhz - 900 mV
500 Mhz - 950 mV
800 Mhz - 1000 mV
1000 Mhz - 1100 mV
1200 Mhz - 1200 mv
1400 Mhz - N/A
1500 Mhz - N/A
I USED THE KERNEL Neak BUT I'll take the RED PILL IS SIMPLY THE BEST BUT THE BEST OF SIYAH MORE FLUID AND ENHANCED THIS LAST
TWO CORES ARE ENABLED
did a test for each freq and volt with STABILITY TEST app.
ROM: cognition 1.51
Kernel: Siyah 2.6.14
I/O Schrduler: sio
CPU Gorvernor: smartassV2
CPU:
100 Mhz - 1600 Mhz
Voltages:
100 Mhz - 850 mV
200 Mhz - 850 mV
500 Mhz - 875 mV
800 Mhz - 950 mV
1000 Mhz - 1050 mV
1200 Mhz - 1200 mv
1400 Mhz - 1275
1600 Mhz - 1400 mv
GPU:
100Mhz-800mv
267Mhz-950mV
normally working from 100mhz-800mhz.
i managed to get lower mv for the cpu and stable but it was the limit. so i added 25mv more for more stable results.
Who dares trying my extreme UV values ?
My UV stable table (Mhz/mA) :
1200 (1125) | 1000 (1025) | 800 (950) | 500 (850) | 200 (800) | 100 (800)
Noop + On demand.
Thanks to NEAK for its magic on my S2
ROM: CM9
Kernel: NEAK 2.0.2x
I/O Schrduler: vr
CPU Gorvernor: ondemand
CPU:
200 Mhz - 1000 Mhz
Voltages:
200 Mhz - 850 mV
500 Mhz - 900 mV
800 Mhz - 950 mV
1000 Mhz - 1050 mV
GPU:
133Mhz-800mv
166Mhz-800mV
Works perfect for me. Always heavy usage and get nearly 24hours with standard battery. Screen on time 4 hours. With siyah I had nearly the half of the uptime.
Wifi always on. Sync on. I mean this is what it was made for
-sent from sgs2 tapatalk
HI
since in ICS firmwares we can talk about different cpu voltages than gb and i think it's a hot subject mostly in kernel threads i believe i can start this thread because many are interested about this. i use speedmod kernel k3-7 and i can use only tegrak overclock ultimate to change voltages. my stable config is:
200 mhz- 825 mv
500 mhz-925 mv
800 mhz-975 mv
1000 mhz-1050 mv
1200 mhz-1150 mv
with this config i get no freeze or sod. so please post your stable config too.
new info:
-seems that i can't go below 925 mv at 500 mhz
-i will see how the battery life will go with these voltages and i will post some pictures because i am interested in undervolting for battery life.
i also saw a post in neak ics kernel where a user had 7 h and 32 minutes display time.
pissyhun said:
HI
since in ICS firmwares we can talk about different cpu voltages than gb and i think it's a hot subject mostly in kernel threads i believe i can start this thread because many are interested about this. i use speedmod kernel k3-7 and i can use only tegrak overclock ultimate to change voltages. my stable config is:
200 mhz- 825 mv
500 mhz-925 mv
800 mhz-975 mv
1000 mhz-1050 mv
1200 mhz-1125 mv
with this config i get no freeze or sod. so please post your stable config too.
Click to expand...
Click to collapse
What were your gb values?
Sent from my GT-I9100 using Tapatalk
Yes, I don't see the values changing with ICS.
I should pay some more time on it... 825mV for 200MHz so amazing
hi
it seems if i go down 925 mV for 500 mhz i got freeze.
Hrithan2020 said:
What were your gb values?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
hi
theese were my values in gb roms:
1200mhz - 1150mv (stock = 1250mv)
1000mhz - 1050mv (stock = 1150mv)
800mhz - 950mv (stock = 1050mv)
500mhz - 875mv (stock = 975mv)
200mhz - 850mv (stock = 975mv)
and i used phenomenal 4.0 extreme without freeze or sod.
my phone was produced in octomber 2011.
pissyhun said:
hi
theese were my values in gb roms:
1200mhz - 1150mv (stock = 1250mv)
1000mhz - 1050mv (stock = 1150mv)
800mhz - 950mv (stock = 1050mv)
500mhz - 875mv (stock = 975mv)
200mhz - 850mv (stock = 975mv)
and i used phenomenal 4.0 extreme without freeze or sod.
my phone was produced in octomber 2011.
Click to expand...
Click to collapse
Strange.. Are you sure, that you had set the lowest possible values for GB?
For me, it looks as if I would have to increase the voltages a bit in ICS.
Haven't looked too much into it.. [running CM9 with Siyah rc3.. both beta.. need work]
GB voltage:
1200 MHz - 1150 mv
1000 MHz - 1050 mv
800 MHz - 950 mv
500 MHz - 850 mv
200 MHz - 800 mv
Always stable for me. I always use this voltage settings until I update my phone into ICS.
ICS voltage:
1200 MHz - 1150 mv
1000 MHz - 1050 mv
800 MHz - 950 mv
500 MHz - 925 mv
200 MHz - 800 mv
It seems I can't set the voltage for 500 MHz lower anymore. Otherwise the phone will freeze.
Sent from my GT-I9100 using xda premium
so far so good.
they seem to be working for me as well.
using Siyah latest kernel and Hydrog3n rom.
hi
some users reported theese voltages to be stable:
200-800 mv
500 - 925 mv
800 - 950 mv
1000 - 1050 mv
1200 - 1125 mV
pissyhun said:
hi
it seems if i go down 925 mV for 500 mhz i got freeze.
Click to expand...
Click to collapse
Hahaha, Are you really sure ?
Who dares trying my extreme UV values ?
My UV stable table (Mhz/mA) :
1200 (1125) | 1000 (1025) | 800 (950) | 500 (900) | 200 (800) | 100 (800)
Noop + On demand.
Thanks to NEAK for its magic on my S2
Hi
Changed kernel-neak and i use now
850 900 950 1025 1125 mv
Sent from my GT-I9100 using XDA
well this are my settings:
Min/max: 100 mHz-1200mHz
vr - smartassV2
100 - 825
200 - 875
500 - 925
800 - 975
1000 - 1050
1200 - 1150
Siyah 3.0
i tryied to go a lil bit under this settings, but then i had some freezes. i think 500 and 800 makes the most problems.
on ics i have to pull up a bit the voltages that were stable for me on gb, but the annoying thing is that i can´t go less than 925mv for 500mhz step, i get freezes and on gb i was on 875
I'm running 200Mhz 775mV stable
800Mhz 925mV
But cant get stable at 1600Mhz, I get freeze on anything between 1325-1500mV
Anyone can?
This thread is kind of useless .. every phone supports different UV !
Sent from my GT-I9100 using xda premium
I dont think so
Sent from my GT-I9100 using XDA
i am confused cause all tht magic an other tweaks really dint work for me,i tried all but sometimes the phone runs jus for few mins and right now my phone is fully loaded like 400+apps an iam downloading more day by day too check how much sgs2 will handle.an yes i think every phone is diff...
Jodelaplaya said:
This thread is kind of useless .. every phone supports different UV !
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
pissyhun said:
I dont think so
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Well, each phone has different tolerance to Undervolting. I for example can not go lower then these values:
200MHz - 900/925mV
500MHz - 950/975mV
800MHz - 1050mV
1000MHz - 1100-1150mV
1200MHz - 1250mV
If I go lower then 1250mV for 1200MHz, I will get freezes (if not instant then when browsing the net or something heavy). As you can see my values are not so "extreme", other people can undervolt much more.
There has been one succesfull thread of this type from Geko, it's called MagicConifg (if you click on Undervolting in my signature you will be taken there). He tested for months which UV settings would work for 99% of the people. I was one of the few people that couldn't handle his config
Anyway, I don't say that this thread is totally useless. Discussing UV settings can be helpfull for others which are new to Undervolting. But for me the UV settings have stayed the same as on GB, don't know if it's so different UV'ing on GB and on ICS.
As long as people realise: the settings that work for somebody may not work on your own phone! A lot of people in this thread undervolt heavy and there is a big chance your own phone will freeze (and if you set it on boot and can't remove them anymore, that means reflashing your rom...). So be carefull
Cm9 rom/kernal
200 @ not used
500 @ 825 mV
800 @ 950 mV
1000 @ 1050 mV
1200 @ 1150 mV
I have read very conflicting things about undervolting; some say it doesn't do much at all, others say it's worth the effort. What most can agree on though, is that it depends on the phone, so I want to get some input to see if people have had success with it on the Fascinate. I tried a mild undervolt today and while I didn't notice much change with the screen on (while using it) I did notice it held a lot better charge while in stand-by. My settings as of right now are:
1200 MHz - 1300mV (-50)
1000 MHz - 1225mV (-50)
800 MHz - 1150mV (-50)
400 MHz - 950mV (-100)
200 MHz - 850mV (-100)
100 MHz - 850mV (-100)
I have been running the over / under volts for a while on different test builds with really good results...
I did do a live o/c for a while but have settled on normal o/c
My over / under settings as of right now are:
1200 mhz O/C
100 mhz minimum
1200 MHz - 1400mV (+50)
1000 MHz - 1325mV (+50)
800 MHz - 1250mV (+50)
400 MHz - 1025mV (-25)
200 MHz - 900mV (-50)
100 MHz - 875mV (-75)
------------------------
------------------------
But i have been wanting to test some other stuff too
I figured i would test this::
And see how it runs
1200 MHz - 1350mV (+00)
1000 MHz - 1275mV (+00)
800 MHz - 1200mV (+00)
400 MHz - 1000mV (-50)
200 MHz - 850mV (-100)
100 MHz - 850mV (-100)
sent from my swagger
aokp 10/22 test / devil kernel
Just curious, but what was your reasoning to raise the voltage? It seems like that would just be a battery drain because at those steps the stock voltage should be more than enough for stability.
I also don't Live OC but that's only because my phone will crash at 110% Live OC so I don't see the point in doing 105% Live OC... so I just do what you do and have 1200 MHz regular OC now
Crawshayi said:
Just curious, but what was your reasoning to raise the voltage? It seems like that would just be a battery drain because at those steps the stock voltage should be more than enough for stability.
I also don't Live OC but that's only because my phone will crash at 110% Live OC so I don't see the point in doing 105% Live OC... so I just do what you do and have 1200 MHz regular OC now
Click to expand...
Click to collapse
Just came from all the reading in the original devil ics thread...
Somebody 'Crack' ran these settings...
http://forum.xda-developers.com/showthread.php?t=1699141
It has so many great answers and Such great info,,, just realized i need to go back and read some more,,,
Think ... devil idle .... :thumbup:
sent from my swagger
aokp 10/22 test / devil kernel
From all the roms/kernels I ever ran on my fascinate undervolting did help slightly. It seems if I remember correctly that pulling -50uv across the board helped with battery life without decreasing stability. Anymore than that is when the random reboots started. Also disabling the 100mhz step made a big difference with SOD's and reboots.
Crawshayi said:
Just curious, but what was your reasoning to raise the voltage? It seems like that would just be a battery drain because at those steps the stock voltage should be more than enough for stability.
I also don't Live OC but that's only because my phone will crash at 110% Live OC so I don't see the point in doing 105% Live OC... so I just do what you do and have 1200 MHz regular OC now
Click to expand...
Click to collapse
You can do both a live oc (fsb overclock), and a regular overclock (multiplier overclock) at the same time. I use 110 live oc and a 200 mhz regular overclock giving me a total of 1320mhz. Set your live oc then use rom controlor whatever to do your regular overclock on top of it.