yashsingh1/xdaforums huggingface dataset:
[Android General] Celestial Fury:
Alarms: 15, Intent: com.google.android.gms.gcm.HEARTBEAT_ALARM

com.android.deskclock Alarms: 5, Intent: change_state

Marshmallow stock deskclock? Seems to drain.

In the guide

Alarms: 5, Intent: com.google.android.gms/.checkin.EventLogServiceReceiver

10025 (Wifi) (Google Play-Dienste): 182.0 KBytes 46,4%

10109 (Wifi) (com.google.android.gm.Gmail): 68.0 KBytes 17,4%

10117 (Wifi) (com.whatsapp.WhatsApp): 45.0 KBytes 11,5%

10029 (Wifi) (com.android.vending.Google Play Store): 42.0 KBytes 10,8%

Some data transfer so not really idle.

The alarm receiver is fine to be limited. The warning is about limiting the

service.

They are related. Newer versions of Play Services may or may not have this problem. So:

Alarms: 6, Intent: com.google.android.gms/.checkin.EventLogServiceReceiver

Alarms: 4, Intent: com.google.android.location.ALARM_WAKEUP_SENSOR_UPLOADER

Alarms: 5, Intent: com.android.internal.telephony.dataconnection.DataConnection.DC-1.action_retry

You may have a widget or something that tries data if WiFi is not available or vice versa or something related. Otherwise, this should not occur if data was not enabled.

Also, some data transfer.

Logcat is not required. In BBS Settings - Advanced, TICK Kernel Wakelocks using API and see if Kernel wakelocks will show up since it doesn't.

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

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

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

Alarms: 3, Intent: com.whatsapp.messaging.MessageService.CLIENT_PINGER_ACTION

Alarms: 3, Intent: com.sharpregion.tapet/.SetWallpaperService

Might want to turn it off your wallpaper changer. Your drain is way beyond what the BBS textdumpfile suggests. Either your battery is bad or you can see Post #3 IF Alarms & Wakelocks are already low OR if you have severe drain for further information.
[Android General] Xerosnow:
Thanks for the reply.

My old stock battery had run into same issues. I was losing almost 50% overnight. I have put in a new battery last week.

I've removed the wallpaper changer. I'll probably reflash the rom and take a new bbs dump with less apps.
[Android General] hazote:
Hello,

I have done a backup restore to make something clean due to New undesirable process.

Problème: sending with Gmail don't Work.receive Work.

Under amplify I have only com.android.vending/..finsky.. Contentsyncservice

And nlpwakelock

And Téléphony.data-stall

No limited any autorisation for Google

What can I do ?

never mind: reset gmail cache and works ..:rolleyes:
[Android General] wxfreak:
Should my drain be bigger on wifi? I've attached a log from last night. I'm not sure what is happening?
[Android General] Portgas D. Ace:
Statistic Type: Boot to Current -> change it to "Unplugged to Current" within BBS

Wifi On (): 6 h 11 m 2 s 100.0%

Wifi Running (): 21 m 14 s 5.7% -> this seems to be your issue: your WiFi was activated the whole time, but connection was only established for around 20 minutes. The WiFi will drain quite some battery while trying to connect to a network. But in the end 0.3% drain per hour is good, so don't worry.
[Android General] wxfreak:
Thanks for the quick response! Should I change my WiFi settings? I have WiFi set to go to sleep when not in use, open network notifications off, and WiFi scanning off for location. With WiFi off using mobile data only I get lower drain.

Thanks! :good:
[Android General] Portgas D. Ace:
The idea behind the idle log file is to identify all drainers that occur while your device is in idle mode with your default usage pattern. In case you prefer mobile data over WiFi, then this is the correct way for a idle log file.
[Android General] wxfreak:
My idle drain on wifi seems to have gone crazy and is what I want to work on. I've attached a log from last night. Many thanks for any assistance.
[Android General] Portgas D. Ace:
15510000.mdmpm_pdata (): 1 h 2 m 21 s Cnt:(c/wc/ec)6495/50/0 13.4%

wlan_oob_irq_wake (): 4 m 5 s Cnt:(c/wc/ec)2843/179/0 0.9%

wlan_rx_wake (): 1 m 1 s Cnt:(c/wc/ec)226/73/226 0.2%

Check this thread, this thread or this thread for a potential solution. Otherwise, try to flash a custom kernel.
[Android General] wxfreak:
Thank you. I'll check into these when I get home tonight. Much appreciation.
[Android General] gregferns:
Hi...

Pls see and advise what I can do best?

My log from last night is attached...

Phone is moto g turbo edition, stock but rooted...

Thanks in advance

