yashsingh1/xdaforums huggingface dataset:
[Android General] Celestial Fury:
Awake (Screen Off) (): 10 m 44 s

See the guide

*net_scheduler* (Google Play services): 6 m 13 s

Alarms: 55, Intent: com.google.android.gms.gcm.HEARTBEAT_ALARM

com.google.android.intent.action.GCM_RECONNECT

Alarms: 5, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_701758

Awake (Screen Off) (): 3 m 6 s

Alarms: 18, Intent: com.google.android.intent.action.GCM_RECONNECT

This is the main thing.

It's based on KitKat and Lolipop because neither MM nor Nougat is available for my phone.
[Android General] :
Thanks, I don't wanna lose push notifications so I guess I'll just bear with it, assuming it delays on stock roms too
[Android General] naughty6t9:
Delete
[Android General] BlackStagea78:
Any chance someone could have a look at this for me and see if there's anything more that could be done without losing functionality?

I know Aquamail is the highest drainer on there, I'd forgotten it was set to check every 5mins. Now set at 30mins.

I don't think it's too bad overall but it does look like I'm getting a lot of "Awake (Screen off)" time.

Cheers.
[Android General] TNSMANI:
First of all, update BBS to RC3 from its XDA thread.

Next, some sensor kept your device awake for more than two hours. Check what you have activated that could be using sensors and switch that off.

Do you require Bluetooth to be on while asleep? If not switch it off.

In kernel wakelocks, you have something called fts_wakelocks for more than 11 minutes. I have no idea what it is.

Aquamail is also eating battery. See whether you can limit some of its processes without losing functionality.

You also have a lot of alarms which could be limited. Read the OP.

Google Play Services was involved in a download of about 1 MB.

After taking care of the above, post a fresh dump.
[Android General] DB126:
Aquamail is quite efficient for what it does but if work is requested battery/power is going to be consumed. Consider dropping auto sync interval to 2+ hours or longer and use manual refresh (down swipe in message list) to grab the latest items as needed. In some use cases IMAP push can be more efficient than scheduled pulls (or dramatically more expensive). Generic guidance for any mail app that supports configurable sync methodologies and windows.
[Android General] :
You could also select only a few folders / accounts to sync. The more folders are synced, the more time it will take to process all of them. I also use AquaMail with an 1 hour sync interval for ~5 folders and the battery drain is minimal.
[Android General] LVME:
please have a look, made all the changes you suggested!
[Android General] :
Your screen on time needs to be less than a minute.
[Android General] LVME:
after i completely charge my phone, you mean, right? sorry noob here
[Android General] :
Yeah, after charging turn off the screen and leave it to idle for at least 6 hours
[Android General] joanquro:
Hello.

I attach my stats. I think they are ok, but just in case...
[Android General] BlackStagea78:
Thanks for the reply.

First off, I've updated BBS.

Now for the rest, unfortunately you haven't really told me much more than I already knew from reading the dump myself. I probably should've been a little more descriptive in my post other than noting the aquamail thing. Sorry.

I've read the Op and limited everything I found from there that showed up in amplify.

I was kind of hoping someone could shed some light on the fts_wakelock. It shows in BBS and WLD but not amplify. Which makes fixing it a pain. Google isn't much help. Might try changing the kernel (which in itself will use more battery than the current one) for that one.

Bluetooth is on because have a tendency to forget to turn it on when I get in the car.

As for the sensor. I'm thinking it must be Velis auto brightness. But why it would be using the sensor while the screen is off is beyond me. I've now greenified it. Will see.

I've extended aquamail refresh to 1hour and it only syncs 6 folders.

Thanks again for the replies.
[Android General] DB126:
While no direct experience with that specific wakelock I lean towards a rogue motion sensor or process/service that attempts to illuminate the screen on specific events. No immediate solution but might help focus the hunt. Good luck.
[Android General] Celestial Fury:
10153 (Wifi) (com.whatsapp.WhatsApp): 25.0 MBytes

Basically, the phone wasn't idle. Do the test before sleeping to reduce WhatsApp activity or if people still send messages in the dead of night - temporarily disable/greenify WhatsApp for the test.

