Just a quick question, and I'm sorry if this is elementary, but do the custom kernels that up the FPS cap on the EVO effect battery life? I'm guessing that one of two things are happening:
a) The cap is based somehow on the CPU/GPU before output and upping the cap will put more load on the CPU/GPU, lowering battery life.
b) The cap is based on something dealing with the output and upping the cap will have minimal or no effect on the battery life.
Which ever way, I'd just like to know before diving in.
Related
So this 30 FPS cap is not gonna fly, can anyone give any input on which Kernel for lifting the cap does it the best while draining the least amount of battery life?
jasonleb1 said:
So this 30 FPS cap is not gonna fly, can anyone give any input on which Kernel for lifting the cap does it the best while draining the least amount of battery life?
Click to expand...
Click to collapse
depends on the screen you have. as far as i know there arent multiple builds of the kernel to deal with battery concerns.
if you have a epson screen, youre in luck there is a kernel that works, or so the thread says.
if you have a novatec screen, there is a kernel that is a work in progess, that for me wont work with fresh 0.5.3
as far as im concerned (for i shant speak for everyone) everything is a work in progress, but more progress has been obtained for epson screens.
Ok, thanks!
I just downloaded setcpu and as I was setting the profiles, I wondered if the frequent changing of CPU speeds could damage anything. For example, when the screen turns off, I set the speed to a low value, because I won't be using anything at that point. But when I start using the phone, it scales up to a bit higher speed. When the phone is charging, its at max speed, 995mhz. When the battery drops below 20%, the speed drops really low to conserve battery. Will these different scale values damage anything?
under clocking the phone will not have near the possibility of damaging the processor as over clocking. The main thing to worry about is the thermal specification of the processor. If you ride that limit too long, or surpass it, then you risk greatly reducing the life of your phone. But under clocking as in your case does not normally present that same form of danger.
elegantai said:
under clocking the phone will not have near the possibility of damaging the processor as over clocking. The main thing to worry about is the thermal specification of the processor. If you ride that limit too long, or surpass it, then you risk greatly reducing the life of your phone. But under clocking as in your case does not normally present that same form of danger.
Click to expand...
Click to collapse
bravo bravo!! /clap
if only we could install a xigmatek dark knight cooler on this thing. we could oc to 3ghz lol
I was wondering what were "optimum" SetCPU settings while running cyanogenmod 7?
Optimum for what? battery life? performance?
Of course, you could just keep it overclocked, as high as 1.8ghz I think depending on your kernel. But your battery life won't be that great.
You can also keep it at the stock 800mhz.
Most people I bet keep it around 1ghz, and have SetCPU profiles set up to lower CPU speed as battery levels get lower and lower.
I personally (not on CM7) set mine up to lower CPU a tad at 40%, even lower at 20%, and drastically lower at 10%.
I guess optimum for performance while saving battery life. I'm new to the whole overclocking and I'm not sure what profiles to set up
Sent from my HTC Vision using XDA App
Well the thing is its really all personal preference when it comes down to it. Just tweak with your settings and check out your results.
I mean optimal performance with maximizing battery life would follow a few basic profiles:
Screen off: 245min/245max
When <10%: 245min/~500max (my personal preference)
And if you're trying to keep your battery pretty decent, I would recommend keeping your clock speed at 1ghz or lower maximum. Anything higher you're gonna start seeing negative battery life.
There are many other things to do to lengthen battery life that aren't SetCPU related, such as managing your radios and networks.
So i have Daemon Controller 3.2 something and I've seen a lot of places mention undervolting. I looked around but couldn't find much information on it.. nothing extensive anyway. So my question is: what are the good things about undervolting (besides battery life) and what are the bad things?
If i undervolt and improve battery life does it decrease performance? Any info here would be awesome. Thanks!
Info here
http://forum.xda-developers.com/showthread.php?t=1611620
PatimusXPrime said:
So i have Daemon Controller 3.2 something and I've seen a lot of places mention undervolting. I looked around but couldn't find much information on it.. nothing extensive anyway. So my question is: what are the good things about undervolting (besides battery life) and what are the bad things?
If i undervolt and improve battery life does it decrease performance? Any info here would be awesome. Thanks!
Click to expand...
Click to collapse
The only thing I can think of that you might find as a benefit from U/V is improved battery life.
If you UnderVolt too far you risk freezing and/or damaging your device.
If you successfully undervolt without going too far and causing problems, you should see no negative effect on performance. Just better battery life.
I typically U/V around 50 for all clock ranges. I have never had any negative results doing this. But I haven't been able to prove I get better battery life either. I just take faith in the fact that I theoretically am. I do get wicked good battery life, but that is probably due to many things including kernel, rom, radio, clock speed settings, U/V settings, and other mods. All these together produce noticeable results, where any one by itself would not give any substantial or noticeable improvement.
TheAtheistReverend said:
The only thing I can think of that you might find as a benefit from U/V is improved battery life.
If you UnderVolt too far you risk freezing and/or damaging your device.
If you successfully undervolt without going too far and causing problems, you should see no negative effect on performance. Just better battery life.
I typically U/V around 50 for all clock ranges. I have never had any negative results doing this. But I haven't been able to prove I get better battery life either. I just take faith in the fact that I theoretically am. I do get wicked good battery life, but that is probably due to many things including kernel, rom, radio, clock speed settings, U/V settings, and other mods. All these together produce noticeable results, where any one by itself would not give any substantial or noticeable improvement.
Click to expand...
Click to collapse
Okay cool, I get pretty good battery life too so maybe I'll just skip UV.. no awesome reward just a lot of risk
There is a balance for reward vs risk there. Undervolting by 50 isn't going to put your phone in danger. But if it gets me a couple percent/an hour of battery life, why not?
I'm a believer in doing all the little things that add up to something substantial. Undervolt, Battery MOD, wifi policies, screen on time, charging habits, Kernel, ridding of problem apps, using things like Juice Defender, etc. These all add up to give me better battery life than you can find on almost any non-Max phone. But it takes all of them together, and a constant eye oout for something else I could be doing.
Undervolting may help you.
I havent been a big fan...on my og Incredible it caused nothing but problems with signal...so I dont anymore although the Sense kernel by Dres is undervolted a tad.
Give it a shot and start with -25 increments. Will it affect battery life? Maybe, but engineering tends to dictate that lower voltages dont always affect discharge rates. Higher voltages certainly affect consumption though (and can also lead to major problems).
TheAtheistReverend said:
The only thing I can think of that you might find as a benefit from U/V is improved battery life.
If you UnderVolt too far you risk freezing and/or damaging your device.
If you successfully undervolt without going too far and causing problems, you should see no negative effect on performance. Just better battery life.
I typically U/V around 50 for all clock ranges. I have never had any negative results doing this. But I haven't been able to prove I get better battery life either. I just take faith in the fact that I theoretically am. I do get wicked good battery life, but that is probably due to many things including kernel, rom, radio, clock speed settings, U/V settings, and other mods. All these together produce noticeable results, where any one by itself would not give any substantial or noticeable improvement.
Click to expand...
Click to collapse
I use the app SetCPU for CPU profiles. If I use something like Incredicontrol to undervolt, will it mess up my phone?
zaza224 said:
I use the app SetCPU for CPU profiles. If I use something like Incredicontrol to undervolt, will it mess up my phone?
Click to expand...
Click to collapse
The only way to mess up your phone is to U/V too far and have the "Save for Boot" box checked and no NAND backup.
Make your NAND and run the U/V settings you choose for a day or two before you check the save for boot box. If it freezes up back off your settings a notch and run it for a couple more days.
I run about 50 under without any problems.
Android 4.2.1
CyanogenMod 10.1 Snapshot M1 (21/1/13)
Franco Kernel R364
I'm trying to maximize my battery time.
(Power mode BeastlyBattery 192MHz~1036MHz, Governor: Lazy, IO Scheduler: deadline, Screen of Max Frew: 384MHz)
I want to UV my CPU (and maybe IVA and GPU also, does it helps too?) to save some battery.
Should I just decrease the voltage a bit, use stability test app and keep going till there will be errors,
or I can just decrease like someone else on the web and then keep going..?
Can it do something to the device? (because Its just undervoltage..)
For how long I need to run the stability test?
I saw this topic:
http://forum.xda-developers.com/showthread.php?t=1599025
and he says:
"1. It has been tested that the 700Mhz frequency is prefereable over the 300Mhz one, due to the drops on frequency signal of the phone."
Anyone tested this?
Does UV degrades preformance?
What is SmartFlex?
Anything else I need to know about that?
Im gonna make this one quick, so my apologies if I don't address your questions directly.
Prior to my Galaxy Nexus, I had a T-Mobile SGSII. I too had the belief that undervolting/clocking would improve my battery life substantially. It seemed to work but then I was only getting the results that I wanted to get, and thats because I went to extremes to lowering my screen brightness to minimum and using my phone a fraction of what I used to.
With the help of others and trial and error, my major conclusion is that undervolting/clocking, though normal headset use will not improve your battery life by a landslide. Android is so well optimized to save you as much battery as it can. Sure there are things here in there that interrupt that optimization such as bugs or kernel issues but that something even undervolting/clocking will not be able to solve.
If you do go into undervolting/clocking your device, please keep in mind that the most you will probably get out of it is maybe 45 minutes to 1hr extension, but thats not display time.
What you can do to improve your battery life is turn off whatever sync services you don't use, lower your screen brightness ( the display is the major battery hog in the GN and SAMOLED devices), use dark wallpapers and dark themes if apps support it, use wifi, disable 3G when not in use. The radio you use can also potentially affect your battery life and signal quality.
Those are just a few suggestions, the rest is up to you.
Good luck!
P.S. Kernels also add variation to the longevity of your battery life. It's been a very long time since I touched CM10 so I'm not gonna go and defame that ROM but do try something else that possibly offers better battery life. If MODs are a MUST for you, then you will be faced with a lower battery life compared to stock based ROM's. It won't be an extreme difference but the difference will be there. If I may suggest a ROM, try this one. I can honestly say I can get up to 3-4 hours of display time on it with about a 12 hour standby.
I read a lot on the web that it does help to battery time.. :S
anyone?
You're not going to see much difference. Running the cpu at a lower clock speed just means it will take longer to complete the same operation so you'll use just as much battery.
063_XOBX said:
You're not going to see much difference. Running the cpu at a lower clock speed just means it will take longer to complete the same operation so you'll use just as much battery.
Click to expand...
Click to collapse
And undervoltage?
Different overnor?
Undervolting will have minimal effect during actual use and a governor is based on specific user needs. One might save me battery while another works better for your usage. You need to actually mess with setting instead of just asking others what they use.