I know this topic has been beaten to death already but there are so many conflicting posts online without a clear solution. Google maps is creating a lot of wakelocks throughout the day even when the phone is idle. I have all the possible settings off, the only thing I have on is Google location services under settings>location settings. As soon as I turn this setting off, the wakelocks go away and the standby battery is much better. Is there a real fix for this or have ppl just accepted this? I can't believe poor programming like this is coming from Google of all tech companies. Btw, I'm running stock 4.1.1.
jknolls said:
I know this topic has been beaten to death already but there are so many conflicting posts online without a clear solution. Google maps is creating a lot of wakelocks throughout the day even when the phone is idle. I have all the possible settings off, the only thing I have on is Google location services under settings>location settings. As soon as I turn this setting off, the wakelocks go away and the standby battery is much better. Is there a real fix for this or have ppl just accepted this? I can't believe poor programming like this is coming from Google of all tech companies. Btw, I'm running stock 4.1.1.
Click to expand...
Click to collapse
With Location Services activated, it's doing exactly what your allowing. You're giving permission for apps to connect to Google's location services. A lot of apps that don't seem location based are actually doing background processes that are -- thus the wakelocks. And GPS/Location services are battery expensive.
My solution: I use Cyanogenmod that has widgets in the notification panel. When I press and hold the GPS Icon it brings me to the Location Services page. I will toggle the services when I actually need it, and allow for no wakelocks. Press the back button and you're back in action.
What worked for me is just turning off Google Now. Yeah you lose some functionality, but it doubles your battery life. Google really screwed up with this one. I really don't know who to blame, Google, Samsung, or Verizon. I dont get these wakelocks on my Nexus with the same app, so it might be something to do with what Samsung did with TW. No wakelocks on 4.2 either.
aooga said:
What worked for me is just turning off Google Now. Yeah you lose some functionality, but it doubles your battery life. Google really screwed up with this one. I really don't know who to blame, Google, Samsung, or Verizon. I dont get these wakelocks on my Nexus with the same app, so it might be something to do with what Samsung did with TW. No wakelocks on 4.2 either.
Click to expand...
Click to collapse
I've always had Google now off but the battery life still suffers considerably even with it off and just Google location services on.
jknolls said:
I've always had Google now off but the battery life still suffers considerably even with it off and just Google location services on.
Click to expand...
Click to collapse
Really? For me it helps on TW roms.
aooga said:
Really? For me it helps on TW roms.
Click to expand...
Click to collapse
Sure, Google now being off definitely helps but location services still chews up battery.
jknolls said:
I know this topic has been beaten to death already but there are so many conflicting posts online without a clear solution. Google maps is creating a lot of wakelocks throughout the day even when the phone is idle. I have all the possible settings off, the only thing I have on is Google location services under settings>location settings. As soon as I turn this setting off, the wakelocks go away and the standby battery is much better. Is there a real fix for this or have ppl just accepted this? I can't believe poor programming like this is coming from Google of all tech companies. Btw, I'm running stock 4.1.1.
Click to expand...
Click to collapse
did you installed 4.2 or note camera, I used to have same problem but after uninstalling it becomes fine. Note camera have a google framework apk inside and I think the incompatibility causing the problem.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Related
I have searched believe me, and I have found some useful threads, articles, etc... But nothing that fixes it. If you look at the screenshots you can see a couple things:
In the 4+ hours I tested:
1.) Youtube took up 26% of my battery
2.) Maps woke my device 60 times!
The weird thing is i never opened either of those apps today.
Did a factory reset yesterday after noticing massive "awake" issues. Still having awake issues today.
Does anyone else have some useful tips, tricks, etc...?
v2.2v said:
I have searched believe me, and I have found some useful threads, articles, etc... But nothing that fixes it. If you look at the screenshots you can see a couple things:
In the 4+ hours I tested:
1.) Youtube took up 26% of my battery
2.) Maps woke my device 60 times!
The weird thing is i never opened either of those apps today.
Did a factory reset yesterday after noticing massive "awake" issues. Still having awake issues today.
Does anyone else have some useful tips, tricks, etc...?
Click to expand...
Click to collapse
If you're rooted, use Autorun Manager, or something similar, to kill unwanted running receivers. I don't have YouTube on my Maxx HD, but Maps (and numerous other apps) runs a bunch of stuff that I don't use that I kill off. Having said that, the battery management on my Maxx HD is so insane, that I'm not sure it matters...coming from a Galaxy Nexus.
tbcpn said:
If you're rooted, use Autorun Manager, or something similar, to kill unwanted running receivers. I don't have YouTube on my Maxx HD, but Maps (and numerous other apps) runs a bunch of stuff that I don't use that I kill off. Having said that, the battery management on my Maxx HD is so insane, that I'm not sure it matters...coming from a Galaxy Nexus.
Click to expand...
Click to collapse
not rooted...also coming from a nexus and when researching on rooting/development on moto devices my mind exploded lol i cant believe how much moto/verizon hates rooters. but anyway i still get good battery life on my maxx hd but i feel it could be alot better if it werent showing my phone is CONSTANTLY "awake". Starting to piss me off actually. BTW after the entire day now my youtube wake issue has seemed to disappear...but "google services" is at the top of my list of things keeping my device awake (and by A LOT) if i uninstall google services then i am unable to use youtube. Getting pissed! lol
If you're not using youtube, I'm not sure why it's showing up.
As far as maps goes, if you're using Google Now, it's gong to want to track your location. If you're not using Google Now, I know that Android 4.1.1 has issues with maps waking up the phone way too much. Even with Google Now location settings turned off, maps seems to want to wake up the phone every few minutes. My theory is that Google did this intentionally to collect location data to improve Google Now. It was fixed in Android 4.1.2. If you disable Maps, you'll probably see you screen on time and awake time closely match.
The good news is that even though maps is causing a lot of wakeups, it really doesn't drain the battery much. When I disabled Maps, I only got an extra 2% - 5% of battery life.
Are you rooted and use nova ? If yes delete the default launcher... you save 3% batttery
Sent from my XT925 using xda premium
Open Google maps and go to settings. There you can turn off the location tracking.
Sent from my DROID RAZR HD using xda app-developers app
Hey guys,
I had the issue with the 40% battery burn overnight again. According to WLD, the CPU was awake for 96% of the ~11 hours since it was charged (which explains it). I want to make sure I'm reading these right, so I've posted screens of wakeup triggers and CPU wakelocks.
I've got Google Now turned on, the "OK Google" keyword detection turned off, location reporting on, location history on, and location services set to high accuracy (I use navigation and what not and would prefer to not have to toggle it constantly). Please see the attached screenshots.
Some googling of my own told me it's location reporting keeping it awake, which I'm afraid is the case, as I didn't have this issue for a while when it was off (it's also been on for several days and I haven't had this issue).
So, I have two questions in total. Is it Google Now's location usage that's draining my battery and keeping my phone awake? Also, since this isn't an every night issue, do you have any suggestions or recommendations to solve it without losing Gnow functionality?
I am running Carbon (July 1st nightly) and the Franco Kernel r55. Thank you very much in advance, this issue has alluded me and annoyed me for months.
Update: upon further research, I'm seeing that blocking wakelocks from Google Search / Google Now related location services will eliminate the problem without affecting Gnow functionality - is there any truth to this? I've also seen people claim to have disabled location reporting without loosing their weather, nearby events, etc. I worry that disabling the wakelock will impede functionality because I don't have the screen on often while traveling. I just can't seem to get a straight answer!
Update 2: after a phone call to Google (yes, they actually gave me a good answer), I was told that Location Reporting *only* tracks where you've been to give you travel time and similar things. Turning it off doesn't disable weather, nearby events, parking location, and so on, so it's looking like just disabling it is a good place to start.
turbofandude said:
Hey guys,
I had the issue with the 40% battery burn overnight again. According to WLD, the CPU was awake for 96% of the ~11 hours since it was charged (which explains it). I want to make sure I'm reading these right, so I've posted screens of wakeup triggers and CPU wakelocks.
I've got Google Now turned on, the "OK Google" keyword detection turned off, location reporting on, location history on, and location services set to high accuracy (I use navigation and what not and would prefer to not have to toggle it constantly). Please see the attached screenshots.
Some googling of my own told me it's location reporting keeping it awake, which I'm afraid is the case, as I didn't have this issue for a while when it was off (it's also been on for several days and I haven't had this issue).
So, I have two questions in total. Is it Google Now's location usage that's draining my battery and keeping my phone awake? Also, since this isn't an every night issue, do you have any suggestions or recommendations to solve it without losing Gnow functionality?
I am running Carbon (July 1st nightly) and the Franco Kernel r55. Thank you very much in advance, this issue has alluded me and annoyed me for months.
Update: upon further research, I'm seeing that blocking wakelocks from Google Search / Google Now related location services will eliminate the problem without affecting Gnow functionality - is there any truth to this? I've also seen people claim to have disabled location reporting without loosing their weather, nearby events, etc. I worry that disabling the wakelock will impede functionality because I don't have the screen on often while traveling. I just can't seem to get a straight answer!
Update 2: after a phone call to Google (yes, they actually gave me a good answer), I was told that Location Reporting *only* tracks where you've been to give you travel time and similar things. Turning it off doesn't disable weather, nearby events, parking location, and so on, so it's looking like just disabling it is a good place to start.
Click to expand...
Click to collapse
The data we need to see isn't shown in your screenshots. This is why I prefer BBS. You can just post a log and nothing will be missing.
Aerowinder said:
The data we need to see isn't shown in your screenshots. This is why I prefer BBS. You can just post a log and nothing will be missing.
Click to expand...
Click to collapse
Ugh, I knew I should have left it. I've got it installed now and will post a screenshot if it happens again. I've got Location Reporting turned off. I want to see if it will still give me the features I want, and if the battery drain issue stops, yippee. I will leave BBS there, however, in case it happens again.
turbofandude said:
Ugh, I knew I should have left it. I've got it installed now and will post a screenshot if it happens again. I've got Location Reporting turned off. I want to see if it will still give me the features I want, and if the battery drain issue stops, yippee. I will leave BBS there, however, in case it happens again.
Click to expand...
Click to collapse
All of the wakelocks that start with Nlp are due to location. Switching the location mode to Device only will stop them. Anything that relies on GPS still works fine. This should be the default setting.
I did a factory restore of the phone, latest Gapps, Carbon rom (07/07 nightly + 07/06 firmware), latest ElementalX Kernel now (so far, better temp/performance + equal or better battery). I know it's only an hour's worth of use, but a problem is pretty apparent.
Location reporting/history is off, Gnow is enabled, keyword detection is off. WiFi is on, and location services are in high accuracy mode. Why is a wakelock created by never released and how do I avoid that?
Is there any reliable setting I can use to avoid a random software issue eating up my battery? This inconsistency is driving me insane.
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.
Apologies if this issue has been covered before but the searches I made displayed quite outdated topics and spoke about things I didn't understand at all or relate to with my Nexus 5. Basically I am having an issue when using Google Maps. Everything functions as normal however when I start navigation, it doesn't continually follow me as I'm driving nor does it reroute if I miss the turn it tells me to take or take one earlier. By that I mean it will work for a few minutes, then be in a pause-like state, then continue again, then pause, etc. Does this have something to do with my Location mode by any chance?
I have been looking up ways to improve battery usage so have the mode set at 'Device only'. Should I be selecting 'High accuracy' instead and disabling location services when I'm not using it to benefit the battery or is there another nifty way to kill two birds with one stone here?
I am using a Nexus 5 with Android version 5.0.1. Cheers guys.
Tilduh said:
Apologies if this issues has been covered before but the searches I made displayed quite outdated topics and spoke about things I didn't understand at all or relate to with my Nexus 5. Basically I am having an issue when using Google Maps. Everything functions as normal however when I start navigation, it doesn't continually follow me as I'm driving nor does it reroute if I miss the turn it tells me to take or take one earlier. By that I mean it will work for a few minutes, then be in a pause-like state, then continue again, then pause, etc. Does this have something to do with my Location mode by any chance?
I have been looking up ways to improve battery usage so have the mode set at 'Device only'. Should I be selecting 'High accuracy' instead and disabling location services when I'm not using it to benefit the battery or is there another nifty way to kill two birds with one stone here?
I am using a Nexus 5 with Android version 5.0.1. Cheers guys.
Click to expand...
Click to collapse
Other people are having this issue, too. And I believe it's also happening on Waze. It's a Lollipop problem.
Well that is a major let down. I tend to use Google Maps quite regularly and have never had an issue with it on the iPhone 5s, so what you're saying about it being an issue on Lollipop could possibly be the cause. Is there any announcements or blog posts regarding it from Google?
Hmm I don't have any issues like this using maps on 5.0.2
Sent from my SHIELD Tablet using Tapatalk
Tilduh said:
Apologies if this issues has been covered before but the searches I made displayed quite outdated topics and spoke about things I didn't understand at all or relate to with my Nexus 5. Basically I am having an issue when using Google Maps. Everything functions as normal however when I start navigation, it doesn't continually follow me as I'm driving nor does it reroute if I miss the turn it tells me to take or take one earlier. By that I mean it will work for a few minutes, then be in a pause-like state, then continue again, then pause, etc. Does this have something to do with my Location mode by any chance?
I have been looking up ways to improve battery usage so have the mode set at 'Device only'. Should I be selecting 'High accuracy' instead and disabling location services when I'm not using it to benefit the battery or is there another nifty way to kill two birds with one stone here?
I am using a Nexus 5 with Android version 5.0.1. Cheers guys.
Click to expand...
Click to collapse
You haven't even tried High Accuracy? It's recommended for turn by turn navigation and certainly something I would try before making threads.
If you want to save battery simply turn off locations when you don't need it and enable it when you do. You'll save much more than continually being in Device Only mode and potentially more accurate navigation as well.
Before registering to this forum I left my location mode on 'Device only' and enabled all the time to conserve more battery than leaving it on on the 'High accuracy' setting. After reading a few topics on this forum I now know that location sucks up a lot of battery, therefore location will be toggled when I need it.
I'll give it a go and see whether there is any significant improvement. I've never had any issue/s whatsoever with the Google Maps app on my iPhone 5s as explained.
ldubs said:
Hmm I don't have any issues like this using maps on 5.0.2
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
I'm on Android 5.0.1. When I check for the latest update it says my system already is up to date. My Google Maps app is also up to date.
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: