Develop Bugs

[Q] What is your average battery draw and CPU usage

Ok EVO nation!
Here's my scenario. I'm running a fresh flash of MikFroyo 4.5 and Netarchy's 4.2.2. cfs nohavs. With almost nothing else running on the phone.
So far I've seen a the stand-by battery drain hover around 100-180mA, with an occasional dip into the 50's. The CPU usage is always just below 10%.
I've seen references all over the forums about users claiming low 40's and idle CPU usage around 3% and I'm wondering WHY I'm not able to achieve the same thing.
Now I've done all of the standard battery tweaks, tried various kernels, and can remember a time last fall when one kernel I flashed seemed to give me incredible battery life.
So...Let's hear what your average stand-by battery drain and CPU usage is.
(And any thoughts you might have about my battery situation)

Get 4.3.2 with more havs. It'll drop the voltages nice and low. When I had mikfroyo with netarchy 4.3.2 with setcpu screen off at 128mhz I had about 30-40 idle drain.
Sent from my (insert daily ROM name here) Evo 4g

I wouldn't worry too much about your idle current draw unless you're having a battery drain problem. The issue with the current draw methodology is it's taking the current consumption that instant in time. Unfortunately, you can't monitor instantaneous current draw without affecting the reading itself.
If you idle for an hour or two (or 5), and your battery only goes down 0-1%, i'd say you're in good shape. Also, it helps if you specify what software you're using to monitor these values with? Mine is based on Battery Monitor Widget (bmw).
Edit: There's more to cpu tweaks than just kernels. Along with kernels, there are governors, and then there are governor parameters. Each will directly affect your battery consumption and cpu load.

I'm definitely having a battery drain problem. At idle, it's falling 3-4% per hour, according to the Battery Monitor Widget.
I've got SetCPU set to 128min/998 max with Conservative scaling, and I've one profile enabled for Screen off settings of 128min/128max.
I did notice that when I try to set the min cpu to 128, the clock speeds jump all over the place. But if I set the min cpu to 245 it quiets right down.
Perhaps I a have CPU that's become finicky?

fsmith3x said:
I'm definitely having a battery drain problem. At idle, it's falling 3-4% per hour, according to the Battery Monitor Widget.
I've got SetCPU set to 128min/998 max with Conservative scaling, and I've one profile enabled for Screen off settings of 128min/128max.
I did notice that when I try to set the min cpu to 128, the clock speeds jump all over the place. But if I set the min cpu to 245 it quiets right down.
Perhaps I a have CPU that's become finicky?
Click to expand...
Click to collapse
I had an issue similar to this where my battery would drain quicker than usual when the CPU min was set at 128 and having a screen off profile of 128/128. I think the problem stems from just setting the CPU way too low and having it use more power to bring the phone 'up to speed'. From my personal experience, I think you'll still be just as good setting your mins to 245, but by all means you're more than welcome to continue experimenting with 128

First off, you need to determine if you have a wake lock issue. Use "spare parts" to see. Look in the battery history, partial wake lock section. It will show you what programs are causing wake lock, and what amount of time they are in a state of wake lock.
Example, my phone was last off the charger 42 hours ago (awake time 7h36m), battery still at 32%, and should last the remainder of the day so long as I don't do too much data. My two biggest wake lock listings are Android system at 1h26m, and my email at 20m.
All it takes is 1 misbehaved program, or even a particular setting within a program to cause wake lock. If that is the cause, then regardless of what your sleep settings are, the phone will still draw the battery down quickly.
You can also look in "/sys/devices/system/cpu/cpu0/cpufreq/stats" at the time_in_state file using a text viewer/editor. It will show how much each cpu frequency is being utilized. I don't recall what unit it's in. But the point here is that if your 128/245 Mhz values are lower than your upper mhz values, something is not right.
The governor parameters will control how much cpu swing is occurring under various load. That is, if you're reading an email, there's little reason for the cpu to be pegged at 998mhz. These parameters control the thresholds (contingent upon which governor is used) at which the cpu scales up or down.
Edit: Each value in time_in_state represent 10ms, or .01seconds. So multiple each value below by .01 to get actual time in seconds. If you notice, the total time in us equal to my awake time of 7h36m, not total uptime.
Mine looks like this
Code:
Mhz cycles seconds
128000 1264017 12640
245000 201083 2011
384000 72728 727
422400 4 0
460800 133450 1335
499200 0 0
537600 72174 722
576000 53479 535
614400 78771 788
652800 38230 382
691200 0 0
729600 87258 873
768000 29579 296
806400 98273 983
844800 18476 185
883200 0 0
921600 599503 5995
960000 0 0
998400 2821 28
Total 2,749,846 27,498
27498seconds = 458min = 7.63h or 7h37m.

