• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Voltage Control help with setting for S2

K

kopite72

Newbie
Any help much appreciated, i rooted my phone at the weekend & flashed some new themes - all looking good & so much better but i just installed app Voltage Control & was wandering what are the best settings to apply for the S2
 
there is no definitive answer i'm afraid. This type of question pops up time and time again not only on here but on xda too. There is no Holy Grail of settings.
The settings you use are very much trial and error, and will depend on what kernel/scheduler/governer you are using.
Even after saying this, one identical bunch of settings can work perfectly on one handset, and perform far worse on another, so it is very much specific to you.
Best way is trial and error, and dont save your settings to boot up with unless your perfectly happy with them.

a usual starting point may be perhaps to drop each voltage on each CPU MHz step by 50, and take it from there. If you undervolt too much you may find your handset totally freezes, especially when coming out of deep sleep. so keep on trying until you have a bunch of settings that suits you and your happy with.
 
hawker said:
there is no definitive answer i'm afraid. This type of question pops up time and time again not only on here but on xda too. There is no Holy Grail of settings.
The settings you use are very much trial and error, and will depend on what kernel/scheduler/governer you are using.
Even after saying this, one identical bunch of settings can work perfectly on one handset, and perform far worse on another, so it is very much specific to you.
Best way is trial and error, and dont save your settings to boot up with unless your perfectly happy with them.

a usual starting point may be perhaps to drop each voltage on each CPU MHz step by 50, and take it from there. If you undervolt too much you may find your handset totally freezes, especially when coming out of deep sleep. so keep on trying until you have a bunch of settings that suits you and your happy with.
Click to expand...


Thanks for your reply i will have a play later to see any improvements!!!
 
All I've been able to U/V is 100 MHZ. Even if I U/V the other points by 25 I get instant freezing and reboots. Currently 100MHZ is U/V by 100 MV without issues.
 
glore2002 said:
I would also love if someone could help me setting lulzactive and Voltage control with my system: CheckRom v4 and N.E.A.K. 1.3.2 kernel.

Thanks in advance!
Click to expand...

As Hawker said above, every phone seems to be different. I used a set of voltages defined on XDA that hundreds of people said work great on their phone and on mine all I got was a bunch of SOD's until I reset back to default. Remember that the customized kernels already have some voltage settings changed so if you go and change even more, you may not be able to boot. Make sure you make a backup that you can get to from CWM!!
 
Sword Fish said:
As Hawker said above, every phone seems to be different. I used a set of voltages defined on XDA that hundreds of people said work great on their phone and on mine all I got was a bunch of SOD's until I reset back to default. Remember that the customized kernels already have some voltage settings changed so if you go and change even more, you may not be able to boot. Make sure you make a backup that you can get to from CWM!!
Click to expand...

Thanks for your answer. I will keep your advice. Right now I am creating a backup through Recovery :-)

I made some voltages changes (as hawker suggested on another thread) and will see what happens. Basically I am lowering each voltage by 50. We'll see :-)
Thanks again,
glore2002.-
 
Slug said:
One frequency step at a time, I hope? ;)

It can take some hours of testing, but the voltages required by each step vary according to load; testing slowly but surely will give more long-term stability.
Click to expand...

What I did was to lower 50mV in each of the voltages. From 1200Mhz to 100Mhz. So, for example, 1200Mhz was originally 1250mV and now is 1200; 1000Mhz was 1150mV and now is 1100mV, etc.

GPU Control: Low Power State: 100Mhz and 800mV.

i/o Scheduler: noop; CPU Governor: Conservative.

And Conservative and sched_mc enabled in Recovery Menu.

What do you think about these settings? Don't hesitate in telling me the truth :)

Thank you very much!
 
What I found works well is locking the CPU at a frequency then step down the voltage by 25 until it becomes unstable, then I just put it back up to the last stable setting. I'll usually spend 5 min on each voltage setting with some browsing, game play and a full Quadrant test, once I'm satisfied I move on. As for as the GPU goes, it doesn't like much under volting, from the Siyah settings anyways. Its all trial and error.
 
JSR84 said:
What I found works well is locking the CPU at a frequency then step down the voltage by 25 until it becomes unstable, then I just put it back up to the last stable setting. I'll usually spend 5 min on each voltage setting with some browsing, game play and a full Quadrant test, once I'm satisfied I move on. As for as the GPU goes, it doesn't like much under volting, from the Siyah settings anyways. Its all trial and error.
Click to expand...

