Hi
I'm on a stock Samsung Note 10+ 5G. I normally disable unused apps with Tasker and only load them as I need them, my primary aim to reduce battery drain. I wanted to see how good Android 12 was at controlling apps battery usage so I've enable all my apps, and put them into the following states:
Mobile Data - I've turned "Allow background data usage" to OFF
Under the battery section, each app is Restricted
I've removed from "Optimise battery usage" section, so they are being battery optimised
Under Developer Options, Standby Apps, I have put each app into Restricted mode
Most apps are behaving fine, but I'm getting quite a few apps over time using battery. When I check under GSAM, all of them have the same wakelock which is Google_C2DM. The apps typically are not active (i.e. when I check in the app manager, "Force Stop" is greyed out) and they are listed as "Manually Disabled". I've tried killing the apps, clearing cache on the apps and the phone, restarting etc but cannot get them to entirely stop battery usage. Is there a solution for this and any idea why its the same Google_C2DM wakelock?
thanks
I myself am investigating YouTube app battery usage and that component is also listed at the top in GSAM.
Related
Been trying to squeeze out some battery life on my S4 running goldfinger kitkat ROM. No matter what I do, I seem to get a bunch of wakelocks, radio/wifi turning on, etc. What I would like is to be able to totally disable everything when the screen is off (with the exception of incoming calls/texts) and then sync when I wake the device up. I'd also like to have a whitelist for apps like slacker/pandora/music. I've tried wakelock detector, greenify, and DS battery saver (these are the ones I've found most useful). Of the three, DS battery saver seems to be the best at shutting everything down, but doesn't have a whitelist feature, and requires a reboot to toggle. Greenify and wakelock detector require you to know which apps are waking your device. This is OK for the big culprits on my device (FB, google play, exchange services), but I still get random wifi/gps/other wakeups. This is likely just the result of having a bunch of apps that want to phone home, even if each of them does it rarely. Again, it would be nice if they could all do it at once. Any solutions?
you can use greenify, it can turn off apps when your phone is off.
Please let me know if you find such app. For now I'm using Greenify, Wakelock Detector and for some time a new Xposed module: Unbounce.
A little more experimenting. Seems that DS battery saver is the best for what I want, which is a sleeping phone except when I'm using it. All the other apps require that I put a certain app to sleep, rather than have everything asleep by default. My phone then gets random wakes, even though there isn't any one single misbehaving app that I can find. DS saver can be turned off temporarily through the notification bar for when I'm using music services in the background without rebooting. Using DS battery saver on "aggressive", I average about 0.6% drop/hour, with 3 minutes awake time/hour. I think that's OK, but not sure if I can do better (like no awake time/hour). I'm wondering if the awake time is just due to cellular traffic. Hmm, maybe I'll see what it looks like in airplane mode.
Hi everyone,
I recently noticed heavy battery drain from the Android OS process. At the end of the day it consumes up to 25% of the whole power while the display-on time was about 1h total.
Since I am using CM11 I have tried disabling some Permissions in the secutity settings. I currently disabled the "Keep awake" and "Wake up" options for the Android System. I also tried disabling "Location" for Android System as well as "Wifi scan" for the LocationServices process. None of these options seemed to help.
Currently I went back to allowing access to the Location to Android System as well as LocationServices however i still experience the battery drain. When opening up App Ops I notice that the Andoid System process is constantly running the "monitor location" command. Also second in the list is always LocationServices with a recent wifi-scan activity which seems to run every five minutes. However like I already mentioned above simply denying access to the location for the Android System does not solve the problem at all.
Is there anyone who could point out an idea of what else could be causing the drain?
Thanks a lot!
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.
Hi guys
I'm a BlackBerry user of ten years and have recently moved over to Android (with some regret).
I know Android is great for customising, so my quest now is to find out how to control individual apps from running too much data - I know of the "Restrict Background Data" option, but is there a way to be more granular and control which apps use data on Wi-Fi and on Mobile Data?
And on that, to reduce battery consumption, is there a way to control the interval frequency with which apps synchronise? For example, Sunrise, Gmail, Inbox, Google Keep - if they're all polling and synchronising regularly, I'm sure that uses up my data and my battery a lot faster. Is there a way to tell them "only poll manually" etc.?
Hi, you can go to settings>battery turn on the battery saver and see what apps or features consumes the most of your battery, analyse them and take action according to that by removing, synchronizing or stop particular apps.
Most of you will be aware that a new "app optimization" feature was added to a recent 5.1.1 based firmware update.
I've been trying to research exactly what this does because Samsung have not updated their user manual (you can access this via the user manual widget) to cover this new feature. After searching online, I've come to the conclusion that I'm not the only one who isn't sure what this feature does and there's a lot of incorrect information out there.
Below is some examples of what I've read:
It's Samsung's implementation of doze - I think this is incorrect as doze is a system wide state that uses sensors and screen off information.
Someone on AC forums was told by a Samsung employee that for example, it will make taxing games black and white so they don't require so much processing power - I really don't think this is the case.
It's Samsung's implementation of app standby - I think this is the most likely.
Does anyone have any concrete evidence as to what this setting actually does?
Furthermore, I've noticed that the "app optimization" implementation will change depending on if you have Smart Manager enabled or disabled. Not only that, but the battery sub menu layout (settings > battery) is also different depending on Smart Manager running or not. Has anyone else noticed this?
From what I can gather, the "app optimization" feature is there regardless if Smart Manager is enabled or disabled, but you can only manually select wether an app is optimised or not. Smart Manager appears to only provide automation of the process by monitoring which apps have not been used for x number of days and then changing the optimisation setting for each app for you.
Based on your screenshots, system apps can now be optimized by default?
Tricks25 said:
Based on your screenshots, system apps can now be optimized by default?
Click to expand...
Click to collapse
Second screen is the 'Optimization Screen' under Setttings > Battery > Battery Usage > Battery Optimization. First one is from the 5.1.1 update, and the second is only present in Marshmallow Beta.
I don't think it's exactly an App Standby, as this keeps the apps 'unoptimized' if they have background services. Samsung's optimization only takes days since last usage for determining if an app should be optimized. Also, I think Samsung's optimization is more aggressive, like Greenify, an it shuts down apps shortly after user lefts them.
Oh, and it seems that you can't explicitly turn App Standby for an app, like you can do it with the Samsung alternative. Putting an app on/off on App Standby only activates App Standby for that app (If conditions are met) or disables it completely.
bregan90 said:
Second screen is the 'Optimization Screen' under Setttings > Battery > Battery Usage > Battery Optimization. First one is from the 5.1.1 update, and the second is only present in Marshmallow Beta.
I don't think it's exactly an App Standby, as this keeps the apps 'unoptimized' if they have background services. Samsung's optimization only takes days since last usage for determining if an app should be optimized. Also, I think Samsung's optimization is more aggressive, like Greenify, an it shuts down apps shortly after user lefts them.
Oh, and it seems that you can't explicitly turn App Standby for an app, like you can do it with the Samsung alternative. Putting an app on/off on App Standby only activates App Standby for that app (If conditions are met) or disables it completely.
Click to expand...
Click to collapse
You're not quite correct on the screen shot front. All screenshots were taken from Android 6.0, the reason they're different is one was taken with Smart Manager running and the other was taken with Smart Manager disabled via Package Disabler.
What it does is that after an app has not been started for 3 days (this is configrable), it freezes (disables) it.
This is really problematic for small apps acting as unlocker of a main app and not supposed to be launched by user, as it prevents the main app to communicate with the unlocker app (bindServices() fails), preventing license verification to work.
This cancer acting in the back of apps used to only be possible on root devices, but Samsung generalized to mainstream devices.