yashsingh1/xdaforums huggingface dataset:
[Android General] Celestial Fury:
It doesn't drain in idle. If it does then something is wrong. You'll have to test it yourself.

com.microsoft.azure.engagement.service.p@[0-9]{5,}

Modified from ALARM_WAKEUP[0-9]{4,}. I presume xxxxx are numbers.

Thanks. I'm using a black theme but it should automatically change the colour to white so there shouldn't be any need to add white colours - now removed.

I believe he's talking about heartbeat alarm. It's related to push notifications.

The guide is based on an idle phone. You've used the phone so alarms/wakelocks are normal and will happen more often.

Do NOT limit anything that doesn't drain for you (unless it's ads or privacy related). This can be found in Post #3 and has now also been added to Post #2.
[Android General] Celestial Fury:
Have you investigated this? And this?
[Android General] demoncamber:
As for the custom regex, I've seen suggested configs of ALARM_WAKEUP[0-9]{4,} or ALARM_WAKEUP[0-9]+ and 9999999 seconds

Which one is considered the best config at this current time?
[Android General] pvnsai73:
Tq for replying [MENTION=5401012]Celestial Fury[/MENTION]
[Android General] renolz:
Yeah i realized that after getting help figuring out which one was causing the clock time freeze :) I searched for all the wakelocks/alarms from the guide manually so i guess when i wrote android.intent.action they all came up and i must have clicked the wrong one..

On a side note: when you say "It's also in Amplify itself", do you mean that some of the alarms/wakelocks you have to add when they are not in the list? I mean, i only added the ones that amplify found when i searched for them :P Wild guess i'd say about 40% of them was not found while searching, should i add these manually in amplify? Or do these go under the "Do NOT limit anything that doesn't drain for you"?

EDIT: Just saw a few posts up a guy asking the same thing, so nvm this.

Anyways, great guide! Helps alot for the battery hungry s6 :)

- Renolz
[Android General] TNSMANI:
We are talking about Heartbeat Alarm, aren't we?

---------- Post added at 06:15 PM ---------- Previous post was at 05:58 PM ----------

When you don't find a wakelock or alarm in your phone, don't go about manually typing them and limiting them. You will not get all the wakelocks/alarms that are mentioned in the OP because it is an exhaustive list containing wakelocks/alarms for LP and MM.

What he meant when said that it was in Amplify itself was that if it appeared in Amplify, it would appear under the heading Not Safe to Limit. So limiting something appearing under that heading is at your own risk.
[Android General] demoncamber:
Well I'm a bit stumped on this one. Any ideas what could be causing this drain and what I should limit?
[Android General] Portgas D. Ace:
Android System and Android OS are shown as drainers, you might be affected by the MobileRadioActiveBug. Read about it and a solution here.

Furthermore, your stats (Amplify) show a lot of Lockbox-related things, those are related to Android Device Manager. If you don't use it, you can turn it off via Settings -> Security -> Device Administrator.
[Android General] demoncamber:
The mobile radio bug is for lollipop only right? I'm on marshmallow. Could It be wifi calling from T-Mobile?

Also I do use Android device manager, can anyone suggest a better alternative?
[Android General] Portgas D. Ace:
It might be, but without a proper BBS idle log file, there is just guessing around. Refer to the OP and upload an idle log file, so that Celestial Fury or someone else can help you.
[Android General] djurkash:
Hi to all...

I am following this thread for some time, but haven't done any of the adjustments yet...

I believe I don't have issues with third party wake-ups, only kernel related, so the adjustments can not help me, but here are mine idle bbs logs to confirm:

First one is with "normal" sleep, wifi and Bluetooth On (connected to home router and to gear fit), rest is off...

Second one is with all services Off, except for mobile networks (mobile data is Off, auto sync too). Here I've enabled aggressive doze, but that is the only thing enabled in greenify...

sent from e6533
[Android General] darthaled:
I follow this guide, but something delay my Whatsapp notification, d'you know what it could be?
[Android General] Portgas D. Ace:
Did you limit anything with a red cloud symbol? Those are known to delay push notifications.
[Android General] demoncamber:
Say no more! Totally forgot you could even do that [emoji23]
[Android General] -Zeppelin-:
Yeah, I did, but somehow it didn't work.

I guess it's due to the fact that it's a leaked rom from qualcomm, so it's working really well on some configs, not on mine...
[Android General] jason504:
I have a question what is this no signal and no connection? I have a full signal I am on WiFi.
[Android General] Celestial Fury:
[MENTION=6932373]elpipo87[/MENTION]

