yashsingh1/xdaforums huggingface dataset:
[Android General] espaciox99:
Anyone help me ? 1.3%/h :( thanks
[Android General] skivnit:
It must be related to ur battery u have a 98% deep sleep. U can try and assign a fixed ip since dhcp is waking ur phone and change app widget update in amplify
[Android General] espaciox99:
I could explain that I have to do ?
[Android General] DB126:
There are dozens of pages and hundreds of helpful posts in this thread. A targeted search will likely yield the information you seek.
[Android General] Wasabi Ice Cream:
This guide changed my life. Thanks!
[Android General] misterhong:
hey please take a look at my dumpfile and need advices.

thank you

cc: [MENTION=5901790]Portgas D. Ace[/MENTION]
[Android General] Portgas D. Ace:
Several kernel wakelocks, check this thread for a possible solution.

Alarms: 10, Intent: com.google.android.location.ALARM_WAKEUP_ACTIVITY_DETECTION -> this one should be in the OP

Alarms: 6, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_808849 -> this one is also in the OP, use Amplify's regex function

Alarms: 17, Intent: jp.naver.line.android/.alarm.LineAlarmReceiver

Alarms: 19, Intent: jp.naver.line.android.legy.SpdyHeartbeatChecker.sendPing

Alarms: 12, Intent: jp.naver.line.android.legy.SpdyHeartbeatChecker.check -> related to Line and required for a proper functionality

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

Alarms: 17, Intent: com.sec.spp.push.REQUEST_TIME_OUT_ACTION -> related to Samsung Push Service

Alarms: 25, Intent: com.facebook.rti.mqtt.keepalive.KeepaliveManager.ACTION_INEXACT_ALARM.MqttLite.com.facebook.katana -> related to Facebook app. You can limit this one to 3600 if you are fine with push notifications arrive once per hour.

Alarms: 25, Intent: com.facebook.rti.b.e.f.ACTION_INEXACT_ALARM.FBNS.com.instagram.android -> same as for Facebook app above

Alarms: 23, Intent: net.myinfosys.permata/.simplepay.service.SimplepayRealtimeAlarmReceiver -> related to PermataMobile app. You can limit this one to 3600 or 7200 if you don't rely on instant push notifications/information
[Android General] SedyBenoitPeace:
[MENTION=5901790]Portgas D. Ace[/MENTION] i see that you're good to analyze the dumps from BBS...here is mine...can you tell me what's the problem? I taked the dump at the end of the day...i'm not a beginner but there is something that i cannot understand in this log...here you will see all the battery hogs apps and also music played...do you see anything else that is abnormal?

I suspect that there is a draining from kernel and also from sensors...thanks in advance!
[Android General] Portgas D. Ace:
An in-use log file is useless for analysis, as we want to minimize the idle drain. So please refer to post #3 about how to produce a proper idle log file.
[Android General] SedyBenoitPeace:
You're right mate.. However I think that I figured out the issue.. It seems that doze is faulty on Oxygen OS (at least for me)
[Android General] whiteandpurple:
Hello,

I'm struggling with the idle drain since LL update even with Amplify and Greenify installed. Recently, I installed L speed and it can reduce the loss to half (from 12% whenever screen off to 1% per 1.5 hrs), still looking for a way to be better though.

Here's BBS log from this morning. Sorry, I can't upload through XDA app and post an outside link neither. Could you look at this log please?

drive(dot)google(dot)com/file/d/0B9ps5hho5qBpWjUwd0JSUWhPQWc/view?usp=docslist_api

My phone is Xperia Z1, stock rom with 3 month battery.
[Android General] raptorskate:
I will advice you to use ForzeDoze app with Xposed, really good idle time, I had like 1% in 8 hours. Using Moto X Play!
[Android General] Asiier:
Hey guys, I haven't checked the topic for a while

Can someone explain to me why is not longer optimal to limit WhatsApp alarms?
[Android General] whiteandpurple:
Thank you so much raptorskate. I doubt it will work with Lollipop, I think I'll stick with traditional ways for now. :o

Somebody help me read my log, please.
[Android General] Celestial Fury:
Alarms (requires BATTERY_STATS permissions)

Network (requires root)

Root permission granted to BBS?

Recent updates to WhatsApp have removed the drain from those alarms so they've been struck out.
[Android General] whiteandpurple:
Yes, it's granted. There's also no alarm in BBS stat screen at that time. And for Network stat, I always in airplane mode at night. Thank you.
[Android General] pijes:
You can use Amplify (paid version) and Servicely app to limit most of the things. I tried both Force Doze and Naptime but they kill AcDisplay and Glance Plus apps even though I've added them in the white list.
[Android General] whiteandpurple:
Thank you pijes, I've already limit almost everything in OP's list, Amplify helps me so much but I still have a huge drop problem (12% lost whenever screen off that solved by L Speed). I'm watching this thread for a year still want to solve by myself but thay didn't work at all so, I'm here.

I'll try Servicely then, thanks for your kindness. :o

If anyone have a time to look into my log would be appreciated. Thank you. :)
[Android General] TNSMANI:
Alarms and network are missing from the stats. Try to pull another idle dump and check whether it has those. If so, post it here.