Greg.
[Android General] Portgas D. Ace:
BetterBatteryStats version: 2.1.0.0 -> update it to v2.2.0.0B6 (available in the BBS thread here on XDA) and produce another idle log file. BBS version 2.1.0.0 has issues with "alarm" stats, it doesn't show the complete one, thus making it rather difficult to tell which exact alarms have been triggered and thus drained battery.

Beside this, your stats show some kernel wakelocks. If possible, flash a custom kernel. But let us first have a look at your new stats according to the above mentioned recommendation.
[Android General] hazote:
hello,

actually at 99,1% deep sleep , 0,7% per hour. I can get better !

Can I limit these alarms ? (Do you know it)

android.appwidget.action.APPWIDGET_UPDATE

com.android.server.device_idle.STEP_IDLE_STATE

ScheduleConditionProvider.EVALUATE

EventConditionProvider.EVALUATE

com.android.server.task.controllers.IdleController.ACTION_TRIGGER_IDLE

since I have limited : com.android.internal.telephony.data-stall,

I get : com.qti.internal.telephony.dataconnection.QtiDataConnection.QtiDC-1.action_retry

Did you try to limit Processes listed under "Processes" in BBS log and how ?
[Android General] wxfreak:
Just wanted to say thank you. After assigning a static IP on my router and changing my Wi-Fi to go to sleep off the charger, my drain droped back to 0.1% per hour while connected to wifi.
[Android General] renolz:
Hi,

I've been using amplify for some months now following this guide :)

One thing that keeps annoying me though, (it may be my own fault limiting something i was not supposed to in the guide by mistake) but when someone send me snaps on snapchat, i do recieve them, but with a few hours delay.

Example: someone sends me a snap at 7am, i might not recieve a push notification on that snap until 12am, not exactly 5 hours, but it usually takes a few hours to recieve it.

Any ideas what i messed up on to get this annoy delay? :/

EDIT: i have double checked that i haven't limited any of the sync / cloud icons from the list.

- Renolz
[Android General] unrealRage:
Since you are using Amplify, you probably limited some Snapchat wakelock or alarm, and that limit causes that walelock/alarm to be active every *amount* of seconds you have allowed it to be (ex. if you limited it to 3600 seconds it will be active every hour).

Try with disabling Amplify in Xposed and see if that works out for you.If it does,my suspicion is right.
[Android General] renolz:
Well ofcourse i have limited something that is causing it, that's why i'm asking if anyone know which wakelock/alarm might be causing it :)

I wouldn't have asked in this thread if i diddn't think it was amplify that was causing it.
[Android General] unrealRage:
My apologies then.

Well it's probably wakelock is delayed by couple of hours.It could be an easy spot if you haven't limited all of your wakelocks on every couple of hours (I do limit some of mine to max amount of seconds).
[Android General] TNSMANI:
Please confirm your suspicion by disabling Amplify. If your problem is solved, then we can go into the things you limited to see which is the cause. But I have a suspicion that Amplify is not the cause.
[Android General] renolz:
I think i just figured it out, i overlooked this one "com.android.vending/com.google.android.finsky.services.ContentSyncServ ice"

I disabled it completely and now it seems to be working fine again! I think it might have affected push in general, not just snap, cus i instantly got some fb pushes aswell :)

Dunno, i'm a newb at this, but as long as it works, i'm happy!

Thanks folks.
[Android General] demoncamber:
Ok guys, so I finally got down to 4.9% idle drain, if anyone sees any room for improvement please chime in.
[Android General] soza971:
First time i get this wakelock and its huge
[Android General] Celestial Fury:
android.appwidget.action.APPWIDGET_UPDATE is in the guide. For the others: Post #3 How to find problems with limited alarms/wakelocks No. 1.

Don't limit com.android.internal.telephony.data-stall then or reduce the limited time. Processes cannot be limited by Amplify.

Thanks. It says sync right in the wording - it's an old one and I don't remember my thoughts about it back then but I've updated it and struck it out since it no longer drains and updated many others.

See Post #3 * how to test * properly then there'll be room to chime in.

If you're asking if it can be limited, it's in the guide. If you're showing that it's running wild, yes - alarms and wakelocks are known to do that.

If anyone wants to help test, see the end of Post #2.
[Android General] misterhong:
im on note4, i flash a new custom rom and restore my amplify backup.

now whatsapp often get delay notifications. any help?

i follow the instruction from post#1
[Android General] koboi.ngangkang:
hi. thanks for your guide. I have done most of your guide. here's my bbs dump. is there any I can mess with?:D

yes I use 2 whatsapps in my phone, I use web.whatsapp both of them, I use (sometime) maps, yes location is set on high accuracy ( I am too lazy to turn it off. :p), yes wifi is mostly always on (I am too lazy to turn it off. :p)
[Android General] Ad.Shk2:
Does anyone know the regex to limit android.net.netmon.lingerExpired ?
[Android General] ianmacd:
You don't need regex for that. Just match the literal string.
[Android General] arunkafley:
android.net.netmon.lingerExpired_[0-9]+_[0-9]+

and

android.net.netmon.lingerExpired_[0-9]+_-?[0-9]+

both to 9999999
[Android General] wonsky21:
I'm a bit confused with that part. Can I control location alarms (marked blue) or they are fine? I use location only for navigation apps.
[Android General] ianmacd:
You can limit them, but with the effect of reduced reliability in location and activity (walking, running, in vehicle, etc.) detection.

Try limiting them and see if you can live with the results. You may not even notice a difference.
[Android General] wonsky21:
OK.

Now, for example, instead ALARM_WAKEUP_LOCATOR I have com.google.android.location.ALARM_WAKEUP_LOCATOR. Are these the same?
[Android General] ianmacd:
They are indeed.
[Android General] hazote:
Thanks, I will try
[Android General] Brutal_Master:
Here is something I've been wondering for months so I'd greatly appreciate if someone could explain it.

WHY are we limiting alarms if alarms themselves to not "wake" the device but only cause wakelocks to fire which in turn do? I would think if we ONLY limited wakelocks it wouldn't matter how often alarms were fired right??
[Android General] DB126:
Same logic applies to wakelocks. Most don't actually 'wake' the device nor use a fraction of the cumulative time attributed to their presence. A few abuses have been generalized to all.
[Android General] ianmacd:
Exactly. And logic dictates that there's no point having the alarm that activates the wakelock if you're not going to use the wakelock, so it's more efficient to trap the event at source, i.e. at the alarm level, if you possibly can.
[Android General] DB126:
Why screw with innocuous alarms in then first place? I only go after those that have a clear (demonstratable) correlation to excessive drain or some other undesirable behavior that cannot be mitigated another way. On most devices that number is zero.
[Android General] ianmacd:
I quite agree.

In saying it was better to attack the alarm than the wakelock, I was answering [MENTION=5163181]Brutal_Master[/MENTION], who asked why one would want to limit alarms, if it's actually wakelocks that keep the device awake. My point was: When you can limit either the wakelock or the alarm that triggers the wakelock, go for the latter. It's more efficient.

But yes, more important is knowing when to leave well alone.

There seem to be a few schools of thought when it comes to Amplify: the minimalist school, that seeks to restrain only the errant and excessive from unduly draining the battery; and the limit-everything-in-sight club, that seeks to eke out every last nanoampere of battery consumption and stamp it out.

I'm much more on the minimalist side of the fence. If it ain't broke, don't fix it; and if it don't drain, don't limit it. Even the wakelocks that do drain battery can usually be tamed by reconfiguring software to be less aggressive.

Amplify is a blunt instrument, a useful instrument when nothing else will do, but a blunt instrument nonetheless, and therefore close to a last resort.
[Android General] DB126:
Excellent post. Thanks for clarifying your original response (my bad). As for the rest - I couldn't have said it better. Last sentence sums it up perfectly.
[Android General] Ad.Shk2:
Thanks bro. I'm gonna try it.

---------- Post added at 04:01 AM ---------- Previous post was at 03:56 AM ----------

I've got another log for today, if someone can see what's wrong here.... list 8% last night, almost 1% per hour.... no location, no Bluetooth on.

