Related
I have a HAVS kernel (Net's 4.2.2 SBC CFS Aggressive HAVS) and as I understand it any sort of CPU Tweaking application will cause conflict and probably a system crash, correct?
Also, can some recommend me any applications that compliment Juice Defender well. I have Juice Plotter already. I am looking for an aggressive auto task killer that's customizable along with any other suggested applications. Thank you!
A system crash is a possibility but they will basically just counteract each other and either make your battery life worse or give a performance hit.
SetCPU helps dynamically underclock/overclock based on certain scenarios. You can set what scenarios you want. Another option is AutoKiller. It isn't Auto Task Killer. Its a different application. Not quite sure how this works but you can research it. However Froyo does a good job managing most applications.
But if you are looking for customization I would go with SetCPU and AutoKiller
Thank's however since I'm running a HAVS kernel I won't use SetCPU. However I will look into Autokiller. Thanks
Vulf said:
Thank's however since I'm running a HAVS kernel I won't use SetCPU. However I will look into Autokiller. Thanks
Click to expand...
Click to collapse
o.o a ton of people use set cpu with havs... its not setting voltages... its setting the cpu speed...
I just installed setcpu and ran it. My phone crashed about 10 seconds after I allowed root access. Tried twice more with same results.
aimbdd said:
o.o a ton of people use set cpu with havs... its not setting voltages... its setting the cpu speed...
Click to expand...
Click to collapse
Its the governors that conflict. Not sure on the exact technical specifics but think of it like OCing a comp.
Some mobos have dynamic OCing. They adjust voltages based on CPU draw. If SetCPU sets CPU speed but HAVS reduces voltage... it would cause a crash. Its always better to have one thing deal with both CPU and voltage.
I'm not a full blown expert with kernels and how they function. All I know is to not mess around with SetCPU + HAVS kernels. It was always unstable or a massive battery drain for me based on my testing.
sekigah84 said:
Its the governors that conflict. Not sure on the exact technical specifics but think of it like OCing a comp.
Some mobos have dynamic OCing. They adjust voltages based on CPU draw. If SetCPU sets CPU speed but HAVS reduces voltage... it would cause a crash. Its always better to have one thing deal with both CPU and voltage.
I'm not a full blown expert with kernels and how they function. All I know is to not mess around with SetCPU + HAVS kernels. It was always unstable or a massive battery drain for me based on my testing.
Click to expand...
Click to collapse
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
lovethyEVO said:
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
Click to expand...
Click to collapse
Ahh there. someone more knowledgable then me explains it perfectly.
I've run set cpu plus haves kernel for the last month... as have almost everyone using savagedzen.. thats what they recommend. If it was causing issues i am sure we would know by now. 100%stable... 0 random reboots! (well... accept for when i didn't follow directions xD)
aimbdd said:
Ahh there. someone more knowledgable then me explains it perfectly.
I've run set cpu plus haves kernel for the last month... as have almost everyone using savagedzen.. thats what they recommend. If it was causing issues i am sure we would know by now. 100%stable... 0 random reboots! (well... accept for when i didn't follow directions xD)
Click to expand...
Click to collapse
I believe you and am not discrediting you but how come when I run SetCPU on a kernel with HAVS, it crashes? (Tried 4.3.1 and 4.2.2.) I moved the maximum value from the default 944 by maybe one or 2 notches up and the device freezes and crashes. Maybe Netarchy's kernels aren't compatible with CPU Tweaking programs? Anyone out there running a Netarchy Kernel w/ HAVS + SetCPU successfully?
Vulf said:
I believe you and am not discrediting you but how come when I run SetCPU on a kernel with HAVS, it crashes? (Tried 4.3.1 and 4.2.2.) I moved the maximum value from the default 944 by maybe one or 2 notches up and the device freezes and crashes. Maybe Netarchy's kernels aren't compatible with CPU Tweaking programs? Anyone out there running a Netarchy Kernel w/ HAVS + SetCPU successfully?
Click to expand...
Click to collapse
Again, it is not setcpu it is your settings. You said you moved the slider "one or two notches up" (overclock) from the default 944? The evos default max is 998. Either way, with what you said you are overclocking and your device cannot handle the overclocked speed.
Like I said, you can do the exact same thing that setcpu does through terminal emulator. Instead of blame setcpu you should observe the speed/governor combo you are using.
I can oc my evo to 1.26 on my personal kernel without it rebooting on certain governors but on others it would reboot randomly and I don't set cpu parameters through setcpu, I use te, init scripts, and tasker.
lovethyEVO said:
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
Click to expand...
Click to collapse
Couldn't have said it better. The common misconception around these parts is that SetCPU has some negative effect on kernels with HAVS and this is just untrue.
Maybe I'm getting some terrible luck. I've always gotten negative results from using both SetCPU and HAVS. Tried different settings and recommended settings from others. As well as trying to tweak it myself. Not working so I just removed it and HAVS worked better on its own.
Sorry for the misinformation.
sekigah84 said:
Maybe I'm getting some terrible luck. I've always gotten negative results from using both SetCPU and HAVS. Tried different settings and recommended settings from others. As well as trying to tweak it myself. Not working so I just removed it and HAVS worked better on its own.
Sorry for the misinformation.
Click to expand...
Click to collapse
The common practice with setcpu is to use it to underclock when sleeping. Depending on the governor you use (besides powersave) you are actually causing the cpu to struggle when completing tasks if you limit the max to 245 for example. During sleep if it needs to perform a task and that task would normally complete in 1 second at 998 mhz imagine how much longer it would take if it was capped at 245.
I have had better results not underclocking while sleeping. I would suggest using setcpu to specify to use the conservative governor when sleeping, ondemand/interactive/smartass when screen on (depending on which one you want), and interactive/ondemand while charging without under/overclocking at all and using the default freqs (245 - 998). I'm certain you would be surprised at how your evo behaves after that.
I don't know though... if race to idle applied here why would phone manufacturers ever under clock their phone? It kind of confuses me. Rti applies to computers but not phones? doesn't make sense.
aimbdd said:
I don't know though... if race to idle applied here why would phone manufacturers ever under clock their phone? It kind of confuses me. Rti applies to computers but not phones? doesn't make sense.
Click to expand...
Click to collapse
My last post may have been a bit confusing so I will clarify. When I said underclock I was referring to the practice of capping the max freq to 245 which is what most people do. If you cap the freq at 245 you are essentially underclocked all the time and would cause your cpu to work harder.
The evo underclocks automatically when the cpu load is low enough (idle for example) to save on power, reduce temps, and to basically keep the system running. But I would assume that most of us who have used setcpu have seen how lousy the evo runs when it can't scale up (locked at 245) when using the evo. The governors will underclock the cpu on their own if the device reports it does not need the higher freqs and this occurs during sleep/screen off as well.
Ugh this is quite frustrating. Perhaps it's the current kernel I'm using that's the problem?
Vulf said:
Ugh this is quite frustrating. Perhaps it's the current kernel I'm using that's the problem?
Click to expand...
Click to collapse
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
freeza said:
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then it you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
Click to expand...
Click to collapse
I'm not sure how I would go testing my kernel? I mean I've been using it since yesterday morning and there haven't been any FC's/phone crashes or anything strange so I guess the aggressive HAVS works well with my phone. I'll try upgrading to 4.3.2. I'm assuming it works fine for you?
freeza said:
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then it you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
Click to expand...
Click to collapse
This.
Very sound advice and yes some evos can't undervolt as well as others. Always remember too that the stock kernel for the evos use CFS. If you are using a bfs kernel that could also cause issues. Some evos run better with bfs versus cfs but it's really going to come down to the amount of time you want to put into testing and confirming what your evo likes.
Vulf said:
I'm not sure how I would go testing my kernel? I mean I've been using it since yesterday morning and there haven't been any FC's/phone crashes or anything strange so I guess the aggressive HAVS works well with my phone. I'll try upgrading to 4.3.2. I'm assuming it works fine for you?
Click to expand...
Click to collapse
Yeah, it does. How far are you trying to overclock before your phone freezes/reboots?
Notes about Battery Saver script
Can be used with kernels that have init.d support
It completely eliminates the need for an application to set CPU speeds or profiles
Easily customizable if you use a text editor(scripts located in /system/etc/init.d)
It will set Max CPU speed to 500MHz & Min CPU speed to 200MHz when a sleep
If SetCPU, Overclock Widget, Android Overclock or QuickClock Advanced Overclock are detected, the script is ignored, so it will not affect them
Preset profiles are:
1.2GHz - 100-85%
1.0GHz - 84-36%
800MHz - 35-0%
And just an FYI, even at 800MHz, the phone still operates very well & smooth but the battery saving are the real benefit
Click to expand...
Click to collapse
Does this mean that if I don't use Set CPU or any app that undervolt it, the phone will AUTOMATICALLY drop the CPU speed according to my battery level:
1.2GHz - 100-85%
1.0GHz - 84-36%
800MHz - 35-0%
Another word, it will automatically drop CPU speed to 800 MHZ when my battery level is 35-0% in order to save battery?
It won't "Drop" the CPU speed, it will lower the Maximum speed the CPU is allowed to ramp up to.
Drumrocker said:
It won't "Drop" the CPU speed, it will lower the Maximum speed the CPU is allowed to ramp up to.
Click to expand...
Click to collapse
So if I am not doing CPU intensive stuff and just play simple games, email, web surfing phone call, then I am not going to see battery improvement since my CPU probably don't ramp past 800MHZ anyway when I am just doing simple stuff.?
Calk's ROM undervolts the CPU at all speeds so that in itself should help a little with battery life. But you are correct, if you are not doing CPU intensive tasks the CPU probably isn't spending much time at the higher speeds.
There is an app called CPUSpy which shows how much time the CPU has spent in each frequency state.
Your phone will ramp up to 1200 mhz more than you think. When it loads a webpage, it will ramp up to 1200, when it's loading your "simple" game, it will max out for a bit, etc.
It might not stay there for very long, but still. The nice thing about Calkuins rom is that even at 800 mhz, the phone is super smooth and lag free. In fact I just turn setcpu down to 800 all the time.
Let me research setcpu and play around with it. Thanks again for the quick answers.
clamknuckle said:
Your phone will ramp up to 1200 mhz more than you think. When it loads a webpage, it will ramp up to 1200, when it's loading your "simple" game, it will max out for a bit, etc.
It might not stay there for very long, but still. The nice thing about Calkuins rom is that even at 800 mhz, the phone is super smooth and lag free. In fact I just turn setcpu down to 800 all the time.
Click to expand...
Click to collapse
The way Calkulin's rom scripts are setup, setcpu gets reset on every reboot, even if you have it set to boot settings. The scripts installed will still take priority and the old rules apply, just to let you know. So you would have to set setcpu every boot for it to work, that or remove the scripts.
Sent from my SPH-D710 using xda premium
Team era... Does the same idea apply to the blazer 2.0 battery saving script? or does tegrak break it?
Sent from my SPH-D710 using xda premium
I havnt opened that rom, but Im gonna say the same applies, I remove those scripts, 2 will affect the cpu state.
edit, let me clarify, the scripts take prority, even if the app makes a script for init.d, the original script will take over on a reboot. So the script breaks tegrak, setcpu, and voltage control unless you set the app on every reboot.
I am running Calks 2 and desperado kernel. I notice when using setcpu, if you have it set on boot, it will override calks script.
His script does work well on saving battery life though. I ran oc'd while at 20% and still had 1700mhz blazing on performance gov.
I'd still use Calks script over setcpu or tegrak only due to the fact im too sporatic with my phone use to create optimal profiles to fit the way and when i need to use the device.
mindgrind said:
I am running Calks 2 and desperado kernel. I notice when using setcpu, if you have it set on boot, it will override calks script.
His script does work well on saving battery life though. I ran oc'd while at 20% and still had 1700mhz blazing on performance gov.
I'd still use Calks script over setcpu or tegrak only due to the fact im too sporatic with my phone use to create optimal profiles to fit the way and when i need to use the device.
Click to expand...
Click to collapse
Actually in my own testing setcpu will not override the scripts, the slider may stay the same, but trust me, it goes back to 800 (or 1200 over 86%batt), Ive tested it several times. If you want proof Ill tell you how to figure it out. I know Im not respected yet, but I am someone that is known under another name that is highly respected, so, take it as you will.
Sent from my SPH-D710 using xda premium
Era, what's your suggestion for keeping the battery saving scripts running and getting a 1500 ish over clock when needed... something that can do both without having to physically change setcpu everytime. I basically want to permanently over clock to 1.5 and still save as much battery as possible when i have the screen off or it is charging. Idk if setcpu profiles work on this phone because i know they did not work correctly on the galaxy s. And one final question... what voltages do u run at what speeds on the "desperado" kernel to undervolt efficiently?
Sent from my SPH-D710 using xda premium
TeamERA said:
Actually in my own testing setcpu will not override the scripts, the slider may stay the same, but trust me, it goes back to 800 (or 1200 over 86%batt), Ive tested it several times. If you want proof Ill tell you how to figure it out. I know Im not respected yet, but I am someone that is known under another name that is highly respected, so, take it as you will.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
ERA. I wasn't looking to say that you were wrong in any way shape or form. I would be interested to know how you seen this as I am still in the beginning phases of learning the android system. I do plan on writing my own kernal/roms but I was actually sharing what my logical thought process would have been given the apps and system info I had avail.
I have a little ways to go in understanding the structure and FS of droid. Time is everyones enemy. Thanks for the correction again!
I havnt opened that rom, but Im gonna say the same applies, I remove those scripts, 2 will affect the cpu state.
edit, let me clarify, the scripts take prority, even if the app makes a script for init.d, the original script will take over on a reboot. So the script breaks tegrak, setcpu, and voltage control unless you set the app on every reboot.
I'm currently running Calkulin's rom v2.5, and even at 41% battery I notice the cpu still hits 1.2 Ghz. Is his script activated by default or am I overlooking something? I also have nothing like setcpu installed.
I am by no means an expert and always thought SetCPU was useful - I don't use it to overclock - just use it primarily to limit the processor when the screen is off. However, with ICS and Jelly Bean and the improvements related to it, is there still a need for SetCPU? Again, not just to overclock, etc, but to limit the processor when the screen is off to attempt to save battery. Thoughts?
I personally have felt no need for SetCPU once I upgraded from my first Android device - a MyTouch3G.
The schedulers in most custom kernels nowadays already throttle back the CPU speeds when the screen is off. As for overclocking, it IMO doesn't make any noticeable difference anymore so I don't even bother.
athakur999 said:
I personally have felt no need for SetCPU once I upgraded from my first Android device - a MyTouch3G.
The schedulers in most custom kernels nowadays already throttle back the CPU speeds when the screen is off. As for overclocking, it IMO doesn't make any noticeable difference anymore so I don't even bother.
Click to expand...
Click to collapse
But, what if you don't use the scheduler in the custom rom, is SetCPU still redundant?
I use it to set the voltages. If the hotplugx worked well with it I'd use it for profiles but unfortunately it'll crash.
Hey I just bought a 32 GB Gnex and got it yesterday but it seems to be unstable at anything above the stock max frequency of 1230 MHz. I've tried Paranoid Android and last night's CM10 nightly and they would both freeze and immediately reboot upon setting it to 1305 MHz. I then flashed the Zen kernel on top of CM10 and I like that it can go up to 1.8 GHz but whenever I set anything beyond 1.23 GHz it starts to lag for about 1-3 seconds. When I knock it back down to 1.23 GHz everything is fine again.
This is the first OMAP device I have since I had the OG Droid back in 09, I loved how they were extremely overclockable and I'm going to be pretty sad if mine has to stay at stock speeds. I've tried using JRummy's ROM Toolbox Pro and the built in Performance settings to try and set the frequencies but it doesn't seem to make a difference on which one I use. I've been using the OnDemand and Interactive(x) Governors.
Is this a known problem or am I alone on this?
some CPUs have a higher tolerance than others for overclocking. looks like you got one of the super low tolerance ones.
I hope that's not the case :-/
brando56894 said:
Hey I just bought a 32 GB Gnex and got it yesterday but it seems to be unstable at anything above the stock max frequency of 1230 MHz. I've tried Paranoid Android and last night's CM10 nightly and they would both freeze and immediately reboot upon setting it to 1305 MHz. I then flashed the Zen kernel on top of CM10 and I like that it can go up to 1.8 GHz but whenever I set anything beyond 1.23 GHz it starts to lag for about 1-3 seconds. When I knock it back down to 1.23 GHz everything is fine again.
This is the first OMAP device I have since I had the OG Droid back in 09, I loved how they were extremely overclockable and I'm going to be pretty sad if mine has to stay at stock speeds. I've tried using JRummy's ROM Toolbox Pro and the built in Performance settings to try and set the frequencies but it doesn't seem to make a difference on which one I use. I've been using the OnDemand and Interactive(x) Governors.
Is this a known problem or am I alone on this?
Click to expand...
Click to collapse
you need to disable smart reflex mpu if you want to overclock. smart reflex doesnt know overclocking, so it sets your voltages to low for an overclocked cpu. thus, instant instability.
to disable smart reflex manually, use a terminal emulator. type su(press enter) then type these 3 lines and press enter after each..
*
echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
0 to disable, 1 to enable.
btw, some cpu control apps give you options to disable/enable smart reflex.
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
edit: still unstable at 1.42 GHz, also what apps would those be that allow this? Antutu CPU Master Pro only has an option to disable PerfLock.
the way to overclock is to keep moving in small increments upward and burn testing them to check for stability. Don't go straight for a 50% overclock. move up and find your threashold, and when you do start tweaking to see if you can slowly creep beyond that
brando56894 said:
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
Click to expand...
Click to collapse
The 3 lines would be:
Code:
echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
echo "0" > /sys/kernel/debug/smartreflex/sr_core/autocomp
echo "0" > /sys/kernel/debug/smartreflex/sr_iva/autocomp
Frankly, though, don't expect 1.8GHz to be stable.
Your particular device's components might not hold it together with that oc.
Sent from my i9250
Darunion said:
the way to overclock is to keep moving in small increments upward and burn testing them to check for stability. Don't go straight for a 50% overclock. move up and find your threashold, and when you do start tweaking to see if you can slowly creep beyond that
Click to expand...
Click to collapse
Yea I know (I used to OC the CPU on my PC), I just wanted to go for something big to see if it could handle it.
Edit: seems to be stable at 1.4 GHz, I'm going to keep increasing it to see what the limit is. I'm assuming i'd have to turn off smartreflex on each boot so I should probably put it in a script in /etc/init.d correct?
brando56894 said:
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
edit: still unstable at 1.42 GHz, also what apps would those be that allow this? Antutu CPU Master Pro only has an option to disable PerfLock.
Click to expand...
Click to collapse
the trinity kernel toolbox lets you disable/enable smart reflex. plus, extremely few gnex will oc to 1.8ghz. and on top of that, to oc even to 1.4 or 1.5ghz, youll need to adjust your voltages to get yourself stable. every device likes different voltages.
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
i can oc my gnex(using trinity kernel) to 1.803ghz.. but to use stable for every day, 1.689ghz is a good speed for my device. a majority of devices wont even oc that high and stable. stable being the key word.
brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
I'd find it surprising that you got 4 different overclock levels stable in 30 minutes. There's a difference between "it boots", "it boots and runs some apps", and "stable".
brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
Is she impressed by your turbo-nerd status?! :silly:
Haha she was an iSheep but I made her get an SGS3 and I turned her into an Android geek, now she flashes ROMs on her own lol
Cilraaz said:
I'd find it surprising that you got 4 different overclock levels stable in 30 minutes. There's a difference between "it boots", "it boots and runs some apps", and "stable".
Click to expand...
Click to collapse
Yea it wasn't stable in the true sense of the word, I meant it just didn't freeze every minute or so.
Sent from my Galaxy Nexus using Tapatalk 2
I'm running the 11/4 build of Paranoid Android with v3.0.51-ZenSeries v4 Tuna and I having problems setting CPU frequencies via Trinity Kernel Toolbox. The frequency will stick until I switch to another app, then when I come back to the app it will be at the stock max frequency. I am also unable to use the built in frequency tuner when using TKT.
I've tried stress testing it with stability test and even when the frequencies will stick in TKT (ex. 1.4 GHz) Stability Test will report that its at 1.1 GHz. WTF is going on here? I have all three of the smart reflex values disabled.
brando56894 said:
I'm running the 11/4 build of Paranoid Android with v3.0.51-ZenSeries v4 Tuna and I having problems setting CPU frequencies via Trinity Kernel Toolbox. The frequency will stick until I switch to another app, then when I come back to the app it will be at the stock max frequency. I am also unable to use the built in frequency tuner when using TKT.
I've tried stress testing it with stability test and even when the frequencies will stick in TKT (ex. 1.4 GHz) Stability Test will report that its at 1.1 GHz. WTF is going on here? I have all three of the smart reflex values disabled.
Click to expand...
Click to collapse
dont use PA cpu settings. do you have any other cpu control apps installed? make sure theres nothing enabled in PA cpu settings, nothing. then reboot. wait 2-3 after bootup then open tkt and try using it. is the problem still there?
It seems to be sticking now for the moment, but I haven't had anything in PA CPU settings before I rebooted anyway. I do not have any other CPU OC apps installed either. Stability test is reporting the correct frequency also. Thanks.
brando56894 said:
It seems to be sticking now for the moment, but I haven't had anything in PA CPU settings before I rebooted anyway. I do not have any other CPU OC apps installed either. Stability test is reporting the correct frequency also. Thanks.
Click to expand...
Click to collapse
sweet.
if you were checking before 3 minutes after bootup, then that was the issue. whatever it was, lets hope it doesnt come back.
I was setting the values after the phone had been up for hours, idk what the problem was :-\q
So I have found that recently every kernel I try to over clock with will cause bad performance on my phone. I am judging this based on benchmarks which should improve when you over clock (I know benchmarks aren't everything, just using them to compare). Every time I over clock to 1.89 it automatically reboots no matter what kernel or rom I am running. No one else in the kernel thread has this issue. If I run benchmarks with the max clock anything above the stock 1.5Ghz makes my benchmark performance absolutely drop. I have tried:
-multiple kernels and ROM combinations
-multiple CPU managers (ROM toolbox to CM performance control)
-multiple bench markers
Did I somehow destroy my CPU on higher clocks somehow?
And I know I don't need OC for good performance, I am just wondering what's up here. It wasn't always like this.
It's not necessarily anything you did. Not all devices are created equally. Some phone can run at 2.1GHZ and get amazing battery life. You just got dealt a bad phone that doesn't over clock well.
Sent from my SAMSUNG-SGH-I747 using xda premium
Yes, if you go over 1890Mhz your phone will restart or get stuck in a bootloop. As the person above said is right. Some phones can go up to 2000MHz and some can't. My Gs3 can overclock to 1890 but I keep mine at 1809.
1. Benchmark apps have no use at all.
Its literally just numbers thrown at you. They have no reflection on real world performance.
2.No one phone is the same. Your phone maybe able to go up to 1.8 with out an issue, but other phones might not even make it past 1.7 I even know of a GS3 that runs at 2.1Ghz with out a problem.
3.OC isn't really needed on an S3 if you're having lag issues or anything Odin back to stock and start again.
I personally run my S3 at 1.1Ghz.
I use custom kernels to under clock and not over as over clocking can drain your battery. Your phone will always reboot past 1.8 regardless of the kernel. That's just how your phone works.
Galaxy S3 / AoCP / V4A / Turbocharged