Develop Bugs

Setcpu Screen off 128mhz or 284mhz

I've heard that having your screen off setting to 128mhz that it drains more battery than 284mhz and does not let the evo perform correctly. Is this true?

I have mine to 128mhz atm and dont seem to notice qany diffrence in battery loss to when it was at 284. I have only had it this way about 24 hours but so far not a big diffrence one way or the other

Haven't noticed any extra power drawn, only thing I noticed and hate is that when you wake up it can lag bad, until the profile changes to a higher clock
Sent from my PC36100 using XDA App

Im interested in this also. I saw some people say 128 drains more battery but nothing to actually show it. I am running some tests of my own currently. Im sure it will be hard to see a difference unless there is something crazy going on.

It must have been me who posted about the 128Mhz bug first.
I'm running latest ota stock rooted, latest ota radio/wimax with Netarchy's 3.0 or 3.7.3c kernel.
I noticed that when I had 128-998 set on boot, the phone wouldn't sleep properly, and the battery drain in standby mode was ~3x what it normally was.
The normal battery drain for my configuration is about 1% an hour in standby.
If you are running a different rom/kernel, I suppose, it's entirely possible not to see this problem. Test it yourself and find out.

I have had my Evo clocked at 128 for Min and Max for about a day. I initially thought the reports of uneven performance were wrong, but a few runs of Pandora during "Screen Off" did cause some long pauses and some FCs on a couple of occasions. I suspect this is why many recommend increasing the clock to 245, especially when you have process heavy apps running.
I personally don't think the difference in such low clocks will have a significant impact on battery life, but for those of you who get the warm and fuzzies from the absolute lowest setting, I have been playing with my Min @ 128 and Max increased to 245 for a couple of hours. It's jumping out of the low clock much smoother (I can immediately drag the lock bar down) and I haven't gotten any FCs while using Pandora with the screen off. I have ran Pandora with the Screen Off and the "adb shell powertop -d" from my terminal. It is reporting that my Evo is staying in the 128 clock, but, like I said, it's transitioning to higher clocks without a hitch when I turn it on.
Hope that helps.

I've also found that 128 is just too low for things to work properly. It stutters a lot when the screen comes on and things like music also stutter.

Having tested this for a little over 24 hours in response to the increased battery drain, I could not tell any additional battery drain still after 24 hours. On the flip side i could not tell of any additional battery saving either. At the end of the day i was in my normal range.
I do not use the Stock rom but do use Netarchy's latest kernel. So ti may just be a stock rom thing. I will agree that the screen comes on sluggishly and music will skip if you have it playing with the screen off. Since i was unable to tell any significant benefit from lowering it i will be stick to 284.

I prefer screen off profile to scale down to 285mhz as opposed to 128mhz. I know the clock differences are minute, but the phone feels more responsive and ready for action when woken up at 285mhz. You can feel the 128mhz drag.

Due to some of the instability I've gotten, I've decided to bump up the Min to 245. It runs much smoother and I cannot see a difference in battery life. I think the occasional lag and FCs that 128 might cause will hurt your battery life before the increase in clock will. I'm now with the "128 is not an option" camp.

scriptx said:
I prefer screen off profile to scale down to 285mhz as opposed to 128mhz. I know the clock differences are minute, but the phone feels more responsive and ready for action when woken up at 285mhz. You can feel the 128mhz drag.
Click to expand...
Click to collapse
What is your screen off profile, min/max? Obviously 285 is min, but what is your max? What about when the screen is on?

I have my screen off setting for 245 min & max. I get no stuttering pandora and it doesn't **** itself when I turn the screen on. The transition to normal is smooth.

I am getting over 40 hours on battery....
with the set-up in my signature below.......
I have Set CPU set to 245/128 with screen off. I get almost no drain with phone resting. Went to be last night and when I picked up my phone this AM, it was still on the same %. This has been consistent for the last 3 nights.
If you go to the baked snack rom thread, towards the last two pages as of today....I discuss my set up. Others are experiencing the same kind of battery results.
I get no hiccups from resting to on. Pandora plays fine. If it needs the 245 for Pandora or such, it's there. If not, it goes down to 125 and uses almost no battery over an extended period of time.

