Related
After updating to latest version of Google Play Services I have started to notice some sort of partial wakelocks. After 6hrs use I've got 44mins wakelock by google play services. Has anyone else noticed such behaviour? I have tried Purity Rom, Cm and Carbon just incase if there's difference, but I've encountered the same wakelock always. Here's what wakelock detector shows
http://forum.xda-developers.com/showthread.php?t=2785128
Lethargy said:
http://forum.xda-developers.com/showthread.php?t=2785128
Click to expand...
Click to collapse
Edit:thanks!
wakelocks are how your phone works, they are supposed to be. an occasional incident might happen, and a process will get "stuck", which could keep a wakelock active. tell me, your wakelock, is it draining battery faster than usual? a reboot will usually fix these kinds of incidences. but you say you flashed roms since, and still the same.. so my next question is which apps are you using that is using this wakelock?
simms22 said:
wakelocks are how your phone works, they are supposed to be. an occasional incident might happen, and a process will get "stuck", which could keep a wakelock active. tell me, your wakelock, is it draining battery faster than usual? a reboot will usually fix these kinds of incidences. but you say you flashed roms since, and still the same.. so my next question is which apps are you using that is using this wakelock?
Click to expand...
Click to collapse
Afaik I don't use any apps that trigger these wakelocks I've experienced. The only solution I've found so far is to disable services called "Configfetchservice" and "userpresenceservice". I've got these wakelocks no matter what ROM or even if I had disabled all Google stuff (sync, location, device manager and so on). Always after a day I have about an hour of Google play services wakelocks by userpresenceservice and configfetchservice. Never had this before. I'm sure it has something to do with latest google play services versions. I know wakelocks are very important part in smartphones but these kind of wakelocks are everything else but wanted.
rockknee said:
Afaik I don't use any apps that trigger these wakelocks I've experienced. The only solution I've found so far is to disable services called "Configfetchservice" and "userpresenceservice". I've got these wakelocks no matter what ROM or even if I had disabled all Google stuff (sync, location, device manager and so on). Always after a day I have about an hour of Google play services wakelocks by userpresenceservice and configfetchservice. Never had this before. I'm sure it has something to do with latest google play services versions. I know wakelocks are very important part in smartphones but these kind of wakelocks are everything else but wanted.
Click to expand...
Click to collapse
so you are saying that these wakelocks exist for you.. one very important question to an answer you havent mentioned at all, are these wakelocks causing battery drain?
simms22 said:
so you are saying that these wakelocks exist for you.. one very important question to an answer you havent mentioned at all, are these wakelocks causing battery drain?
Click to expand...
Click to collapse
Not really shocking drain but noticable it is, which is nothing exceptional. It does these wakes during deepsleep every now and then. And of course when device is not used much and there is google play services on top 3 consuming elements at settings-> battery that's not the way it should be. Now I'm going to enable those services again and look for the logcat if I could find out to which app it is related to.
rockknee said:
Not really shocking drain but noticable it is, which is nothing exceptional. It does these wakes during deepsleep every now and then. And of course when device is not used much and there is google play services on top 3 consuming elements at settings-> battery that's not the way it should be. Now I'm going to enable those services again and look for the logcat if I could find out to which app it is related to.
Click to expand...
Click to collapse
if its draining some battery, but nothing in large amounts, i wouldnt really worry about it. as sometimes these wakelocks appear, then disappear a week or two later.
simms22 said:
if its draining some battery, but nothing in large amounts, i wouldnt really worry about it. as sometimes these wakelocks appear, then disappear a week or two later.
Click to expand...
Click to collapse
I guess you're right. I'll just keep those services enabled for a week or so and see wheter it goes away or gets nasty and drains my battery in couple hours.
rockknee said:
I guess you're right. I'll just keep those services enabled for a week or so and see wheter it goes away or gets nasty and drains my battery in couple hours.
Click to expand...
Click to collapse
a while back, these kinds of things drove me crazy. then one day i just decided not to think about them anymore, and have been better off since. sure, every once in a while(rare, usually location oriented) a wakelock will appear that will drain lots of battery, but ill just use the disable services app to kill that wakelock for a week or two, then ill switch it back and all will be normal.
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
KodRoute said:
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
Click to expand...
Click to collapse
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Lethargy said:
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Click to expand...
Click to collapse
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
KodRoute said:
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
Click to expand...
Click to collapse
The CPU throttles at 65C by default (some kernels change this or give you an option to change it), and shuts down at 105C. 47C is hardly anything.
Hello guys. This topic is pretty long and it is hard to read all of it but try to read all of it till end.
Well, let me begin. The main problem of the nougat update is the dramatic increase of battery consumption (for me at least) But why this is happening?
Actually this is a matter of battery managers. Huawei had created a great phone but obviously they messed things up in the software side. Google announced "Doze" feature with Marshmallow. If we could have a brief explanation of "what doze is" is it is basically a battery protection policy created by google. In Android, apps have the ability to use what’s called a “wakelock” to prevent your phone from going into a power-saving deep sleep mode. This deep sleep mode usually kicks in when your phone’s screen is off, but that can get in the way of how some apps work. For example, if you’re using a fitness tracker, you don’t want your phone turning off GPS or your accelerometer just because your phone is in your pocket with the screen turned off.
In principle, this is a good concept. Apps keep your phone awake and working when they need to, and let it sleep when they don’t. This is a problem, though, when every developer thinks their app is important enough to keep your phone on all the time. That’s why apps like Facebook kill your battery, even when you’re not using them.
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device). Here is a graphical explanation of how doze works versus time:
http://itresan.com/wp-content/uploads/2016/05/doze-header.jpg
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device)
If we turn back to the main topic, as I mentioned before, Huawei has some difficulties combining it's own features with google's. Huawei has its own battery manager. That's why you are not receiving some notifications from facebook or whatsapp. That is because that freaking battery manager shuts everything off but still, since it has a very poor approach, the system drains battery. It is basically a matter of doze does not kicking in. As you can see, the battery usage when the screen is turned on is about the same. However, the same thing cannot be seem when the screen is off.
So what to do in order to save some juice?
-There is some workarounds for doze kicking in like these ones:
https://play.google.com/store/apps/details?id=com.yirgalab.dzzz
https://play.google.com/store/apps/details?id=com.suyashsrijan.forcedoze
These two apps have different approaches. I prefer ForceDoze as it seems the google's intended way.
I want to highlight this item because this might be the most important thing in this topic. If you don’t do anything with your phone, Doze will still do its job. It runs almost invisibly in the background. Occasionally you’ll get a few messages at once, rather than spread over a few minutes, but for the most part there’s no noticeable change. In other words this is a bit different from the conventional full deep sleep and you do not have to afraid from doze as you do with the full deep sleep.
-DO NOT CLEAN YOUR RAM TOO OFTEN. This will cause closed apps re-open and hence, more cpu usage.
-No! Cleaners, Task managers and other stuff does not work! As I mention before, they even lead more battery consumptions.
-Huawei has poor google service implementations. Even one or two implementation has some bugs that causing battery drain(for example: google backup). Try to turn them off.
-Know when to reboot your phone. Too frequent reboots may do the same thing as you cleaning your ram. However, rebooting cleans app caches so the system will work smoother. Once a week or two weeks is fine I suppose.
Please hit the "Thanks" button if you like and please point out the missing things and if you see a mistake please warn me for correcting it. I hope you liked the topic.
Have a nice day!
Doze is problem for me. I don't have push notification by the night.
darrr1 said:
Doze is problem for me. I don't have push notification by the night.
Click to expand...
Click to collapse
It's probably not because of the doze but the huawei's power manager itself.
Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem
darrr1 said:
Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem
Click to expand...
Click to collapse
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.
I did everything what I can without succes.
furkey said:
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.
Click to expand...
Click to collapse
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?
xtcislove said:
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?
Click to expand...
Click to collapse
Doze is not on kernel level but it is on software level. Programmatically we can activate what is left from doze or at least simulate it. However, if there is a certain need for doze we should cook a whole new rom and yes, it requires open source too.
But, let's clear a thing here: Huawei did not completely removed doze. Actually, I think they can't do that if they wish to use Android. Just some settings of Huawei conflicts with doze and prevent its functioning.
I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.
antimatter.web said:
I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.
Click to expand...
Click to collapse
Could you finally solve this?
I also have and Honor 9, and have the same problem with aplicacition radardroid. Is getting killed, and also have all configured to prevent this...
Try by having both in the Settings
-Battery/Close apps after lock screen (uncheck in the list)
-Apps/Settings gear/Special access/Ignore battery optimization (make it allowed)
Thank szgfg,
Both are already well configured, but still closing the app.
mikicl said:
Thank szgfg,
Both are already well configured, but still closing the app.
Click to expand...
Click to collapse
Check also is not being closed by the automatic cleanup (so add it to clean whitelisted apps) and that is not being closed due to high consumption...disable that on battery settings... Let the advertisement but do not let phone administrator close that apps automatically
Enviado desde mi EVA-L09 mediante Tapatalk
Hi jcalderonv74,
Thanks for your answer. I didn't know about the clean whitelisted apps, was a surprise to find it. But unfortunetly, everything was well configured.
Option to avoid being closed due to high consumption was already OK.
So nothing to change, everything was as it has to be. Seems more a software problem in EMUI 5.0
After some days without touching anything in the phone's configuration, finally observed that everything is working fine. All aplications configured keep opened, and it's only Radardroid aplication that sometimes closes alone (only sporadically after a recent update)
Seems more an error in Radardroid aplication that in telephone's software. So I'm not worring more about that.
I am running into a Wakelock issue and I am completely stumped. For some reason, my phone refuses to go into deep sleep for hours on end. Better Battery Stats shows that the phone spends the majority of its time with the CPU at its lowest frequency, but refuses to go into deep sleep. The issue started when I clean flashed LinageOS back when I tried 14.1. Since 15.1 has recently released, I tried to have another go, yet the problem remains. I am using a Oneplus 5.
The very weird thing about these Wakelocks is, is that they are completely invisible. Wakelock Detector isn't showing any specific wakelocks (Advanced mode enabled), but does show that the phone isn't entering the deep sleep state. Not even for a single second. Better Battery Stats shows the same thing, with zero seconds spent in Screen off (deep sleep) and all the time spent in Screen off (Awake). No application is listed anywhere that's causing these wakelocks. They aren't visible under partial wakelocks nor kernel wakelocks.
Now this is where things get bizarre. I tried removing all my applications and reinstalling them one by one to find out if it was an app that was causing the issues. Each time I installed an app, I would check whether the phone would go into deep sleep when I wasn't using it. It turns out that the phone stopped going into deep as soon as Whatsapp was installed. Yet Whatsapp would never register more than a few seconds of wakelocks each passing hour.
I'm not sure where to even begin to try and solve this issue. Has anyone else ever experienced these kind of invisible / hidden wakelocks, and if so, how did you manage to fix these issues? Thank you very much in advance for helping me out
Nobody with a similar problem to mine? It's really killing battery life for me
Mushoz said:
Nobody with a similar problem to mine? It's really killing battery life for me
Click to expand...
Click to collapse
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
IanHodgson said:
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
Click to expand...
Click to collapse
No, I still have the same issue unfortunately. Though my issue seems to be slightly different than yours in the sense that Whatsapp is very low in the list. The total minutes of Wakelock is far below the total minutes of awake (screen off). But uninstalling Whatsapp instantly solves the wakelock issue. Out of interest, what phone are you using and what rom?
Mushoz said:
Out of interest, what phone are you using and what rom?
Click to expand...
Click to collapse
Redmi Note 4, Pixel Experience Oreo 8.1
I got here through a google search. I am not sure it's whatsapp causing this (haven't removed it yet) but on a Moto G3 with LOS 15.1 unofficial by Rahul I have the same symptoms.
First off, I love the phone and I'll keep it, but ever since I got the phone I've been wondering why it's draining so much in standby. It's my first Samsung phone since 2011, so naturally I assume it's Samsung apps/services that drain? Especially since I don't use any new apps than on my other phones and in the battery stats it doesn't really show any user apps that use a lot.
Anyone has way to measure what system/user apps drain during standby? Or even better, any dev that could do a deeper dive into this?
For example, I just lost 32% battery while sleeping for about 8h, it has never been this much on any other of my previous phones (OnePlus Nord/Pixel 3a/Pixel 3/Pixel 2).
In fact, my OnePlus Nord with 815mAh more than the Flip3 is currently on last charge 3 days ago (it doesn't show me hours anymore) and 2h35m SOT and 25% battery left. On the Flip I just now got 17h with 1h30m SOT and 5% left. Settings all similar besides location accuracy turned off for the Flip as that was a massive drain.
Something must be unintentionally draining the battery during standby and I really hope one of you smart guys can find it. Or Samsung fixes it with an update..
I disabled AOD and any unnecessary account sync processes. It's only drained about 2% in standby the last 5 hours, but there are still some things to finish configuring.
twistedumbrella said:
I disabled AOD and any unnecessary account sync processes. It's only drained about 2% in standby the last 5 hours, but there are still some things to finish configuring.
Click to expand...
Click to collapse
If have AOD on a schedule so it's turned off during sleeping, account syncing I don't have anything that I can turn off and I never did on any previous phone
M4-NOOB said:
If have AOD on a schedule so it's turned off during sleeping, account syncing I don't have anything that I can turn off and I never did on any previous phone
Click to expand...
Click to collapse
How old is your device? You got to give it some time to settle. I had 15% battery drain the first night, after that it went down to 5%.
M4-NOOB said:
If have AOD on a schedule so it's turned off during sleeping, account syncing I don't have anything that I can turn off and I never did on any previous phone
Click to expand...
Click to collapse
The first step in improving the battery is to remember that this isn't any other phone. You may want to explore what options are available and what all you have enabled. By default, almost everything is on to show off all the cool new features that make this a Flip 3, not a OnePlus Nord.
ione2380 said:
How old is your device? You got to give it some time to settle. I had 15% battery drain the first night, after that it went down to 5%.
Click to expand...
Click to collapse
Got it 4 days ago
twistedumbrella said:
The first step in improving the battery is to remember that this isn't any other phone. You may want to explore what options are available and what all you have enabled. By default, almost everything is on to show off all the cool new features that make this a Flip 3, not a OnePlus Nord.
Click to expand...
Click to collapse
Which Flip features are in use during standby though? During standby it's just another phone
M4-NOOB said:
Which Flip features are in use during standby though? During standby it's just another phone
Click to expand...
Click to collapse
Not true. Samsung has a bunch of features still in use.
Settings -> Advanced features -> Motions and gestures has a whole collection of things that are still running when the screen is off (and most aren't useful to the Flip, but came from "another phone").
Settings -> Cover screen allows you to disable turning on the screen when notifications arrive, if that is not something you need.
Also, unless you are using the app to lower the refresh rate, you may be running a bit high when idle.
twistedumbrella said:
Settings -> Advanced features -> Motions and gestures has a whole collection of things that are still running when the screen is off (and most aren't useful to the Flip, but came from "another phone").
Click to expand...
Click to collapse
I've turned a few things off there, but a lot of them OnePlus has too + a few more, which I had all enabled
twistedumbrella said:
Settings -> Cover screen allows you to disable turning on the screen when notifications arrive, if that is not something you need.
Click to expand...
Click to collapse
I didn't really get any notification during last night, so I doubt this was the culprit
twistedumbrella said:
Also, unless you are using the app to lower the refresh rate, you may be running a bit high when idle.
Click to expand...
Click to collapse
Yes I'm using that app and have it set to 48-96Hz
Appreciate the help, I believe there must be something that's unintentionally draining and while I went through every single setting in the beginning, I'm still very new to OneUI (and also impressed how far it came from the TouchWiz ****show)
One thing I always forget is that a lot of those features are running services and polling when they're enabled. Even though I'm not touching the screen with the tap to wake enabled, it's constantly waiting for that tap when it's asleep. Any one isn't a big impact, but Samsung has so many "convenience" features that I end up wasting battery to never use.
The calibration period is also horrible. Android 11 is slow to calibrate the battery and Samsung is worse. You can get a good idea of what is draining battery by going to Settings -> Battery and device care -> Battery. That may help find out if it's a renegade app.
One thing Asus does that I wish Samsung would embrace is Auto-start management. Some apps aren't efficient at polling for notifications and more than once have been the cause of major drain.
Another one even Samsung admits to be a source of drain is the edge panels. If you don't use them, it's best to kill the entire feature.
twistedumbrella said:
Even though I'm not touching the screen with the tap to wake enabled, it's constantly waiting for that tap when it's asleep. Any one isn't a big impact, but Samsung has so many "convenience" features that I end up wasting battery to never use.
Click to expand...
Click to collapse
I just assumed it's not a big impact as OnePlus has those as well, for example draw a "V" on screen for flashlight or ">" to skip song besides the regular double tap to wake and it never appeared to be a battery issue for me before.
twistedumbrella said:
You can get a good idea of what is draining battery by going to Settings -> Battery and device care -> Battery. That may help find out if it's a renegade app.
Click to expand...
Click to collapse
Do I assume correctly that some system apps or similar are hidden there? I just did the calculations and the percentages only make up 43.6%. I attached a screenshot
M4-NOOB said:
I just assumed it's not a big impact as OnePlus has those as well, for example draw a "V" on screen for flashlight or ">" to skip song besides the regular double tap to wake and it never appeared to be a battery issue for me before.
Do I assume correctly that some system apps or similar are hidden there? I just did the calculations and the percentages only make up 43.6%. I attached a screenshot
Click to expand...
Click to collapse
OnePlus also optimizes them better than brand new Samsung firmware. I had a lot of stuff enabled on the Note 20 Ultra that I won't be using for a month or two now.
Some apps are excluded, but it will let you know if it's something not included with the phone.
Another good idea is to uninstall, disable, or "adb uninstall" any bloat you don't use. Besides clearing up space in the app drawer, it kills off services you don't use. A lot of the apps will run services even before you sign in, even though they aren't actually handling any data.
twistedumbrella said:
Another good idea is to uninstall, disable, or "adb uninstall" any bloat you don't use. Besides clearing up space in the app drawer, it kills off services you don't use. A lot of the apps will run services even before you sign in, even though they aren't actually handling any data.
Click to expand...
Click to collapse
I already went through the list and uninstalled which I 100% knew what it was and that it's not needed, but not sure about 99% of Samsung stuff. Some Samsung apps on the phone I don't even know what they are and when I start them it just prompts to agree to some terms before starting the app... I'll have a look around for a Samsung debloat list
M4-NOOB said:
I already went through the list and uninstalled which I 100% knew what it was and that it's not needed, but not sure about 99% of Samsung stuff. Some Samsung apps on the phone I don't even know what they are and when I start them it just prompts to agree to some terms before starting the app... I'll have a look around for a Samsung debloat list
Click to expand...
Click to collapse
If you have the unlocked version, they allowed uninstall for a lot of apps that were previously locked. A lot can also be downloaded later from Google Play or the Galaxy Store if you change your mind.
I use Firefox, so I uninstall Samsung Internet and Chrome. Members and Health are two big ones that like to run those "please enable us" services. It's a lot of deciding what you might use versus what you can live without.
Another good idea is to add anything you won't use, but didn't remove to deep sleeping apps to kill it's ability to run in the background. It's the closest thing to auto start management without rooting.
[HOW-TO][DEBLOAT][ADB] The ultimate ADB debloating thread for the S20/+/U series
Hi, i´ve seen some threads and questions about debloating in the s20 forum, but by having a quick look at them, theres not much information for beginners. Thats why I decided to sign up and join the xda community. I would like to make this the...
forum.xda-developers.com
twistedumbrella said:
Another good idea is to add anything you won't use, but didn't remove to deep sleeping apps to kill it's ability to run in the background. It's the closest thing to auto start management without rooting.
Click to expand...
Click to collapse
Yeah I do have 57 apps there already
I just removed 85 apps/services via adb, let's see how it is tonight and I'll report back tomorrow
M4-NOOB said:
Yeah I do have 57 apps there already
I just removed 85 apps/services via adb, let's see how it is tonight and I'll report back tomorrow
Click to expand...
Click to collapse
Thank you for taking the time, mine is also going down %30 overnight. would love to hear about your result.
ShayMagen said:
Thank you for taking the time, mine is also going down %30 overnight. would love to hear about your result.
Click to expand...
Click to collapse
So far I don't have much hope sadly. Whole day currently at home and not using the phone much and it's looking like in the screenshot (screen off, loosing almost 2.7% per hour, as comparison my OnePlus is at 0.9% per hour)
https://imgur.com/RLITZwQ
It's 21:21 at the moment and I'm at 54% after 9h 42m (comparison OnePlus with 815mAh more: 7% after 79h with 2h54m SOT)
https://imgur.com/M9zO2hV
I'll probably head to bed in a few hours and then report back tomorrow morning how much I lost during the night..
I'm not claiming to have amazing battery life, since I almost considered keeping my trade-in and returning this one over it. I am interested why it is so bad for others, though.
twistedumbrella said:
I'm not claiming to have amazing battery life, since I almost considered keeping my trade-in and returning this one over it. I am interested why it is so bad for others, though.
Click to expand...
Click to collapse
HOLY **** I would love to have this battery life. I'm literally not doing anything with the phone and just loosing so much. I'm pretty much the opposite of a power user, so my phone is in standby most of the time and loosing so much is pretty frustrating.
EDIT: I might have an idea why it's so bad for me, I don't really have reception in my apartment (as you can see on my screenshots), so I assume it's constantly trying to get better receptions, I see 2 bars sometimes, but most of the time 0. I'll keep my phone at the window where I have reception for the rest of the day and see if it makes a difference. (Although the OnePlus has also bad reception, but does have a different carriers SIM card)
M4-NOOB said:
Yeah I do have 57 apps there already
I just removed 85 apps/services via adb, let's see how it is tonight and I'll report back tomorrow
Click to expand...
Click to collapse
Dependencies, dependencies, dependencies... some of those apks just sit there unless needed.
Do not disable apks/services unless you know what they do and what, if any, their dependencies are. Go too far and you'll end up in a boot loop.
What works for others probably isn't ideal for you.
Package Disabler is a better option as you easily toggle apks on/off as needed.
Screen off the serial offenders tend to be Google backup Transport, Framework and any cloud apps.
Try disabling Google play Services at night and see if that helps. You may need to disable Find my Device first as System Administrator if disable is greyed out.
Disabling play services also kills Gmaps and Playstore which are know hogs. Gmail as well to a lesser extent.
Google Firebase, do you need it? If not disable.
Carrier, Google, Samsung and app feedback, disable.
Using power management can cause erratic behavior and not solve the problem. Treat each power hog on a case by case basis instead. It takes a lot longer but yields a cleaner, more stable setup.
Play with it, go through -all- the settings. It's actually quit fun to explore and almost impossible to crash and burn.
Try this trick to stop ads globally: