yashsingh1/xdaforums huggingface dataset:
[Android General] organick87:
Since really getting into wakelocks and such, I began with Wakelock Detector and just ended up tossing it. BSS is indeed what I use to see what's draining the battery now in conjunction with Amplify. Amplify offers total wakelock counts whether they drain battery or not so I do think that that information is useful when having Amplify side by side with BBS. I also felt as if Amplify's unit of measure of a wakelock/alarm's duration ran is not just "seconds."
[Android General] 95thfallout:
Hey, first thanks for the guide, I just applied it and am measuring results and will hopefully keep everyone here posted. However I have two questions:

1) Is it expected to not be able to find many of the wakelocks/alarms/services in this guide, I can tell some are app or rom specific but some others I couldn't seem to find

2) Im no longer getting my push notifications (gmail, snapchat, FB messenger, etc) in a timely manner. Which settings in the guide affect this, so I can adjust them to a lower time?

Thanks again!
[Android General] Celestial Fury:
[MENTION=6049694]95thfallout[/MENTION]

These should be common for KitKat: location alarms/wakelocks, other android alarms/wakelocks, Facebook, WhatsApp.

The ones which have this GCM icon (currently 3) affects push notifications as well as anything with Sync in it.
[Android General] khr0n0s12:
what do you mean by this? how much time can i limit in this section? :confused:
[Android General] Celestial Fury:
[MENTION=5927935]khr0n0s12[/MENTION]

Those are the Global Positioning System (GPS) alarms. I limit them to once a day. Unless, you use apps/widgets that need to update GPS (more often) in idle mode. GPS is still near instantaneous when I need to use it.
[Android General] vesparados150:
I ve limited those tagged as location in blue at 43200 without any problems. its been a month since I did that. also I used most of google stuff such as google now etc.

I managed to keep most of my wakelocks under control except for android system(netmon.linger alarm) and WhatsApp. I've been trouble shooting those two without any results. I don't really mind the WhatsApp wake lock as I use it a lot so I cud close an eye but for the android system wake lock its really annoying and its only netmon.linger alarm everytime. I think it has something to do with androids network monitor but not sure how to trouble shoot it. among things that I had tried without any success are flashing modems, kernels etc. google is not a big explaining this either.

PS: connectivityservice. action.pkt_CNT... wasn't limited as I was testing..I would usually limit this.
[Android General] 95thfallout:
Im running lollipop 5.1 so it could help to explain some of the missing wakelocks/alarms. Thanks.
[Android General] boojay:
Just a heads up for anyone else who is experiencing delayed Hangouts messages as a result of following this guide. It appears as though limiting the following alarm was the culprit:

com.google.android.intent.action.GCM_RECONNECT

Someone else should confirm this to be accurate, but since reactivating that alarm, I'm receiving Hangouts messages instantaneously again. Everything else seems to be working as it should though and I've even limited more wakelocks/alarms than what's been outlined in the OP.

Swyped from my Z3C
[Android General] Emmyx1:
Great Share :)

Thankyou for the share :good: I was wondering if this method will be effective for Samsung Galaxy S3 and Note 3 ?:confused:

whatsappforpc
[Android General] zelleb:
I can confirm that after unlimiting com.google.android.intent.action.GCM_RECONNECT push notifications get delivered instantly. I used to get TextSecure messages only after I opened the app or connected to a WiFi network, but now it works:good:
[Android General] eywan:
Dear OP / everyone. Please refer to the attached image. Did anyone face high wakelock from rilj?(clouded in red). And is it safe to limit the 'safe to limit item'm

Thanks
[Android General] v7:
High numbers in Amplify doesn't mean that they cause the drain.Use BBS to see if it drains the battery.

You can limit the safe to limit items.But you should be careful with the numbers.Limiting it for a long time may cause conflicts.

Tapped from my furious Dogo :')
[Android General] Celestial Fury:
If it's just one or two alarms in a long idle period, I'd say there's no need to limit it.

So, I tested it out myself. DISABLED Amplify in Xposed, rebooted and sent a Hangouts msg from another phone - no notification until I turn the screen on. So, obviously, Amplify wasn't blocking anything since it was disabled. It was the Sony Stamina Mode. I had to add Hangouts to "Apps Active in Standby" and messages come in near instantly. Re-enabled Amplify in Xposed and rebooted and tested again and messages come in without having to turn on the screen. com.google.android.intent.action.GCM_RECONNECT is limited at 43200.

First, can you edit your post and remove the quote of the first post? Thanks. It should be effective for any Android phone.

[MENTION=3945809]eywan[/MENTION], what [MENTION=5867207]vaisakh7[/MENTION] said on the drain. If it doesn't appear in BBS, it is (apparently) not noticeably draining battery. As to why BBS and Amplify report differently, I don't know. Maybe somebody wants to ask in those threads?
[Android General] v7:
I've missed the notifications after limiting com.google.android.intent.action.GCM_RECONNECT.I tried it with different custom ROMs.Limiting these alarm did stop the Push Notifications.

Tapped from my furious Dogo :')
[Android General] eywan:
Thanks both [MENTION=5867207]vaisakh7[/MENTION] & [MENTION=5401012]Celestial Fury[/MENTION]

I totally forgot to counter check with BBS. Silly me
[Android General] Celestial Fury:
[MENTION=5867207]vaisakh7[/MENTION]

I guess mileage will vary? Or perhaps it's because of custom ROM that relies more on it? I'm on stock rooted.
[Android General] zelleb:
I could be wrong but maybe its because of your stamina mode? Because I don't have that on my stock Moto G and push notifications start working again after enabling GCM_RECONNECT again :eek:
[Android General] v7:
I've used Amplify along with stock KK 4.4.4 on my Xperia ZR some time ago.I remember limiting this so called alarm during that time.So maybe it's the custom ROM that makes the change.

Tapped from my furious Dogo :')

---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------

[MENTION=5401012]Celestial Fury[/MENTION] So I conclude that limiting this alarm is only applicable for Stock Sony ROMs.

Tapped from my furious Dogo :')
[Android General] Celestial Fury:
Let's get more feedback before updating the guide:

[MENTION=3060432]boojay[/MENTION]

Limiting com.google.android.intent.action.GCM_RECONNECT breaks your push notifications. Are you on custom ROM or stock ROM?

[MENTION=5734597]zelleb[/MENTION], can you test some more for this alarm for a longer period?
[Android General] zelleb:
Sure. Do you want me to test it on rooted stock or can I stay on CM12? Because right now I'm on CM, but I can just restore my stock backup if that's what you prefer.
[Android General] Celestial Fury:
[MENTION=5734597]zelleb[/MENTION]

Test on your stock Moto G? My theory is that custom ROMs rely more on com.google.android.intent.action.GCM_RECONNECT for push notifications. But you say that it's also broken on your stock Moto G. But stock should be the same and it shouldn't be broken.
[Android General] v7:
You should try stock.I've tested this on my XZR and GT P3100 with various custom ROMs yielding the same result.

Tapped from my furious Dogo :')
[Android General] zelleb:
Alright. Will restore to stock and report back tomorrow :fingers-crossed:
[Android General] boojay:
You're right, I tried disabling Amplify at one point and that didn't fix the delayed messages either, so I just assumed it was a server problem on Google's end, but I also tried the process of elimination that you recommended near the start of this thread. i.e. I reset Amplify's stats and used Hangouts, and com.google.android.intent.action.GCM_RECONNECT was the only wakelock that seemed relevant and was blocked consistently, so I enabled it. I saw immediate results once I reactivated/unlimited it, but now after leaving my phone over night, I once again notice a delayed message.

I am on stock Sony Z3C LP .726 and NOT running stamina mode. On the bright side though, my phone only drained 0.2%/hr overnight! \(^_^)/

Will continue to test and report back.

Swyped from my Z3C
[Android General] khr0n0s12:
Hey dude, BBS still don't have a reading in kernel's section, i really don't know what causes it.
[Android General] Portgas D. Ace:
Settings -> Advanced -> check "Use API for kernel wakelocks" and report back. If this didn't help, report your issue in the BBS forum.
[Android General] zelleb:
So I've tested things on completely stock ROM and I don't know what to say...

It seems too random! Sometimes I get the notifications and sometimes I don't. I guess it even differs on WiFi/3g. I have to test this some more to be sure but at home on WiFi after I turn my screen off for 10 minutes and sent a message from my wife's phone, my phone won't get it until I open TS! Mails come through though (with k9-mail).

