yashsingh1/xdaforums huggingface dataset:
[Android General] Celestial Fury:
[MENTION=2988507]AutomaticFailure27[/MENTION] see above.

[MENTION=2329669]Weetbix[/MENTION] I don't supposed you know how to do this for stock Google Backup, do you? Bear in mind Google Backup is not an on/off toggle. Disabling it means it will erase the backup.
[Android General] Emmago:
Please take a look at the screenshots below.. What should I do to those triggered a couple of times?
[Android General] Weetbix:
Sorry, I have no idea. I've never used google backup. Never looked into it actually. Might do that one day next week on my commute to work.
[Android General] Celestial Fury:
You should see Post #3 on how to test as Amplify does not show drain.
[Android General] Celestial Fury:
- com.oasisfeng.greenify.CLEAN_NOW

Greenify alarm now moved under dangerous. Limit it and it stops hibernating any apps not yet in hibernation. I don't think Greenify is needed if Amplify is used to limit.
[Android General] Emmago:
I know.. But am trying to know if the highest amount of time a service, wake lock and alarms was triggered means higher it drains battery..

---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------

I see no reason too.. But am still getting used to Amplify.. I haven't found my way around it yet.. I have also limited the services and wake locks posted on the OP but there are still others for the various apps I have installed... Can I also use this to reduce battery life while screen is on?
[Android General] Celestial Fury:
[MENTION=6131391]Emmago[/MENTION]

High numbers of wakelocks/alarms in Amplify does not mean higher drain. You can compare with BBS. I don't know why they don't have the same numbers.

As for reducing drain while screen is on, it'll depend on the wakelock/alarm in question and how well the app in question will work once limited and you can only tell by testing it.
[Android General] Emmago:
How about high number of services? Does that indicate anything?
[Android General] ClownShoes:
Morning fellas, I'm still getting a fair amount of idle drain that I can't pin down. Any help would be appreciated
[Android General] Celestial Fury:
Services don't trigger like alarms/wakelocks. They're either enabled or disabled. Each time you reboot they go up by 1 count if I'm not mistaken (unless you use another app to disable/enable it on-the-fly without a reboot). The total number is from since the last reset in Amplify.
[Android General] Celestial Fury:
Awake (): 54 m 52 s 15.0%

Aren't these high?

Alarms: 57, Intent: com.google.android.intent.action.MCS_HEARTBEAT

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

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

Alarms: 2, Intent: ALARM_WAKEUP_PASSIVE_COLLECTOR

Alarms: 12, Intent: com.google.android.apps.gsa.kato.ACTION_ALARM

Alarms: 12, Intent: com.google.android.apps.dashclock.action.PERIODIC_ALARM

Your CPU is awake at all stages. You might want to see also android's battery usage screen.

==========

CPU States

==========

2.46 GHz (): 6 m 5 s 1.7%

2.27 GHz (): 2 m 24 s 0.7%

1.96 GHz (): 3 m 42 s 1.0%

1.73 GHz (): 5 m 21 s 1.5%

1.57 GHz (): 6 m 44 s 1.8%

1.5 GHz (): 7 m 16 s 2.0%

1.27 GHz (): 6 m 53 s 1.9%

1.19 GHz (): 5 m 37 s 1.5%

1.04 GHz (): 4 m 2 s 1.1%

960 MHz (): 2 m 29 s 0.7%

883.2 MHz (): 1 m 22 s 0.4%

729.6 MHz (): 42 s 0.2%

652.8 MHz (): 32 s 0.1%

422.4 MHz (): 18 s 0.1%

300 MHz (): 1 m 19 s 0.4%
[Android General] closee91:
Hey [MENTION=5401012]Celestial Fury[/MENTION] what exactly does this alarm do. And can it be limited?

com.android.server.action.NETWORK_STATS_POLL
[Android General] Celestial Fury:
Alternative technique for push for mobile data connection (?).

http://stackoverflow.com/questions/17782512/android-event-for-current-network-traffic

http://developer.android.com/training/efficient-downloads/regular_updates.html

You'll have to test. I seldom use mobile data.
[Android General] closee91:
I'll limit it and report back. Thanks!
[Android General] agbazinga:
Hey guys I had a question regarding Google Play Services, if I follow the guide and disable the alarms and wake locks related to Google as mentioned , is it required to use Privacy Guard also ?

