I can't find any information in non-software-dev context. It's often high on my kernel wakelock list in better battery stats, so I'd like to understand what it is to see if maybe it's contributing to battery drain problems for me.
I don't see it listed when I search in service disabler, either.
I believe it is Google's Cloud Services. Email, calendar and doc are a few that use this.
I have been watching that wake lock too. Somehow the wake lock time seems to increase while the phone is used but not during sleep, according to BBS.
But let me know if you figure out a way to get rid of it.
Jon8RFC said:
I can't find any information in non-software-dev context. It's often high on my kernel wakelock list in better battery stats, so I'd like to understand what it is to see if maybe it's contributing to battery drain problems for me.
I don't see it listed when I search in service disabler, either.
Click to expand...
Click to collapse
Have you tried blocking it and observed if there is any negative side effects or not?
Jon8RFC said:
I can't find any information in non-software-dev context. It's often high on my kernel wakelock list in better battery stats, so I'd like to understand what it is to see if maybe it's contributing to battery drain problems for me.
I don't see it listed when I search in service disabler, either.
Click to expand...
Click to collapse
That´s from the sensor-hub driver.
aoc_channel_dev.c - kernel/google-modules/aoc - Git at Google
It doesn´t have any relation to drain. Without the wakelock, that driver wouldn´t work properly.
As @dr.wtf already mentioned it happens mostly during screen-on state anyway.
Freak07 said:
That´s from the sensor-hub driver.
aoc_channel_dev.c - kernel/google-modules/aoc - Git at Google
It doesn´t have any relation to drain. Without the wakelock, that driver wouldn´t work properly.
As @dr.wtf already mentioned it happens mostly during screen-on state anyway.
Click to expand...
Click to collapse
Do you have any information on the s5100_wake_lock kernel wakelock as well?
Not_Purgatory said:
Do you have any information on the s5100_wake_lock kernel wakelock as well?
Click to expand...
Click to collapse
that´s from a driver connected to modem.
drivers/soc/google/cpif/modem_ctrl_s5100.c - kernel/gs - Git at Google
Freak07 said:
that´s from a driver connected to modem.
drivers/soc/google/cpif/modem_ctrl_s5100.c - kernel/gs - Git at Google
Click to expand...
Click to collapse
So either this one or the usf wakelock isn't something to worry about?
Not_Purgatory said:
Have you tried blocking it and observed if there is any negative side effects or not?
Click to expand...
Click to collapse
Have not. In my limited experience, I don't know how to since it wasn't a service listed in the service disabler app.
Freak07 said:
That´s from the sensor-hub driver.
aoc_channel_dev.c - kernel/google-modules/aoc - Git at Google
It doesn´t have any relation to drain. Without the wakelock, that driver wouldn´t work properly.
As @dr.wtf already mentioned it happens mostly during screen-on state anyway.
Click to expand...
Click to collapse
Thank you so much. For a couple of weeks I've hoped to find info. All I found was source code like that, but didn't know what to make of it or how to interpret its role. Now I can disregard it. Thank you!
Not_Purgatory said:
So either this one or the usf wakelock isn't something to worry about?
Click to expand...
Click to collapse
no generally kernel wakelocks are nothing to worry about.
except when they run for 100% of the time, completely blocking deep sleep, which is very rare.
They´re necessary for the device to function correctly. Screen wants to stay on, needs a wakelock, wifi needs to receive some data, needs a wakelock, bluetooth connection needs to send/receive packages, needs a wakelock and so on.
Blocking (random) kernel wakelocks, can introduce very nasty and random issues.
Freak07 said:
no generally kernel wakelocks are nothing to worry about.
except when they run for 100% of the time, completely blocking deep sleep, which is very rare.
They´re necessary for the device to function correctly. Screen wants to stay on, needs a wakelock, wifi needs to receive some data, needs a wakelock, bluetooth connection needs to send/receive packages, needs a wakelock and so on.
Blocking (random) kernel wakelocks, can introduce very nasty and random issues.
Click to expand...
Click to collapse
Just wanted to have your input / opinion on this, specially when people seemed to be worried about if the mentioned KWL's had any impact on the battery life on their Pixel 7 (Pro) units.
For me personally - this whole kernel related topic is a interesting subject, considering that I have been on and off (with a break between 2020 til' about 1-1,5 week ago for giving Apple and iOS a chance) on Android since 2011 when (the now buried) Sony Ericsson joint venture released their goodbye line-up with the Xperia Arc & Co devices.
I still remember all the good stuff that was made for the P2(XL) series "back in the days" - kernels, ROMS, mods and scripts of all kinds, specially because I made myself the old (but defunct) BlackenedMod stuff for Wahoo.
Yes, it's me - xFirefly93 - if you remember that name?
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.
So i got installing all the battery saver apps, greenify etc... they all close apps and not much else, my version comes from the mind of an electronics engineer view point...
hardware drains power NOT some little app running in the background! (Purely software programmer logic... )
So my app grabs what states wifi/gps/bt/modem at the time the screen goes off...
When the screen comes on, it re enables them! Eg go bed with 95% wake up with 94% put in your pocket it just does it...
The 2nd feature is the lost/stolen phone feature while the app itself can not get your gps data (no permissions for it) it can switch gps on/off...
So you send "on" without the surrounding quotes, the app will then switch on gps/wifi/modem/bt... it then disables itself
Now you can use wheres my droid or any other location finding app to easily pinpoint your lost or stolen phone (try getting a location with gps/agps/data disabled which people often do to save power!)
(Includes option to keep wifi/gps untouched from the app)
as for ads!... the ui has 1 ad, no popups or notifications ... and when activated the activity with the ad on is destroyed and can't touch battery life ... at all
Craig's Root Battery Saver!
https://play.google.com/store/apps/details?id=saver.battery.craigs.craigsbatterysaver
Well done
Holy crap! Someone replied (first for me here lol)
Thanks!
To be honest, your app is great when it comes to save battery, but in my opinion your approach is plain wrong in terms of the main purpose of a smartphone - receiving notifications in a timely manner, not when you turn on the screen manually. The same purpose can be achieved by using DS Battery Saver, which will in addition turn on mobile data once per specific time interval to receive push notifications.
And you should reconsider your opinion about "software does not drain battery but hardware does". Check this great thread for example. I am using a combination of different apps (Greenify, Amplify, Power Nap) to tame aggressive services/alarms/wakelocks and I am able to achieve a battery drain close to 0.0% per hour while screen is turned off with WiFi, mobile data and location turned on the whole time without losing instant notifications.
The app supports wake up notifications (well, will... the app's not quite finished yet, been too busy to get everything finished)
If you had gone to the playstore you'd have seen
Also you might want to reconsider what i said..... hardware drains it not software!
You refer to wake locks ... well believe it or not, wake locks turn on hardware which drains the battery, i program microcontrollers with the esp8266 / bluetooth / compass / etc ...
Software can only drain the battery if it's purposely trying to max out the cpu, and if it did you'd know it's malware... there are wakelock detectors too
Craig Capel said:
The app supports wake up notifications (well, will... the app's not quite finished yet, been too busy to get everything finished)
If you had gone to the playstore you'd have seen
Click to expand...
Click to collapse
I came across this, therefore my reference to DS Battery Saver, that already is capable of exact those things. Nevertheless, your app is doing what it was designed for - saving battery (and this is pretty good, indeed).
Craig Capel said:
Also you might want to reconsider what i said..... hardware drains it not software!
You refer to wake locks ... well believe it or not, wake locks turn on hardware which drains the battery, i program microcontrollers with the esp8266 / bluetooth / compass / etc ...
Software can only drain the battery if it's purposely trying to max out the cpu, and if it did you'd know it's malware... there are wakelock detectors too
Click to expand...
Click to collapse
Well, I am familiar with what wakelocks are. But without software, that produces a wakelock, there would be no noticable drain, right? Thus we can go round and round here, I guess. From my point of view the most battery drain on an Android device is the result of poorly programmed software (which results in an unneccessary wakelock) and alarms waking up your device, not from ****ty hardware. You can hunt down those wakelocks/alarms by using apps like Better Battery Stats or Wakelock Detector and reduce them to a minimum without losing functionality. Therefore I consider this as a better approach.
But without software, that produces a wakelock, there would be no noticable drain, right? Thus we can go round and round here, I guess. From my point of view the most battery drain on an Android device is the result of poorly programmed software
Click to expand...
Click to collapse
Unless the software drains it by intensive cpu work, anything else has to be hardware, if i power a gps module, talk to it via uart to enable/disable it... then it's hardware doing it not software..
Take Qualcomm, the newer cpus support an embedded DSP
https://gigaom.com/2014/12/12/5-things-to-expect-from-qualcomms-flagship-mobile-chip-in-2015/
Qualcomm*made that feature possible*in the Snapdragon 800*with its DSP, and they’re pushing hot words even farther. New devices will have the ability to passively listen, using only a small amount of power, for more than just the word “OK.” Qualcomm calls this feature Snapdragon Sense.
The first feature it will enable is a much faster Shazam search. So if you find yourself too slow on the draw when trying to identify unfamiliar music, you’ll love this: When you boot up Shazam, it’ll already have been listening just a little bit, so it can identify the song in a few seconds.
Click to expand...
Click to collapse
As hardware gets smaller and uses less power, then things like the embedded dsp chip will allow you to use wakelocks without little drainage, but were no where near that yet...
think of it like this... software simply carries instructions which can turn on hardware via a field effect transistor, that binary 1 value shows up as 3v logic and the fet begins to conduct between the drain and source, this sets a flip flop and the hardware starts wasting power...
Or to put it another way after the software enables the hardware via a gpio the software stops, or better still, show me software draining the battery with all hardware services disabled... it can't
Good
Does it really work ..
Don't you believe the title? (Really works!)
Craig Capel said:
As hardware gets smaller and uses less power, then things like the embedded dsp chip will allow you to use wakelocks without little drainage, but were no where near that yet...
Click to expand...
Click to collapse
True words. I can also see your other points and do agree with them. But as you said, we are not even close to a system where wakelocks do not drain as much as they currently do. Would we have such a system, your app wouldn't be required, I guess. Therefore taming the unneccessary wakelocks is a good way to achieve a great battery life without losing functionality for the moment.
Awesome
Awesome!!!
Can't open the settings and this sound makes me rly angry lol. Why it makes this sound? (even my phone is silence)
Gesendet von meinem ONE A2001 mit Tapatalk
There are no settings... work in progress (says so in the play store readme)
I've had the flu for the past week so i've not been developing much... expect updates shortly to remove the "settings" option which annoyingly is placed there by default... i never put it there
The sound is cool no? ... it plays a low volume sound to indicate the app is working!
Alright, update includes support for android 4.1 for gps now... i'm slowly working my way through android oddities and different techniques to switch hardware / on and off and with 5 phones to use 4 of them use kitkat!
Had to stop for a break i've had the flu all week, throwing up constantly, later on i'll add the finishing touches to wake up notifications as right now it's extreme power saving mode...
Stay tuned.... oh and i found a bug supporting lollipop, fixed that too, so if you have lollipop and it never worked, it should now ...
Antibiotics did the trick! It was sadly not the flu but some rare bug...
I've almost finished the autowakeup every x minutes 5, 10, 20 min intervals..
Unless someone here can think up a value or maybe add it as an option.
.
I removed the blocking side of things prior i used a thread/sleep now i use a timer event this stops the lag when unlocking the device on older models...
nive work :good:
I dumped the smart check (as far as i can tell anroid never fails, so i removed it)
It should now be seamless between lock screen and the main screen without any more lock up due to the threading...
Enjoy!
great!! will try it. thanks!
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.
Insanely high alarms by "com.google.android.location.ALARM_WAKEUP_ACTIVITY _DETECTION"
Hi there, I've been using OOS 9.0.2 and I got some excessive wakelocks by *walarm*:com.google.android.location.ALARM_WAKEUP_ACTIVITY_DETECTION which happens about every 60 seconds. I'm not sure if this is normal or what the culprit could be as the location services are deactivated all the time, yet it occurs. Any idea what it could be? Can it be related to Android Wear?
UPDATE: It appears that Sleep as Android is causing it even when not using the app. I've contacted them now. For me the options are using Greenify during the day for the app, uninstalling it or ignoring it for now.
Macusercom said:
UPDATE: It appears that Sleep as Android is causing it even when not using the app. I've contacted them now. For me the options are using Greenify during the day for the app, uninstalling it or ignoring it for now.
Click to expand...
Click to collapse
How did you figure that one out? Just curious. Maybe the next person can use the same tools or methods
spartan268 said:
How did you figure that one out? Just curious. Maybe the next person can use the same tools or methods
Click to expand...
Click to collapse
I wish I could say I simply used a wakelock detector or something like that. I loaded my apps to a secondary device and disabled them one by one. I wasn't sure whether Greenify would prevent it but it did. So greenifying different apps and see if it changes was how I figured it out.
My battery consumption during standby went significantly down. Even though alarms are just the triggers and not the wakelocks, triggering the Network Location Provider every 60 seconds prevents the device from deep sleeping and was a main cause of the standby issues. I suggest to check it for yourself with BetterBatteryStats.
My ALARM_WAKEUP_ACTIVITY_DETECTION exceeded 1000 alarms by the end of the day. While I still get a few Android Wear wakelocks if my smartwatch is not connected. They make up at least 150 too. What I'm trying to say is that I don't say you should have no alarms anymore, but even 150 seem normal for Google Play Services. But over 500 or 1000 definitely isn't normal.
I don't that greenify is needed anymore hence we are on android 9.0 , DOZE does that work pretty good.
oksagi said:
I don't that greenify is needed anymore hence we are on android 9.0 , DOZE does that work pretty good.
Click to expand...
Click to collapse
That's my point. Even with light doze active apps still have a maintenance window and Sleep as Android seems to have permanently used sensors via Play Services. Once greenified it stops using it completely and I went from 1.2%/h idle drain to under 0.7%/h or less. I'm just trying to help people who have the same issue as I do. If no app seems to use any sensor, location etc. you don't need Greenify of course. But it can help with some apps.
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: