Post your UV settings - T-Mobile Samsung Galaxy S II SGH-T989

As I started flashing kernels & ROMs on my Galaxy S2, I started undervolting for the first time. However, I couldn't (and still can't) find a good listing of people's UV settings. I feel that applying a global -X setting can't give the best settings, as that approach essentially assumes that the existing values are already optimized and over-volted by a fixed amount. I found that that was not the case.
Anyway, I ended up spending a couple of evenings using system tuner to fix my phone to a given frequency, take my best guess for the voltage and run a stress test (Stability Test). Sometimes it would pass the stress test, but once I started using the touchscreen, it'd lock up, so I'd bump the voltage back up. If I couldn't get it to lock, I'd lower the voltage and try again. It took a lot of time and several resets, but eventually I could find the absolute lowest voltage for any given frequency.
I have not tested every single possible frequency, so there are some extrapolated values in between the tested ones. A number of those could likely still be lowered, as I had bumped most of the untested frequency's voltages up a bit, since I was getting random crashes in the 1-1.2 GHz range.
I don't know if I just lucked out with my phone, but I have noticed that my voltages are way lower than what I am seeing in most kernels. For example, I can run mine at 1.5 GHz with only 1050 mV. Given that power usage is correlated to V squared, I believe that I am saving quite a bit of power here.
Anyway, I wanted to start a thread, so that people can in their own results. Collectively, we should be able to find a good set of voltages that would work on any phone without having to err on the side of overly high voltages. Or conversely, we may find that there are huge differences between phones.
I have been applying these voltages through an init.d script for about a week and have not had any crashes. While I have tested @ 1.836 GHz, note that I do not regularly run my phone above 1.512. I currently run at 384-1512 with a sleep profile of 192-384.
Freq Voltage Tested
192000 812500 Yes
310500 812500
384000 812500 Yes
432000 812500
486000 812500
540000 812500
594000 812500
648000 825000
702000 825000
756000 825000
810000 825000
864000 837500 Yes
918000 850000 Yes
972000 875000 Yes
1026000 900000
1080000 900000
1134000 900000
1188000 937500
1242000 937500 Yes
1296000 987500
1350000 1000000 Yes
1404000 1037500 Yes
1458000 1050000 Yes
1512000 1050000 Yes
1566000 1125000
1620000 1175000
1674000 1175000
1728000 1200000
1782000 1225000
1836000 1250000 Yes

I don't use system tuner but I'm uv around 87.5 all around. I'm using the latest bullet kernel on juggernaut. The kernel is undervolted by -25 default.
Sent from my SGH-T989 using xda premium

What's the point of UV'ing? Save battery?
Sent from my SGH-T989 using Tapatalk

juntjoo said:
What's the point of UV'ing? Save battery?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Yeah, if you can run the CPU at the same frequency but with a lower voltage, it will consume less power. Since power consumption is tied to the square of the voltage, the savings can be substantial.

Shouldn't UV settings be consistent across kernels?
I just tried applying my settings from the first post on the Synergy kernel, and my phone started crashing HARD. I had to pull the script using adb.
I was surprised by this, because the same voltages worked fine on jugs and bullet kernels. Has anyone ever seen a case where the CPU responded differently with different kernels?

Related

[Myth Busting] SetCPU

Original Thread - http://www.villainrom.co.uk/forum/showthread.php/4874-Myth-Busting-SetCpu
Right I was a little late into the SGS2 game, as many of you know I had to wait quite a while for my phone to arrive due to a system error at my carrier OrangeUK. I have now had my phone for 2 weeks and been using SETCPU since day 1.
Now I am not sure where the said myth has come from but you all have probably seen someone say it, or heard whispers of it. It goes something like this:
"SETCPU DOES NOT WORK ON THE SGS2"
Now this is a lie!!!!!
I have been a user of SETCPU for a long time, a paid user so granted I was a little biased when I chose to use it on the SGS2, however I am not stupid enough to continue to use an app that is not working so despite everyone telling me otherwise I did install the app.
And to mine (and others) surprise it was working perfectly
I underclocked my main profile to 800mhz and made a profile for screen off 200-500 conservative and have been monitoring my time in state ever since.
And has it been wrong? at all? ever??? HAS IT HECK!! its been perfect every time
Has my phone failed to wake?? Got stuck at a certain clock??? used a clock that it higher than my max?? NO! NOT AT ALL, NADDA
Please please please stop spreading idle rumours and whisperings of things you have not had time to properly investigate yourself. Set cpu is a great app, made by a great dev and does not deserve to have people not use it because a few people decided that it did not work.
Maybe it didn't work at first, but SETCPU has been updated 3 times since the SGS2 was first released, all I know is for the last 2 weeks its worked perfectly yes at least 20 times I have seen someone say on xda/twitter/irc or somewhere that setcpu does not work.
Please stop this now!
Photo Evidence:
{
"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"
}
works fine for me too ha
I can only confirm this. Using SetCPU since I rooted my SGS2 (so a couple hours after I got it ), never had any wake issue, freeze or whatever. It's easy to check if it works, just limit your CPU to 500MHz and check some Flash websites
Ondemand on screen off (200-500MHz), and some profiles when low battery and such. Otherwise it's set to ondemand 200-1200MHz. Working fine.
XpLoDWilD said:
I can only confirm this. Using SetCPU since I rooted my SGS2 (so a couple hours after I got it ), never had any wake issue, freeze or whatever. It's easy to check if it works, just limit your CPU to 500MHz and check some Flash websites
Ondemand on screen off (200-500MHz), and some profiles when low battery and such. Otherwise it's set to ondemand 200-1200MHz. Working fine.
Click to expand...
Click to collapse
Mine only works with screen of 200-800 mhz. But maybe thats because mine is uv.
Are you experiencing some relevant battery improvements?
Razer(x) said:
Are you experiencing some relevant battery improvements?
Click to expand...
Click to collapse
yes massively, with no noticeable performance drop
Lennyuk said:
yes massively, with no noticeable performance drop
Click to expand...
Click to collapse
I'll ask you back my money in case i don't see
Razer(x) said:
I'll ask you back my money in case i don't see
Click to expand...
Click to collapse
setcpu is available for free on xda if you don't want to pay
just search on google for "setcpu xda"
Lennyuk said:
setcpu is available for free on xda if you don't want to pay
just search on google for "setcpu xda"
Click to expand...
Click to collapse
Dammit, too late
I'll report my experience in there
Razer(x) said:
Are you experiencing some relevant battery improvements?
Click to expand...
Click to collapse
With Samsung Apps frozen (wifi sharing, hubs, etc), 3G and Sync always on, with casual usage, I'm at about 40% of battery after 1 day and 6 hours.
Not so bad.
Razer(x) said:
Are you experiencing some relevant battery improvements?
Click to expand...
Click to collapse
Had my phone going for 2 days and some minutes before connecting to a charger. I think it was at 13 % battery left at that time too bad I didn't take a picture of it
XpLoDWilD said:
With Samsung Apps frozen (wifi sharing, hubs, etc), 3G and Sync always on, with casual usage, I'm at about 40% of battery after 1 day and 6 hours.
Not so bad.
Click to expand...
Click to collapse
Screen time?
After setting SetCPU to 500-800MHz:
Code:
# pwd
/sys/devices/system/cpu/cpu0/cpufreq/stats
Code:
# cat time_in_state
1200000 111
1000000 21
800000 25771
500000 2511
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 26237
500000 2511
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 26850
500000 2511
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 27099
500000 2511
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 27291
500000 2511
200000 1188
After setting to 500-500MHz:
Code:
# cat time_in_state
1200000 111
1000000 21
800000 31048
500000 2809
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 31048
500000 3084
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 31048
500000 3174
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 31048
500000 3298
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 31048
500000 3425
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 31048
500000 3525
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 31048
500000 3621
200000 1188
# cat time_in_state
1200000 111
1000000 21
800000 31048
500000 3721
200000 1188
Conclusion: Latest SetCPU works on the SGSII.
LennyUK,you are both right and wrong pal.
First,yes,all these rumours with SetCPU not working on the SGS2 are pure bull****.I've been using SetCPU since I bought my Desire and it's worked every single time.On my SGS2 it works like a charm,UNLESS I am heavily undervolting with Tegrak Overclock Ultimate.Now,this is where you are a little wrong.SetCPU profiles sometimes conflict with Tegrak's app.Especially the screen off one.Why this is happening or exactly when is completely over my head.I want to do some testing though.For starters,I think I'll raise my 200MHz voltage to 825mV and see what happens.
I myself have experienced such behaviour.The phone wouldn't wake up unless I pulled the battery and SetCPU's SCREEN OFF PROFILE,NOT THE APP ITSELF was the cause.However,it never happened with Cognition,where I couldn't use Tegrak's app.
To sum it app,SetCPU is an awesome app by an awesome developer.It's well worth its money,even if it doesn't work well on one device,even if that device is the Galaxy S 2.Not that the latter is true,it works pretty well,but just sayin'.Maybe Tegrak would have to make his app more "compatible".Maybe not.We'll see!
tolis626 said:
LennyUK,you are both right and wrong pal.
First,yes,all these rumours with SetCPU not working on the SGS2 are pure bull****.I've been using SetCPU since I bought my Desire and it's worked every single time.On my SGS2 it works like a charm,UNLESS I am heavily undervolting with Tegrak Overclock Ultimate.Now,this is where you are a little wrong.SetCPU profiles sometimes conflict with Tegrak's app.Especially the screen off one.Why this is happening or exactly when is completely over my head.I want to do some testing though.For starters,I think I'll raise my 200MHz voltage to 825mV and see what happens.
I myself have experienced such behaviour.The phone wouldn't wake up unless I pulled the battery and SetCPU's SCREEN OFF PROFILE,NOT THE APP ITSELF was the cause.However,it never happened with Cognition,where I couldn't use Tegrak's app.
To sum it app,SetCPU is an awesome app by an awesome developer.It's well worth its money,even if it doesn't work well on one device,even if that device is the Galaxy S 2.Not that the latter is true,it works pretty well,but just sayin'.Maybe Tegrak would have to make his app more "compatible".Maybe not.We'll see!
Click to expand...
Click to collapse
Yeah that is where common sense should kick in, you should not be using 2 apps that do the same thing (or near enough the same thing) it is bound to cause conflicts!
tolis626 said:
LennyUK,you are both right and wrong pal.
First,yes,all these rumours with SetCPU not working on the SGS2 are pure bull****.I've been using SetCPU since I bought my Desire and it's worked every single time.On my SGS2 it works like a charm,UNLESS I am heavily undervolting with Tegrak Overclock Ultimate.Now,this is where you are a little wrong.SetCPU profiles sometimes conflict with Tegrak's app.Especially the screen off one.Why this is happening or exactly when is completely over my head.I want to do some testing though.For starters,I think I'll raise my 200MHz voltage to 825mV and see what happens.
I myself have experienced such behaviour.The phone wouldn't wake up unless I pulled the battery and SetCPU's SCREEN OFF PROFILE,NOT THE APP ITSELF was the cause.However,it never happened with Cognition,where I couldn't use Tegrak's app.
To sum it app,SetCPU is an awesome app by an awesome developer.It's well worth its money,even if it doesn't work well on one device,even if that device is the Galaxy S 2.Not that the latter is true,it works pretty well,but just sayin'.Maybe Tegrak would have to make his app more "compatible".Maybe not.We'll see!
Click to expand...
Click to collapse
Moderator edit: flaming/offensive language
Lenny can you please tell me exactly your SetCpu settings and profiles?
Main Profile
Max - 800mhz
Min - 200mhz
Governor - On Demand
Other Profiles
Screen off
Max - 500
Mix - 200
Governor - Conservative
Razer(x) said:
Screen time?
Click to expand...
Click to collapse
Sent from my GT-I9100 using XDA App
Well my friend advised me to use this app for battery back up improvement and I purchased it from Market, used it for two weeks. Tried every possible setting I could, and at the end, it's uninstalled. Well setting it 200 MHz shuts the phone off, that's ridiculous. I used On Demand mode with Min 200 and Max 1200 MHz. Now don't tell me I needed to set mine to 800 MHz, it's really funny and crazy that someone using his/her 1200 MHz CPU on 800 MHz. Undervolting and Underclocking is OK when you are sleeping but continuously keeping it at 800 MHz is weird. Anyway, after two weeks of use, I didn't find any sort of improvement in battery life. I don't know if some people uses this application for Underclocking or to get more juice outta battery, if it's the latter one then you will be disappointed. I am saying BS, well the app costs just US$ 2, so go on and buy it, then state here how did you like it.
To sum it up in a line, I DO NOT recommend this app at all to improve battery back up.
Regards.

Benchmarks and how to interpret them

Hi
Benchmarks apps like AnTuTu are Quadrant are very polular.
This thread should give you some insights why the results
of such benchmarks should not be taken too seriously
"Real world" example:
KISS kernel with max 1.5GHz OC
Using scheduler "odemand" -> AnTuTu will score at about 4000
Using scheduler "smartassV2" -> AnTuTu will score at about 2800
(Quadrant results are similiar in ratio)
So how to "read" this:
The ondemand scheduler scales very fast to highest frequencies.
This means you will get higher numbers at the "cost"
of beeing not so good on battery life.
smartassV2 is "smarter" by doing this frequency upscale differently which leads
to lower numbers since a benchmark can not take that into account.
BUT actually you will not notice a difference in speed in "daily" usage of your device
whereass you will notice a difference in battery usage especially if you tune
the govener to a battery "friendly" profile
regards
max
Thanks for the explanation... I guess the real feel of the ROM is more important that the benchmark score.
Anyway, here is my benchmark score running your kernel at 1.5 smartassV2. single run.
Database IO is :good:
ckpv5 said:
Thanks for the explanation... I guess the real feel of the ROM is more important that the benchmark score.
Anyway, here is my benchmark score running your kernel at 1.5 smartassV2. single run.
Database IO is :good:
Click to expand...
Click to collapse
Thanks for the results
For smartassV2 it also dependend on the "tweaks" you apply
So if you "force" values to be more performant "friendly". The values
are of course higher (CPU clock switching is faster then)
Have you changed any smartssV2 tweaks on your device for this
benchmark runs? The defaults are more performant friendly IIRC
BTW: you can run "my" getcpuinfo.sh script which will print out
all the govener settings
Regards
max
maxwen said:
Have you changed any smartssV2 tweaks on your device for this
benchmark runs? The defaults are more performant friendly IIRC
BTW: you can run "my" getcpuinfo.sh script which will print out
all the govener settings
Click to expand...
Click to collapse
No change to smartassV2 tweaks, use it as it is.
As requested:
Code:
Starting getcpuinfo 08-06-2012 04:42:08
--------------------------------------------------
Available goveners:smartassV2 conservative Lionheart ondemand performance
Available frequencies:245760 368640 768000 806400 1024000 1200000 1401600 1497600
Active govener:smartassV2
min CPU frequency:245760
max CPU frequency:1497600
Scaling min CPU frequency:245760
Scaling max CPU frequency:1497600
--------------------------------------------------
Settings for govener smartassV2:
awake_ideal_freq :800000
debug_mask :0
down_rate_us :99000
max_cpu_load :55
min_cpu_load :25
ramp_down_step :300000
ramp_up_step :200000
sample_rate_jiffies :2
sleep_ideal_freq :200000
sleep_wakeup_freq :99999999
up_rate_us :48000
--------------------------------------------------
VDD values:
24576: 900
61440: 900
122880: 900
184320: 900
192000: 900
245760: 900
368640: 950
768000: 1000
806400: 1000
1024000: 1100
1200000: 1150
1401600: 1175
1497600: 1175
--------------------------------------------------
End getcpuinfo 08-06-2012 04:42:09

Undervolting (Custom Voltage, new approach)

I made a function to calculate voltages for the Google Nexus
As a minimum voltage I found for stock 840mv always.
Best stable undervolt for everyone start from 800mv
840-1000-1090-1200mv
--> VOLTAGE = 733.9031364956^(0.0004200816*FREQUENCY)
REQ= MIN FREQUENCY = 800
Results in table:
MARGIN OFFSET APPLIED: -40mv
350MHz - 800mv
700 - 945
920 - 1040
1200 - 1175
1350 - 1254
1400 - 1281
1500 - 1338
1600 - 1388
Please test the settings and post back here. I believe these are stable for everyone.
I am experimenting to try pushing these into the CM10 repositories.
Not every phone under volts the same
Sent from my Galaxy Nexus using xda premium
The standard setting for 1190 MHz with Trinity kernel is 1150 mV, and it's solid as a rock for many users. That would fit right into your chart easily, so that's at least some confirmation of its accuracy.
I'll test 800 mV @ 307 MHz, and 945 mV @ 691 MHz. Those are lower than Trinity's defaults of 850 mV and 1000 mV for those frequencies.
No immediate problems but I'll leave it this way and see what happens.
Smallsmx3 said:
Not every phone under volts the same
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
that's why we could use the function:
VOLTAGE = 733.9031364956^(0.0004200816*FREQUENCY) + MARGIN
I am currently thinking about rewriting something for the Google Nexus
Let's disable Smart Reflex.
Replace it with stock voltages generated by this curve found by the frequencies the MPU runs at.
No need to program voltages!
Next is the availability of a voltage_margin value which users can modify with the android terminal emulator or a script.
How would you guys like this? This will make undervolting easier. Maybe little more limited but undervolting shouldn't take so much time in my opinion. You can't undervolt a Sandy Bridge CPU for each frequency separately. So why should phones.
Please let me know if you guys would like this feature. Then I will start developing.
GOALS:
- Making undervolting easy for everyone!
- Consumes less time!
I'd really appreciate and use this feature! I hate looking for Voltages again and again. Calculating them would be much more comfortable!
I use Franco.Kernel with Voltages from 230 to 1804 MHz and I tried to calculate the Voltages with your funktion within an excel-sheet. But my results are so damn far away from a realistic Voltage...
For example for 700MHz I get the Voltage "6,96"
I took this:
VOLTAGE = 733,9031364956^(0,0004200816*FREQUENCY)
put in the frequency:
VOLTAGE = 733,9031364956^(0,0004200816*700) = 733,9031364956 ^ 0,29405712 = 6,9608371895070636295467507606432
VOLTAGE = 6,9608371895070636295467507606432
Where's my mistake?
This sounds like a great idea, I hate trying to undervolt my phone cause I feel like I end up doing too much and start ruining the experience with ROMs so I stopped altogether.
I Like The Idea Of Making It Simple But every Single CPU Is Different And OC Differently And Will UV Differently. Even with Different Kernels And Roms You Will Have Different Results.
I Do Applaud Your Efforts but The Only Way To see How Low You Can Go Is To set It And Test It.
It Will Either Run Or It Won't, You Can't Really Harm Your CPU With UV'ing Like With OC'ing.
Sorry About The Capitals, Only Way My Phone Does It On Here I Guess
t-rip said:
I'd really appreciate and use this feature! I hate looking for Voltages again and again. Calculating them would be much more comfortable!
I use Franco.Kernel with Voltages from 230 to 1804 MHz and I tried to calculate the Voltages with your funktion within an excel-sheet. But my results are so damn far away from a realistic Voltage...
For example for 700MHz I get the Voltage "6,96"
I took this:
VOLTAGE = 733,9031364956^(0,0004200816*FREQUENCY)
put in the frequency:
VOLTAGE = 733,9031364956^(0,0004200816*700) = 733,9031364956 ^ 0,29405712 = 6,9608371895070636295467507606432
VOLTAGE = 6,9608371895070636295467507606432
Where's my mistake?
Click to expand...
Click to collapse
+1 ...But look awesone this idea!!
Cheers!
Great idea. Why you don't put directly a Google/Excel sheet?

[Q] Weird voltage values being displayed - How do I know what they actually are?

I've always been a fan of undervolting my phones and ran into this problem with every ROM I've tested on my Note 2. The voltage values are completely out of whack, and I can't really tell what the original values are, preventing me from successfully undervolting my phone. Here are some of the values displayed by SetCPU:
200 MHz: 912500 mV
400 MHz: 937500 mV
600 MHz: 962500 mV
800 MHz: 1012500 mV
1000 MHz: 1075000 mV
1200 MHz: 1137500 mV
1400 MHz: 1200000 mV
1600 MHz: 1250000 mV
I thought they could be the regular values times 1000, but that doesn't work. For example, as soon as I move the slide on 200 MHz one step down, it changes from 912500 mV to 1500 mV. If the original number were 912.5 mV as I assumed, it should go down to a closer value like 900 mV, but it goes to 1500 mV instead. I don't know what to do here. I am using JediXP12 ROM straight out of the box with a totally clean install.
How can I find out the actual values of the voltages at the different speeds? Has anyone here had the same issue? How did you solve it?
Im guessing reflash your kernel lol
Here are mine...this is saber 17
saber kernel's voltages aren't compatible with voltage adjustment apps
the developer has made sure of that... he's got his own idea of voltage optimization... check the kernel thread for more details
ShadowVlican said:
saber kernel's voltages aren't compatible with voltage adjustment apps
the developer has made sure of that... he's got his own idea of voltage optimization... check the kernel thread for more details
Click to expand...
Click to collapse
Oh, I didn't know that. I'll check out the thread and other kernels. Thanks.

Undervolting-Most Stable-Guide

