When you play games, some games dont play properly, you know hwat i found out if i change the voltage only 25 less dan default value then my games work fine, but if i go downer than that,, then my gaems dnt work, there wierd choppy frame rate lowers to, get oc/uv controller and u can control your voltage make sure for lower dan 500 mhz less dan 50 volts fine but if ur over dat den only -25 volts
Related
If I set the min cpu speed to the minimum (245MHz) using SetCPU and then refresh the CPU monitor, it's always at Max (998MHz).
However if I set the min to 384MHz and refresh, it's at 384 (unless something else is going on in the background in which case it might increase a bit).
This is all with the CPU governor set to on-demand
If I set MAX cpu to 245 then the monitor says it's 254, btw, so it seems it can run at that speed fine and the monitor is working ok apparently. It's just with min speed set to 254, it seem to stick at 998Mhz.
Does anyone else see this behaviour?
It this just a problem with SetCPU, or an underlying issue?
well, having played around with it some more, it seems it's actually the cpu speeding itself up so rapidly when monitoring it that it registers max MHz!
If I increase the up threshold, or the sampling rate, so that it doesn't step up a gear so quickly, then the monitor reads 245MHz.
This does raise the question though that if simply pressing the refresh button is enough to up the cpu to max when it's at the default settings, maybe there are better settings for battery life?
Maybe a slightly higher minimum speed is better, so that it doesn't step up all the time (because when it does, it seems to go straight to max).....
Hi !
Since I'm using Android my phone is getting hot after 5-10 mins of intensive use ( playing with the market, internet,youtube, twitter ... ). The temperature is about 37°c and when I'm playing games like Nova, my phone is getting close to 45°c. I don't think it could damage my phone, just want to know if it's "normal" temperature.
So, anyone know what maximum temperature the phone can handle ?
Thanks !
hellbleazer said:
Hi !
Since I'm using Android my phone is getting hot after 5-10 mins of intensive use ( playing with the market, internet,youtube, twitter ... ). The temperature is about 37°c and when I'm playing games like Nova, my phone is getting close to 45°c. I don't think it could damage my phone, just want to know if it's "normal" temperature.
So, anyone know what maximum temperature the phone can handle ?
Thanks !
Click to expand...
Click to collapse
I've had the same experience. The trick that worked for me was installing SetCPU, mentioned in other threads in this forum. Using default values, i was able to keep temperature down at about 30 degrees celsius. It also increased battery time significantly. In SetCPU you are able to define profiles, activating defined CPU scaling settings when specified conditions are met, e.g. when temperature is above a specified level. I couldn't get this to work properly, maybe due to the DisablePowerManagement settings in my ChuckyDroid ROM registry. But, with default settings in SetCPU, you should be ok.
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.
Right, so I'm going mad trying to undervolt my CPU.
Sometimes I drop voltages by -50mv, and the phone crashes. Alright I know that the voltage settings have been applied, and it's too low.
On other occasions, I can drop the voltage by ridiculous amounts and have 2.2Ghz running at 600mv (which is obviously impossible), and the phone doesn't crash for two or three days. Obviously the settings aren't being applied.
So my question is, when is the best time to apply voltage settings such that I know they are actually in effect? And is there a way to verify that the voltage settings are actually in effect?
I have been doing a bit more testing.
It seems to me that voltage settings are applied if you apply the setting to all frequency levels (for example some apps like Kernel Tweaker have a -25mv button). Hitting that button twice (for a total of -50mv) causes the phone to crash. However if I were to adjust just the voltage for one frequency at a time, the phone doesn't crash.
Should this be reported to kernel devs? Just want to make sure I'm not doing stuff wrongly.
First of all voltage regulator has some minimum and maximum values, if you go above or bellow those, they will not be applied. If you change voltage just for one frequency, do you force CPU into that particular frequency? Otherwise CPU could be skipping that frequency, for example if you change 600MHz, CPU could be going from 300MHz idle to 0.9GHz skipping some in between values and never actually stay on your changed 600MHz.
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.