I just tried setting 128 as min and 245 as max for screen off and my phone got stuck in a boot loop. After sitting idle for a few minutes it started rebooting on its own.
I had to remove the battery and was then able to get into the OS. I have since set my phone back to 245 . I will update if I find out this was happening for another reason or if I try 120 again.

[Q] Paradox with underclock & battery savings, does it actually hurt? SetCPU, etc.

[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?

[Q] setvsel cpu damage

hey guys, just wondering will using a lower vsel damage my cpu and/or battery?
i have previously beein using milestone overclock on 1ghz and 60 vsel and am adding setvsel into the mix, also any ideas on starter settings? thanks
also could someone just give me a heads up on what vsel actually IS

I don't believe there are any studies that show effects of long term use of lowering the voltage, which is what you are doing with vsel in order to save battery juice...or you could increase the voltage but that defeats the purpose and also heats up the battery which leads to shorter life span. Many use it without reporting any damage to battery or cpu, I believe it's safe (however, if you are overheating you might fry the battery or cpu, so you'll need to moniter and play with settings to get the desired effect without any overheating issues).
With regards to setvsel, there are reported issues from users with different roms...from what I've read (and you can do your own research to see if this is what you are seeing...this is the conclusion that I've come to by reading a lot of threads), it is better to use milestone to overclock and setcpu to lower the vsel.
With that being said, I've used them all and like setvsel so keep going back to it...but I've been having some issues lately so I've removed setvsel to see if that is what is causing some problems (too early to tell).
Oh, and as for settings...pop on the overclocking/undervolting thread in the development section to see a lot of different settings and remember that what works for one user might not work for you...you'll have to experiment a bit to find your ideal setting.

oh okay i think i might go back to my old settings with milestone overclock and setcpu and just lower the vsel! i was under the impression for some reason that lowering the vsel would heat the battery. Thanks!

I'm no expert to be honest, I'm more of a research kinda person. From what I've researched, undervolting can help keep temps down, and may particularly help when you overclock (as overclocking is stressing the cpu to go beyond it's normal operating design hence it may heat up...supplying it with less power, or voltage, is what helps keep the temps down.
Of course, this is given you find the optimal setting for your phone, and as it seems from reading through these forums, many users have experienced completely different results using the same settings (i.e., one user will have a stable setting without any problems while another user on the same rom using the same settings will have crashes and/or issues like overheating). Doesn't seem right, but it is what it is

yeah ive read through most of that stuff too, i went down to 1ghz at 51 vsel, seeming stable, but i decided to go with 54 anyway

1.1 GHz @ Stock vsel for over a month without any issues...I hope it lasts.
Sent from my MB525 using XDA App

Hi,
I've also read a lot regarding the underclocking 'dangers' but couldn't find anything to prove that there is such an issue. I think that it is an urban myth spread everywhere by people asking if there is a danger with low vsel [but that are never getting a positive answer on it].
The only thing I found using setvSel is that I had to first install Milestone Overclock and load its module prior to start setvsel. There is a way around it, but requires you to copy files in the system folders and change their permissions. I find that my way is much easier.
As far as over-heating goes, it's an overclocking thing; not underclocking.
My Defy is set at 900Mhz and really, I don't see the point of going much higher: everything runs smooth and lag free already.
vsel: 21/300; 32/600; 43/900 - 90% up_threshold
Been like that for about a month now and never experienced any problem at all.
The underclocking is great for saving battery; no exact numbers to give here but it feels like my battery now last 2 times longer. I can easily get 4 days between charges with low/moderate usage and would get to 6+ days "IF" I could stay away from games and having the screen ON for long sessions of browsing/video watching.
I tried SetCpu before but I didn't like the interface; the simplicity of SetvSel is really nice.

i use setcpu for scaling and profiles, and run 18/300, 36/600, 50/1000 stable and smooth as

Undervolting is not a bad thing at all. It means less Watts consumed for running (Watts = Voltage x Amperage), less of your battery consumed.
Ussually companies test a large batch of components and how they react on different voltages and freqvencies, and then they decide for a voltage that works with all components and that is safe for all cases. Eg. when they have different CPU speeds and thus different options for CPU's this is one way to decide which one work at 3GHz and which one at 2.7 GHz (the other one is demand for components).
Phisically you will not have any problems and you can't damage your phone by undervolting, so no problem here, only possible software problems if you go too low.
Advantages :
+ Lower processor temperature
+ Lower phone temperature
+ Longer battery time
+ Longer components life
Disadvantages
- Stability issues (freeze, artefacts, slowness)

maxi2mc said:
Disadvantages
- Stability issues (freeze, artefacts, slowness)
Click to expand...
Click to collapse
You know, I was recording a video and when playing back noticed that there were squiggly lines that went through the video a couple of times (in a two minute clip). This was the first time I saw this...and have recently lowered vsel by 2 on vsel3...could that be the artifacts that you are mentioning?
I just figured it perhaps I was too bouncy with the phone while recording making it glitch...but now that I see this post I'm thinking maybe I undervolted too much...what do you think?
My settings: 54/1000 44/700 28/300

I know what people mean by same settings don't work for every phone even if it's the exact same model. My Defy won't underclock as much as others. I'm using SetVesel, and I've been able to drop 5 points from each, and that's about it before it reboots itself. I only tested undervolting, but I mainly overclock to get as much speed as I can, and give it enough juice to run super fast. I'm current running [email protected], [email protected], [email protected] Threshold at 75%. The highest the temp ever got was 112F, and that was after playing a game for about an hour. Usually it stays below 90F for normal use. I get around 17-20 hours out of it with screen on time at about 3 hours @ 50% brightness. I've been running these settings about a month, and have not had any issues.

If you put something like 100vsel will the phone accept and then burn? Is there any protection? Does anyone know what's the highest acceptable vsel?
Just for curiosity...

im pretty sure 80 is the highest you should EVER use and that'll significantly increase the chances of your phone burning out. @bobbyphoenix you should be able to lower your vsels a fair bit or your really unlucky! i run a lower vsel for 1ghz than u do for 700mhz smooth and stable

stewi21 said:
im pretty sure 80 is the highest you should EVER use and that'll significantly increase the chances of your phone burning out. @bobbyphoenix you should be able to lower your vsels a fair bit or your really unlucky! i run a lower vsel for 1ghz than u do for 700mhz smooth and stable
Click to expand...
Click to collapse
CM7, rather non-technical person here. I seem to have a very happy phone at setvsel settings of [email protected], [email protected], [email protected], 86%. Been running this for the month or so since I rooted and the phone feels like it was made for this config. I've never seen the temp above ~32c. My 2¢.

Screen brightness and battery life.

I have been searching for 20 mins and can't find an answer (first time using the app so may have missed something).
I was wondering if anyone had any data on brightness % and power usage. People seem to go to great lenghts to change the brightness levels but I remember something on last years Google dev. con. videos on YouTube that said it didn't make as much difference as originally thought. (i can't find the video either lol. Bad search day here).
Sent from my HTC Desire using XDA App

