yashsingh1/xdaforums huggingface dataset:
[Android General] :
Unhelpful answer? The author of the other thread already said everything looks good, even the logs show nothing out of the ordinary unless you want to limit stuff that will break your phone functionality.

If you believe that it's not good enough, use the guide from this thread and then limit everything else in the other thread.
[Android General] DB126:
Brilliant! I can see more "unhelpful" answers in your future ...
[Android General] LVME:
my stats

Can you guys please look at my stats? com.google.android.gms is showing 49% in alarms, is this normal?

drive.google.com/file/d/0B9-Y9aWl9dm2aXh4ZnJVUnFqMlk/view?usp=sharing

Thanks in advance!
[Android General] Celestial Fury:
The original functionality of GCM Push for greenified apps doesn't work properly as emails and IM messages are supposed to come through even if the screen is off (which as you found out it doesn't). Having the additional functionality of aggressive doze and/or deep hibernation makes it worse. It takes android functionality to make the push connections (by turning the screen on) to get your emails and messages which you normally would get if you didn't greenify those apps. So, don't do it for apps which you need a reliable connection.

Since you didn't get a satisfactory opinion from another thread:

Awake (Screen Off) (): 48 m 12 s

Active Whatsapp

Alarms: 19, Intent: com.whatsapp.messaging.r.LOGOUT_ACTION

Alarms: 20, Intent: com.whatsapp.alarm.CLIENT_PING_TIMEOUT

Alarms: 8, Intent: android.content.syncmanager.SYNC_ALARM

Active network connections

10026 (Mobile) (Google Play-Dienste): 1.0 MBytes 45,5%

10096 (Mobile) (com.whatsapp.WhatsApp): 1.0 MBytes 33,5%

10089 (Mobile) (com.google.android.gm.Gmail): 289.0 KBytes 9,3%

10035 (Mobile) (com.android.vending.Google Play Store): 246.0 KBytes 7,9%

10124 (Mobile) (net.lovoo.android.ultimata.LOVOO): 26.0 KBytes 0,8%

10174 (Mobile) (de.amazon.mShop.android.Amazon): 25.0 KBytes 0,8%

0 (Mobile) (0): 24.0 KBytes 0,8%

10119 (Mobile) (com.amazon.mShop.android.shopping.Amazon Shopping): 18.0 KBytes 0,6%

10048 (Mobile) (com.google.android.syncadapters.contacts.Google-Kontakte synchronisieren): 14.0 KBytes 0,5%

10084 (Mobile) (com.google.android.apps.maps.Maps): 8.0 KBytes 0,3%

1000 (Mobile) (CyanogenMod-System): 152.0 Bytes 0,0%

This means your device wasn't idle even though Screen On (): 8 s you didn't use it. Once you have an idle log, then I'd look at:

*alarm* (CyanogenMod-System): 1 h 57 m 38 s Count:14 20,3%

*alarm* (com.android.vending.Google Play Store): 1 h 57 m 38 s Count:1 20,3%

*launch* (com.oasisfeng.greenify.Greenify): 1 h 57 m 38 s Count:0 20,3%

*alarm* (com.android.email.E-Mail): 1 h 57 m 32 s Count:2 20,3%

*alarm* (com.whatsapp.WhatsApp): 1 h 47 m 53 s Count:178 18,6%

alarmtimer (): 31 m 53 s

system (CyanogenMod-System): Uid: 1000 Sys: 52 m 56 s Us: 17 m 14 s Starts: 0

*wakelock* (com.android.vending.Google Play Store): Uid: 10035 Sys: 18 m 28 s Us: 7 m 5 s Starts: 0

*wakelock* (com.oasisfeng.greenify.Greenify): Uid: 10130 Sys: 18 m 28 s Us: 7 m 5 s Starts: 0

com.whatsapp (com.whatsapp.WhatsApp): Uid: 10096 Sys: 6 m 36 s Us: 18 m 49 s Starts: 0

*wakelock* (com.android.email.E-Mail): Uid: 10051 Sys: 18 m 11 s Us: 6 m 42 s Starts: 0

*wakelock* (com.whatsapp.WhatsApp): Uid: 10096 Sys: 15 m 41 s Us: 5 m 31 s Starts: 0

