Hey Guys. I know there are posts about over clocking and that there are threads like this in the other device forums.. BUT
Now that the new CyanogenMOD CM6.1 is out I was wondering what everyone is doing for their SETCPU profiles.
Can it please be time for us to make a thread like this for the Aria?
To start out, I'm confused about the order of my profiles.
(sorry but i don't have screen capture on the aria yet. anyone have a suggestion on what to use, PM me.)
here is what i currently have going on, highest priority first
100) Temp >50"C = 122"F then.. max 600, min 245, ondemand
75) screen off = max 245, min 245, ondemand
50) charging/full = max 864, min 245, ondemand
40) batt < 10% = max 245, min 245, powersave
30) batt < 25% = max 480, min 245, ondemand
20) batt < 50% = max 600, min 245, ondemand
so my biggest concern is if the temp gets too hot.. scale back to the default max of 600mhz.
if the screen is off then i'm not using my phone so slow the roll
if the batt is full or charging and the screen is on then FULL SPEED AHEAD!!!
if the batt is less than 10%, slow down as much as possible
if the batt is less than 25%, take it easy to conserve power
if the batt is less than 50%, bring it back down to the default max of 600mhz
does that make sense?
Check out "screenshot" by Gik Soft, small and simple, shake to take a screenshot.
Your interpretation of the profiles looks fine to me. For screen off, powersave limits the CPU to the minimum speed anyway, so min=max is redundant.
I noticed quite a bit more battery drain when using profiles (because SetCPU is constantly monitoring your device) but results may vary. Personally, I only boost the CPU for games and documents, and SetCPU will typically bump your phone down to minimum when idle anyway (assuming you don't have intensive background apps running).
I noticed the same, using profiles seems to drain my battery faster. So I just manually toggle my clock speeds. If you set to on demand you dont really even need to worry about a screen off profile. And when my battery starts to get low I just scale down the speed. The only time I've ever come close to needing a temp profile was if overclocked to 825 and using my phone intensively while it was charging...i never go over 806 anymore so temp is never a problem.
I can however see profiles being useful if you keep your phone overclocked to the max all the time.
Hello together,
first of all i would say that im completely new to this rooting and flashing stuff so dont be too hard to me. Lets start with my story: last year ive buyed my wildfire and used it for 2 months without rooting it. fast i've seen that it would be much more easier for me if i start rooting and flashing it with a custom ROM. Wildpuzzle was the first ROM i've ever used on this phone and i didn't updated it for a long time because i thought i can do anything bad to my phone. 3 days ago i've felt very bored so i read myself once again through all of the tutorials and FAQs. I decided to search the forum for a new ROM without sense so i picked CyanogenMod 6.1 because i wanted a stable ROM which dont reboot 4 times a day(like my old Wildpuzzle one). Today I wanted to speed um my phone and read through some posts and found out that I can overclock my wildfire with SetCPU. I've never overclocked a phone or a pc so i dont know what setup is good for it or which is not.
And thats my question: HOW should i do this and with what cpu setup(min/max) for a stable working phone.
PS: as i've read through the overclock posts i've found out that my phone is already flashed with a overclocking kernel(2.6.32.21-HCDRJacob)
PPS: i'm excuse myself for my bad english and hope you all can understand what i mean
Depends on your preferences really. For me, on my SetCPU Normal Profile, I have set it as 614 MHz Max and 245 MHz on Min, Interactive Scaling. Apart from that, I have also set the following profiles:
1: Screen Off - Max 352, Min 245
2: Temp >46C - Max 352 Min 245
3: Battery <20% - Max 480 Min 245
I had set the minimum earlier to 122, while it gave me awesome battery life, the phone would hang whenever I got an incoming call / message (CPU too slow to handle it), hence, after several experiments, I have found it to be stable at 245. For Max, you can keep it upto 710 MHz, but, I wont recommend a speed beyond that for 24x7 usage. For short purposes (like playing a game, benchmarking etc.), you can go till 768, or the max your phone is stable at.
Amazingly my set up is nearly identical to 3xeno but my max in normal profile is 691 MHz
3xeno said:
Depends on your preferences really. For me, on my SetCPU Normal Profile, I have set it as 614 MHz Max and 245 MHz on Min, Interactive Scaling. Apart from that, I have also set the following profiles:
1: Screen Off - Max 352, Min 245
2: Temp >46C - Max 352 Min 245
3: Battery <20% - Max 480 Min 245
I had set the minimum earlier to 122, while it gave me awesome battery life, the phone would hang whenever I got an incoming call / message (CPU too slow to handle it), hence, after several experiments, I have found it to be stable at 245. For Max, you can keep it upto 710 MHz, but, I wont recommend a speed beyond that for 24x7 usage. For short purposes (like playing a game, benchmarking etc.), you can go till 768, or the max your phone is stable at.
Click to expand...
Click to collapse
so what is exactly the interactive scaling ??
what is the difference between ondemand, userspace, performance, interactive...
while searching for the answer ... i also saw pple tlking about powersave and conservative scaling ... i dont have these options ... :s
Sorry to butt in but since we are on the subject of overclocking etc and I dont want to make another thread. Is that setcpu app from the market any use on my wildfire? its not rooted.
No you need rout access to change frequencies mate.
Sent from my HTC Desire using Tapatalk
3xeno said:
Depends on your preferences really. For me, on my SetCPU Normal Profile, I have set it as 614 MHz Max and 245 MHz on Min, Interactive Scaling. Apart from that, I have also set the following profiles:
1: Screen Off - Max 352, Min 245
2: Temp >46C - Max 352 Min 245
3: Battery <20% - Max 480 Min 245
I had set the minimum earlier to 122, while it gave me awesome battery life, the phone would hang whenever I got an incoming call / message (CPU too slow to handle it), hence, after several experiments, I have found it to be stable at 245. For Max, you can keep it upto 710 MHz, but, I wont recommend a speed beyond that for 24x7 usage. For short purposes (like playing a game, benchmarking etc.), you can go till 768, or the max your phone is stable at.
Click to expand...
Click to collapse
What, your settings are extractly like me, lol
are you referring to old wildpuzzle 8.0.11, i got freezes with that, but after changing to new wildpuzzle, i have not had one freeze or reboot with settings below.
set on performance
3xeno said:
Depends on your preferences really. For me, on my SetCPU Normal Profile, I have set it as 614 MHz Max and 245 MHz on Min, Interactive Scaling. Apart from that, I have also set the following profiles:
1: Screen Off - Max 352, Min 245
2: Temp >46C - Max 352 Min 245
3: Battery <20% - Max 480 Min 245
I had set the minimum earlier to 122, while it gave me awesome battery life, the phone would hang whenever I got an incoming call / message (CPU too slow to handle it), hence, after several experiments, I have found it to be stable at 245.
Click to expand...
Click to collapse
Thank you for sharing this information, I changed mine to this too. Can I ask if you 'Set on Boot' on the main profile? I think you would, but I thought i better check!
alfanhui said:
Thank you for sharing this information, I changed mine to this too. Can I ask if you 'Set on Boot' on the main profile? I think you would, but I thought i better check!
Click to expand...
Click to collapse
Yes, I do have the 'Set At Boot' option enabled
3xeno said:
Depends on your preferences really. For me, on my SetCPU Normal Profile, I have set it as 614 MHz Max and 245 MHz on Min, Interactive Scaling. Apart from that, I have also set the following profiles:
1: Screen Off - Max 352, Min 245
2: Temp >46C - Max 352 Min 245
3: Battery <20% - Max 480 Min 245
I had set the minimum earlier to 122, while it gave me awesome battery life, the phone would hang whenever I got an incoming call / message (CPU too slow to handle it), hence, after several experiments, I have found it to be stable at 245. For Max, you can keep it upto 710 MHz, but, I wont recommend a speed beyond that for 24x7 usage. For short purposes (like playing a game, benchmarking etc.), you can go till 768, or the max your phone is stable at.
Click to expand...
Click to collapse
I usually set my speed to Max 710, Min 480 Ondemand, no profile. I think it's interesting to try your setting. Thanks for sharing.
Has anyone else noticed this? My phone only goes to 245 mhz for idle speed. Android system info said that the cpu can go as low as 122mhz. I think it would save some battery life right?
yes we can... but you need root acces and setcpu
and you can underclock
PM me if you need more help
i suggest dont do that..
i ever do that, n phone become slowly ..
even to open setting..
it will become slow like symbian, and what ur friends think about it??
maybe they will thinking, android very slow :|
godfadger said:
Has anyone else noticed this? My phone only goes to 245 mhz for idle speed. Android system info said that the cpu can go as low as 122mhz. I think it would save some battery life right?
Click to expand...
Click to collapse
what ROM are you using? I'm using racht's floyo 0.15 and when the screen goes off the cpu idles at 122 MHz well.
or maybe you checked cpu freq when screen is on? because it's not 'idle' state.
This sounds interesting - can you guys let me know if you manage to extend battery life with this... and how much by, daily charging is sucky!
I use setcpu with this configuration:
Max: 600000
Min: 122880
Scaling ondemand
check: set on Boot
I also create profile:
Screen Off
Max: 320000
Min: 122880
Scaling ondemand
Hello,
I've flashed cyanogenmod 7.1 RC1 and immediately switched to using the smartass governor. However, I've noticed that the apps that can detect CPU speed (like SetCPU or OS Monitor) always detect frequency as 480 MHz. I've set the Max freq to 748 MHz and min to 245 MHz, but whatever I do, the frequency stays at 480 MHz. I've also seen in the messages section of OS Monitor errors about setting to 768000 from 480000, so I guess there is some kind of a problem there.
So is there a problem or does this governor work in a completely different way - if so, how? ;-)
Thanks a lot.
Cheers...
Smartass caps the frequency when screen on to 480 MHz to ensure responsiveness. This also helps with video playback being smooth, as it otherwise will begin to stutter when the frequency is lower than this.
OK, but how does it behave during screen off and battery low scenarios? Does it put the freq to to minimum value which is selected in the freq options of cyanogenmod setup?
I just want to understand if indeed the smartass governor can replace setcpu with profiles using the ondemand governor and keep the battery usage at optimal values.
Thanks...
When screen off smart ass governor sets the minimum CPU frequency to the value you entered (even below 480 which is to conserve the battery).
Sent from my HTC Wildfire using XDA App
What voltages can I set for frequencies from 2457 MHz? For now I have such voltage settings.
You must've spent a lot of time perfecting that. Can you remind me of your SoC's PSV value? Boeffla's app lists it in the Overview section as ASV/PSV.
I tried your 600 mV idle voltage on my PSV 9 phone. Didn't work, got a soft reboot. 625 mV seems to work. Seems crazy this is possible when the stock idle voltage is around 775 mV.
https://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
edit: Tested for a few hours. Currently using
990 mV - 2534 MHz
1010 mV -2611 MHz
1030 mV - 2764 MHz
1045 mV - 2841 MHz
1075 mV - 2899 MHz
Seems stable in stability tests, haven't tried in daily use yet. If you want to increase the max speed the sweet spot is probably 2764 or 2841.
If you haven't seen this chart yet it has estimated voltages for each PVS binning on speeds above stock, maybe it's what you're looking for. According to the table the "worst" voltage a terrible PVS stock phone will use is 1120 mV. If you do not exceed that while overclocking your phone will probably be okay.
Thanks for the voltage references, I'll use them to tweak some more!
I came up with a stability test that hopefully tests phone stability without causing it to burn up. You just need the Boeffla app and Termux.
-Make a separate Boeffla profile
-Manually select and apply the new profile every time you're testing the undervolt
-Add some extra startup delay in the Boeffla settings
-In the Boeffla app change the Tuned governor's profile to "Performance". The normal profiles don't really care about using high CPU states so you need this.
-Don't change the hotplugger, default is "Tuned"
-Reduce your max charging speed for AC and USB to 1200 mA if you want to do testing with a charger plugged in
-Try to start on 100% charge so less heat is generated charging
-Lock the GPU to 27 MHz. Why not? The screen will be off anyways.
-Make undervolting adjustments to your CPU states' voltages. Only tweak the values of one or two states at a time.
-Adjust the minimum and maximum CPU speeds with the sliders so your phone is more likely to hit the states you just tweaked. If you just tweaked a low CPU state set it to the minimum speed, and if you just tweaked a high CPU state set it to the maximum speed etc.
-Launch Termux and then "Acquire Wakelock" in the menu or in the notification bar
-Run this one-liner:
while true; do openssl speed -evp aes-256-gcm; sleep 15s; done
Click to expand...
Click to collapse
Explanation: No real reason to do it this way. Openssl's speed benchmark with AES is a cheap way to test CPU stability on many computer systems. This runs a benchmark on 1 thread, sleeps for 15s to let the phone cool off for a bit, and repeats. If the phone isn't throttling it will typically max out the CPU clock of the core the thread's running on. Sometimes you can spot anomalies when the benchmark scores deviate a lot. You can also add -multi [# of cores you want to test on] to run the test on more cores but this may heat up the phone too much and cause anomalies.
-Give your phone some cooling with a fan or something or put it on top of something that dissipates heat.
-Turn the screen off to keep heat down or keep it on low brightness.
-Check the phone once in a while to see if it's still stable
-If you are happy continue adjusting other values
-This test isn't perfect because it's not representative of real-world use but hopefully it's close enough :silly:
-The battery generally doesn't like it when it goes above 40C just pointing this out :silly:
-Possible alternative stress test: dim the screen to minimum brightness and play a video the phone doesn't really like such as webms
-If your phone is looping from bad settings just hold power + vol down + home to force a hard reboot
Boatshow said:
You must've spent a lot of time perfecting that. Can you remind me of your SoC's PSV value? Boeffla's app lists it in the Overview section as ASV/PSV.
I tried your 600 mV idle voltage on my PSV 9 phone. Didn't work, got a soft reboot. 625 mV seems to work. Seems crazy this is possible when the stock idle voltage is around 775 mV.
https://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
edit: Tested for a few hours. Currently using
990 mV - 2534 MHz
1010 mV -2611 MHz
1030 mV - 2764 MHz
1045 mV - 2841 MHz
1075 mV - 2899 MHz
Seems stable in stability tests, haven't tried in daily use yet. If you want to increase the max speed the sweet spot is probably 2764 or 2841.
If you haven't seen this chart yet it has estimated voltages for each PVS binning on speeds above stock, maybe it's what you're looking for. According to the table the "worst" voltage a terrible PVS stock phone will use is 1120 mV. If you do not exceed that while overclocking your phone will probably be okay.
Thanks for the voltage references, I'll use them to tweak some more!
I came up with a stability test that hopefully tests phone stability without causing it to burn up. You just need the Boeffla app and Termux.
-Make a separate Boeffla profile
-Manually select and apply the new profile every time you're testing the undervolt
-Add some extra startup delay in the Boeffla settings
-In the Boeffla app change the Tuned governor's profile to "Performance". The normal profiles don't really care about using high CPU states so you need this.
-Don't change the hotplugger, default is "Tuned"
-Reduce your max charging speed for AC and USB to 1200 mA if you want to do testing with a charger plugged in
-Try to start on 100% charge so less heat is generated charging
-Lock the GPU to 27 MHz. Why not? The screen will be off anyways.
-Make undervolting adjustments to your CPU states' voltages. Only tweak the values of one or two states at a time.
-Adjust the minimum and maximum CPU speeds with the sliders so your phone is more likely to hit the states you just tweaked. If you just tweaked a low CPU state set it to the minimum speed, and if you just tweaked a high CPU state set it to the maximum speed etc.
-Launch Termux and then "Acquire Wakelock" in the menu or in the notification bar
-Run this one-liner:
Explanation: No real reason to do it this way. Openssl's speed benchmark with AES is a cheap way to test CPU stability on many computer systems. This runs a benchmark on 1 thread, sleeps for 15s to let the phone cool off for a bit, and repeats. If the phone isn't throttling it will typically max out the CPU clock of the core the thread's running on. Sometimes you can spot anomalies when the benchmark scores deviate a lot. You can also add -multi [# of cores you want to test on] to run the test on more cores but this may heat up the phone too much and cause anomalies.
-Give your phone some cooling with a fan or something or put it on top of something that dissipates heat.
-Turn the screen off to keep heat down or keep it on low brightness.
-Check the phone once in a while to see if it's still stable
-If you are happy continue adjusting other values
-This test isn't perfect because it's not representative of real-world use but hopefully it's close enough :silly:
-The battery generally doesn't like it when it goes above 40C just pointing this out :silly:
-Possible alternative stress test: dim the screen to minimum brightness and play a video the phone doesn't really like such as webms
-If your phone is looping from bad settings just hold power + vol down + home to force a hard reboot
Click to expand...
Click to collapse
I have PSV 10. My current undervolting.