gpz1100 said:
Example, my phone was last off the charger 42 hours ago (awake time 7h36m), battery still at 32%, and should last the remainder of the day so long as I don't do too much data. My two biggest wake lock listings are Android system at 1h26m, and my email at 20m.
Click to expand...
Click to collapse
gpz1100, Please describe your setup and usage. I'm curious to know how you're getting that kind of battery life.
Anyway....
Good morning gang!
I gave this a couple of days for the fresh install to settle in, and hopefully let it learn how to use the battery more efficiently. But it's still a power hungry beast.
Yesterday I calculated it's use ate 3.9% an hour, based on battery % / time unplugged.
Mind you, I made 2 short phone calls yesterday, and checked my Exchange mail a few times throughout the day. No Angry birds while I'm trying to sort out batter life.
It's still using 100-150mA in standby, and it seems like the governor (SetCPU) is working like it should.
Right now the battery is at 97% and has been off the charger for 1.5 hours. That's 2% an hour. Which isn't bad, but I doubt the average will be that low by the end of the day.
For those of you who like numbers, here's some stats for you. Do you see anything that raises any red flags?
Looking at Spare Parts, in the wake lock section, I see these values.
Android System: 9m9s
UID 10020: 54s
Facebook: 39s
Voicemail: 30s
Mail: 14s
Maps: 11s
Tasker: 9s
WidgeLocker: 6s
Other Usage...
Running: 36.1%
Screen on: 16.7%
Phone on: .9%
Wifi On: 100%
Wifi Running: 100%
The values from my 'stats' file:
128000 0
245000 84095
384000 20371
422400 9
460800 0
499200 127
537600 4743
576000 100
614400 9
652800 75
691200 4238
729600 0
768000 23
806400 1358
844800 2439
883200 0
921600 0
960000 976
998400 18361
1036800 0
1075200 0
1113600 0
1152000 0
1190400 0
1228800 0
1267200 0