Contrary to an alternative opinion that says *alarm* doesn't drain, I'd differ. If BBS registers it then it's doing something. All that I highlighted in green are hardly seen in stock ROMs. While your [0,4%/h] battery loss is commendable even with your processes and kernel acting up, once you have an idle log and the physical battery is not the cause then it's the ROM.
[Android General] flubber1911:
Thank you so much! I´ll install another rom today and check out the wakelocks.
[Android General] Celestial Fury:
I knew said this somewhere before. (emphasis on the brackets)

Post #3 updated.
[Android General] flubber1911:
Hey man,

I installed another rom now. The wakelocks and alarms look better now I think. What do you say?
[Android General] Celestial Fury:
Hi, have you tried downloading your attachment? It's all messed up and it's also not what's needed. It's the BBS text dumpfile that's needed.

You can skip the other log that you attached.

[0,4%/h] drain.

Awake (Screen Off) (): 14 m 37 s

422,4 MHz (): 13 s

307,2 MHz (): 12 m 36 s

Your Wakelocks are keeping your phone awake from 5-15 mins.

AudioOffload & AudioMix - Google voice? Or something set to listen for voice commands? Or uses audio

*alarm* (com.android.vending.Google Play Store) - I don't see Play Store in your network usage. Poor signal?

Greenify - It normally also drains a little due to how it works but when more things drain it also has to work harder.

com.resurrection.ota.Aktualisierungen - OTA update trying to keep a connection?

Mi Band Tools & Mi Fit - External hardware?? connected to Android can be a source of Audio wakelocks as well as it's own wakelocks

WhatsApp - I see some data in network

Many, many more.
[Android General] LVME:
sorry, wrong file

sorry for that! //drive.google.com/file/d/0B9-Y9aWl9dm2UFNVRGVqSVNLdHc/view?usp=sharing[/url] here it is!
[Android General] thepomp:
Hello. Can someone check my dumps? Its too much awake
[Android General] NBAPwns:
I've tried limit everything i could, and im still getting idle drain during sleep. 100% to 93% over night.
[Android General] junkyde:
Still have some drain..

Would be nice if anyone could check this.

http://cloud.tapatalk.com/s/57cd032a52455/BetterBatteryStats-2016-09-05_064038530.txt
[Android General] jhunt75:
Is it safe to mess with the red alarm here?
[Android General] snoprosledneck88:
I have before without issues. Apps change so much so if it breaks anything just member to move it back.
[Android General] LVME:
can anyone have a look at my stats please? //drive.google.com/file/d/0B9-Y9aWl9dm2UFNVRGVqSVNLdHc/view?usp=sharing

com.google.adroid.dms is showing 49% alarms

Thanks in advance
[Android General] Celestial Fury:
Screen On (): 40 m 24 s

Post #3 First sentence.

Awake (Screen Off) (): 1 h 26 m 28 s

In the guide

Alarms: 149, Intent: com.google.android.location.ALARM_WAKEUP_ACTIVITY_DETECTION

Alarms: 85, Intent: com.google.android.location.ALARM_WAKEUP_LOCATOR

And several others. Also active network. Not idle log.

Awake (Screen Off) (): 58 m 53 s

In the guide

Alarms: 7, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_294008

Using this drains battery

com.cyanogenmod.lockclock

Also active network. Not idle log.

Awake (Screen Off) (): 8 m 20 s

Need to see what alarms are under these two categories (Are you using the latest BBS version?)

android (): Wakeups: 24 (3,2 / h)

com.google.android.gms (): Wakeups: 23 (3,1 / h)

Network a little active and contributed to the drain.

No. Post #3 Test Idle Battery Drain No. 6.
[Android General] LVME:
screen on less than 1 minute now//drive.google.com/file/d/0B9-Y9aWl9dm2ZllYQ2I3RjVLR1E/view?usp=sharing
[Android General] Bencoderus:
Nice it works like magic;)
[Android General] NBAPwns:
Active network? I kept my phone on sleep at full charge haven't touched it during idle testing. Kept WiFi on and cell network on.
[Android General] Hiraethic:
- ALARM_WAKEUP_LOCATOR

