yashsingh1/xdaforums huggingface dataset:
[Android General] haris182:
You made me want to root my phone again

Lol thanks
[Android General] Celestial Fury:
If idle partial wakelocks are at 0%, that's great. Make sure they're also less than a minute each. This other time already includes screen on time so it's not idle. Idle awake time should also be under a minute.
[Android General] hatersmakemefamous:
I got kernel wakelock 0-1 %, partial wakelocks 0-1% but alarms are quite high: whatsapp: 27,3 wakeups / h, google.android.gms 25 wakeups / h, android.talk(hangouts) 53 wakeups / h. (havent received any messages and its still that high..?)

also RILJ is causing very showing very high wakelocks in amplify but not in BBS. What can be done about this?:confused:
[Android General] Celestial Fury:
Don't limit something that doesn't cause drain for you (unless it's ads/privacy).

The point being, we want to limit drain WHILE maximizing functionality. While most android alarms/wakelocks are similar, not all phones are the same so if something doesn't drain for you, why limit it and lower your functionality? It's also good to go slow and limit slow so that it's easier to identify any problems that may crop up.
[Android General] Celestial Fury:
Have you confirmed that it's a limitation in Amplify that's causing this? Disable Amplify in Xposed and reboot. Does the problem still happen?
[Android General] Celestial Fury:
Yes for me. You can post your in-use dump.
[Android General] Celestial Fury:
Disable Amplify in Xposed and reboot. Does the problem still happen?
[Android General] Celestial Fury:
It should be ok if you really must. If anything happens, all limitations can be reset, Amplify itself can be disabled in Xposed and Xposed itself can be disabled during reboot.
[Android General] Celestial Fury:
First, confirm that it's a limitation in Amplify that's causing this. Disable Amplify in Xposed and reboot.
[Android General] Daedulus Minion:
[MENTION=4609304]ataft[/MENTION] [MENTION=5401012]Celestial Fury[/MENTION] The service ads.jam.negotiation service causes the "Google play services has stopped". It doesn't use battery or anything so it's ok to not deny it.
[Android General] Celestial Fury:
I heard about this. It doesn't stop Google play services for me. Amplify shows its service as being blocked: 1. And it's been disabled since I put it in the guide.

Did you use Servicely to disable this? Disabling this (and a probably a few others - I have the screenshot but I'm not keen to test them one by one) using

Servicely

causes "Google play services has stopped". And re-enabling it in Servicely doesn't make the warning go away. I had to restore a Nandroid backup. If Servicely stops services on-the-fly then stuff can happen. You heard it here first.
[Android General] Daedulus Minion:
Do you have location turned on? If yes then on what mode? Until now I have read 3 "solutions" to avoid this error:

1) Keeping location off or on device only mode.

2) Not denying wakeup for play services in Privacy Guard or App Ops (it denies this ads.jam.negotiation service also I guess)

3) Not denying ads.jam.negotiation service using Amplify or Servicely.

Edit: Servicely is more aggressive which causes such issues.
[Android General] vctrrl:
Here goes my in-use dump. Posting one from today just in case.
[Android General] Portgas D. Ace:
I disabled all "analytics" services without any issue, despite the fact that they do not drain much battery, but I do not want any analytics service to sniff on my phone. But you are right, a (full) reboot is always recommended when one changes system settings like this.
[Android General] filipeataide:
Yap, the problem still happens. I disabled the module, rebooted, went to amplify and it asked me to activate the module again, which I did, rebooted again, amplify and same error: Doesn't recognize that I have the paid version.

Edit: I disabled Greenify and MyAndroidTools, rebooted and it seems that the problem went away. Let's see how it goes in the next few hours.
[Android General] lazer155:
I will confirm disabling amplify entirely fixes it later today (I need about a day to see if text sending constantly works since the failures are so sporadic). It did work before I followed this guide so I think I just blocked something that my phone needs but maybe others don't.

I managed to capture the wakelocks that occur when text messages fail to send. Only 3 appear when it fails. When it is successful several more appear like in the screen shots I originally posted. I'm on mobile right now or I would repost the screenshot from my old post that shows what happens when it successfully sends a text. The attached screenshots are the ones that happen when it fails.

