Ive seen an undervolting option in systemtunerpro and ive seen people talking about undervolting.
what will it do to my phone?
if so what should I under volt it to?
the app has 2 buttons that add or subtract 12.5(I think I can't check right now) to all the values at one time. how many times should I press it?
I've searched but cant find nothing
rom is Prime 5 with bricked kernel 1.0 badass gov
Sent from my Primed Sensation 4G with Beats Audio
If you do it right your battery lasts longer and your cpu will be cooler.
It means that the cpu needs less power than normal. But every cpu is different, so you can probably not undervolt that much like someone other.
If you want to do it right, try this:
Search the App "Stability Test".
Then go into System Tuner and look, which Cpu-Freq. are needed most. These are the ones on which you should focus on to undervolt.
First you can set all freq. -25mv, then run the "scaling stability test" in the stability test app. If your phone doesn't freeze in the next 15 min, you can set -25mv again. Do this until your phone reboots or abort the test itself. Then set it 2 steps above the values which didn't work to prevent reboots.
Now you should change only the freq which were used most. But only one after one. If your phone uses (for example) 192 mhz, 1,08ghz and 1,5 ghz most, first undervolt the 192mhz (again till your phone reboots or you can't set it lower).
Then the same with 1,08 Ghz and then 1,5Ghz. If your phone reboots, set it 2 steps above the value which didn't work, so you can be sure that your phone doesn't reboot again.
If you found out which values your phone can handle, go into "System Tuner", CPU, Voltage, Boot settings, then "Re-apply CPU Settings". For the first time you should set it to "On boot completed", if you didn't notice any problem you can set it to "init.d script".
If this doesn't work for you, go back to "voltages", then hold "reset all/clear" till it changes to "save defaults". Press it once, so your values are set as defaults. If you rebooted your phone you have only to go into "System Tuner" and press "Reset all/clear" once, then it will set your values again.
I hope my englisch is good enough to understand it
Related
so i noticed that when i reboot my tab, setcpu is not recognizing (with auto detect). i always have to launch the app and press menu to auto detect it. anyone know how to fix this? my phone would get stuck and reboot if i don't do this after reboot when i put the device on sleep mode (tap power button).
SetCPU seems to have major problems with the tab (it does with mine at least), it's not very beneficial and probably detrimental as the device stands at the moment.
The one time i used it with 'start on boot' after the reboot, the min and max cpu resetted at 19 with a max of 500 :| need to wait for modded kernels.
Sent from my GT-P1000
glad i'm not the only one with this problem. i'll disable it for now until we get some kernels. thx.
I rarely use SetCPU. The default "conservative" mode (100MHz --> 1GHz) is adequate. Of course the current kernels do not allow overclocking, so SetCPU is limited to underclocking (i.e. save battery) or to using the "performance" mode, on-demand (i.e. no need for "run at boot"). As it stands, I need neither, I am very impressed by the "conservative" algorithm.
Whenever I enter the app, it looks like all my settings have been reset, and it shows me running at 1000mhz (despite me setting the max to 800).
Here's how I'm using it, I change all the settings, click apply, then save profile, then save boot settings. Then I reboot my phone.
Additionally, all the menu items under I/O Scheduler and CPU Governor are tripled. What's going on?
I have problems with the boot settings...from what I understand you have to just reconfigure it every time your phone boots. Kinda sucks.
Also, you don't have to reboot to apply settings: it does it as soon as you hit save.
I am using the Clemsyn Kernel now, but have never done any overclocking before.
What is the effect on battery life if I went to around 1.4ish?
What is the effect on the lifetime usage of my unit if I overclock?
After I download SetCpu, what settings do I use? Do I have to change anything in voltage?
I read something where people sometimes underclock when the screen is turned off. How can I do this?
Thanks for any help. I am a noob when it comes to overclocking.
deadhead85 said:
I am using the Clemsyn Kernel now, but have never done any overclocking before.
What is the effect on battery life if I went to around 1.4ish?
What is the effect on the lifetime usage of my unit if I overclock?
After I download SetCpu, what settings do I use? Do I have to change anything in voltage?
I read something where people sometimes underclock when the screen is turned off. How can I do this?
Thanks for any help. I am a noob when it comes to overclocking.
Click to expand...
Click to collapse
Start off by setting your main profile to 1.4GHz and tick set on boot. And theres your overclock... I think interactive gov. is the most useful, you can try others if you want.
If you would like to limit the speed when screen off, add a profile under profiles select screen off and set your wanted frequency when screen off.
reidar.ostrem said:
Start off by setting your main profile to 1.4GHz and tick set on boot. And theres your overclock... I think interactive gov. is the most useful, you can try others if you want.
If you would like to limit the speed when screen off, add a profile under profiles select screen off and set your wanted frequency when screen off.
Click to expand...
Click to collapse
+1 This is exactly what I've done
If you set the max speed to 1.4 GHz and set the governor to performance it will drain the battery faster than if you had it set to the others. You'll most likely have already upgraded the TF by the time it dies due to overclocking. It does shorten the life, not dramatically though. You can set up underclocking in profiles.
If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2
why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor
Jamin13 said:
If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.
i guess setcpu makes it easier to change cpu frequencies quickly through the widget, ns tools doeesnt have a widget so its "harder"
qtwrk said:
why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor
Click to expand...
Click to collapse
SetCPU won't control the Backlight Notifications and Dimmer.
Harbb said:
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.
Click to expand...
Click to collapse
I'm just a bit OCD about battery life some days. I'd rather use the app than making my own scripts. I kinda derped with the profiles earlier today. All is good now.
I wish the two would play better together too - and I don't see how "just don't use them both" or saying SetCPU is no longer needed is acceptable answers. Especially since many of us actually paid for SetCPU...
Now that it looks like we'll only get two governors in MathKids kernel (what a crock)... saying you are picking the wrong one is a bad answer too. Ondemand certainly isn't the best for battery life, and for those of us who have tested and measured battery life we know just picking one isn't a solution either.
So what is the actual answer? Because setting the governor parameters at boot isn't the problem. It's switching between profiles - and the governors that give you the best battery life and giving acceptable performance need to be tweaked from their defaults.
With OnDemand I'm looking at using over 16% battery per hour under 4.1, even with considerable screen off time. Not being able to set it to Wheatley on screen off is killing the battery.
I will say the problem seems to lay directly with SetCPU and I'm going to contact the dev and see what I can find out. I don't see why it should be changing the parameters back to default on profile change.
But people who use neither or just one probably just not comment. Not to flame, or fight, but it's not helpful to add nothing.
I'm currently using CM10.1 AOSP [KANG] from the thread here -- http://forum.xda-developers.com/showthread.php?t=2115520. In essence, I cannot raise either the minimum or maximum CPU speeds above 384MHz.
I just tried restoring my phone using a RUU recovery.exe file, then re-rooted, S-OFF'd, unlocked the bootloader and then updated the firmware. Right after flashing CM10.1, I am still having issues with changing the CPU speed. The maximum and minimum CPU speeds I can choose are either 192MHz or 384MHz. I can go into settings > performance then change the maximum CPU speed to anything higher than that, but almost instantly after I select it the maximum CPU speed drops back down to 384 MHz. The same goes for trying to raise the minimum CPU speed above 384MHz. It makes the phone nearly unusable, as it takes multiple seconds to open almost any application and also reboots randomly quite often. Is there any way I can fix this?
Thanks!
Anyone have ideas/insight? Sorry to bump this!
Right. Here's what I did last time. I used something called SetCPU. Ticked the Set On Boot then it worked. But I unticked the ones in the Performance option.
This is what I do. Hope I help.
if you want do this also
go to system>etc>init.qcom.post_boot.sh and put this line(you can edit with simple text editor)
echo the value > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
do the same for cpu1 if you want to have the same frequency in both cpu