Develop Bugs

[Q] "Android OS" and battery usage

Hello.
Sometimes my phone works normally about 25hours, sometimes it works twice shorter ~10 hours. I've analyzed battery usage and found out that only difference in Android OS process.
25 hours battery usage
Display - 60%
...
Android OS - 4%
10 hours battery usage
Android OS - 60%
Display - 15%
This definitely looks like a bug. OS should not use more than a display.
Is there any way to found out what is Android OS in details?
Why it takes to many power?
P.S. I guess that bug is triggered by programs like Google maps,
but can't definitely confirm it.

Is there a way to shut off maps till needed?

Get spare parts and you can check what is using what. It could also be useful to get watchdog or similar app to check if you have any apps gone crazy. It isn't unusual though that the screen usage is lower if you just haven't actually used the phone that much as the percentage is always 100% and is divided among the things that used the battery, thus the usage percent doesn't imply mA usage.
Sent from my Desire HD using XDA App

I have still pretty high "Android OS".
Display 31%
Android OS 21%
I've tryed Spare parts (Battery history), but it doesn't help.
It just doesn't display such name.
Is there any other way to find out whois is lurking
behind this mysterious title?

I'm betting you have a "suspend process" issue.
What does Battery history from spare parts say? Choose CPU usage, Since last unplugged. Is "suspend" close to the top? What CPU usage details does it have (if you select it)? Obviously look at this data at the end of your phone's battery life, before you plug in.

Also what rom are you using? With cm7 it seems that the battery stats are quite crazy and don't seem to add up to the actual usage, it's been discussed a bit in the nightly thread. The inaccurate stats don't explain the changes in actual battery drain though...

just to be sure, you have usb debugging enabled right?

I'm on official ROM (no root) with USB debugging enabled (I confirm init issue).
My last guess that "Android os" caused by "Location -> Wireless networks".
Now have ~2 days uptime without ever running "Google Maps" and with "Location -> Wireless networks" constantly unchecked.
P.S. Spare parts constantly eats about ~3% CPU at top. Too many for battery monitor. Removed it.

sergey1369 said:
P.S. Spare parts constantly eats about ~3% CPU at top. Too many for battery monitor. Removed it.
Click to expand...
Click to collapse
Hey, since you're worried about slight additional CPU-usage and overall performance, you really should consider S-OFFing and getting a different Radio and a custom ROM like ARHD. Or at the very least flash a new kernel, Buzz' kernel did wonders for me.

Battery Life - Idle drain?

I was wondering if anybody else had this issue or had any suggestions.
Battery life is normally great on the tablet, except every once and a while it gets stuck awake overnight. There doesn't seem to be a 3rd party app that is holding it awake, as Android system and OS is what's using most of the battery.
As you can see in the screenshot, Doze works fine and barely any better is drained, I used it briefly, came home from work and half the battery had been drained.
Thanks for the help

Not sure if it's normal but mine does the same.
Sent from my Nexus 6 using Tapatalk

I've seen a 30ish % drain sitting overnight a couple of times over the past 2 weeks. Can't seem to find a rhyme or reason for it.

I can't imagine it being "normal" since, with Wifi set to off while sleeping that the device should drain that much.
It's odd and happens randomly, I'm on the same page as you bluestang.

It happened to me once, at night it wastes a 15% battery.
I changed in wifi advance options to not maintain WiFi always awake, only in charge.

sabisavi said:
It happened to me once, at night it wastes a 15% battery.
I changed in wifi advance options to not maintain WiFi always awake, only in charge.
Click to expand...
Click to collapse
That's the setup I have though - so I get no notifications or anything when it's not on. Yet something is still keeping the device up.