I think it may be the ICing service that it needs. I'm testing it with that wakelock set to unlimited now. I looked up that wakelock and it is apparently sms related: http://xdaforums.com/showthread.php?t=2225288
[Android General] aidy.lucas:
If you disable every wakelock and alarm you're gonna have problems I've never once needed to limit anything under not safe to limit. It says not safe to limit for a reason I'd reset the lot and start from scratch one wakelock and alarm increasing the delay a bit at a time it's the best way to get the results you want

D2303 18.3.1.C.1.15 kk deodexed, rooted, philz touch recovery, xposed, z1 bravia engine 2 + x-reality+ z3 super vivid, viper audio
[Android General] kcustom11:
I had this issue yesterday too. It only came up when location was toggled on. The error popped up repeatedly. I narrowed it down to UlrDispatchingService wakelock. The guide says to enable it, but for me it causes Google play services to stop.
[Android General] Emmago:
Don't know what to make of this. But I got this from BBS stats.. Can someone please advice?
[Android General] Emmago:
Not a good sign?
[Android General] Celestial Fury:
My location is on High accuracy mode. Google Play Services is Google's life blood. It can potentially force close when something messes with it - disabling Google Play Services in Servicely, greenifying Google Play Services, and using App Ops on it. I don't have problems with ads.jam.negotiation. It's been limited since it was in the guide.
[Android General] Celestial Fury:
Firstly, I don't know how you're using your phone - if you use more of a certain app then it will naturally have a bigger drain. What I can do is only identify the major causes of the drain that should be safe to limit but only you can test to find out.

- org.telegram.messenger.Telegram (lots of messaging?)

- com.sand.airdroid.action.http_retry.start_thread (lots of retries)

- ALARM_WAKEUP135214 (can't do anything about this one)

- com.facebook.push.mqtt.d.b.ACTION_INEXACT_ALARM.com.facebook.orca (lots of FB messaging?)
[Android General] Celestial Fury:
Sorry, I misread your problem. If you suspect a limitation in Amplify is messing with your paid Amplify then go to Setting and RESET TO DEFAULTS and reboot. This will clear all limitions while letting Amplify be active. Note, you will have to limit everything again from start. If the problem still persists then it has nothing to do with any limitations since nothing is limited.
[Android General] Celestial Fury:
What is StartingAlertService and why is it limited? What app is using it (as reported by Amplify)? Icing is a Google Services wakelock. If your 3rd party sms app needs to use it to send messages then, yes. Stock SMS does not need Google Services. What version of Amplify are you using? For Icing, mine says Google Services but yours says Google Play Services.
[Android General] Celestial Fury:
I confirm. UlrDispatchingService didn't cause problems in the past but any Google Play Services update can always change things. I haven't had it limited for some time but testing it with a GPS app and the problem occurs. Guide updated.
[Android General] Celestial Fury:
The advice is to get a dump before using your phone for hours. See Post #3 under Test Idle Battery Drain.
[Android General] Ippolito1971:
Interesting concept for battery drains. I've been using the extreme method with power nap, Greenify, wld , and Amplify. At first it was amazing but after 2 weeks battery is worse then prior when in use. Even the downtime / sleep time used an average of 10% overnight which was about 6-7 hrs for me. I'll give your method a go and advise how things turn out. Greatly appreciate your work here!!!
[Android General] Celestial Fury:
Comparing a before and after without seeing what is actually using the battery (aka BBS text dumpfile) is like driving a car and saying the mileage is better or worse by basing on the fuel left - without taking into account driving style, destination, distance travelled.
[Android General] vctrrl:
Telegram is the app I most use, so I guess there's nothing to do but while idling it do not disturb. FB Messaging even if I don't use triggers a lot of alarms. Air Droid is in the same boat. I don't use both a lot but they're always triggering alarms, so they're my concern. I'd like to preserve functionality though.
[Android General] vctrrl:
Btw, I've just activated Google Now and high precision location and a "Google Play Services Stopped" poped up. Should I unlimit it?
[Android General] Celestial Fury:
Limiting UlrDispatchingService seems to have a bad affect when using location. Do you have it limited? See Post #602.
[Android General] Ippolito1971:
Agreed. Before I make the changes I will do a report. Thanks for the input.

LG G3 VS985 SkyDragon LP

If I've helped you please hit the thanks!! ? ?
[Android General] filipeataide:
Does anyone know what the gms/lockbox alarm is for? It sure appears a lot on my log...
[Android General] Celestial Fury:
Which log - Amplify or BBS? See Post #3 - Test Idle Battery Drain - No. 6. Also, read under Lockbox.
[Android General] Dendis:
How can I reduce ir Any way these 3alarms from messenger, because it shows, that it drains alot. And How much can I disable them?
[Android General] closee91:
Do you have amplify?

Sent from my LG D851 running Blisspop ROM
[Android General] athibanvasanth:
Thanks for this thread. Very useful as a beginner to explore Amplify :)
[Android General] Dendis:
Yes, of course I have, I need what alarms from messenger i should limit And How much?.
[Android General] SOLheel:
Did anyone running power nap for xposed and amplify for xposed have or hear of any issue receiving SMS/MMS?