fsmith3x said:
gpz1100, Please describe your setup and usage. I'm curious to know how you're getting that kind of battery life.
Click to expand...
Click to collapse
My setup is as described in the sig. The only additions would include custom conservative governor settings of 80/55/10 % on the up/down/freq steps thresholds; min/max cpu of 128/921 Mhz respectively. I don't use setcpu, tasker, or anything similar. Background updates is on, but nothing is checked (no gmail, facebook, etc.). I used to have email push enabled (using k9 mail), but decided to turn off push altogether, and just poll the server manually when I need to check email when away - little reason to getting emails as they come in if I have access to a computer at the same time.
I have found that even with wifi, the quality of your voice signal drastically affects battery life. I'd say I have average signal, (3-4 bars most of the time) for voice. However, sprint provided an airave because data speed is terrible here. A byproduct of the airave is it provides excellent voice signal. So, just with that in place, consumption while the phone is sleeping/idling is reduced by a good 10-20% over connecting to the tower directly. I'd say most of my usage is voice, some texting/emailing, and on occasion, heavy browsing. No games or videos, no facebook/twitter. It's hard to quantify use, but I think that's the bulk of it.
Yesterday I calculated it's use ate 3.9% an hour, based on battery % / time unplugged.
Mind you, I made 2 short phone calls yesterday, and checked my Exchange mail a few times throughout the day. No Angry birds while I'm trying to sort out batter life.
It's still using 100-150mA in standby, and it seems like the governor (SetCPU) is working like it should.
Right now the battery is at 97% and has been off the charger for 1.5 hours. That's 2% an hour. Which isn't bad, but I doubt the average will be that low by the end of the day.
Click to expand...
Click to collapse
What you need to keep in mind, is that unless you're using an sbc kernel, your battery may or may not stay above 90% for too long after being removed from the charger. Unfortunately, battery consumption is not constant. Demand on the battery is changing depending on what the phone is doing. Also, 1.5 hrs really isn't a large enough time period to draw an accurate average from. Based on your cpu usage below, it indicates your device was actually on for 22 min.
Your wakelock numbers don't look bad, but the data is inconclusive. The question is, when these readings were taken, what was the up time, and what would you say was the time with the screen off (rough estimate is the diff between uptime and awake time). Leaving wifi on is a good idea, as it draws much less energy than using 3g.
One number that does seem surprising (assuming total run time of 1.5h's since removed from charger) is your running % of 36.1%. If the phone was not used during this time, that seems excessive. In fact, looking at the next value, screen on - 16.7%, would suggest that 20% of the awake time was when the screen was off.
I would start by disabling or uninstalling(if you use titanium backup, the FREEZE) tasker and widgetlocker. Running % - screen on % = % of time spent not sleeping even though the screen is off - things like receiving email, performing weather updates, etc...

[Q] CPU Governor

Hi, just another cpu governor question:
Smartass VS Interactive, 122/710
Ive notice this behavior with these two via OS Monitor:
Interactive: This mod seems to adjust the cpu frequency based on current cpu usage, from 122 to 710 (and some steps between these two, again based on usage) - is my thinking correct?. Same should be for sleep, where is no cpu usage, therefore 122mhz or so.
Smartass - based on interactve, expected to be better: This one is also adjusting the cpu frequency when needed, but in ON mode its from 480 to 710 and when sleep its from 122 to 352.
When I know these two information (assuming they are correct) the interactive governor seems to be better for battery saving with same performance (idle system for few seconds - 480mhz vs 122mhz). Or is there any significant performance difference when interactive got such a huge scaling range? Did I miss something relevant when comparing these two?

Copy-Pasting a post from arco which explains Smartass:
"Smartass caps the frequency when screen on to 480 MHz to ensure responsiveness. This also helps with video playback being smooth, as it otherwise will begin to stutter when the frequency is lower than this."

The Interactive governor is designed to reach maximum speed with no lag, so there should not be any need to raise minimum speed just because the screen is on, but the smartass governor has been optimised for android so it must be a good choice.
Personally, I am testing the Conservative governor which should take about 2 seconds to get from min to max speed, and I am not seeing any difference from on-demand.
Standby battery life is improved by dropping min speed, you don`t NEED to change anything else.

I have been investigating this matter for 2 weeks now. Using SetCPU to set the governor and CPU Spy for monitoring, here's what I typically get on my Nexus S with Netarchy Kernel.
Ondemand
1000Mhz: 3%
800: 1%
400: 0%
200: 0%
100: 12%
Deep Sleep: 84%
Conservative
1000: 2%
800: 3%
400: 3%
200: 0%
100: 8%
Deep Sleep: 84%
Smartass
1000: 2%
800: 5%
600: 5%
400: 2%
200: 0%
100: 3%
Deep Sleep: 83%
Smartass looks more responsive but drains more battery. Surprisingly, ondemand should drain less battery than conservative.
What do you guys get?

Avoid the Conservative Governor - I am only using it for fun. It saves a small amount of power by picking up speed slowly, but wastes more by dropping speed even slower. I can improve that by messing with the source, but in standard form it is pretty hopeless.
SmartAss lets you drop speed in standby to ridiculously low levels without losing performance when the sceen is on. I couldn`t recommend anything else.

Ooops
There is a bug in the Conservative Governor : it is wasting power because it will not reduce CPU clock until CPU usage is below 10% (default).
Suggested fix:
--- /usr/src/ez/drivers/cpufreq/cpufreq_conservative.c 2011-04-25 01:51:20.000000000 +0100
+++ /usr/src/buzz35/drivers/cpufreq/cpufreq_conservative.c 2011-07-29 18:10:12.184895733 +0100
@@ -30,7 +30,7 @@
*/
#define DEF_FREQUENCY_UP_THRESHOLD (80)
-#define DEF_FREQUENCY_DOWN_THRESHOLD (20)
+#define DEF_FREQUENCY_DOWN_THRESHOLD (70)
/*
* The polling frequency of this governor depends on the capability of
@@ -524,9 +524,9 @@
/*
* The optimal frequency is the frequency that is the lowest that
* can support the current CPU usage without triggering the up
- * policy. To be safe, we focus 10 points under the threshold.
+ * policy. To be safe, we should focus 10 points under the threshold.
*/
- if (max_load < (dbs_tuners_ins.down_threshold - 10)) {
+ if (max_load < dbs_tuners_ins.down_threshold) {
freq_target = (dbs_tuners_ins.freq_step * policy->max) / 100;
this_dbs_info->requested_freq -= freq_target;

The conservative governor was designed to keep CPU usage between 20% and 80%, which seems fairly wasteful.
In early 2009 the code was changed to make it more like OnDemand, and the lower limit was (accidentally?) lowered to 10% (default). That "mistake" is still present in the 3.0 kernel so clearly no-one uses the conservative governor, but if they did I recommend setting the lower limit to 10% below the UPPER limit of 80% (or even 90%) to stand any chance of using less power than with on-demand.

[GUIDE] Learn to Overclock and Undervolt your phone

This is an article that I've founded on a website and I want to share with you. Everything has been already posted and there is no new info for advanced users, but I think this will be very useful to many of you. Anyways, here it is
Click to expand...
Click to collapse
Your phone was taught to underachieve
You are not getting the maximum power and battery life out of your phone. At factory settings your Motorola Defy is underclocked and overvolted, which means that it runs slower than it should and drinks too much battery juice (even so it performs well and has a good battery life compared to other Android phones). Some people believe that the Defy was deliberately crippled for commercial reasons: Motorola didn't want to jeopardise sales of more expensive models by making the Defy too attractive. Nobody knows if this rumor is true or false. Either way, there is a tradeoff between performance and battery life, and Motorola erred on the side of caution. A phone that crashes because it runs too fast at too low a voltage causes a lot of expensive work for customer service. A phone that drains the battery a bit faster while running a bit slower won't send its users back to the stores to demand a fix, as long as it performs within the advertised specifications.
And the specs are too conservative. Your phone can run longer and faster.
To understand why, let's dig into the numbers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Speed, voltage, and battery trade-offs
Motorola set the three CPU speed/voltage combinations for the Defy at:
1) 300 MHz at VSel1 = 33;
2) 600 MHz at VSel2 = 48;
3) 800 MHz at VSel3 = 58;
at a threshold of 86%.
The threshold determines when the processor steps up to a higher speed. By default, it switches to high speed if it runs at 86% capacity, and slows to a lower gear when the usage drops.
Higher speed (more MHz) requires a higher voltage, which is why the VSel (Voltage Select) goes up. VSel is related to voltage according to:
V = 0.0125*VSel + 0.6.
So at the lowest default VSel (33), your phone runs at 1.0125 V. At the highest default VSel (58) it runs at 1.325 V.
The power consumed by the processor increases in a linear fashion with the clock speed (twice the speed is twice the power), but quadratically with the voltage: twice the volts means four times more power.
The display and the radios eat up most of your battery. Turning down the brightness and switching off GPS, Wi-Fi and mobile data when not in use improves battery life more than undervolting your processor.
However, you can squeeze a few more hours out of a battery charge if you undervolt your CPU, and overclocking may make some apps run a little smoother. Just don't expect miracles, and be prepared for errors and crashes when you push the wrong buttons.
Room for improvement
The main battery saver is a low VSel1 (the lowest voltage at the lowest speed), because your phone runs at this speed most of the time. Underclocking VSel1 is not a good idea, because below the default 300 MHz it takes noticably longer before your phone responds to an incoming call in standby mode. Reducing VSel1 too much makes your phone hang or reboot when it's idle, but you can reduce VSel1 within reason to increase standby time. If you cut VSel1 from 33 to 20 the processor uses 40% less power most of the time, which can make the difference between your phone lasting a full day or blacking out before you get a chance to plug it in. (There are more ways to stretch your battery without dumbing down your smartphone.)
Lowering the intermediate voltage at medium speed (600 MHz by default) saves a bit of juice when you're playing with your phone a lot, because VSel2 is the typical setting when you're using your phone. If you use your phone as an mp3 player on a long trip you may notice the difference.
Your phone rarely runs at top speed. It spikes at VSel3 occassionally, but even with QueueTube streaming, Wi-Fi Ruler scanning, GPS Status looking for satellites, and Dolphin HD loading pages in the background my processor spent most of the time at 600 MHz instead of the default maximum (800 MHz) or my custom 1 GHz.
Overclocking may make a difference if you're playing resource-hungry games or watch badly encoded videos. Just don't overdo it, because the voltage required to run at more than 1 GHz makes your phone produce more heat, reduces battery life, and may even shorten the life of your hardware. Try to keep the maximum VSel below or at the default maximum, and don't let the temperature increase beyond 35°C for too long unless you live in a very hot place. High temperatures won't kill your phone at once, but they will kill your processor and battery slowly. Batteries may be cheap, but a dead processor will turn out very expensive. Especially when the manufacturer finds out you've messed with the settings and voids your warranty.
So what settings should you use?
Workout schedule for your phone
There is no one-size-fits-all answer. Processor performance varies, even if they're from the same batch. Your optimum settings depend on your phone, whether it runs Eclair or Froyo, how you use it, where you use it. A phone in a hot jeans pocket doesn't dissipate heat as fast as a phone in a cool handbag, and shooting video is more demanding than listening to podcasts. You'll have to find the best settings for your phone by trial and error.
Start by lowering VSel1 in small steps and check if your phone runs stable for a while under real world conditions. The stability test that's built in SetVsel is a rough indication, but also test stability by running a couple of streaming video apps over 3G together with other power-hungry apps, because seemless switching between speeds is not the same as an artificial stress test at constant voltage. If your phone starts rebooting by itself, increase the VSel by a safe margin.
There's no point trying to push the numbers to the max, because the power used by your CPU is just a small part of the big picture. Tweak the next VSel after you have the first one tuned. Don't change all at once, because then you don't know which one is wrong if your phone becomes unstable. Tweak your VSels one at a time.
Remember: undervolting won't damage your phone. Pushing the voltage too high may fry your CPU and kill your battery. I wouldn't push my Defy beyond 1000 MHz unless I can make it run at a very low voltage.
Judging from reported values at which Motorola Defy (most of them on Eclair, some on Froyo) phones ran without issues (see below for details), the safe ranges seem to be:
- 300 MHz, VSel1 24-33
(some people report stable systems as low as VSel1 14);
- 600 MHz, VSel2 31-48;
(some people report stable systems as low as VSel2 27);
- 800 MHz, VSel3 41-58.
(some people report stable systems as low as VSel3 39);
- 1000 MHz, VSel3 45-74.
(above VSel3 58 your phone may get really warm).
I started with 300/24, 600/34, 1000/52. When that ran OK for a couple of days I knocked the voltage down in bits and pieces. I now keep my phone running at 300/16, 600/28, 1000/52, with the threshold at the original 86%. My phone runs smoothly, passes the stability test (check the bottom of the SetVsel screen) with flying colors, and the battery lasts noticably longer than with the default settings.
Of course that doesn't necessarily mean these settings will work for you, because every CPU is different. The only way to find out is by trial and error. Push your VSels down in small steps, one at a time, until your phone fails the stability test or starts rebooting by itself. Then go back to the last "safe" setting and continue with the next VSel.
If you like to take risks and don't mind your phone getting hot:
- 1100 MHz, VSel3 55-66;
- 1200 MHz, VSel3 60-75.
More options
SetVsel has two options to let your phone go on a diet when your battery runs low. The first option is to limit your phone to VSel2 when the battery level drops below a set percentage (e.g.30%), the other method is setting the threshold to 99% when the battery runs low. New versions of SetVsel may come with new tricks to squeeze some extra time out of dry batteries.
SetVsel can show your processor status in the notification bar if you check the speed icon box. Don't panic if the reported speed is different from what you entered into the program. SetVsel polls the processor speed more often than the notification refreshes, so the numbers indicate average speeds.
The "apply at boot" option is best left alone. If your phone runs well you won't reboot it very often anyway, and if it crashes a lot you'll probably need to try different voltages and reduce the maximum speed.
Go get it
• SetVsel (Android Market)
• SetVsel (xda forum)
SetVsel was designed for the Motorola Defy, but it also works on the Droid X and the Milestone. It may work on other phones, but your best bet is to search the market for "overclock" or "undervolt" and pick an app tailored for your device. Read the comments in the market to check if it works on your phone model. Checking out forums like xda before you start messing with the voltage is a good idea too.
Note: all overclock/undervolt apps require that your phone is rooted.
The safe ranges were estimated by searching Google for "Motorola Defy undervolt" and taking the speed-VSel combinations reported as being stable or unstable. The full list of values used:
reported as stable:
300/15 ? ?, 300/15 500/34 600/38, 300/14 550/26 800/38, 300/16 550/27 800/39, 300/16 600/28 800/39, 300/18 600/33 800/43, 300/20 600/32 800/50, 300/26 600/32 800/44, 300/26 600/33 800/39, 300/24 600/34 900/44, 300/28 600/38 900/46, 300/28 600/38 900/48, 300/18 600/30 1000/52, 300/18 600/38 1000/52 86%, 300/20 600/28 1000/54, 300/20 600/30 1000/48, 300/20 600/30 1000/52 80%, 300/20 600/34 1000/52, 300/22 600/32 1000/52, 300/22 600/32 1000/52, 300/24 600/34 1000/52, 300/24 600/36 1000/56 80%, 300/26 600/32 1000/56, 300/26 600/34 1000/54, 300/30 600/48 1000/58, 300/30 600/48 1000/58, 300/33 600/48 1000/52 92%, 300/33 600/48 1000/58, 300/16 600/27 1100/58, 300/19 600/29 1100/54, 300/26 600/34 1100/58 60%, 300/28 600/44 1100/58, 300/28 600/44 1100/62, 300/30 600/40 1100/58, 300/30 600/44 1100/60, 300/15 600/25 1200/60, 300/20 600/32 1200/63, 300/24 600/34 1200/62 80%, 300/30 666/46 1000/58, 300/17 700/35 1100/57, 300/28 700/52 1100/62, 300/30 700/46 1100/58, 300/16 700/33 1200/60 90%, 300/16 700/34 1200/63, 300/30 700/48 1200/68 86%, 300/30 700/48 1200/68 92%, 300/28 800/46 1200/60, 300/28 800/46 1200/60 76%, 300/25 900/56 1100/66, ? 900/40 ?, ? ? 900/46, ? ? 1000/45, ? ? 1000/50, ? ? 1000/56, ? ? 1000/56, ? ? 1000/56, ? ? 1000/58, ? ? 1000/60, ? ? 1000/74, ? ? 1100/55, ? ? 1100/56, ? ? 1100/58 70%, ? ? 1100/58, ? ? 1100/59, ? ? 1100/64, ? ? 1200/64, ? ? 1200/65, ? ? 1200/66, ? ? 1200/68, 300/33 600/48 800/58 1200/68
reported as unstable:
300/13 ? ?, 300/20 ? ?, 300/20 600/30 800/40, ? ? 900/46, ? ? 1000/56, ? ? 1000/60, ? ? 1100/53, ? ? 1100/54, 300/26 600/40 1100/58, ? ? 1200/60, ? ? 1200/66, ? ? 1350/76​

