As the title says. No governor, be it on-demand or performance, doesn't stay after a reboot. I've tried Adam, Perseus, issue persists on both of them! Is this because of this new 4.3? If I remember correctly this wasn't a problem on 4.2! I've tried with SetCPU, No Frills, nothing...I always used performance, now I can't set it and it bothers me very much....
Anyone?
Sent from my GT-I9500 using Tapatalk
Have you got more than one app actively trying to set the governor ? You've said you're using SetCPU, but make sure the rom (Performance Control for example) or kernel doesn't have an app that's also trying to set the governor on boot for example. If they are, disable those & then try with SetCPU.
MistahBungle said:
Have you got more than one app actively trying to set the governor ? You've said you're using SetCPU, but make sure the rom (Performance Control for example) or kernel doesn't have an app that's also trying to set the governor on boot for example. If they are, disable those & then try with SetCPU.
Click to expand...
Click to collapse
Well I have tried with either Adam or Perseus, and in that case S-Tweaks and Synapse are automatically installed respectively. And I don't see there's any setting under those apps to change Governor! So I am forced to use SetCPU, are you saying I should uninstall S-Tweaks or Synapse in order to get SetCPU working properly? Because there's no visible settings under S-Tweaks or Synapse to change governor but there could/must be a hidden setting there which changes Governor at each reboot! and probably conflicts with SetCPU?
Actually, first up, try clearing cache/data on SetCPU, reboot, apply settings you want, reboot & see if they stick.
Then try uninstalling those other apps which might be conflicting. Also, check in rom settings to see if you have anything like Performance Control which might be setting something at boot. Also check to see if you have an init.d folder/if there's any scripts lurking in there which might be causing problems.
MistahBungle said:
Actually, first up, try clearing cache/data on SetCPU, reboot, apply settings you want, reboot & see if they stick.
Then try uninstalling those other apps which might be conflicting. Also, check in rom settings to see if you have anything like Performance Control which might be setting something at boot. Also check to see if you have an init.d folder/if there's any scripts lurking in there which might be causing problems.
Click to expand...
Click to collapse
Nah, tried everything, no profile sticks, even master wiped the device with full stock ROM and kernel, nothing. It's not actually a reboot needed for the default governor/settings to take place, if I just turn the screen off and turn it back on after a minute or so the set governor by me doesn't stick.
I am quite sure this is how it is suppose to be, but whatever, I don't like it. The fluidity I have seen with performance, well nothing could beat it. Maybe the CPU architecture of i9500 is the thing to blame here. Damn...
That's really weird. Maybe try another app other than SetCPU (or a bunch of them) ? Some kernels have variables that can't be set by the user or you can set them but they immediately go back to whatever setting the dev who made the kernel wants them to be at (some individual governor settings like sampling rates/etc), but setting the actual governor shouldn't be one of those. If the governor is available in the kernel, you should be able to both set it 'on the fly' and set it on boot.
MistahBungle said:
That's really weird. Maybe try another app other than SetCPU (or a bunch of them) ? Some kernels have variables that can't be set by the user or you can set them but they immediately go back to whatever setting the dev who made the kernel wants them to be at (some individual governor settings like sampling rates/etc), but setting the actual governor shouldn't be one of those. If the governor is available in the kernel, you should be able to both set it 'on the fly' and set it on boot.
Click to expand...
Click to collapse
Nah, not really weird as I understand it now. CPU hits throttle temp at 1.6 GHz and automatically defaults out at a lower clock rate, in this case 800 MHz. That's just too bad for me anyway, I have never used anything besides performance, now I am forced to use something else! I wonder how come no one has mentioned this yet!
Related
Mine is
Performance
Min/Max 1.2 ghz
Auto dectect
Whats yours?
Really auto detect? After every kernel dev says that auto detect isn't stable?
Really?
what should i put?
RacerXFD said:
Really auto detect? After every kernel dev says that auto detect isn't stable?
Really?
Click to expand...
Click to collapse
???
you have to use auto-detect for setcpu to detect your availble clock speeds
on-demand is BROKEN
performance will drain your battery abnormally
running at 100 min / whatever max on conservative is the most stable option for this device at the current time
Leave the advanced settings alone also?
jt1134 said:
you have to use auto-detect for setcpu to detect your availble clock speeds
Click to expand...
Click to collapse
not to contradict, but you dont have to use it, you can use the setCPU.txt file and i recommend it
here is the one i use currently with the D02 1250LV kernel, it is nothing more than a simple text file which tells the setCPU app what are valid steppings/scaling so it cannot auto-detect incorrectly as it often does
http://dl.dropbox.com/u/12311939/setcpu.txt
all you have to do is edit it to the steps that match the kernel you load and drop it in the root of the sd card, then go into setCPU, hit softmenu to go to device selection, scroll down and choose custom or manual...i forget what its called...then scroll down to the bottom and tell it to use the setcpu.txt file option and restart....done, no more problems at boot with setCPU
I only use performance when benchmarking. I use on-demand day to day. Set to 1250 max 100 min. I actually read the entire setCPU dev page, I suggest you do also, keeping in mind the limitations of the kernel you choose to load. I do not use on-demand scaling. I do not use profiles either. I do however, after testing my own device, use "set at boot". Two things on that. 1. setCPU now has a safe mode feature to get out of a problem and 2. I also use the setcpu.txt option instead of auto-detect which is hit or miss. Using the setcpu.txt file method (be sure to go to device selection and choose the bottom custom option) setCPU cannot accidentally set itself to the wrong frequency, it gets it's allowed steppings from the file you create.
if you read the setCPU dev page you (not directed at you jt ) will learn all of this and also about the advanced settings....but they work fine as they are for my device/kernel/usage
jamesnmandy said:
not to contradict, but you dont have to use it, you can use the setCPU.txt file and i recommend it
here is the one i use currently with the D02 1250LV kernel, it is nothing more than a simple text file which tells the setCPU app what are valid steppings/scaling so it cannot auto-detect incorrectly as it often does
http://dl.dropbox.com/u/12311939/setcpu.txt
all you have to do is edit it to the steps that match the kernel you load and drop it in the root of the sd card, then go into setCPU, hit softmenu to go to device selection, scroll down and choose custom or manual...i forget what its called...then scroll down to the bottom and tell it to use the setcpu.txt file option and restart....done, no more problems at boot with setCPU
I only use performance when benchmarking. I use on-demand day to day. Set to 1250 max 100 min. I actually read the entire setCPU dev page, I suggest you do also, keeping in mind the limitations of the kernel you choose to load. I do not use on-demand scaling. I do not use profiles either. I do however, after testing my own device, use "set at boot". Two things on that. 1. setCPU now has a safe mode feature to get out of a problem and 2. I also use the setcpu.txt option instead of auto-detect which is hit or miss. Using the setcpu.txt file method (be sure to go to device selection and choose the bottom custom option) setCPU cannot accidentally set itself to the wrong frequency, it gets it's allowed steppings from the file you create.
if you read the setCPU dev page you (not directed at you jt ) will learn all of this and also about the advanced settings....but they work fine as they are for my device/kernel/usage
Click to expand...
Click to collapse
Contradict much?
Nice find there james
Im wondering what would happen if you didnt match the increments in your txt file to the kernels native ones?
Lol, I only speak of what I know to be true you guys have far more knowledge but I tested this on my own device and also used it on the ally I had so I know its good
Sent from my SCH-I500 using XDA App
Id say probably either fc or nothing. Either it would try to hit something it cant and fc or it would discard the step, but then the large jump sau from 200 to 600 skipping 400 may cause an issue
Sent from my SCH-I500 using XDA App
Well, if I can keep mine running stable for a couple of days, with no "permasleeps" then I will give start on boot a try. So far I'm having excellent luck with 1100 max 100 min with conservative. Set to auto, it brought the right figures up immediately. So far the thing is really running great with the 1100 LV kernal and the settings I mentioned above. I'm sure my quadrant will be lower than 1200, but for some reason the 1200 kernal was only stable when I was placing load on the device, actually using it. When it was idle the screen would "permasleep". Very odd. Stress testing on the 1200 LV kernal threw no errors, but I still had idle issues.
SirKronan said:
Well, if I can keep mine running stable for a couple of days, with no "permasleeps" then I will give start on boot a try. So far I'm having excellent luck with 1100 max 100 min with conservative. Set to auto, it brought the right figures up immediately. So far the thing is really running great with the 1100 LV kernal and the settings I mentioned above. I'm sure my quadrant will be lower than 1200, but for some reason the 1200 kernal was only stable when I was placing load on the device, actually using it. When it was idle the screen would "permasleep". Very odd. Stress testing on the 1200 LV kernal threw no errors, but I still had idle issues.
Click to expand...
Click to collapse
Maybe check out the 1200SV as well and/or jt's 1200. Heck I tried them all myself at least briefly
saps said:
Maybe check out the 1200SV as well and/or jt's 1200. Heck I tried them all myself at least briefly
Click to expand...
Click to collapse
The SV is working good so far, but where do you get jt's?
SirKronan said:
The SV is working good so far, but where do you get jt's?
Click to expand...
Click to collapse
Right here: http://forum.xda-developers.com/showthread.php?t=804317
Sorry if it is a noob question but
I have the jt's voodoo kernel and just restored my setcpu from the titanium back up...
the max that it gives me is only 1000000....
I thought It should change to 1200000
how can I change it?
if not what should I do to OC this bad boy?
btw I Used the recommended speed...
Thanks
Zirabius said:
Sorry if it is a noob question but
I have the jt's voodoo kernel and just restored my setcpu from the titanium back up...
the max that it gives me is only 1000000....
I thought It should change to 1200000
how can I change it?
if not what should I do to OC this bad boy?
btw I Used the recommended speed...
Thanks
Click to expand...
Click to collapse
Download the 1200 w/ boot animation. This happened to me last night when updating my wife's fascinate. I first downloaded the one without boot animation, which was fine, but only would clock to 1000 and was getting the battery not connected error. So I flashed the 1200 w/boot animation and fixed everything.
mackeydesigns said:
Download the 1200 w/ boot animation. This happened to me last night when updating my wife's fascinate. I first downloaded the one without boot animation, which was fine, but only would clock to 1000 and was getting the battery not connected error. So I flashed the 1200 w/boot animation and fixed everything.
Click to expand...
Click to collapse
Thanks works great now
Sent from my SCH-I500 using XDA App
mackeydesigns said:
Download the 1200 w/ boot animation. This happened to me last night when updating my wife's fascinate. I first downloaded the one without boot animation, which was fine, but only would clock to 1000 and was getting the battery not connected error. So I flashed the 1200 w/boot animation and fixed everything.
Click to expand...
Click to collapse
I just flashed my Fascinate with the 1200 w/ boot animation and then SetCPU from the market but SetCPU only allows my Max slider to 528MHz??? what did i do wrong?
Sorry for another noob question.
rickys08 said:
I just flashed my Fascinate with the 1200 w/ boot animation and then SetCPU from the market but SetCPU only allows my Max slider to 528MHz??? what did i do wrong?
Sorry for another noob question.
Click to expand...
Click to collapse
Think about it for a second... Has it sunk in yet? Didn't think so.
You changed speeds so you need to redetect your speed. Either do that or uninstall the app and reinstall it.
Sent from my SCH-I500 using XDA App
rickys08 said:
I just flashed my Fascinate with the 1200 w/ boot animation and then SetCPU from the market but SetCPU only allows my Max slider to 528MHz??? what did i do wrong?
Sorry for another noob question.
Click to expand...
Click to collapse
that happend too me too man,
what I did was I went to the menu and did an auto speed detect...
and the problem solved! its been running smoothly ever since
So, I guess I'll just C+P my post from the SetCPU thread since no one was able to answer the question there. I figure I might get some help from the EVO crowd since this might be specific to the device.
'So I have a wee bit of an issue with 2.0.4 I think... I just rooted my EVO 4G, installed SetCPU, AutoDetect, main Profile 768/460 set on boot. However, I rebooted and it says in the Notification bar that that's the profile it's running, however when I open up SetCPU the speeds jump between 245 and 998...Is SetCPU not throtleing the CPU correctly?'
Also, the only options for SetCPU I'm getting are userspace, ondemand and performance.
Is there something I did wrong when I rooted it?
What kernel are you using? The reason I ask is because I had the king #12 installed and setcpu didn't seem to be doing anything. Based on the the scaling options it sounds like a Toast kernel. Different kernels get different options. King kernels have about 5 different scaling options. I think for $29.95 he will add a 6th option.
Stock kernel. I haven't gotten around to messing with the kernel or ROM yet. Do I have to be running a modded kernel for SetCPU to function at all?
Shushunmire said:
Stock kernel. I haven't gotten around to messing with the kernel or ROM yet. Do I have to be running a modded kernel for SetCPU to function at all?
Click to expand...
Click to collapse
Well this is very simple then you can't OC the stock kernel. I also don't think that SetCPU can govern a stock kernel. You must flash either Toast or Kings..
SetCPU will govern a stock ROM, just hit menu on its main screen and select Disable Perflock. Disable the perflock and tell it to do so on boot. Then you can change the clock speeds around and profiles will work. Only downside is it still won't overclock, but if you are looking for power savings, this is the way to do it.
superlinkx said:
SetCPU will govern a stock ROM, just hit menu on its main screen and select Disable Perflock. Disable the perflock and tell it to do so on boot. Then you can change the clock speeds around and profiles will work. Only downside is it still won't overclock, but if you are looking for power savings, this is the way to do it.
Click to expand...
Click to collapse
Ya I didn't think you could use setcpu with a stock kernel so that's some good info right there.. thanks.
Thanks! That did it! I wasn't really liking the idea of flashing a custom ROM or kernel to my device just yet, so this is great. I had my fair share of issues with HD2 running custom ROMS and kernels and for now I want something that just works until I get more familiar with the process.
Like the title says, I was just wondering if there was a way to change the default CPU speed on boot permanently? I know I can use SetCPU, but sometimes that hasn't held through a boot and I had to set the speed manually. So, I was hoping there was just some script somewhere I would have to change. But then I got to wondering, would that be possible from my phone? Would I have to build my own kernel? Or would I just be able to decompile the rom in dsixda's kitchen to change a kernel script? Any help is greatly appreciated!
I use ROM Toolbox. It has a ton of stuff including CPU Control and CPU Profiles (like to make it 691MHz max when the screen is off). And you get a lot of other stuff with ROM Toolbox. But you could say the CPU part is like Set CPU. Don't really know if this answered your question. Hope I helped though.
I'm pretty sure CM7 has a built in CPU setting feature in its Cyanogenmod Settings -> Performance menu. It gives you the option to set on boot as well. I've never played around with it so I'm not sure if it'll give you the same problems you're describing now, but it's worth a shot if you don't want the separate app.
Is your phone rooted?
Sent from my Black Ice'd Glacier using XDA App
c707h3j said:
I'm pretty sure CM7 has a built in CPU setting feature in its Cyanogenmod Settings -> Performance menu. It gives you the option to set on boot as well. I've never played around with it so I'm not sure if it'll give you the same problems you're describing now, but it's worth a shot if you don't want the separate app.
Click to expand...
Click to collapse
I think I remember this too.
--sent from my glacier.
You can search all you want and still come up short, I'm trying to use system tuner to change the cpu and gpu settings and I cant find any help on how to use this app. Im running the latest Kaos Droid rom for 4.1.2, the latest Motley kernel and twrp, props to all developers:good:. Im looking for what the optimal settings are and how to use system tuner to change them. Can someone tell me or show me the right thread that can help? Im not sure what the min/max cpu settings should be and I cant seem to find where to change the gpu settings. We are all noobs at some point. I just want to beef my nexus up a little, nothing crazy.
aww for real?
I wouldn't use system tuner for this because it doesn't have the ability to change the GPU speed. I'd recommend TricksterMOD which is available here for free. Depending on your kernel (not sure if motley's kernel has configurable GPU now, it didn't when I used it) you can change different settings. It is personally up to you how you want to configure your device and change things depending on how it runs. Anyway, I'll give you an idea of my settings that I have changed.
CPU - Governor is Interactive (my kernels default but another alternative would be ondemand) running @ 102mhz min - 1600mhz max
IO - Governor is deadline (again default but imo the only one you should use) with cache at 1024.
GPU - 600mhz
VOLTAGES - My kernels defaults.
Make sure that you set the settings to be applied at boot (I use a delay of 1 because it didn't seem to apply without it) and also make sure your kernel has the powerHAL fix included, or else (in the case of trinity kernel) you will need to download this file (this is for Android 4.2.x). This will allow your CPU overclock to stick and not be reset to stock.
Hopefully this helps! But again, just play around with your frequency's and maybe look into voltage tweaking to get your personal balance between performance and power consumption. And if you are going for performance, I'd look at turning off fsync and using the ext4 mount script to boost your I/O dramatically (this will result in things such as faster app installs)
smt8544 thanks alot man! now I can start somewhere, I didnt wanna do anything stupid without some knowledge, I appreciate it!
Hi.
I'm running stock 6.0.1 ROM with latest squid kernel and I'm having problem with hispeed_freq settings, when I choose a desired frequency it won't stick to that, it always reverts to 1459200MHz. I followed a guide for interactive governor from http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/post64279960#post64279960 and the results are great except when hispeed_freq starts to screw itself up, the big CPU is then always stuck on 1459200MHz frequency which destroys the purpose of the guide. It happens also on stock based custom roms and that probably means it is ROM related. The same happens on stock and ultra kernels, the weird part is that it somehow worked normally on stock 6.0 and squid kernel even though not from the day one. Any ideas how to make hispeed_freq to stick to 533333MHz?
http://imgur.com/SS1ZWaf
EDIT: title should be CPU governor tunables on stock and custom kernels problem. My keyboard is dying.
ViperX85 said:
Hi.
I'm running stock 6.0.1 ROM with latest squid kernel and I'm having problem with hispeed_freq settings, when I choose a desired frequency it won't stick to that, it always reverts to 1459200MHz. I followed a guide for interactive governor from http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/post64279960#post64279960 and the results are great except when hispeed_freq starts to screw itself up, the big CPU is then always stuck on 1459200MHz frequency which destroys the purpose of the guide. It happens also on stock based custom roms and that probably means it is ROM related. The same happens on stock and ultra kernels, the weird part is that it somehow worked normally on stock 6.0 and squid kernel even though not from the day one. Any ideas how to make hispeed_freq to stick to 533333MHz?
http://imgur.com/SS1ZWaf
EDIT: title should be CPU governor tunables on stock and custom kernels problem. My keyboard is dying.
Click to expand...
Click to collapse
It does stick if you use profiles in k.a.,but every time you launch an app its reverting for about 2 seconds showing the 1459Mhz and reverts back to normal when the app is finished loading. It works but still not perfect and im googling for days to solve this issue.It has something to do with a stock qualcom script that tries to overwrite the settings when you launch an app. I found the files to edit the go_hispeed_freq and i also have read and write acces but every time I try to change it just reverts back. Very frustrating.
Its located in: /sys/devices/system/cpu
Strange thing is even when you have set the correct hispeed freq and it works fine, it doesnt change it in the sys/devices/system/cpu directory when using a file browser.
Hello Viper if you are still tweaking with this governor I think I found the cause. Takes a little risk to fixnbecause you have to use stock android interactive and on demand standard settings instead of Motorola's settings. Found a few posts people with similar issues and they deleted (I renamed it for backup) the "init.qcom.post.boot.sh" file. Seems like this file gets messed up when you flash a custom kernel. You can check it with a text editor and see its constantly showing very strange freqs and switching between ondemand and interactive constantly (weird). After I renamed it to .bak everything sticks after applying the profile and CPU monitor apps also seems to react different with lot less ramping up the cores and the 1.4 freq doesn't show up anymore like before.
Sickaxis79 said:
Hello Viper if you are still tweaking with this governor I think I found the cause. Takes a little risk to fixnbecause you have to use stock android interactive and on demand standard settings instead of Motorola's settings. Found a few posts people with similar issues and they deleted (I renamed it for backup) the "init.qcom.post.boot.sh" file. Seems like this file gets messed up when you flash a custom kernel. You can check it with a text editor and see its constantly showing very strange freqs and switching between ondemand and interactive constantly (weird). After I renamed it to .bak everything sticks after applying the profile and CPU monitor apps also seems to react different with lot less ramping up the cores and the 1.4 freq doesn't show up anymore like before.
Click to expand...
Click to collapse
Hi Sickaxis79 and sorry for the late reply, I've been working a lot lately. I gave up on interactive settings b/c my battery life was awful on interactive gov . but now that you mentioned this i'll give it another go this weekend and will let you know what are the results.
Can you just tell me where can I locate init.qcom.post.boot.sh file?
Thanks for showing interest to help me out, I appreciate it bro.
I was wrong,lol. Don't rename it or your battery start to drain when idle.
It contains all your governor settings and how your big.LITTLE cores work together (HMP Scheduler).
The good part is that you can edit this file and search for your model.nr "msm8939" with a unix text editor and enter all governor settings directly into this post_boot.sh file (i use quickedit app or notepad++ for pc) and you don't need a kernel manager anymore. The hispeed_freq will also stick and only for a few seconds you can see it when you switch apps, but it doesn't revert back to 1,4MHz permanently like before.
The file is located in /system/etc/init.qcom.post_boot.sh
Peace