I have *exactly* the same problem with an all new device, and with nothing but a game installed on it. After a reboot, if I let the Pixel C right there for a night, then it only drains ~3/4%.
Then I play the only game I have for 5 minutes, and let the device again for a night => it now wastes a 20% battery!
No idea what's going on... "Android OS" appears first in the list of app, but this does not help me so much to find what is actually happening...
The issue still appears even after a full reset of the system (I'v tried, without success).

sylar12 said:
I have *exactly* the same problem with an all new device, and with nothing but a game installed on it. After a reboot, if I let the Pixel C right there for a night, then it only drains ~3/4%.
Then I play the only game I have for 5 minutes, and let the device again for a night => it now wastes a 20% battery!
No idea what's going on... "Android OS" appears first in the list of app, but this does not help me so much to find what is actually happening...
The issue still appears even after a full reset of the system (I'v tried, without success).
Click to expand...
Click to collapse
Exactly. If I reboot the device and let it sit, doze works fine, the second I open an app, use it and put the tablet down, something hangs and keeps it awake. Always Android OS that is keeping it awake as well...

I have this issue too. Are you guys on xceed Kernel?
Whats really interesting even better battery stats Shows no culprit.

I'm on the stock-just-reset-again last version of the system.

Freak07 said:
I have this issue too. Are you guys on xceed Kernel?
Whats really interesting even better battery stats Shows no culprit.
Click to expand...
Click to collapse
I'm on stock - not even rooted

I'm on stock MM here as well.
Also, not sure if it a coincidence or not, but I changed this and haven't seen overnight battery drops anymore. In Settings>Location I changed the Mode from High accuracy to Battery saving. Since the Pixel C doesn't have GPS device, then why use it.
Like I said, not sure if it a coincidence, but battery life has been great overnight since.

bluestang said:
I'm on stock MM here as well.
Also, not sure if it a coincidence or not, but I changed this and haven't seen overnight battery drops anymore. In Settings>Location I changed the Mode from High accuracy to Battery saving. Since the Pixel C doesn't have GPS device, then why use it.
Like I said, not sure if it a coincidence, but battery life has been great overnight since.
Click to expand...
Click to collapse
So last night, I rebooted before I went to sleep, but overnight the battery drained from 85% down to 57% in about 8 hours.
I decided to check my location settings as per your post and found it was set to high accuracy, so I changed it to "Battery Saving".
I did nothing else(no reboot) until I checked my battery now about 3 hours later, it has only dropped by a further 2%.
Looking at "Battery Monitor Widget Pro" history statistics, it is clear to see that overnight the battery was draining considerably more.
It takes readings every 10 minutes and was showing between 450 and 275 mA being used every 10 minutes overnight.
Since I changed the location settings, most of the time it is 15mA with occasional jumps up to a max of 297mA.
Although this could not be classed as conclusive proof, it does seem to have had an effect, I will keep monitoring it to see how it goes.

Yep, I change that setting on the 19th or 20th and haven't seen any major drains overnight.
I think I may have found a winner with that little tweak

So far so good for me too. I don't know if it is related to the GPS settings, but no more inconsistent major drains so far.

if location services is on it can drain a good deal

Just to add that I had exactly the same issue on stock 7.1.2, tablet was staying awake and draining. Reduced location precision and now only a 2% drain during an 8 hour sleep which is a massive improvement.

Terrible battery life probably caused by wakelocks

My battery will completely drain after <10 hours while the screen is off!
However I was able to find out thatquickgooglesearchbar is always the top app.
Those screenshots are a bit old but it's still the same thing, I did manage to root it today, and I was testing Greenify which did nothing even with the Xposed modules, service disabler apps just did not show that specific service for some reason. I was able to remove the widget with Xposed GEL settings but it was still running even though the widget wasn't there.
So can someone please help me out here, maybe the search bar isn't the problem but I just want some battery life.
h ttp://imgur.com/a/gdXKW
(I still can't post links sorry If this is against your forum rules but this is urgent)

Eidoss said:
My battery will completely drain after <10 hours while the screen is off!
However I was able to find out thatquickgooglesearchbar is always the top app.
Those screenshots are a bit old but it's still the same thing, I did manage to root it today, and I was testing Greenify which did nothing even with the Xposed modules, service disabler apps just did not show that specific service for some reason. I was able to remove the widget with Xposed GEL settings but it was still running even though the widget wasn't there.
So can someone please help me out here, maybe the search bar isn't the problem but I just want some battery life.
h ttp://imgur.com/a/gdXKW
(I still can't post links sorry If this is against your forum rules but this is urgent)
Click to expand...
Click to collapse
search and install betterbatterystats (read the whole first post) and it will tell you if its wakelocks etc.
Service disabler apps will need a setting to show system apps (or something similar) ticked or switched to etc.
greenify system apps in greenify also needs to be selected. You may also need to cut wake up paths to get it to stay greenified.
You could alternatively delete the apk of hibernate it (byfar the easiest option of all this).

Darke5tShad0w said:
search and install betterbatterystats (read the whole first post) and it will tell you if its wakelocks etc.
Service disabler apps will need a setting to show system apps (or something similar) ticked or switched to etc.
greenify system apps in greenify also needs to be selected. You may also need to cut wake up paths to get it to stay greenified.
You could alternatively delete the apk of hibernate it (byfar the easiest option of all this).
Click to expand...
Click to collapse
I don't need betterbatterystats, I have battery Battery Historian, check the screenshots, It's clearly the search bar, on my other phone It isn't shown as a top app.
Also I went in the system folder /apps and there was no googlesearchbar, or in any other system apk remover tool, perhaps it was removed by another app, but it's still for some reason running.

Eidoss said:
I don't need betterbatterystats, I have battery Battery Historian, check the screenshots, It's clearly the search bar, on my other phone It isn't shown as a top app.
Also I went in the system folder /apps and there was no googlesearchbar, or in any other system apk remover tool, perhaps it was removed by another app, but it's still for some reason running.
Click to expand...
Click to collapse
Your 3rd image shows googlequicksearchbox had 370ms (milliseconds) of wakelocks over a 9hr period. I really doubt that is your issue.
If it is your top app, then it is probably because of Google Now launcher listening for OK Google spoken keyword.
I seriously doubt that is your battery drain problem as almost 90% of people probably have OK Google turned on and are using Google Now launcher and only a very few have serious battery drain.
BTW wakelocks aren't the issue usually. In the past it has been "partial wakelocks" which means an app locked the device from sleeping, but never released the lock, so the device never goes to full sleep. If you see some app with partial wakelocks or if you see some app with hours of regular wakelocks then that might be an issue. Minutes or microseconds of wakelocks are inconsequential.
I suggest you flash factory image and install your battery tester only. Turn off wifi, bluetooth, nfc, cell radio. Test the drain overnight. That is a baseline for the minimum drain your device can have. Then enable what wireless stuff you normally have turned on. See what that drain is. Then start installing apps and see what that drain is.
If you have reasonable/expected battery drain with stock and everything turned off, then it is just a process of elimination to see what is causing your battery drain.
If you can't get reasonable/expected battery drain with stock and everything turned off, then you probably have a bad battery.
For the record, my overnight battery drain with everything turned off is 0-1% With wifi turned on about 1-2%. With wifi+cell about 2-3%.
IMO the biggest drains for standby are wifi and/or cell signal related. Either bad signals or apps sending data in background or apps that are polling all the time.

sfhub said:
Your 3rd image shows googlequicksearchbox had 370ms (milliseconds) of wakelocks over a 9hr period. I really doubt that is your issue.
If it is your top app, then it is probably because of Google Now launcher listening for OK Google spoken keyword.
I seriously doubt that is your battery drain problem as almost 90% of people probably have OK Google turned on and are using Google Now launcher and only a very few have serious battery drain.
BTW wakelocks aren't the issue usually. In the past it has been "partial wakelocks" which means an app locked the device from sleeping, but never released the lock, so the device never goes to full sleep. If you see some app with partial wakelocks or if you see some app with hours of regular wakelocks then that might be an issue. Minutes or microseconds of wakelocks are inconsequential.
I suggest you flash factory image and install your battery tester only. Turn off wifi, bluetooth, nfc, cell radio. Test the drain overnight. That is a baseline for the minimum drain your device can have. Then enable what wireless stuff you normally have turned on. See what that drain is. Then start installing apps and see what that drain is.
If you have reasonable/expected battery drain with stock and everything turned off, then it is just a process of elimination to see what is causing your battery drain.
If you can't get reasonable/expected battery drain with stock and everything turned off, then you probably have a bad battery.
For the record, my overnight battery drain with everything turned off is 0-1% With wifi turned on about 1-2%. With wifi+cell about 2-3%.
IMO the biggest drains for standby are wifi and/or cell signal related. Either bad signals or apps sending data in background or apps that are polling all the time.
Click to expand...
Click to collapse
Factory reset didn't do anything a few days ago, the results were exactly the same that was when my phone wasn't rooted, so I guess I should return the phone, and get a new one?

Eidoss said:
Factory reset didn't do anything a few days ago, the results were exactly the same that was when my phone wasn't rooted, so I guess I should return the phone, and get a new one?
Click to expand...
Click to collapse
What is your battery drain per hour with nothing installed and all wireless turned off and everything stock?
I'd only return it if that is significantly more than 0-.2% or 1% every 5 hours.
Otherwise it is something you have installed or something to do with the signal and how it interacts with your phone.
Once you start installing stuff or turning on wireless (wifi/bt/cell) then it is no longer purely about the battery and there are more factors that need to be isolated independently.
You really need to establish a baseline to see what the minimum battery drain is. Then you can determine if the battery is the problem or something else.
If you just install everything and turn everything on, there are too many moving parts.

sfhub said:
What is your battery drain per hour with nothing installed and all wireless turned off and everything stock?
I'd only return it if that is significantly more than 0-.2% or 1% every 5 hours.
Otherwise it is something you have installed or something to do with the signal and how it interacts with your phone.
Once you start installing stuff or turning on wireless (wifi/bt/cell) then it is no longer purely about the battery and there are more factors that need to be isolated independently.
You really need to establish a baseline to see what the minimum battery drain is. Then you can determine if the battery is the problem or something else.
If you just install everything and turn everything on, there are too many moving parts.
Click to expand...
Click to collapse
Okay, I now have android N, and my battery life seems to be better, I will leave mobile data off. I will see tomorrow if my battery life has changed.
Do you think I should use Adaptive brightness for more battery life?

Eidoss said:
Okay, I now have android N, and my battery life seems to be better, I will leave mobile data off. I will see tomorrow if my battery life has changed.
Do you think I should use Adaptive brightness for more battery life?
Click to expand...
Click to collapse
Which battery life was the one you think you have a problem with, standby or in use? IMO for in use battery time this phone is about average. Your title of "wakelock" made it seem like you were concerned about standby battery time as it doesn't matter if there is a wakelock if the device is already turned on and in active use.
When turned on, the screen is probably the number one thing eating power, so adaptive brightness could help, but if you are in a bright area, it might be worse than if you fixed the brightness below max.
Even if you have adaptive brightness turned on, the slider scale still is useful as you give the adaptive brigthness mechanism some idea what level of brightness you feel comfortable when the mechanism detects dark, med, bright situations.
One of the worse things for eating power is for the cell radio to be turned on but have no signal, like inside office building or just a bad signal area in general. The reason is the cell radio is power efficient once it establishes signal, but when it is searching for (or loses) signal it uses a lot of power.
If you are doing a lot of disk activity like taking video or hdr pictures, it would probably help to have your userdata unencrypted as this device does software (kernel) encryption and doesn't use the fast/more power efficient co-processor.

sfhub said:
Which battery life was the one you think you have a problem with, standby or in use? IMO for in use battery time this phone is about average. Your title of "wakelock" made it seem like you were concerned about standby battery time as it doesn't matter if there is a wakelock if the device is already turned on and in active use.
When turned on, the screen is probably the number one thing eating power, so adaptive brightness could help, but if you are in a bright area, it might be worse than if you fixed the brightness below max.
Even if you have adaptive brightness turned on, the slider scale still is useful as you give the adaptive brigthness mechanism some idea what level of brightness you feel comfortable when the mechanism detects dark, med, bright situations.
One of the worse things for eating power is for the cell radio to be turned on but have no signal, like inside office building or just a bad signal area in general. The reason is the cell radio is power efficient once it establishes signal, but when it is searching for (or loses) signal it uses a lot of power.
If you are doing a lot of disk activity like taking video or hdr pictures, it would probably help to have your userdata unencrypted as this device does software (kernel) encryption and doesn't use the fast/more power efficient co-processor.
Click to expand...
Click to collapse
Standby is the problem, on screen times are good enough.
Anyway, I don't even know what to do at this point. Android N didn't help enough (cell data is off), I guess I can flash Android 6.0 again and then try to fix it using apps...
What do you suggest I should do, I'm out of ideas at this point.

Eidoss said:
Standby is the problem, on screen times are good enough.
Anyway, I don't even know what to do at this point. Android N didn't help enough (cell data is off), I guess I can flash Android 6.0 again and then try to fix it using apps...
What do you suggest I should do, I'm out of ideas at this point.
Click to expand...
Click to collapse
What is the power drain over a couple of hours with *no apps installed* completely stock, and wifi/cell turned off? What is the change when wifi is turned on?

Eidoss said:
What do you suggest I should do, I'm out of ideas at this point.
Click to expand...
Click to collapse
Have you set "WiFi on during sleep" to "Never"? in the Advanced WiFi settings?
In the original release, there was a bug where WiFi would stay on even if you had set it to "Never" draining battery in standby.
Somewhere between MDA89E and MHC19Q they fixed it and WiFi will go to deep sleep after being in standby for a while, but they introduced another (or exposed existing) bug where WiFi will not resume after coming out of sleep, unless you cycle WiFi off/on. So you're standby battery should be better with this setting, but it'll be a little more annoying when turning on your device.

Horrible Battery life on Pixel 2 XL (Pie) (6%/H Drain)

I'm a really light user. I lost a little less than 2% every hour. Basically I use it as a purely communication device. Mostly check facebook messenger, my emails, and occasionally, browse facebook, reddit, 9gag or watch a short youtube video. I stay up about 16 hours on average and at the end of the day, I was regularly around 80%. If I left the phone unplugged overnight while I slept, I only lose about 6% over 8 hours. I was really happy with the battery life. I could very easily see 3 full days out of my phone off a single charge. This was before the Pie update. I tried both the Beta and the Stable once it released, and my battery life has suffered severely. I'm losing 6% every hour, even with the screen off the entire time. At the end of the day, my phone is in the red and has already turned on power saving mode. Android Pie has killed my Pixel 2 XL's battery. I gave it 2 weeks to "learn" my usage habits, but ultimately, I factory reset and even went back to 8.1, but I still suffer from battery issues. Battery usage gives no hint to the culprit. My phone has been unplugged for 7 hours, with 45 minutes of screen on time, and at 54% remaining battery life. Screen On time is the highest battery drain according to the system battery stats. I didn't have this issue until I installed Android Pie Stable.
I have no idea what could be going on, but could really use some help with this.
TL;DR: From 2% to 6% per hour battery drain on Pie. Reverted to Oreo and FR but still an issue. Advice?

Did you check if the WiFi scanning is turned ON? Settings --> Location --> Scanning
I feel its the only issue, nothing should drain your P2XL crazy if apps remaining constant factory reset.
-- personal experience.

I also use it very similarly to you and easily get 2 days with a single charge on Pie. During night my device drains 1 or 2 % only (wi-fi, bluetooth and 4g on), but I have wi-fi scanning off. Google location services are on (including Location Accuracy on). "At a Glance" is turned off but still using stock Pixel Launcher. No hacks/mods installed.

Same except I have at a glance enabled. I disable it 6 hours ago to test and didn't affect battery drain at all. Still losing 6% every hour. Location and scanning settings default except connect to open WiFi is enabled. Right now testing if connect to open WiFi and Bluetooth WiFi location improvement affecting battery drain.

Testing that now. Will report in a day. Heading to bed now. Gn

Does the phone charge all the way to 100%? Does the phone ever turn off by itself when low on battery ~10%? Install and run Accubattery. After a few charging cycles you will get a very close approximation of your battery's remaining capacity as compared with new in mAh. Battery capacity will be located under the health tab. The more charge cycles you monitor, the more accurate it gets, but it will zero in on a number pretty quickly after the first 2-3 charges. Could be the battery... stranger things have happened. This also assumes the user has fully wiped the phone several times going between DP's, Pie and reverting to Oreo.

Does the phone charge all the way to 100%?
- Yes
Does the phone ever turn off by itself when low on battery ~10%?
- Honestly, I don't know. I never let my battery get that low.
Install and run Accubattery. After a few charging cycles you will get a very close approximation of your battery's remaining capacity as compared with new in mAh. Battery capacity will be located under the health tab. The more charge cycles you monitor, the more accurate it gets, but it will zero in on a number pretty quickly after the first 2-3 charges. Could be the battery... stranger things have happened.
- Will do
This also assumes the user has fully wiped the phone several times going between DP's, Pie and reverting to Oreo.
- You assume correctly.

Didn't seem to help.

Didn't seem to help at all.

Video of battery stats and settings.
https://drive.google.com/open?id=164lujTgzt6hihESdFlkb0AdQdOFGiYtX

I changed some settings and now I'm getting 17mAh drain. Fixed.

The biggest battery sucker for me was having Auto-connect to open wifi enabled and fixing stuck sync tasks. It was preventing my phone from sleeping.

Great to know you were able to stop the draining, I think it might be of great help to other P2XL owners to know what were the settings you changed that fixed the issue.

What settings did you change?

I am having the same issue. I would be interested in hearing your changes as well. Thank you

Download and install Accubattery to monitor your mAh usage. Make sure you check your deep sleep percentage. By the sound of things, your phone is running hot when idle, so it's not sleeping like it should be. You can install Wakelock Detector Lite to see which apps are keeping your phone awake. Once you find out what apps are draining your battery, use the System battery manager in Settings to restrict battery usage for those apps. If that doesn't help, then uninstall the app (unless it is necessary to you). If an app isn't keeping your phone awake, then it may be your system settings. Turn off location scanning for wifi and bluetooth (in the GPS section). Turn off Wifi auto-connect to open wifi. Where I live I have pretty weak cellular connection. I opted to disable Mobile data always active in developer options (Go to about phone, and tap the build number 7 times, then enter your device password). While you are here, you can check Running services in developer options and see what you have running. Also, make sure your accounts aren't stuck trying to sync. If they are, cancel the sync and restart it. Depending on how far you are backlogged, this can take a while. If the sync still gets stuck, try removing and re-adding the account that is getting stuck.
After I restricted/uninstalled the misbehaving applications and tuned the device settings, I'm getting great standby time on my Pixel 2 XL. If I close all my apps before putting the phone back in my pocket, according to accubattery, I'm losing 15mA/h or about 0.4%/h. If I charged my phone to 100%, then unplugged it without using it at all, it would take 10 days for the battery to run out. It's pretty good. As someone who primarily uses their phone as a communication device and research tool, I'm a pretty lightweight user.

+1 What settings did you change?

Yes, please, don't keep us in suspense!
Just got a used one so trying to learn all about getting optimum performance.

Battery drain by Google..

Google is running in background and its Max battery drain app.. in the screenshot, i selected put app sleep when not in use, but still its active for 13+ hours in background.. how to fix it..

For me google play services keep running in the background.
Could you please share a pic of your entire battery drainage from the apps?

I disabled it (google app, not play services) since day one, along with other annoying pests via ccswe and package disabler pro, both complement each other perfectly, of course there is the ADB commands method, but I preffer the apps I mentioned, as they provide very useful widgets to enable/disable problematic apps as google, playstore, updates, chrome, etc, you can even disable services within the apps, to avoid background data access or runnig on boot

Subham jyoti said:
For me google play services keep running in the background.
Could you please share a pic of your entire battery drainage from the apps?
Click to expand...
Click to collapse
This one?

winol said:
I disabled it (google app, not play services) since day one, along with other annoying pests via ccswe and package disabler pro, both complement each other perfectly, of course there is the ADB commands method, but I preffer the apps I mentioned, as they provide very useful widgets to enable/disable problematic apps as google, playstore, updates, chrome, etc, you can even disable services within the apps, to avoid background data access or runnig on boot
Click to expand...
Click to collapse
Can you guide me what needs to be done with these apps? I never seen so much battery drain due to google app on my previous phones

atrix4nag said:
This one?
Click to expand...
Click to collapse
Thnx. Yeah it's same like me. I don't know why it keeps running in the background

atrix4nag said:
Google is running in background and its Max battery drain app.. in the screenshot, i selected put app sleep when not in use, but still its active for 13+ hours in background.. how to fix it..
Click to expand...
Click to collapse
Firstly,
Look at my Google usage, screenshot
9 hrs background and only 0.1 % usage..!
So even if your Google is enabled in background
it should only take a minimum % eg 1 % ..?
So i would say that some settings in your
Google..?
that is enabled, eg syncing..... etc
I don't know all the tasks connected to Google.
I would rather cross check with battery
apps eg Betterbatterystats, Gsam battery monitor,
Wakelock detector lite etc
to pinpoint reason, than try and restrict Google.
Bottom line,
If you don't know what to do and you are desperate,
i would then factory reset device.
Should solve the problem..... hopefully.!
Good luck.

willcor said:
Firstly,
Look at my Google usage, screenshot
9 hrs background and only 0.1 % usage..!
So even if your Google is enabled in background
it should only take a minimum % eg 1 % ..?
So i would say that some settings in your
Google..?
that is enabled, eg syncing..... etc
I don't know all the tasks connected to Google.
I would rather cross check with battery
apps eg Betterbatterystats, Gsam battery monitor,
Wakelock detector lite etc
to pinpoint reason, than try and restrict Google.
Bottom line,
If you don't know what to do and you are desperate,
i would then factory reset device.
Should solve the problem..... hopefully.!
Good luck.
Click to expand...
Click to collapse
Thanks for your suggestions.
I don't want to do factory reset. I will try with other options first.

atrix4nag said:
Google is running in background and its Max battery drain app.. in the screenshot, i selected put app sleep when not in use, but still its active for 13+ hours in background.. how to fix it..
Click to expand...
Click to collapse
Same happened to me. What I did was to delete Data from Play services app, then I deleted cache from phone an voila. I have all sync and functional.
Ps. I charge my phone to 90% and I can get 5-6 SOT at 30% left everyday.

The issue op mentioned is not about google play services, it is about the google app instead I think

The problem is I don't think any batter stat apps can get low enough level stats to indicate what is using the Google app in the background to determine what is causing the drain. Usually, the culprit is an app frequently using location service (your GPS) to check your location which I believe the Android location service coordinates for apps other than the native Android/Google apps are obtained through the Google app in the background. That latter point is purely a guess because as we all know the Google app is a "multipurpose" app and you can't see detailed enough battery usage to determine what function of the app is being used that causes battery drain.
On my S10 5G, for the first 2 weeks I've used it, Google never was in the top 5, taking like 1-2% over the course of a day. Then seemingly all the sudden, it was #1, consuming like close to 1% an hour in the background. So I think, what did I change recently? I enabled Google Discover, but set the option to mae it update less fequently (6 hours) to reduce battery (the option actually says this will reduce battery usage). It didn't make a difference. So I disabled Google Discover and installed Google News instead. My Google app battery usage is lower now. About 0.9% per hour (all background usage of course). I think for most people that's good, but not when you were used to it being more like 0.1-0.2% an hour before.
I think the bottom line is if you want to use more features on your phone you have to live with a bump in battery usage. The 4500 mAh battery on my S10 5G lasts me abotu 1.5 days. LOL. But I don't play games or check Facebook/Instragram all day. Just a few texts, weather alerts, maybe an hour or two of browsing. Mabe an hour total of talk time. So relative to other people I should be less concerned if my phone is lasting well over a day on a charge, actually close to 2 days many times. I know a lot of other more "frequent users" (probably a lot of people younger than myself) that are on social media a lot and or listening to music/watching videos would kill to have their phones last 20-48 hours without having to charge.
Still, I keep an eye on things and it bugs me Google has jumped up. A great app to use is Accubattery and monitor the "SCREEN OFF" discharge rate. You're not actively using apps when the sceen is off so this gives you a good idea of your total background battery usage. You can make changes to settings, charge your for for a while, and let several hours pass, then check the screen off discharge rate and compare it to other discharge periods before you made the settings to determine if the changes you made had much of an effect.
Of course background usage isn't going to be 100% consistent, so the longer you measure the better, as if you look at it over like a 1 hour period, it could be certain apps were just more or less active during that particular hour. But if you compare like half day or more (6+ hour) periods to previous periods, you can get a good gauge if apps setting changes or newly installed apps are eating more battery in the background.

I disable Google feedfack, all their data collecting junk and their data backup too. Google is a pig.
Some blocked Google apks like Playstore are enabled as needed.
Even when Framework and Google Transport are blocked it's sometimes periodically necessary to clear their data to get them from using excessive cpu cycles.
Battery Tracker reports Google Framework running when AOD is on but it's likely misreading as long as battery draw remains at around 1%@hour while phone is screen off.
I'm running on Pie... who knows what Q will do.
Most likely make a bigger mess.