I'm not sure if my provider had an issue, or if its because of those apps

Any help would be great
[Android General] vctrrl:
I had it limited. Unlimited it and now it's ok. Turned high precision location and location history in order to use Google now but a lot of alarms triggered :(
[Android General] lazer155:
I am not sure what StartingAlertService is. I limited it because amplify and the amplify spreadsheet report it as being safe to limit to 240 seconds. I thought it was related to notifications based on a couple posts from the amplify thread. I still get notifications from 8sms fine. If I switch to the built in text app, I have the same problem with sporadic sending failures. I thought google play services was related to 8sms because it appears everytime I send an sms. I'm not sure why though because the app doesn't support any kind of cloud or internet based messaging. I know the app has an in app purchase to upgrade to the pro version and I am just using the free version so maybe ICing comes up everytime to check the license. Regardless, setting StartingAlertService and ICing to unlimited for a day didn't seem to fix the problem. I'll try disabling amplify entirely and test that all day.
[Android General] closee91:
Limit all three that are in the screenshot. Limit them AT LEAST 3600. I prefer 7200 though

Sent from my LG D851 running Blisspop ROM

If I helped you out, hit thanks!!! :D
[Android General] Dendis:
Will I lose chat heads or instant notifications?
[Android General] closee91:
Yes you'll lose notifications instantaneously but you won't lose chat heads

Sent from my LG D851 running Blisspop ROM

If I helped you out, hit thanks!!! :D
[Android General] Celestial Fury:
I don't know about PowerNap but it's supposed to be based on Stamina Mode and Stamina Mode doesn't need anything whitelisted for SMS to work. Nothing in the guide will stop stock SMS from working either. 3rd party SMS app may depend on what it wants to use in order to work.
[Android General] Celestial Fury:
Location alarms are limited at 86400 secs in the guide which from your screenshots aren't.
[Android General] vctrrl:
Sorry, just realized after posting.

I've successfully limited airdroid and fb messenger and both are working nice so far :)

Otherwise, after enabling Google Now and location, etc, new alarms kicked in while in use. Any chance of limiting them?
[Android General] Portgas D. Ace:
Useless stats, as you have used your device for more than two hours. Post an idle dump.

BTW: for the (random) ALARM_WAKEUP1234567, check post #2 (category Not Recommended) for more infos about them.
[Android General] Emmago:
I finally tested for idle time after leaving phone for 7hrs upon full charge. Please advice so I know the next step to take
[Android General] Celestial Fury:
These new alarms mostly come from the apps that you were using. They are meant to kick in.
[Android General] Celestial Fury:
The stats don't say 7 hours. They say 5 mins and less. And how are you creating the dump in 5 different files? Shouldn't there be just one? BBS --> Share --> Text Dumpfile.
[Android General] Emmago:
What I did was charge my phone to 100%..switched off for more than 7hrs..switched on and took the stats.. Oo.. I wasnt meant to switch it off right?
[Android General] vctrrl:
So is normal/acceptable that battery drops more quickly now while screen is on? Obviously Google Now/High Precision Location drains more battery but those alarms can't be limited? I didn't had wakeups from com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD, even while in use, for example.

As for the ALARM_WAKEUPXXXX, I'll wait for your solution.
[Android General] Celestial Fury:
If the phone is off, how can any alarms or wakelocks trigger? ;)
[Android General] TNSMANI:
You are supposed to charge it to 100% and leave it on and idle ie. not use it for about 7 hrs. Do not switch off the phone. Then after expiry of ~7 hrs open BBS, click the share button and then check Text Dump File and then click Save. That is all.

Do not go on saving the text file from the Others screen, Alarms screen, Partial Wakelocks screen etc. One text file from the Others screen is sufficient.
[Android General] Celestial Fury:
Logically, it'll drop quicker with the screen on rather than off. How quick will depend on how intensive you're using the phone.