1st link on Google search? leads to a Samsung / Note specific kernel wakelock. It's extraneous info because - next point:

Why you can't find fts_wakelock in Amplify - Post #1 (Ctrl-F "Kernel")

Awake (Screen Off) (): 40 m 7 s

In the guide

Alarms: 44, Intent: com.google.android.gms.gcm.HEARTBEAT_ALARM

Alarms: 6, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_237130

CPU States

1.27 GHz (): 14 m 19 s

300 MHz (): 11 m 57 s

Active Aquamail + Samsung Push Service + Bluetooth = not idle
[Android General] joanquro:
These stats were obtained while I was sleeping. That's weird. I'm not using Greenefy but I will try.

Thank you.
[Android General] Celestial Fury:
The phone wasn't idle because people were sending you messages while you were sleeping which means your phone wasn't sleeping (idle) because it was receiving all those messages.
[Android General] BlackStagea78:
Thank you celestial fury.

I've been to that thread numerous times to search for that exact post. Maybe it's something to do with Tapatalk but it sends me to the last page. Then after finding the correct date range, I can't find that exact post. I'll need to check on a desktop when I get a chance. Only info I could find from other threads in the same search results was to run a certain build.prop script, change scheduler in kernel tweaking app, do a fresh clean install without restoring any previously backed up data or de-fragment something or other. I was hoping to find it, and limit it in amplify.

I've limited the other alarms. I was under the impression after reading the op that the heartbeat alarm could break push notifications on custom roms, so didn't limit it originally as I use a custom rom. We'll see.

Thanks again.
[Android General] LVME:
There it is. Thanks in advance! Hope I can stop this crazy drain
[Android General] LVME:
anyone? lost 25% overnight in idle
[Android General] DB126:
Glancing at the dump I see some interesting candidates but will leave it to others to make specific suggestions. Battery health also comes into question as the fall off rate seems excessive even with a few obvious drainers.

