Undervolting, what are your settings? - Samsung Galaxy S (4G Model)

My battery is getting old and along with that its life length. So I decided to undervolt and found it stressful but fun (lol weird huh?).
I'm currently stress testing it using SetCPU's stress test, so far it has not crashed.
My undervolt settings:
100 MHz - 950
200 MHz - 950
300 MHz - 975 *
400 MHz - 1000
500 MHz - 1025 *
600 MHz - 1050 *
700 MHz - 1075 *
800 MHz - 1100
900 MHz - 1125 *
1000 MHz - 1150
1100 MHz - 1175 *
1200 MHz - 1200
* - I'm just assuming SetCPU sets this automatically since it skips some clock speeds.
However I set the voltages increment by 25, so far the stress test has not shown any crashes.
What are your settings?

I run about -75 I think across the board using AndroidTuner, no stress test, but seems stable.

Related

OC/UV - What Are Your Results?

Just started playing around with UV/OCing tonight and am pretty happy so far with the results. I'm just currently looking at getting some extra battery life with UVing.
Just curious what everyone else has achieved.
And yes I know, and everyone else should know, that just because someone else was able to get a certain OC/UV doesn't mean you will. So is the game of OCing anything.
Please post the full details of what you have achieved and/or what you run as a daily driver.
In this format:
(My current results, so far)
1120Mhz @ -125
1000Mhz @ -125
900Mhz @ -125
800Mhz @ -125
600Mhz @ -125
400Mhz @ -125
200Mhz @ -125
100Mhz @ -125
Rom: Continuum v4
Kernel: Onix - 2.0.1 #7
(I'm curious what the lowest voltage has been attained at stock/1120 clock)
bnevets27 said:
Just started playing around with UV/OCing tonight and am pretty happy so far with the results. I'm just currently looking at getting some extra battery life with UVing.
Just curious what everyone else has achieved.
And yes I know, and everyone else should know, that just because someone else was able to get a certain OC/UV doesn't mean you will. So is the game of OCing anything.
Please post the full details of what you have achieved and/or what you run as a daily driver.
In this format:
(My current results, so far)
1120Mhz @ -125
1000Mhz @ -125
900Mhz @ -125
800Mhz @ -125
600Mhz @ -125
400Mhz @ -125
200Mhz @ -125
100Mhz @ -125
(I'm curious what the lowest voltage has been attained at stock/1120 clock)
Click to expand...
Click to collapse
I have mine oc. to compensate with battery drain I was undervolting also here is my specs:
1400- 0 Quadrant - 2258 Linpack - 20.1
1000- 50
800 - 100
400 -125
200 -125
100 -150
Here's what I got
1400 @ -25 Quadrant ~1900 Linpack ~19
1200 @ -50
1000 @ -50 Quadrant ~1600 Linpack ~14
800 @ -75
400 @ -75
200 @ -100
100 @ -100
EDIT: I use Voltage control app, some people seem to have issues with set CPU
______________________
Samsung Captivate
ROM: designgear's Cognition v4.2.2
Kernel: eXistZ's KB1 #7 beta
i envy you guys that can run stable at those numbers. my results are
1280 -50
1000 -25
800 -100
400 -100
200 -50
100 -50
with less over clock i can get much lower voltages across the board and without over clock i can go lower still.
having the actual voltage the same for 1000 and 1280 seems to help stability. my chip deosn't seem to like voltage fluctuations. also the difference between the upper and lower voltage seems to be a problem. my phone is stable at -100+ across the board if i dont over clock. for that reason i tend to test things by undervolting from the upper frequencies down, if i go from the low frequencies i will see instability with very little undervolt untill the upper frequencies are also undervolted.
CM7 03182011, Kernel du Jour v4.2
Just UV, with governor set to "conservative"
1000: -100
800: -100
600: -125
400: -125
200: -150
100: -150
Cognition 4.3
Voltage Control App
Stability Test
Neocore
Linpack
Mhz UV Temp. Linpack
1300 -50 (20c/42c) 17.8~
1000 -50
800 -75
400 -100
200 -100
100 -100
Serendipity 6.3
Paragon 6 kernel @ 1344mhz
Linpack = ~18.8
1344 - 0
1000 - 50
800 - 75
400 - 100
200 - 125
100 - 125
I'm liking your numbers... I wonder if having 100 and 200 enabled makes a big difference. Eliminating 1200 and going from 1000 to 4000 seems quite a bit snappier.
Idk. Paragon kernel defaults the states.
jgrnght said:
I'm liking your numbers... I wonder if having 100 and 200 enabled makes a big difference. Eliminating 1200 and going from 1000 to 4000 seems quite a bit snappier.
Click to expand...
Click to collapse
Interesting thread...would be great to see what people are using for different roms..
I can't get 1400 stable, even at stock voltage.... but at 1300 I can get down to -75:
1300 @ -75
1000 @ -100
800 @ -100
600 @ -100
400 @ -100
200 @ -100
100 @ -100
Last time I tried going down to -125 it wasn't stable, but that was on a different kernel... gonna give it a try when I get a chance.
CM7 and The Escapist's kernel with Noop scheduler and 1300mhz limit enabled
1300 -50
1200 -75
1000 -75
800 -100
600 -100
400 -125
200 -125
100 -125
Nice to see everyone posting their numbers.
I'm finding that the UV setting I have are causing the phone to lock up once and a while. I did pass 50 passes of stability test and 30min of neocore. So are those programs really that accurate at testing stability? Is there anything better out there?
Playing Cordy for a bit seems to effectively stress the system, as I can get it to lock quickly even when seeming stable in the synthetic tests.
Cordy spends almost 100% of the time in top frequency state from what I've seen, plus its pounding the GPU.
bnevets27 said:
Nice to see everyone posting their numbers.
I'm finding that the UV setting I have are causing the phone to lock up once and a while. I did pass 50 passes of stability test and 30min of neocore. So are those programs really that accurate at testing stability? Is there anything better out there?
Click to expand...
Click to collapse
I've found that stability test is only accurate on the Mhz it is testing at. What i did was lock my Mhz at 1400, then 1300, then 1200, 1120, 1000, lastly 800. I had to have 5 frequencies ticked to get 800 to even work. I did each level to find the max UV for each level... then used those numbers.
I found having 1000 being my 2nd highest frequency, makes for a much snappier interface. Right now I have 1300, 1000, 800, 400, 200, 100.
Although I was able to use stability test all the way down to 800, I really couldnt test the lower frequencies with it. I found 125 was stable on the lowest 3 while doing benchmarking, however when moving back and forth quickly through settings options, mainly the drop down menus, it would cause it to lock up. So I raised the lower number up to 100 and no longer got crashes in option menus.
Here are the numbers I've settled with and get the quickest overall feel with.
noop scheduler.
1300 -50
1000 -50
800 -75
400 -100
200 -100
100 -100
Cognition 4.3 btw.
Tryng to underclock now. Blah, such a pain!
noop scheduler.
1200 -100
1000 -100
800 -100
400 -100
200 -100
100 -100
On Phoenix Ultimate Special Edition with Onix 2.0.3 kernal
No one else wants to brag?
Anyone aware of (or maybe could make?) an app that can test at each frequency? It would be very helpful to be able to test UV settings for frequencies in the 100-800 range. So far it seems the only "test" is once the phone locks up while navigating thew menus, bump up the voltage to all of the frequencies bellow 800.
(Thanks jgrnght for the suggestion on how to test each frequency 800+)
bnevets27 said:
No one else wants to brag?
Anyone aware of (or maybe could make?) an app that can test at each frequency? It would be very helpful to be able to test UV settings for frequencies in the 100-800 range. So far it seems the only "test" is once the phone locks up while navigating thew menus, bump up the voltage to all of the frequencies bellow 800.
(Thanks jgrnght for the suggestion on how to test each frequency 800+)
Click to expand...
Click to collapse
lol...nothing can beat with hands on experience...you can download cpu spy from the market it will tell you how your cpu stays in every frequency/states you have. From that data you will know which fequency needs more undervolting or tweaks.
Has anyone noticed a definite increase in battery life as a result of undervolting? Common sense points to that it would (less voltage needed, less battery power needed to power it) but does it really translate into solid real life results?
I'm hoping that all this UV business doesn't just give me an extra 15 minutes or something and that it actually translates into an hour or 2.
I got on CM7 TheEscapist's kernel:
1000: -125
800: -125
600: -125
400: -125
200: -150
100: -150
Scheduler: noop
Governor: Conservative

[Q] UV and power usage at different frequencies

Hopefully someone can either confirm my beliefs or clear up any confusion I may be suffering from lol.
If these are my UV settings (just the lower end of the freqs range):
192 MHz > 800 mV
310 MHz > 800 mV
384 MHz > 800 mV
432 MHz > 800 mV
486 MHz > 825 mV
540 MHz > 837.5 mV
Is there any difference in power usage between having my minimum wake frequency set to 432 MHz as opposed to 192 MHz? I am currently under the impression that since both frequencies are set to 800 mV, the end power usage will be the same.
Current Daemon Controller settings are:
Wake Min > 432 MHz
Wake Max > 1026 MHz
Ondemand
Sleep Min > 192 MHz
Sleep Max > 384 MHz
SmartassV2
And using Bricked 1.6 AOSP kernel.
And thanks, of course!
Sent from my Sensation using XDA App
-bump-
44 views and no one knows?
Sent from my Sensation using XDA App

[Q] Phone Reboots Instantly on Incoming Call

Hi XDA,
I recently installed Apex ROM and have tried a couple kernels (Matr1x and Trinity) but it seems that whenever I receive an incoming call AND the screen is off my device reboots.
I am able to receive calls normally when my screen is on. I'm also able to make outgoing calls without any problems.
I suspect that it has something to do with either my minimum frequency or my voltages (i.e. my phone isn't coming out of deep sleep properly), but after raising either/both of them the problem persists.
Has anyone come across this before, or have any suggestions on how to fix this? Would flashing a different radio help (although I've used my current radio on a different ROM without any issues)?
I apologize if this has been asked before. I did a brief search but did not find anything similar to this exact problem.
Some more info:
-ROM: Apex v1.1.3
-Kernel: Trinity (T132-NS-CV-56HZ-ANY-201212623)
-When a call is incoming:
1) The screen remains off, while the capacitive touch keys light up. There is no ringing either.
2) After a few seconds, the phone reboots and the splash animation appears.
What clock speeds are you running at (Min and max)? Are you using deep idle? etc.
063_XOBX said:
What clock speeds are you running at (Min and max)? Are you using deep idle? etc.
Click to expand...
Click to collapse
I do not have deep idle enabled.
Frequency:
400/1000 MHz, ondemand
(15000 sampling rate, 98% up threshold, 1 sampling down factor, 0 powersave bias)
Voltages:
Max Arm Volt - 1500 mV (1250 mV INT)
1320 mhz - 1425 mV (1150 mV INT)
1000 mhz - 1425 mV (1150 mV INT)
800 mhz -1200 mV (1150 mV INT)
400 mhz - 1100 mV (1150 mV INT)
200 mhz - 1000 mV (1150 mV INT)
100 mhz - 1000 mV (1050 mV INT)
developersdevelopers said:
I do not have deep idle enabled.
Frequency:
400/1000 MHz, ondemand
(15000 sampling rate, 98% up threshold, 1 sampling down factor, 0 powersave bias)
Voltages:
Max Arm Volt - 1500 mV (1250 mV INT)
1320 mhz - 1425 mV (1150 mV INT)
1000 mhz - 1425 mV (1150 mV INT)
800 mhz -1200 mV (1150 mV INT)
400 mhz - 1100 mV (1150 mV INT)
200 mhz - 1000 mV (1150 mV INT)
100 mhz - 1000 mV (1050 mV INT)
Click to expand...
Click to collapse
Your ARM voltages are all wrong. This can cause crashes, if they're too high.
Stock from 100 to 1000.
950
950
1050
1200
1250
polobunny said:
Your ARM voltages are all wrong. This can cause crashes, if they're too high.
Stock from 100 to 1000.
950
950
1050
1200
1250
Click to expand...
Click to collapse
Thanks for responding.
The default voltages for Trinity are slightly higher than default because of the bus OC I believe. It was only after I realized I had this problem that I raised the voltages for 100 MHz to 400 MHz a bit.
Anyways, I tried your above voltages but the problem remains.
I'm going to try flashing a couple more kernels (AirKernel, SimpleKernel) and finally my ROM again to see if that helps.
developersdevelopers said:
Thanks for responding.
The default voltages for Trinity are slightly higher than default because of the bus OC I believe. It was only after I realized I had this problem that I raised the voltages for 100 MHz to 400 MHz a bit.
Anyways, I tried your above voltages but the problem remains.
I'm going to try flashing a couple more kernels (AirKernel, SimpleKernel) and finally my ROM again to see if that helps.
Click to expand...
Click to collapse
Which kernel are you using presently? It is quite possible if it's a Trinity kernel that your phone simply doesn't support any type of overclock whatsoever. I'd recommend something a bit more "stock-ish" like the CM9 kernel, thalamus or simple kernel. Air kernel is very good too, very solid on my phone and not overclocked in any way by default. Has the stock voltages too.
Ok so apparently it's an issue specific to the Apex v1.1.3 ROM (which I would have realized if I read that thread more thoroughly, doh).
I'm on Euroskank CM9 now and everything seems to be working just fine.
Oh damn, those kind of things happen I guess. Good to know you got skankwich on this ;D

GALAXY FIT Best SETCPU Settings

What are the best settings of SETCPU for the galaxy fit?
(i have the Cyanogenmod 7.2)
122 - 480 Mhz : Battery life really good ! performance really bad
122 - 604/600 Mhz : Battery good ! performance stable !
122 - 745 Mhz : Battery reduces faster , but performance is Great !
122 - 801 Mhz : Battery drains faster, but performance is F***** good !
Battery Saver
122 - 480 Mhz : Good !
245 - 480 Mhz : Battery drops litte slower
320 - 480 Mhz : Not really good
Performance Blower
480 - 604/600 Mhz : Stable !
480 - 745 Mhz : Performance increased !
604 - 801 Mhz : Your Fit turned into a low-class F1 !
745 - 901 Mhz : Your Fit turned into a med-class F1 !
Blow Your Mind
600 - 600 Mhz : Never drops your performance !
745 - 745 Mhz : Never slow down !
801 - 801 Mhz : No slowdown !
901 - 901 Mhz : Your Fit turned into a super fast motorcycle !
Never think like this
901 - 982 Mhz : Your Fit turned into a hot pan !
1000 - 1120 Mhz : Your Fit exploded !
1500 Mhz - 2000 Mhz : Faster than a SIII !
4000 Mhz - 8000 Mhz : You are crazy !
10000 Mhz - 11000 Mhz : You are fastest low-end device !
13421 Mhz - 15293 Mhz : You burn your house !
31931 Mhz - 78832 Mhz : You burn 4 house !
39239 Mhz - 88392 Mhz : You destroyed your city !
99999 Mhz - 100000 Mhz : You destroyed your country !
source
What i have to do with the governator and the other settings?
Inviato dal mio GT-S5670 con Tapatalk 2
Best for performance and battery ,for me, min 122- max 710 and as governator SMARTASSV2.
PRESS THANKS IF I HELPED YOU.
Sent from my GT-S5670 using xda app-developers app
Harryhades said:
122 - 480 Mhz : Battery life really good ! performance really bad
122 - 604/600 Mhz : Battery good ! performance stable !
122 - 745 Mhz : Battery reduces faster , but performance is Great !
122 - 801 Mhz : Battery drains faster, but performance is F***** good !
Battery Saver
122 - 480 Mhz : Good !
245 - 480 Mhz : Battery drops litte slower
320 - 480 Mhz : Not really good
Performance Blower
480 - 604/600 Mhz : Stable !
480 - 745 Mhz : Performance increased !
604 - 801 Mhz : Your Fit turned into a low-class F1 !
745 - 901 Mhz : Your Fit turned into a med-class F1 !
Blow Your Mind
600 - 600 Mhz : Never drops your performance !
745 - 745 Mhz : Never slow down !
801 - 801 Mhz : No slowdown !
901 - 901 Mhz : Your Fit turned into a super fast motorcycle !
Never think like this
901 - 982 Mhz : Your Fit turned into a hot pan !
1000 - 1120 Mhz : Your Fit exploded !
1500 Mhz - 2000 Mhz : Faster than a SIII !
4000 Mhz - 8000 Mhz : You are crazy !
10000 Mhz - 11000 Mhz : You are fastest low-end device !
13421 Mhz - 15293 Mhz : You burn your house !
31931 Mhz - 78832 Mhz : You burn 4 house !
39239 Mhz - 88392 Mhz : You destroyed your city !
99999 Mhz - 100000 Mhz : You destroyed your country !
source
Click to expand...
Click to collapse
Hahaha lol...suicide attack is dat much easy
tbh as long as u use smartass v2 i put 480-729 or 749 , becouse smartass have profile in it to put sleep clock max 245 or 320 not sure , and there is no need to phone bumping from 122 to 750 when screen is on, just put it at 2 clocks 480 and whatever max u want, ul get stable phone and battery is not really afected, btw 122 use more battery than 245 , and 245 to 480 are same.
Max:- 748-767
Min:- 245 (doesn't matter)
Governer:- On demand
I/O scheduler:- Sio
Overclocking beyond 767 is unstable for FIT in most cases & your phone will restart with default C.P.U. values or even bootloops (it depends...)
Sent from my GT-S5670 using xda premium

[Q] Best undervolting settings for custom kernel

If you use a custom kernel like Aero Kernel, what is your best undervolting settings?
I have been using this for a week and my phone is very stable
300 mhz - 990 mV
384 mhz - 990 mV
600 mhz - 1000 mV
787 mhz - 1000 mV
998 mhz - 1025 mV
1094 mhz - 1025 mV
1190 mhz - 1050 mV
Any suggestions to undervolt it even better?

Categories

Resources