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!
Related
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.
I've been having severe issues with battery drain both before and after a factory reset, using a completely stock setup. The system app consistently waking the device was NlpCollectorWakeLock - no real news there. However, I managed to fix it with a slightly strange change.
I don't want to disable location services, but I've no interest in location history (which is disabled). However, when I went into the setting (Settings: Location >> Google Location History) there was a message at the top saying "Could not detect current setting" - although the box was unchecked. Checking and unchecking the box both removed this message and has stopped my Note 3's battery drain.
Presumably, because this setting is stored on Google's servers, this would explain how the issue could survive a factory reset. I'm also assuming that whatever this error was was causing constant wakeups.
Though I would share on the off chance it could help somebody else with this issue.
Try amplify (exposed) it limits the Wakelocks... And you don't need to disable features
Hi everyone,
I have a Google Nexus 5, that has never been rooted.
Nearly each time my phone is running out of battery (meaning nearly every day because I am using Waze, a GPS app, quite often), when Android is starting a message saying "Optimizing 1 of x.. apps" and this take a lot of time (sometimes more than 10 minutes).
Do you know what is causing this issue and how to solve it?
It happens since I upgraded to a previous version of Android but I don't remember which one as is it not the latest one.
Now, my phone is running Android 5.1.1 build LMY48M.
Thanks a lot.
Can't solve your problem, but I will add some information and a test suggestion:
I have a Nexus 7 (2013) Tablet which was recently updated to Lollipop 5.1.1.
Not surprisingly, right after the update, the tablet went through the exact same app optimization process (no surprise there).
Although the tablet was charged and in 'Sleep Mode' last night, I woke up this morning to find the tablet powered off (which I considered strange).
Upon powering it back on, it went through the same app optimization process that you have described.
I considered the possibility that a software update had been applied to the tablet last night which did not require my permission (but that seems unlikely).
Then I wondered if the battery had somehow become depleted and that the app optimization process was a function of the power loss and subsequent restart.
In the Windows environment, an 'ungraceful' shutdown leads to a boot option to start the computer in 'Safe Mode'.
And I had considered the possibility that one or more Android processes or 3rd party apps might have triggered the requirement for app optimization upon restart.
This is what led me to your post.
However, I have now let the battery drain two times, with two subsequent restarts -- and I am not getting the app optimization.
So, I'm not sure what the trigger is -- but I have a suggestion for a test:
Restart your device so it is fresh
Do not start any applications or Android processes (other than those that start themselves)
Leave the device on so that the battery fully drains (you might want to accelerate the process by maximizing the screen brightness)
After the device shuts down due to battery loss -- charge it
Restart the device and see if app optimization happens
If it does not happen -- them maybe your app optimization is related to an ungraceful shutdown of one or more Android processes or 3rd party apps
If it does happen -- then I don't know what's going on
However, we can't ignore the fact that your device is a phone and mine is a tablet
And, therefore, your device always has processes running that might represent an ungraceful shutdown upon battery depletion.
Of course, this does not answer the question relating to the problem I witnessed this morning
But maybe I had too many apps open and too many browser tabs open when my battery depleted (although I still don't know why my battery depleted)
And maybe that triggered my own app optimization
There is one more thing: yesterday, for the first time, I ran an app on the tablet called Slingbox Player
That's the only thing different that I have done on the tablet for many months
And the Slingbox Player was open in the background when I went to sleep
I suppose a badly coded app could have drained my battery
But that still leave the question regarding the app optimization requirement upon restart
Please share your findings.
Why do Android System, Android OS, & Bluetooth account for majority of battery drain?
On my old Galaxy S4, I found that the screen was almost always the highest battery drain -- and if I saw some app using close to or more than the screen, then I knew something was wrong. However, with my Galaxy S5 (running OptimalROM 13.1), I am consistently seeing Android System is the highest drain, followed by Android OS -- at times I'm getting only 10 to 12 hours of life, but other times I get over a day -- in both cases, it's the Android System and Android OS using the bulk of the power, never an app.
I also see some odd things like Bluetooth using nearly 10%, even though it isn't connected to any devices the entire day -- why would it use that much on standby?
I also see Google Services sometimes using over 10% -- I think that was while I had Google Maps in the background (not navigating).
Nerva said:
On my old Galaxy S4, I found that the screen was almost always the highest battery drain -- and if I saw some app using close to or more than the screen, then I knew something was wrong. However, with my Galaxy S5 (running OptimalROM 13.1), I am consistently seeing Android System is the highest drain, followed by Android OS -- at times I'm getting only 10 to 12 hours of life, but other times I get over a day -- in both cases, it's the Android System and Android OS using the bulk of the power, never an app.
I also see some odd things like Bluetooth using nearly 10%, even though it isn't connected to any devices the entire day -- why would it use that much on standby?
I also see Google Services sometimes using over 10% -- I think that was while I had Google Maps in the background (not navigating).
Click to expand...
Click to collapse
I believe that is the new normal. Unfortunately, "Andoid System" in our battery stats is nonspecific: that heading actually covers dozens of little apps and functions. With each successive generation, the phones try to have more features.
You can get a little better idea with GSam Battery Monitor: by clicking on the "Android System", it brings up another window showing you all of these processes. That doesn't mean you'll be able to do much about it, though.
I was able to solve one major problem with ridiculous battery drain by looking more closely: I have a lot of mp3s and pictures on my sdcard. Android system was scanning them, but Samsung indexing service was also scanning them for no useful purpose, and every time I rebooted it would start chewing on them again. I froze the samsung indexing service and the battery life improved by many hours per day.
Where do I disable the Samsung Indexing Service? I doubt it's causing problems, but it's useless to me.
Nerva said:
Where do I disable the Samsung Indexing Service? I doubt it's causing problems, but it's useless to me.
Click to expand...
Click to collapse
The safest way is to use Titanium Backup to "freeze" IndexService and, optionally, "S Finder". If you run into any issues, you can re-enable them easily by "defrosting" them.
Disabling them doesn't affect me at all because I use a file explorer to browse to my files directly.
OK, I installed GSam Battery Monitor a few weeks ago. Today I am dumbfounded by what my phone is doing -- after undocking it for just two hours and not using it at all, I notice it is hot in my pocket, so I pull it out and see the battery has already dropped to 78%. I check the list of open apps, and there's not much there -- my phone dialer, Camera, Chrome (with no pages open), and Messaging -- that's it.
I check the GSam battery usage, and it says the screen is using 2%, the cell radio 2%, the WiFi 1%, and the rest is "App Usage" -- I click on apps, and Kernel (Android OS) is using ~60%, Bluetooth is using 22%, and Android System is using ~10% -- so they combine for 90% of "App Usage". My Bluetooth is "on" but not connected to anything -- indeed, it is paired with only one device, which I have not even turned on in months -- the phone is getting all of its data via WiFi, which is only using 1%, yet the Bluetooth with nothing to do is using 22%!
What the hell is going on?
Nerva said:
OK, I installed GSam Battery Monitor a few weeks ago. Today I am dumbfounded by what my phone is doing -- after undocking it for just two hours and not using it at all, I notice it is hot in my pocket, so I pull it out and see the battery has already dropped to 78%. I check the list of open apps, and there's not much there -- my phone dialer, Camera, Chrome (with no pages open), and Messaging -- that's it.
I check the GSam battery usage, and it says the screen is using 2%, the cell radio 2%, the WiFi 1%, and the rest is "App Usage" -- I click on apps, and Kernel (Android OS) is using ~60%, Bluetooth is using 22%, and Android System is using ~10% -- so they combine for 90% of "App Usage". My Bluetooth is "on" but not connected to anything -- indeed, it is paired with only one device, which I have not even turned on in months -- the phone is getting all of its data via WiFi, which is only using 1%, yet the Bluetooth with nothing to do is using 22%!
What the hell is going on?
Click to expand...
Click to collapse
I know that sometimes it gets hung up if it encounters a corrupted media file while scanning for them, and that produces the symptoms you're describing. Scan your SDcard (it's fastest to do it on a computer, but there are many ways to accomplish this) for any files that are of size "0 kb" (that is, zero kb) and delete them. See if that resolves your issue.
Also try clearing cache and dalvik cache, just because that can alleviate strange problems for no discernable reason.
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.