My response was motivated by the ping you felt necessary to leave <8 hours after previous post. Amazing fact: other VOLUNTEER contributors lead lives that don't involve servicing this thread. Imagine that - going to work, tending to family, even (unbelievably!) taking in a few hours sleep. What a bunch of slackers ...
[Android General] prakashkushwaha74:
It happens with weak network on 4g . :D
[Android General] LVME:
100% no data connection, so that's not the case
[Android General] DB126:
Poor WiFi can trigger the same behavior. Kill the radio (don't just dump it into airplane/flight mode) and see if drain subsides. As noted here and elsewhere two year old battery is also suspect (calibration and/or age).
[Android General] TNSMANI:
You have wifi issues. See if setting up a static IP for the phone improves battery consumption. Your wifi was on and also connected all the time. Enable 'only during charging' or 'never' in SETTINGS>WIFI>Advanced (provided you don't want wifi while the phone sleeps).

But the main culprit seems to be a download during sleep: "10135 (Wifi) (com.ideashower.readitlater.pro.Pocket): 97.0 MBytes 98.2%". No wonder you lost 27% battery!

EDIT: I also see the significant motion detector being woken up 35 times by Whatsapp for 3+ hours. Your mobile data was also on for sometime, contrary to what you said

"0 (Mobile) (0): 9.0 KBytes 0.0%

10135 (Mobile) (com.ideashower.readitlater.pro.Pocket): 8.0 KBytes 0.0% 10010 (Mobile) (Google Play services): 2.0 KBytes 0.0%"
[Android General] DB126:
As noted here and the handful of posts that follow.
[Android General] misterhong:
i see that u limited contextmanagerwakelock to 900.

do u limit alarm com.google.android.gms.location.fused.SEND_LOCATIO N_IN_SMD_MODE too?if yes, what's the number to limit it?
[Android General] DB126:
Yes - same (900 sec)
[Android General] :
If only there was a way to see what google changed in their Play Services. It looks like they fixed the problem with Icing, thought the OP still does not recommend it.

But the wakelock is so small that it's negligible anyway
[Android General] DB126:
Limiting icing and *most* other Play Service wakelocks is ineffectual at best and often counter productive. Wakelocks, and to a lesser degree Alarms, are poorly understood by the community. People react to the huge numbers shown in Amplify, BBS and other tools without fully understanding what they mean and the impact on idle drain, deep sleep and 'core' functionality/services. That said, everyone's situation is different and there are a handful of rogue alarms/wakelocks that can make a meaningful difference when limited. Best path is to limit what has proven to be a drainer (big numbers are not conclusive evidence) and leave the rest alone.
[Android General] :
Exactly.

I just wish there was more documentation on some of these well-known drainers so the app can maybe find a better balance for them rather than blind trial and error
[Android General] DB126:
Really depends on the device, settings, app suite, usage patterns, external conditions (eg: signal strength) and user expectations. My limit list small but likely has some surprising inclusions/exclusions. Drain metrics rival the top 20% reported here and in similar threads. Not looking for "extreme" anything, just a fully functional device that still has plenty of juice at the end of the day.
[Android General] samsald:
Hello everyone. I tell that I only have one kernel wakelock and not able to solve. I am looking on the internet and everywhere and can not find how to remove this wakelock of them a screenshot. It is the first sec_battery_momitor. anyone knows how to fix it please help
[Android General] hollow1:
How about my amplify here:

It still has this
[Android General] Miaou63:
How do you get that level of details ?
[Android General] :
Limit the activity detection to 86400 seconds
[Android General] samsald:
Hello everyone. someone can help me with a wakelock that more and try not able to remove it. Down my fresh dump 0.5 x h drain of this only wakelock
[Android General] hollow1:
I Just click on it...the round icon which % inside

What is the side effect of this limit ?
[Android General] :
From what I read, it delays background location fix for apps like Google Now. Navigation apps are not affected.
[Android General] brezzz:
is there a config file that can be installed with all the recommended settings in?
[Android General] Sam Nakamura:
If you are talking about amplify it is sufficient to do all settings once and save the xml file in /, data, data, com.ryansteckler.nlpunbounce, shared preferences to for example Google Drive you can then backup & restore this xml with all settings made later on again and again.. Without going to the pain of doing the settings over and over again, even sharing preferences is possible..

Just turn the amplify module of, reboot, replace xml, turn module back on & reboot..

https://drive.google.com/file/d/0B0FpJqT1UCyaYzhGbF9WSEJmOUU/view?usp=drivesdk

These are my settings but only what is possible under marshmallow.. So maybe some editing from your site is necessary may someone had even better settings..
[Android General] HeaDShoTHuntR1:
Do al these wakelocks still have the same name?

Which ones should i limit???
[Android General] HeaDShoTHuntR1:
Ill try your settings
[Android General] spartan268:
So normally I would say I'm pretty good at these kinds of things but this one is currently f*cking me up the as*.

Starting yesterday or the day before battery life has taken a turn for the worse when my phone is being actively used. I found that it was Google Play Services related but nothing more. Strangely enough on sleep it's gone, since I have Amplify, Power Nap, and Greenify running, it likely suppressed it. I realized that since it's suppressed it'll be hard to find information on the active drain aspect. I since disabled the A.P.G. combo for more visibility and found some monkey Google stuff going crazy.

In the logs it appears to be the Icing wakelock wreaking the most havoc. Net_scheduler isn't that bad. Likely whenever I take my phone off standby it tries to process these wakelocks immediately which explains my active drain. I do know the logs don't follow the standard procedure of 4 hours idle time, but it seems quite clear cut where the issue lies. I just don't know how to possibly even squash it, even if I use Amplify again it'll just haunt me again as soon as I take my phone off standby.

Currently on Android 5.1 with Google Play Service 9.6.83

- Tried clearing cache/data for Google Play Services and Framework

- Tried uninstalling updates for Google Play Services and re-installing

- Uninstalled talkback and gmail

- Barely had any syncs with Google to begin with

- Rebooted multiple times

EDIT: Added in another persons log who's experiencing similar issues as me incase his is more accurate for your standards.

EDIT #2: I used de service app and disabled the Icing service. Had the google play DC message a few times but then it hasn't appeared again since. Everything seems to be stable for now, texts and notifications going through without issue. Until there's an update to GPS gonna leave it disabled for the time being.
[Android General] Celestial Fury:
How can I show you Zen unless you first empty your cup?

How can I show you Zen unless you first empty your cup?

[MENTION=5485572]spartan268[/MENTION], different logs, different problems.

Post #3 You know but do not do.

Post #3 Last line in red.

End of today's lesson.
[Android General] spartan268:
Apologies master. Just the crippling wakelock really messed me up for work today so I was p*ssed.

For those who may have the same problem check out my second edit. It's likely a hit or miss but your phone will be alive at the least right
[Android General] HeaDShoTHuntR1:
Ive tried all these things and tips but i have way better battery life without any tweaks :P
[Android General] Lither:
I have these Google and Android wakelock alarms, what value should I use to stop or reduce the times it happens in Amplify as it is draining the battery?
[Android General] DB126:
None of these appear to be excessive. Just Android and Google Play Services going about their business. Keep in mind alarms themselves don't drain; it's the actions that follow that *may* be an issue. In many cases an alarm fires and nothing happens.
[Android General] Celestial Fury:
Only thing of note is this Kernel Wakelock sec-battery-monitor (): 12 m 5 s

You have some widget or application monitoring the battery. Check your settings.

Mostly. The ones in the guide.

The problem is that you already think you know the problem. You are posting an active battery drain log in an

idle

battery drain thread. Active drain can differ wildly. In your 2 h 31 m 58 s log, see how much network activity you had. See all the switching between mobile and cellular connections. You describe your problem as suddenly happening a day or two ago. It is highly unlikely for something to suddenly act up. Several possible causes: an update/new app, you changed/limited/blocked a setting. At least 3 services have been identified in Post #2 that causes its related wakelock to run wild if it's disabled. Most likely there are others that haven't been identified. Only you will know what you did.

The answer is in Post #2.
[Android General] koekoek91:
[MENTION=5401012]Celestial Fury[/MENTION]

First of all thanks for this thread.

Could you have a look at the dump and the screenshots I added? The dump is from an 8 hours idle test.

Im only getting about 1 hour of SOT, which I think is really bad for my phone (Sony Xperia Z5). I read others getting 4-6 hours on this phone.

Thanks and keep up the good work :good:
[Android General] Celestial Fury:
Level lost [%]: Bat.: 24%(71% to 95%) [-2,3%/h]

Not an idle log, you've used your phone until 75% then charged it up to 95%. Did you

remove

Screen On from the log? It should come right after Awake (Screen Off).

SOT depends on the environment temperature as well. Air conditioned office? Cold climate? Screen on continuously like watching a movie = higher SOT. Average SOT for a particular phone model is more reliable than SOT claims that are 3x-4x more than the average but without showing logs / screenshots or what modifications they did.

In BBS advanced setting, make sure API is NOT selected as it's less accurate. Your screenshots do not correspond to your log either.
[Android General] aukhan:
I don't use maps on my device so I am ok to disable them. Disabling them will cause high wakelock you mean ??

Powered by ET !
[Android General] Portgas D. Ace:
If you do not use Maps or any other navigation app, then you are fine with disabling GoogleLocationManagerService :) The CheckinService caused a high wakelock for me after I disabled this service. Re-enabling it solved this. Disabling GoogleLocationManagerService did not cause any wakelock for me.
[Android General] Celestial Fury:
Your flight mode is [0.1%/h] This means in normal mode you can't get lower than this.

I'd go with disabling anything related to ads or analytics. You'll have to test for any negative side affects. What program do you use to do this? In Amplify I've got 2 Android, 1 FB and 1 Sony Analytics

service

disabled (for a total of 4) as well as 1 FB and 1 android Analytics

alarm

blocked (for a total of 2). Don't disable CheckinService as mentioned in Post #2. In short, for me, I only disable stuff that relates to ads or privacy. Otherwise, I'd leave it alone if it doesn't cause drain.
[Android General] Celestial Fury:
If you have restarts, are you using a permission manager like XPrivacy to block any permission? Your testing time is also too short. Charge it to full then leave it alone for 7 hours (don't use) then post screenshots.
[Android General] aukhan:
Disable Service

This is the app I use for disabling service.

Have you got a chance to paly around with Wakelock terminator Xpose Module ??
[Android General] Celestial Fury:
It's listed under DANGEROUS - DO NOT LIMIT / DENY in Post #2. It can be disabled but its related receivers will also have to be disabled which Amplify can't do.
[Android General] Odin777:
wow nice guide
[Android General] Portgas D. Ace:
Yes, I found out about this before coming across your guide :) Nevertheless your guide was extremely helpful for me.
[Android General] Celestial Fury:
No, from the video it seems that you need to copy paste the name in order to block? Seems troublesome and seems similar to what Amplify does but I don't think I know how it works for sure.
[Android General] aukhan:
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService

adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver

adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$Receiver

adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver

adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateActivity

adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity

adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateService

adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver

adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver

[MENTION=5401012]Celestial Fury[/MENTION] what are your thoughts on disabling them via ADB ?? Can you recommend which are safe and which are unsafe ??

Powered by ET !
[Android General] Celestial Fury:
I don't get it - why would you want to disable system updates? Do they drain battery? This guide is all about minimizing drain and maximizing functionality.

In fact, I've got some new better screenshots of my own which I'll be posting in a short while :o.
[Android General] aukhan:
[MENTION=5401012]Celestial Fury[/MENTION], Yes these are OTA updates and BTW as I am running a custom rom i dont really think we would require OTA updates right ?

or these are the ota updates which is related to Google Playstore for the apps?

I am trying to find more info to see what are these services.
[Android General] rawalmaulin:
Now would u pls suggest? I have gone thro gh the whole thread and setup but still 39% over night the phone was on silent mode . Posting BBS dump for ref.

Thanks
[Android General] Portgas D. Ace:
I guess, [MENTION=5401012]Celestial Fury[/MENTION] will help you with those issues. I would go one step further and suggest you to use Disable Service to disable some battery draining services from Google Play Services.

Start with the following services:

- AdvertisingIdService

- AnalyticsIntentService

- AnalyticsSamplerService

- AnalyticsService

- NegotiationService

- NlpLocationReceiverService

- ReportingAndroidService

- ReportingSyncService

- UserPresenceService

Afterwards, you can use your phone for some days and report back if that helped you.
[Android General] Celestial Fury:
I don't know what they are without googling them but most likely FOTA. Unless they show up in BBS as causing drain, disabling them for the sake of disabling goes beyond the ambit of this guide. You might want to ask your custom ROM dev why they weren't disabled in the ROM in the first place.

I need your 'other' screenshot. Or just attach a Text Dumpfile. What I suggest is after fully charging, clear ALL recent apps from the list. Apps that aren't cleared tend to be more active. Your Event Log and Checkin Handoff are running wild. Did you disable CheckinService and EventLogService? See Post #2 under DANGEROUS - DO NOT LIMIT / DENY. I can't see the Kernel wakelock screenshot as the hanging window is blocking the view. Note that there's nothing much that can be done for kernel wakelocks. So, attaching a Text Dumpfile will ensure you've posted most of what's needed.
[Android General] sniickers:
Awesome thread!!!!

I have been watching since page 2 I think. Had a solid set up. Then had some serious software issues. Did a new flash of a rom. These screen shots are after 10 hours on battery with no usage on a full charge. Any suggestions to help reduce drain?
[Android General] Celestial Fury:
What's the problem with the attachment? Did you see the upload button in the attachment window? At least edit your previous post and wrap then in CODE so they're not so long.

Firstly, IDLE drain means the drain when you are NOT using the phone. Your stats show that your screen has been on for one and a half hours which means you've been using your phone for that long. To find out what's draining your phone unnecessarily you have to separate your using time with your idle time. If it's mixed, then it makes it difficult to tell. You've seen Post #3 on how to test, right? Do it when you're sleeping and not using the phone.
[Android General] Celestial Fury:
No usage? So screen on time shows under a minute? I'm replying on my phone for the next few days but I can see several things.

Your gear - connected to your phone. It's the nature of the beast to keep a close connection to your phone, hence the drain. Only you can tell how constant a connection you want by limiting it.

Your Gmail, lots of activity - did it correspond with lots of emails in the same period? If not then something's off.

Your Bluetooth, it's on? In comparison I had my Bluetooth on for 10 hours tethered to another phone with Internet connection and idle drain was [0.3%/h].