What app does this - com.google.android.apps.gsa.kato.ACTION_ALARM come from? Look in Amplify for it - the name will be displayed.

This - com.google.android.googlequicksearchbox/com.google.android.velvet.VelvetBackgroundTasksImpl@Service comes from using Google Now. It's well-behaved and doesn't cause drain while idle.

- DELAYED_KEYGUARD is listed under NOT SAFE in Amplify if I'm not mistaken.

- ALARM_WAKEUP_BURST_COLLECTOR is the only location alarm in your screenshots that is mildly active. If it's already limited at 86400 secs, it can be left alone.
[Android General] Celestial Fury:
Alarm_wakeupxxxx

The solution seems stable. I know how annoying 'Google Play Services has stopped' can be. BUT it will be frustrating to say the least, if reverting whatever changes made to Google Play Services doesn't stop the notice - and it has happened as I mentioned before. In fact, I have a backup made in recovery before making the changes to Google Play Services so I can restore it if it goes crazy and reverting doesn't solve it.

The solution can be found in other threads. I'm not sure I want to mention it here and take responsibility since not everyone knows or bothers to make a backup in recovery. While it may also be fine now, any Google Play Services update can potentially screw things up when it can't work the way it wants to.
[Android General] vctrrl:
I mean the screen on without Google Now/Location normally drain less battery.

com.google.android.apps.gsa.kato.ACTION_ALARM comes from Google App.

ALARM_WAKEUP_BURST_COLLECTOR should be limited at 86400?
[Android General] Celestial Fury:
How much less without Google Now and how much more with it? You can try limiting Google Now's two alarms and see if it still works ok.

ALARM_WAKEUP_BURST_COLLECTOR is in Post #2.
[Android General] vctrrl:
I would normally have 4 hours of screen on (wifi only) and 3 hours with of screen on with Google Now/Location.
[Android General] vctrrl:
Feel free to mention the thread as you have no liability for it.
[Android General] ar2o:
Hi everyone,

I have a few questions to ask if you all don't mind:

Once you establish your 2 baselines and you begin the idle testing procedures:

-does it need to be 7 hrs of idle time or can it be say 5 hr? What is the bear minimum if I may ask? It cannot be awake for more than 1 minute or it will skew the results right?

-during the idle time, what happens if you get notifications/messages/emails/calls (obviously you don't answer/reply/check them) does it skew your testing results?

-does it matter if you just flashed a Rom and have to let it settle before you follow through with these tests or it makes no difference?

-after every wakelock/alarm you tweak, do you need to reboot and check functionality, etc?

-you keep wifi on all the time regardless if your within a wifi connection or not or did I misread the OP wrong? I always thought if the phone needs to scan for a wifi connection it's killing its own battery. Like for example the "DHCP" wakelock under "android system".

Thanks for your patience! This seems like a tedious but st the same time fun process of tweaking your device! :p awesome thread sir!:o

Device:

T-mobile Samsung Galaxy note 4

Sent from my PopRocks V5X Xparent Skyblue Tapatalk 2
[Android General] vctrrl:
[MENTION=5401012]Celestial Fury[/MENTION] may give you a better answer but what I understand is:

1) Overnight is enough but if you can keep your phone idling for longer, probably better

2) Before limiting anything is important to know what to limit. Maybe your phone/rom triggers different alarms/wakelocks and it's important to check BBS to know what is waking your phone

3) A few notifications won't probably give you an inconsistent reading of alarms/wakelocks. Lots of notifications otherwise will probably drain more battery and shows you alarms that are normal under those conditions

4) Those from the guide are known to be safe. Limit them and reboot. You'll need to reboot after you limit anything. Don't limit lots of things at once (except things from this guide). If you have alarms from an app, start limiting them and keep checking for functionality. If something goes wrong will be easier to track what caused issues.
[Android General] ar2o:
I really appreciate your time to explain this to me! Cheers to you mate :beer:

Sent from my PopRocks V5X Xparent Skyblue Tapatalk 2
[Android General] Puckapunyal:
I lol'd
[Android General] Celestial Fury:
I don't know. Stuff from here gets re-posted without attribution.
[Android General] Celestial Fury:
The longer the idle period the better. You can't take a dump without turning on the screen (unless someone knows how to automate this?). Any skewing should be minimal. If during the idle period, lots of notifications come in then you're not likely to achieve 0% [0.0%/h].