Overclocked
[email protected]
[email protected]
[email protected]
[email protected]

My values are:
[email protected]
[email protected]
[email protected]
[email protected]
I Have Slim Defy wJellyBean4.3 and Works Like a Charm.

[email protected]
[email protected]
[email protected]
[email protected]
Have had these settings working nice and stable for a long time on CM7 then CM10. Now on Mokee 43.1 and seems good so far.
Also using Aero Control to overclock the GPU to 266Mhz, this has made quite a big difference. My Antutu score went from approx 4500 to 5000 and everything seems just a bit smoother. Only problem is I can't get Aero Control to retain the settings on boot.

MB526[Defy+]:
[email protected]
[email protected]
[email protected]
[email protected]

themaker69 said:
MB526[Defy+]:
[email protected]
[email protected]
[email protected]
[email protected]
Click to expand...
Click to collapse
Mine are:
[email protected]
[email protected]
[email protected]
[email protected]
everything's just fine with it.

Title is misleading
hoderer said:
Mine are:
[email protected]
[email protected]
[email protected]
[email protected]
everything's just fine with it.
Click to expand...
Click to collapse
I found this thread from a huge noob guide, it's disappointing to see it only refers to one type of phone i've never even heard of. I searched for overclocking Samsung Galaxy Mega and nobody seems to know anything yet. If anyone has tested settings for this phone, pls advise. I'm on a L600 Sprint tinkering around with a bunch of stuff, and overclocking is certainly on my to do list.