Your Deep Sleep and Awake (screen off) times are excellent. There are no wakelocks running wild. You should not have this much drain unless your alarm and network stats give us some clue. So how old is the battery?
[Android General] whiteandpurple:
It's 3 months old and I'll try again soon, thank you tnsmani.
[Android General] bigpapa007:
Hi everyone, does anyone know what this one is for or if it is safe to limit?

I have a s7 edge and that's by far the biggest alarm on my phone.

Any help will be appreciated.
[Android General] DB126:
That sucker seemed to pop up in conjunction with the Context Manager Wakelock that has proven to be a wild boar on many devices. I have it limited with no apparent ill effects.
[Android General] bigpapa007:
Great! Thank you.

Do you also have Context Manager Wakelock limited?

What value do you have on both for those alarms?
[Android General] DB126:
I do. 900 sec for both. I know some favor larger values but I find diminishing returns on most alarms/wakelocks after just a few minutes. Sometimes a more aggressive block becomes counterproductive. 15 min is one of the longer limits I have set.
[Android General] l7ssha:
Soo nice
[Android General] :
There seems to be some conflict in the timing values and limit/disable options with this thread. Your thoughts?
[Android General] TNSMANI:
To each his own.
[Android General] DB126:
There are no rules. Use this thread and others to educate yourself and make choices that best support your personal preferences. Yes, there are a few hard dos/don'ts that you'll want to observe. Beyond that it's an artist's pallet. Enjoy!

