Develop Bugs

[Q] Calk's Preset Profiles to save battery question?

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.

SetCpu sets my clock speed passed the limit I set

So I just got my galaxy S3 sgh-i747, I have rooted it, installed a custom kernel (ktoonsez Sammy kernel) and installed the pro version of setCPU.
The problem I am having is that even though I set an overclock limit to 1674 mHz, setCPU will occasionally boost it to 1890 for no apparent reason. This causes my phone to heat up immensely and renders it unstable.
I have also tried profiles (one for screen on, other for screen off) yet even with the profiles and notifications I get, the app still acts up. I am wondering if the widget and the app are just glitchy and displaying those speeds but not really setting the CPU at that level...
Here are some screenshots for clarification:
Edit: Sigh.. I cannot post screenshots..
But basically in my screens I show that the slider is set to a max of 1674 yet in another screenshot it shows that my time spent at 1890 mhz is 40%.... yikes
Has anyone experienced this before? How would I go about fixing this?
Thanks for any help!

Reymundo911 said:
So I just got my galaxy S3 sgh-i747, I have rooted it, installed a custom kernel (ktoonsez Sammy kernel) and installed the pro version of setCPU.
The problem I am having is that even though I set an overclock limit to 1674 mHz, setCPU will occasionally boost it to 1890 for no apparent reason. This causes my phone to heat up immensely and renders it unstable.
I have also tried profiles (one for screen on, other for screen off) yet even with the profiles and notifications I get, the app still acts up. I am wondering if the widget and the app are just glitchy and displaying those speeds but not really setting the CPU at that level...
Here are some screenshots for clarification:
Edit: Sigh.. I cannot post screenshots..
But basically in my screens I show that the slider is set to a max of 1674 yet in another screenshot it shows that my time spent at 1890 mhz is 40%.... yikes
Has anyone experienced this before? How would I go about fixing this?
Thanks for any help!
Click to expand...
Click to collapse
Im set 486 min and 1.89 max also..
sent from my red ass oc'd s3

Try voltage control, it's what ktoonsez recommends for his kernel and works like a champ for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Reymundo911 said:
So I just got my galaxy S3 sgh-i747, I have rooted it, installed a custom kernel (ktoonsez Sammy kernel) and installed the pro version of setCPU.
The problem I am having is that even though I set an overclock limit to 1674 mHz, setCPU will occasionally boost it to 1890 for no apparent reason. This causes my phone to heat up immensely and renders it unstable.
I have also tried profiles (one for screen on, other for screen off) yet even with the profiles and notifications I get, the app still acts up. I am wondering if the widget and the app are just glitchy and displaying those speeds but not really setting the CPU at that level...
Here are some screenshots for clarification:
Edit: Sigh.. I cannot post screenshots..
But basically in my screens I show that the slider is set to a max of 1674 yet in another screenshot it shows that my time spent at 1890 mhz is 40%.... yikes
Has anyone experienced this before? How would I go about fixing this?
Thanks for any help!
Click to expand...
Click to collapse
You running old version of sammy kernel ? get newest 8-15b , i to use setcpu and have no such problems , very early versions of his kernel did that.

Post a link to the new kernel...8-11 buikd is fine setcpu and system tuner is the best 2 there is imo
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] Franco Kernel - Magically Changing CPU

I've been using Franco kernel for a long time now, on various ROMs. My current ROM is JBSourcery (4.1.1); I've always had this problem though, no matter if the kernel was on a milestone build or nightlies. The Max cpu and governor change almost randomly! I'll set the max cpu to 1536 or 1612 and after a few hours or a few minutes it changes on its own!
For example, I changed the CPU to 1612 max and 384 min with 'interactive' governor.
Later that day (less than an hour later) it starts lagging like crazy, so I look at the settings and it's changed to 1036 max, 728 min and the 'ondemand' governor. This happens frequently, usually after I've locked it for awhile, and reopened it. It's starting to drive me crazy!
I have "set cpu settings on boot" checked, as well as "set governor control on boot" This is happening on all the kernel versions I've tried so far, including 262, 264, 268 and Milestone5. What on earth is going on?!

dmesg or it never happened
post in franco's thread, way better chances of getting his/other users attention than here.

TimjTech said:
I've been using Franco kernel for a long time now, on various ROMs. My current ROM is JBSourcery (4.1.1); I've always had this problem though, no matter if the kernel was on a milestone build or nightlies. The Max cpu and governor change almost randomly! I'll set the max cpu to 1536 or 1612 and after a few hours or a few minutes it changes on its own!
For example, I changed the CPU to 1612 max and 384 min with 'interactive' governor.
Later that day (less than an hour later) it starts lagging like crazy, so I look at the settings and it's changed to 1036 max, 728 min and the 'ondemand' governor. This happens frequently, usually after I've locked it for awhile, and reopened it. It's starting to drive me crazy!
I have "set cpu settings on boot" checked, as well as "set governor control on boot" This is happening on all the kernel versions I've tried so far, including 262, 264, 268 and Milestone5. What on earth is going on?!
Click to expand...
Click to collapse
what are you using to set your cpu speed?

