Related
i have it set up as follows:200MHz Minimum Slider, 1200MHz Maximum Slider, Conservative mode and just followed the instructions as per https://sites.google.com/site/projec...allation-guide, but every time i boot up my phone and i start setcpu my readings are 1000max 100min but my sliders are set as 200MHz Minimum , 1200MHz Maximum. i know there is an option to set on boot but according to the link it states not to:
"Do not configure profiles, do not configure for set on boot. Set manually. There is a known problem with SetCPU that incorrectly configures your system at boot if selected. "
so if i want the settings to stick i have to click on the slider and it sets them to 200MHz Minimum , 1200MHz Maximum.
any suggestions as doing this manually is a pain....
adinis78 said:
i have it set up as follows:200MHz Minimum Slider, 1200MHz Maximum Slider, Conservative mode and just followed the instructions as per https://sites.google.com/site/projec...allation-guide, but every time i boot up my phone and i start setcpu my readings are 1000max 100min but my sliders are set as 200MHz Minimum , 1200MHz Maximum. i know there is an option to set on boot but according to the link it states not to:
"Do not configure profiles, do not configure for set on boot. Set manually. There is a known problem with SetCPU that incorrectly configures your system at boot if selected. "
so if i want the settings to stick i have to click on the slider and it sets them to 200MHz Minimum , 1200MHz Maximum.
any suggestions as doing this manually is a pain....
Click to expand...
Click to collapse
Until the bugs are fixed in the program, get used to manually setting it every time you re-boot your phone. Thems the breaks I'm afraid. Gotta set it manually, there is no work around until it gets fixed inside the program.
Dragoth12 said:
Until the bugs are fixed in the program, get used to manually setting it every time you re-boot your phone. Thems the breaks I'm afraid. Gotta set it manually, there is no work around until it gets fixed inside the program.
Click to expand...
Click to collapse
thank you, hoping there was another way
adinis78 said:
thank you, hoping there was another way
Click to expand...
Click to collapse
I actually just barely ran across this in another thread, I can't vouch for how it works as I am just relaying info, check out this post:
http://forum.xda-developers.com/showpost.php?p=8725283&postcount=10294
If it works, you will not even have to use SetCPU. Good luck.
Dragoth12 said:
I actually just barely ran across this in another thread, I can't vouch for how it works as I am just relaying info, check out this post:
http://forum.xda-developers.com/showpost.php?p=8725283&postcount=10294
If it works, you will not even have to use SetCPU. Good luck.
Click to expand...
Click to collapse
hmm sounds like an idea but how do i access /system/etc/init.d and i don't mind using SetCPU as i have a profile saved so that if my phone starts to overheat it will revert to the setting i have set up, i might just stick with it until SetCPU is fixed.
Dragoth12 said:
I actually just barely ran across this in another thread, I can't vouch for how it works as I am just relaying info, check out this post:
http://forum.xda-developers.com/showpost.php?p=8725283&postcount=10294
If it works, you will not even have to use SetCPU. Good luck.
Click to expand...
Click to collapse
That idea is now brain fart? uhhhhhh. hahaha.
I'm also using 1.9.1 currently, and I use profiles, and use the "autodetect" option in setcpu. Haven't had any problems since.
Even though the sliders say 100min/1000max, it shows 200min/1200max.
PaiPiePia said:
That idea is now brain fart? uhhhhhh. hahaha.
Click to expand...
Click to collapse
haha, that's funny....guess it doesn't work.
Sorry this is somewhat off topic from the thread...but what's the benefits/pros of using SetCPU? And are there any negatives/cons to using it?
The option exists in Glitch's kernel recovery. What does it mean? Should I have enabled it?
Thank you!
The phone will work fine without it, though you can set it to whatever you want. I set it to conservative. All it does is make it so that it changes the cpu governor when you turn the screen off.
Sent from my MIUI SCH-i500
sageDieu said:
The phone will work fine without it, though you can set it to whatever you want. I set it to conservative. All it does is make it so that it changes the cpu governor when you turn the screen off.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
+1... plus you save a lot a battery that way.
Hi!
Is there an app that can change the CPU governor according to useage? I mean, I'd like to have the governor on "ondemand" setting, while I'm not using the phone (the screen is black), but it would be cool if an app would set the governor to "performance" as soon as the screen lights up. It could be done with Tasker perhaps, but Tasker doesn't want run on my phone, doesn't even want to install...
Is there an app for this? Thanks for the answer!
koko008 said:
Hi!
Is there an app that can change the CPU governor according to useage? I mean, I'd like to have the governor on "ondemand" setting, while I'm not using the phone (the screen is black), but it would be cool if an app would set the governor to "performance" as soon as the screen lights up. It could be done with Tasker perhaps, but Tasker doesn't want run on my phone, doesn't even want to install...
Is there an app for this? Thanks for the answer!
Click to expand...
Click to collapse
Yyyyy, SetCPU ....
Sent from my GT-I5800 using XDA Premium App
cop1976 said:
Yyyyy, SetCPU ....
Sent from my GT-I5800 using XDA Premium App
Click to expand...
Click to collapse
Such a dumb, I am... Of course SetCPU! I've been using NoFrills for some time, I'm changing that. Thanks!!!
Use Set CPU, go the 2nd page in that and there you can select profiles.
For example suppose your kernel allows you upto 667 MHZ, then you can select in the profile something like :
When in call, max 300 Mhz.....or Screen Off, Max 200 MHz.
in the 3rd page of Set CPU, it also allows you to undervolt, you may try with -50 in the values.
umangsagar said:
Use Set CPU, go the 2nd page in that and there you can select profiles.
For example suppose your kernel allows you upto 667 MHZ, then you can select in the profile something like :
When in call, max 300 Mhz.....or Screen Off, Max 200 MHz.
in the 3rd page of Set CPU, it also allows you to undervolt, you may try with -50 in the values.
Click to expand...
Click to collapse
My default profile is 390-1170 MHz with performance scaling, and I've set up a profile for screen off with 390-780 MHz with ondemand scaling. I suppose I can set it to lower frequencies as you suggested.
How does undervolting affect CPU usage? I don't know much about these things
Hello,
I have a Samsung Galaxy S2, running CheckROM HD 6 (Android 2.3.6).
I also running SiyahKernel 2.3.14 and SetCPU 2.3.0.
This is the thing:
I set on the first page (Main) the governor to "conservative" and also check "Set on boot".
But everytime I reboot my phone, the governor goes back to "ondemand".
I had given to SetCPU root privileges.
Is there any way to fix it?
Or is there any way to check if something is overwriting the SetCPU setup?
I used to have older versions of SetCPU installed... and after so many upgrades... maybe the new versions are saving the setting in a different file/folder?
Help?
Thanks!
Try use voltage control app from play store
But is there any way to clear all the settings that SetCPU has defined?
pepemosca said:
But is there any way to clear all the settings that SetCPU has defined?
Click to expand...
Click to collapse
Yep, just uninstall set cpu
But where does SetCPU defines the init script for changing the Governor or something like that?
Does SetCPU do something like this: http://androidforums.com/esteem-all-things-root/510543-fix-cpu-governors-not-sticking.html
Code:
init.qcom.post_boot.sh
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
Or this? http://forum.xda-developers.com/showthread.php?p=23330719
set-cpu
good afternoon friend, on the main screen you must press the menu key and give you perflock disabler for Governor Acknowledge the default one, then you must manually setting it and then to check on set on boot and go.
Venomdroid said:
good afternoon friend, on the main screen you must press the menu key and give you perflock disabler for Governor Acknowledge the default one, then you must manually setting it and then to check on set on boot and go.
Click to expand...
Click to collapse
Hello! I've tried what you suggest on "perflock"... But SetCPU says that I don't have the "perflock".
Any other ideas?
Same issue here!
The only solution is to create an init.d script.
My solution, I'd installed Voltage Control https://play.google.com/store/apps/details?id=com.darekxan.voltagecontrol&hl=en
pepemosca said:
My solution, I'd installed Voltage Control https://play.google.com/store/apps/details?id=com.darekxan.voltagecontrol&hl=en
Click to expand...
Click to collapse
Unfortunately voltage control doesn't have the option to set the parameters for the governors... Sampling rate, samplig down factor, etc
How about using ExTweaks?
November13 said:
How about using ExTweaks?
Click to expand...
Click to collapse
Nope, ExTweaks doesn't have the option to change the parameters of the governors either. just setcpu but when you change the parameters they are not applied upon boot.
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
Netrunner157 said:
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Click to expand...
Click to collapse
Mpdecision.. Qualcomm closed source. Hate it.
> Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
How do I do this?
> Mpdecision.. Qualcomm closed source. Hate it.
Is this a tool that fixes this?
So many people have upgraded to Lollipop and yet how is it that I'm the only one bringing up this 787 issue?
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
This is from the program kernel adiutor program you can find here( http://forum.xda-developers.com/android/apps-games/app-kernel-adiutor-t2986129) If you turn hotplugging off you might have better luck setting the min. It will be listed as CPU hotplug in the menu.
Davinci50 said:
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
Click to expand...
Click to collapse
Oh man I did not know how to use google. You opened my eyes. /s
> kernel adiutor
kernel auditor did not help, even after two reboots. i still see min stuck at 787. Is this issue perhaps solved in the lollipop pacman rom?
CM drops to 300.. Turn off mpdecision.
OK so I definitely turned off mp decision both via the app and by renaming /system/bin/mpdecision --> /system/bin/mpdecision-lolololol
Rebooted and checked setcpu and my min is still stuck at 787. Granted I check in a few times a day and sometimes I catch the min at 300 yet sometimes I catch it at 787. What else am I missing?
Moody66 said:
CM drops to 300.. Turn off mpdecision.
Click to expand...
Click to collapse
Is it a stable rom? How many reboots do you get, wifi issues, force closes etc? I'm not a fan of rom's not based off of stock rom, because of instability. I left those behind with the Note 1, Motorola Atrix.
Its in snapshot phase. Of course its stable.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Yes it might be a stable version of CM but is it stable on the Mate 2. I know the difference between stable and nightly.
Its fine. Read the cm forum thread.
@Moody66
No probably like most of the rest he wants to be spoon fed, I was able to determine what you meant in your first post about mp desicsion and determine the appropriate course of action that I wanted to take and also referenced your thread about battery life.
Make a backup, load the rom ,and test drive it like we all do.
God I love Google NO /s
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Moody66 said:
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Click to expand...
Click to collapse
So the general consensus is that Lolipop stock rom cannot have the 787min freq fixed and the solution is to switch rom's altogether? Like I said I disabled mpdecision and even renamed the binary and commented out the entry in build.prop. What else is left?
Isn't that easy. It will always default of there isn't something to takes its place.
Moody66 said:
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
what is easy? You mean to tell me stock lollipop will default to 787 until what takes it's place? No one knows?
It's stock ROM. If you want to make changes flash a ROM. Huawei isn't going to give you that customization.
Noone has made a custom kernel for it. Obviously since it has emui.
Is 787 hardcoded somewhere in this rom that it's usually defaulted to?