Related
In the last week or so I have picked up my phone three times and it has been dead.
The power button doesn't turn it on again.
I have to take the battery out and then restart it.
I'm running a rooted 2.35 JVT.
I have nothing untoward running ...
Settings
Sense analogue clock
DRM content
Software update
SnsService
Google Play Store
Samsung keypad
Apart from Angry Birds, there's almost nothing else, and nothing new for months except Bad Piggies.
deanbilly said:
In the last week or so I have picked up my phone three times and it has been dead.
The power button doesn't turn it on again.
I have to take the battery out and then restart it.
I'm running a rooted 2.35 JVT.
I have nothing untoward running ...
Settings
Sense analogue clock
DRM content
Software update
SnsService
Google Play Store
Samsung keypad
Apart from Angry Birds, there's almost nothing else, and nothing new for months except Bad Piggies.
Click to expand...
Click to collapse
Could it be a dead battery?
otherwise, tried to wipe and (re)flash a rom?
The battery is fine, and the ROM has been there for well over a year with no problems.
Finding the root cause of battery drain...
deanbilly said:
In the last week or so I have picked up my phone three times and it has been dead.
Click to expand...
Click to collapse
There are a number of standard steps to run through to find the root cause of battery problems, assuming the drain is caused by the OS or apps and not actually due to a physically failing battery.
I have been tracking a few battery issues myself recently and this is what I have learned from doing some reading on XDA:
There are two free apps on the app market that are typically used to diagnose battery problems:
Better Battery Stats
CPU Spy
I would recommend installing both apps. The third place to look is in the battery details in the system settings...sorry I can't remember what they look like on Gingerbread because upgraded to Jelly Bean a couple months ago, though I do remember there was less information in the stock battery info on Gingerbread.
IF you are not, indeed dealing with a physically dead battery, then the root of your battery drain is most likely caused by a background process or app that is keeping the processor in a partially active state even though the screen is turned off and one would assume the phone should not be using any power.
Android OS will automatically change the running speed of the processor in the phone based on the demand of the system. If only a few background tasks are running and updating information the speed might be 200 or 400 Mhz. If the system is running full out servicing a graphic intensive game the processor will likely be running at the full 1000 MHz speed. The speed of the processor will directly effect the battery drain.
The expectation is that when we turn the display off (not power down, just put the phone to sleep) the processor should need fewer resources and slow down, tending towards a state known as "Deep Sleep". At this point the processor us using very minimal amounts of power. Any app or process that is active in the background will prevent the processor from getting to Deep Sleep. The CPU spy app will allow you to check how much time the phone runs at various speeds. Once you install it and run it, then reset the timers in the menu and turn your screen off for about 10 or 15 minutes. Then 'refresh' the timers. Normally, you should see most of the time accumulated in Deep Sleep. There are standard background tasks such as syncing with the cell tower, updating time, mail, checking alarms etc. That will engage the processor momentarily but they should be relatively short compared to the deep sleep time. In my case, an errand process was keeping my phone at 100Mhz constantly preventing deep sleep.
Once you know that something is keeping the phone awake in the background, you can use Better Battery Stats to narrow down which process or app it is the cause. This app allows you to track the individual processes that are consuming the most time and preventing 'wakelocks'. Wakelocks are essentially an app preventing the sleep state and are very well explained in this post: http://forum.xda-developers.com/showthread.php?t=1827676
The battery info in the system settings can also be used to give clues though again, I can't remember how much detail was included in Gingerbread..
If your problem only started happening recently, then it could be a new app that you installed recently, a feature or setting you changed recently or possibly a recent update to an app that was already installed. Try to think back at any recent events that could have triggered a change in the system.
Common problem apps I have read about are:
- Facebook - seems to be bad at using lots of background processor time. (Don't run this app but reading several posts shows its a processor hog)
- Google Apps that sync - Gmail, Chrome (syncs browser history, tabs etc.), Google location stats.
The wakelocks link goes into a great deal of detail and is hugely valuable in nailing your issue down.
Good Luck, let use know via a post if you find the root cause...
Sorry, maybe I wasn't clear about it being 'dead'.
The battery is 100% or thereabouts, no problems ever with the battery.
The phone looked as though it was turned off, but wouldn't turn on again with the power button.
I have to take the battery out and put it back again, then it starts on the button.
I've cleaned the contacts, and it still happened.
User error.
Sent from my GT-I9100 using xda app-developers app
To me, it sounds more like a rogue process messing up power managing or response, but it's hard to tell what it could actually be.
For instance, you might come a cross a game that leaves your phone locked in max cpu frequency, draining the battery without explanation.
If it was me, I'd re-flash the rom from Odin, perhaps with an sd card wipe too.
Sent from horseback.
Anyone using battery monitoring apps like BBS or GSam, can you share some of your stats here? I'm trying to figure out whether the seemingly massive amount of wakelocks I'm having is normal or not. The biggest problems seem to be coming from the kernel itself. BBS shows a lot of kernel wakelock time, and GSam consistently lists the kernel as the highest drain in its app sucker screen. Also, the Phone app seems to be waking the device a lot since upgrading to .5.51, which wasn't a problem on .3.374.
I've attached some screenshots that illustrate the problem. I'm already using ForceDoze and Greenify, which have been enabled via ADB, and I've restricted background activity and data for the vast majority of my apps. I'm really hoping there's something I can do about this given that it's impossible to use another kernel (LB and none available for this phone anyway). I've software repaired/clean flashed 3 times.
My battery drain is actually not bad at under 4%/hr (combined screen on/off) and about 1%/hour with the screen off overnight. Today I've logged over 4.5 hours SOT in a period of 17 hours and am sitting pretty at 36%. That's better than any phone I've ever used. But I worry that all the wakelocks are using my phone's CPU, raising its temperature, and might contribute to faster battery degradation.
Also, this is with bluetooth off and my Pebble not paired, but battery drain becomes substantially worse with that setup. My idle drain triples with my Pebble connected. I'm trying to troubleshoot one issue at a time and want to nail these wakelocks before moving onto the bluetooth issues.
If your battery stats looked like mine and especially if you figured out how to fix it, please share!
Given that Sony ended .5.51 deployment prematurely and is currently rolling out .8.49, I think you should update to .8.49 (or wait until your region gets the update if you don't have it yet) then recheck if your problem still persists.
Pouring time and resources into a version that Sony is no longer pushing isn't that great of an investment, especially since it's possible that it was fixed in .8.49.
mhaha said:
Given that Sony ended .5.51 deployment prematurely and is currently rolling out .8.49, I think you should update to .8.49 (or wait until your region gets the update if you don't have it yet) then recheck if your problem still persists.
Pouring time and resources into a version that Sony is no longer pushing isn't that great of an investment, especially since it's possible that it was fixed in .8.49.
Click to expand...
Click to collapse
Everything except the phone app using more battery was the same on .374. And I fixed that after force stopping the phone app and rebooting. I've been trying to troubleshoot this for weeks but just upgraded to .5.51 a couple of days ago. I will flash it when it comes out for Customized UK, but I don't think .5.51 is the root of the problem.
(Oh cool, Xperifirm actually shows .8.49 available for Customized UK now. Time for some flashing!)
Edit: I'm seeing the same degree of wakelocks so far on .8.49.
Update: The battery drain from "phone" is actually Android System. There's a bug in Oreo where sometimes Android System is showing as Phone/RCS in the battery stats. Doesn't explain why Android System is using so much battery though.
https://www.reddit.com/r/GooglePixel/comments/7f7jk2/pixel_2_rcs_battery_drain_is_there_any_way_to/
https://www.reddit.com/r/GooglePixel/comments/7edcav/rcsservice_draining_battery/
https://forums.oneplus.net/threads/rcs-draining-battery.657535/
https://forums.oneplus.net/threads/rcs-service.666045/
https://forums.oneplus.net/threads/found-way-to-end-rcs-sucking-battery-after-oreo.659711/
So I managed to get a lot of my battery drain figured out, but a few things are still bothering me.
1) Google Play Services and Android System and/or Phone (see my last post) are using the Significant Motion Sensor to wake my device constantly.
2) Sony's smart charger (com.sonymobile.smartcharger) is waking my device. I'm assuming this has something to do with Battery Care, which I find to be a useful feature. But why does it need to continue sending alarms to wake up our phones when not plugged in?
I've attached 2 screenshots from Better Battery Stats showing the first issue (Sensors/Play Services and Phone) and 1 showing the second (Alarms/Smart Charger). Note the "wakeup=true" and long times recorded for Significant Motion. This held true when I had my phone sitting face-down on a table for 6+ hours to do battery testing earlier.
Anyone else who uses battery monitoring apps: have you noticed any similar issues?
jrbmed08 said:
So I managed to get a lot of my battery drain figured out, but a few things are still bothering me.
1) Google Play Services and Android System and/or Phone (see my last post) are using the Significant Motion Sensor to wake my device constantly.
2) Sony's smart charger (com.sonymobile.smartcharger) is waking my device. I'm assuming this has something to do with Battery Care, which I find to be a useful feature. But why does it need to continue sending alarms to wake up our phones when not plugged in?
I've attached 2 screenshots from Better Battery Stats showing the first issue (Sensors/Play Services and Phone) and 1 showing the second (Alarms/Smart Charger). Note the "wakeup=true" and long times recorded for Significant Motion. This held true when I had my phone sitting face-down on a table for 6+ hours to do battery testing earlier.
Anyone else who uses battery monitoring apps: have you noticed any similar issues?
Click to expand...
Click to collapse
I'm with you on RCSService being main culpirt for me. No I don't think it's a bug, it actually does use lots of battery. I listen to 3+ hours of bluetooth music a day and when I saw that RCSService was using more power than my bluetooth, then I thought it was time to experiment. So I uninstalled Carrier Service and RCSService and suddenly my battery life jumped by 20%. There was something in the November update to these services that made them go nuts. Several people have noticed a jump in battery usage, but most people, myself included, thought it was down to the new firmware. Uninstalling these 'features' has made no difference to SMS for me, other than I don't get a read confirmation.
I don't know about smart charger, sorry.
Pretty sure the proximity sensor is always on and that must use some power, but I don't know what that would be called in BBS.
Didgesteve said:
I'm with you on RCSService being main culpirt for me. No I don't think it's a bug, it actually does use lots of battery. I listen to 3+ hours of bluetooth music a day and when I saw that RCSService was using more power than my bluetooth, then I thought it was time to experiment. So I uninstalled Carrier Service and RCSService and suddenly my battery life jumped by 20%. There was something in the November update to these services that made them go nuts. Several people have noticed a jump in battery usage, but most people, myself included, thought it was down to the new firmware. Uninstalling these 'features' has made no difference to SMS for me, other than I don't get a read confirmation.
I don't know about smart charger, sorry.
Pretty sure the proximity sensor is always on and that must use some power, but I don't know what that would be called in BBS.
Click to expand...
Click to collapse
Thanks! I should clarify that when I say it's a bug, I believe something is using a lot of battery, but I don't know that it's necessarily Phone/RCS, because it shows up randomly as either that or just Android System. I think it might be something within Android System but being labeled as Phone or RCS. (Edit: Or the other way around; it could be 100% RCS and sometimes shows up as Android System because the phone is part of that umbrella.) I could be wrong but based my judgment on the links I posted above.
That being said, I disabled Carrier Services on your recommendation in the other thread because my carrier doesn't support VoLTE, VoWiFi, or RCS, I've never seen a "delivered" message, and I don't even use the Google Messages app anyway (I use Texra for SMS and keep Messages disabled). So like you, I don't need these services. And I do think there's been an improvement. Might be time to go through the rest of what you recommended via ADB. The only thing that concerns me about doing that is that I'll have to factory reset if I ever switch carriers and want those services, but I guess that's a small price to pay and an unlikely scenario anyway.
The smart charger thing is just weird. It shouldn't need to constantly check whether I'm charging since it kicks in when you plug in. Yesterday I disabled battery care during the day and re-enabled it at night to charge, and I had the best battery life since I've owned the phone: 4.5 hours of SOT over 18 hours off the charger with 30% remaining. I may have to look at idle drain with battery care disabled. I like the idea of battery care, but if it's draining my battery then it just defeats the purpose.
Regarding sensors, BBS has its own category for proximity sensor; this is a separate sensor for significant motion. Somehow Google Play Services and either Phone/RCS or Android System are using that particular sensor all the time. And not just listening to it, but causing lots of wakeups and doing so while the device is sitting on a table all night. I can only deduce that it's somehow seeing motion when there isn't any.
jrbmed08 said:
Regarding sensors, BBS has its own category for proximity sensor; this is a separate sensor for significant motion. Somehow Google Play Services and either Phone/RCS or Android System are using that particular sensor all the time. And not just listening to it, but causing lots of wakeups and doing so while the device is sitting on a table all night. I can only deduce that it's somehow seeing motion when there isn't any.
Click to expand...
Click to collapse
Do you have 'On Body Detection' enabled in smart lock? That would force the phone to affirm if it's moving/stationary regularly and quite often.
Didgesteve said:
Do you have 'On Body Detection' enabled in smart lock? That would force the phone to affirm if it's moving/stationary regularly and quite often.
Click to expand...
Click to collapse
I never enabled that from the start, but just checked in case Google did something, and it's still off.
I also checked my app permissions, and the only ones with access to body sensors are Google Play Services and Tasker. None of my active Tasker profiles require the significant motion sensor. One of them does use the orientation sensor to turn the speakerphone on when it's face-up during a call, but I tried disabling that profile and the stats didn't change.
Maybe I have a messed-up accelerometer...do you know of a way to test that? (Edit: Found it in the Support app - my accelerometer, gyroscope, and proximity sensor are fine)
I think I might head to the Sony Mobile forums with the smart charger issue for that matter. It may be a bug that affects all phones with Qnovo features, or maybe they could at least give me an explanation.
jrbmed08 said:
Might be time to go through the rest of what you recommended via ADB. The only thing that concerns me about doing that is that I'll have to factory reset if I ever switch carriers and want those services, but I guess that's a small price to pay and an unlikely scenario anyway.
Click to expand...
Click to collapse
Correct me if I'm wrong, but couldn't you just "reinstall" those services via the same adb commands? Where you typed uninstall, just replace with install?
Maybe, but I don't know where I would be installing them from...? Since I don't have a backup of the package. I uninstalled a bunch of stuff via adb before and it didn't return with a dirty reflash. I had to flash userdata. So that's all I'm going by.
I'm not sure of the actual technical mechanics, but I believe uninstalling system apps doesn't actually remove the package from the system image, so you can reinstall them at any time.
I think it's like taking down a sign on a store, the actual store is still there, just all references to it are no longer there, so to the OS it's not listed - "uninstalled".
Hello - was there any solution found for this issue?
jrbmed08 said:
Anyone else who uses battery monitoring apps: have you noticed any similar issues?
Click to expand...
Click to collapse
Hi there, what was the final solution to your issue?
Dean F said:
Hi there, what was the final solution to your issue?
Click to expand...
Click to collapse
I gave up. I still have a ton of wakelocks. GSAM shows a bunch of them even when my phone is supposedly dozing. My battery life is OK, not nearly as great as I hoped I'd have with this phone, but it gets me through the day so I've just been living with it. I have noticed better battery on the latest firmware (July patch) than June. I also got rid of the RCS stuff, which helped a bit. And finally I traced a lot of my drain to an app I was using called "hide running in background notification" which the last few firmwares can do natively.
(Edit: Sorry for missing your previous post!)
Edit: I was sadly mistaken about better battery on the July patch. The battery is only better if I'm not on wifi. I posted in the wifi drain thread about it just now.
Has anyone been able to shoot video over 13 minutes with the flash on in the camera app on the S21 Ultra? When I pull for 13 minutes, the device gives an overheating warning and I cannot use the camera for 30 minutes. Is this normal do you have it?
When I check the temperatures with the CPU Monitor application, the processor is 52, the battery is 50 celcius.
Yea been the same with me, max i ever got was 16min video recording.
IDK how this is not fixed yet.
You can't use the phone like that, it will get damaged.
Overheating/excessive battery consumption is a common issue on misconfigured Samsungs.
First try clearing the system cache.
Turn off all power management. Deal with power hogs on a case by case basis.
Does it happen in safe mode?
If you did any major firmware updates it's factory reset time* otherwise find the root cause(s) and correct them or find a work around.
Try disabling Google backup Transport and Framework. Firebase too.
Still doing it?
Disable Google play Services see if this help.
*factory reset if you used SmartSwitch to move data from an old to new device. It's a known trouble maker.
blackhawk said:
You can't use the phone like that, it will get damaged.
Overheating/excessive battery consumption is a common issue on misconfigured Samsungs.
First try clearing the system cache.
Turn off all power management. Deal with power hogs on a case by case basis.
Does it happen in safe mode?
If you did any major firmware updates it's factory reset time* otherwise find the root cause(s) and correct them or find a work around.
Try disabling Google backup Transport and Framework. Firebase too.
Still doing it?
Disable Google play Services see if this help.
*factory reset if you used SmartSwitch to move data from an old to new device. It's a known trouble maker.
Click to expand...
Click to collapse
Now 60 celcius. I tried update with Odin. I tried hard reset. But the same.
dont think i have ever had a samsung phone that did not overheat.
happened quite a few times on s21u for me.
unfortunately you cant go too long filming.
mrbogusbaxter said:
dont think i have ever had a samsung phone that did not overheat.
happened quite a few times on s21u for me.
unfortunately you cant go too long filming.
Click to expand...
Click to collapse
I shoot video on iPhone XR with 4K but it is not warming and i took 1 hour nothing it is gonna happen
blackcemre said:
Now 60 celcius. I tried update with Odin. I tried hard reset. But the same.
Click to expand...
Click to collapse
140F is way too hot.
Find what apk(s) are using the power and deal with them directly.
Disable useless bloatware you don't use. Cut out Google constant background bs if you don't need it. All cloud crap, the WhatsApp, FB etc. crapware... kill it. Carrier, Google, Samsung and apk feedback, disable it.
Take out the trash for starters.
My 10+ uses 7-11%@hr SOT. It use to be a hot running, battery eating hog though.
S21U is heating up if you take videos more then 10 minutes and there is nothing we can do about it. It's in Samsung's hands. Or maybe in God's hand.. Mine is only reaching 45°C, but that is still to much.
ione2380 said:
S21U is heating up if you take videos more then 10 minutes and there is nothing we can do about it. It's in Samsung's hands. Or maybe in God's hand.. Mine is only reaching 45°C, but that is still to much.
Click to expand...
Click to collapse
Use the tools you have to examine and look for the cause(s).
Is it a memory leak?
What apks and services are running, what's their memory usage?
What new ones open up when you shoot vids?
A package disabler is a useful troubleshooting tool.
It may be scoped storage rearing its ugly head but I don't think so. Check all settings in used and associated apks/services.
Try a hard reboot.
Try clearing data in the problem apks and remember to keep dependencies in mind.
Disable all power management as it can cause erratic behaviors. Are any cloud apps running?
Look at all Gookill settings and disable Firebase if not needed. Try temporarily disabling Google play Services, see if that gets it...
Play with it and keep exploring until you find a fix or work around.
It ain't no plain Jane dumb Apple, you have many options and tools at your disposal.
Androids wuv attention... sort it out.*
* my 10+ was a hot running cpu/bandwidth hungry hog. After a -lot- of optimizing its now a fast, cool running, battery efficient, very stable platform. I don't update the OS at all. Still running Pie. Keep a fixed constant rather than constantly introducing new variables, and new issues. Fix what you got... and be happy.
Forget the constant update hyperbole... it's not needed to run Android effectively.
@blackhawk, thanks, but I'm in this game for a long time, so I think I know what I'm doing. I rooted and installed my first custom rom over twelve years go. I use to flash windows mobile 6 roms back in the day.
My phone is not running hot in general, I optimised everything I could and it's running absolutely fantastic with great battery life. The problem is just with the camera system that is very power/cpu hungry. Only Samsung can do something about it. I've seen dedicated cameras overheating and shutting down.
ione2380 said:
@blackhawk, thanks, but I'm in this game for a long time, so I think I know what I'm doing. I rooted and installed my first custom rom over twelve years go. I use to flash windows mobile 6 roms back in the day.
My phone is not running hot in general, I optimised everything I could and it's running absolutely fantastic with great battery life. The problem is just with the camera system that is very power/cpu hungry. Only Samsung can do something about it. I've seen dedicated cameras overheating and shutting down.
Click to expand...
Click to collapse
That maybe true but if you stop looking...
Hard to believe Samsung or the reviewers didn't spot that. Factory load version of the apk?
Troubleshooting a stock Android can be counterintuitive worse not as many diagnostic tools available in the name of privacy in 10, 11.
Samsung will eventually punch out an update if it's large batch of phones that are effected.
However during a production run chipsets and smaller components may be substituted as needed. This can create a sub batch of that production run. The firmware update may not fully mesh with the different parts. Samsung is notorious for doing this and sloppy with the records. To even know if it's an issue they need to physically examine the phone.
They can then amend the firmware* or in extreme cases replace the part(s).
You see the implications here... yes it's a crap shoot if the firmware isn't working. In rare case the only way it will be fixed is to send it in for factory service.
*that new firmware update will then be punched out.
Will Samsung fix it, not likely based on their history. Exynos SoC's have had heat disapation issues for years Maybe will see a better offering in the S22.
@varcor, your point is? ANY phone can get hot under certain circumstances. This is not about Exynos. I still don't have OVERheating problems with my personal device. I've never seen the overheating warning.
But you do you. See if you can get more people to sign that anti-Exynos petition or make as many post as you can to convince people not to buy phones with that problematic Exynos that should be avoided at any cost. Keep the hate going. Wait, I forgot that you already know, nobody is buying them, so why go to all this trouble? It's already dead. You can relax now and retire your account.
Why did you edit your post?
When will Apple, Xiaomi or Oneplus fix their overheating problem? Maybe next year.
What power mode is it running in?
Play with the settings.
Sucks being a paying betaware tester...
ione2380 said:
@varcor, your point is? ANY phone can get hot under certain circumstances. This is not about Exynos. I still don't have OVERheating problems with my personal device. I've never seen the overheating warning.
But you do you. See if you can get more people to sign that anti-Exynos petition or make as many post as you can to convince people not to buy phones with that problematic Exynos that should be avoided at any cost. Keep the hate going. Wait, I forgot that you already know, nobody is buying them, so why go to all this trouble? It's already dead. You can relax now and retire your account.
Why did you edit your post?
Click to expand...
Click to collapse
First you state you have no overheating issues then you state you do and there's nothing you can do about it. So which is it? Snapdragon has heat disapation issues as well and here's why. Qualcomm agreed to allow Samsung Foundries to manufacture the 5nm 888 Chipset and they regret that decision. For the upcoming 895 they're pulling out and moving production back to TSMC - Taiwan. To this point Samsung in it's fixation to win the benchmark war continues to boost clock speeds. They haven't been able to manufacture a SoC that doesn't overheat in a very long time. I gave up on Exynos after my S8 and very happy I did. No comparison in heat issues between the Exynos and Snapdragon variants, Exynos losses that battle by a huge margin. Nothing you can argue will change that fact, it is what it is.
Qualcomm Snapdragon 895 to Ditch Samsung, Use TSMC Cores to Fix Overheating in Snapdragon 888 - News18
The Qualcomm Snapdragon 895 has been teased to feature 4nm Kryo 780 cores, a Snapdragon X65 5G modem, Adreno 730 GPU and more.
www.google.com
blackhawk said:
140F is way too hot.
Find what apk(s) are using the power and deal with them directly.
Disable useless bloatware you don't use. Cut out Google constant background bs if you don't need it. All cloud crap, the WhatsApp, FB etc. crapware... kill it. Carrier, Google, Samsung and apk feedback, disable it.
Take out the trash for starters.
My 10+ uses 7-11%@hr SOT. It use to be a hot running, battery eating hog though.
Click to expand...
Click to collapse
I installed the software from with Odin. Nothing is currently installed on the phone. I'm using Samsung own camera app. The same. Latest update is installed. While charging, the battery rises to 58 celcius.
blackhawk said:
What power mode is it running in?
Play with the settings.
Sucks being a paying betaware tester...
Click to expand...
Click to collapse
I didn't change any settings. It is default.
blackcemre said:
I installed the software from with Odin. Nothing is currently installed on the phone. I'm using my own camera app. The same. Latest update is installed. While charging, the battery rises to 58 celcius.
Click to expand...
Click to collapse
Keep the battery below 102F. Li plating is possible at high temperatures. At 103F stop the charge cycle.
Heat and high cell voltage kills Li's.
Do Not discharge below 30, 40% is better.
Charge no higher than 90%, 80% or less is better.
Never attempt to charge an Li at 40F or below!
Do not charge with screen on. Make sure cloud crap isn't going nuts in the background.
Listening to Poweramp via bt is ok during charging though.
Cool it. Fan and/or moist microfiber cloth.
87-99F is the optimum fast changing temperature range.
Below 72F Li plating may occur and fast changing may not engage.
Li's love frequent midrange power cycling from about 40-70%
Charging from below 20% is stressful on the battery especially if the temperature is not kept below 100F. Break and allow to cool.
Ambient temperature where I'm at is 90+F and I have no problems staying in the green zone while fast charging with a 25w brick using the above methods on my new 4300 mAh 10+ battery.
blackcemre said:
I didn't change any settings. It is default.
Click to expand...
Click to collapse
Factory settings aren't necessarily optimized settings. Trust nothing... and generally some bloatware you don't need or want. Google is just as guilty of this. Crap like Google Firebase.
Play with it.
I bought my first Samsung phone in over 10 years, the Samsung S20 FE 4G with the Snapdragon chipset.
To my surprise the device is heating up very quickly while in use:
With light use, like messaging apps the CPU stays around 37 to 49°C,
While gaming it stays around 47 to 50°C+ (I believe the 60°C was the biggest temperature spike).
I've heard people saying that transferring data from your older phone via Smart Switch may cause this heating issue, but I don't think that should be a issue.
Lastly, I have no clue on how weather affects the phone's temperature.
Despite being winter, we're having temperatures around 40°C where I live, but even when the night comes and the temperature drops to around 20°C (right now it's 26°C and the CPU temperature is around 40°C, while I'm listening to music via Bluetooth and (re)writing this post) my phone still heats up (just not as much as in the rest of the day).
I think it's worth mentioning that the CPU temperature is also changing quickly, I don't know if that's normal or not but for instance, when I switch from one app to another, if the app I'm using to measure the device temperature (CPU Monitor) is to be believed, the temperature jumps some 2 to 5°C. It usually comes back down again, but I really don't know if that's normal.
I went to the Samsung store today, they checked, did some tests, and said that the temperature was at normal range, but they said that the temperature while switching between apps was a little strange.
They also said that their system detected a temperature spike caused by Fine Lock on the day that I bought the phone, which I find weird since it's only a launcher to the Good Lock apps, but nevertheless they advised me to uninstall it and keep monitoring the temperature for a few more days, and that if the device gets too hot (over 60°C), that I should go back again and ask for a replacement.
Anyway, should I give some time, should I worry about it, should I take it back to the store?
I have the same model as you and I haven't experienced any of the symptoms you are talking about. If I were you I'd return it and get another one. At least then you can be sure if it is normal or a defective device.
SmartSwitch isn't that smart especially between different OS's/devices.
I think you better start from the beginning...
Backup your contacts etc to the PC using cut/copy plus at least one other hdd.
Factory reset. Reload from scratch. Run factory loaded versions; do not update any at first.
Avoid enabling any power management at least at first.
See what you got and go from there.
It's likely not hardware at all but a bad configuration. Common with Samsungs and correctable.
Orcam said:
I have the same model as you and I haven't experienced any of the symptoms you are talking about. If I were you I'd return it and get another one. At least then you can be sure if it is normal or a defective device.
Click to expand...
Click to collapse
Thank you. I'm thinking about doing it. I've talked to some S20 FE owners who live in my country (which is a very hot country) and they said that the device temperatures are basically the same as theirs, but at the same time I'm still worried about it's long term effects since I plan to keep this phone for at least two years.
blackhawk said:
SmartSwitch isn't that smart especially between different OS's/devices.
I think you better start from the beginning...
Backup your contacts etc to the PC using cut/copy plus at least one other hdd.
Factory reset. Reload from scratch. Run factory loaded versions; do not update any at first.
Avoid enabling any power management at least at first.
See what you got and go from there.
It's likely not hardware at all but a bad configuration. Common with Samsungs and correctable.
Click to expand...
Click to collapse
Thank you, I did what you told me (except for flashing the factory stock ROM since I couldn't find it), I've only restored the apps using the Google backup, but didn't restore my settings. I've also did a mild debloat of the phone (removed Bixby and the Facebook apps) and while using the phone to browse through social media doesn't heat the phone as much as it used to, it still heats up more or less the same during gaming, so I'm guessing that might be normal.
Depending on how CPU cycle intensive the game is, it could normally use a fair amount of power.
Running background apps can make it noticeable worse though.
Try temporarily disabling Google play Services and see if that helps.
blackhawk said:
Depending on how CPU cycle intensive the game is, it could normally use a fair amount of power.
Running background apps can make it noticeable worse though.
Try temporarily disabling Google play Services and see if that helps.
Click to expand...
Click to collapse
It's Honking Impact 3rd, it's not intensive like PUBG or something like that, but can be intensive depending on the game mode. It runs at 53°C max. I found out that one of the apps that I was using to measure the temperature apparently only shows the temperature of the hottest CPU core, that's why the temperature sometimes shoot up to 60°C whenever I took a screenshot for example, and then came back down to around 50°C.
But I'll try disabling Play Services and playing again.
Do you know if those temperatures are safe btw? Around 50°C while I'm gaming.
The battery's temperature doesn't go past 40°C, in fact I don't even think I've ever seen it getting to 40°C.
Anyway, thank you very much.
You're welcome. The Farenheit is scaled better for real world use.
140F is well within tolerance for the CPU/mobo as long as the battery doesn't get hotter than that. I don't let my battery go beyond 103F.
The CPU/mobo can handle up to probably 165F but it's best never to push it that hot as auto thermal shutdown doesn't always work in time to save the components that are running hot and have a sudden additional power usage spike.
Really the phone shouldn't feel hot... it's killing the battery too. Track them down.
If it feels warm when using the browser, something(s) are running in the background driving it up.
Any cloud apps, including Google backup Transport, Framework and Google Firebase.
Ditch any trashware apps like WhatsApp, Twitter, Instagram etc.
I'm using my 10+ in a case at a 75F ambient air temp browsing with a CPU temp of 89F right now. It is stock but heavily optimized.
blackhawk said:
You're welcome. The Farenheit is scaled better for real world use.
140F is well within tolerance for the CPU/mobo as long as the battery doesn't get hotter than that. I don't let my battery go beyond 103F.
The CPU/mobo can handle up to probably 165F but it's best never to push it that hot as auto thermal shutdown doesn't always work in time to save the components that are running hot and have a sudden additional power usage spike.
Really the phone shouldn't feel hot... it's killing the battery too. Track them down.
If it feels warm when using the browser, something(s) are running in the background driving it up.
Any cloud apps, including Google backup Transport, Framework and Google Firebase.
Ditch any trashware apps like WhatsApp, Twitter, Instagram etc.
I'm using my 10+ in a case at a 75F ambient air temp browsing with a CPU temp of 89F right now. It is stock but heavily optimized.
Click to expand...
Click to collapse
The phone doesn't feel hot, unless I'm playing a game, depending on the game it gets somewhat hot.
It's been colder in my city these past two days, but tomorrow we'll have a temperature that's closer to normal. If the phone manages to stay in an acceptable temperature range I'll keep it, if not, I'll return it to the store and see what I can get done.
My old phone didn't have a plastic back, so feeling the phone warm is a new thing for me.
Most Google apps are disabled, I only use WhatsApp to talk to my family, I have Instagram installed but I don't even remember when it was the last time I've used it (I put it on deep sleep also).
Thank you very much once again.
Using power management can cause erratic behavior and sometimes increased power usage especially if set globally.
Developer options>standby apps, all buckets should show as active otherwise power management is running.
blackhawk said:
Using power management can cause erratic behavior and sometimes increased power usage especially if set globally.
Developer options>standby apps, all buckets should show as active otherwise power management is running.
Click to expand...
Click to collapse
With Power Management you mean the Background Usage Limits from the Device Care app?
furquim97 said:
With Power Management you mean the Background Usage Limits from the Device Care app?
Click to expand...
Click to collapse
Yeap. I have a 10+ running on Pie.
Your may get different results but it's a known source of instability and trouble.
This is how mine is configured.
blackhawk said:
Yeap. I have a 10+ running on Pie.
Your may get different results but it's a known source of instability and trouble.
This is how mine is configured.
Click to expand...
Click to collapse
I'll try it. Thank you once again.
blackhawk said:
Yeap. I have a 10+ running on Pie.
Your may get different results but it's a known source of instability and trouble.
This is how mine is configured.
Click to expand...
Click to collapse
I did it but now all my apps under Standby Apps are set as "Active" and I can't change it. Won't this consume more battery?
furquim97 said:
I'll try it. Thank you once again.
Click to expand...
Click to collapse
Once you do that you need to track down the trouble makers and deal with each on a case by case basis. Sometimes simply cleaning the system memory in Device Care can work wonders. Keep open apps to a minimum.
Here's the old version of Device Care. It uses 360° which cleans very well but is CCP junk.
To safely use it use Karma Firewall* to block its internet access. It will still run normally.
Before uninstalling your current version use Apk Export** to make a installable copy, just in case.
*freeware, uses almost no battery
**freeware that is very useful to backup all your apps and updates for future use... ditch Playstore for reloads
blackhawk said:
Once you do that you need to track down the trouble makers and deal with each on a case by case basis. Sometimes simply cleaning the system memory in Device Care can work wonders. Keep open apps to a minimum.
Here's the old version of Device Care. It uses 360° which cleans very well but is CCP junk.
To safely use it use Karma Firewall* to block its internet access. It will still run normally.
Before uninstalling your current version use Apk Export** to make a installable copy, just in case.
*freeware, uses almost no battery
**freeware that is very useful to backup all your apps and updates for future use... ditch Playstore for reloads
Click to expand...
Click to collapse
Thanks. But I can't uninstall the current Device Care app. Is it safe to do it via adb?
furquim97 said:
I did it but now all my apps under Standby Apps are set as "Active" and I can't change it. Won't this consume more battery?
Click to expand...
Click to collapse
This is normal. Just because their bucket state is marked as active doesn't mean they are running. It simple means Android is no longer managing them by assigning a bucket state to them and so on. Google it... it sounds like a great idea but it never worked well for me in practice. Android still manages the apps with it off less the added resource burden of this system.
furquim97 said:
Thanks. But I can't uninstall the current Device Care app. Is it safe to do it via adb?
Click to expand...
Click to collapse
Sorry. You are correct.
I got rid of the updated version by doing a factory reset. You can try loading the older version by first force stopping the loaded version. It may worked... try this first.
I guess a adb edit would allow you to disable the current one. If the older one will load is another question.
blackhawk said:
This is normal. Just because their bucket state is marked as active doesn't mean they are running. It simple means Android is no longer managing them by assigning a bucket state to them and so on. Google it... it sounds like a great idea but it never worked well for me in practice. Android still manages the apps with it off less the added resource burden of this system.
Click to expand...
Click to collapse
Oh, I get it. Thanks.
blackhawk said:
Sorry. You are correct.
I got rid of the updated version by doing a factory reset. You can try loading the older version by first force stopping the loaded version. It may worked... try this first.
I guess a adb edit would allow you to disable the current one. If the older one will load is another question.
Click to expand...
Click to collapse
I'll see what I can do.
I'll also test the phone again tomorrow when the weather in my city will return to normal. If everything goes well I'll keep the phone, if not I'll have to take it to the store and see what they offer me, a replacement, another device, I really don't know how it works in this particular store that I bought.
Anyway, thank you very much, you've been very helpful!
My 10+ was a battery guzzling hot running hog before I optimized it. It took some time and effort
Today you never guess it is that same phone.
If there's any doubts get a refund. It could be hardware, even a heat sink or pipe issue.
That said this is a commonly seen problem that has nothing to do with hardware in Samsungs.
Do some Google searches for that device and hot running issues. See what you find.
blackhawk said:
My 10+ was a battery guzzling hot running hog before I optimized it. It took some time and effort
Today you never guess it is that same phone.
If there's any doubts get a refund. It could be hardware, even a heat sink or pipe issue.
That said this is a commonly seen problem that has nothing to do with hardware in Samsungs.
Do some Google searches for that device and hot running issues. See what you find.
Click to expand...
Click to collapse
I can relate. I had a Xiaomi before this one, and the stock ROM was plagued with app killing and battery drain. I'm glad you managed to work it out, all I had to do was switch to a custom ROM.
I've tested the same game again today since the temperature has gone back to normal where I live, and while the CPU temperatures are in acceptable range, the battery temperature got to 40°C/104°F.
I did some research regarding overheating on this phone and it's always the same thing, some have it like I do, while others say the phone doesn't even warm up the palm of their hands. So I don't know if its a configuration issue or if there are a lot of defective devices out there.
Looking at the OnePlus 10 pro on paper, it has everything you would possibly need to achieve incredible screen on times.
The idea behind this besides some healthy competition is to whittle out the bugs and battery draining apps and habits.... in the hope that we all benefit from the knowledge learned and gathered.
LEADERBOARD
--------------------------
dladz - 11 hours 21 minutes: EU 11_A.12
2. Macke93 - 8 hours 40 minutes: EU 11_A.12
3.
4.
5.
6.
7.
8.
9.
10.
Rules
---------
If you'd like to register an SOT, you will need to provide a screen shot of your battery stats using the stock battery app, clearly showing the up time and screen usage time and app list.
Your OS, kernel if different from stock (no screen shot required)
NOTE*** Without this proof, your name and score won't be added.
That's it
Good luck
Some tips for better battery life.
Change 5G to 4G
Remove Facebook use web based
Remove Facebook messenger use web based
Remove Twitter use web based
Remove any ad based apps pay for the pro version
Turn off gestures like lift to wake
Change from QHD to FHD (No difference)
Allow auto brightness
Turn off WiFi overnight
Turn all updates to manual not auto (play store)
Remove any so you don't use
Change back up to once a month (WhatsApp)
Turn off location history (Google)
Use titanium to remove any system apps you don't need
Don't allow anonymous usage statistics for any app ever.
Don't allow tracking cookies on any website
Use adaway (root needed)
Don't open web pages in Google app (I use Samsung browser)
Don't use xposed.
If you game you will not get high SOT scores, period.
Don't bother with battery saving apps or monitoring apps.
Streamline your apps, if you don't use it, remove it.
Don't allow WiFi scanning (as in letting other apps use it when it's not on)
Never allow personalised ads.
Never allow notifications from websites
Always decline cookies unless your absolutely have to allow some tracking (common sense prevails here)
Optimise as many apps as possible unless it affects performance.
Don't allow apps to remain open in the notification area.
Change your launcher, my preferred launcher is lawn chair and this did actually burn up some battery when compared to the OnePlus launcher.
Don't use live widgets (yes they look cool, but they annihilate your battery)
Live wallpaper, again very cool, but battery burners.
Again! Don't charge overnight, make a note of your percentage then see what it is in the morning, you shouldn't be losing more than 5% really, if you've done well then it'll be reflected here, the good SOT results will follow.
Turn off live read outs of network speed, RAM usage in the status bar.
Turn off NFC unless in use.
Leave location on in quick settings.
Don't overcharge your phone, IE: overnight
Don't allow your phone to fully deplete the battery.
Whatever anyone says, this does 100% damage batteries, there is no argument here and I won't entertain anyone who says otherwise, Ive seen through real life tests what this results in, bloated, inefficient, possibly dangerous lithium batteries.
Keep your phone out the sun.
Keep it out of extreme cold.
Keep your device clean and dust free.
Snapchat, Viber, house party, apps like that tend to use more battery as they don't have great dormancy periods, use them if required and get rid.
Apps like speed test by Ookla tend to have location tracking, similarly they tend to turn themselves on and off when they feel like it, my advice, install test and uninstall.
Allow a couple of battery cycles between tweaking sets, to give you an idea of how much of a difference you've made.
Use BBS to see what is being used, once you've removed problems, remove BBS.
I've just written this from the top of my head so I've probably missed some things, the general idea is to keep your device clean and fresh, remove files / apps / mods / widgets / features you don't need any more.
Keep an eye on apps that misbehave or aren't wanted, index your folders so they aren't a mess.
The more good things you do means the more potentially bad apps you can have on your phone, eg if you really need Facebook, you could keep it so long as you clean up other areas of your phone.
Hope this helps.
9 hours 45 11_A.12 NE2213
NE2213_11_A.12
EU model, Oxygen OS 12.1
Only 4G, no WiFi!
7 hours 1 minute.
(Screenshot deleted while re-locking bootloader).
Macke93 said:
NE2213_11_A.12
EU model, Oxygen OS 12.1
Only 4G, no WiFi!
7 hours 1 minute.
(Screenshot deleted while re-locking bootloader).
Click to expand...
Click to collapse
I'll put it up as there's none up and a believable time.
Changed over to lawnchair 2 and holy moly the difference has been amazing.
0% lost overnight 8 hours
Currently on 4 hours with normal usage, it's heading for a ridiculous screen on time.
6 hours and 2 minutes with 41% used.
Crazy
dladz said:
Changed over to lawnchair 2 and holy moly the difference has been amazing.
0% lost overnight 8 hours
Currently on 4 hours with normal usage, it's heading for a ridiculous screen on time.
Click to expand...
Click to collapse
Any difference between lawnchair 2 and other lawnchair versions then?
kouzelnik3 said:
Any difference between lawnchair 2 and other lawnchair versions then?
Click to expand...
Click to collapse
Not that I've noticed.. its just the one from the play store. I think it's 2. Could be wrong, certainly more efficient than anything else I've tried.
I'm just happy I've managed to get my phone to be dropping 0% overnight, that's how it should be.
My 8 pro used to take about 4-8% overnight
dladz said:
Changed over to lawnchair 2 and holy moly the difference has been amazing.
0% lost overnight 8 hours
Currently on 4 hours with normal usage, it's heading for a ridiculous screen on time.
Click to expand...
Click to collapse
Gonna try out Lawnchair launcher and see if it helps my phone too
Most recently I now have 8 hours SOT with 12% battery left. Feels good gonna try to empty the battery to 1-2% and report back the SOT here once again.
dladz said:
Not that I've noticed.. its just the one from the play store. I think it's 2. Could be wrong, certainly more efficient than anything else I've tried.
I'm just happy I've managed to get my phone to be dropping 0% overnight, that's how it should be.
My 8 pro used to take about 4-8% overnight
Click to expand...
Click to collapse
I got 2 % drain overnight 8 hours, which is ok for me with everything I got installed (airplane mode).
I wonder whether I will try lawnchair too, but I am using Nova for years
kouzelnik3 said:
I got 2 % drain overnight 8 hours, which is ok for me with everything I got installed (airplane mode).
I wonder whether I will try lawnchair too, but I am using Nova for years
Click to expand...
Click to collapse
Comparing the two I prefer lawnchair, nova is a little too flicky for my liking, I prefer smooth transitions and fluidity rather than overly quick and flicky, you'll know what I mean when you install it 2% is still 2-6% better than the 8 pro..
Macke93 said:
Gonna try out Lawnchair launcher and see if it helps my phone too
Most recently I now have 8 hours SOT with 12% battery left. Feels good gonna try to empty the battery to 1-2% and report back the SOT here once again.
Click to expand...
Click to collapse
Tbh that's still great time you're making.
It's nuts I'm on 7+ hours with 52% left.
Haven't been doing anything special, just using my phone.
dladz said:
Not that I've noticed.. its just the one from the play store. I think it's 2. Could be wrong, certainly more efficient than anything else I've tried.
I'm just happy I've managed to get my phone to be dropping 0% overnight, that's how it should be.
My 8 pro used to take about 4-8% overnight
Click to expand...
Click to collapse
Try disabling Google play Services when not needed. It has a bunch of power sucking dependencies. I disable more Google system apps than that on my N10+, but disabling play services may be enough to tone it down especially at night.
Use manual brightness control and keep below 50%.
Social media apps should never be installed for a variety of reasons including excessive battery consumption... just saying.
blackhawk said:
Try disabling Google play Services when not needed. It has a bunch of power sucking dependencies. I disable more Google system apps than that on my N10+, but disabling play services may be enough to tone it down especially at night.
Use manual brightness control and keep below 50%.
Social media apps should never be installed for a variety of reasons including excessive battery consumption... just saying.
Click to expand...
Click to collapse
I agree buddy, but I'm not sure I need to disable anything else.... At this rate I'll have 14 hours SOT..
Have a look at the second post for my idea of keeping the battery down
But then again, could always have more...
So when you disable Google play services. What method are you using?
Just literally disable it?
dladz said:
I agree buddy, but I'm not sure I need to disable anything else.... At this rate I'll have 14 hours SOT..
Have a look at the second post for my idea of keeping the battery down
But then again, could always have more...
So when you disable Google play services. What method are you using? It was listed at one time on Package Disabler Pro but was inexplicably removed.
Click to expand...
Click to collapse
Agreed, it sounds optimized to me! Hell yeah.
Most Android phones need to be optimized to get best performance... just the way it is.
I go to settings>apps, search for play, then disable/enable it there. I use it 2-3 [email protected] day, sometimes less.
If the disable option is grayed out, go to security and disable Find my Device as a system Administrator.
So many big sister Gookill system apps I hate...
blackhawk said:
Agreed, it sounds optimized to me! Hell yeah.
Most Android phones need to be optimized to get best performance... just the way it is.
I go to settings>apps, search for play, then disable/enable it there. I use it 2-3 [email protected] day, sometimes less.
If the disable option is grayed out, go to security and disable Find my Device as a system Administrator.
So many big sister Gookill system apps I hate...
Click to expand...
Click to collapse
Just done it but getting a lot of dings every time I unlock, little annoying tbh. I'm just wondering is the call to open services actually using battery ? I dunno. Perhaps if there wasn't a load of notifications..
I'll leave it for this cycle and maybe see how it compares next time, I'm not out over the weekend so have a good location to get fault results.
dladz said:
Just done it but getting a lot of dings every time I unlock, little annoying tbh. I'm just wondering is the call to open services actually using battery ? I dunno. Perhaps if there wasn't a load of notifications..
I'll leave it for this cycle and maybe see how it compares next time, I'm not out over the weekend so have a good location to get fault results.
Click to expand...
Click to collapse
On my phone it can suck up to 1+%@hr with screen on... so it adds up. No reasoning with it.
You can kill those very annoying notifications; Gmaps, Gmail, do it; disable notifications. There may be more depending on your configuration.
Leave the warning running and when you disable notifications in the right app... it will stop. Instant gratification