Because currently I am using Privacy Guard to prevent Keep Awake, Wake up and Auto Start for Google Play Services but whenever I turn on Location I keep getting Google Play Services Force Close ( may be due to Privacy Guard ) . So what is the solution to prevent idle battery drain from Google Play Services and at the same time be able to prevent FC when Location is turned on

( PS -A general question regarding wakelock ,

If a wakelock / alarm , suppose related to Location is delayed by 12 hours but if I am using an app that needs to access location while screen is on will it affect the app.

I mean does delaying wakelocks and alarms affect the functionality of a particular app even if the app is running when screen is on )
[Android General] AutomaticFailure27:
How would I go about changing this to limit once per hour? I tried changing the overall sync wakelock to 3600 and everything that has the *sync* tag within it, but gmail still seems to sync once every 4 minutes or so.
[Android General] Celestial Fury:
Look for alarms that have *gmail* in it.
[Android General] AutomaticFailure27:
Did that and it's interesting since gmail is the only one within the sync that seems to be going off the timed set. Everything else hasn't sunk since I changed their timings. I will keep an eye on it to see what happens throughout the day.
[Android General] Celestial Fury:
Is Privacy Guard mentioned as required in the guide? Alarms/wakelocks aren't disabled by Amplify, only delayed. Alarms/wakelocks by Google Play Services can be limited in Amplify to limit drain. If you suspect a limited alarm/wakelock that is causing a FC, then disable Amplify, reboot and see if the FC still occurs.

For location alarms/wakelocks in the guide, they won't affect any app that you run manually. Location will still be found. Others will depend. For examples, see under DANGEROUS - DO NOT LIMIT / DENY and Not Recommended in Post #2.
[Android General] Celestial Fury:
Reset Amplify stats.

Go to Gmail and force a refresh.

Open Amplify and see what Gmail related alarms/wakelocks were triggered.
[Android General] agbazinga:
Thanks for the prompt reply...will try it out to get to the exact cause (y)

Btw do you rely on Privacy Guard for Google Play Services ( in context to Wake Up , Keep Awake and Auto Start ) or only Amplify does the job ?
[Android General] Celestial Fury:
Currently, Amplify can't limit random renaming alarms like

- ALARM_WAKEUP(#####) - Google Play Services will just create another (number) Fix here. but the fix is there using AppOps and Servicely. Look under Not Recommended in Post #2.
[Android General] tersagun:
Hello and thanks for the awesome guide.

I've followed vaisakh7's guide and tweaked a little bit (without PowerNap as it wasn't working on my G3) and I've achived to reach less then 0.5/hour drainage on stand-by. Checking this thread to improve it even more ;)

First things first; I wanna know how useful blocking alarms/wakelocks in reality are. I mean, Amplify blocking 1000 alarms is a good thing but it also means that there are apps generating 1000 alarms all the time which means they are still using battery. Is that just too marginal that you can ignore it?

And other than that, even though I've managed to get very low idle-drain, my BBS graph shows lots of wakelocks during the night. What kind of graph would be ideal? Is it possible to have like only several wakelocks during sleep?

Thanks again :)

Add: Example graph.
[Android General] Emmago:
Thanks for the prompt response.. So it's safe to limit the alarms and wake locks that have a high count right? Hope it won't cause any issues? I will also limit all alarms and wake locks from the OP on page 1...but will it be safe to limit alarms and wake locks under 'UNKNOWN'

Can I limit all and not get problems?
[Android General] Weetbix:
Just curious - what is your recommended duration for this alarm? Post #2 has it as both 7200 and 43200 seconds. I've just limited it to 43200 so I guess I'll see how that works out for me...

I'm just resetting up my phone after a rom update, and this is the first time I am limiting anything to do with the calendar (finally trying the alternative calendar app mentioned) ... so I've never really paid very close attention to this before.
[Android General] closee91:
43200 is my personal set. No problems here
[Android General] ClownShoes:
Ok so as my idle sleep times have been so bad recently, I decided to do a clean reinstall of my rom, just to ensure that wasn't part of the problem. Sadly it made no difference and my phone is still staying awake for a ridiculous amount of time. Scratching my head here!

I have removed all other battery saving apps, such as Greenify and Power nap and anything that controls services such as appops

I'm determined to tame my phone with amplify, it's just proving tougher than I first thought
[Android General] ar2o:
Request for Guidance Please

Hi everyone,