I just want to share my most stable maximum undervolting of my Wonder,
I did not say that I am the first one to post this, I know there are already successfully undervolted their phones.
I've learned this from Pepoluan post, I've forgot that thread already.
We all know that undervolting our device gives advantages, such as extending battery life, increases power supply, extends the life of the device and less heat.
Here's what i've used.
1. Latest CM9 Rom (cm9-20130603-UNOFFICIAL-ancora) by our master Arco68
2. Kernel capable for unvervolting- I'm using HurtSky's kernel ( 3.0.82ICSHurtSky V 3.5)
3. IncrediControl app from playstore
So here are the tabulation below:
HTML:
Frequency Default V UV(My Setting) Difference % Savings
122880 900 750 150 16.7%
245760 900 750 150 16.7%
368640 900 750 150 16.7%
768000 1050 825 225 21.4%
806400 1100 925 175 15.9%
1024000 1200 925 275 22.9%
1113600 1200 975 225 18.8%
1209600 1200 1025 175 14.6%
1305600 1225 1050 175 14.3%
1401600 1250 1100 150 12.0%
1516800 1250 1150 100 8.0%
1612800 1275 1200 75 5.9%
1708800 1300 1275 25 1.9%
1804800 1325 1325 0 0.0%
I have conducted a stress test for every frequency to determine its most stable voltage.
TIPS:
- Use minimum frequency of 368 MHz since they have the same voltage with 122 and 245.
Advantage
- Improves scrolling ( based on my experience)
- Music clarity (also based on my experence)
- Launching Apps is much faster ( again based on my experience)
Disadvantage
- please let me know
Please, if you want to use this set up on your phone, please dont blame me if your phone crashes.
Please conduct a stress test first for every step down on undervolting for every frequency and here is the a Quick Guide below:
Quick Guide - Undervolting
What you need:
1. KERNEL - Capable for UnderVolting.
2. IncerdiControl App
3. Apps for Stress Test or Heavy Games or Benchmarking Apps.
4. Patience.
STEPS
1. Set the minimum frequency and maximum frequency of the CPU - the minimum should be the lowest existing frequency of the cpu and the maximum should be 1 step higher than the minimum (sample: min= 122MHz and max = 245 MHz)
2. Open IncrediControl app and set each frequency by 1 step down ( less 25 each),
3. Then apply, do not apply at boot first, ( so when it crashes it will revert back to the default settings)
4. Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
5. When it passed, repeat steps 2, 3, 4 until your phone crashes.
6. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
7. Record now the stable lowered voltage.
8. Next, increase the maximum frequency by 1 step higher (not the voltage).
9. The minimum frequency should be set to the recorded safe lowered voltage.
10. Open IncrediControl and set the voltage of the maximum frequency only by 1 step down (less 25).
11. Then Apply, do not apply at boot first,
12.Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
13. When it passed, repeat steps 10, 11, 12 until your phone crashes.
14. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
15. Repeat steps 8, 9, 10, 11, 12, 13 and 14 for the remaining frequencies, until you have determined the stable lowered voltages for each frequencies.
16. Now, after you have determined the undervoltage, apply it to your phone, no not apply first at booth,
17. Observe and stress test your phone for at least 1 hour.
18. if it will not crash anymore, you have now the Stable Undevoltage.
19. To be more safe, for daily use, increase the voltages by 1 step for each frequencies, except those which did not changed the value.
20. You can now apply the settings at boot.
21. Enjoy.
Note:
If your phone became unresponsive or vibrates continuously, that's the time that your phone is crashing, just turn off the phone, press the power for at least 10 seconds and it will turn off, or simply pull the battery.
TO THOSE WHO HAD SUCCESSFULLY UNDERVOLTED THEIR GALAXY W, MAY POST HERE AND MAY SHARE THEIR SETTINGS, SO SOME OF THE MEMBERS MAY GET AN IDEA.
Thanks to
Arco68
HurtSky
Pepoluan
honeyx
& Galaxy W Community
stock rom compatible?
Hi, thanks for sharing this:good:
Will i be able to use it with a rooted stock rom?
is stock rom capable of undervolting?
jakelq said:
I just want to share my most stable maximum undervolting of my Wonder,
I did not say that I am the first one to post this, I know there are already successfully undervolted their phones.
I've learned this from Pepoluan post, I've forgot that thread already.
We all know that undervolting our device gives advantages, such as extending battery life, increases power supply, extends the life of the device and less heat.
Here's what i've used.
1. Latest CM9 Rom (cm9-20130603-UNOFFICIAL-ancora) by our master Arco68
2. Kernel capable for unvervolting- I'm using HurtSky's kernel ( 3.0.80ICSHurtSky V 3.4)
3. IncrediControl app from playstore
So here are the tabulation below:
HTML:
Frequency Default V UV(My Setting) Difference % Savings
122880 900 750 150 16.7%
245760 900 750 150 16.7%
368640 900 750 150 16.7%
768000 1050 825 225 21.4%
806400 1100 925 175 15.9%
1024000 1200 925 275 22.9%
1113600 1200 975 225 18.8%
1209600 1200 1025 175 14.6%
1305600 1225 1050 175 14.3%
1401600 1250 1100 150 12.0%
1516800 1250 1150 100 8.0%
1612800 1275 1200 75 5.9%
1708800 1300 1275 25 1.9%
1804800 1325 1325 0 0.0%
I have conducted a stress test for every frequency to determine its most stable voltage.
TIPS:
- Use minimum frequency of 368 MHz since they have the same voltage with 122 and 245.
Advantage
- Improves scrolling ( based on my experience)
- Music clarity (also based on my experence)
- Launching Apps is much faster ( again based on my experience)
Disadvantage
- please let me know
Please, if you want to use this set up on your phone, please dont blame me if your phone crashes.
Please conduct a stress test first for every step down on undervolting for every frequency and here is the a Quick Guide below:
Quick Guide - Undervolting
What you need:
1. KERNEL - Capable for UnderVolting.
2. IncerdiControl App
3. Apps for Stress Test or Heavy Games or Benchmarking Apps.
4. Patience.
STEPS
1. Set the minimum frequency and maximum frequency of the CPU - the minimum should be the lowest existing frequency of the cpu and the maximum should be 1 step higher than the minimum (sample: min= 122MHz and max = 245 MHz)
2. Open IncrediControl app and set each frequency by 1 step down ( less 25 each),
3. Then apply, do not apply at boot first, ( so when it crashes it will revert back to the default settings)
4. Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
5. When it passed, repeat steps 2, 3, 4 until your phone crashes.
6. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
7. Record now the stable lowered voltage.
8. Next, increase the maximum frequency by 1 step higher (not the voltage).
9. The minimum frequency should be set to the recorded safe lowered voltage.
10. Open IncrediControl and set the voltage of the maximum frequency only by 1 step down (less 25).
11. Then Apply, do not apply at boot first,
12.Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
13. When it passed, repeat steps 10, 11, 12 until your phone crashes.
14. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
15. Repeat steps 8, 9, 10, 11, 12, 13 and 14 for the remaining frequencies, until you have determined the stable lowered voltages for each frequencies.
16. Now, after you have determined the undervoltage, apply it to your phone, no not apply first at booth,
17. Observe and stress test your phone for at least 1 hour.
18. if it will not crash anymore, you have now the Most Stable Undevoltage.
19. You can now apply the settings at boot.
20. Enjoy.
Note:
If your phone became unresponsive or vibrates continuously, that's the time that your phone is crashing, just turn off the phone, press the power for at least 10 seconds and it will turn off, or simply pull the battery.
Thanks to
Arco68
HurtSky
Pepoluan
& Galaxy W Community
Click to expand...
Click to collapse
Dude, these voltages are extreme!!! For gaming, these kind of voltages will surely crash the W. Well i tried putting 1.4/1.5GHz to 1175V and it crashed while playing Subway Surfers. Set at 1200V is stable enuff !
Sent from my GT-S6500 using xda app-developers app
lincoln_bw said:
Hi, thanks for sharing this:good:
Will i be able to use it with a rooted stock rom?
is stock rom capable of undervolting?
Click to expand...
Click to collapse
As far as i know, the stock rom is not capable for undervolting.
IncrediControl apps will work only for rooted phone and kernel capable for undervolting.
Thank you...
TiTAN-O-One said:
Dude, these voltages are extreme!!! For gaming, these kind of voltages will surely crash the W. Well i tried putting 1.4/1.5GHz to 1175V and it crashed while playing Subway Surfers. Set at 1200V is stable enuff !
Sent from my GT-S6500 using xda app-developers app
Click to expand...
Click to collapse
Yup, but this was the result after the tests and its really stable enough.
If you really want to check the stable undervoltage for 1.4GHz and 1.5GHz, you may set your minimum frequency to 1.4GHz and 1.5GHZ for the maximum frequency, undervolt it and check if it really crashes your phone.
Sometimes, crashes may caused by the low frequencies, not the maximum frequencies.
Thank you,
To be 100% sure you should check each frequency separately, not just lower all voltages at the same time by 25mV till it causes your phone to crash. For me I could lover the voltages for the lower frequencies more than for the upper frequencies. By saying this even not thinking about the oc frequencies, just the standard clock frequencies.
Also some games and benchmarks will be not enough to test stability. For me many games and benachmarks passed the voltages i set while testing but for example the facebook app freezed the phone after launching it. At some voltages the phone even could last for 3 days stable but crashed then, so the whole procedure took me a while till I found my stable undervolting settings.
honeyx said:
To be 100% sure you should check each frequency separately, not just lower all voltages at the same time by 25mV till it causes your phone to crash. For me I could lover the voltages for the lower frequencies more than for the upper frequencies. By saying this even not thinking about the oc frequencies, just the standard clock frequencies.
Also some games and benchmarks will be not enough to test stability. For me many games and benachmarks passed the voltages i set while testing but for example the facebook app freezed the phone after launching it. At some voltages the phone even could last for 3 days stable but crashed then, so the whole procedure took me a while till I found my stable undervolting settings.
Click to expand...
Click to collapse
+1
Maybe after determining the stable low voltage during stress tests, it would be safe to increase the voltage by 1 step higher for each frequency.
Thanks for sharing,
jakelq said:
+1
Maybe after determining the stable low voltage during stress tests, it would be safe to increase the voltage by 1 step higher for each frequency.
Thanks for sharing,
Click to expand...
Click to collapse
That´s what I also recommend. It doesn´t hurt to incrase all voltages by 25mV after finding the lowest stable values and will incrase stability a lot, as there always might be some small fluctuations while the frequencies are changing.
honeyx said:
That´s what I also recommend. It doesn´t hurt to incrase all voltages by 25mV after finding the lowest stable values and will incrase stability a lot, as there always might be some small fluctuations while the frequencies are changing.
Click to expand...
Click to collapse
Yup, I've already included your recommendation, that would be a great help.
Thanks for the recommendation.
Noob question, what is Undervolting?
Dhada said:
Noob question, what is Undervolting?
Click to expand...
Click to collapse
Are you seroius about this? It´s quite obvious when looking at the first post. It´s lowering the voltage of the CPU to reduce consumption and so also the battery drain.
honeyx said:
Are you seroius about this? It´s quite obvious when looking at the first post. It´s lowering the voltage of the CPU to reduce consumption and so also the battery drain.
Click to expand...
Click to collapse
Sounds to conflict
Dhada said:
Sounds to conflict
Click to expand...
Click to collapse
Baby steps!
I assume you play games and probably set ur phone clock speed stock at 1.4 GHz rite? Sometimes, you notice a huge battery drain after playing games like NFSMW or Modern Combat... Well, undervolt is for you to lower the voltages for EACH clock speed of your device to make battery last abit longer... Setting it too low may result in CRASHING or FREEZING and so u have this guide to show you the most stable undervolting thing... hope it helps CMIIW
Sent from my GT-I8150 using xda app-developers app
TiTAN-O-One said:
Baby steps!
I assume you play games and probably set ur phone clock speed stock at 1.4 GHz rite? Sometimes, you notice a huge battery drain after playing games like NFSMW or Modern Combat... Well, undervolt is for you to lower the voltages for EACH clock speed of your device to make battery last abit longer... Setting it too low may result in CRASHING or FREEZING and so u have this guide to show you the most stable undervolting thing... hope it helps CMIIW
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Nice i already did it
TiTAN-O-One said:
Dude, these voltages are extreme!!! For gaming, these kind of voltages will surely crash the W. Well i tried putting 1.4/1.5GHz to 1175V and it crashed while playing Subway Surfers. Set at 1200V is stable enuff !
Sent from my GT-S6500 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately, not all W's are equal; some are more equal than the others
What I meant was: the components are varying, quite so in fact that a W might survive at those very low voltages, while others give up the ghost and/or go crazy.
One have to test; therefore, great job for @jakelq for posting the complete procedure :thumbup:
-- sent from Samsung GT-I8150 running CM10 by Arco68
pepoluan said:
Unfortunately, not all W's are equal; some are more equal than the others
What I meant was: the components are varying, quite so in fact that a W might survive at those very low voltages, while others give up the ghost and/or go crazy.
One have to test; therefore, great job for @jakelq for posting the complete procedure :thumbup:
-- sent from Samsung GT-I8150 running CM10 by Arco68
Click to expand...
Click to collapse
Hey, where have you been?
Thank you, but you know the credit should go for you.
jakelq said:
Hey, where have you been?
Thank you, but you know the credit should go for you.
Click to expand...
Click to collapse
Had been extremely busy at work... I have to supervise so many things, I lost track of this Wonder-ful forum...
-- sent from Samsung GT-I8150 running CM10 by Arco68
pepoluan said:
Had been extremely busy at work... I have to supervise so many things, I lost track of this Wonder-ful forum...
-- sent from Samsung GT-I8150 running CM10 by Arco68
Click to expand...
Click to collapse
Glad you still find time for our community.
Thank you,
jakelq said:
I just want to share my most stable maximum undervolting of my Wonder,
I did not say that I am the first one to post this, I know there are already successfully undervolted their phones.
I've learned this from Pepoluan post, I've forgot that thread already.
We all know that undervolting our device gives advantages, such as extending battery life, increases power supply, extends the life of the device and less heat.
Here's what i've used.
1. Latest CM9 Rom (cm9-20130603-UNOFFICIAL-ancora) by our master Arco68
2. Kernel capable for unvervolting- I'm using HurtSky's kernel ( 3.0.82ICSHurtSky V 3.5)
3. IncrediControl app from playstore
So here are the tabulation below:
HTML:
Frequency Default V UV(My Setting) Difference % Savings
122880 900 750 150 16.7%
245760 900 750 150 16.7%
368640 900 750 150 16.7%
768000 1050 825 225 21.4%
806400 1100 925 175 15.9%
1024000 1200 925 275 22.9%
1113600 1200 975 225 18.8%
1209600 1200 1025 175 14.6%
1305600 1225 1050 175 14.3%
1401600 1250 1100 150 12.0%
1516800 1250 1150 100 8.0%
1612800 1275 1200 75 5.9%
1708800 1300 1275 25 1.9%
1804800 1325 1325 0 0.0%
I have conducted a stress test for every frequency to determine its most stable voltage.
TIPS:
- Use minimum frequency of 368 MHz since they have the same voltage with 122 and 245.
Advantage
- Improves scrolling ( based on my experience)
- Music clarity (also based on my experence)
- Launching Apps is much faster ( again based on my experience)
Disadvantage
- please let me know
Please, if you want to use this set up on your phone, please dont blame me if your phone crashes.
Please conduct a stress test first for every step down on undervolting for every frequency and here is the a Quick Guide below:
Quick Guide - Undervolting
What you need:
1. KERNEL - Capable for UnderVolting.
2. IncerdiControl App
3. Apps for Stress Test or Heavy Games or Benchmarking Apps.
4. Patience.
STEPS
1. Set the minimum frequency and maximum frequency of the CPU - the minimum should be the lowest existing frequency of the cpu and the maximum should be 1 step higher than the minimum (sample: min= 122MHz and max = 245 MHz)
2. Open IncrediControl app and set each frequency by 1 step down ( less 25 each),
3. Then apply, do not apply at boot first, ( so when it crashes it will revert back to the default settings)
4. Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
5. When it passed, repeat steps 2, 3, 4 until your phone crashes.
6. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
7. Record now the stable lowered voltage.
8. Next, increase the maximum frequency by 1 step higher (not the voltage).
9. The minimum frequency should be set to the recorded safe lowered voltage.
10. Open IncrediControl and set the voltage of the maximum frequency only by 1 step down (less 25).
11. Then Apply, do not apply at boot first,
12.Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
13. When it passed, repeat steps 10, 11, 12 until your phone crashes.
14. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
15. Repeat steps 8, 9, 10, 11, 12, 13 and 14 for the remaining frequencies, until you have determined the stable lowered voltages for each frequencies.
16. Now, after you have determined the undervoltage, apply it to your phone, no not apply first at booth,
17. Observe and stress test your phone for at least 1 hour.
18. if it will not crash anymore, you have now the Stable Undevoltage.
19. To be more safe, for daily use, increase the voltages by 1 step for each frequencies, except those which did not changed the value.
20. You can now apply the settings at boot.
21. Enjoy.
Note:
If your phone became unresponsive or vibrates continuously, that's the time that your phone is crashing, just turn off the phone, press the power for at least 10 seconds and it will turn off, or simply pull the battery.
TO THOSE WHO HAD SUCCESSFULLY UNDERVOLTED THEIR GALAXY W, MAY POST HERE AND MAY SHARE THEIR SETTINGS, SO SOME OF THE MEMBERS MAY GET AN IDEA.
Thanks to
Arco68
HurtSky
Pepoluan
honeyx
& Galaxy W Community
Click to expand...
Click to collapse
nice and gonna try it soon, just wanna ask, if i change to another kernel, then i have to reset it again?? .. anyway thankss
jakelq said:
Glad you still find time for our community.
Thank you,
Click to expand...
Click to collapse
Going back here feels like coming back to a family... a slightly dysfunctional family, but still a family nonetheless
Just like some other senior members ; they maybe without a W for some time, but they keep peeking in every now and then, just to enjoy the camaraderie and help people when they can...
hanafi200 said:
nice and gonna try it soon, just wanna ask, if i change to another kernel, then i have to reset it again?? .. anyway thankss
Click to expand...
Click to collapse
Most probably so; a different kernel might stress the system in different ways compared to the previous kernel. What works with one kernel might not be stable with another kernel.
However, if you're using IncrediControl, the app saves the voltage settings so you can start from those numbers instead of starting from scratch. Unless you go Pristine™ of course... in which case I suggest you manually saving the numbers somewhere safe.
-- sent from Samsung GT-I8150 running CM10 by Arco68

Categories

Resources