Heat

Some phones are great to take camping because if you play Asphalt 8 long enough, the back warms up to the ideal temperature that can bake bread. Rate this thread to express the extent to which the Samsung Galaxy S11 stays cool under extended heavy use. A higher rating indicates that even when playing strenuous games for long periods of time, the phone doesn't get uncomfortably warm.
Then, drop a comment if you have anything to add!

I have the exynos version of the S20 Ultra and..... I don't get how many people can get overheating with the phone. I live in a tropical country when even indoors, the air is still very hot. I haven't experienced any severe heat problems with the phone (only an occasionally rare noticable jump in temperature that time when I was watching a video with a bluetooth earphone in a direct sunlight with a high brightness).
Keep in mind that again, this is the exynos version.

---------- Post added at 01:11 PM ---------- Previous post was at 01:09 PM ----------
[/COLOR]
AlvinZahran98 said:
I have the exynos version of the S20 Ultra and..... I don't get how many people can get overheating with the phone. I live in a tropical country when even indoors, the air is still very hot. I haven't experienced any severe heat problems with the phone (only an occasionally rare noticable jump in temperature that time when I was watching a video with a bluetooth earphone in a direct sunlight with a high brightness).
Keep in mind that again, this is the exynos version.
Click to expand...
Click to collapse
Could you please install a battery temp app and share your temperature with us?
Thank you