I thought I tamed my phones wakelocks/alarms but suddenly I wake up one morning and all the wakelocks/alarms are running even tho limited to 86400 ... I reset amplify in amplify settings, rebooted, charged and left idle for the night. I will attached a text dump + pictures and maybe somebody can start me off on the right path please. The only alarms/wakelocks cannot really touch are Microsoft Exchange ones as its linked to my work account syncing every hour Monday to Friday 9am-5pm but from 5-9pm and all day weekends it's set to 4 hr sync and my stock .Calendar as well. I would really appreciate anyone's generosity :)

I cannot upload a text dump file on my current version of Tapatalk so I'll do that when I log onto the pc.

Sent from my PopRocks V6X Xparent Skyblue Tapatalk 2
[Android General] closee91:
0.4% isn't too bad yeah upload a dump and I can look at it
[Android General] Celestial Fury:
You'll have to strike a happy balance between drain and functionality. The alarms/wakelocks limited in the guide represent my happy balance. As long as you've got the idle drain you want, you can ignore the rest of the alarms/wakelocks.

BBS graph show a more detailed wakelock. For 0% [0.0%/h] it's enough if android battery usage shows little to no wakelocks .
[Android General] Celestial Fury:
It's safe to limit whatever's in the guide. High count in Amplify does not necessarily mean drain. You'll have to test for yourself if you want to limit others. Or you can just attach a dump but whatever is recommended to limit from your dump will still need to be tested by yourself.
[Android General] Celestial Fury:
Thanks for the catch. It was initially limited at 7200 but as it still drained it was then limited at 43200. This means it will sync twice a day if that's fine for you. However, any limitation of this alarm will cause problems with the calendar alarm triggering to remind you of an event. Hence, the alternative calendar that's more well-behaved than the stock calendar.
[Android General] Celestial Fury:
What's ridiculous is Awake (): 1 h 43 m 1 s at [0.2%/h]. Why is your Statistic Type: Custom to Current? If you've charged it to 100% then select unplugged instead of custom. Currently, there's something not right in your high awake with low drain.

You still haven't limited according to the guide. These are still the same ones that I pointed out in my previous reply to you. Follow the fix for ALARM_WAKEUPxxxxx as well. Then we can look at the ones that are not in the guide.
[Android General] Celestial Fury:
There's no point in posting all those screenshots if Amplify isn't limiting the alarms/wakelocks. You have to solve that problem first. Reset Amplify stats then after idle period, show the Amplify screenshots where they are limited but not working. Then show that Amplify is ticked in XPosed. Are other Xposed modules working? Post Amplify version, android version, ROM. Then post an Amplify log in the Amplify thread.
[Android General] ClownShoes:
I completely ignore the low drain, because I have an LG G3 and there appears to be a recognised battery calibration issue, where 100% to 99% is completely out of whack. It's the same reason I usually do a custom from anything other than 100% to see what's going on. I forgot today and left it on 100% ;)

I'm not sure what I've missed from the guide? I think I've added everything you suggested, including the ones you pointed out in your previous replies
[Android General] Celestial Fury:
Identifying battery drain is part statistics and part art. After looking at hundreds of dumps you tend to get a feel of things and knowing what the actual drain should be like is part of that feeling.

In the guide

Alarms: 66, Intent: com.google.android.intent.action.MCS_HEARTBEAT

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

Alarms: 21, Intent: ALARM_WAKEUP4410299 (see the Fix)

Alarms: 1, Intent: ALARM_WAKEUP_ACTIVE_COLLECTOR

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

Alarms: 1, Intent: ALARM_WAKEUP_BURST_COLLECTION_TRIGGER

Alarms: 1, Intent: ALARM_WAKEUP_CACHE_UPDATER

Test these

Alarms: 15, Intent: com.android.internal.telephony.ACTION_CHECK_NETSTAT

Alarms: 13, Intent: com.google.android.apps.gsa.kato.ACTION_ALARM

Alarms: 13, Intent: com.google.android.apps.dashclock.action.PERIODIC_ALARM

Alarms: 6, Intent: com.anydo.cal.UPDATE_REMINDERS

Your bittorrent was active as well.
[Android General] ar2o:
No no, what I did was reset the amplify to default stats, rebooted, charged to 100% and left idle over the night. I followed your op's step 3 and posted the screen shots + extra. The only thing I need to do is attach the dump file. Nothing is limited as this is a fresh re-run to see what's killing my battery and what I can start limiting. I remember you suggesting to limit the alarms in the first 3 alarm postings and see how it turns out correct?

