How does everyone feel? I've always assumed that it forces better battery life but I've noticed a lot of people do. I've done it till now just because I figured it has to help since every kernel I've used on any phone is under volted. Do you think it helps? Any kind of proof is welcome but so are opinions.
Sent from my Galaxy Nexus using XDA App
I'm on board with a modest under volt, but when you drop the voltages to the point that the phone is no longer 100% stable any minuscule battery savings would be undone by the forced reboot.
GN's cpu uses a power management technology called smartreflex which dynamically changes voltages used by different frequencies. The values that are set with setcpu and similiar apps are only the maximum voltages that smartreflex is allowed to use. The actual voltages may be well below the nominal ones.
Personally I never noticed any significant improvements. It's hard to tell how much but it is definitely not worth going really low. Right now I am using leankernel which is undervolted slightly by default.
codesplice said:
I'm on board with a modest under volt, but when you drop the voltages to the point that the phone is no longer 100% stable any minuscule battery savings would be undone by the forced reboot.
Click to expand...
Click to collapse
This.
Apps may stop working randomly or the phone may have random reboots if you mess with the wrong speed.
Honestly speaking, just go to setting...
1. then data and limit background data of certain unimportant apps
2. developer options > background process limit. Set it to like at most 3.
These ways are much safer and will boost your battery life.
Thanks. Right now I have a decently aggressive but stable UV but I'm gonna up them another 50mv just to be safe and do that. Thanks for the suggestion I didn't know I could do that. I'd hit thanks if I wasn't on a phone...
MilkPudding said:
This.
Apps may stop working randomly or the phone may have random reboots if you mess with the wrong speed.
Honestly speaking, just go to setting...
1. then data and limit background data of certain unimportant apps
2. developer options > background process limit. Set it to like at most 3.
These ways are much safer and will boost your battery life.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using XDA App
Related
ive only been rooted a day but can someone give me some advice on cpu speeds. assuming if i turn it up it will drain battery much quicker but whats a good speed to go for running cm7.
The stock HTC rom sets CPU speed to 1Ghz. So if you think your DHD was not fast enough, overclocking (i.e. moving the upper CPU frequency beyond 1Ghz) is a good option. Users here set the upper limit to either 1.2G, 1.3G, or 1.4G. 1.5G and above are not usually recommended because you may experence system hangs or reboot.
Overclocking not necessarily means larger battery consumption. Currrent custom kernels all use lower-than-stock voltages so the energy consumption is lower than that of stock. And the time CPU stays on the above-1G state in fact is not that much. You shouldn't worry about this.
ywliu
If you are satisfied with the original 1Ghz speed, and battery is your concern. You can lower the upper value to 800MHz or so to prolong battery use.
Also, CPU governor is another key issue. Choosing either Smartass/Smartass2, or On Demand usually is a safe bet.
great, thanks. i'll have a little play with the speeds and see what works. dont suppose you know if you can store more than one backup rom with rom manager/clockworkmod can you?
rhodri11 said:
great, thanks. i'll have a little play with the speeds and see what works. dont suppose you know if you can store more than one backup rom with rom manager/clockworkmod can you?
Click to expand...
Click to collapse
You can only backup Roms with cwm But you could keep the flashable zips. But that would mean a fresh install each time. Titanium backup maybe could help.
Sent from my HTC Desire HD using XDA Premium App
Is there any way to really monitor what's going on with my CPU?
I've installed SetCPU and checked my CPU limits, but it just doesn't feel to be changed. I've seen some posts about CPU figures just changing as figures, but the actual frequency remaining unchanged.
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
ImjuzCY said:
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
Click to expand...
Click to collapse
Any overclocking can be unsafe as it can shorten the lifespan of your memory and CPU. But with that said I run mine at 1200 with no issues. Most people don't go higher than 1600 but anything 1400 or lower is not going to burn it up too quick IMO. Everyones hardware will react differently though.
Sent from my Inspire 4G using xda app-developers app
They usually say phone will get damaged, but I think its a myth. You can go up to 1600. After that it will get unstable.
Sent from my Inspire 4G
ImjuzCY said:
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
Click to expand...
Click to collapse
I run IceColdSandwich and have found 1459MHz to be the best combo of performance and stability on my phone. Every phone handles OCing a little differently, some can reportedly take over 1600 without a flinch and others will lock regularly with even a slight OC. Just experiment with the "set at boot" option turned off until you find something that works reliably on your phone.
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Sent from my HTC Desire HD using Tapatalk 2
asif9t9 said:
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Sent from my HTC Desire HD using Tapatalk 2
Click to expand...
Click to collapse
I think OC can affect battery drain only if you use an application which utilizes a full cpu load. But, if you're using this app in normal mode, economy will not be great also. So, when you using your phone for calling or general usage you will not see any problems with battery discharge.
I'm using DHD with Blackout v3.0 and I set 1200Mhz for maximum cpu value. I have no problems, phone is stable. Some time ago I used Leedroid ROM and set also 1200Mhz, but phone was rebooted by itself very often. More than twice a day.
You should try to use OC, as someone said above, without "set on boot" option. I think there is no danger for hardware up to 1600Mhz.
asif9t9 said:
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Click to expand...
Click to collapse
Not under normal use. There's a school of thought that says even though the increased speed requires more power, it can also finish tasks and go back to sleep faster, so it ends up being a wash. I've overclocked all three smartphones I've owned to date and haven't experienced any significant difference in battery life.
ai6908 said:
They usually say phone will get damaged, but I think its a myth. You can go up to 1600. After that it will get unstable.
Sent from my Inspire 4G
Click to expand...
Click to collapse
They say that as a precautionary measure just as they say flashing a custom ROM can be dangerous. For people who don't know what they're doing. But precaution aside, just like you said you can go up to 1600 MHz safely on this phone. I know every phone behaves differently but on average no one has issues upto that frequency. But above that frequency the phone might be unstable. The CPU will be drawing much more power at high frequencies and will heat up more. The CPU heating up too much and too frequently reduces the life of the CPU. So it's not a myth.
Sent from my Desire HD using xda premium
2ghz.... the phone is old now. Make it bleed.
Sent from my Desire HD
Don't try to Cross above 1600.
I'm running SOA B2 with their kernel, in performance setting it allows me to go up to a maximum of 1836 MHz, is this safe?
Will battery life worsen?
Should I change the governor or I/O scheduler?
If you know what any of it means, it'd probably be best to stay away from it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have many app ideas, but don't have the skill or the time to learn how to make an app. if you would like to know an idea and attempt to make one, just message me.
Listen arianaLarge, don't bother replying if all you are gonna do is talk ****. Help the rookie out. This is a place for learning and contributing, its a community, it does not belong to you.
Having said that,.....you will lose stability and battery life if you go that high.
You will gain considerable performance but for what really?
Do you need it, probably not.
Personally I underclock to 1.18 for 80% of the day during the week, and run at 1.67ghz all day on the weekends. Its very easy to kick it up higher if you need the performance boost.
Also educate yourself on the various governors to better manage your CPU draw.
Google is your friend and the greatest tool you have for information.
Use tricksterMod or system tuner in the play store to manage CPU states and governors, both are free.
Both are great
there is no spoon.....
I never touch my CPU settings and use stock rom kernels....I've never seen a significant reason to bother with changing things. And I've never had hardly any of the problems I read in the rom dev threads.
Just my two cents.
Sent from my cell phone telephone....
Make sure you don't click the save on reboot button (or whatever it's called) because you may end up in a boot loop until you can flash some recovery to reset the setting. I don't think you're at too much of a risk, but the phone may not run stable and will likely shut down if it's pushed too hard. That's what I think.
Yes the battery life will be shorter. It may not be drastic unless you are constantly using it because the CPU speed will go back down when you idle.
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
What part of "you won't save more than 2%" you didn't understand?
ilusi0n_ said:
What part of "you won't save more than 2%" you didn't understand?
Click to expand...
Click to collapse
Well, i don't really understand WHY it doesn't save more than 2% of the battery life. Afaik, EXUV does reduce heat and improve battery life by miles. But that's what I thought. In reality which is this, im not rly sure why that even with EXUV, it still cant save more than 2% of the battery life.
Sent from my S800 China Phone
TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
I'm not technically expert with things like this but I have read an article/ blog before that undervolting may damage a phone since it was designed to work with that specific voltage. So, I actually didn't do that even UC or OC. Just saying.....
Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)
r25txe said:
Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)
Click to expand...
Click to collapse
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/samsung-kernel-msm7x30/commit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware
sir mordred said:
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/sa...mmit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware
Click to expand...
Click to collapse
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.
So to sum all this up. We just have to leave the CPU & voltage tables alone since it damages hardware?
Via the Internet
It's not that you have to, but that chip designer recommends it.
r25txe said:
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.
Click to expand...
Click to collapse
That was also the POST that I'm referring to that I've read :good:
Hi everybody,
I want to know if we can overclock our Snapdragon 808 to 2GHz (ARM A72 cores) with a modified kernel.
Also, If somebody is going to work on this challenge.
Thanks!!
Androsesp said:
Hi everybody,
I want to know if we can overclock our Snapdragon 808 to 2GHz (ARM A72 cores) with a modified kernel.
Also, If somebody is going to work on this challenge.
Thanks!!
Click to expand...
Click to collapse
A57 cluster, probably yes. I'm also working on a kernel, but I intensely dislike Overclocking because it isn't all that useful. The key to performance is with optimisation, not with raw power. So I'm most likely not going to include it, sorry.
What about underclocking and/or undervolting?
I think performance is good enough as it is, but would like to get better battery life.
I would like to be able to undervolt in order to relieve the bugging high temp warning. This phone rarely uses max performance. So, overclocking is not really a priority. Maybe a custom hotplug.
Crappy cpu. No point messing with it.
Sent from my A0001
GUGUITOMTG4 said:
I would like to be able to undervolt in order to relieve the bugging high temp warning. This phone rarely uses max performance. So, overclocking is not really a priority. Maybe a custom hotplug.
Click to expand...
Click to collapse
Hotplugging has been dropped not long ago. You'd basically need to reinvent it. Plus it costs more power than it would save
And what about undervolting to prevent excessive heat, @mythos234?
yea i guess undervolting is the only benefit here coz 2 ghz wont be hard to achieve but getting that overheating msg sooner aint worth it...
next thing u know is accessory back plates with mini fans to keep the phone cool...
seriously tho what good is the extra power for ? the phone is already fast with the correct setup (not that i saw any lag when it was stock)
anyone knows how to see the cpu binning in this phone?
oile said:
And what about undervolting to prevent excessive heat, @mythos234?
Click to expand...
Click to collapse
Excessive Heat?
mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
A number of people have gotten over-temperature messages, sometimes with the phones even shutting down.
This has been reported with using navigation, I believe, and I know people have reported it when shooting video. High screen brightness is likely a contributor. But there are examples of the phones running too warm.
Personally, I'd be more interested in cooler running, and longer battery life, rather than increased peak performance. So underclocking, if anything.
Well, the overclocking is not necessary, but is an opportunity to know the limits of the chipset. Moreover, with it we could know if we can make undervolting to our phones and make it more battery efficient with an underclocking kernel, when we need it.
RedOCtobyr said:
A number of people have gotten over-temperature messages, sometimes with the phones even shutting down.
This has been reported with using navigation, I believe, and I know people have reported it when shooting video. High screen brightness is likely a contributor. But there are examples of the phones running too warm.
Personally, I'd be more interested in cooler running, and longer battery life, rather than increased peak performance. So underclocking, if anything.
Click to expand...
Click to collapse
Happens to me too when gaming. The problem I observe is that Indeed, it is not excessive heat. But LG thinks otherwise.
You can actually underclock using Kernel Auditor and disable cores. Unless you meant Undervolting.
mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
Wanna check out periscope and comment back ? Atleast I know that app will push the phone to its limits.
Sent from my LG-H818 using XDA Free mobile app
Currently using Kernel Adiutor to disable both A57 cores and the phone screen does not heat up like before... Battery life has improved from what i saw yersterday. Continuing testing today. Only problem i have is the damn phone will enable one of the A57 cores after a while which i dont like. I need my settings to stick.
Any Kernel Dev know which files are causing this? Tab 3 had something like this but a couple of files changed solved the non sticking settings on cpu.
Overclocking/underclocking sure but just disabling cores would work for most.
Sent from my LG-H815 using Tapatalk
mythos234 said:
Excessive Heat?
Click to expand...
Click to collapse
lol, you're funny.
marcadam said:
lol, you're funny.
Click to expand...
Click to collapse
I haven't had any popups or heat related reboots, so I was wondering what the matter is here.
On every phone I see complaints over heat so I wondered if something is to it here or if it's the usual. And if there are overheating warnings and shutdowns, then there might be indeed something in the bush.
Try charging your phone in the car whilst using google maps to get to an important meeting, and then take a call just for good measure............and boom, there you have your own little meltdown.
marcadam said:
Try charging your phone in the car whilst using google maps to get to an important meeting, and then take a call just for good measure............and boom, there you have your own little meltdown.
Click to expand...
Click to collapse
That happens on every phone I ever had though. It's advised to not use a device while charging at all, so if you stress it to 120% while charging, of course it heats up..
@mythos234 is a pleasure to have you here (speaking as xiaomi mi2s owner too xD)
What Temps do you reach using cpu intensive apps?