(keep in mind stock is a reasonable choice for 95% of the population; never wander too far from home and you probably won't get lost).
[Android General] :
Thanks, I took bits and pieces from both. Hopefully the phone won't choke me in my sleep.
[Android General] Sveneezy:
Have any of you guys been experiencing random Facebook FC since their last update?
[Android General] raptorskate:
Only with Twitter!
[Android General] raptorskate:
Actually, it gives you the option with Xposed if your phone doesn't have Doze! You should try it at least :)
[Android General] :
Spoiler content hidden.

Okay, i've no idea what happened. For now I'm resorting to clean installs and not plugging in while turning on/off the phone in case I trigger this batspit crazy glitch and reverted to an older version of SuperSU ;_;
[Android General] skyred5:
I am still having context_manager_alarm_wakeup popping up on the alarms list even though I have put in the custom regex.

What I have is "CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]{4,}"

I think I have it correct. My stats were reset after putting this, so it can't be old alarm.
[Android General] raptorskate:
Is there something on this thread that keeps the clock to updating itself even though it's in Doze?
[Android General] pijes:
I had the same issue as yours, and having the same regex too. I then created 3 copies of that regex, replacing 4 with 6 and the other copies as 7 and 8. No more context manager alarm showed up in bbs after that.
[Android General] Mr.Mirajul:
How use greenefy with amplifie
[Android General] Vuska:
What is the '4' or '6' or '7' etc in regex option ?
[Android General] pijes:
"CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]{4,}"

4 as in the last section of it = {4,}

so now I have...

"CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]{6,}"

"CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]{7,}"

"CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]{8,}"
[Android General] ianmacd:
{4,} means '4 or more of the previous token', so in this case 4 or more digits.

The bottom three patterns therefore add nothing here, because everything they match is already matched by the first pattern.
[Android General] pijes:
I know, but somehow the alarm wakeup still popping up in the alarm list (amplify). Once I did that they all gone.
[Android General] haiderrkhalid:
Hey guys. Could someone please help me make sense of my BBS log? I can't seem to understand what i can limit to make my battery life better.

My current setup is Resurrection Remix 5.7.1 with Boeffla kernel version 3.1 beta 5, with Pico Gapps, and Xposed version 86, on my Galaxy S5.

BBS says I have around 0.8%/hour battery drain. The log is attached. Any ideas?

Thanks in advance!

http://cloud.tapatalk.com/s/5792e94791d31/BetterBatteryStats-2016-07-23_083224339.txt
[Android General] TNSMANI:
Your alarm stats don't have detail. Update BBS to 0B6 from XDA. Then post a fresh idle dump.
[Android General] Asiier:
I'm finally done setting up everything on my OP3 so now is time for the battery test

First Baseline test: 0.00% Drain

Second Baseline test: 0.00% Drain

First Actual test: 0.4% Drain (I believe I could get better results since I got a WhatsApp around 1:15AM and I believe the notification light have been blinking till 11PM when I checked)

Plese take a look at my BBS stats
[Android General] haiderrkhalid:
Hey, so I did what you asked. Here's the dump file. Could you help me make sense of it? My battery drain seems to have increased to 1.1% per hour..

My setup is still the same with Boeffla kernel 3.1 beta5, RR 5.7.1, Xposed v86, and Pico Gapps

Thanks!

http://cloud.tapatalk.com/s/57943a2325b65/BetterBatteryStats-2016-07-24_082029772.txt
[Android General] TNSMANI:
You have some kernel wakelocks. Look for some alternative custom kernels.

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

Alarms: 4, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_134667

The first one you can limit using Amplify but if you use wifi calling, it may create issues. The second one can be eliminated completely by using the regex function of Amplify.

Whatsapp and deskclock can also be controlled by using Amplify.

Wakelocks:

launch* (org.cyanogenmod.audiofx.AudioFX): 38 m 40 s Count:0 8.2%

*launch* (Android Core Apps): 38 m 40 s Count:0 8.2%

*launch* (com.android.dialer.Telephone): 38 m 40 s Count:0 8.2%

*launch* (com.android.deskclock.Clock): 38 m 40 s Count:0 8.2%

*launch* (com.resurrection.ota.Updates): 38 m 40 s Count:0 8.2%

*launch* (de.andip71.boeffla_config_v2.Boeffla-Config V2): 38 m 40 s Count:0 8.2%

*launch* (com.whatsapp.WhatsApp): 38 m 40 s Count:4 8.2%

*launch* (com.syncme.syncmeapp.Sync.ME): 38 m 40 s Count:0 8.2%

*launch* (com.tozelabs.tvshowtime.TVShow Time): 38 m 40 s Count:0 8.2%

*launch* (com.oasisfeng.greenify.Greenify): 38 m 40 s Count:0 8.2%

*launch* (com.ryansteckler.nlpunbounce.Amplify): 38 m 40 s Count:0 8.2%

There is something wrong with the above. All of them show the same time. May be some one with better knowledge can help you here.

I see that you have Amplify. Then why aren't you following the recommendations in the OP of this thread for setting limits? Set up Amplify as per the OP.
[Android General] Nokiacrazi:
Hi guys. Had a chance to install xposed, amplify and greenify. Have followed the guide to block certain wakelocks and alarms and greenify apps. Seems to be getting 0.5%/h as opposed to 0.3%/h that I had without xposed. Also should note that I have Android wear watch connected via Bluetooth. Custom rom custom kernel

Any help with reducing the idle drain would be appreciated :)
[Android General] haiderrkhalid:
Thank you!

Ah yes, I can't seem to understand why they show the same time as well. There's a collective *launch* wakelock in amplify but limiting it causes too many problems.

Yes I do have amplify and I've set it up as per the Original post. That's how I manage to still get 1.1%, otherwise I used to get around 2.3% battery drain per hour. It was a nightmare.
[Android General] speedy56:
Is com.android.servier.device_idle_STEP_IDLE_STATE save to limit?

I have it aprox. 9/h
[Android General] Asiier:
So apparently certain WhatsApp alarms can no longer be controlled with Amplify

They are supposed to not drain battery anymore but my BBS doesn't think so, since I end up getting somewhere between 20-50 of these alarms at the end of the day

The conflicting alarms are as follow:

com.whatsapp.messaging.CLIENT_PINGER

com.whatsapp.messaging.LOGOUT_ACTION

The rest of the alarms can be limited as the were before, but this 2 "cannot" and I say "cannot" because they can actually be limited, but after a reboot (I believe this happen whenever you limit the alarm and then reboot your phone) WhatsApp will make a new alarm called, for example; com.whatsapp.messaging.z.CLIENT_PINGER or similar