I did some research and it seems that TS relies on WebSocket for delivery and on GCM for a wakeup event. Must be a problem with TS then...
[Android General] khr0n0s12:
ok. so i tried it and didn't change anything. maybe my kernel's is not supported? :confused:

i got xperia c, kernel version 3.4.5, and build number 16.0.B.2.16
[Android General] Celestial Fury:
[MENTION=5927935]khr0n0s12[/MENTION]

See here. Others seem to have the same problem and you can get help from the same place.
[Android General] Celestial Fury:
[MENTION=5734597]zelleb[/MENTION]

Does Push Notifications Fixer v4.5.2 make a difference?
[Android General] boojay:
I'm not overly confident, but I may have narrowed down the issue(s)....possibly.

Judging by the previous comments, it seems both [MENTION=5401012]Celestial Fury[/MENTION] and I are using Xperia phones. Personally, I'm on LP 5.0.2 which is known to have the memory leak despite Sony's claims, and I'm thinking that also contributes to the delayed messages. Bear with me while I attempt to make sense of it.

It seems if Hangouts (or whichever push notification app in question) is currently in memory, i.e. recently activated and running in the foreground or is an active background process, then messages will be delayed if the GCM RECONNECT wakelock is limited, but work properly if it is allowed. However, because of the LP 5.0.x memory leak, always running apps will often be kicked out of memory and forced to restart, which means messages will be delayed regardless of Amplify's settings, so you'll either have to manually start the app, or wait for the app to restart whenever the system allows it to, which can seem random when receiving notifications.

What do you guys think?

Swyped from my Z3C
[Android General] vesparados150:
Thanks for the reply! yeah that netmon.linger.expired is bothering meso crazily cos i just dont know how to control it. Plus its on the top 2 list of partial wakelocks caused by an alarm.

On another note, do you use greenify for whatsapp? i had greenified whatsapp previously, but i get high wakelocks caused by greenify which is weird. beats the purpose of using it to reduce wakelocks. i have uninstalled it since. cc [MENTION=5867207]vaisakh7[/MENTION]
[Android General] Celestial Fury:
It's certainly a very interesting theory. Anyone else who says limiting it breaks push notifications should also say what they're running: KitKat/Lolipop; Stock/Custom ROMs.

I used but now currently testing with it not greenified and also greatly shortened my greenified app list. Too many apps to greenify may make it work harder.
[Android General] aukhan:
[MENTION=5401012]Celestial Fury[/MENTION] all these days since upgrade to LL xposed wasn't working we've is working now I shall share the stats which you need after 10 hours.

Note 4 Powered By ET!!
[Android General] pratik_193:
[MENTION=5401012]Celestial Fury[/MENTION]

is it advisable to disable below under services ?

1 - com.google.android.gms/.gcm.GcmService ( 227 )

2 - com.google.android.gms/.deviceconnection.service.DeviceConnectionServiceBroker (221)

3. com.google.android.gms/.lockbox.LockboxService (220)
[Android General] atrix4nag:
I am not seeing few alarms for facebook and most of the alarms from OP.

Also I don't see none of wakelocks given in OP. so what am I missing?

is it good or bad?
[Android General] aukhan:
[MENTION=5401012]Celestial Fury[/MENTION]

Can you share the screenshots of Greenify Experimental Features, As I need to know which needs to be checked.
[Android General] organick87:
those "ALARM_WAKEUP########" kind

[MENTION=5401012]Celestial Fury[/MENTION], do you have any more info on these alarms by any chance?

