is it just me or does the cpu setting not work for custom values?
changing the performance profile does change the frequencies but say I'm on Balanced, and I want to change Minimum to 400. I tap it, the frequency would appear to stick for half a second and then change back to 300.
I've not seen anyone ask this question so maybe I'm the only one..
confused.
Related
What scaling setting do you use, maybe you have custom profile?
I personally use 'ondemand', but I was thinking.... It would be nice to have a smart scaling setting, based on the amount the phone is used, screen brightness and the battery temperature, etc.
Sent from my X10a using XDA App
Hi.
I've set mine at 576 max and left minimum at 245, scaling is on demand, and have set a profile for screen off at 245 for both. I've left the advanced screen as I don't have a clue what any of it means lol.
Non
Used it at first when got rooted. still on root BA23 firmware and im very happy with the current setup. I left the processor to operate the way it want to do.
Dont take me wrong, its a great software, everything is depends on overall apps you are running. and its unique to your phone, check its really necessary.
After-all we are talking about android, not windows.
I want to know the best setting also I had some custome profiles (after reading in a post on XDA) but phone got slow, laggy & sometimes call drop. Then i deleted all custome profiles
Mano1982 said:
I want to know the best setting also I had some custome profiles (after reading in a post on XDA) but phone got slow, laggy & sometimes call drop. Then i deleted all custome profiles
Click to expand...
Click to collapse
I had that problem once. But i think it is a OS bug than the SetCPU bug itself. You should re-root your fone and set profiles one more time. It will help you save a lot of battery
My setting (following someone on the net)
- Fully chage (AC/USB): 998/245
- Screenoff: Max: 348 Min: 245
- Battery <25%: Max: 348 Min: 245
Ok Dundun, I've set profiles again same as yours let's see how it workd
Just came across this thread for decent SetCPU setting: http://forum.xda-developers.com/showthread.php?t=734886
Hi guys,
I've just gotten my G2 setup to overclock at 1.4GHz and I'm trying to set up some profiles so that it runs at around stock or just higher when it's on battery.
Problem I'm having is that the sliders for setting the frequencies won't let me choose anything in between!!
It only allows me to go from 768 straight up to 1401 but nothing in between!
Can anyone help at all?
Much appreciated!!
Without setcpu or pimp installed, if I just set the max of 1000 and min of 216 in the cm7 performance settings menu to restore on boot, will I get the same effect (the only governor setting that will stick is "null")?
Or is it still beneficial to use setcpu to set a screen-off profile?
And the screen-off profile, should the min and max be the same? 216/216? Or is it better to stagger it a little, like 216/312?
I ended up still using setcpu. The built in CPU settings did not work for me.
Sent from my G2x using Tapatalk
mmapcpro said:
Without setcpu or pimp installed, if I just set the max of 1000 and min of 216 in the cm7 performance settings menu to restore on boot, will I get the same effect
Click to expand...
Click to collapse
No, because this allows the governor to change the CPU anywhere between 216 and 1000. This is the default; unrooted stock has it like this.
And the screen-off profile, should the min and max be the same? 216/216? Or is it better to stagger it a little, like 216/312?
Click to expand...
Click to collapse
I keep it 216/216 then allow an in-call profile that goes up to 312 in case when I'm calling someone and the screen is off it needs a bit more juice.
So basically, if I have setcpu installed, but I leave profiles "DISABLED", and leave the sliders alone, then I'm getting no different result from stock? The governor will decide to use the cpu at whatever frequency between 216 and 1000 that it needs at the time?
mmapcpro said:
So basically, if I have setcpu installed, but I leave profiles "DISABLED", and leave the sliders alone, then I'm getting no different result from stock? The governor will decide to use the cpu at whatever frequency between 216 and 1000 that it needs at the time?
Click to expand...
Click to collapse
The Tegra 2 chipset doesn't allow you to change the governor settings. So to answer your question, yes the CPU chooses what frequency it needs depending on load.
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