https://drive.google.com/file/d/0B-YehMCBHI-nYV8yUk5yWmZkZWs/view?usp=drivesdk
[Android General] sl___:
I have not applied the stuff in the guide as I was hoping to keep what I amplify to a minimum. I was hoping someone could take a look at my BBS file first. Idle dump is 0.5%/h but the most I can get for use is 4h SOT and 21h usage. Anyone anything I can do to help? (looks like it will probably involve amplify, but was curious to see if there's anything I can do besides that). Looks like I get a lot of nlp wake locks and Android.gms alarms during use.

I'm using oneplus two cm13/boeffla kernel.
[Android General] skivnit:
Its weird really u cant optimize it more as u have 98% of deep sleep i dont get how u lost 8% when the phone has slept almost 99% of the time. Btw u could limit nipwakelocks but dont think it will make a difference
[Android General] Portgas D. Ace:
Yeah, you should use Amplify to limit those location-related wakelocks and alarms.

But more important: if you want good battery life, don't use FB Messenger. Use FB Lite or any other alternative client. They are far more battery friendly.
[Android General] DB126:
An older battery with diminished capacity can exhibit this behavior (non linear discharge).
[Android General] wxfreak:
Another overnight run on wifi. Can I improve my drain? Thanks!
[Android General] sl___:
I have applied some Amplify settings and did another idle BBS log. The weird thing is although there's less wakelocks, I had 1%/h drain over the 6 hours, which is worse than the previous one with no xposed/amplify (.5%/h)??! Can someone review this with me? Thank you.
[Android General] TNSMANI:
Pull another dump on airplane mode and post it here. Also do you have screenshots of the battery history details from SETTINGS>Battery for the dump already posted by you? How old is the battery?

---------- Post added at 02:24 PM ---------- Previous post was at 02:20 PM ----------

I think that this is the best you will get. You have signal issues and you are on mobile data. Given these, the drain is acceptable.
[Android General] ahmad albab:
guys. i'm new and noob here. how to attach a file? i idk how attach my BBS file. thank you.
[Android General] Arcendus:
Would any of the recommended Amplified alarms/wakelocks here potentially cause issues with Smart Lock? I've been having problems with Trusted Places on my Nexus 6P out of nowhere, and no amount of resetting Smart Lock and clearing Google Play Services data has been able to fix it.
[Android General] junioramboy:
Yes. Trusted Places uses your location and if you limited the location alarms, then it won't work.
[Android General] Arcendus:
Makes sense. I'll cut back on my limiting of com.google.android.location.ALARM_WAKEUP_LOCATOR and try to find a limit that doesn't break Trusted Places. Thanks!
[Android General] abhijeet715:
Hi guys, Im new to amplify and so im a bit confused of the terms being used here. Could someone explain me what does "Allow every 7200 seconds or 2 hours" mean ? Is it like it allows that particular action to execute only for the specifies time period, or something else. With reference to the same, could someone also explain me about the "Allow every Alarms (Allow every 9999999 seconds or max)" meaning ?

Im on a custom kernel, and the battery drain is a bit too high for the device, and so i am thinking of using the steps mentioned here but i dont understand these. I also want to get notifications immediately for whatsapp, messenger and facebook, along with notifications for calendar and dont wanna miss any alarms :laugh: so could anyone help me in selecting the best step as mentioned above. It would be really appreciated. Thanks in advance :)

____

EDIT: Understood the striked part. Anyone can help me with the rest please ?
[Android General] knpk13:
Read the amplify basics first. Here. Read up on wakelocks and alarms as well.

http://xdaforums.com/xposed/modules/mod-nlpunbounce-reduce-nlp-wakelocks-t2853874/page701

Read the OP. And read even more than you post. Standard procedure for getting help is attaching a BBS dump file with your own observations. Vague posts like this without any data won't net you much.

Here's the sister thread. http://xdaforums.com/android/general/guide-extreme-battery-life-t3095884

It's currently being monitored by the very helpful Portgas D. Ace as far as I can tell. Post a BBS log there or here for more specific help.(which will take into factors like custom kernels, etc) ;)

Edit: also, use search(pick a keyword, like "com.google.android.gms") and read all posts on it by Portgas D. Ace. His posts are concise, informative, very reliable, and a good starting point for new users.(after you've read the basic documentation of course)

I'm no expert(yet), but you can PM me for OP2 specific battery life comparisons/discussion.

P.S Man, I love one piece.
[Android General] wxfreak:
Deleted
[Android General] lepa71:
Can somebody look at mine? This is drain in airplane mode. I have 7000 zerolemon battery in my S3 i535 running TW 4.3 and it could be that the battery is just getting old.

https://drive.google.com/open?id=0Bwga8b5AaM9EaVdxcnNxbGp3SEk

Thanks
[Android General] sl___:
What is ContextManagerWakelock? It's the biggest wakelock I get after limiting other things.
[Android General] DB126:
Can't answer the question but have had recent success quelling this aggressive wakelock and associated battery drain by clearing all cached data from Google Play Services. Might be a placebo as the 'fix' hasn't been extensively tested. Does not appear to have adverse side effects so worth a try IMO.

Credit to [MENTION=7559860]blackson1c[/MENTION] for suggestion.
[Android General] skivnit:
Gor the same thing
[Android General] davidred7697:
Context manager wakelock is also an insane battery drainer and as soon as I try to limit it, my phone starts draining like hell and it gets hot. About 1% drain per minute with låt and other "icing" and "Google search" wakelocks/alarms/services limited.
[Android General] DB126:
Also experiencing the ContextManagerWakelock on a device that historically slept like a baby without the use of Amplify or similar tools. Have the regex to limit this pup; see how it goes.
[Android General] DB126:
I found limiting the alarm 'com.google.android.gms.location.fused.SEND_LOCATION_IN_SMD_MODE' dramatically reduces the frequency of ContextManagerWakeLocks and allowed device to easy enter deep sleep. While ContextManagerWakeLocks can also be limited but this seems unnecessary as it does not appear to drive up CPU activity or actually wake the device. For some there may be side effects to limiting the above alarm including sluggish recognition of physical location changes. 600 seconds works for me but probably isn't the right number for everyone. Hopefully Google fixes this or someone comes up with a better solution. I'm not a big fan of limiting alarms/wakelocks as there are frequent side effects that many not always manifest cleanly.
[Android General] beefx:
Guys, how i can export all my limited alarms and wakelocks?
[Android General] ianmacd:
Use a third-party back-up program.
[Android General] Durrz:
-deleted-
[Android General] saifkhan9187:
Please help me

Kindly check the bbs log and recommend settings.
[Android General] Durrz:
Any help would be greatly appreciated :)
[Android General] Portgas D. Ace:
Alarms: 38, Intent: com.kingstudio.purify/com.kingroot.kingmaster.network.statistic.performance.report.mgr.AlarmBroadcast -> Purify is the main reason for your battery drain. I would recommend to uninstall it as it is just a task killer without any real value. Instead, it drains your battery.