Once again, you can limit this alarm (I'm pretty sure that Amplify actually limits it but I could be mistaken) but after a reboot, you will have a brand new alarm
[Android General] ianmacd:
If this is truly the case, use a regex to trap all such alarms.
[Android General] Asiier:
Could you tell me what should I put on the regex?
[Android General] ianmacd:
Assuming that the .z in your example is always a dot followed by a single lower-case letter when it appears at all, the following should work (also for the case of the original, unmodified alarm), assuming that Amplify supports regex grouping:

com\.whatsapp\.messaging(\.[a-z])?\.CLIENT_PINGER
[Android General] Asiier:
Thank you for the answer

I get as well 2 letters (example: com.whatsapp.messaging.bj.CLIENT_PINGER_ACTION)

So it will be com\.whatsapp\.messaging(\.[aa-zz])?\.CLIENT_PINGER_ACTION

I'll report if actually works fine
[Android General] ianmacd:
No, that syntax won't work. Try this:

com\.whatsapp\.messaging(\.[a-z]+)?\.CLIENT_PINGER_ACTION

(\.[a-z]+)? means 0 or 1 instances of 'a dot followed by one or more letters'. So, this should work for:

No dot and no letters

A dot and one or more letters

Good luck.
[Android General] DB126:
The regex needed to address self propagating alarms/wakelocks is being addressed by others; no need to elaborate. That said, I question the need to limit. Just because something shows up in BBS doesn't make it bad or draining. I've seen single occurrences that devastate a device and instances where hundreds/thousands of firings per hour have no material impact. Analysis needs to go deeper than reacting to a dashboard light.
[Android General] Neuz:
Please can you share amplify setting? (screenshot or some) I'm on OP3 too :)

Thank you
[Android General] Asiier:
I have limited pretty much everything is on the OP

I know that If it shows on the BBS doesn't mean is bad, the thing is that as [MENTION=5401012]Celestial Fury[/MENTION] said: "Strikeouts mean that the alarms/wakelocks used to drain but no longer seem to but should still be safe for you to limit if they drain for you."

And those alarms are actually waking up my device from sleep more often that I would like, so that is the reason for me limiting them
[Android General] speedy56:
I thought limiting Client_pinger_action alarm kills wapp notifications... ?

Does it make much sense in limiting it if so?
[Android General] Asiier:
I didn't know that

So does it completely kill them or you get them every XXXX seconds you have set the alarm?
[Android General] speedy56:
I wouldnt know that... I was limitin it for 2h if remember correctly and I didn't get any notifications (even if they arrive after 2h it doesnt make much sense, even if I limit it by just 10mins its still quite a delay)

I'd like to get rid of that alarm, it's killing my battery with the rate of 11-12 alarm per hour ?

Strangely, I didnt have it that much before, it started a couple of days ago, maybe because of an update or somerhing
[Android General] Asiier:
I still get notifications but I guess I get them when the device is not on Deep Sleep or whenever Amplify haven't done what he does just yet

Although I don't mind getting my WhatsApp notification every, let's say 30 minutes. If someone has something important to say they will call me

My question now is; Is this the only alarm that will mess with the notifications? Because it will be interesting to know which alarms mess with notifications so I can set them to a lower value
[Android General] speedy56:
I think it is. It says so in the OP and I never had any problems with limiting Available_timeout, Client_ping_timeout and whatever the other alarms are called

Maybe Client_pinger_action going mad is related to limiting wapp wakelocks. Maybe I'll try and reinstall wapp tommorow and use it without anything limited, maybe that will calm c_p_action down
[Android General] zigbye82:
Is it safe to limit this:

com.google.android.chimera.container.IntentOperationService.MODULE_SPECIFIC
[Android General] speedy56:
So... a day after...

I've reinstalled wapp, didn't limit anything in Amplify aaaaaand..... Client_pinger_action is still rocking at about 12 alarms/h :(

Edit:

Tried to limit pinger_action now and the notifications seem to be coming normally, will see during the day
[Android General] TNSMANI:
That relates to Doze, so don't limit it.
[Android General] dirkdigles:
Noticed I'm now getting a ton of ACTION_CHECK_QUEUE alarms. I'm not sure if this is an app or what, not much has changed on my phone. I installed Firefox but otherwise can't think of something that might cause this?

Maybe new Play Services? Anyone else seeing this behavior?

I'm on a GS4, stock rooted 5.1 gpe
[Android General] speedy56:
AnyMotionDetector wakelock is related to Doze I guess? ?

It's not that active, I'm just curious ?
[Android General] Snowby123:
Limit the alarm. The more I limit it the better the battery performed in my experience. I don't know the cause of the wake lock but limiting it changes nothing but the battery life
[Android General] antroid88:
Hi! Sorry if it was covered before. Can I use the settings from the 1st post on nexus 5x or there are some specifics?
[Android General] :
Yeah, it will apply for all devices. Used for my Note and Xperia, both controlled things well
[Android General] antroid88:
Thx! Is the difference before and after remarkable?
[Android General] :
I'm not sure about the with/without Amplify usage since it's been a long time using it, but I just discovered this thread recently and compared to a guide in another thread this one suits me best.

My notifications are no longer delayed plus i can leave wifi on the whole night and there won't be a single wakelock/alarm to interrupt deep sleep.
[Android General] Hari Haran:
Link to that thread?
[Android General] :
xdaforums.com/android/general/guide-extreme-battery-life-t3095884/page1028
[Android General] Hari Haran:
Thanks mate
[Android General] snky1987:
Is anyone here with experience over: "com.google.android.gms.location.fused.SEND_LOCATION_IN_SMD_MODE" alarm ?

In 1h it was triggered over 336 times so it looks like a resource hog.

I didn't use any GPS related apps at this time at all.

Is it safe to limit ?

What is it related to (app wise cuz I can see it is a Location service in general) ?

Doe's anyone limited it and what was the effect ?
[Android General] Rohandd:
Is it okay to limit *alarm* and *launch* as these both are mentioned in partial wake locks which are keeping the device awake.. and if so, with what value should I limit them?
[Android General] DB126:
That and ContextManagerWakeLock are both related to Google location services and were introduced (or at least became more visible) in a recent update to Google Play Services. I have both limited to 900 sec on several devices with no apparent ill effects. Note I am not a fan of aggressive limiting and only go after those items that truly impact my experience in a negative way. In this case ContextManagerWakeLock was being tripped tens of thousands of times per day and blocked deep sleep for hours at a time on a device that does not have a discrete GPS chip. Really bad programming on someone's part.
[Android General] snky1987:
Fantastic. I will limit them at the same way and do some Location Services related tests.

I think if Google Maps and PokemonGo will still work as they should then I will consider it a safe option.

Will post here if I had any issues with limiting those services at all.
[Android General] Hari Haran:
Are these good? Suggest some ways to improve
[Android General] DB126:
Absolutely not.
[Android General] liquidgik:
I block "com.google.android.gms.location.fused.SEND_LOCATION_IN_SMD_MODE" alarm with value 900 and no problem with mock location, checkin or camera photo include location.

I use A-GAPPS minium (http://xdaforums.com/android/general/gapps-gapps-6-0-1-minimal-t3276606 ) on CM13.
[Android General] snky1987:
It looks lie your display eats **** out of your battery. I had the same before I reduced the 2k dipsplay to HD disaplay resolution, but this is a different discussion.

5% awake doesn't look too bad tbh.
[Android General] Hari Haran:
I have a 720p display mate, and I'm 24*7 on LTE!
[Android General] snky1987:
24*7 LTE doesn't seem to eat your battery alive here. I can clearly see from the diagram when you've been using the "screen on". I had the same on my Nexus 6p.

Apart of that when your screen is off then you have nice non-active times so wakelock wise it looks quite right.

Also it looks from the diagram that every time you receive notification you put the screen on to check it (which is normal :D).

So in this case if you want to extend your battery life and do not care to get the notifications a minute after it arrives then I would suggest to use "Aggressive Doze" from Greenify (to get rid of notifications at all apart of sms and calls when Dozing), or limit "android.content.syncmanager.SYNC_ALARM" alert so it would post prone sync. of apps by give number of seconds.

You will get less notifiactions, less screen on time and more battery life (but by giving up on being immediately notified).
[Android General] Hari Haran:
I have the non-donated version of amplify mate :v, can't limit wakelocks!
[Android General] haiderrkhalid:
Hey guys. I'm using a Galaxy S5 with RR 5.7.1, Xposed v86, and Boeffla Kernel.

I'm using the apps and methodologies that have been described in this thread and I'd like to thank everyone because it sure has made a difference for me.

My screen on time is now amazingly better. Stats are posted below:

I made some changes in configuring governors and underclocking and all, on my own that helped, but I'm glad I stumbled upon this thread. Thank you for helping me make my phone last the better part of the day!
[Android General] DB126:
So donate and recognize the developer for his/her hard work. Otherwise don't complain.
[Android General] :
If you can't afford the donation then just use what you can.
[Android General] Hari Haran:
I know that -_-
[Android General] antroid88:
Question about manual in the first post:

"Deny these Ads/Privacy related Services " - how can I deny with Amplify?
[Android General] h1ghland3r:
Select the options Services.

Sent from my Xperia Z3
[Android General] antroid88:
Is it normal that on Nexus 5X I was able to find and deny only 1 service described in the 1st post?
[Android General] h1ghland3r:
I haven't found all the services to deny as well. It really depends your apps.

Sent from my Xperia Z3
[Android General] antroid88:
Has anyone tried to delay all wakelocks , alarms and services related to facebook and twitter? Does it affect the apps? I don't care about its notifications.