I had the same issues till the latest ATCT update. SOT would not get pas 4 hours 40 minutes and heat was mind-blowing. Now I'm getting up to 6.5, even 7 hours with 120 Hz. And heat issue is much much better. Still heats on camera, specially on videos, but it's manageable. Still, should heat like this.

19ho3in98 said:
---------- Post added at 01:11 PM ---------- Previous post was at 01:09 PM ----------
[/COLOR]
Could you please install a battery temp app and share your temperature with us?
Thank you
Click to expand...
Click to collapse
This is my typical temp (31-35°)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

My temperature is quite high
Snapdragon

AlvinZahran98 said:
I have the exynos version of the S20 Ultra and..... I don't get how many people can get overheating with the phone. I live in a tropical country when even indoors, the air is still very hot. I haven't experienced any severe heat problems with the phone (only an occasionally rare noticable jump in temperature that time when I was watching a video with a bluetooth earphone in a direct sunlight with a high brightness).
Keep in mind that again, this is the exynos version.
Click to expand...
Click to collapse
Exynos here too. N my s20+ is like a heater. Scroll fb or anything n the temp is like 38 to 40. Play pubg, temp is waving from 42 to 46. N these days a microphone issue. I regret buying this junk lol.

Mine is an S20 Ultra Exynos 512GB.
When I leave the CPU monitor app to sit by itself, the CPU usage drops to the level as shown in my screenshot. If yours does not do this, that means there is a rogue app running in the background which you need to identify and put to deep sleep when it is not loaded up on your screen. Culprits tend to be web browsers, Youtube, Facebook. These apps chew up CPU cycles eventhough they are not doing anything in the background.
After setting all of my apps up properly so that the only ones allowed to keep running are the instant messaging apps. As a result, the longest I have been able to run at 60Hz has been 9 hours 42 minutes on a single charge, running until 1% remaining through normal use across 2 days.
Comparing the current draw between 120 and 60Hz, I found that with only Accubattery on:
120 Hz discharge current: 185 - 289 (642 mA peak when scrolling)
60 Hz discharge current: 129 - 224 (453 mA peak when scrolling)
Based on this, the power consumption difference between 120 and 60 Hz is up to a whopping 50%! Very high and disappointing as I was expecting maybe 20-30% difference.