There is no mobile radio drain but only a time reporting bug which has since been corrected from its initial claim in this thread. I do not use it since I do not see any bug and I try to keep my Xposed modules to a minimum.

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

qpnp_fg_memaccess (): 7 m 11 s - Kernel draining

system (Android System): Uid: 1000 Sys: 18 m 18 s Us: 4 m 31 s - Android draining

Need to see the individual details in these

com.google.android.gms (): Wakeups: 25 (4.3 / h)

android (): Wakeups: 12 (2.1 / h)

com.android.bluetooth (): Wakeups: 23 (3.9 / h) - your gear fit

The signal does not refer to WiFi but to the cell radio signal. I doubt BBS can identify types of signals or even if there are types or if it should even matter. I always take it to read as Signal on: xxx mins since BBS can identify the time length of the signal but good luck trying to get BBS to make a simple wording correction.
[Android General] jason504:
Thanks for the reply. That's what I was talking about I have a full cell signal. At least I have almost full signal. But it always says that I just never have looked in to it until now .
[Android General] Asiier:
Hey guys, check the stats I got during the night

There is like 30 second of awake time (because I greenify Google Services and Whatsapp)

But I still getting some "significant" drain, I just wanted to confirm If the problem is related with the kernel or cpu

Because I remember that on my G2 I could get up to 11 min of awake time and 15 hours of sleep with out losing 0.1% of battery
[Android General] TNSMANI:
Ofcourse the language could have been better but what it means is that either you had no cell signal or you had no known signal. In other words, though you might have had full cell signal, BBS does not know the source.
[Android General] phanipk:
hi here is my 8hours idle dump stat. from 100% to 86% in 8 hours of idle.any help??
[Android General] darthaled:
Solved.

It was an hided function of my rom, after the flash of the last update Whatsapp wasn't whitelisted.

sent from a White Aries
[Android General] djurkash:
I don't see much problem in that log, there were few wake-ups, but not so much...Looks like mobile network is draining too much...what was mobile signal strength during these 8h?

sent from e6533
[Android General] phanipk:
thanks for ur reply

ya im having network problem in my area. but because of only network problem i lost 14% battery ???
[Android General] darthaled:
Yes it happens.

I use Intelli3g with Xposed to switch in 2g when I'm with wifi at home, always max signal strength.

Without it phone use to automatically choose 4G with very poor signal.

sent from a White Aries
[Android General] rdoane:
Has anyone found a solution for these kernel wakelocks?

qpnp_fg_memaccess

qpnp_fg_update_temp

qpnp_fg_update_sram