Sent from my PopRocks V6X Xparent Skyblue Tapatalk 2
[Android General] Celestial Fury:
You said this:

If Amplify is not working for you then you need to fix it first. If it is, then most of what you posted as draining is in the guide. If they were already limited then there is no need to reset them as you just have to do them all over again. From your screenshots there are more than just the top 3 alarms to limit.
[Android General] ClownShoes:
It's certainly becoming easier as I get used playing with things in Amplify.

I had actually already added most of the alarms you'd quoted there, but I did find two I had missed.

It also appears much of my problems have been caused by my wifi connection, as I have now taken that out of the equation and reduced my awake times to about 6%

I'm going to do another idle test tonight and I'll post the BBS log tomorrow if there's a significant improvement.

Thanks again for all your help :)
[Android General] agbazinga:
Thanks for the suggestions , it turned out that privacy guard was causing the FC, so removed the play services from Privacy Guard and delayed the alarms for play services as mentioned in the guide.

I got an idle drain of around 1%/h.

I am attaching a link to dump file from battery stats, could you help in suggesting some improvements ( apart from whatsapp alarms/wakelocks ).

Thanks :)

https://www.dropbox.com/s/r6riwjolnb36jqk/BetterBatteryStats-2015-07-14_063914181.txt?dl=0
[Android General] ar2o:
Any Help Starting Out Is Much Appreciated

Im posting my Stats gentlemen. Any help is much appreciated! :)
[Android General] Portgas D. Ace:
Try limiting the *net_scheduler* wakelock, as it kept your device awaken for nearly 14 minutes.

Try limit the following alarms according to the OP:

Alarms: 140, Intent: ALARM_WAKEUP_LOCATOR

Alarms: 25, Intent: com.google.android.gms/.checkin.EventLogService$Receiver

Alarms: 29, Intent: com.facebook.push.mqtt.d.b.ACTION_INEXACT_ALARM.com.facebook.orca

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

Alarms: 30, Intent: com.facebook.rti.mqtt.b.b.ACTION_INEXACT_ALARM.

Alarms: 19, Intent: com.google.android.apps.gsa.kato.ACTION_ALARM
[Android General] PIRATA!:
Hi [MENTION=5401012]Celestial Fury[/MENTION] !!!

I have some questions about your guide.

According to your listing, I'd like to understand how to read it and manage the limitations.

1) the Alarms every 43200 seconds are all notification sensible?

As you said in OP, I thought that your guide was totally leaving notifications as stock, in the sense that setting these limits won't affect not only the notifications but also the time I receive them!

How do I set the limits so NOT have any notification delay??

2) Alarms every 86400 seconds are Location sensible?

As you said in OP, I thought that your guide was totally leaving Location as stock, in the sense that setting these limits won't affect not only the Location finding but also the time I get hooked!

How do I set the limits so NOT have any London delay or bad accuracy??

3) about the

DANGEROUS

- DO NOT LIMIT / DENY list, does it involve the 3 sub lists

Wakelocks

,

Alarms

and

Services

underneath it??

4) about the

Not Recommended

section, I'm quite confused as underneath it I see a

Wakelocks

section and just under a

Services

(Deny - Ads / Privacy) section.

Are they both to be considered as

Not Recommended

, or that is only for the

Wakelocks

section just underneath it?

5) in the last list

Services

(Deny - Ads / Privacy) you have wrote a message:

After disabling any service,

reboot

the phone because it is dangerous to disable any service on-the-fly according to Amplify so it's only disabled on a reboot.

Do you mean that for ANY service in that list that I see, is it supposed to make a device Reboot EACH TIME I "deny" one??

About all you have listed here, my needs are to have stock notifications (in the manner of receiving them and in the same time gap as stock) for WhatsApp, Facebook and Messenger (external app from Facebook), PLUS have good GPS location and usage as I use my device as my work street driving navigator AND for my sports records while running PLUS use S Health pedometer.

About important apps running, I have Greenify, PowerNap, and BBS.

So, from all the things I see listed here, which ones are to be considered to NOT set its limitations??