- ALARM_WAKEUP_ACTIVITY_DETECTION

- ALARM_WAKEUP_ACTIVE_COLLECTOR

- ALARM_WAKEUP_BURST_COLLECTOR

- ALARM_WAKEUP_BURST_COLLECTION_TRIGGER

- ALARM_WAKEUP_PASSIVE_COLLECTOR

- com.google.android.gms.flp.BATCH_FLUSH

- com.google.android.gms.location.fused.GPS_ALARM_BA LANCED_ACCURACY

- com.google.android.location.reporting.ACTION_UPDAT E_WORLD

- com.google.android.location.ALARM_WAKEUP_IN_OUT_DO OR_COLLECTOR

- com.google.android.location.ALARM_WAKEUP_SENSOR_CO LLECTOR

- com.google.android.location.ALARM_WAKEUP_SENSOR_UP LOADER

- com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVE_COL LECTOR

- com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_D ETECTION

- com.google.android.gms.nlp.ALARM_WAKEUP_BURST_COLL ECTOR

- com.google.android.gms.nlp.ALARM_WAKEUP_BURST_COLL ECTION_TRIGGER

- com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR

- com.google.android.gms.nlp.ALARM_WAKEUP_PASSIVE_CO LLECTOR

- GPS_ALARM_BALANCED_ACCURACY

not one of the above is shown in amplify :/

and others too
[Android General] Portgas D. Ace:
Be patient. Normally, it takes some time until alarms/wakelocks are shown in Amplify. The other option is that they simply don't exist on your setup. Alarms/wakelocks depend on each individual setup.
[Android General] LVME:
can anyone have a look at mine //drive.google.com/file/d/0B9-Y9aWl9dm2ZllYQ2I3RjVLR1E/view?usp=sharing ? battery draining too fast!

Would really appreciate it!
[Android General] Celestial Fury:
You didn't use the phone but the phone can use itself. That's what the thread is about: seeing why the phone is using itself and stopping it. Search for Network in the log you posted.

10025 (Wifi) (Google Play services): 1.0 MBytes

You probably have auto-update turned on. Update (all) only when on the charger so you don't need to drain the battery. If you don't have it turned on then you have another problem.
[Android General] NBAPwns:
My auto update apps are set to "Do not auto-update apps" I can't seem to find the problem, it's all from Google Play Services/Android OS. Maybe i should report with a new log... :(
[Android General] LVME:
//drive.google.com/file/d/0B9-Y9aWl9dm2ZllYQ2I3RjVLR1E/view?usp=sharing can you guys help me?
[Android General] Celestial Fury:
Deep Sleep (): 1 h 59 m 12 s

Too short a time for testing. Have you actually read Post #3?

Need to see the detailed alarms for these to know what to limit (so use the latest version of BBS):

com.whatsapp (): Wakeups: 47

com.google.android.gms (): Wakeups: 19

com.facebook.orca (): Wakeups: 13

(Google Services): 2.0 MBytes

2.27 GHz (): 7 m 13 s

In short, your phone was not idle. So, use a longer testing period to rule out inconsistencies and use the latest BBS version.
[Android General] XFi1382:
ContextManagerWakeLock

Did anyone find a solution to reduce the ContextManagerWakelock wakelocks I get? It seems I get almost 1 every second...

PS: I'm on a Samsung S7
[Android General] DB126:
What's the problem? Limited that wakelock to 900 sec months ago and haven't looked back (meaning no ill effects). Did you bother searching before posting? Half dozen+ posts on this topic in this thread alone.
[Android General] XFi1382:
Thanks for the comment! I did look, and some of the posts say to not limit it, others just mention just the wakelocks, but I didn't find a solution. I just wanted someone to confirm limited shouldn't harm performance... No need to be so aggressive :)
[Android General] DB126:
Yes - I see respected contributor [MENTION=5867207]v7[/MENTION] recommends against limiting ContextManager wakelock and favors going after the root alarm(s) instead. My experience differs so you'll want to consider both points of view. As previously noted I have not experienced any issues limiting ContextManager wakelock on a heavily used device but it could be a reflection of device type and/or app suite. This disruptive wakelock appeared in the May/June 2016 timeframe concurrent with an update to Google Play Services and prevented several of my devices from dropping into deep sleep for hours. I don't limit much in Amplify but opted to go after this pup with no apparent side effects. I do not have the corresponding alarms limited. As further evidence sleep drain rate on my daily driver is about 0.2% per hour with push mail active; full activity rate hovers in the 10-15% per hour range with 6-7 hour SOT before dipping below 15% on the battery.
[Android General] XFi1382:
Sounds like you've got your battery under control!! I gave it a shot, let's see what happens :)
[Android General] XFi1382:
One more question. Got rid of most of the alarms, but this one behaving horribly...