Reading through several threads it looks like it occurs on stock (what I'm running) and Pure Nexus. However no one seems to have a solution.

FYI I am also running ElementalX 1.17.

Thanks in advance!
[Android General] DanielF50:
FYI, I've just noticed that blocking "Icing" in conjuction with the latest version of Google Play services (9.0.83) (on my N4, N5 & N6P) causes Chrome, WhatsApp, Google Play Store, Google Play Services, Dialer etcetera to FC, just incase anyone just it updated and wondered why everything was FC'ing after the update.

Icing isn't mentioned in the OP, but Amplify states that it is safe to limit, though it doesn't currently seem that it is with the latest build of GPS.

Edit, apparently this is common knowledge on the Amplify thread, who knew! (my GP services hasn't updated in 2 months, haha)
[Android General] Sveneezy:
So you're telling me that if I remove Icing from the sleep list everything will work again?

Let us try.

So far so good... Wauw
[Android General] jason504:
I was just about to say this Chrome keeps Fc
[Android General] jide1:
The same here , all of a sudden Google chrome and Google play services started crashing , the google play services error kept popping up every second, i barely could get access to amplify ,managed to access Amplify and reset to defaults and hey !, the error pop up stopped immediately.Funny thing is that i installed Amplify a few days ago and limited recommended wakelocks\alarms, and did not have any error message till yesterday , what exactly is the cause ?
[Android General] DanielF50:
;)

Hope this helped!

A recent Google Play Services update (probably updated in the background) caused blocking "Icing" to be unstable, you can re-enabled Amplify and just disable the blocking of "Icing" under wakelocks & it should stop Chrome etc from FC'ing.

---

I've got another issue now though, my phone is being held awake by the wakelock "CmaSystemUpdateService" (awake 8m, phone has been booted 8m) & it's not on the Amplify services/wakelocks/alarms catagories, so it's just destroying battery - anyone find a fix for this? Seems to happen on my brothers M8 too since the GPS update.

edit: followed this guide to fix the battery issue: http://xdaforums.com/general/general/fix-fix-systemupdateservice-wakelock-t3060548 - only, I disabled every "SystemUpdateService" listing instead of just those three (2 of them didn't even exist), re-enabled Amplify and my battery is back to 0%/h drain again! :)
[Android General] jason504:
Yes taking Icing off stopped all the FC
[Android General] Sveneezy:
I do notice Google Maps FC whenever I want to its directions to get somewhere.
[Android General] Adamask:
Someone can help me tame more wakelocks?
[Android General] DB126:
Wakelocks are an unlikely source given near linear drain curve. Look for a misbehaving app.
[Android General] Adamask:
I will do that. Thanks
[Android General] djurkash:
Looks like gmail caused most of the issues. The rest are Google play services. Just reboot your phone, and do again log, it'll be better...

sent from e6533
[Android General] Audipower:
Hello has someone tested "com.google.android.location.internal.action.ULR_BLE_SCAN_Alarm" is it save too Amplify it ?
[Android General] phoberus:
I saw, that I should block the alarm "com.google.android.intent.action.MCS_HEARTBEAT", but I have just the "com.google.android.gms.gcm.HEARTBEAT_ALARM" alarm. Should I amplify this?

Is it safe to amplify com.whatsapp/.AlarmService?
[Android General] NoyNoying:
Please help me guys....

6 hours 5% lost in battery. How can I improve this? Please help me guys in how to improve battery....

:crying::crying::confused:
[Android General] djurkash:
I've limited all alarms and processes as described in the beginning of the thread, and the situation is even worse. Phone was in idle with mobile networks, Wi-Fi and Bluetoothon, and I understand kernel wake locks caused the drain, but can something be done about this?

sent from e6533
[Android General] TNSMANI:
You have drain associated with BT and wifi apart from kernel wakelocks. Do you require BT even during sleep? For wifi, try to allot static IP for the phone. Heartbeat alarm is also draining battery. You can limit it if you can bear with delayed push notifications.

For kernel wakelocks, you can try another kernel. Apart from these, I don't find any other issue.
[Android General] djurkash:
Thanks Tnsmani,

well, I use openfit app, for connecting phone and samsung gear fit, it's via 4.0LE, and shouldn't be an issue, and yes, I'd like to have it through the night too.

Anyhow, I'll do another idle log, with all turned off (airplane mode), but I've done it before, and result was around 1.1%/h, so slightly better.

Regarding Wi-Fi , I already have a static IP address from my current ISP. I suppose you don't mean at some phone settings, which I don't see...

For heartbeat alarms, what processes should I limit and to which ms value, is it:

Regarding kernel wakelocks, yes idle consumption is rather high at Z3+, and we still don't have custom kernels, hopefully devs will do smtg in this direction...

Thanks again

sent from e6533
[Android General] TNSMANI:
For wifi, if you use a modem, the static IP is to be set there.

For heartbeat alarm, the one you identified is to be limited. Start with 3600 which will delay notifications by one hour and see how comfortable you are with the setting. If not, you can raise or lower the limit as you wish.

So use of BT and no alternate kernel mean that this is the best you will get.
[Android General] Brutal_Master:
Anyone happen to know if I can reduce the wakelocks for com.google.android.gms/.icing.proxy.SmsMonitorIntentService ? It appears to be another google service so I'm surprised no one else has mentioned it but it gets fired A LOT.
[Android General] ianmacd:
How often it gets fired is much less of an issue than how long it's cumulatively active. One errant wakelock could hold the device awake for a minute, while several thousand others might amount to mere seconds.

If it's really eating a lot of time on your device, make sure you know how to recover from a bootloop and then try gently limiting it. if that works without adverse effects, increase the wait time until you're satisfied or something bad happens.
[Android General] djurkash:
Hi Tsnami, could you check last night's log:

I've disabled all connections, and turned airplane mode on, and the best I've got it's still pretty high: 0.8%/h

Both awake time (2mins) and SOT (<1min) were ok

What I see strange is PowerManagerService.Display which should show how long screen was on, is showing 10mins !?

qpnp-smbcharger-ffffffc0c0097400 is probably related to Qi charging case (I charge my phone wirelessly) but this is first time I see this wakelock that high

qpnp_fg_memaccess and wlan_rx_wake are pretty low now, so no issues there

Regarding processes I only see com.sonymobile.xperiaweather.Weather a troublesome, is this too high?

Alarms are on the minimum as expected, as no data connection was available from any source, so even HEARTBEAT is ok....

And, this takes us to CPU states:

CPU States

==========

1.56 GHz (): 2 m 18 s 0.6%

1.48 GHz (): 13 s 0.1%

1.34 GHz (): 27 s 0.1%

1.25 GHz (): 39 s 0.2%

960 MHz (): 1 m 47 s 0.5%

864 MHz (): 13 s 0.1%

768 MHz (): 13 s 0.1%

672 MHz (): 8 s 0.0%

600 MHz (): 13 s 0.1%

460.8 MHz (): 10 s 0.0%

384 MHz (): 9 m 53 s 2.6%

Deep Sleep (): 6 h 1 m 42 s 95.7%

Pretty high SOC usage to me, especially at max frequency, also this 10mins at minimum frequency correlates with SOT, so, really strange to me...

And, again 0.8%/h , I think is too much, seeing what others manage...

Any ideas? Thanks...

sent from e6533
[Android General] Jimmy1life:
So glad i found this thanks
[Android General] TNSMANI:
Statistic Type: Unplugged to Current

Since 6 h 18 m

No or Unknown Signal (): 6 h 2 m 2 s 95.8%

I don't know why there is a difference of about 16 minutes in the above statistic. It should have been 100%.

Kernel wakelocks are your culprits. Since on aeroplane mode you get 0.8% drain, your idle drain can not be lower than that. So your current idle drain is ok in the circumstances.

If you want to reduce the drain further, your only option AFAIK, is a ROM/kernel change.
[Android General] aidy.lucas:
Link to my new working regex blocking for Google play services alarms

CONTEXT_MANAGER_ALARM_WAKEUP_XXXXXX to replace ALARM_WAKEUPXXXXXZ

http://xdaforums.com/showthread.php?p=66986424

D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more
[Android General] lazer155:
Deleted
[Android General] rdoane:
Does anybody have experience with limiting the alarm titled com.google.android.gms/.vision.DependencyBroadcastReceiverProxy?

---------- Post added at 11:05 AM ---------- Previous post was at 11:04 AM ----------

I'm also getting a lot of these alarms. I just wrote a regex to limit them, will report back on if it breaks anything.
[Android General] Epsil:
Hi,

Please help me, my phone lost 3% per hour.

Not enter in deepsleep ?

http://cloud.tapatalk.com/s/57480fd98f3fa/BetterBatteryStats-2016-05-27_111106248.txt

Envoyé de mon LG-H815 en utilisant Tapatalk
[Android General] DB126:
You need to help yourself. Read and learn; this thread is filled with useful information. Then ask specific questions as needed.
[Android General] Epsil:
Your answer does not help me much. I have already traveled the guide, I use Amplify and Greenify any two set as recommended. My phone hardly ever enters deep sleep, only Doze sessions. 15% lost in one night from 7 am barely.
[Android General] :
If as you say phone doesn't enter deep sleep, then this guide is not useful i think for you.. I would suggest a factory reset..

When your phone works ok, and enter derp sleep then folow this threat to make battery better.
[Android General] TNSMANI:
If you had read this thread fully as you claim, then you would have known that only an idle dump will help others to help you. What you have supplied is a dump from boot to current that too while charging. This is useless. This information is available in the first page itself and in almost every alternate page.

If you can't help yourself, the least you can do is supply proper information so that others can attempt to help you.
[Android General] Epsil:
Hi,

Sorry for bad dump.

http://cloud.tapatalk.com/s/57495ef265a73/BetterBatteryStats-2016-05-28_110256013.txt

Thanks for your help.

Envoyé de mon LG-H815 en utilisant Tapatalk
[Android General] TNSMANI:
This is the same dump.

Did you read my post fully?
[Android General] Epsil:
I don't have choice

Envoyé de mon LG-H815 en utilisant Tapatalk
[Android General] TNSMANI:
Why?
[Android General] Epsil:
I can't change. Only boot. I reboot my phone it's same.

Envoyé de mon LG-H815 en utilisant Tapatalk
[Android General] Celestial Fury:
You're misunderstanding. Instructions on

How To Test

are in Post #3.

Step 1

is always Charge battery to full (100%). Follow the instructions.
[Android General] arunkafley:
Can someone please help me I am having bad battery drain.

View attachment BetterBatteryStats-2016-05-31_092538090(1).txt
[Android General] Celestial Fury:
Level lost [%]: Bat.: -11%(100% to 89%) [1.7%/h]

Wifi On (): 7 s 0.0%

No Data Connection (): 10 s

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

Alarms: 4, Intent: com.google.android.gms.gcm.ACTION_CHECK_QUEUE

It shouldn't drain this bad with WiFi/data off. Establish the baselines in Post #3 first.
[Android General] arunkafley:
Seems to be a kernel problem. Installed Boefflla kernel and now its much better

View attachment BetterBatteryStats-2016-06-01_071028361(1).txt

Is there anything else that can be done to improve the battery drain?
[Android General] phanipk:
hi here is my 6 hours idle dump stat. from 100% to 86% in 6 hours of idle.any help??
[Android General] pvnsai73:
There seems the problem with entering in doze mode...use aggressive doze frm greenify which disables all sensors
[Android General] phanipk:
thanks for ur reply

already im using aggressive doze frm greenify
[Android General] dipseeet:
i have a (stupid?!) question:

should i greenify whatsapp?
[Android General] ianmacd:
That depends on a number of things, not least of which is your usage pattern.

Do you use it a lot? If so, definitely do not greenify it.

In my opinion, hibernation has been superseded by Agressive Doze, anyway. I hibernate only 2 apps. The rest I leave to Aggressive Doze.
[Android General] demoncamber:
Anyone see anything here I can limit and by how much?
[Android General] ianmacd:
The Facebook wakelock for a start.

I would uninstall the anti-virus package. That stuff doesn't belong on a phone, IMHO. If you insist on keeping it, try limiting it and see what happens.

You can certainly tame those location wakelocks, but depending on what you're doing with location services, you might notice a downside. Ditto that location alarm.

The rest of the alarms I would personally leave alone.
[Android General] demoncamber:
Ok will do. I'm still getting some nasty idle battery drain even after following both amplify power saving threads, trying to figure out what else I can limit within my highest offenders.
[Android General] ianmacd:
Have you collected an idle log from BBS? That should help pinpoint what's going on.
[Android General] pvnsai73:
What is this alarm in kernelwakelock draining my battery??...any ideas???...any help would be highly appreciated
[Android General] Th3DaRk_Vampire:
What is that 2 first process??? I don't have activate any powersaver on my display
[Android General] dipseeet:
i'm on kitkat so i don't have this doze mode.

i always hibernated it but since i am using amplify i have those push delays.

and i don't know which Alarms and WL's i should limit or unlimit to get those pushes without delay.

i already looked at the OP and left those unticked with the red cloud. but i still get those delays even without hibernating whatsapp anymore.

i'll post a dump asap so someone may look at it and help me.
[Android General] TNSMANI:
They relate to your screen on time. Don't bother about them.
[Android General] ianmacd:
It's hard to know what to advise without seeing your current configuration.

If you're seeing push delays with your incoming WhatsApp messages, you should unlimit any wakelocks and alarms with GCM in the name. Those are related to Google's cloud messaging.

If you still see delays then, disable Amplify altogether. Perhaps your problem isn't even related to it.

If the delays disappear, you can start to disable wakelocks and alarms again until you see the problem return.
[Android General] dadr0p:
Hi, I followed the guide and I lost my Gmail notification. I dug through forum and thought that the heartbeat alarm limits may cause the issue. So I unlimited it but the Gmail notification has not return. Any suggestions would be appreciated.
[Android General] TNSMANI:
Did you reboot after unlimiting?

Also try reinstalling Gmail.
[Android General] dadr0p:
I did reboot, wiped dalvik, cache and reinstalled Gmail. Still nothing.

Finally, I disabled Amplify module and Gmail notifications are back.
[Android General] ianmacd:
When using a tool as invasive as Amplify (or really any tool at all), it's best to take an incremental approach. Apply a single change and observe the results. If nothing untoward is seen, repeat the cycle. If strange behaviour is observed at any point along the way, you're almost certain to know what caused it.

What no-one should do is take the guide in the OP and apply it in blanket fashion to a completely different device, possibly running a different version of the OS, or a different kernel on a different ROM. That's just asking for trouble. There are too many differences in hardware and software for that to be a safe thing to do, and it will be a painstaking chore to find the source of any given issue.

Even limiting all of the wakelocks and alarms that Amplify itself says are safe to limit is an unsafe thing to do. That's not just my opinion; it's a fact that the recent problems with the icing wakelock have demonstrated. What's safe today may not be safe tomorrow.
[Android General] demoncamber:
What wakelock or alarm would be directly responsible for sms messages? I'm getting some failed sms messages here and there, not sure which did it.
[Android General] Vuska:
what is this do ?

thank you