simms22 said:
what are you using to set your cpu speed?
Click to expand...
Click to collapse
The Franco Kernel Updater...paid for it

TimjTech said:
The Franco Kernel Updater...paid for it
Click to expand...
Click to collapse
then its your rom thats broken, probably doesnt have the powerhal fix. some cpu control apps include the fix in the app for that reason, like the trinity kernel toolbox app. i dont think francos app includes it. or the fix could be as simple as updating your busybox.

simms22 said:
then its your rom thats broken, probably doesnt have the powerhal fix. some cpu control apps include the fix in the app for that reason, like the trinity kernel toolbox app. i dont think francos app includes it. or the fix could be as simple as updating your busybox.
Click to expand...
Click to collapse
Thanks! I'll try the trinity toolkit for a week and see what happens.

Overclocking Instability

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

Unable to stick at lower CPU freq

I am currently using this rom http://forum.xda-developers.com/showthread.php?t=2306650 , but i doubt its the rom fault.
Using the MIUI settings, Antutu CPU master, or ROM ToolBox, applying a lower CPU max freq will not stick.
Ex: The max is 1890mhz, but i want it at 1566mhz for the max. After turning the phone off and on, the max CPU freq. goes back to the original 1890mhz. With a reboot, it sticks, half the time.
What do i do? Please reply ASAP, my S4 gets hot while playing games so i like to underclock it.

With many years of experience, the best thing I can tell you is to not place a MHz cap that is too high. Your phone can potentially be a potato if you're not careful.
Sent from my GT-I9505G using Tapatalk

HenryTheUnicorn said:
I am currently using this rom http://forum.xda-developers.com/showthread.php?t=2306650 , but i doubt its the rom fault.
Using the MIUI settings, Antutu CPU master, or ROM ToolBox, applying a lower CPU max freq will not stick.
Ex: The max is 1890mhz, but i want it at 1566mhz for the max. After turning the phone off and on, the max CPU freq. goes back to the original 1890mhz. With a reboot, it sticks, half the time.
What do i do? Please reply ASAP, my S4 gets hot while playing games so i like to underclock it.
Click to expand...
Click to collapse
Download CPU controller app from the market. It will reset your CPU upon screen on.
Sent from my SGH-M919 using Tapatalk

elesbb said:
Download CPU controller app from the market. It will reset your CPU upon screen on.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Everything I've ussed applies settings on boot, but it wont frickin work sometimes.

HenryTheUnicorn said:
Everything I've ussed applies settings on boot, but it wont frickin work sometimes.
Click to expand...
Click to collapse
SetCPU has different profiles to configure. And which ROM are you on? There might be an init.d script adjusting the frequencies. SetCPU will apply them AFTER any init.d scripts are ran so that should fix it. I loved SetCPU till ktoonsez made his own app.

elesbb said:
SetCPU has different profiles to configure. And which ROM are you on? There might be an init.d script adjusting the frequencies. SetCPU will apply them AFTER any init.d scripts are ran so that should fix it. I loved SetCPU till ktoonsez made his own app.
Click to expand...
Click to collapse
the rom i am on is in the first post.
How do i check the script if it is?
Meh, till i figure that out, time to use SetCPU. I MUCH prefer Antutu Cpu Master Pro, a profile for overheating? Hell yes, i set mine to 1.2ghz at 105 degrees F. and 1.5/1.6ghz when its normal. Helped ALOT

HenryTheUnicorn said:
the rom i am on is in the first post.
How do i check the script if it is?
Meh, till i figure that out, time to use SetCPU. I MUCH prefer Antutu Cpu Master Pro, a profile for overheating? Hell yes, i set mine to 1.2ghz at 105 degrees F. and 1.5/1.6ghz when its normal. Helped ALOT
Click to expand...
Click to collapse
I believe setCPU has that profile as well
Sent from my SGH-M919 using Tapatalk

elesbb said:
I believe setCPU has that profile as well
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Oh darn. It worked for a bit. Now instead of going back to normal max frequency after a reboot or boot up, it does it when I'm using the phone.
Does PAC ROM have this issue? If not, I'll use pac rom instead. Or it may be a kernel problem? Idk much about android stuff

HenryTheUnicorn said:
Oh darn. It worked for a bit. Now instead of going back to normal max frequency after a reboot or boot up, it does it when I'm using the phone.
Does PAC ROM have this issue? If not, I'll use pac rom instead. Or it may be a kernel problem? Idk much about android stuff
Click to expand...
Click to collapse
Sounds like the kernel is overriding certain things in different scenarios. I'd try a different kernel.