BetterBatteryStats version: 2.1.0.0 -> update BBS to the latest version (2.2.0.0B6, can be found in the BBS thread here on XDA) and post another idle log file as "alarm" stats are incomplete

Screen On (): 1 m 21 s 0.4% -> try to minimize this time, save the log file right after you turn on your screen
[Android General] hazote:
finally : 0.0% drain per hour (and 0.0% for 9h ... ) !

(under Z5C and with kernel from http://xdaforums.com/z5-compact/general/9-battery-drain-overnight-97-deep-sleep-t3382145)
[Android General] MustangLife03:
One of the best battery saving write ups I've ever read. Great Job
[Android General] carlitobahsoun:
can u share ur amplify setting plz????

N920c/64g/infinity new ux (by lam 1990)/ xposed : powernap+greenify+amplify/ arya mod sound
[Android General] pijes:
I only use amplify and servicely to limit things. Still managed to get flat graph when idle
[Android General] wonsky21:
Can you share, what servi es you blocked in Servicely?
[Android General] hazote:
I tried to only limit process that consume batterie on MY phone: I didn't limited process show on the thread that doesn't appear on my phone.

Wifi,GPS,NFC allways off (put in On manually when needed)

First with know process (following this thread), then with unknow and a lot of backups :)

(I use power nap / amplify / greenify a little)

don't know hoto share amplify settings, but screen can helps:
[Android General] carlitobahsoun:
thanks a lot brother

N920c/64g/infinity new ux (by lam 1990)/ xposed : powernap+greenify+amplify/ arya mod sound
[Android General] pijes:
All apps that I don't want to run in the background, including all Google Play stuff. When in standby/idle, I only want my phone to accept phone calls, sms and whatsapp messages.
[Android General] Durrz:
As requested, please see attached :)
[Android General] Portgas D. Ace:
Alarms: 22, Intent: com.facebook.rti.mqtt.e.e.ACTION_INEXACT_ALARM.MqttLite.com.facebook.orca -> related to FB Messenger. It's up to you to decide if you want to use FB Messenger and live with the drain or to install an alternative, more battery-friendly client such as FB Lite or Metal for Facebook.

Alarms: 14, Intent: com.viber.voip.action.KEEP_ALIVE_RECEIVE -> in case you rely on instant push notifications, there isn't much we can do here

Alarms: 6, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_2791013 -> use Amplify's regex function to limit those kind of alarms (CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]{3,} and limit it to 9999999)

Alarms: 7, Intent: com.uc.action.push.utils.alarm -> related to UC Browser, which can be greenified if you don't rely on push notifications from the browser. Otherwise, limit it to an amount that suits your needs (for example 3600 for push notifications once per hour).

Alarms: 7, Intent: com.laurencedawson.reddit_sync/.receiver.MessageReceiver -> this one is strange, it's related to Sync of reddit, but shows up under Textra. Does extra has any reddit-implementation that you know of? You could limit it to 7200 or any other value of your choice.
[Android General] Durrz:
Wow. Thanks for the detailed assistance!

To answer last paragraph, I'm not sure why it shows up that way. Textra and Sync are totally unrelated on my end. At least I think it is.
[Android General] TNSMANI:
You were on mobile data for which this drain is more than acceptable.