I see in your first posts that you recommend not limiting them with Amplify because G.P.S. will just create another and I get that, but where do they come from initially? I think I recall once before seeing one a week or two ago, but then it went away. Now, in the same fashion that that one appeared I have another one this morning show up in BBS. I installed a new app, Sync.ME, to sync Facebook photos for my contacts, but other than that I've made no changes. Please advise?
[Android General] Celestial Fury:
I don't recommend anything that's not in the guide since I didn't test them myself. DON'T disable services (unless they're ads/privacy related). Services, once disabled can't turn on when it's needed. Alarms and wakelocks can be limited but not disabled so they still work, their interval is only increased. Services can't be limited, only disabled so they don't work anymore. And those 3 services listed are important.

A different android version/ROM/not enough time for stats to be collected/some stuff on your phone has been disabled/the app in question is not used.

I've stopped using Greenify because when it comes to what really matters, it doesn't work - Google Play Services. It can be greenified but won't hibernated because Google Play Services is in use by... Greenify. :rolleyes: And Greenify itself causes a slight drain. For experimental features, Working mode is boost and check everything.

ALARM_WAKEUP#### - have you opened it up in Amplify? Then you can see that it says Google Play Services. That's where it comes from. Google got the idea from WeChat because WeChat started this random unkillable alarm first - and you heard it here first.
[Android General] organick87:
to do what?

I suppose what I meant, was only recently have I noticed this alarm and for instance, yesterday when I posted my question initally I had one of these alarms all day, since unplugging last night at 10PM until now I have not had one single instance of such an alarm. Understandably you've shown me it's coming from GPS, but to do what and why so inconsistently (not that i'm complaining lol)?
[Android General] boojay:
Just wanted to report that I've been fooling around like crazy with all kinds of settings the past few days, trying to figure out what's causing the delayed notifications by limiting/unlimiting wakelocks, alarms, and services, disabling/re-enabling Amplify AND Greenify, but still no dice. It's either a Lollipop, Xposed, or Xperia issue. I'm at a total loss and have no idea what's going on. Talk about frustrating.
[Android General] Celestial Fury:
Don't know what it does but it's new and the phone works fine previously so it's probably only important for Google and not for us. What to do - get Amplify Dev to implement wildcard auto-limiting of random renaming alarms in the format of ALARM_WAKEUP(*****).
[Android General] Celestial Fury:
Have you messed with disabling receivers or something like it previously? If you uninstalled the app that disabled them they aren't automatically enabled.
[Android General] boojay:
Don't think so, the only mods I'm using are the two I mentioned (Amplify & Greenify) as well as AppOpsXposed, but I only use that to turn off location access for apps that abuse it.

For the past 12+ hours after my last comment I disabled both Amplify and Greenify and my notifications started working again. I don't know if it helped, but I also logged out of my Google account(s) and cleared cache/data for Gmail, Hangouts, Google Play Services, etc., then logged back in.

After that experiment, I reactivated Greenify and tested for several hours, and my notifications were still working, so I reactivated Amplify, and surprisingly, still working. But....once my screen went off for 5+ mins, I experienced delayed messages again, so I wiped Amplify and tried again.

At first it didn't work, but once I manually opened Hangouts and sent/received some test messages, it appeared to be working again. I've been testing it periodically for the past 12 hours and it seems to be working, so what I'll do is gradually limit the wakelocks/alarms in your guide and see which is causing the delayed notifications. It could be just me, I don't know, but for now I'll only limit them one at a time and use Better Battery Stats to observe which are the worst offenders and cross reference those with your guide.

Swyped from my Z3C
[Android General] Celestial Fury:
[MENTION=3060432]boojay[/MENTION]

Z3? If you're using Stamina Mode you need to add them to its exclude list.
[Android General] boojay:
Definitely not running Stamina, I rarely do since my battery lasts all day and I charge in the evening while sleeping regardless of how much is remaining.

Swyped from my Z3C
[Android General] dojodo:
Celestial. Do u had late or delayed notification by using your setting ?

I wonder how just by 52 second wake up and not having any late notification.

This app is great and i still using it at mild setting. I comeback to kitkat because wondering how this app works. I wonder The art change by google on lolipop is against this amplify app
[Android General] Celestial Fury:
[MENTION=5112067]dojodo[/MENTION]

I tested again and this time I didn't get the notifications. In Post #2 the ones with this icon will affect notifications so don't limit them. They didn't play nice previously but with some recent Google Play Services updates, I'll test again to see if they've been optimized.
[Android General] brooker88:
All was working fine 2-4 week ago when was using this guide. I installed a new ROM and applied these settings now my google play doesn't work. Any idea what could of cause it without resetting the whole of amplify?
[Android General] pratik_193:
[MENTION=5401012]Celestial Fury[/MENTION] - Try the latest greenify, oasisfeng removed the dependencies of google play services..!!
[Android General] Celestial Fury:
[MENTION=5112067]dojodo[/MENTION]

The 3 alarms with still don't play nice - they still drain so it's up to you to limit them or not.

[MENTION=5806912]brooker88[/MENTION]

I get that when Google Play Services is greenified.
[Android General] dojodo:
Well. After comparing my kitkat and lolipop , both with amplify enabled, i do think that the battery life is way much2 better in lolipop than kitkat. The art changed done by google really make the difference how android treat wakelock.
[Android General] brooker88:
Location alarms (Global Positioning System)

- ALARM_WAKEUP_LOCATOR

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

- ALARM_WAKEUP_ACTIVITY_DETECTION

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

- ALARM_WAKEUP_BURST_COLLECTOR

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

- GPS_ALARM_BALANCED_ACCURACY

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

- ALARM_WAKEUP_ACTIVE_COLLECTOR

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

- ALARM_WAKEUP_PASSIVE_COLLECTOR

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

- ALARM_WAKEUP_BURST_COLLECTION_TRIGGER

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

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

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

Are these safe to limit if don't use anything to do with location? What are these?
[Android General] Celestial Fury:
[MENTION=5806912]brooker88[/MENTION]

Location alarms (both rough and fine) - they wake up your device to get a fix (from GPS/network/cell towers). Google needs to know where you are at anytime so that they can tell you what to do, where to go, and the best time to go and do it.

These alarms are limited and my GPS is still near instantaneous when I actually need to use it and Google now still works but may need a swipe down to refresh current location.
[Android General] Mudahuda:
You should check what PNF Root does (supposedly fixes delayed notifications)

Also Power Nap (Stamina mode for AOSP or other than Sony's phones.)
[Android General] netyang:
[MENTION=5401012]Celestial Fury[/MENTION], Can you tell me should I limit the Could alarms in Post#2? and how about "Location alarms "? should it be limited to every 86400 seconds?

Could you write a little bit comments in Post #2? Every time you update the Post#2, I have to read through all thread to find what color means and some changes. thank you for you work. very appreciate.
[Android General] Celestial Fury:
[MENTION=4236789]netyang[/MENTION]

Updated:

* affects push notifications

Location alarms (both rough and fine)

* they wake up your device to get a fix (from GPS/network/cell towers)

Yes, location alarms come under 86400 secs. I've edited to make it clearer.
[Android General] Rvl7:
Hello iam using "Cerberus anti theft" https://play.google.com/store/apps/details?id=com.lsdroid.cerberus&hl=en

so i can track my device if lost.

It is safe to use your setting?
[Android General] Celestial Fury:
[MENTION=4276113]Rvl7[/MENTION]

You'll have to try as I don't use Cerberus. The ones that may affect are:

push notifications (cloud icon)

location alarms

anything with 'sync' in it
[Android General] lazer155:
How often do you recommend allowing those location alarms to wakeup the device? It sort of seems like they are under the 86400 second section but there is a dashed line so I'm not positive that they are supposed to be 86400.
[Android General] Celestial Fury:
[MENTION=4856730]lazer155[/MENTION]

Another edit without the dotted line. Location alarms are under 86400 secs. It's perfectly fine with maps/GPS/Google Now.
[Android General] lazer155:
Could you take a look at my betterbattery stats? After almost 8 hours idle it is at -0.3 % per hour. That's a big improvement from what it was originally but I just wanted to check if there was room for any more improvement. I am also using the xposed module Power Nap to limit the apps that can run off screen to gmail and my text messaging app. It is an s5 with a custom touchwiz lollipop 5.0 based rom. When I was adjusting alarms based on your guide, I noticed that I didn't have very many of the location ones you listed. I probably only saw 3 and all the others were not appearing. I never use the low power location option though which uses wifi so that was disabled and maybe that's why there wasn't very many location related ones.
[Android General] Celestial Fury:
@ lazer155

action_batterystats_refresh - what app is this? This alarm is draining heavily over your low drain. Once you've fixed this then check your drain again.

I have these 2 limited for some time now and shall add them to the guide now.

com.google.android.gms.analytics.ANALYTICS_DISPATCH

com.google.android.gms.common.receiver.LOG_CORE_ANALYTICS