com.google.com.android.gms.location.fused.SEND_LOCATION_IN_SMD_MODE

I can't find any info on that alarm. Anyone an idea?
[Android General] Celestial Fury:
It's probably this. Search without the underscore_ Google skill 101. If it's behaving horribly check if something's sending SMS locations with/without your knowledge. Snoop software installed? :confused:
[Android General] XFi1382:
My mistake, it is SMD not SMS... So com.google.com.android.gms.location.fused.SEND_LOC ATION_IN_SMD_MODE
[Android General] DB126:
Have this one limited to 900 sec on one temperamental device but may (and likely will) impact the effectiveness of location services. Before limiting it suggest clearing Amplify stats, rebooting and see if it rematerializes with high frequency. Don't just react to raw numbers. Establish a correlation between presence and actual drain (or unwanted wakes) before limiting anything. Fanboys like to squash everything but my experience suggests (in general) aggressive alarm/wakelock limiting creates far more problems than it solves. Alarms themselves consume negligible power; it's the potential actions that follow that can be problematic. Same for wakelocks which are poorly understood by most.
[Android General] samsald:
Hello everyone wants advise me on di limit this wakelock called com.whatsapp.messaging.r.CLIENT_PINGER_ACTION .

in 12 hours it has 74 activations and would limit but not if it affects my whatsapp notifications

Enviado desde mi SM-N900 mediante Tapatalk
[Android General] :
Read the first post. Limiting will delay notifications and it will not drain.

It is normal behaviour, you can't expect everything with a high number to be dangerous.
[Android General] samsald:
Thanks for your answer autumqueen92

Enviado desde mi SM-N900 mediante Tapatalk
[Android General] sohebq:
Alarms (Allow every 7200 seconds or 2 hours)

* affects push notifications (alerts from mail, social apps, etc.) Things may get delayed if the phone has been idle for a while. Turning on the screen, connecting to a new WiFi or any event that wakes up the phone can trigger push notifications.

- ALARM_WAKEUP_CACHE_UPDATER

- android.net.ConnectivityService.action.PKT_CNT_SAM PLE_INTERVAL_ELAPSED

- com.android.vending/com.google.android.finsky.services.ContentSyncServ ice

- com.google.android.apps.sidekick.SCHEDULED_REFRESH

- com.google.android.sidekick.shared.a.a.UPDATE_CALE NDAR_ACTION

- com.google.android.apps.gsa.kato.ACTION_ALARM

- com.google.android.googlequicksearchbox/com.google.android.sidekick.main.TrafficIntentServ ice

- com.whatsapp.alarm.AVAILABLE_TIMEOUT

- com.whatsapp.MessagingService.RECONNECT

Sorry for Nob question, do we need to limit all these alarms listed above or how do we need to use? Thanks
[Android General] junkyde:
So here is my new log with the newest version of better battery stats.

Hope it will help to identify some nasty Wakelocks :)

http://cloud.tapatalk.com/s/57d29efa48dc9/BetterBatteryStats-2016-09-09_081845667.txt
[Android General] samsald:
hello someone could help me with my dump please want to go down to 0 / h and not to wakelock prevents me

http://cloud.tapatalk.com/s/57d41843af03a/BetterBatteryStats-2016-09-10_090154736.txt

Enviado desde mi SM-N900 mediante Tapatalk
[Android General] ddee105:
Hi guys can u take a look to my log? Im on S7 Flat, i have AOD active

and got 10% drain during night, this drain comes just from AOD

or is there something else. Thnaks in advance
[Android General] Celestial Fury:
Post #2 First red sentence.

