This is an article that I've founded on a website and I want to share with you. Everything has been already posted and there is no new info for advanced users, but I think this will be very useful to many of you. Anyways, here it is
Click to expand...
Click to collapse
Your phone was taught to underachieve
You are not getting the maximum power and battery life out of your phone. At factory settings your Motorola Defy is underclocked and overvolted, which means that it runs slower than it should and drinks too much battery juice (even so it performs well and has a good battery life compared to other Android phones). Some people believe that the Defy was deliberately crippled for commercial reasons: Motorola didn't want to jeopardise sales of more expensive models by making the Defy too attractive. Nobody knows if this rumor is true or false. Either way, there is a tradeoff between performance and battery life, and Motorola erred on the side of caution. A phone that crashes because it runs too fast at too low a voltage causes a lot of expensive work for customer service. A phone that drains the battery a bit faster while running a bit slower won't send its users back to the stores to demand a fix, as long as it performs within the advertised specifications.
And the specs are too conservative. Your phone can run longer and faster.
To understand why, let's dig into the numbers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Speed, voltage, and battery trade-offs
Motorola set the three CPU speed/voltage combinations for the Defy at:
1) 300 MHz at VSel1 = 33;
2) 600 MHz at VSel2 = 48;
3) 800 MHz at VSel3 = 58;
at a threshold of 86%.
The threshold determines when the processor steps up to a higher speed. By default, it switches to high speed if it runs at 86% capacity, and slows to a lower gear when the usage drops.
Higher speed (more MHz) requires a higher voltage, which is why the VSel (Voltage Select) goes up. VSel is related to voltage according to:
V = 0.0125*VSel + 0.6.
So at the lowest default VSel (33), your phone runs at 1.0125 V. At the highest default VSel (58) it runs at 1.325 V.
The power consumed by the processor increases in a linear fashion with the clock speed (twice the speed is twice the power), but quadratically with the voltage: twice the volts means four times more power.
The display and the radios eat up most of your battery. Turning down the brightness and switching off GPS, Wi-Fi and mobile data when not in use improves battery life more than undervolting your processor.
However, you can squeeze a few more hours out of a battery charge if you undervolt your CPU, and overclocking may make some apps run a little smoother. Just don't expect miracles, and be prepared for errors and crashes when you push the wrong buttons.
Room for improvement
The main battery saver is a low VSel1 (the lowest voltage at the lowest speed), because your phone runs at this speed most of the time. Underclocking VSel1 is not a good idea, because below the default 300 MHz it takes noticably longer before your phone responds to an incoming call in standby mode. Reducing VSel1 too much makes your phone hang or reboot when it's idle, but you can reduce VSel1 within reason to increase standby time. If you cut VSel1 from 33 to 20 the processor uses 40% less power most of the time, which can make the difference between your phone lasting a full day or blacking out before you get a chance to plug it in. (There are more ways to stretch your battery without dumbing down your smartphone.)
Lowering the intermediate voltage at medium speed (600 MHz by default) saves a bit of juice when you're playing with your phone a lot, because VSel2 is the typical setting when you're using your phone. If you use your phone as an mp3 player on a long trip you may notice the difference.
Your phone rarely runs at top speed. It spikes at VSel3 occassionally, but even with QueueTube streaming, Wi-Fi Ruler scanning, GPS Status looking for satellites, and Dolphin HD loading pages in the background my processor spent most of the time at 600 MHz instead of the default maximum (800 MHz) or my custom 1 GHz.
Overclocking may make a difference if you're playing resource-hungry games or watch badly encoded videos. Just don't overdo it, because the voltage required to run at more than 1 GHz makes your phone produce more heat, reduces battery life, and may even shorten the life of your hardware. Try to keep the maximum VSel below or at the default maximum, and don't let the temperature increase beyond 35°C for too long unless you live in a very hot place. High temperatures won't kill your phone at once, but they will kill your processor and battery slowly. Batteries may be cheap, but a dead processor will turn out very expensive. Especially when the manufacturer finds out you've messed with the settings and voids your warranty.
So what settings should you use?
Workout schedule for your phone
There is no one-size-fits-all answer. Processor performance varies, even if they're from the same batch. Your optimum settings depend on your phone, whether it runs Eclair or Froyo, how you use it, where you use it. A phone in a hot jeans pocket doesn't dissipate heat as fast as a phone in a cool handbag, and shooting video is more demanding than listening to podcasts. You'll have to find the best settings for your phone by trial and error.
Start by lowering VSel1 in small steps and check if your phone runs stable for a while under real world conditions. The stability test that's built in SetVsel is a rough indication, but also test stability by running a couple of streaming video apps over 3G together with other power-hungry apps, because seemless switching between speeds is not the same as an artificial stress test at constant voltage. If your phone starts rebooting by itself, increase the VSel by a safe margin.
There's no point trying to push the numbers to the max, because the power used by your CPU is just a small part of the big picture. Tweak the next VSel after you have the first one tuned. Don't change all at once, because then you don't know which one is wrong if your phone becomes unstable. Tweak your VSels one at a time.
Remember: undervolting won't damage your phone. Pushing the voltage too high may fry your CPU and kill your battery. I wouldn't push my Defy beyond 1000 MHz unless I can make it run at a very low voltage.
Judging from reported values at which Motorola Defy (most of them on Eclair, some on Froyo) phones ran without issues (see below for details), the safe ranges seem to be:
- 300 MHz, VSel1 24-33
(some people report stable systems as low as VSel1 14);
- 600 MHz, VSel2 31-48;
(some people report stable systems as low as VSel2 27);
- 800 MHz, VSel3 41-58.
(some people report stable systems as low as VSel3 39);
- 1000 MHz, VSel3 45-74.
(above VSel3 58 your phone may get really warm).
I started with 300/24, 600/34, 1000/52. When that ran OK for a couple of days I knocked the voltage down in bits and pieces. I now keep my phone running at 300/16, 600/28, 1000/52, with the threshold at the original 86%. My phone runs smoothly, passes the stability test (check the bottom of the SetVsel screen) with flying colors, and the battery lasts noticably longer than with the default settings.
Of course that doesn't necessarily mean these settings will work for you, because every CPU is different. The only way to find out is by trial and error. Push your VSels down in small steps, one at a time, until your phone fails the stability test or starts rebooting by itself. Then go back to the last "safe" setting and continue with the next VSel.
If you like to take risks and don't mind your phone getting hot:
- 1100 MHz, VSel3 55-66;
- 1200 MHz, VSel3 60-75.
More options
SetVsel has two options to let your phone go on a diet when your battery runs low. The first option is to limit your phone to VSel2 when the battery level drops below a set percentage (e.g.30%), the other method is setting the threshold to 99% when the battery runs low. New versions of SetVsel may come with new tricks to squeeze some extra time out of dry batteries.
SetVsel can show your processor status in the notification bar if you check the speed icon box. Don't panic if the reported speed is different from what you entered into the program. SetVsel polls the processor speed more often than the notification refreshes, so the numbers indicate average speeds.
The "apply at boot" option is best left alone. If your phone runs well you won't reboot it very often anyway, and if it crashes a lot you'll probably need to try different voltages and reduce the maximum speed.
Go get it
• SetVsel (Android Market)
• SetVsel (xda forum)
SetVsel was designed for the Motorola Defy, but it also works on the Droid X and the Milestone. It may work on other phones, but your best bet is to search the market for "overclock" or "undervolt" and pick an app tailored for your device. Read the comments in the market to check if it works on your phone model. Checking out forums like xda before you start messing with the voltage is a good idea too.
Note: all overclock/undervolt apps require that your phone is rooted.
The safe ranges were estimated by searching Google for "Motorola Defy undervolt" and taking the speed-VSel combinations reported as being stable or unstable. The full list of values used:
reported as stable:
300/15 ? ?, 300/15 500/34 600/38, 300/14 550/26 800/38, 300/16 550/27 800/39, 300/16 600/28 800/39, 300/18 600/33 800/43, 300/20 600/32 800/50, 300/26 600/32 800/44, 300/26 600/33 800/39, 300/24 600/34 900/44, 300/28 600/38 900/46, 300/28 600/38 900/48, 300/18 600/30 1000/52, 300/18 600/38 1000/52 86%, 300/20 600/28 1000/54, 300/20 600/30 1000/48, 300/20 600/30 1000/52 80%, 300/20 600/34 1000/52, 300/22 600/32 1000/52, 300/22 600/32 1000/52, 300/24 600/34 1000/52, 300/24 600/36 1000/56 80%, 300/26 600/32 1000/56, 300/26 600/34 1000/54, 300/30 600/48 1000/58, 300/30 600/48 1000/58, 300/33 600/48 1000/52 92%, 300/33 600/48 1000/58, 300/16 600/27 1100/58, 300/19 600/29 1100/54, 300/26 600/34 1100/58 60%, 300/28 600/44 1100/58, 300/28 600/44 1100/62, 300/30 600/40 1100/58, 300/30 600/44 1100/60, 300/15 600/25 1200/60, 300/20 600/32 1200/63, 300/24 600/34 1200/62 80%, 300/30 666/46 1000/58, 300/17 700/35 1100/57, 300/28 700/52 1100/62, 300/30 700/46 1100/58, 300/16 700/33 1200/60 90%, 300/16 700/34 1200/63, 300/30 700/48 1200/68 86%, 300/30 700/48 1200/68 92%, 300/28 800/46 1200/60, 300/28 800/46 1200/60 76%, 300/25 900/56 1100/66, ? 900/40 ?, ? ? 900/46, ? ? 1000/45, ? ? 1000/50, ? ? 1000/56, ? ? 1000/56, ? ? 1000/56, ? ? 1000/58, ? ? 1000/60, ? ? 1000/74, ? ? 1100/55, ? ? 1100/56, ? ? 1100/58 70%, ? ? 1100/58, ? ? 1100/59, ? ? 1100/64, ? ? 1200/64, ? ? 1200/65, ? ? 1200/66, ? ? 1200/68, 300/33 600/48 800/58 1200/68
reported as unstable:
300/13 ? ?, 300/20 ? ?, 300/20 600/30 800/40, ? ? 900/46, ? ? 1000/56, ? ? 1000/60, ? ? 1100/53, ? ? 1100/54, 300/26 600/40 1100/58, ? ? 1200/60, ? ? 1200/66, ? ? 1350/76
Overclocked
[email protected]
[email protected]
[email protected]
[email protected]
My values are:
[email protected]
[email protected]
[email protected]
[email protected]
I Have Slim Defy wJellyBean4.3 and Works Like a Charm.
[email protected]
[email protected]
[email protected]
[email protected]
Have had these settings working nice and stable for a long time on CM7 then CM10. Now on Mokee 43.1 and seems good so far.
Also using Aero Control to overclock the GPU to 266Mhz, this has made quite a big difference. My Antutu score went from approx 4500 to 5000 and everything seems just a bit smoother. Only problem is I can't get Aero Control to retain the settings on boot.
MB526[Defy+]:
[email protected]
[email protected]
[email protected]
[email protected]
themaker69 said:
MB526[Defy+]:
[email protected]
[email protected]
[email protected]
[email protected]
Click to expand...
Click to collapse
Mine are:
[email protected]
[email protected]
[email protected]
[email protected]
everything's just fine with it.
Title is misleading
hoderer said:
Mine are:
[email protected]
[email protected]
[email protected]
[email protected]
everything's just fine with it.
Click to expand...
Click to collapse
I found this thread from a huge noob guide, it's disappointing to see it only refers to one type of phone i've never even heard of. I searched for overclocking Samsung Galaxy Mega and nobody seems to know anything yet. If anyone has tested settings for this phone, pls advise. I'm on a L600 Sprint tinkering around with a bunch of stuff, and overclocking is certainly on my to do list.
Related
what is maximum safe freq. for overcloking artemis ?
in some rom i see 247MHz in default,but Battrey Status can overclock it up to 312MHz!!!
mine is a standard T-Mobile MDA Compact III, and it runs at 201MHz (standard) The 'safe' clocking speed is usually up to 247MHz.
ive got mine scaled (so + and - scaling) and up to 247 with a boost to 273! No problemo's here. 286 goes with no problems too, but uses lots of battery power! I would not recomend to go any higher. The maximum can be different in different makes of the artemis. Ive heard ppl having problems with 286 already.
If you try out to go any higher, be sure to unselect the setting 'scale on reboot'! Then you can give it a SR and try a lower setting again!
I would say 247 as mine crashes above 260 and on 260 the text goes all fuzzy and moves around, like it's tripping.
thanks for your answers
is there any damage to CPU if I overclock it to 312MHz or just it don't work ?
also is there any way to reduce speed for longer battry life
Mine goes to 299MHz without problems, I have it set at a max of 286MHz for a while now without issues. But please see below.
The max frequency beyond which artifacts/faults show up could be different for each individual device - it depends on the production lot of the chip. The max possible frequency also depends on the ambient temperature a lot and generally worsens with ambient temperature - you could go overclocking to 299MHz when you are outdoors in the cold but it may conk out in warmer environments or when summer arrives! That is why I have mine set a notch below the max it can handle. You need to find out the max frequency of your particular device yourself by stepping it up one notch at a time and testing it with various apps for a few minutes continuously. Other's experiences are not useful in this regard. Some people wait a day or two but this is unnecessary as long as you test all scenarios - the thermal time-constant would be of the order of a few seconds.
The above applies to immediate faults which you can observe - there may be some long term repercussions when you overclock it for a period of months or years - the lifetime of the chip may go down slightly due to the higher internal temperature arising from overclocking - but I estimate this may be negligible.
I don't think anybody can brick a device permanently by just overclocking - when the overclocking is removed, it should boot normally. If anybody has experience in *permanently* bricking a device by overclocking, please share it here. BatteryStatus has couple of methods by which it can recover from this condition by removing the overclocking. BatteryStatus also has a neat CPUscaling feature which also saves power when the device is not being used.
-Ravi
I temporary overclock to 273 mhz by Battery Status when playing heavy videos or when I call by Skype, but for normal use my Artemis run very well with standard 201 mhz.
mine 286Mhz without any problem... But my device can't boot up with 299Mhz... keep on restarting...
Hi, I'm a noob to undervolting here (just rooted and flashed Vanilla Froyo to my Defy a week ago, and I'm hoping to squeeze out as much battery life as I can); just some quick questions about undervolting that I haven't found answers to in other threads:
1) What exactly is "vsel" and how does it relate to the actual battery voltage? For example, even though I've changed the maximum voltage in setvsel and Milestone Overclock (down to about 45 vsel at 800 Mhz so far, haven't tried lower), the battery voltage reported by Spare Parts is still reading between 3800 mV and 4000 mV. Does this mean that setvsel/milestone aren't working or does a ~30% decrease in vsel *not* equal a 30% decrease in battery voltage?
2) If anyone else has undervolted their Defy, can they testify as to what kind of battery life improvements they've gotten? I've heard that custom ROMs are already fairly undervolted
If laptops are anything to go by.. laptops can be undervolted to make them run less hot, thereby extending their life. Though battery life is increased too, this increase is virtually negligible.
Since the limits of undervolting (and over/underclocking), are done on a per-cpu/gpu basis for computers, because they are not all exactly the same and may not work with the same non-default values, I think it's a bad idea to assume that phones will run without problems when using values only tested by people with a phone that is not yours.
If you want to undervolt/over- or underclock, test your device, find out the lowest/highest values and then inrease or decrease that value, to have a safety margin, do not copy someone elses' settings.
A common issue with undervolting on 2.1 (at least with me on 2.1) is that if the minimum clock speed is below 300 mhz, it takes around 3-5 sec to actually respond to incomming call on your defy when defy is on stand-by mode.
Undervolting + Ondemand made my battery work at 23ºC vs +29ºC
I did not wrote down numbers, but battery life increased AT LEAST in 8 hours.
My values
vsel 1; 18 -300
vsel 2; 33 - 600
vsel 3; 43 - 800
(-15 points each value VS factory values)
Removing bloatware, root apps, autostart at boot apps, widgets (they autostart too) etc. or freezing them with "antitek app manager"
Decreased phone memory ussage from 140Mib to 80Mib; Also decreased cpu ussage from 10%-15% average idle to just 1%-5%
Apps / Widgets / Many System preinstalled apps, are autoloaded when phone is turned on, and they run 24/7. waste of resources and app auto killers just aren't good enough, coz apps reload themselves, you have to remove them or freeze them.
fortunely modders are realeasing their custom roms with most of this optimizations
45 vsel
using milestone oc I got 1ghz @ 45vsel from the day I got it I have owned the device for 1 1/2 months now not one single problem but it depends from device to device I must have a bin'd cpu
I am new to android phones. And i have no experience about overclock.
Will my cpu easily break down due to keep overclocking?..
Honestly, i seldom change my cell phone model, i want my defy can stay a life at least 1.5yr.
i think overclocking can't really damage your phone, voltage can. so i suggest you keep the voltage around [email protected] (default is [email protected], so this should be fine), and if the phone doesn't hang or reboot, you're good to go but you could try lowering vsels, you know, the lower the voltage, the lower the power consumption, the heat and the chance to fry your cpu but i'm not sure!
Yep, 1 GHz is safe, I'm using [email protected] as well, and the CPU is capable to run easily at [email protected] continuously. The leaked Gingerbread ROM from Motorola uses 1GHz as well, so don't worry, you just have to find the safe vsel settings.
thanks for replying, i m currently using 1GHz @ 58 .. Everything is alright
Should I make the voltage as low as possible?
yeah, just to lower the power consumption and temperature, but it isn't necessary.
Can you share your voltage setting please..?
I do the stability test and it gets successful run for 5min then this means the setting is okay?
i don't overclock, just undervolt, here are my settings (with setvsel):
800MHz - 45vsel
600MHz - 30vsel
300MHz - 18vsel
up_threshold: 90%
actually if you wanna make absolutely sure your device is stable, you should run it like for an hour. but if it runs for 5 minutes without error that's quite okay, you shouldn't have problems with those settings
Thanks so much, i m trying to lower my voltage setting.
Besides, i want to ask about the battery temperature, what is the maximum temperature before getting damage to the cell? I usually goes up to 37~39 degree celsius.. is it normal?
mine is usually around 29-32 °C, but i have it undervolted, so idk. but 37-39 seems a bit high, that means the cpu temp is way over 40 degrees, you should check it out!
EDIT: tried stress testing for 20 minutes with [email protected], it went up to 35°C, so you should definitely find out what's wrong with your device!
I actually underclocked to 600MHz, since I couldn't see a big difference even at 1200MHz in normal usage. A Pentium3 at 4Ghz will still not perform as well as a slower clocked new CPU for example, CPU design is more important - what instructions it supports.
Battery life is more imprtant to me and heat is very bad for Li-ion batteries too.
Also I found changing the CPU governor to "interactive" made a difference in GUI responsiveness and I have had less stuttering.
nisamtetreb said:
I actually underclocked to 600MHz, since I couldn't see a big difference even at 1200MHz in normal usage. A Pentium3 at 4Ghz will still not perform as well as a slower clocked new CPU for example, CPU design is more important - what instructions it supports.
Battery life is more imprtant to me and heat is very bad for Li-ion batteries too.
Also I found changing the CPU governor to "interactive" made a difference in GUI responsiveness and I have had less stuttering.
Click to expand...
Click to collapse
so, what's your standby lifetime after underclocked cpu?
I can see the performance improved when i was watching flash video on browser. But honestly, i dont think there are anymore huge difference after overclocking..
But as the battery life still remains quite well, i will still keep overclocking to 1GHz.. Isn't it a good idea?
nisamtetreb said:
I actually underclocked to 600MHz, since I couldn't see a big difference even at 1200MHz in normal usage. A Pentium3 at 4Ghz will still not perform as well as a slower clocked new CPU for example, CPU design is more important - what instructions it supports.
Battery life is more imprtant to me and heat is very bad for Li-ion batteries too.
Also I found changing the CPU governor to "interactive" made a difference in GUI responsiveness and I have had less stuttering.
Click to expand...
Click to collapse
lol... What happend to HD and THD games... Did u try playing them at 600mhz??
Overclocking to 1 GHz with the right voltage values seems to be absolutely no problem for Defy.
BTW, does anyone know whether it's possible to set scaling governor to "Interactive" mode under Froyo? Gingerbread kernel let me set it, but I haven't found the way under Froyo.
Battery life was a little bit better, the display and 3G always draw a lot of power.
Standby time got better, but I don't use very low vsel any more due to errors in YouTube and dropped connection of radio streams.
Before I used 300-600-800 at 20-30-48, this was very stable in stability test, but for example Youtube would start showing "error playing video". After I increased vsel, it went away.
I mostly did it to lower temperature, optimal temperature for li-ion is around 25°C according to Wikipedia I think.
I don't play 3d games, they would benefit the most from overclock I believe.
Angry birds RIO for example would stutter for a second or two after a level loaded, but it would become as smooth as at higher clocks, when I wait for a second.
I hope flash gets better, when hardware acceleration gets enabled in Quarx's CM7.
I was running [email protected] for a month straight. No issues at all. The highest my temp reached was 112F after playing games for about an hour straight. I now just run it at [email protected], and it's plenty fast for me. I did some "testing" with all the options in SetVsel. It's not science sound, but if you use the Gingerbread Icon in the notification bar, and are running at stock (800 speed) you will notice when the CPU maxes out it doesn't even reach full capacity. I found Words with Friends to really use the CPU, and at 800 it pings the meter in the orange (The notification icon shows green, orange, and red for "zones"). If I overclock it at 1000 or above then the meter goes into the red. I don't know the exact number it switches from orange to red, but being at stock 800 is well below what the chip can really do since it doesn't even max out the meter. I hope I didn't confuse anyone. It makes sense to me.
weird...my cpu at any game reach the 800mhz
yet even in normal situations like browsing through the files on the phone it reaches 800mhz
and also despite the values i use in setvsel are not high(which is:
24 @ 300
34 @ 600
48 @ 800
)
the phone still reaches maximum 38C when i play games and if i set the value in the third vsel the games starts to hang!!
seems like i am the only one who have these problems..but why
anyone have any idea
im running stock arabic froyo btw
if someone can confirm to me that i can keep Arabic language if i installed another rom using custom restore in nandroid then i would be using prays or official 2.3 but no one answered me about that
anyway the important thing is anyone knows why my cpu temp is always high?
Well ambient temperature is important too. If it is 30°C where you live and your phone's temperature is at 35°C I'd say you are good. If the outside temperature is 10°C and your phone is dat 40°C I'd say there is something wrong (unless you were playing games or watching a movie).
in my opinion, it is definitely safe that you overclocking to the leaked moto level.
however, the voltage is still a mystery.
there's no constant conclusion about this.
i'm using [email protected], [email protected], [email protected], and it works fine for me
I'm getting really annoyed. No problems clocking up to 1100mhz with stock voltage (58). But changing the voltage settings, even slightly, makes the phone more or less unstable.
Hello!
I recently noticed how frequencies 122MHz through 460MHz all employ the same voltage (900mV). I've come to understand that the higher the CPU frequency the faster your battery will drain. What I don't understand is why a higher frequency will drain your battery faster.
Is the only cause for higher battery drain when running a higher frequency, the higher voltage which comes with a higher frequency, or are there other factors?
If, then, a higher voltage is the only cause, then my battery would not drain faster if I clocked my minimum frequency at 460MHz instead of 122Mhz?
Thanks in advance to anyone who can shed some light on this!
Hi
cpu power consumption at a specific frequency is bound to its voltage.
you should test a voltage for a frequency while your device has 100% workload, because you could find a voltage so that your device is stable while being idle, but freezes when it needs to work. (for more information search for linux phc)
my conclusion:
the voltage for a specific frequency has minimum!
you can set your minimum frequency to 460 if you want to, since the screen consumes most power, it should not matter that much. i have set my minimum freq that high, too. I believe that way, my phone needn't raise the frequency when dooing simple stuff, like playing music.... but i am just guessing.
i theory it must get hotter than at lower frequencys, but i did not notice that.
i have had a palm pre and a custom kernel introduced a voltage on demand governor, which kept the device at 1ghz all the time, but changes the voltage with the workload. i think the developer of the awesome idea is "unixpsycho" ... i would like to see something similar on android.
greetings
matto
EDIT:
http://en.wikipedia.org/wiki/Dynamic_frequency_scaling
it looks like it is bound to the frequency, too!
~const*f*V^2
the Voltage is quadratic, that means it tkes a higher priorety.
e.g. lowering the voltage from 900mv to 800mv => (0.8^2)/(0.9^2) ~ 0.79
460mhz*0.79~363mhz
=> [email protected] consumes as much power as [email protected] (Stock)
A couple weeks ago, I installed SetCPU to help with battery life. It did great! But, I didn't see the amazing improvement that I thought I would.
So, I did some research and found out about Profiles. Profiles are settings that you can make that will be applied when certain conditions are met.
Below are the profiles that I have created on my Nitro. I have seen 11 to 12 hours of medium use from my phone with these settings. If you have any suggestions on changes, please let me know. I'd like to find the absolute best settings and share them for everybody.
Profile Name: Screen Off
Conditions: Screen Off
CPU Max: 384Mhz
CPU Min: 192Mhz
Governor: powersave
Priority: 90, Exclusive
Profile Name: Charging Any
Conditions: Charging Any
CPU Max: 1512Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 85, Exclusive
Profile Name: In Call
Conditions: In Call
CPU Max: 810Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 80, Exclusive
Profile Name: Battery <= 10%
Conditions: Battery <= 10%
CPU Max: 594Mhz
CPU Min: 192Mhz
Governor: conservative
Priority: 75, Exclusive
Profile Name: Battery <= 25%
Conditions: Battery <= 25%
CPU Max: 972Mhz
CPU Min: 192Mhz
Governor: conservative
Priority: 70, Exclusive
Profile Name: Battery <= 50%
Conditions: Battery <= 50%
CPU Max: 1242Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 65, Exclusive
Profile Name: Battery <= 75%
Conditions: Battery <= 75%
CPU Max: 1350Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 60, Exclusive
By setting the profiles base on battery percentage like that, you are sacrificing the speed to improve battery life. It works in some cases but has side-effect in many other cases:
- Firstly, for some tasks that requires high CPU, apparently you need more time at lower speed, so power consumption for CPU is the same but more power needed for longer screen on -> worse battery life
- Secondly, the more profiles you use, the longer it takes for SetCPU to decide and change CPU speed, so the responsiveness is lower
For you screen off profile, if you use powersave governor, your CPU always runs at min speed, so setting the max speed at 384 MHz is meaningless.
For me, the only profile I use is the screen off profile with min = 192MHz, max = 432MHz, governor = ondemand, so that my phone will wake up faster when there's a call (otherwise you will have to wait a little bit before you can sliding Answer/Reject)
noemtfj said:
By setting the profiles base on battery percentage like that, you are sacrificing the speed to improve battery life. It works in some cases but has side-effect in many other cases:
- Firstly, for some tasks that requires high CPU, apparently you need more time at lower speed, so power consumption for CPU is the same but more power needed for longer screen on -> worse battery life
- Secondly, the more profiles you use, the longer it takes for SetCPU to decide and change CPU speed, so the responsiveness is lower
For you screen off profile, if you use powersave governor, your CPU always runs at min speed, so setting the max speed at 384 MHz is meaningless.
For me, the only profile I use is the screen off profile with min = 192MHz, max = 432MHz, governor = ondemand, so that my phone will wake up faster when there's a call (otherwise you will have to wait a little bit before you can sliding Answer/Reject)
Click to expand...
Click to collapse
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
mattman86 said:
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
Click to expand...
Click to collapse
His point was that scaling your CPU back so significantly isn't necessarily going to give you better battery life, and may even make it worse. When the phone is running at a slower speed, it takes longer to do certain things, which means your CPU/screen will be turned on for longer. Of course it entirely depends on what you're doing on the phone.
I think you might get just as good battery life by using interactive 1.2GHz all the time. People assume governors like interactive will destroy their battery but you'd be surprised.
mattman86 said:
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
Click to expand...
Click to collapse
If you have to charge your phone every 3 hours without SetCPU then I suggest you buy a new phone or new battery rather than playing with SetCPU
drumist said:
His point was that scaling your CPU back so significantly isn't necessarily going to give you better battery life, and may even make it worse. When the phone is running at a slower speed, it takes longer to do certain things, which means your CPU/screen will be turned on for longer. Of course it entirely depends on what you're doing on the phone.
I think you might get just as good battery life by using interactive 1.2GHz all the time. People assume governors like interactive will destroy their battery but you'd be surprised.
Click to expand...
Click to collapse
I don't do much with my phone in the way of heavy gaming or video watching. I am going off of the last couple days of having SetCPU enabled and getting almost 15 hours of medium use out of my phone.
noemtfj said:
If you have to charge your phone every 3 hours without SetCPU then I suggest you buy a new phone or new battery rather than playing with SetCPU
Click to expand...
Click to collapse
It was an arbitrary number.
Does anybody find this kind of post meant to make peoples phones better helpful? It seems like every time I post something that I personally have found to make the Nitro even more awesome gets a tone of comments basically telling me that none of it will ever work. I'm sure that if people would just try the things I post, they would be happy.
my setcpu setting-> uninstall
i found it did more harm than good. jd ultimate handling screen dimming&wifi with simple ondemand gov works much better for me.
scott0 said:
my setcpu setting-> uninstall
i found it did more harm than good. jd ultimate handling screen dimming&wifi with simple ondemand gov works much better for me.
Click to expand...
Click to collapse
That what I've heard also... But I found that JD ran my battery down in about 6 hours without me even touching it one day.
If you have any suggestions on settings for it, I'd love to give them a try.
mattman86 said:
That what I've heard also... But I found that JD ran my battery down in about 6 hours without me even touching it one day.
If you have any suggestions on settings for it, I'd love to give them a try.
Click to expand...
Click to collapse
yeah, i guess it's diff for everybody, just like the roms eh, some get great batt perf on 1 and sucky on another and someone has exactly opposite.
anyhoo, my jd ultimate settings are
Status
advanced profile
graphical notification->quickbox
Controls
wifi enabled->wifi preferred
brightness min 20% mid 45% max 150% (gotta get the most of this screen in the sunlight!)
light sensor fast
cpu min 192 mid 918 max 1512
governor ondemand
schedules
none, i also turned off night schedule as i have the phone plugged in during those hours.
triggers
Apps enabled
Configure->configure apps allow on during screen off->pandora
Location enabled
****************i find it makes a world of difference to give jd =>3 days to get it all right.
make sure setcpu is out of the way as well.