The biggest improvement in battery life (IMO) comes from setcpu. I also keep my screen at 40% which I suppose helps some. I've got a Mugen extended life battery and setcpu set at around 537 max (on demand) with the screen off. I get 2 days out of my battery... And I use my phone a lot.

k3an said:
The biggest improvement in battery life (IMO) comes from setcpu.
Click to expand...
Click to collapse
Lol, now uninstall it, set smartass governor and see how meaningless that app really is.
madmaveric said:
I was wondering if anyone had any data on brightness % and power usage.
Click to expand...
Click to collapse
The bad thing is that on Sense roms, I have yet to see brightness going lower than 30%, even in pitch dark. Aosp does far better job as long as brightness is concerned. Setting it at low value is not an option for me either as it renders your phone unusable in direct sunlight.

/accidental double post

erklat said:
Lol, now uninstall it, set smartass governor and see how meaningless that app really is.
Click to expand...
Click to collapse
How to set governor when i don't have an app which can do this any more?
Swyped from my HTC Desire using XDA App

MatDrOiD said:
How to set governor when i don't have an app which can do this any more?
Swyped from my HTC Desire using XDA App
Click to expand...
Click to collapse
Every rom has it listed under its changelog, usually it is smartass for sense roms. It isn't by accident either, some have reported lag waking the phone up. I haven't across almost all roms available, and even if I did I'd still prefer 20% less performance over 20% less battery life.