any solution for this heat
did anyone find a solution for this heat in this device , CPU always between 45 & 48 degrees , sometimes it is higher when I am using network 4G data.

After the ATD3 temperature has been quite nice! In Celsius, minimum (idle) used to be 33. No I'm seeing 31, even 32. And went out to bright sun, with maxed brightness and it never went beyond 38 (previously it would just in a minute to 40 and even up to 42. I'm using 120 Hertz.
Happy with the upgrade!

YoSoyCarlosG said:
After the ATD3 temperature has been quite nice! In Celsius, minimum (idle) used to be 33. No I'm seeing 31, even 32. And went out to bright sun, with maxed brightness and it never went beyond 38 (previously it would just in a minute to 40 and even up to 42. I'm using 120 Hertz.
Happy with the upgrade!
Click to expand...
Click to collapse
but with using mobile data it is become too much high.

I only use 4g data every day and it stays about 32.

German Exynos Galaxy S20 Ultra 5G user here. I bought my device just recently and updated immediately to firmware ATD5.
To test thermal behaviour of my handset, I set my display resolution to WQHD+ at 60 Hz frequency, installed CPU Monitor und GFXBench 5.0.0 as well as Geekbench 5.
My ambient room temperature is about 23 °C, idle SoC temperature is 32 °C.
With GFXBench, I ran 3 benchmark passes with these tests enabled:
Aztec Ruins Vulkan (High Tier)
Car Chase (ES 3.1)
Manhattan 3.1 (ES 3.1)
Tessellation (ES 3.1)
SoC temperature immediately after the third pass was 42 °C. No throttling, all final results were identical regarding fps.
With Geekbench, I ran 4 benchmark passes.
SoC temperature immediately after the third pass was 43 °C. Maybe very slight throttling, single core performance result fell from 915 to 901.
Either I've managed to get an exceptional production sample or Samsung managed push out some serious update magic. Because these results are remarkable compared to Exynos benchmarks I've performed in the past and test results I've seen online.
EDIT:
I ran Basemark GPU 8 times in a row at 1440p medium on Vulkan, no throttling whatsoever!

Sleepycat3 said:
Mine is an S20 Ultra Exynos 512GB.
When I leave the CPU monitor app to sit by itself, the CPU usage drops to the level as shown in my screenshot. If yours does not do this, that means there is a rogue app running in the background which you need to identify and put to deep sleep when it is not loaded up on your screen. Culprits tend to be web browsers, Youtube, Facebook. These apps chew up CPU cycles eventhough they are not doing anything in the background.
After setting all of my apps up properly so that the only ones allowed to keep running are the instant messaging apps. As a result, the longest I have been able to run at 60Hz has been 9 hours 42 minutes on a single charge, running until 1% remaining through normal use across 2 days.
Comparing the current draw between 120 and 60Hz, I found that with only Accubattery on:
120 Hz discharge current: 185 - 289 (642 mA peak when scrolling)
60 Hz discharge current: 129 - 224 (453 mA peak when scrolling)
Based on this, the power consumption difference between 120 and 60 Hz is up to a whopping 50%! Very high and disappointing as I was expecting maybe 20-30% difference.
Click to expand...
Click to collapse
How's you battery life update so far, also sot between 120 and 60