Tnx so much.
[Android General] Portgas D. Ace:
1) Only those with the blue cloud symbol affect push notification and thus are to be handled with caution. My recommendation: leave them unlimited until you have set up your device according to your needs and then test those by limiting one by one and see how push notifications are affected. If you rely on Facebook push notifications, don't limit com.facebook.push.mqtt.keepalive.KeepaliveManager. ACTION_INEXACT_ALARM.com.facebook.katana. As far as I know, this affects Facebook's push notifications through mqtt (similar to Google's Cloud Messaging GCM).

2) No idea, as I haven't limited those, because I use location services quite often. For me they do not drain battery, so no need for me to limit them. I would suggest you to not limit them.

3) Yes, the "dangerous" category lists all dangerous-to-limit items from the three categories (wakelocks, alarms, services). Do not limit/disable them as they will cause big issues.

4) The "not recommended" section consists only of the listed wakelocks. Limiting those might result in misbehaviour of your phone. The "service" section underneath lists all services that you can disable.

5) You do not have to reboot your phone each time you disable one service. Only when you have disabled all relevant services do a reboot once.
[Android General] ClownShoes:
Morning all

It does appear that my wifi connection has been messing with my deep sleep. I tried setting my wifi to switch off when my screen goes off and lo and behold I have considerably better deep sleep!

Now I don't know whether it is a problem with my wifi connection or a rogue app that is keeping it active, but at least I have worked out the major cause of my problems :)

Now as I mentioned yesterday, I have an LG G3 which seem to be notoriously bad for properly recording battery drainage, so once again my log says I am consistently on 100%, when I clearly am not! So what I'm wondering is, what is a decent deep sleep time? My phone seems to be fairly consistently sitting at around 92% deep sleep, when both idle and when in use. Is this fairly decent? Or could I be doing more to get it down?

I also noticed I'm still getting wakelocks from the 'googlequicksearchbox' Is this google now? and If I limit this will I lose google now functionality? I currently like having the google now cards appear in my notification bar and I wouldn't want that to stop

I'm also still getting a lot of MCS Heartbeat alarms 'Alarms: 42, Intent: com.google.android.intent.action.MCS_HEARTBEAT' These are related to my sync settings right? I already have this limited as suggested in the guide, so I wonder is this still a normal amount? I don't want to mess with my sync if it will affect my receiving emails on time
[Android General] ClownShoes:
I also have a question about this, if that's cool? What is the reason for applying the AppOps hack, but then using Servicely to terminate Google play services? To the best of my knowledge the AppOps hack will only work for services limited within AppOps

Maybe I have misunderstood what you are suggesting?
[Android General] aidy.lucas:
Use one or the other personal preference I suppose, I'm using servicly myself now instead of greenify. Seems to be doing the job well so far.

D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
[Android General] AutomaticFailure27:
You aren't the only one. My phone has terrible deep sleep when I am connected to wifi, yet there is nothing strange being shown in BBS at all. I can not figure out what it causing it. I don't have location on, my sync settings are for every hour, nothing really has changed until the addition of Amplify.
[Android General] ClownShoes:
Ok, I'm really glad you said that, because the test I did last night was eye opening. I decided to fully charge my phone and then turn off wifi completely without changing any other settings. When I woke after about 7 hours I was pleasantly surprised to see my phone had been in a deep sleep for 97% of the time as opposed to the usual 72%... Wow!

What was even more of a surprise was that for the very first time my battery drainage stats seemed to be working correctly! Where my phone would usually stay on 100% for a ridiculous amount of time, even under heavy usage, it now said it was down to 98%. Could this all be wifi related?
[Android General] Portgas D. Ace:
Yes, this could be WiFi related. Could you make a screenshot of the Advaced WiFi Settings section (WiFi -> Advanced)? I guess the culprit can be found in your WiFI settings.
[Android General] ClownShoes:
Cheers, although I'm really not sure what that will tell you....
[Android General] Portgas D. Ace:
Actually, your settings are the same as mine. I thought yours might differ, so changing some settings may have helped identifying the culprit.

I guess your WiFi signal is strong enough, so not constant disconnecting/connecting cycles are occuring, right? This is one of the biggest battery drainers while connected to WiFi.
[Android General] AutomaticFailure27:
It's strange since I haven't changed anything regarding wifi for months now. Using static IP, no location, wifi scanning off, perfect signal, no wlan_rx wake thing and still running 4.4.4. It all seemed to have started happening when using Amplify. I've seen on Reddit somewhere that it could be related to the latest 7.xx Play Services, so hoping an update comes out soon.