madmaveric said:
I have been searching for 20 mins and can't find an answer (first time using the app so may have missed something).
I was wondering if anyone had any data on brightness % and power usage. People seem to go to great lenghts to change the brightness levels but I remember something on last years Google dev. con. videos on YouTube that said it didn't make as much difference as originally thought. (i can't find the video either lol. Bad search day here).
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Why dont u test it wiht currentWidget or so? Okay, i did it:
0% -> 125mA
25% -> 150mA
100%-> 280mA
So what do we learn? Brightness and/or Screen has a big impact and probalby most people here trying kernel tweaks and whatever to improve the battery dont understand math.
MatDrOiD said:
How to set governor when i don't have an app which can do this any more?
Click to expand...
Click to collapse
You can just use the Terminal... its linux after all.

x潮騒x said:
Why dont u test it wiht currentWidget or so? Okay, i did it:
0% -> 125mA
25% -> 150mA
100%-> 280mA
So what do we learn? Brightness and/or Screen has a big impact and probalby most people here trying kernel tweaks and whatever to improve the battery dont understand math.
You can just use the Terminal... its linux after all.
Click to expand...
Click to collapse
Agree. Just check the battery usage, you will get the idea.
On mine, display usually uses 40% - 60%, with data always on.

Apologies for the late reply. lost internet connection for a week then forgot I posted it
Thanks for the replies guys. I eventually found the video, took ages lol
(youtube.com/watch?v=OUemfrKe65c).
According to what they say in this the screen actually doesn't account for that much of the total battery usage (mainly due to the screen being off most of the day) overall given everything else using battery.
i.e. coming up with a way to keep the device asleep for longer when turned off would completely out strip any adjustment to the screen brightness in terms of battery life.
So things like lower cpu when in standby can be really good but only when not getting data transfer (as this needs to be done very quickly as its expensive).
As adjusting screen brightness is easy to do I think that is why so much time is spent on this. In reality though it seems like it is only going to give a limited battery life increase.

But if you put low cpu, the cpu needs more time at low to do the same that a fast cpu, thats why the setcpu apps its a bit crap. I think that set low the brightness of the screen save more battery than putting the set cpu really low... (just my two cents)

I leave the brightness on my phone to around 30% for better battery, and i can see it ok in the daytime. I have recently had it up at 100% and noticed how quick my battery goes dead.

Gsanez said:
But if you put low cpu, the cpu needs more time at low to do the same that a fast cpu, thats why the setcpu apps its a bit crap. I think that set low the brightness of the screen save more battery than putting the set cpu really low... (just my two cents)
Click to expand...
Click to collapse
Very true.
I guess ideally you want the CPU low when its not doing anything and high when doing data transfers etc (to speed up the high current draw activities).
I guess a good app would be one that puts the phone in airplane mode for 90% of the time when inactive. Only coming out once every so often to check for text/data etc. I can see that giving better returns than anything else. from what was said in the video a phone in standby doing nothing would apparently last nine days (as apposed to one normally). Given this data I guess its possible to double the battery life with this kind of app.
I may have to have a go at writing one

SMF_12 said:
I leave the brightness on my phone to around 30% for better battery, and i can see it ok in the daytime. I have recently had it up at 100% and noticed how quick my battery goes dead.
Click to expand...
Click to collapse
I agree that turning the brightness down makes sense and saves battery. It just seems a disproportionate amount of time people spend over brightness vs better ways of extending battery life.
I guess the rewards also depend on the amount of time you use the phone as the more you use it, the better reward from the screen and the less from the standby solutions

Fix Exynos 990 battery drain and Overheating Issues -[ It works ]

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.