xnostra said:
How's you battery life update so far, also sot between 120 and 60
Click to expand...
Click to collapse
I've been using 120Hz now, but I have not checked full battery life again as I have been just topping up to 70% battery to reduce the number of cycle wear. I'd estimate that I am getting about 6 hours SOT, but I have set apps which I don't need running in the background into the sleeping and deep sleep categories in the batter's app power management settings. Accubattery says that my screen on power consumption would give 9 hours and 42 minutes, but that is very optimistic.

S20 Ultra Exynos on ATD3. Temperature stays cool when I am not using the phone (21 °C) and goes up to 33 °C when using it.
Highest I've seen is when charging with the 45W charger. Even though it is only charging at 32W, it does hit 38 °C.

Just a minor update, I did some throttling tests with synthetic benchmarks, you find the results attached. Throttling behaviour is good, nothing to complain about!

more2come said:
Just a minor update, I did some throttling tests with synthetic benchmarks, you find the results attached. Throttling behaviour is good, nothing to complain about!
Click to expand...
Click to collapse
What app is that? I would like to test it out. Thanks.

Sleepycat3 said:
What app is that? I would like to test it out. Thanks.
Click to expand...
Click to collapse
It's called cpu throttling test! :good:

S20 Ultra Exynos here, totally useless with Samsung Dex attached to an ultrawide monitor. Even the fan included in the dock station can't cool it enough. After a few minutes I got warnings for every app that they will close within 20 secondes. Garbage. Thinking about going back to my Note10+!

Question A52s: CPU cores 1-4 always max

Hello. Is it normal that the cores 1-4 are always at maximum frequency? This is only the case, when the screen is on. The phone goes into deep sleep when it's off. Cores 5-8 are at dynamic speed as I would assume it. Could please anybody check this with CPU-Z on A52s? Betterbatterystats doesnt see the cores 5-8 (I assume), so it always shows only the frequencies "deep sleep" and 1804 to me.
Thank you !

If your screen on battery time is normal I would not worry about it.

gvamp said:
Hello. Is it normal that the cores 1-4 are always at maximum frequency? This is only the case, when the screen is on. The phone goes into deep sleep when it's off. Cores 5-8 are at dynamic speed as I would assume it. Could please anybody check this with CPU-Z on A52s? Betterbatterystats doesnt see the cores 5-8 (I assume), so it always shows only the frequencies "deep sleep" and 1804 to me.
Thank you !
Click to expand...
Click to collapse
1800 MHz is not max. Cores 1 to 4 (0 to 3) have a max of 2400 MHz so at 1800 they are only half asleep as expected so to be able to respond quickly when needed.
I have the same and have excellent battery time and screen on time.

gerhard_wa said:
1800 MHz is not max. Cores 1 to 4 have a max of 2400 MHz so at 1800 they are only half asleep as expected so to be able to respond quickly when needed.
I have the same and have excellent battery time and screen on time.
Click to expand...
Click to collapse
No, 2400 is the max. of cores 5-8 and is at dynamic speed and reaches sometimes 2400. Cores 1-4 should also be at dynamic speed with max. 1804. Could you please send a screenshot of your CPU frequencies? Do they also stuck at 1804? This really drains my battery more than normal, when the screen is on. With lower frequencies I get better SOT. BTW, the overlay app CPU Float is great for tracking the CPU frequency of all 8 cores.
Edit:
1.Screenshot: most times my freqs are at this. 2nd: with some activities these are the values. Sometimes after reboot all cores are at 691 but at some point (could be a minute or an hour) first 4 cores max out with stucking there and never returning back to 691. 3rd: difference can be easily seen in battery statistics. It's both screen on at the mentioned point, but battery gets drained. I have now reported this to Samsung.

gvamp said:
No, 2400 is the max. of cores 5-8 and is at dynamic speed and reaches sometimes 2400. Cores 1-4 should also be at dynamic speed with max. 1804. Could you please send a screenshot of your CPU frequencies? Do they also stuck at 1804? This really drains my battery more than normal, when the screen is on. With lower frequencies I get better SOT. BTW, the overlay app CPU Float is great for tracking the CPU frequency of all 8 cores.
Edit:
1.Screenshot: most times my freqs are at this. 2nd: with some activities these are the values. Sometimes after reboot all cores are at 691 but at some point (could be a minute or an hour) first 4 cores max out with stucking there and never returning back to 691. 3rd: difference can be easily seen in battery statistics. It's both screen on at the mentioned point, but battery gets drained. I have now reported this to Samsung.
Click to expand...
Click to collapse
If CPU-Z is running my four first cores are at 1804. I am happy with this, and I have as I said no problem with this. If you want the save battery you should consider using a power saving setting.
I have very good battery time and plenty of SOT!