I would question whether 5 min's is long enough on each setting to test for SOD as this only kicks in when the phone is in Deep Sleep.

Also beware of something I saw the other day and that was someone who'd tweaked their settings so badly that there was not an even spread of usage.

By that I mean that they were using 100Mhz and 200 & 500Mhz were virtually unused, 800Mhz was used, 1000 Mhz was unused ande 1200Mhz was heavily used. This was because they had wrongly u/v'd and were in fact using more battery than the stock settings.
 
5 minutes is definitely not enough.

I really "went for it" last night and put some serious undervolting settings on NEAK to put it through its paces. I'm already running it quite heavily undervolted, but with the exception of LPB modem, I've not had a flash in days and I was bored, so I decided to see what it was capable of.

After big style undervolting, I gave it my usual tests and found it to be behaving perfectly in all my frequently used apps: music, video, gallery, email, browsing, sms etc etc. It was coming out of deep sleep nicely. Perfect.
I then came back onto here, pleased as punch to PM my ground-breaking settings to a member on here. I was about 90% through composing my smug message and guess what.....it froze solid! :D

I would give it a good half hour rigorous testing before passing it through as bootable.

And agree there with ironass. Lower is not necessarily better. Try and get a good usage spread across your frequency ranges. CPU Spy is your best friend here.
 
ironass said:
By that I mean that they were using 100Mhz and 200 & 500Mhz were virtually unused, 800Mhz was used, 1000 Mhz was unused ande 1200Mhz was heavily used. This was because they had wrongly u/v'd and were in fact using more battery than the stock settings.
Click to expand...


As a complete noob to undervolting, that suddenly made things seem a lot more uncertain. :confused:
Does this effectively mean that you should not be uniformly decreasing the voltages but instead dropping and testing each level one by one? How does one go about testing an individual speed?
 
Kuragari said:
Does this effectively mean that you should not be uniformly decreasing the voltages but instead dropping and testing each level one by one?
Click to expand...

That's definitely the best way to achieve optimum settings for your particular device.

How does one go about testing an individual speed?
Click to expand...

Hawker pretty much echoed my own approach. I'll make a -25mV adjustment with Voltage Control (prior to that I used SetCPU) and see if it affects 'normal' use, including letting it idle and deep-sleep. If everything seems okay after an hour or two I'll give it a few AnTuTu and/or SmartBench runs, using my chosen governor, to see how it behaves when working hard. If I still haven't broken it, my final "sign-off" test is a 90min scaling test using Stability Tester. If it endures that torture unscathed I reckon it's good to go. I'll then move onto the next freq step.

Some people advocate benchmarking using the performance governor and the max freq locked to the one you're testing, but I feel that's too artificial and doesn't allow for voltage fluctuations as the CPU load varies.

It's a long and somewhat tedious process, but the reward is (hopefully!) a stable and reliable handset. Of course, it's much less hassle to just stay on stock settings but where's the fun in that? :)
 
ironass said:
I would question whether 5 min's is long enough on each setting to test for SOD as this only kicks in when the phone is in Deep Sleep.

Also beware of something I saw the other day and that was someone who'd tweaked their settings so badly that there was not an even spread of usage.

By that I mean that they were using 100Mhz and 200 & 500Mhz were virtually unused, 800Mhz was used, 1000 Mhz was unused ande 1200Mhz was heavily used. This was because they had wrongly u/v'd and were in fact using more battery than the stock settings.
Click to expand...

Fair enough. But I haven't run into any stability issues using this method.
 
The more aggressively you change the settings, the more testing you need to undertake, otherwise, there's a pretty good chance it will bite you in the bum sooner or later!
:)
 
I've made mine all - and noop conservative with siyah everything is smooth and good battery last night from charge after 4 hrs 3 which was in deep sleep was just down 4%

I have noticed Neak can't handle the settings anywhere as good as Siyah
 
Hawker said:
The more aggressively you change the settings, the more testing you need to undertake, otherwise, there's a pretty good chance it will bite you in the bum sooner or later!
:)
Click to expand...

Ditto that hawker.

A while back I did a fairly gung ho aggressive uv, was very proud of myself, only to find screen freeze on internet browsing and sod about 48 hours later.

Problems may definitely not be apparent at first.
 
You must log in or register to reply here.
Back
Top Bottom