Awake (Screen Off) (): 11 m 1 s

In the guide

Alarms: 19, Intent: android.appwidget.action.APPWIDGET_UPDATE

Alarms: 6, Intent: android.content.syncmanager.SYNC_ALARM

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

Awake (Screen Off) (): 17 m 48 s

Nothing much in alarms or wakelocks. Only kernel:

sec-battery-monitor (): 11 m 39 s

Lots of hits on this but the best explanation seems to be that the BatteryService checks the battery too often. You may need to try a different kernel or ROM as Amplify can't limit Kernel Wakelocks.

Awake (Screen Off) (): 1 h 10 m 45 s

Alarms: 508, Intent: com.samsung.android.app.aodservice.ClockTimer.TICK

AoD - Always on Display relating to the clock? Check your setting.

Alarms: 17, Intent: android.net.wifi.DHCP_RENEW

How long since your router was shut down/restarted?

In the guide

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

Alarms: 25, Intent: com.sec.spp.push.ACTION_SEND_PING_MESSAGE

Samsung push service. Limiting this may delay Samsung services.
[Android General] sohebq:
Thanks @OP. The suggestions here are very valuable and working well.

Just a but confused on bluedroid. See the heavy numbers it is generating. Since i am not using Bluetooth, why these are appearing. Should i limit?
[Android General] ddee105:
1.Yes AOD is showing the clock so is related

2. I think it was restarted like 3 days ago

3. - - - - -

4. Like which Samsung services would have delays?

Thanks for your support!
[Android General] boilavera1980:
Is there any way to find out why i have so many gms alarms and what exactly is causing this?
[Android General] Portgas D. Ace:
Sure. Update BBS to the latest version (currently v2.2.0.0 RC3, can be found in the BBS thread here on XDA) and post another idle log file.
[Android General] :
Don't know if anybody could confirm, my experience is that if App updates are pending in play store, the gms alarms run crazy till you hit the update button. May this be a correct observation?

Gesendet von meinem GT-P5210 mit Tapatalk
[Android General] Oswald Boelcke:
I can't confirm that observation; however, I turned the notifications about app updates off in PS settings (as well as automatic updates anyway).
[Android General] DB126:
Better yet just Greenify the Play Store and be done with it. Any pending app updates will display when the store is manually opened (might take a few seconds to populate). After installation Greenify hibernates the PS on next screen off. Perfect.
[Android General] h1ghland3r:
How can I Greenify Play Store? I've donation app, but I can't see Play Store here.

Sent from my Xperia Z3
[Android General] tet-bundy:
U have to make it display system apps. Upper right corner

Gesendet von meinem ONE E1003
[Android General] h1ghland3r:
I know it. I can see Play Games, YouTube for example, but I can't see Play Store or Google Play Store.

Sent from my Xperia Z3
[Android General] DB126:
...and enable "Greenify system apps" in settings under Xposed-based features
[Android General] tet-bundy:
Weird. Working for me..

Gesendet von meinem ONE E1003
[Android General] h1ghland3r:
It's enabled..

Sent from my Xperia Z3
[Android General] DB126:
Appreciate the attitude. Launch Play Store and see if it appears. Otherwise reboot device and try again. If still no joy then ping the developer.
[Android General] h1ghland3r:
I tried both methods a few minutes ago, I even searched for com.google.vending (package name from Play Store). I'll try to contact the dev. Thanks.

Sent from my Xperia Z3
[Android General] boilavera1980:
So i found out it's com.google.android.gms.gcm.ACTION_CHECK_QUEUE

It's push but it's weird that it's so high. Attached log and some screenshots of some other wakelocks.

ContextManagerWakelock and com.google.android.gms.location.fused.SEND_LOCATION_IN_SMD_MODE
[Android General] Portgas D. Ace:
First thing I noticed while reading your log file:

Screen On (): 54 m 42 s 24,5%

