This is a short guide with a few apps that can save a lot of battery life when used correctly. They will not drastically affect performance for most users.
Root is required for these.
First App - Juice Defender Ultimate (https://play.google.com/store/apps/details?id=com.latedroid.ultimatejuice&hl=en)
There is a lot of talk about if this uses more battery than it saves. But from my experience it saves a lot of battery. It mainly does this by turning off data/wifi while the screen is off and schedules it to turn on for syncing. Sure, you could do this yourself, but why not automate it?
Settings for this go as follows.
STATUS TAB---advanced
CONTROLS---mobile data, enabled---wifi,enabled---autosync,ping---disable everything else
SCHEDULES---enabled---frequency,15m or 30m.---duration,30s---controls,default---night,enabled,whenever you go to sleep to when you wake up,---
TRIGGERS---battery,enabled---threshold,5%---charger,ac---screen,enabled---traffic enabled---threshold,normal,30s---location,enabled.
If I didn't list an option keep it on it's default setting.
Second App - SetCPU (https://play.google.com/store/apps/details?id=com.mhuang.overclocking&hl=en)
This is what we will use to keep the processor at the power it needs to be for certain situations.
PROFILES
Temp>40.C------1000max 51 min---priority 100 (this keeps the phone from overheating and damaging the battery)
Screen off-------340 max 51 min---priority 95 (saves battery while screen is not on)
Charging--------1500 max 51 min--priority 90
Battery<10%----1000 max 51 min--priority 51
Battery<31%----1200 max 51 min--priority 46
Battery<51%----1400 max 51 min--priority 41
Battery<101%---1500 max 51 min--priority 31
Third App - CoreControl (http://forum.xda-developers.com/showthread.php?t=1652136)
This app while allow you to turn off cores of your processor.
Set this to use only 2 cores. This will save a good deal of battery, the only time you really need 4 core is for tegra gaming. You can just set it back to 4 if you plan on doing a lot of gaming.
Other tips:
Use a tweak such as the one in leedroid tweaks to lower autobrightness levels. This will save a noticeable amount of battery.
brentett said:
Third App - CoreControl (http://forum.xda-developers.com/showthread.php?t=1652136)
This app while allow you to turn off cores of your processor.
Set this to use only 2 cores. This will save a good deal of battery, the only time you really need 4 core is for tegra gaming. You can just set it back to 4 if you plan on doing a lot of gaming.
Click to expand...
Click to collapse
Tegra 3 does that automatically.
DarkDvr said:
Tegra 3 does that automatically.
Click to expand...
Click to collapse
Yea but it still actives more than 2 cores when doing general tasks sometimes, it's more of a guarantee it won't ever cross 2 by using the app, or editing the tegra_hotplug file itself.
DarkDvr said:
Tegra 3 does that automatically.
Click to expand...
Click to collapse
Yes it doesn't use all 4 cores all the time, but occasionally it will use more cores than it needs to so to get around that you force it to only use 2.
brentett said:
Yes it doesn't use all 4 cores all the time, but occasionally it will use more cores than it needs to so to get around that you force it to only use 2.
Click to expand...
Click to collapse
And you think that "occasional" usage of 2 more cores will drain the battery significantly enough to make this change?
I doubt it, but nice to have options.
DarkDvr said:
And you think that "occasional" usage of 2 more cores will drain the battery significantly enough to make this change?
I doubt it, but nice to have options.
Click to expand...
Click to collapse
It may not save tons of battery, but every little bit adds up and it's worth doing because it doesn't affect performance for many people. You could also play games using only 2 cores which would also save battery, versus using all 4 cores.
brentett said:
It may not save tons of battery, but every little bit adds up and it's worth doing because it doesn't affect performance for many people. You could also play games using only 2 cores which would also save battery, versus using all 4 cores.
Click to expand...
Click to collapse
So it's like buying a car with v8 and then run it on 4 cylinders because it has too big fuel consumption. To be honest I don't get it (no offence)
maxld said:
So it's like buying a car with v8 and then run it on 4 cylinders because it has too big fuel consumption. To be honest I don't get it (no offence)
Click to expand...
Click to collapse
Well its to save battery, and it's exactly like your analogy to fuel consumption. You sacrifice some potential, most likely never used performance for more battery life. How many people with a v8 race it on an open track everyday full-throttle? But how many people use their v8 to commute to work? There's are other reasons people may have bought this phone then to run it at its max performance all the time. I didn't buy this phone with the intent of playing tegra 3 games 8 hours a day. I liked the build quality, the camera, the software in addition to its processing power. Obviously if you want to use all the performance your phone has to offer then disregard battery saving options, I just know there are some people that would rather have more battery life.
maxld said:
So it's like buying a car with v8 and then run it on 4 cylinders because it has too big fuel consumption. To be honest I don't get it (no offence)
Click to expand...
Click to collapse
I agree I've tested locking it 2 cores vs 4 and there is not enough battery improvement to even consider it and as for juice defender I can do that using power options widget or the sense quick toggles removing the need of that app saving more power.
And set CPU still allows for your clock speed to go over max set.
Sent from my HTC One X using xda premium
brentett said:
Well its to save battery, and it's exactly like your analogy to fuel consumption. You sacrifice some potential, most likely never used performance for more battery life. How many people with a v8 race it on an open track everyday full-throttle? But how many people use their v8 to commute to work? There's are other reasons people may have bought this phone then to run it at its max performance all the time. I didn't buy this phone with the intent of playing tegra 3 games 8 hours a day. I liked the build quality, the camera, the software in addition to its processing power. Obviously if you want to use all the performance your phone has to offer then disregard battery saving options, I just know there are some people that would rather have more battery life.
Click to expand...
Click to collapse
I have to say that maybe you have a point here. Some people will be surely interested in some more battery juice.
not a great believer myself regarding juice defender or any other similar apps..but kinda changed my mind regarding them few days ago and have seen some considerable difference..i know with the way android is now you can set them all yourself and i fell for the hype and got juice defender ultimate....but so far not complaining...time will tell
thanks OP anyway
Does SetCpu work on un rooted phones? I had my Desire rooted and used it, but haven't done my One x until I am a bit more confident. Would like to use SetCpu though, it works a treat :-D
RBFesquire said:
Does SetCpu work on un rooted phones? I had my Desire rooted and used it, but haven't done my One x until I am a bit more confident. Would like to use SetCpu though, it works a treat :-D
Click to expand...
Click to collapse
Nah, sorry it only works on rooted phones.
Related
[Q] Paradox with underclock & battery savings, does it actually hurt? SetCPU, etc.
In theory, using SetCPU or other underclocking app to reduce CPU clock should reduce the power draw from the CPU, therefore reducing battery consumption.
However, underclocking does not reduce the amount of work that needs to be done. That is to say, whatever app or kernel processing that needs to be done will still be done. When UC'ed, they will be done at a slower pace, therefore taking longer time. In some cases, the UI becomes sluggish, requiring more user interaction time as well.
If, at 1Ghz, a process takes 10 seconds to complete and requires 10mA per second. This task should consume 100mA. By underclocking to 500mHz, perhaps the CPU takes only 6mA, but the task will require 20 seconds to complete. Now the task actually takes 120mA (plus the longer screen on time).
Is my theory sound?
Also, does the constant scaling itself consume power?
As far as I know, Froyo is supposed to scale the CPU anyway. So why underclock? Does it actually work or does it hurt the battery life?
Input please!
Thanks.
Edit: I know the function of CPU speed vs. efficiency vs. battery drain is never linear, and each situation has a different break-even point, but I'm curious the general application of underclocking within the Android environement and its effect on battery life, and more specifically, the Evo.
i'm a regular dude with a phone, but im educated...that being said im sure your aware of the diminishing marginal utitlity law. For example if me and you can mow a lawn in 2 hours, and we got one more guy, we can do it in in less than two...Bu you eventually reach a breakoff point where it is hurting you and those extra guy(s) are not needed and acutally slow down the process or are just a waste. Same thing here, although i am not sure of the numbers, im positive there is a sweet spot for underclock and if you go too low it actually is a waste or hurts battery life. It also could be in the middle meaning, im going to make up numbers. 1ghz uses 100 Mah in 10 seconds. 800 mhz used 50 mah. 900 uses 60 mah. Now, the difference ratio of battery usuage and spees would lean you towards using 900 because if you relate this to sales on products or even anything, for lack of better words this setting is the best abng for your buck...my 2 cents
http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNFlNlZCm-gnvD1PzEsDezCIPeA8jQ
Sent from my PC36100 using Tapatalk
Interesting stuff... Take a look at this thread:
[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock
The data seem to suggest that underclocking an Evo at idle yields real results. I would think that this can only work if there is not a lot of background/idle tasks going on?
snovvman said:
Interesting stuff... Take a look at this thread:
[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock
The data seem to suggest that underclocking an Evo at idle yields real results. I would think that this can only work if there is not a lot of background/idle tasks going on?
Click to expand...
Click to collapse
both pics depicts very different device usages. not a fair comparison imo.
quocamole said:
both pics depicts very different device usages. not a fair comparison imo.
Click to expand...
Click to collapse
Yea I went through and read the whole thread. I'm now even less convinced that SetCPU provides any tangible battery benefits at all.
snovvman said:
Yea I went through and read the whole thread. I'm now even less convinced that SetCPU provides any tangible battery benefits at all.
Click to expand...
Click to collapse
Do you think i am right on any part of which i said or am i talking out of my arse lol
A microprocessor does not live by its clock alone. lol
It can cycle through a huge math operation, which is loaded into its registers lickity split with a fast clock. It will have to wait while the memory/code of the programs it runs are loaded either into its cache memory or into execution space. So in calculating theoretical energy use, you got to figure the bus speed, as well as the type of operations the processor is doing.
Golly, ( pronounced like a resident of Mayberry) the bus is key on loading programs to be run. What's the bus clock triggered off? That's the key. You don't want the bus to slow while slowing the cpu. If you can cycle the processor while it prefetches then you've got optimal use, providing it isn't thrashing.
Google cpu wait states for bus synchronization
This is basically the reason HAVS is supposed to be better than static scaling and underclocking. With HAVS, voltage is based on workload as well as clock speed, so you should get the benefits of running fast/idling more often combined with the benefits of using as low of a voltage as possible. As long as you don't have something pegging the CPU at 100% all the time in the background, it should, in theory, work better.
In practice, I haven't seen all that much of a difference.
iitreatedii said:
i'm a regular dude with a phone, but im educated...that being said im sure your aware of the diminishing marginal utitlity law. For example if me and you can mow a lawn in 2 hours, and we got one more guy, we can do it in in less than two...Bu you eventually reach a breakoff point where it is hurting you and those extra guy(s) are not needed and acutally slow down the process or are just a waste. Same thing here, although i am not sure of the numbers, im positive there is a sweet spot for underclock and if you go too low it actually is a waste or hurts battery life. It also could be in the middle meaning, im going to make up numbers. 1ghz uses 100 Mah in 10 seconds. 800 mhz used 50 mah. 900 uses 60 mah. Now, the difference ratio of battery usuage and spees would lean you towards using 900 because if you relate this to sales on products or even anything, for lack of better words this setting is the best abng for your buck...my 2 cents
Click to expand...
Click to collapse
iitreatedii said:
Do you think i am right on any part of which i said or am i talking out of my arse lol
Click to expand...
Click to collapse
What you wrote makes sense and the concept is sound. I just wish we knew what that sweet spot is, although I think it changes constantly based on load, code, and operational requirements.
With the two posts above, it would seem like phone manufactures would do everything they can to optimize efficiency. Having SetCPU loaded for 24 hours, I too, can say that I have not seen a huge difference...
Noxious Ninja said:
This is basically the reason HAVS is supposed to be better than static scaling and underclocking. With HAVS, voltage is based on workload as well as clock speed, so you should get the benefits of running fast/idling more often combined with the benefits of using as low of a voltage as possible. As long as you don't have something pegging the CPU at 100% all the time in the background, it should, in theory, work better.
Click to expand...
Click to collapse
Does the stock HTC kernel, 2.6.32 "#11" have/use HAVS?
I've been using CyanogenMOD 7 and love it (mostly). The one thing I don’t like about it is the short battery life. I'm kind of new to rooting phones so it took me a bit to get it rooted and get CM7 rolling. I was wondering if there are any mods out there like CM7 that have better battery life? Or if there's any thing I can add to CM7 to give it more batter life?
I've been using android since the first phone came out so I’m already knowledgeable in what to turn off to try and extend the battery life, but I have noticed a big decrees in batter since installing CM7.
Thanks for the help guys
Trench
You can under clock the processor when your phone is asleep. This creates better battery life.
Sent from my HTC Vision using XDA App
Have you tried wiping battery stats?
evilcuber said:
You can under clock the processor when your phone is asleep. This creates better battery life.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
your phone automatically underclocks your processor when it sleeps (for most CPU governors), you do not need to tell it to do so.
I'm not picking on you fyi, I'm just making sure we are giving people accurate information... there's only one thing worse than no information: incorrect/incomplete information.
op: which version of CM7 are you running? remember, the more minimal your setup (ie less homescreens, less widgets, manual syncing of gmail and whatever else, etc) the better your battery life will be. this is especially true of newer phones that are getting heftier cpu & gpus that, while intelligent with power consumption, are going to drain even larger capacity batteries relatively quick with moderate/heavy usage.
how long are we talking with battery life? how heavy a user are you? for reference, I get around 16 hours of battery life if I don't charge the phone at all from unplugging to battery dying with moderate to heavy usage (texting ~50 times a day, sometimes up to 100 emails depending on what's happening at work, couple hours of calls, couple hours of streaming music [pandora or audiogalaxy], couple of hours of games [peggle and plants v zombies mostly - both of which are resource hogs], etc).
I have just learned to get used to the fact that the phone is going to die if I use it a lot, so I've purchased three micro-usb cables and a car charger.. that way, unless I'm in an area where there is no charge-capable usb port nearby, I'm always able to get a little more juice if need be.
pmcqueen said:
your phone automatically underclocks your processor when it sleeps (for most CPU governors), you do not need to tell it to do so.
I'm not picking on you fyi, I'm just making sure we are giving people accurate information... there's only one thing worse than no information: incorrect/incomplete information.
op: which version of CM7 are you running? remember, the more minimal your setup (ie less homescreens, less widgets, manual syncing of gmail and whatever else, etc) the better your battery life will be. this is especially true of newer phones that are getting heftier cpu & gpus that, while intelligent with power consumption, are going to drain even larger capacity batteries relatively quick with moderate/heavy usage.
how long are we talking with battery life? how heavy a user are you? for reference, I get around 16 hours of battery life if I don't charge the phone at all from unplugging to battery dying with moderate to heavy usage (texting ~50 times a day, sometimes up to 100 emails depending on what's happening at work, couple hours of calls, couple hours of streaming music [pandora or audiogalaxy], couple of hours of games [peggle and plants v zombies mostly - both of which are resource hogs], etc).
I have just learned to get used to the fact that the phone is going to die if I use it a lot, so I've purchased three micro-usb cables and a car charger.. that way, unless I'm in an area where there is no charge-capable usb port nearby, I'm always able to get a little more juice if need be.
Click to expand...
Click to collapse
but i also mean setting the max sleep to 368mhz. by default its set at 800mhz. sometimes with apps running in the background, the processor may go to 800mhz without you knowing
check out 'powersave' and set your cpu max to 806mhz. should last you a nice long time like that. responsiveness suffers, of course.
'ondemand' and 806mhz is the best comprimise for me. still fine with HDvideo recording, streaming audio, Nav, etc
if you really want to make it last... clock down to 400mhz, turn off all the sync, set brightness and timeout to minimum, all the radios off (airplane mode), and the volume down, on vibrate.
;-)
pmcqueen said:
your phone automatically underclocks your processor when it sleeps (for most CPU governors), you do not need to tell it to do so.
I'm not picking on you fyi, I'm just making sure we are giving people accurate information... there's only one thing worse than no information: incorrect/incomplete information.
op: which version of CM7 are you running? remember, the more minimal your setup (ie less homescreens, less widgets, manual syncing of gmail and whatever else, etc) the better your battery life will be. this is especially true of newer phones that are getting heftier cpu & gpus that, while intelligent with power consumption, are going to drain even larger capacity batteries relatively quick with moderate/heavy usage.
how long are we talking with battery life? how heavy a user are you? for reference, I get around 16 hours of battery life if I don't charge the phone at all from unplugging to battery dying with moderate to heavy usage (texting ~50 times a day, sometimes up to 100 emails depending on what's happening at work, couple hours of calls, couple hours of streaming music [pandora or audiogalaxy], couple of hours of games [peggle and plants v zombies mostly - both of which are resource hogs], etc).
I have just learned to get used to the fact that the phone is going to die if I use it a lot, so I've purchased three micro-usb cables and a car charger.. that way, unless I'm in an area where there is no charge-capable usb port nearby, I'm always able to get a little more juice if need be.
Click to expand...
Click to collapse
But some govenors don't drop the sleep to the lowest profile. In fact almost all keep it above the lowest clock. Other kernels allow it and you can also use third party to set it lower. When the tweaKr script becomes universal it will be even better =)
Sent from hells ghost chili mexdroid
ohgood said:
check out 'powersave' and set your cpu max to 806mhz. should last you a nice long time like that. responsiveness suffers, of course.
'ondemand' and 806mhz is the best comprimise for me. still fine with HDvideo recording, streaming audio, Nav, etc
if you really want to make it last... clock down to 400mhz, turn off all the sync, set brightness and timeout to minimum, all the radios off (airplane mode), and the volume down, on vibrate.
;-)
Click to expand...
Click to collapse
It suffers in powersave because it stays at the lowest setting only. No reason to set to 806. Lol and that bottom comment is hella funny =), but if he does that his phone will just be...a waste of pocket space.
Your best bet is to do some research on kernels. If you are using cm7 to cm 7.0.3 id recommened pyros kernel. If you are on 7.1 or a nightly over 121 I believe id go with eugene's streamline5. It did wonders for mine Also there is a battery saving tips. Google G2 battery saving tips. Should be first link that comes up.
Cyanogenmod roms are known to be battery hungry. Nom nom nom.
Sent from hells ghost chili mexdroid
cjward23 said:
Have you tried wiping battery stats?
Click to expand...
Click to collapse
I used the battery califration app if that's what you mean.
Thanks for all the help guys, i'll check out some Kernals.
popimp315 said:
Your best bet is to do some research on kernels. If you are using cm7 to cm 7.0.3 id recommened pyros kernel.
Click to expand...
Click to collapse
Do you have link for this? I'm running 7.0.3.. but I dont think im finding the correct Kernal.
Mugen 3600mah = better battery life...
Can you elaborate on what kind of battery life you are getting now? How many hours, and for what level of usage?
How long have you been on CM? It takes a couple charge cycles of the battery after flash any ROM, for the battery meter to be accurate. Clear battery stats (as mentioned) then charge to 100%, let drain to about 20%, repeat a couple times. Don't drain until the phone dies. Some people say to do this, and its not good advice. Over discharge of Li ion batteries can cause them to no longer take a charge. There are people on here, on the Vision and other phones, that let their battery drain to empty, then the phone would no longer boot, forcing them to replace the battery.
Mog said:
Mugen 3600mah = better battery life...
Click to expand...
Click to collapse
It has good battery life but the battery sticks out a lot and its very uncomfortable
Sent from my HTC Vision using XDA App
evilcuber said:
It has good battery life but the battery sticks out a lot and its very uncomfortable
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yup its all opinionated. I would never go back to stock.
Sent from my T-Mobile G2 using XDA App
trench619 said:
Do you have link for this? I'm running 7.0.3.. but I dont think im finding the correct Kernal.
Click to expand...
Click to collapse
Dev section
Sent from my HTC Vision using XDA Premium App
Which kernel do you guys prefer? Gladdos is awesome because I love its app with sound options . App seems to also work with Franco kernel though, but as far as reliability and performance goes, which do you guys like more?
Sent from my Galaxy Nexus using XDA
Both are very stable. Use the one that you like more. Franco also has an app.
Sent from my GT-P3113 using xda premium
Personally I'm a big fan of the CM9 kernel. I use CMPlus by Cheekybutt simply because headphones sound like crap without Ezekeel's high performance audio mod.
I use Glados. Its outstanding. I find I can oc higher much more reliably. I use 1.6 for everyday usage which is not even seen as an option on many other kernels. on a lot of other kernels, Franco included I can't run higher than 1.35 CPU and 384GPU. I run 1.6 and 512 with glados. And the app kicks ass with tons of adjustable features!
M3drvr said:
I use Glados. Its outstanding. I find I can oc higher much more reliably. I use 1.6 for everyday usage which is not even seen as an option on many other kernels. on a lot of other kernels, Franco included I can't run higher than 1.35 CPU and 384GPU. I run 1.6 and 512 with glados. And the app kicks ass with tons of adjustable features!
Click to expand...
Click to collapse
512 GPU doesn't make a difference.. neither really does OC or UC
"Long is the way, and hard, that out of hell leads up to light."
joshnichols189 said:
512 GPU doesn't make a difference.. neither really does OC or UC
"Long is the way, and hard, that out of hell leads up to light."
Click to expand...
Click to collapse
I heavily beg to differ. I notice a difference immediately. Everything is smoother when I do oc.
Just tried ocing the gpu in glados kernel and wow, definitely a difference! Now, at 504mhz, does it effect our battery life in a major way?
Sent from my Galaxy Nexus using XDA
Glados with the wheatley gov.
Awesomesauce.
Sent from my Galaxy Nexus using XDA
afive720 said:
Just tried ocing the gpu in glados kernel and wow, definitely a difference! Now, at 504mhz, does it effect our battery life in a major way?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
From what I've heard (not tried), the gain from OC'ing is minimal and battery consumption increase is quite big.
Swyped on my CM9 Galaxy Nexus
why do you even need to overclock? To me battery life is most essential factor and I have yet to come across a kernel that can give me satisfactory results, stock included. The screen on this thing is beautiful but eats battery like no other. I can't wait for Verizon to have a larger Note like device so we can have a larger battery.
The battery life on this phone is amazing for a Verizon LTE phone. Before I activated the phone I played with it around the house for about a week (had to take care of some things before I quit using the iPhone). I went 25 hours with 3 hours of display time. Mind you this was all on WiFi and since it wasn't activated there was no talk time. LTE is the battery destroyer not so much the screen. I have never ran this phone stock, so I have no benchmark to compare it too, but the charging times on the Franco kernel are insane. Went up 65% in 1 hour over a car charger.
I'll have to check out the Gladdos kernel.
what car charger do you have and what apps were you running? I have a 1.2amp usb charger from monoprice and with maps and pandora on it charges for a bit before it gets too hot and switches to "not charging" to not overheat. Then it stays at about the same battery level, give or take a few %
Something similar to this....http://www.newegg.com/Product/Product.aspx?Item=9SIA07Y02A5396. Since it's dual port I'm sure it has a bigger fuse.
M3drvr said:
I heavily beg to differ. I notice a difference immediately. Everything is smoother when I do oc.
Click to expand...
Click to collapse
I suggest reading through the Franco.Kernel thread.. everything above 384 is minimal at best.
"Long is the way, and hard, that out of hell leads up to light."
ashish8 said:
The battery life on this phone is amazing for a Verizon LTE phone. Before I activated the phone I played with it around the house for about a week (had to take care of some things before I quit using the iPhone). I went 25 hours with 3 hours of display time. Mind you this was all on WiFi and since it wasn't activated there was no talk time. LTE is the battery destroyer not so much the screen. I have never ran this phone stock, so I have no benchmark to compare it too, but the charging times on the Franco kernel are insane. Went up 65% in 1 hour over a car charger.
I'll have to check out the Gladdos kernel.
Click to expand...
Click to collapse
which brings me back to the another comment I made in another thread, LTE speeds for a phone is unnecessary. Lose battery life and pay up the wazooo if you don't have unlimited data (soon all of us)? Just a way for the big red to justify charging more. #switchingoffLTE
joshnichols189 said:
I suggest reading through the Franco.Kernel thread.. everything above 384 is minimal at best.
"Long is the way, and hard, that out of hell leads up to light."
Click to expand...
Click to collapse
Then why offer a 512oc if its nothing? Reality is, the phone is noticeably smoother with it. And virtually no hit on battery life. I'm still getting high 3 hours screen on time and 20+ hours battery life. I'll take the much smoother experience for minimal battery life hit.
M3drvr said:
Then why offer a 512oc if its nothing? Reality is, the phone is noticeably smoother with it. And virtually no hit on battery life. I'm still getting high 3 hours screen on time and 20+ hours battery life. I'll take the much smoother experience for minimal battery life hit.
Click to expand...
Click to collapse
Much smoother? Exaggerate much??
And as for battery life, I get 5hrs screen on with 384.
Games run smoothly, UI is smooth, what more do you need.
If you can run 512 then why not but it does not make that much of a difference.
I have used both and I find no difference.
nodstuff said:
Much smoother? Exaggerate much??
And as for battery life, I get 5hrs screen on with 384.
Games run smoothly, UI is smooth, what more do you need.
If you can run 512 then why not but it does not make that much of a difference.
I have used both and I find no difference.
Click to expand...
Click to collapse
Well, for me on my phone, its a major difference between 384 and 512. And I've seen several people comment that it is a difference on their phone too. Web pages scroll is jerky on 384 for me, and with 512 its perfectly smooth. I've never ever gotten 5 hours screen on time with any setting I've ever chosen on my phone so thats not even in the question. Max ever was 4:30 screen on, that was with screen brightness lowest possible, entire time with wifi, which is not even in the question for me on a normal day. Normal for me is high 3's.
Anyways, we all know none of these phones are the same. They react differently to different settings. All I know, is on my phone, 512 is by far smoother than 384. And at a 40% OC of the CPU (1680-1700mhz) the phone is also noticeably faster. And actually, on my old Galaxy S, 1400 was the magic number i needed for things to actually FEEL and LOOK faster, which was 40% more. Anything less than that, I couldn't notice a boost. Thats just my thought on my phone.
Its very easy to see the difference in scrolling smoothness between 512gpu and 384gpu.
All you have to do is go to theverge.com mobile site and just scroll up and down using the stock browser.
The difference is very noticeable.
Glados 1.34 seems to resolve data drop issue, so I've stuck with it for now.
Sent from my Galaxy Nexus
I have a doubt , whether enabling two core and disabling the other won't cause damage to the enabled one as they will be overclocked when performing some high end task ?
I am afraid of that and not disabling the two . But I like to use if they save battery.
Sent from my HTC One X using Tapatalk 2
forumhookersdotcom said:
I have a doubt , whether enabling two core and disabling the other won't cause damage to the enabled one as they will be overclocked when performing some high end task ?
I am afraid of that and not disabling the two . But I like to use if they save battery.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Overclocked? They will run at a maximum of 1.5GHz, regardless of how many cores are active, unless you overclock them.
I have my One X constantly set to dual core mode and haven't experienced any problems as of yet. Quad-core is massive overkill at the moment on Android and is completely unnecessary.
Meltus said:
Overclocked? They will run at a maximum of 1.5GHz, regardless of how many cores are active, unless you overclock them.
I have my One X constantly set to dual core mode and haven't experienced any problems as of yet. Quad-core is massive overkill at the moment on Android and is completely unnecessary.
Click to expand...
Click to collapse
Won't they get destroyed as they are running at maximum clock ?
Do they save battery , enabling only two cores.
Sent from my HTC One X using Tapatalk 2
forumhookersdotcom said:
I have a doubt , whether enabling two core and disabling the other won't cause damage to the enabled one as they will be overclocked when performing some high end task ?
I am afraid of that and not disabling the two . But I like to use if they save battery.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Setting it to 2 cores is really pointless for batery savings since it almost never goes to 3 or 4 cores unless you play graphically intense games.
Besides that, yes it is safe.
forumhookersdotcom said:
Won't they get destroyed as they are running at maximum clock ?
Do they save battery , enabling only two cores.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
No, I highly doubt it. 1.5GHz isn't the maximum this processor can physically reach anyway, it's just the cap that has been implemented. It's the Battery and CPU heat you need to be worried about, these can cause real problems. Fortunately, disabling 2 of the cores also reduces the Battery temperature quite drastically. I've not done much testing with CPU temperature though, but it certainly doesn't seem to increase it.
As for battery life, I've not noticed a huge increase in battery life but it does seem to be a little better. This could just be a placebo effect though
Meltus said:
No, I highly doubt it. 1.5GHz isn't the maximum this processor can physically reach anyway, it's just the cap that has been implemented. It's the Battery and CPU heat you need to be worried about, these can cause real problems. Fortunately, disabling 2 of the cores also reduces the Battery temperature quite drastically. I've not done much testing with CPU temperature though, but it certainly doesn't seem to increase it.
As for battery life, I've not noticed a huge increase in battery life but it does seem to be a little better. This could just be a placebo effect though
Click to expand...
Click to collapse
I'll add to meltus post.
CPU will only hit 1.5 on 1 core, 1.4 on 2 cores and 1.2 on 4 cores.
CPU is good upto 90c so CPU temp isn't a worry but HTC seem to think that 48c is over heating for the battery where it is ok up to 60c.
Sent from my HTC One X using xda premium
Is there any other app to turn on 4 core when games ?
Sent from my HTC One X using Tapatalk 2
forumhookersdotcom said:
Is there any other app to turn on 4 core when games ?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
This goes along with a thread I was in earlier. You could use tasker to create a profile to enable 4 cores (and in the case of our other thread, the interactive governor) when playing a game, then disable 2 when exiting the game. You can set up Tasker to do all kinds of cool things for battery management and all automated too.
I have the exynos 990 version of the S20 FE and as we all know, the 990 is a little bit of a hot mess. However it has quite a lot to give if limited correctly.I'm running One UI 3.1 on android 11. I rooted my FE with magisk and installed Franco kernel manager. The steps below will give you good battery life and performance.
Step 1: Straight up disable the M5 mongoose cores. They are Samsung's biggest undoing.
Step2 : Limit all clock speed to 2Ghz. Trust me, the IPC on the 990 is really damn good and you don't need to worry about performance loss. Forget the benchmarks, everything just works. Getting the last 2.7ghz or 2.5ghz usually requires a significant voltage bump and you mostly wont need the speed.
Step3 : The GPU is actually just fine as is. Try to set the max clock to 370mhz, which sounds ridiculously low, but the 990's GPU was made for 1440p screens, so the UI still remains smooth even at 120Hz. I played Riptide Renegade with this setting and it was very smooth as well. You can play with this number according to how much you game, I, for the most part, don't.
My hypothesis, based on my usage of about 2 months (yeah, i rooted this bad boi about a week from purchase, screw warranty, i'm gonna be alone for life :-( ) is given below >>>>>>
Thermal throttling seems to be due to the M5 cores clocking up like crazy while doing basically nothing. This is probably mostly because Samsung uses their own "energy_step" CPU governor which still needs some work. You can try changing this to schedutil ( which is basically EAS ) and see how it fares. The GPU also ends up underclocking because the GPU has a " joint " governor ( basically ramps up and down with CPU speed to some extent, not entirely sure about this, i may be completely wrong).
I have also have put a battery charge limiter in place at 90% but that doesn't really make a difference. I use my phone quite heavily and at 120Hz but still get about 18 - 20 hours of usage (not 20h screen on time!)if on FULL CHARGE
In fact if you even disable the "BIG" i.g A77 cores, and use only the four A55 "little" ones, it's still good for daily usage. Processing time on the camera takes a bit of a hit, but you can always create a custom profile for that to enable all cores for the camera app. I have my phone skinned with the AOSP-R day/night hex installer theme.
Also huge reasons for rooting :
Tasker > for some insane automation profiles i made
Naptime, Servicely > Free extra battery life
The battery charge limiter to preserve my long term battery life.
Also a GCAM update, the scan3d APKs of BSG are getting rather good. We need to get together an tune the hell out of this sensor to get it to par with the stock camera tho, especially during night. Also no telephoto support, AFAIK. One S20FE confing shall be in the works.
Unrelated shameless self plug : https://www.youtube.com/c/siddharthlh please visit my youtube channel. It does contain some interesting tutorials for tech heads
I'm going to share this thread over on reddit with the army of disgruntled Exytoast users. if this works they will love you as a living god
3mel said:
I'm going to share this thread over on reddit with the army of disgruntled Exytoast users. if this works they will love you as a living god
Click to expand...
Click to collapse
Maybe tag me in the post or something I'm siddharth_lh on reddit. I can help out there itself
done...
https://www.reddit.com/r/GalaxyS20FE/comments/ndnp0s
By "M5 mongoose cores" you mean the ones labeled as "Prime cores"? Just rooted and tried this. Will report back with results.
hectorviov said:
By "M5 mongoose cores" you mean the ones labeled as "Prime cores"? Just rooted and tried this. Will report back with results.
Click to expand...
Click to collapse
Yep
bipolar unbound said:
Yep
Click to expand...
Click to collapse
Did you apply these settings?
How's performance and results been?
bipolar unbound said:
Step 1: Straight up disable the M5 mongoose cores. They are Samsung's biggest undoing.
Click to expand...
Click to collapse
What does this do?
Also I dont wanna set the clock speed any lower is that fine?
Cheetah1020 said:
What does this do?
Also I dont wanna set the clock speed any lower is that fine?
Click to expand...
Click to collapse
if you're changing the max frequency via a kernel tweaking app you can simply change it back if you don't like it.
hectorviov said:
By "M5 mongoose cores" you mean the ones labeled as "Prime cores"? Just rooted and tried this. Will report back with results.
Click to expand...
Click to collapse
How did it go?
Cheetah1020 said:
How did it go?
Click to expand...
Click to collapse
It's been about a week and just 2 days ago I started seeing better battery life. The first 4-5 days were the same as before. I straight up disabled the 2 "prime" cores and the performance is basically the same. Never noticed a hiccup or a slow down. Before I rooted and tried this I was getting about 2.5 hrs SOT before I had to charge and now I'm getting about 3-3.5 hours, just a little more. Seems like less overheating (haven't check temps, just the feeling of it). What I haven't figured out is how to make the change on the GPU frequencies stay, if I set a max, it doesn't cares about it and it still goes above the limit. I'm always using 120 hz on this changes, so I'd say it's worth it.
hectorviov said:
It's been about a week and just 2 days ago I started seeing better battery life. The first 4-5 days were the same as before. I straight up disabled the 2 "prime" cores and the performance is basically the same. Never noticed a hiccup or a slow down. Before I rooted and tried this I was getting about 2.5 hrs SOT before I had to charge and now I'm getting about 3-3.5 hours, just a little more. Seems like less overheating (haven't check temps, just the feeling of it). What I haven't figured out is how to make the change on the GPU frequencies stay, if I set a max, it doesn't cares about it and it still goes above the limit. I'm always using 120 hz on this changes, so I'd say it's worth it.
Click to expand...
Click to collapse
I think should wait for Android 12 to see if it gets better if not then I will do this process
Me too. Great tips!
Go to settings and search for "Limit CPU speed to 70%" and turn it on. Normally gives better battery life. Haven't seen any major bottleneck in performance.
adhikraman said:
Go to settings and search for "Limit CPU speed to 70%" and turn it on. Normally gives better battery life. Haven't seen any major bottleneck in performance.
Click to expand...
Click to collapse
Doesnt it affect performance in games and stuff?
Cheetah1020 said:
Doesnt it affect performance in games and stuff?
Click to expand...
Click to collapse
Haven't experienced any major performance hit in regular usage. Not a heavy gamer so your mileage might vary.
Guys...the last update for Exynos really worked? I've heard about changes in CPU governor that worked!
hectorviov said:
It's been about a week and just 2 days ago I started seeing better battery life. The first 4-5 days were the same as before. I straight up disabled the 2 "prime" cores and the performance is basically the same. Never noticed a hiccup or a slow down. Before I rooted and tried this I was getting about 2.5 hrs SOT before I had to charge and now I'm getting about 3-3.5 hours, just a little more. Seems like less overheating (haven't check temps, just the feeling of it). What I haven't figured out is how to make the change on the GPU frequencies stay, if I set a max, it doesn't cares about it and it still goes above the limit. I'm always using 120 hz on this changes, so I'd say it's worth it.
Click to expand...
Click to collapse
Still that§s a really poor battery performance, and now without warranty... I will take my s20fe to samsung and if they wont repair or change it, I will be also forced to root my phone.
My experience rooting S20+ Exynos 990 following this thread:
TL;DR: Added 6-8 hours of standby battery life just from turning off prime and big cores, haven't checked on screen battery life since I don't use my phone much at work, but I wanted standby time improved.
Before turning off the prime and big cores, I got 11 hours tops on battery life. Seemingly out of nowhere the phone was always warm, despite just sitting at my desk with a very strong signal. I knew that at 12 pm, with 50% brightness, 120hz, and AOD I would expect at least 50% just gone even though I barely even used the damn thing. The straw that broke me, is that even though I was connected to wifi, I could only expect maybe at most, 3-4 hours of screen on time, which finally drove me insane. I checked out the thread sometime ago but was skeptical if it really was worth the trouble since it seemed a lengthy process. Take it from someone who hasn't rooted in a long time, just follow the guides and it all is pretty simple.
After turning off the prime and big cores, immediately thermals were so much better, after 3-5 minutes the phone was much cooler, about 5-8 degrees cooler on the chip area. Since the phone was reset, I couldn't really tell if battery was better. After the using my phone for a week rooted I can tell you, the battery difference is abysmal.
Before, I was struggling to end my day on 30-20%, now I can confidently end my day on 60-50%, depending on how much I used my phone. When idle the phone, barely sips battery, my estimate is that it went from 8-10% just idling, to 3-4% (need to check since I haven't turned on the prime cores ever since rooting). I wasn't willing to sacrifice 120hz so I always kept it on and battery life was good, however I will test with Max Hz on 96 hz, which should extend battery life.
Performance on the little cores is virtually the same, I haven't noticed any hiccups, lag or anything by that matter. I was concerned that on this thread it was mentioned that the camera took a hit, but on the S20+ nothing has changed, maybe the shutter is 0.3 seconds slower but I honestly don't notice or it doesn't bother me at all. Recording high resolution videos is no problem, and nothing really changed for me. Thermals are massively improved, if you're doing a heavy task, like recording, downloading or uploading, or something that you know requires heavy lifting, of course the phone will get warm, but not even close to how hot it would get just idling or doing the same tasks with the big or prime cores.
Since I don't play games I can't really say whether gaming has taking a hit or not, I would say that it depends on the game you're playing. You can always create a profile that enables the prime and big cores on FKM.
Overall I can say this, if you have an exynos 990 phone and getting real sucky battery life, rooting is the way to go. This phone just feels so much better with this extended battery life, and now rooting allows me to mod it as I want it or turn off things that weren't useful. Just be warned you will lose Google Pay and some apps from Samsung that use Knox, but for me what you get in return is so much valuable.
Please let me know if you have other questions from rooting the chip.