Whether flashing a ROM or not, what's important is to identify the alarms/wakelocks that regularly cause the drain. If something appears today but not tomorrow during idle then it should be left alone.

Alarms and wakelocks are limited immediately so you should test the app immediately and for several days to your satisfaction. Only reboot upon disabling services. They're only disabled upon a reboot and it's best to test it as soon as possible.

For the 0% [0.0%/h] drain screnshots posted, WiFi is always on and scanning always available but it was tested at home so constant connection to only one WiFi.
[Android General] ar2o:
Thank you kind sir for the update! Last night I charged my phone and turned it off for 7 hours to test the battery only drain, which showed 100% but after a minute it dropped to 99%. Either way no battery % dropped over the 7 hours of the phone being off. Tonight I'll give the 7 hours of airplane mode a go on a full charge and tomorrow I'll try the 7 hours of idle time with amplify and I'll limit the alarms/wakelocks that I notice are causing drain.

Thanks again for this awesome guide kind sir :)

Sent from my SM-N910T using Xparent Skyblue Tapatalk 2
[Android General] intruder16:
[MENTION=5401012]Celestial Fury[/MENTION],

Amplifying "UlrDispatchingService" wakelock doesn't trigger "Google Play Services has stopped" error in my device. Infact i don't have any errors in both previous and latest (today's?) versions of GPS.

EDIT: FYI, i only denied "com.google.android.gms/common.analytics.CoreAnalyticsIntentService" service using Amplify and also amplified related (analytics) alarms. For device, ROM info look at my sig.

I can post all alarms and wakelocks i disabled if you want.
[Android General] Celestial Fury:
[MENTION=5338267]intruder16[/MENTION]

Did you open Maps or something that uses GPS? I tried it with Sygic and the error message would keep appearing at regular intervals. UlrDispatchingService used to drain but doesn't seem to anymore.
[Android General] intruder16:
I did. To show all the location related alarms so that i could disable them. In all 3 location modes. I used GPS Status, Maps and OLA apps. I did it again with Maps to check but no error still.

EDIT: I also think there is no need to tame UrlDispatchingService coz i don't see many wakelocks related to it (atleast in my device).
[Android General] garthybarthy:
Hello all,

Can anyone confirm what *alarm* is? Had a quick Google but just brings up random alarms.

Wondering if its safe to limit.

Thanks.

Thanks
[Android General] v7:
[MENTION=6283568]garthybarthy[/MENTION] They comes up on every ROM running 5.0+.No need to worry about them.

Tapped from my furious dogo ;)
[Android General] Celestial Fury:
Maybe the difference is Lolipop or AOSP.
[Android General] Celestial Fury:
Do you use Lolipop then? Do these alarms drain a lot? Another reason not to be on Lolipop.
[Android General] Celestial Fury:
What about attribution? Do I need to worry about them? :rolleyes:
[Android General] v7:
Didn't get you?Oh..My thread..:)

I didn't steal your work mate.Its not a repost.I've used your guide Before.I tested it and checked with the official list from the Amplify dev.

There's much difference in mine from yours.So I believe there's nothing much to worry about.:)

Tapped from my furious dogo ;)
[Android General] garthybarthy:
It's under wakelocks, yes I'm on lollipop. It's not a massive drainer so if its not a problem that's fine.
[Android General] Emmago:
I finally pulled out my dump.. Please take a look and advice.. Thanks
[Android General] ar2o:
Hello everyone :)

I must ask, is it smart to limit say 3-5 of the worst wakelocks? Under alarms, go under each alarm and limit the the alarms with the most intents (leave the ones that say "1")? Is this a safer procedure so that one does not get any errors and is forced to start testing from scratch?

Also, if there is a wakelock/alarm NOT listed in the list thats in the OP, is there a general recommendation for how much to limit it at first to stay on the safe side?

Or maybe someone or OP has a specific strategy/game plan they go about when limiting wakelocks/alarms to minimize error? Would like to hear an opinion please.

Thanks :)
[Android General] jagman96:
I charged my phone to 100% before bed last night. I wiped Amplify before unplugging it and BBS of course started again as it was unplugged. This was after many hours of sitting unused. What do you think?

https://drive.google.com/file/d/0B2AhsHVR27R_M2Q5NWRULTFHM2s/edit?usp=docslist_api