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.
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?
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