Hey everyone, I figured we deserved to have this thread as I hadn't seen one yet. I'm forever trying to tweak and adjust my voltages on my NS4G and I just wanted to see what everyone else was running and with what degree of success.
List your ROM/Kernel combo and your OC/OV/UV settings!
Currently:
CodenameAndroid 1.4.0
Matr1x v17.5 cfs
1300/400 SavagedZen
Deep Idle on.
@1.3GHz - 1430mV
@1.2GHz - 1350mV
@1GHz - 1280mV
@800MHz - 1205mV
@400MHz - 1030mV
...Stability tests are ongoing.
Rom: MIUI 2.3.9 (ICS)
Kernel: Matrix 17.5
Live OC: 105
Min: 210
Max: 1050
Voltage: All stock voltages dropped by 25
Scheduler: Deadline
Deep Idle: On
The voltages being dropped immensely helps battery life. I get at least 12 hours with heavy use and about a day and a half with light use.
Sent from my Nexus S 4G using xda premium
Almost same..
http://forum.xda-developers.com/showthread.php?t=1335429
Undervolting doesn't actually help the battery :$.... Well by much anyways. If it does it will be like a 2% difference... Instability doesn't seem worth it for 2%
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged
309041291a said:
Undervolting doesn't actually help the battery :$.... Well by much anyways. If it does it will be like a 2% difference... Instability doesn't seem worth it for 2%
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged
Click to expand...
Click to collapse
I always doubted bedalus claims on the matter (and even communicated with him through PM).
Time permitting, I'd like to do some tests myself about undervolting, because I am pretty sure it has an impact.
Anyway, my settings are in my signature.
polobunny said:
For those interested, I spent the night yesterday testing out ARM voltages on my phone that were absolutely stable but hopefully under the stock ones to save more battery.
Had a look at morfic's git for a good idea, so thanks to him.
Might not work on your phone, so use at your own risk.
100MHz 875mv (75mv under stock)
200MHz 875mv (75mv under stock)
400MHz 900mv (150mv under stock)
800MHz 1125mv (75mv under stock)
1000MHz 1225mv (25mv under stock)
Click to expand...
Click to collapse
Some people have a problem with 400MHz at 900, 950mv seems good for anyone though.
AOKP milestone 4
mart1x cfs v18.0
both settings have been run for days without reboot
setting no.1
840/100 smartassv2 noop
selective liveoc 105
freq arm int
840 1075 950
400 950 950
200 850 950
100 850 900
setting no.2
1000/100 smartassv2 noop
freq arm int
1000 1150 1000
800 1050 950
400 950 950
200 850 950
100 850 900
lolokman said:
AOKP milestone 4
mart1x cfs v18.0
both settings have been run for days without reboot
setting no.1
840/100 smartassv2 noop
selective liveoc 105
freq arm int
840 1075 950
400 950 950
200 850 950
100 850 900
setting no.2
1000/100 smartassv2 noop
freq arm int
1000 1150 1000
800 1050 950
400 950 950
200 850 950
100 850 900
Click to expand...
Click to collapse
What's the battery like? And I believe the matrix kernel is already Undervolted by default.
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged
Just got over 1 day of battery dropping all stock voltages by 25.
Codename 1.5.5
Matr1x 18.0 cfs
1200/200 lazy
Sent from my GT-P7510 using XDA Premium HD app
gear.h34d.2012 said:
Just got over 1 day of battery dropping all stock voltages by 25.
Codename 1.5.5
Matr1x 18.0 cfs
1200/200 lazy
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
On-screen time? With a screen
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (110 - Noop)
v6 Supercharged
lolokman said:
AOKP milestone 4
mart1x cfs v18.0
both settings have been run for days without reboot
setting no.1
840/100 smartassv2 noop
selective liveoc 105
freq arm int
840 1075 950
400 950 950
200 850 950
100 850 900
setting no.2
1000/100 smartassv2 noop
freq arm int
1000 1150 1000
800 1050 950
400 950 950
200 850 950
100 850 900
Click to expand...
Click to collapse
Interestingly I'm able to undervolt quite a lot more than I've ever been able to using this smartassv2/ noop setup. I'm not sure what it is but anytime I'd try to under volt matrix v18 any below stock I'd get reboots but with this setup I'm close to the values you've set and it's been stable so far. Its not undervolted as heavily and I don't have liveoc enabled at the moment. I'm just enjoying the ability to under volt it to where it is at the moment.
Sent from my Nexus S using Tapatalk
Currently using Franco kernel 1.2 and I dropped the stock voltages by 50(I was feeling a bit adventurous). Getting pretty nice battery life and stable(no reboots yet).
Sent from my Nexus S using Tapatalk 2 Beta-2
polobunny said:
I always doubted bedalus claims on the matter (and even communicated with him through PM).
Time permitting, I'd like to do some tests myself about undervolting, because I am pretty sure it has an impact.
Anyway, my settings are in my signature.
Some people have a problem with 400MHz at 900, 950mv seems good for anyone though.
Click to expand...
Click to collapse
Not sure if lower voltages, would make for less amp/wattage draw,
Sent from my Nexus S 4G using Tapatalk
what exactly is the difference between arm and int voltage? and what should i drop? both?
i have been undervolting with the internal voltage controle of aokp and this only drops int voltages //edit: After taking a second look, it seems like its arm thats changing...
I've dicked around with undervolting since my Evo days, and honestly, it does nothing for battery life. Multiple kernel developers - not to mention bedalus's tests - confirm this.
Undervolting seems useful only for providing an excuse for futzing with your phone. Any power savings are likely anecdotal or psychological.
i start from now the undervolitng , i chek and after i post my expirience .
gear.h34d.2012 said:
Just got over 1 day of battery dropping all stock voltages by 25.
Codename 1.5.5
Matr1x 18.0 cfs
1200/200 lazy
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There it is.
gear.h34d.2012 said:
There it is.
Click to expand...
Click to collapse
I bet your phone was on idle most of the time.
currently running with these voltage settings:
freq arm int
1200 1350 1125
1000 1225 1075
800 1075 1000
400 950 1000
200 875 975
Governor:SmartassV2
Scheduler:noop
mix/max:200/1200
Rom:Codename Android 3.6.0
Kernel:AirKernel 65fps+BlueColor HBM #211
no reboots so far, but i feel that i've not reached the down-limit point! especially for 1000mhz freq
i'm default
please give me description about voltages.
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)
Q&A:
What is Overclocking??
Overclocking is running the cpu, and possibly other system components like memory, faster than the speed for which it was rated. It's not something to take lightly as it's something that actually can physically damage the phone.
What is Undervolting?
If you are performing CPU intensive tasks, you reap the most benefit from the UV kernel because it needs less power to run at 1 GHz (or whatever the maximum clock speed is set to for that kernel).
If you spend alot of time idling, for instance reading interspersed by web requests, you are spending most of your time at the minimum clock speed. With the stock kernel, that is set to 0.1 GHz. With a UV kernel, the minimum clock needs to be set to something higher to keep the CPU running.
What in the hell is BFS/CFS???
CFS: Completely Fair Scheduler - The original process scheduler. CFS is better for multitasking, BFS is better for user interactions
BFS: Brain F**k Scheduler - The updated and improved process scheduler of CFS. The scheduler is designed to offer low latency when used interactively
What in the hell is Noop/SIO/Others???
NO-OP: This scheduler only implements request merging.
SIO: Simple I/O Scheduler - SIO is like a lighter version of deadline but it doesn't do any kind of sorting, so it's aimed mainly for random-access devices (like SSD hard disks) where request sorting is no needed (as any sector can be accesed in a constant time, regardless of its
physical location).
CFQ: Completely Fair Queueing - The CFQ scheduler has always tried to divide the bandwidth of each block device fairly among the processes performing I/O to that device; the time-sliced version goes further by giving each process exclusive access to the device for a period of time.
BFQ: Budget Fair Queueing - BFQ is a proportional share disk scheduling algorithm, based on CFQ, that supports hierarchical scheduling using a cgroups interface
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BFQ vs CFQ
Slowest task's bw (MB/s) Fastest task's bw (MB/s)
-------------------------------------------------------------------
BFQ (2 files) 9.81 +/- 0.47 9.95 +/- 0.43
CFQ (2 files) 8.61 +/- 0.67 11.92 +/- 0.44
-------------------------------------------------------------------
BFQ (5 files) 4.29 +/- 0.10 4.31 +/- 0.09
CFQ (5 files) 4.01 +/- 0.17 5.24 +/- 0.14
__________________________________________________________________________________________________________________________________
The voltage settings are going to be differ by each of us, but sharing some of your settings will help the "New" or any people to find their stable settings.
Ex:
Kernel Type: TW/AOSP
OTB version: 1.1b/1.2b/etc
Scheduler: cfq/bfq/sio/Noop/Deadline/etc
Settings: Highest to Least
7/09
ASOP
OTB 2.6.35.13 CFS 0704
BFQ
1500: -0
1400: -0
1300: -0
1200: -50
1000: -75
800: -75
400: -100
200: -100
100: -125
bfq scheduler, clocked to 1120 Mhz
1120 : -25
1000 : -25
800 : -50
600 : -50
400 : -75
200 : -125
100 : -150
Stable for 36hrs
1400 - 50
1300 - 50
1000 -50
800-0
400- 50
200 - 50
100 - 200
Noop also
Thoes are my settings test settings as of today so far so good XD
Sent from my SCH-I500 using XDA App
CFQ Scheduler
1200 - 0
1000 - 25
800 - 25
600 - 50
400 - 50
200 - 50
Still testing more aggressive settings but this has been 100% stable for me.
SIO scheduler. Clocked at stock 1000 Mhz
1000 : -75
800 : -75
600 : -75
400: -75
200: -125
100: -150
Testing for stability now, but it seems to be working great for now.
Its kinda weird but when I first flash the OTB I am not able to run voltages as low as I can after a few hours. Makes no sense to me but whatever.
My 100% of the time fail safe settings are:
1300 -75
1200 -25
1000 -50
800 -50
400 -75
200 -75
100 -75
With the above its always been perfect. Now as aforementioned after a short while I can adjust to these following voltages:
1300 -75
1200 -50
1000 -75
800 -75
400 -100
200 -125
100 -125
But again oddly if I try testing these right after a fresh kernel install I get some kind of freeze/lock up issue.
As always YMMV and truly you need to find what is stable for your own phone and the only way to do that is thru individual testing.
In terms of the scheduler I was mostly using cfq since OTB came out for voltage control but I have played with SIO and BFQ. IMO there is not a tangible difference
So what is the difference between the different schedulers? I see some people use SIO and some use CFQ. Is there a place I can go to read up on the differences?
xceebeex said:
So what is the difference between the different schedulers? I see some people use SIO and some use CFQ. Is there a place I can go to read up on the differences?
Click to expand...
Click to collapse
From the community rom thread:
http://forum.xda-developers.com/showpost.php?p=13209379&postcount=247
saps said:
From the community rom thread:
http://forum.xda-developers.com/showpost.php?p=13209379&postcount=247
Click to expand...
Click to collapse
Awesome, thanks. It is hard to find information in that thread with it being so long now
So BFQ is "supposed" to be the best, but it is one of those things where YMMV I am assuming.
BFQ Scheduler
1300 -75uv
1200 -50uv
1150 -50uv
800 -75uv
400 -75uv
200 -100uv
100 -150uv
Running good for a day!
Will update as I go.
xceebeex said:
Awesome, thanks. It is hard to find information in that thread with it being so long now
So BFQ is "supposed" to be the best, but it is one of those things where YMMV I am assuming.
Click to expand...
Click to collapse
Yeah YMMV always. In quadrant tests I get the highest IO scores with sio actually. Mind you its just a few dozen points higher which translates into just a few points higher overall. But it is consistently just a tad bit better than bfq and cfq which are dead end on my phone. After using cfq the past week Im currently on bfq since supposedly thats the one to have. In the end I believe it makes little difference
saps said:
Yeah YMMV always. In quadrant tests I get the highest IO scores with sio actually. Mind you its just a few dozen points higher which translates into just a few points higher overall. But it is consistently just a tad bit better than bfq and cfq which are dead end on my phone. After using cfq the past week Im currently on bfq since supposedly thats the one to have. In the end I believe it makes little difference
Click to expand...
Click to collapse
For general purpose phone use CFQ and BFQ are best, SIO is non time critical and only suitable for single purpose imbedded applications such as dedicated flash controllers where latency had much less importance than data throughput.
If audio and video causing hangs or stutters then CFQ or BFQ are absolutely required.
how are the stock settings on this kernel? UV? how much?
if i don't change anything is it a stock kernel or is there some inherent changes already built in?
saps said:
Its kinda weird but when I first flash the OTB I am not able to run voltages as low as I can after a few hours. Makes no sense to me but whatever.
My 100% of the time fail safe settings are:
1300 -75
1200 -25
1000 -50
800 -50
400 -75
200 -75
100 -75
With the above its always been perfect. Now as aforementioned after a short while I can adjust to these following voltages:
1300 -75
1200 -50
1000 -75
800 -75
400 -100
200 -125
100 -125But again oddly if I try testing these right after a fresh kernel install I get some kind of freeze/lock up issue.
As always YMMV and truly you need to find what is stable for your own phone and the only way to do that is thru individual testing.
In terms of the scheduler I was mostly using cfq since OTB came out for voltage control but I have played with SIO and BFQ. IMO there is not a tangible difference
Click to expand...
Click to collapse
I used these settings and have only had one freeze up (when using the camera and clicking on the preview tab). Thing FLIES.
I actually underclocked mine a little to 800. I prefer the battery life I guess.
800-50
600-75
400-75
200-125
100-125
Battery life still wasn't great lol
I switched over to a Peanut Butta Jelly Time kernel though at the moment to test that out.
gevis said:
I actually underclocked mine a little to 800. I prefer the battery life I guess.
800-50
600-75
400-75
200-125
100-125
Battery life still wasn't great lol
I switched over to a Peanut Butta Jelly Time kernel though at the moment to test that out.
Click to expand...
Click to collapse
Make sure after you find the voltage profile you like you reset the batt stats after you fully charge the battery
Sent from my SCH-I500 using XDA Premium App
Since i can not post in the DEV forum yet:
Thanks for this ROM, I upgraded from SC 2.9.2 and i am blown away by this fantastic, well built and fast ROM!
So once again thank all of you for all of your hard work!
saps said:
Make sure after you find the voltage profile you like you reset the batt stats after you fully charge the battery
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
thanks for that... didn't think about that
Anybody have updates with V1.3 they can share?
I use:
800-75
600-75
400-75
200-75
Underclocked, but the phone is still pretty snappy, and the battery life is awesome. My phone doesn't like 100mhz so I only go down to 200. Now what is this about wiping batt stats?
So, i know alot of us SG2 user are always on the go with tweaking, OC/UC/OV/UC, all for better battery!
And i noticed there are no such threads about this, therefore i decided to start this one , so we could all share our experience and UV values for comparison.
I'm on CM7 stable? (2.3.7) with the following UV values set on boot for a couple of days now;
1200Mhz - 1175mV
1000Mhz - 1075mV
800Mhz - 975mV
500Mhz - 875mV
200Mhz - 625mV (yes! i know . tried 650mV and my screen washed out!)
like i said, i have been using this for a couple of days now, and everything seems fine; quadrant, Asphalt, golf, maps, everything.
So, what are your values.
everyones values will be diferent mate mine wont undervolt by much before it crashes , where as my old sgs2 could be undervolted loads
to be honest iam using speedmod kernel at the minute and there really isnt any need to undervolt or overclock
iam getting pretty much the same battery i did on my old sgs2 that could be undervolted loads like your one can
iam also getting great scores on benchmark programs
Yes, i know everyone's value will be different, i just think it would be interesting to see what people are doing with their beasts!
oh, and what happened to your old SG2?
What do I need to undervolt my SG2? Another different kernel?
I am on stock KI3 + CF-Root
Any recommended STABLE kernel?
Thank you
Thanks for the update
henrychukx said:
So, i know alot of us SG2 user are always on the go with tweaking, OC/UC/OV/UC, all for better battery!
And i noticed there are no such threads about this, therefore i decided to start this one , so we could all share our experience and UV values for comparison.
I'm on CM7 stable? (2.3.7) with the following UV values set on boot for a couple of days now;
1200Mhz - 1175mV
1000Mhz - 1075mV
800Mhz - 975mV
500Mhz - 875mV
200Mhz - 625mV (yes! i know . tried 650mV and my screen washed out!)
like i said, i have been using this for a couple of days now, and everything seems fine; quadrant, Asphalt, golf, maps, everything.
So, what are your values.
Click to expand...
Click to collapse
From what I've read on xda, you can't go 625.. that's why you can set 650 but can't do that for 625. It will jump to the minimum possible mV. Correct me if I'm wrong.
I don kno abt this uv thing worked the same on my sgs1 so iam not into uv on sgs2....kernel fixs tht prblm....but will try now an c wat the effect is...presently on siyah 2 kernel.....cheeerz
the minimum that i would undervolt at is at 800mv on 100mhz..anything under that would just freeze my phone...so to the OP you must have one damn beastly phone to be able to go that low..anyway i always manage to get 5hours screen on time with my settings so im happy..but please share how you manage to use it that low and not have any problems
I'm on CheckRom Revolution 1.0 and running RAGEmod U1-v1.1b.
These are my stable UV settings.
1200Mhz - 1150mV
1000Mhz - 1050mV
800Mhz - 950mV
500Mhz - 850mV
200Mhz - 825mV
gusoldier said:
From what I've read on xda, you can't go 625.. that's why you can set 650 but can't do that for 625. It will jump to the minimum possible mV. Correct me if I'm wrong.
Click to expand...
Click to collapse
i think each SG2's chip is different in some way.
for e.g, i can't set my 1200Mhz @ 1150mV, would be fine for a min or 2, then freeze. i think i also know some guy on XDA here who has 650mv or so.
what apps are you guys using ? setcpu or tegrak ?
yakyllan said:
What do I need to undervolt my SG2? Another different kernel?
I am on stock KI3 + CF-Root
Any recommended STABLE kernel?
Thank you
Click to expand...
Click to collapse
I don't think CF-root supports OC/UV. you need to flash a kernel that supports that! its amazing how much battery u can save....
i get about 68-75% left after using the for 14hours! wih about 2-3hrs of music, few calls, sms, mobile internet.
last night i forgot to plug in for recharge and i only lost 1% battery in 8hrs!
its awesome!
What kernel are you using for the UV?
Any recommended ?
(I don't want to lose my root)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
henrychukx said:
So, i know alot of us SG2 user are always on the go with tweaking, OC/UC/OV/UC, all for better battery!
And i noticed there are no such threads about this, therefore i decided to start this one , so we could all share our experience and UV values for comparison.
I'm on CM7 stable? (2.3.7) with the following UV values set on boot for a couple of days now;
1200Mhz - 1175mV
1000Mhz - 1075mV
800Mhz - 975mV
500Mhz - 875mV
200Mhz - 625mV (yes! i know . tried 650mV and my screen washed out!)..
Click to expand...
Click to collapse
I'm using roughly similar settings (top is 1252mhz @ 1175mv).. although my 200mhz is at 825mV, can it really go down to 625mV without issues? Anyone else have input on this?
yakyllan said:
What kernel are you using for the UV?
Any recommended ?
(I don't want to lose my root)
Click to expand...
Click to collapse
now im on CM7, using codewokx kernel (cmw 5.0).
a while back when i was on stock ROMs i used, Ninpho and siyah kernels, both were good on battery, i know with siyah 1.7.8 u can UC to 100Mhz (the standard 200mhz).
u should try one of em out, and see which is best for you.
viva.fidel said:
I'm using roughly similar settings (top is 1252mhz @ 1175mv).. although my 200mhz is at 825mV, can it really go down to 625mV without issues? Anyone else have input on this?
Click to expand...
Click to collapse
On 200mhz, i can only set voltage from 875-800, and anything btw 800 and 625 gives me a reboot. right now im doing 1d3h28m and still got 34% left.
Thanks to the OP, didn't think I could get to 625mv on 200hz.
850 mv 200 Mhz was my previous setting (825mv would crash)
Tested 625mv and so far so good. CM7 kernel & SetCPU.
200 Mhz - 625 mV
500 Mhz - 850 mV
800 Mhz - 950 mV
1000 Mhz - 1050 mV
1200 Mhz - 1150 mV
Stable.
Geumbou said:
Tested 625mv and so far so good. CM7 kernel & SetCPU.
200 Mhz - 625 mV
Click to expand...
Click to collapse
That's unbelievable. my phone just freezes at such a low voltage
Most custom kernels now a days comes with undervolting underclocking scripts.
Eg: my galaxy s2 is on Touch X xwki8 based rom, which contains undervolting scripts.
Mhz : mv
1400 : 1275
1200 : 1175
1000 : 1075
800 : 975
500 : 875
200 : 850
100 : 825
All of them installing these roms never complained on hanging or not booting problems.
I installed them and never caused a problem for me either. But when I replaced the siyah 1.8 kernel with siyah 2.1, the same scripts never worked on the same phone. In fact it never booted. I had to change the voltages slightly inorder to make it boot again.
My conclusion is the phone manufacturers are making the phones almost 99.99% alike. The changes in volts must be because of different roms or probably kernels installed on different phones. I believe 2 same phones with the same rom and kernel will work with the same under volt script.
What do you think..?
Sent from my GT-I9100 using xda premium
click on my sig to see the results of mine
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.