What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
I use SMARTASS as my CPU speed governor and I set my CPU to 480-748 MHz, seems pretty stable for me.
Sent from my LG-VM670 using xda premium
thaunknownartist said:
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
Click to expand...
Click to collapse
Overclocking values differ from phone to phone. Test it out with different values and use the one which is stable for you.
This was just discussed in the IHO technical-discussion thread, as a matter of fact.
My phone is stable for most stuff at 806 MHz, but sometimes the camera will cause a freeze/reboot. So I run at a 786 MHz max. Your phone will be different; this has to do with minute physical differences between individual chips.
The thing to keep in mind when overclocking is that the processor in our phone (unlike those of many other phones) does not make use of dynamic voltage scaling. There are only two voltage levels: a lower one if the phone is running at or below (or is it just below? correct me if I'm wrong, guys) 480 MHz, and a higher one if the phone is running above. So below 480 MHz, the system will give the processor a certain amount of voltage (period), and above, the processor will get a certain higher amount of voltage (period).
Because of that, the tests that have been done indicate that 806 MHz is the sweet spot for battery efficiency when the phone is in use--and the closer you get to 806, the better. Thus, I've had the following settings for quite some time:
786 MHz min
786 MHz max
Performance governor
which has treated me pretty well. On a day of light to moderate use, I'd end up with 65-75% battery left (occasionally more like 80%), depending on cell signal where I am et al. And it gives me probably the best performance I'm gonna get out of this phone.
However, I very recently decided to change the minimum to below that 480 MHz threshold and see what a lower voltage when idling would do for my battery life. My current settings are:
320 MHz min (may change to 480)
786 MHz max
Smart*** governor
There is actually a noticeable performance decrease when I first wake the phone up, so I may switch governors as well. In any case, I've had those settings for only one full day now, but for that one day the battery life was noticeably better. I'll post an update when I've had a few more days to test.
As always, it's difficult to quantify battery life in a reliable/rigorous manner (much less a universally applicable one), so YMMV.
Related
Hello..anyone can teach me how to overclock xperia x10
Bootloader is not unlocked. It's impossible at the moment.
Sent from my X10i using XDA App
satAxOnic said:
Hello..anyone can teach me how to overclock xperia x10
Click to expand...
Click to collapse
First, you crack the bootloader.
When you've done that, I'm guessing you allready figured out how to OC the CPU
Sent from my FreeX10i beta2.
satAxOnic said:
Hello..anyone can teach me how to overclock xperia x10
Click to expand...
Click to collapse
For now just use the overclock widget. set top two settings as high as you want up to 998 click on off screen frequency. set between 246 and next number you choose. set at boot save. define settings at what mhz you like and experiment. do not run on screen and off screen freq at max. i have had my battery sweating and even plugged in all day and not gained a single % of charge. until boot loader is cracked.... this is all you can do.
xperiax10a
2.2b2
Bummmod
gapps1901
quadrant 1800
linpack 40.XX
Although it's impossible today because of bootloader, note it's always dangerous and not great to overclock embedded cpus.
You can't overclock a lot, as you have a battery (X10 works about 5-10 hours with full speed - 998MHz), and the CPU only has passive elements to cool. Overclock can damage your CPU and your motherboard, stress all elements and low your battery life (battery charge and cycle of charge). (Even there's a self shutdown when too hot)
You can get an idea of overclock on Nexus forum, as we have the same CPU (Snapdragon 8250) - I saw overclock up to 1300 MHz, but it's really not looking safe to me
Thanx everyone..
Perceval from Hyrule said:
Although it's impossible today because of bootloader, note it's always dangerous and not great to overclock embedded cpus.
You can't overclock a lot, as you have a battery (X10 works about 5-10 hours with full speed - 998MHz), and the CPU only has passive elements to cool. Overclock can damage your CPU and your motherboard, stress all elements and low your battery life (battery charge and cycle of charge). (Even there's a self shutdown when too hot)
You can get an idea of overclock on Nexus forum, as we have the same CPU (Snapdragon 8250) - I saw overclock up to 1300 MHz, but it's really not looking safe to me
Click to expand...
Click to collapse
Depends also on the voltage (as long as your voltage isn't increasing as you overclock, it isn't really that harmful as long as you watch the heat), and what you have your underclock speed set to with screen off (as this can in some sense reverse some of the possible "damage")...
I had my htc hero overclocked to 710 with the screen on, and underclocked 176 with the screen off and it ran a lot better.
I digress, I see no purpose in doing so when you already have a 1ghz processor that is super fast. I only really see a point in overclocking if the possible benefit is greater than the possible harm, and in this circumstance, I really don't think you would see that much benefit.
fiscidtox said:
Depends also on the voltage (as long as your voltage isn't increasing as you overclock, it isn't really that harmful as long as you watch the heat), and what you have your underclock speed set to with screen off (as this can in some sense reverse some of the possible "damage")...
I had my htc hero overclocked to 710 with the screen on, and underclocked 176 with the screen off and it ran a lot better.
I digress, I see no purpose in doing so when you already have a 1ghz processor that is super fast. I only really see a point in overclocking if the possible benefit is greater than the possible harm, and in this circumstance, I really don't think you would see that much benefit.
Click to expand...
Click to collapse
I have seen considearable difference when maxed out. however the dangers are high of overheat. ive done it once and onetime only. kept on and off screen at 998 and hat it plugged in all day with out a single gain of battery. it was like on life support and was hot enough the phone was sweating even when sitting next to a fan blowing on it constantly.:-( since then i have made adjustments to run between 700 and 998mhz on screen and min 246 and 400mhz when screen off.
if looking for better performance without the overclock and good drain of battery, download and install sysctl from market and follow settings below.
min free kb: 900000
dirty ratio:500000
dirty background:200000
vfs cache pressure:10
Oom allocating: checked
On SetCPU there is Set on boot- to be checked or not?
Sent from my X10i using Tapatalk
it should be checked
OC can damage yo device. Id say its better to hv a lil slower device than a dead device
Sent from my X10x using XDA App
live4speed said:
OC can damage yo device. Id say its better to hv a lil slower device than a dead device
Sent from my X10x using XDA App
Click to expand...
Click to collapse
Not in all instances. Depends on the quality of the chip. Lot of chips are capable of handling higher speeds and temps but are set lower quality assurance.
For instance, I've got a NookColor that has base CPU set at 800MHz and is now overclockable to 1.2GHz
We'll have to do stress tests on some to see what they're capable of.
andrewddickey said:
Not in all instances. Depends on the quality of the chip. Lot of chips are capable of handling higher speeds and temps but are set lower quality assurance.
For instance, I've got a NookColor that has base CPU set at 800MHz and is now overclockable to 1.2GHz
We'll have to do stress tests on some to see what they're capable of.
Click to expand...
Click to collapse
Agreed.
My Motorola Defy has a Omap3630 that comes at 800MHz,stock but can be easily overclocked to 1.3GHz without a sweat.
Just depends on the chip's capacity of "Stress".
Respect
As I understand solution for "998 MHz with screen on" bug is found: http://forum.xda-developers.com/showthread.php?t=1225411&page=17#post16944722
We need to replace only one governor.
I don't want to play with different ROMs and kernels and I'm looking for simplest solution.
Is it possible to compile it as a module ("ondemand_mod" for ex.) and add it to stock ROM?
Or any other (simple) way?
Wrong section ...
Sent from my X10i using Tapatalk
Why wrong Section, this is Development to get the CPU Governor working correctly
Wolfbreak said:
Why wrong Section, this is Development to get the CPU Governor working correctly
Click to expand...
Click to collapse
Exactly, this is the right section for such request.
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
My_Immortal said:
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
Click to expand...
Click to collapse
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
As I see it's possible to compile and use governor as module.
Could someone compile it? And assemble as xRecovery package?
Or point me where to read about compiling for arm, where to get tools and so on...
Karlson2k said:
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
Click to expand...
Click to collapse
The thing is, on 245 MHz, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Xperia X10i via Tapatalk
My_Immortal said:
The thing is, on 245 MHz with high load, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Click to expand...
Click to collapse
There is no need to work on 245MHz as proper governor rise frequency automatically when it's necessary.
And really no stress for CPU to work an low frequency at full load. Moreover - CPU will consume more power at 500Mhz with 45% load than at 250Mhz with 95% load.
Sometime I use phone for navigation - long time with screen on and very low load. In this scenario battery drains very fast.
And last one - I like to have everything working properly. In case that I'll really need high frequency all the time I'll use other governor. I just want to have a choice.
I need a simple solotion for this too..I use z kernel and I found that Thego2s kernel fixed this problem..I was going to flash that kernel but think that has a bug and stoucks on logo ..can some one sayas a simple way?
Yes, I think a lot of people would prefer to use just small and simple fixes rather than replacing the whole kernel with a lot of nice but (personally) unnecessary features.
I am waiting for developers to release a fix for this problam
I'm looking for a good baseline to see what works best on this phone.
list everything, screenshots prefer and please specify your rom, kernel, and theme.
Mine are as follows...
all info in my sig. I use 500-1400 conservative with a 500-500 power save profile set for when the screen is off.
My battery lasts between 28-42 hrs pending my usage level from high - low. YMMV.
Miui
200 to 1200
Conservative
Noop
Using no-frills
Same settings when using perception. Awesome battery life, almost two days.
Sent from my SGH-I777 using Tapatalk
CM7
200-1400 On demand
nothing else changed in setcpu
using red drop them for theme changer
CM7 launcher (ADW)
Widgetlocker for lockscreen theme
So, I'm heavily themed, but not much in widgets.
Seems good on battery, can last ~14 hours with moderate to high use.
Stable as well, no major crashes other than the usual browser and market.
I use Voltage Control myself and I've UV'd all across the board by -50. I've also dropped max speed to 1000Mhz. The rest should be pretty self explanatory...
Oh and I can't really list battery life because my usage really varies day to day, by quite a bit. I will say that I definitely get through an entire day with very high usage with no problems at all. Much... MUCH better than when I was running stock.
Default voltages and frequencies, ondemand, ignore nice load
llescaflownell said:
CM7
200-1400 On demand
nothing else changed in setcpu
using red drop them for theme changer
CM7 launcher (ADW)
Widgetlocker for lockscreen theme
So, I'm heavily themed, but not much in widgets.
Seems good on battery, can last ~14 hours with moderate to high use.
Stable as well, no major crashes other than the usual browser and market.
Click to expand...
Click to collapse
Do you notice any difference at all in performance? How much display time do you get?
Cansomeone tell me the stock voltages I think mine are messed up
Sent from my SAMSUNG-SGH-I777 using xda premium
roadrash7 said:
Cansomeone tell me the stock voltages I think mine are messed up
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Add 50 to each of the ones in my picture posted in the reply up above.
Simba501 said:
Default voltages and frequencies, ondemand, ignore nice load
Do you notice any difference at all in performance? How much display time do you get?
Click to expand...
Click to collapse
Day to day performance, there really is no difference than stock, but to compare quadrant, I got ~3300 stock, but at this OC I get ~4400. It's gonna be smooth as butter either way, I just like numbers
Display time, I'm not too sure, but my settings are at its 1/3 highest (so not too bright, but not too dim either for me). If I were to approximate, I would say a good 2 hours of the display being on, give or take an hour or too (not the best estimate, but Ill try and keep track next time and report back).
Rooted stock
No themes
I get a good 14 to 18 hrs (minimal usage during the day and heavier usage evenings/nights - lots of wifi or data intensive apps)
Kadin said:
Add 50 to each of the ones in my picture posted in the reply up above.
Click to expand...
Click to collapse
thanks but it looks like that is not stock settings, turns out if you click revert in setcpu it tells you how to get back to stock. they are...
1200-1275
1000-1175
800- 1075
500 - 975
200 - 950
my new settings are...
1200-1175
1000-1100
800 - 1000
500 - 925
200 - 850
all is well so far. stress test with no probs.
Here's my settings
Main Profile: 200Mhz Min 1Ghz Max running conservative governor. During the day. Conservative is performing better than ondemand for me.
I've also been toying with the up and down thresholds on the conservative governor to find a difference. Haven't really experienced any lag unless I set the up threshold to 90 or over.
Screen Off: 200 Min 500 Max also conservative
Charging: 200 Min 1400 Max ondemand
Battery <25% 200Min 800Max conservative
I've been finding the phone is just as good running at 800mhz max on the main profile. It's amazing how much faster this thing is then my captivate.
As far as voltages
1600: 1450
1400: 1325
1200: 1225
1000: 1100
800: 1000
500: 900
200: 825
Been getting amazing battery life. Been on battery for 10 hours now. Still 65% battery. Not bad.
My phone absolutely blows for overclocking. anytime i try the settings posted here it locks up
Also using No Frills here. Settings are:
Max: 1200
Min: 200
Conservative and Noop
I unplug it at 7am and by the time I get off of work at 5:30ish I still have 60%+ of my battery left. Running MIUI with quite a few widgets and I leave wifi on all the time.
roadrash7 said:
thanks but it looks like that is not stock settings, turns out if you click revert in setcpu it tells you how to get back to stock. they are...
1200-1275
1000-1175
800- 1075
500 - 975
200 - 950
my new settings are...
1200-1175
1000-1100
800 - 1000
500 - 925
200 - 850
all is well so far. stress test with no probs.
Click to expand...
Click to collapse
Thanks for this!
DJSLINKARD said:
My phone absolutely blows for overclocking. anytime i try the settings posted here it locks up
Click to expand...
Click to collapse
Might have to Overvolt. I had to overvolt 1400Mhz by 25mv in order to get it stable.
Also I've noticed lately when it's not happy with the setCPU settings I'm using the phone seems to emit a high pitched frequency when you put your ear to the back cover. When I get stable it appears to stop.
roadrash7 said:
thanks but it looks like that is not stock settings, turns out if you click revert in setcpu it tells you how to get back to stock. they are...
1200-1275
1000-1175
800- 1075
500 - 975
200 - 950
my new settings are...
1200-1175
1000-1100
800 - 1000
500 - 925
200 - 850
all is well so far. stress test with no probs.
Click to expand...
Click to collapse
Not sure what to tell ya. I just installed SetCPU and this is the default settings showing - the same as Voltage Control and what I was referring to. I deleted the boot and profile settings first from Voltage Control and then rebooted, then installed SetCPU.
The only thing I can think of is that since I'm running UnNamed with Entropy's daily driver, maybe the voltage was tweaked from him? I'm only assuming because reading through his thread doesn't seem to indicate that he upped the default voltage on all levels. Unless I missed it somewhere.
This is in Entropy's Daily Driver thread - http://forum.xda-developers.com/showpost.php?p=18433190&postcount=213
Kadin said:
Not sure what to tell ya. I just installed SetCPU and this is the default settings showing - the same as Voltage Control and what I was referring to. I deleted the boot and profile settings first from Voltage Control and then rebooted, then installed SetCPU.
The only thing I can think of is that since I'm running UnNamed with Entropy's daily driver, maybe the voltage was tweaked from him? I'm only assuming because reading through his thread doesn't seem to indicate that he upped the default voltage on all levels. Unless I missed it somewhere.
This is in Entropy's Daily Driver thread - http://forum.xda-developers.com/showpost.php?p=18433190&postcount=213
Click to expand...
Click to collapse
Thanks for the clarification
I'm still trying to find settings that give the most performance and give the best battery life
bump...
No one cares to share?
Stock voltages and frequencies - on demand
Charging - stock frequencies - on demand
screen off - 200-500 conservative
I flashed the cm7 1.4 240-325-300 Kernel.
In my settings what should I keep my min and max at for all time usage?
I max them and my quad score is like 5501
don't know if your supposed to keep those certain.
Also does decrease or increase battery life.
I left mine at the default values. Was wondering this myself though. How do you test quad scores?
Download quadrant standard from market
Sent from my MB855 using XDA App
You want the lowest value to be at the lowest(216 i think) because this allows the processor to idle at that low speed, if you keep the minimum speed at 1ghz your processor will ALWAYS be running 1ghz at the lowest, and that will be an obvious way to kill your battery in no time. So set that to the lowest, and for the maximum i personally run mine at 750 for CM9, think i had it at 800 for CM7 but cannot remember for sure. This is limiting how fast the processor can run so the lower the better as far as battery goes. It comes down to you personally, if you game and do processor heavy tasks often then having the processor underclocked like i run mine will affect your gaming/app/overall experience. Its always like 2 clicks away to bump it up to a higher speed and i have a link on my home screen so if i do decide to do anything processor heavy i can bump it up quickly. But in general it takes more power for your processor to run higher so if your really concerned about battery life try bringing it down. I can still score a solid 1,500+(with a bunch of crap installed on my Photon mind you) on CM9 with my max at 750 and min and 216. Benchmarks are honestly just a number, it comes down to how if performs for you and what you are doing with your phone.
Awesome, I'm lowering it now and battery is dropping slow so its good, thanks for the detailed reply.
Sent from my MB855 using XDA App
What is the difference between undervolting and underclocking? What does each do to battery life, performance, etc.
Also, what are the best, stable undervolting and underclocking value for the Rezound? I'm running Neo's Tron rom
gleggie said:
What is the difference between undervolting and underclocking? What does each do to battery life, performance, etc.
Also, what are the best, stable undervolting and underclocking value for the Rezound? I'm running Neo's Tron rom
Click to expand...
Click to collapse
Undervolting is lowering the amount of power the processor draws at a certain frequency. Let's say, for example, a processor uses 1025mV at 1.18GHz normally. If you lower the voltage to 975mV for that frequency (using System Tuner or something similar) that's undervolting. If you lower the voltage too much the device will be unstable and reboot.
Underclocking is lowering the top speed of a processor. On our Rezound, the maximum speed of our processor is 1.5GHz stock. If you lower the maximum speed to 1.18GHz that's underclocking. Obviously lowering the maximum speed of the processor will decrease the performance of the device somewhat, depending on how much you lower it and what you're doing. Just getting on Twitter and XDA you might not notice the difference in speed, but during gaming it'll become more prevalent.
There isn't an established "best" amount to undervolt by, as each device is different. One device might be able to undervolt by 50mV with no problems, while another might not be able to handle any undervolting at all. If you're using the latest version of TRON ROM you should already be on Snuzzo's FunkyBean kernel, which has been undervolted by 50mV at every frequency.
Undervolting is also a subjective thing. Some people choose to go with 1.18GHz, while others may choose something higher than that, like 1.35GHz. It all depends on how you use your device and how you want it to perform. I suggest trying out something around 1.24GHz and seeing if it's alright with you. If it's too laggy just raise the speed bit by bit until you're satisfied with it.
I'm sorry for the long winded reply, but I wanted to make sure I covered everything.
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
Undervolting is lowering the amount of power the processor draws at a certain frequency. Let's say, for example, a processor uses 1025mV at 1.18GHz normally. If you lower the voltage to 975mV for that frequency (using System Tuner or something similar) that's undervolting. If you lower the voltage too much the device will be unstable and reboot.
Underclocking is lowering the top speed of a processor. On our Rezound, the maximum speed of our processor is 1.5GHz stock. If you lower the maximum speed to 1.18GHz that's underclocking. Obviously lowering the maximum speed of the processor will decrease the performance of the device somewhat, depending on how much you lower it and what you're doing. Just getting on Twitter and XDA you might not notice the difference in speed, but during gaming it'll become more prevalent.
There isn't an established "best" amount to undervolt by, as each device is different. One device might be able to undervolt by 50mV with no problems, while another might not be able to handle any undervolting at all. If you're using the latest version of TRON ROM you should already be on Snuzzo's FunkyBean kernel, which has been undervolted by 50mV at every frequency.
Undervolting is also a subjective thing. Some people choose to go with 1.18GHz, while others may choose something higher than that, like 1.35GHz. It all depends on how you use your device and how you want it to perform. I suggest trying out something around 1.24GHz and seeing if it's alright with you. If it's too laggy just raise the speed bit by bit until you're satisfied with it.
I'm sorry for the long winded reply, but I wanted to make sure I covered everything.
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
Thanks for the thorough response!