That's not an idle log file. Don't use your device during idle time, otherwise the stats are more or less useless for analysis, as your usage pattern will trigger most alarms/wakelocks, but we want to minimize idle drain.
[Android General] boilavera1980:
Okay i will take this into account and create a new log.
[Android General] raptorskate:
Can you look at this? Thanks!
[Android General] :
This doesn't show anything, it's just a log of what happened one second ago? Read the second post to get an idea of what to produce.
[Android General] raptorskate:
That's what I did.. that's weird, I charged to 100%, disconnected and just left it there
[Android General] :
Does it have root rights? Or are there any app like stamina mode, power nap, greenify preventing it from getting stats? Did you leave it to idle for 7 hours?
[Android General] raptorskate:
It is rooted, the only app would be Greenify

The weird thing I that I got a complete dump file after 5 min of screen on.
[Android General] xda sharru:
guyss plss helpp... Im using redmi note 3 3gb ram variant... installed amplify and blocked many alarms, wakelocks ... but one problem - fingerprint recognises and vibrates but screen is not waking.... when power button pressed at tht time it wakes and unlocks....
[Android General] Sam Nakamura:
Use the xposed Uninstaller... It should start normally afterwards, then you can try again from scratch.. It's not recommended to randomly block alarms - stick to the guide for system stability and if you modify by your own do it step by step to have a possibility to evaluate at what point it crashes..
[Android General] raptorskate:
OK, this is it for what I'm seeing, this one has all the info. Can you help me? Thanks!
[Android General] sohebq:
Got massive standby drain today. Anyhelp would be appreciated. I am wondering why i am having such high kernal wakelocks.
[Android General] abhijeet715:
Your alarms has been firing due to a widget, i guess its the transparent clock widget app. And it was also working during deep sleep i guess, logs would have been better to intercept :)
[Android General] sohebq:
You are 100% right on alarms. There is one alarm that triggers a lot because of widget. If i limit it, time of widget wont update. I like this app so i am stuck lol.
[Android General] spartan268:
Does anyone know what the 4-0048 kernel wake lock is? It's always my third most wake lock, right behind the screen on ones.
[Android General] :
You could also try writing to the developer and ask to fix the issue.

There is no valid reason for such a widget to update when the screen is turned off.
[Android General] sohebq:
If this is disabled, how time will update then?
[Android General] DB126:
Can't have your cake and eat it too. If the app/widget is misbehaving disable it until the dev fixes the problem.
[Android General] sohebq:
TRied another similar app and result is same. Seems like this is a general behavior.
[Android General] :
This kind of widget should really only update itself while the screen is on (or probably even only when the widget itself is visible). I would start looking for an alternative. A brute force solution would be to use any automation software (Tasker, etc.) with Amplify to block the wakelock completely when the screen is off.
[Android General] DB126:
Have you tried removing all similar widgets to see if drain improves? A previous poster speculated the elevated alarm count (which wasn't really all that high) was due to widget behavior but there is no definitive proof in the screen snips you provided ... hence the value of logs.
[Android General] samsald:
Hi all can i limit that wakelocks

Enviado desde mi SM-N900 mediante Tapatalk
[Android General] sohebq:
Issue is that all such apps are no where appearing in BBS alarms or WLD alarms. Should I assume these are not draining battery despite high count in Amplify?
[Android General] :
Yes and no (unfortunately).

In case of widgets they will likely be all lumped together under 'android.appwidget.action.APPWIDGET_UPDATE' without any actual app names. I use only one widget (calendar) so it is easy for me to check for any misbehaviour, but if you have more than one then you may need to enable them separately to find the culprit. With no widgets active the alarm will not trigger at all.
[Android General] Xerosnow:
[MENTION=5401012]Celestial Fury[/MENTION] The new battery wasn't helping. But somehow from last week it is making it to a day and a half. I've a attached the fresh bbs dump. I see a lot of heartbeat_alarms. Not sure what is causing them. Please take a look when you get time.

I'm running on sultan's latest cm13 + xposed 86 + greenify + amplify. Haven't limited much in amplify. Only installed them like 2 days ago.
[Android General] Randyshare:
Nice Post .

Keep develop :)
[Android General] :
Got a new log. I used to get 30 minutes wakelock in idle but suddenly it seems to get tamed. Anyhoo, it'll still be great if it could be improved further
[Android General] 4r44444:
Is there any new list? The one in start post is not new and much services changed name or are updated...