I was wondering who had their hw6915 overclocked (and to what speed)
I am wondering because i feel sometimes that the device is just a tad too slow
XCPUScaler
I have a 6915 and use the Advanced Speed Settings to take it from 208Mhz when idle to 520Mhz between 71 -100% usage. Had it for about a year now and still fine with no problems with stability or reliability
IronMaiden1965 said:
I have a 6915 and use the Advanced Speed Settings to take it from 208Mhz when idle to 520Mhz between 71 -100% usage. Had it for about a year now and still fine with no problems with stability or reliability
Click to expand...
Click to collapse
Hi, can you give us your exact speed settings? I am very interested on testing this.
Thank you in advance.
I made the pda to 520mhz all the time, and my pda freezes from time to time, like 3 times a day when running it 520 full time... so i put it back to 412 and using it on that settings...
P.
Speed Settings
Here are the Settings I use with no freezing at all:
CPU Load Speed Setting
15% 208Mhz
40% 312Mhz
70% 416Mhz
71-100% 520Mhz
These were setup on the advanced tab, my default speed setting is 416Mhz on the speed tab but with "Auto Scale with CPU Load" enabled this becomes irrelevant.
Have fun
use the HR INSTALTION i gave on more tips 6900 thread and you will see things going fast
IronMaiden1965 said:
Here are the Settings I use with no freezing at all:
CPU Load Speed Setting
15% 208Mhz
40% 312Mhz
70% 416Mhz
71-100% 520Mhz
These were setup on the advanced tab, my default speed setting is 416Mhz on the speed tab but with "Auto Scale with CPU Load" enabled this becomes irrelevant.
Have fun
Click to expand...
Click to collapse
I use the same settings except that I have it to 624 MHz at >71%. Never had a problem at that setting and have used it for a very long time. The thing I appreciate also is the scaling ability seems to make the battery last longer.
Wow. This is an old thread, but there might be people still in love with their Sable like I am.
I own a ASUS P320 (Galaxy Mini) which is notoriously infamous for its battery life. Therefore I was looking for a way to underclock the processor to squeeze out a few more hours of its battery. I wanted to autoscale the CPU Speed as and when required.
OMAPScaler did not work though it was able to set the processor speed to the desired value, so did OMAPClock, but the CPU scaling functions did not work. Neither did Homescreen PlusPlus. The reason I found out that my CPU always reports a 99.8% to 100% usage thus these utilities always set it to the highest speed I had configured (201 MHz for my device).
It was then, while using Chi Tai's awesome Homescreen PlusPlus Advanced version that I found this registry setting which enables an alternative method of CPU Load calculation.
Code:
Create a DWORD called UseIdleLoop of value 1 under \HKLM\SOFTWARE\Microsoft\Today\Items\Homescreen PlusPlus. Reboot/Reset your device.
The CPUScaler function started working after that Also the "Get Original CPU Speed" function does not work. You can manually save it and click on OK to save it.
My CPU Scaler settings :
Min : 117 MHz
Orig: 143 MHz
Max: 201 Mhz
No Boost. CPULoad Threshold : Low 30%, High 80%. All other settings default.
Works fine with my ASUS 320. Will report on battery life in a couple of days.
Thanks to timmymarsh who helped me a lot with my questions via PM on this thread : http://forum.xda-developers.com/showthread.php?t=549145
abesh
Hi all,
Has anyone tried using SetCPU on his rooted legend? I tried on my non rooted one just too have a look at the CPU frequencies, to see how it behaves at idle and so, and while max is 600MHz the min is "only" 480MHz.
Doesn't that sound a bit high for the min frequency? The snapdragon is clocked at 1GHz and idle is 250Mhz. Has anyone tried lowering the idle frequency on the legend to gain some battery life?
Hi Bricolo_fr,
I found this entry in the FAQ of SetCPU documentation fount here (http://www.pokedev.com/setcpu/):
"Why aren't there more speeds to choose from?
The speeds which the CPU can run at is in part a kernel limitation and in part a hardware limitation. Attempting to set the CPU frequency to anything else won't cause any changes in CPU speed. On some devices, the kernel can be modified to enable certain other frequencies. There are other speeds that would be useful, the capabilities of the processor itself often hinders which frequencies are available on a device."
Anybody has the skills for making a kernel change?or some ideas for us being able to use this properly?
Hi,
Today I rooted my legend and tested again SetCPU. At the begining, it was only possible to set CPU from 480 to 600 mhz, but then I red this in SetCPU documentation:
http://www.pokedev.com/setcpu/
--------------
10. Disabling Perflock
On most stock HTC kernels and some custom kernels, HTC has enabled a driver called "perflock" that constantly resets SetCPU's Max and Min settings. This does not apply to mostly "Google experience" HTC devices such as the T-Mobile G1, the myTouch 3G, any Google development device, or the Nexus One. It does, however, apply to "HTC Sense" devices such as the HTC Hero, Droid Eris, HTC Desire, HTC Incredible, EVO 4G, and myTouch Slide. Non-HTC devices never have perflock enabled.
SetCPU can disable perflock on newer HTC kernels, giving you control of the Max and Min settings of the CPU. To do this, press the Menu button on your device in the Main tab and choose "Disable Perflock." Read through the notice and then press the button in the dialog. If successful, you should be able to change the frequency with SetCPU. If this process fails, please e-mail the developer with your kernel version and device so support can be added.
Keep in mind that disabling perflock does not enable overclocking, though some overclocked kernels may require perflock to be disabled. Overclocking, in most cases, requires a custom kernel.
-------------------
So, in the last version of SetCPU there is an option in the menu called "Perflock Disabler" With this option, it is possible to select the minimun frequence to any value from 0 to 600 Mhz.
I have not been able to modify maximun to a value higher than 600 mhz (overclock) but I think the best target is to reduce battery consumtion decresing the minimun mhz value. Actualy I set minimum 128, maximun 600.
so, are you sure you could set it to the minimum of 128? because i think it doesn't work actually...at least without a modified kernel
I got a min at 19 MHz. to 600 Mhz.
casca said:
so, are you sure you could set it to the minimum of 128? because i think it doesn't work actually...at least without a modified kernel
Click to expand...
Click to collapse
Yes. Also confirmed with the app Os Monitor:
-Saling range: 122880-600000
-Frequency range:19200-600000
-Governor: ondemand
-Current: 122880
Software version: unbranded 1.31.405.4 (just rooted with Monodaco method and applyed all OTA updates)
In SetCPU Info:
-Time in state:
19200: 22
122880: 1169071 (Currently I set minimum at 122880)
128000: 0
245760: 269491
480000: 362472
600000: 347583
SetCPU in Legend allows the following governors: userspace, ondemand, and perfromance. Ondemand works fine. Userspace and performance makes extrage things (i tested quickly, to be honest)
I defined several profiles in SetCPU, depending of battery chage, and seems to work fine. But, I did not enable "Set on boot" option in SetCPU and need to activate "Perflock Disabler" in SetcPU menu everytime I reboot Legend (I prefer to test a SetCPU a few days before enabling "Set on boot")
well...this is nice... after disabling the "perflock" option...
I set the minimum value to 19mhz....lol... with "ondemand" management of the cpu...
I think I'have seen a HUGE improvement of the battery...When I mean HUGE, I really mean HUUUUUGE!
Like, for a 12hours use always with 3g data on,and 2 hours of wireless...lost only 30% of battery...
Testing today for more results...
I use the profile manager in SetCpu to set the CPU to 128-256 while screen off, max mhz while charging, etc.
I have seen big improvements.
Yes, battery improvement is very nice. This solution is great.
I am testing a profile to 122-245 while usb charging. So, when I use Googla Mobile Navigation it is able to load a bit battery while using GPS (normaly drains battery a bit while charging)
out of charge at 6am...it's now 10am...3g ON...wireless ON now for 2hours...
So, in resume, on 4 hours of use the battery loss - 6%
At this rate, and with these settings it should last for about 66hours, about 2,7 days.
Let's see...
casca said:
out of charge at 6am...it's now 10am...3g ON...wireless ON now for 2hours...
So, in resume, on 4 hours of use the battery loss - 6%
At this rate, and with these settings it should last for about 66hours, about 2,7 days.
Let's see...
Click to expand...
Click to collapse
Holy crap!!Yea, that would definately make me root!
Sent from my HTC Legend using XDA App
I can only say...in 3g mode and with the wireless ON 90% of the time from 6am to 00.00, i had more than 40% battery left at 00.00 when i went to bed.For me it's a new record.
Sent from my HTC Legend using XDA App
In my case, tested yesterday:
Battery consumption:
battery at 100% at 10:00 am. 3g data on 1 minute every 15 minutes (JuiceDefender), 30 mÃnutes call and 8 emails received and red a long de day. Battery was at 41% at 1:00 am. I spent the day in a place with low 3g network (between 1 and 2 bars in the top right corner)
SetCPU Configuration:
-Profile 1: when battery is between 50% and 100%: min 122 mhz, max 600 mhz
-Profile 2: when battery is between 30% and 50%: min 122 mhz, max 480 mhz
-Profile 3: when battery is between 0% and 30%: min 122 mhz, max 245 mhz
So, battery save is very nice.
this is soooooo interesting....
I couldnt find the app in the market...i found the apk in the HTc Dream forum...version 2.01 by coolbho. Is it ok to use that ?
i think so...
in worst scenario...it won't run lol...(i think!)
If i use linpack i can see someone with a legend that runs on 711mhz? Am i missing something can we overclock..
Sent from my HTC Legend using XDA App
I've made some profiles too, and it's working really well.
Are you guys using the auto detection of the device? I've used it in the first time, but it detected my device as a Hero(?) since the max frequency was only 528mhz. Then I've changed the device and selected MSM7x27 manually and got the 600mhz max and many middle frequencies like 120, 122 and 128mhz. Now I've changed the device again to auto detection and it worked this time, got the 600mhz max, but less middle frequencies (no 120 or 400mhz). Also, i'm using 122mhz as the minimum frequency in all profiles, isn't 19mhz too low? Or the demand feature really works that well and I will not even notice any difference?
wasup!
19mhz is not too low, i've used it and had a huge increase in battery life.
I am using profiles also at the moment.
Regards
Learners Lisence said:
this is soooooo interesting....
I couldnt find the app in the market...i found the apk in the HTc Dream forum...version 2.01 by coolbho. Is it ok to use that ?
Click to expand...
Click to collapse
Hi,
You can download from this link:
http://forum.xda-developers.com/showthread.php?t=505419
If you like the app, you can donate getting from Maket. Look for "setcpu for root users". It is only 1.99 USD.
Does anyone do undervolting here? What kind of settings have you been able to use?
I myself have managed to use the following stable profiles:
I'm using fugumod beta kernel which has different sets of frequencies, in case you're wondering.
Quick guide for anyone wanting to use pimpmycpu
(I offer no warranty if something happens to your phone, but I can assure you, nothing will happen. Worst case scenario is that your phone hangs and you have to reboot it.)
1. Download PimpMyCpu (You must have a kernel that supports undervolting, eg. fugumod)
2. Open it, press on the max MHz frequency you use (for me it is 780mhz, I don't use higher then that)
3. Lower the voltage with 25-50mv steps
- If your phone hangs immediately upon saving, you have reached the max voltage for that frequency and have to use a higher one
- If you succesfully manage to change your voltage, do a stress test or use your phone for a while for eg. gaming
4. When you go to lower MHz (eg. 390MHz) frequencies, I suggest you open SetCPU and from there set the min\max to that frequency. Close and open SetCPU once to see if it hangs. You can also use PimpMyCpu to do this, but I myself use SetCPU. This should be done for all frequencies.
Notice that different phones can get different results, so don't get upset if your phone hangs at voltage X al thought your friend can reach it
Why undervolt?
- It can greatly improve your battery life. Especially if you use a 'screenoff' profile in setcpu. I myself have gained about 10 hours of additional battery life with medium usage.
I ventured into undervolting this week.
The results are simpy amazing. I get about double the battery life, to about 60hrs.
I'm using the standard 2.4b3 kernel with these voltages, from low to high all minus :
125 125 125 150 150
I still need to test more, but haven't taken the time to do it properly. Setting min/max to the same freq is a good tip. Why are you using setcpu for this ? You can do it PMCpu as well, no ?
Your profiles are not displaying though.
Yeah, thanks for pointing that out. Should be displaying now.
And yeah, you can use pimpmycpu for changing frequencies (added that to the guide now) but I personally use setcpu. Mainly cause I have a ScreenOff profile in setcpu for 195 max\156 min and I don't want it to conflict.
After I undervolted my PC for years I just started with my G3. I am using the prereleased FuguMod Ultra Kernel and it's running in conservative profile with 156-1366 MHz.
- for 1366 MHz my deepest working Voltage is -95 (1430 mv).
- for 156 MHz I am currently getting lower and lower. At this time a Stress test with -400 (600 mV) is running (for about 1 minute now).
- When the lowest working Voltage for 156 MHz is found I will analyze one between highest and lowest, and scale all the others equably.
I will post my working settings as soon as I found it.
-400Mv? How did you even get an option to get it that low (Thought PimpMyCpu goes only upto -250Mv. Also for me the stress test in pimpmycpu causes a crash to the program immediately upon trying to use it.
I myself use SmartAss scaling, which seems like a real nice option. Though I'm not entirely sure what's it about.
I'm using 800Mhz with 1125mv, Its stable sofar, but i cant save the Profile, it shows boot settings not saved, when i want to save as boot, It shows Save boot settings? but i cant decide between Yes or No...
can someone help me?
Thom47 said:
-400Mv? How did you even get an option to get it that low (Thought PimpMyCpu goes only upto -250Mv.
Click to expand...
Click to collapse
If you do undervolting in the latest version of SetCPU you can undervolt by up to 500 mv.
Alright, as promised here are my final settings. Its running smooth without crashes for two days now.
Code:
freq / mV relative/mV absolute
156 / -500 / 500
195 / -500 / 500
260 / -500 / 550
390 / -500 / 550
780 / -500 / 700
975 / -225 / 1275
1170 / -175 / 1350
1366 / -75 / 1450
While searching for the right Voltages I discovered that the Stresstest in SetCPU almost never made the Phone crash - even on Voltages that were really instable. The Phone mostly crashed right at the moment when I switched into the frequency. So I tested the Voltages by switching into the frequency, out again, in again, and so on. If it didn't crash for about a hundred times, I ran a 20 minute stresstest to be sure.
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.