yashsingh1/xdaforums huggingface dataset:
[Android General] ClownShoes:
Nope, my signal is strong as an Ox, both at home and work. I've tried 2.4ghz and 5ghz, but both with the same above average drain in both locations

I have had WIFI off for 12 and a half hours now and my awake time is still only 4% despite having had a 15 minute phone call and my office being in a very patchy reception area

Fortunately I have unlimited data on my mobile plan, so I can ride this out until I work out the cause, but I've got to say, it's really weird.

---------- Post added at 02:15 PM ---------- Previous post was at 02:10 PM ----------

I really don't know when it started for me, (I don't think it's been long, but like most on here I am regularly flashing new roms and kernels etc) but the difference is now night and day

I'm running an LG G3 with Cloudy's 2.5 rom (near stock)
[Android General] Portgas D. Ace:
Well, this is really weird, but with an unlimited data plan you are free to go without using WiFi quite often. Maybe it is ROM-related (kernel issue?), but as I do not have much experience with such topics, do not expect help from my side with this.
[Android General] ClownShoes:
Well I'm actually inclined to think this could still be a wakelock issue.

Something could well be keeping the wifi connection in a state where it keeps slowly draining
[Android General] PIRATA!:
[MENTION=5401012]Celestial Fury[/MENTION]

I have an important proposal for increasing the quality of your thread. :)

I've noticed that the Amplify Alarms/Wakelocks/Services listed in OP are a lot and that can be updated with new limits, or old/obsolete limits can be removed, or better limits can be edited with new timings!

Sooo...here it is:

" why don't you put a date at beginning of each line corresponding to the last edit date, so to check easily if a limit has been edited or a new limit has been added, or an old limit has been deleted in the Amplify listing?? "

For example, it you edit the Alarm for a specific thing today, and if you place the today date at the beginning of that limit element, I can be practically sure if that limit is the last edit version, just checking the date you have wrote next to it with the one I know I've made my last edits to Amplify!!

In this way the forum could be much more light and in just a minute people can check if something has been changed!!

An extra nice thing could be to colour with red only the last date edited, or to place at top of OP the date reporting last edit.

People could then just check that date and see if something have changed, and then go through the list of limits searching for dates forward that date!! :)

The only bad thing would be at the beginning to add next to each limit a date...but I think will be a 5 min work [emoji4] ...and then future edits will be just easy!!

Please let us know ;)
[Android General] Celestial Fury:
Your Net Scheduler is acting up so try limiting it. Also Android System is using up CPU for 6 minutes. CPU used in the low range for 17 minutes. Awake time 24 minutes.

I can look closer when I get back to a computer in a week or so.
[Android General] Celestial Fury:
What phone is this - A Note? You got huge awake time and lots of alarms and CPU cycles that normally wouldn't go with such a low drain. Must be the huge battery.

Your location alarms don't seem to be limited to once a day. Also, your FB and Exchange mail have large alarm triggers.
[Android General] Celestial Fury:
The guide says it won't break your push notifications. The problem is push notifications aren't as energy saving as phone calls and sms. So, having instant messaging without fail will come at a battery cost. The next best thing is to find an acceptable compromise between instant and drain. If you don't want push notifications to be touched then don't limit the app's alarm, alarms with the cloud icon and any alarm with sync in it.

The Location alarms mostly have to do with Google wanting your location. Navigation apps are fine with them limited. Google Now seems OK but I haven't paid close attention. If you have an app that doesn't play well, let me know.

The rest have been answered I believe.
[Android General] ar2o:
Hey Celestial Fury and Community,

I want to confirm for my own assurance:

-follow OP steps to aquire baseline drain's

-when beginning to limit items, begin with the alarms, once they are tamed then you can move onto wakelocks as alarms are what trigger wakelocks

If I got that on point then here is my question:

-when limiting alarm/wakelocks already featured in the guide, should I be using the lowest limitation number (7200) for the given alarm/wakelocks that's causing me drain or can I go ahead and use the limitations featured in the guide?

Thanks :)

Sent from my SM-N910T using Xparent Skyblue Tapatalk 2

---------- Post added at 10:25 AM ---------- Previous post was at 09:53 AM ----------

Note 4 to be exact :p I actually clean flashed a ROM and will let the build settle until the weekend to calibrate the battery. I will post my results during the weekend of my baselines and battery drain before adjustments/limitations.

Thanks :)

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

I'm still struggling with WiFi keeping my phone awake and I'm trying to work out the best way to troubleshoot it.

If I were to do two logs of 4 or 5 hours, one with data on and one with wifi on, would you be able to compare the two?

The difference in sleep times when idle is ridiculous. Data gives me around 4% awake, whereas on wifi I get about 25% awake
[Android General] Celestial Fury:
The dump doesn't show drain due to your ROM issues. For comparison you can look at the attachments in Posts #1 and #2. Google quick search box is most likely the search bar in your home screen. I personally don't use it and just long press the home button if I want to search for anything.

If you've limited MCS Heartbeat at 43200 then it shouldn't appear much. Reset Amplify stats when you next do an idle test and see if Amplify is actually limiting it.
[Android General] Celestial Fury:
Without the hack, disabling the keep awake and run at boot setting in AppOps won't stick. Servicely can kill Play Services but it's hard to kill and it needs both these apps to stop the alarm_wakeup from occurring.
[Android General] Celestial Fury:
No double posting. Especially. Because reasons.
[Android General] Celestial Fury:
Yes. Traditionally you start with a low number then if it still drains you increase the number. The numbers in the guide have all been increased several times to the point where they no longer drain. Still, different phones will be different.
[Android General] Celestial Fury:
Yes but in a week when I'm back at a computer. It seems you have wifi issues. Try an idle test on a different wifi.
[Android General] ClownShoes:
Thanks, that would be great, although fingers crossed I will have cracked it by then ;)

I have tried a number of WIFI connections, all with the same repeatable issue
[Android General] ar2o:
If your getting the DHCP drain from wifi then just set your device IP address on your router to a static IP address and not a dynamic IP. The wakelock won't pop up anymore.

Sent from my SM-N910T using Xparent Skyblue Tapatalk 2

---------- Post added at 06:34 PM ---------- Previous post was at 06:31 PM ----------

I understand and thank hli for your response. So it is safe to use the limitations the guide offers but you still recommend to start limiting at the lowest number being 7200 to maintain device functionality. In worst case if I skew things I guess I can reset amplify in the settings and start from scratch :)

Sent from my SM-N910T using Xparent Skyblue Tapatalk 2
[Android General] ClownShoes:
Thanks, but that isn't my issue. Besides I've already assigned a static IP to my phone.

Cheers for the suggestion though ;)
[Android General] LilBlinx:
I somehow got convinced to try this and I am pretty impressed but there is a little problem (attached log file). When I unplugged the percentage dropped from 100 to 98 instantly.
[Android General] Portgas D. Ace:
Did you unplug your device right after it reaches 100%? From my experience you have to leave your device connected to the charger approximately 10 to 15 minutes after you reached 100%, because the battery percentage isn't totally accurate during charging.
[Android General] LilBlinx:
Trying that right now. I will post a log after that. I also have quite a lot alarms, services and wakelock that have quite a big count in amplify which aren't disabled
[Android General] Portgas D. Ace:
A high number in Amplify does not neccessarily mean a high battery drain. BBS gives you a good overview about what drains your battery.
[Android General] LilBlinx:
Again, the same thing, instant drop to 98%. Maybe it's just a faulty buttery but if someone could take a look and what can be blocked further it would be nice.
[Android General] Celestial Fury:
This dump is AFTER the sudden 2% drop so of course it won't show the alarm or wakelock that caused it to drop in the first place (if any).

First, in BBS advanced, stop using alarms and kernel wakelocks using API. It's less accurate.

Second, when your phone is charged to 100%, before you unplug, in BBS advanced select enable while charging then past the dump for that 2% period.

Third, use the phone until it's completely drained and shuts off by itself. Then charge to 100% with the phone OFF. Then see if the drop still occurs.
[Android General] Droid1019:
Thanks for this guide! I've limited everything I could find just like you have it and everything is good. Can I limit some of the other wakelocks showing up like: LocationManagerService, Networkstats, GCoreFlp, Icing, SyncLoopWakeLock, Wakeful StateMachine, GpsLocationProvider? If they're ok to limit, how long would you limit them for? TIA

Droid Turbo rooted running ComputerFreaks 5.1 image.
[Android General] Celestial Fury:
If BBS shows them as draining then you need to test them yourself. Anything not in the guide hasn't been tested by me and these don't drain for me. The point is not to simply limit and reduce functionality but only manage that which drains unnecessarily.
[Android General] PIRATA!:
[MENTION=5401012]Celestial Fury[/MENTION] ...I quote this again.

Would you implement please something for dating the limits so to check easily for new updates of the lists in OP??

It's difficult to check all of them always, and dating at least the edits would be good for understanding is something had changed.

Tnx.
[Android General] closee91:
Dude, if he hasn't responded before he's not going to. Don't clutter the thread with something like this. If he wanted to do it, he'll do it. He's doing this on his OWN TIME helping everyone out. So just let it go
[Android General] Jason761:
I tried this and followed your guide. But I'm not sure what other alarms/wakelocks are safe to limit.
[Android General] Portgas D. Ace:
Limit the following alarms and post another idle dump afterwards:

android.appwidget.action.APPWIDGET_UPDATE to 3600 (widgets will update once per hour)

com.google.android.googlequicksearchbox/com.google.android.sidekick.main.TrafficIntentService to 1800 (as I do not know what exactly this alarm is for, limit it to half an hour and check if you lost functionality. If not, you might even rise the number to 3600 or even 7200)
[Android General] PIRATA!:
I'm telling that for increasing the quality of the thread, not for spamming, so don't treat it as that.

Tnx.
[Android General] ar2o:
I understand where you're coming from but the OP went out of his way to even create thus thread and answers everyone's individual questions, no one else seemed to mind correct? I'm sure if something was invalid he would change it. I'm following the op for which ever alarms/wakelocks I have to limit and it's working fine no issues.

Sent from my SM-N910T using Xparent Skyblue Tapatalk 2
[Android General] Celestial Fury:
I already replied here. If you've been following this thread since about a month ago you'll understand the 3 sentences.

That said, the guide is quite mature and stable. I could put a 'new' icon and the date but you still wouldn't know it was updated unless I made a post saying it was and I'm not sure if it's important enough to make a post for 1 or 2 new things.
[Android General] Celestial Fury:
You didn't limit these accordingly:

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

Alarms: 15, Intent: android.content.syncmanager.SYNC_ALARM

You can limit these and test. I sometimes get these too after using Google Now for a while so I'll test them too.

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

Alarms: 26, Intent: com.google.android.googlequicksearchbox/com.google.android.sidekick.main.TrafficIntentService

How accurate do you need your widgets?

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

How accurate do you need this to be?

Alarms: 38, Intent: WeatherEyeServices_system_timer
[Android General] ar2o:
Limitting Suggestions Much Appreciated!!

Hey everyone,

I have made my first adjustment to alarms mainly google play services to reduce the drain and I am wondering how to proceed now? The limitations i set were to:

alarm_wakeup_activity_detection - 7200

alarm_wakeup_locator - 7200

android.appwidget.action.appwidget_update-7200

MCS_heartbeat-7200

com.google.android.aps.gsa.kato.action_inexact_alarm-7200

com.facebook.rti.mqtt.b.b.action_inexact_alarm-7200

com.google.android.gms./checkin.eventlogservice$receiver-7200

my drain to start with was 0.4% per hour and after adjustment went down to 0.3% per hour. Any suggestions on What should I be limiting next?

Any advice much appreciated :)
[Android General] Celestial Fury:
[MENTION=6388973]ar2o[/MENTION]

Basically, l like to limit whatever is over a minute or has more than a few alarms. In your case, it's mostly

location

alarms/wakelocks which aren't limited to once a day.

In the guide:

Alarms: 4, Intent: android.content.syncmanager.SYNC_ALARM

Then these:

Alarms: 24, Intent: {com.android.exchange/com.android.exchange.MailboxAlarmReceiver}

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

Alarms: 7, Intent: {com.quoord.tapatalkskyblue.activity/com.quoord.tapatalkskyblue.alarm.PingsOnAlarmReceiver}

Alarms: 7, Intent: com.myfitnesspal.android.IN_APP_NOTIFICATION_ALARM

Alarms: 3, Intent: com.facebook.rti.mqtt.b.b.ACTION_INEXACT_ALARM
[Android General] ar2o:
Thank you for your response Fury. what do you consider more than a few alarms, because in "Google play services" I have say 10 alarms but each one only reacting say 1-5 times (i.e. mcs_hesrt beat is 1 alarm but goes off say 5 times in a 7 hr idle span) in 7 hours. Are you referring the alarm count or overall alarms that go off during idle period? if so, then that means I have alot of google services that I need to limit even tho they only go off say 2-5 times during the idle state.

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

Yes, total during idle period. If you want to bring drain down some more, those are the ones that stand out.
[Android General] ar2o:
Would you say 0.1-0.2% drain is a "tolerable" idle drain rate? Once I start using my phone bbs shows say 1.8-2.0%/hr drain but I'm assuming it's accumulating total drain then which is skewing my reading.

I'll give that a shot tonight and post a dump file tomorrow. I guess that once I get all the alarms that are say higher than 5-10 counts and all I have left are individual alarms (alarm with 1-3 or so counts) that's when I start limiting those before I chose to go for wakelocks (mainly nlp_wakelock) hopefully I have the idea?

Also Sync_alarm which you mentioned to limit, that probably affects sync notifications which I have to be careful at. At the moment all my limitations are at 7200 seconds and I notice a difference.

Sent from my SM-N910T using Xparent Skyblue Tapatalk 2
[Android General] vctrrl:
I was out of the town for a few days. I'm using servicely and appops as recommended.
[Android General] Portgas D. Ace:
Well, according to your BBS dump file, your drain of 1.1% per hour is way too high, I think. The strange thing is that the number of alarms/wakelocks is pretty low, so there must be something different which is causing the drain.
[Android General] justyourimage:
Should / could be related to the Kernel or more likely the Modem / WiFi / Mobile Connection. Try to put your phone in Airplane Mode first and see if the Drain overnight changes.

You could try to flash older / new Modems, different Kernels and/or ROMs and see if the situation improves.

Otherwise nothing you can do since it 's probably Low Level / Hardware related (yea I know it sucks).

---

What I wanted to ask - [MENTION=5401012]Celestial Fury[/MENTION]: Are you using Sony 's Superstamina Mode ?
[Android General] ClownShoes:
Afternoon fellas,

could you take a look at my latest log?

Ignore the fact it's still at 100% battery. My G3 seems to hold a charge for quite a while before dropping, so I only bother looking at the voltage lost and sleep and awake times as I definitely didn't lose 0.0% battery in 7 hours :D

I've been getting greatly increased wake times while on wifi, so I now set it to switch to data connection when the screen is off, to try and nullify that.

Anything I can tweak here, without losing functionality?

Cheers
[Android General] Portgas D. Ace:
You could try to limit those two alarms, but remember that they affect push notifications:

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

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

Beside this there is no real potential to decrease your idle drain even further without loosing functionality :good:
[Android General] Celestial Fury:
Looks like ALARM_WAKEUP no longer drains. The dump doesn't show much drain from wakelocks/alarms. Have you established what the drain is for both baselines yet?

How do you charge the phone - with it on or off? When you use the phone try letting it drain and power off by itself then charge it to full with the phone off. Turn it on while still connected to the charger. When it's settled, unplug and let it idle.
[Android General] JazonX:
Hey Mate!

I've got a problem with Gmail. I cant see new emails as notifications until I open the app and pull down to refresh.

Is it because of the two alarms you mentioned above?

I've removed the limitations. for both. but still its the same.

Any other alarms related to this (Gmail Notifications) ?
[Android General] Portgas D. Ace:
Have you limited android.content.syncmanager.SYNC_ALARM? As far as I know, this one is responsible for Gmail sync. Limiting it to 43200 results in Gmail being synced only once per day.

Do you use apps like Greenify or Servicely?
[Android General] Celestial Fury:
Yes and in extended mode too. Unfortunately, my battery is currently bad so I can't tell how well it helps. Just got the phone back from repairs a few months ago so not keen on sending it so soon for repairs for another month again.
[Android General] hdmiacc:
how to setting AudioMix?
[Android General] Portgas D. Ace:
Leave it unlimited. It is responsible for notification sounds. You will not hear any notification sound if you limit AudioMix.
[Android General] Celestial Fury:
Without losing functionality - sure. Without losing some functionality - no. I can see alarms/wakelocks that aren't limited according to the guide. Hence, the voltage lost.
[Android General] hdmiacc:
okey, thanks. :D
[Android General] ClownShoes:
Thanks Orville, I thought that might be the case

Thanks Celestial, would you mind pointing out what doesn't look like it has been limited according to the guide? I thought I had it all covered, but may have missed something
[Android General] Celestial Fury:
Alarms: 45, Intent: com.google.android.intent.action.MCS_HEARTBEAT

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

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

Alarms: 3, Intent: com.android.providers.calendar.intent.CalendarProvider2

Once these are limited properly then check what the drain is like.
[Android General] Jason761:
Thanks I've tried both your suggestions. Unusually I've lost 5%/hr and I'm down to 56% battery. I also couldn't reset stats in Amplify. My phone only went into deep sleep 95% for some reason. What could've caused this huge battery drain?
[Android General] AlkaliV2:
[MENTION=5401012]Celestial Fury[/MENTION],

Just in case it hasn't been mentioned so far "com.android.internal.telephony.data-stall" breaks Wi-Fi calling on my Note 4. Device states that service is not available when this wakelock is blocked. I just wanted to mention this so if others have this issue you could post it in the OP next to that service to let T-Mobile users that limiting that wakelock could break Wi-Fi calling.

Thanks for the guide! I just finished blocking the items you had listed and rebooted so hopefully I will see no idle battery drain overnight tonight. It's clear you put a lot of time into discovering the apps that are safe to control and I'm glad you decided to share it with us :good:
[Android General] Portgas D. Ace:
95% Deep Sleep is okay, but 5.3% per hour drain is definively not okay. Have you checked your system battery stats? Maybe you can find the culprit there. Beside this there is no known (at least to me) draining activity logged in your dump file. Strange. Could you do another one to check if this hasn't been a once-in-a-while thing?
[Android General] ar2o:
Hey Everyone!

Can anyone help me track down the culprit which keeps my phone awake? Google play services has alot of individual alarms with 1-2 counts only so I'm not sure which I should tackle now. Any help is much appreciated as usual :)
[Android General] ClownShoes:
I've added all of these except for com.google.android.gms.gcm.ACTION_CHECK_QUEUE as you mentioned in the OP that it would probably break push notifications and I rely on them for my work gmail.

I am now getting better deep sleep but I'm noticing some notifications only arrive when I turn my screen on, hangouts being one of those. Is there a particular alarm out of the guide I should consider allowing if my notifications are delayed?

Cheers
[Android General] Celestial Fury:
Alarms: 5, Intent: android.appwidget.action.APPWIDGET_UPDATE needs to be limited some more unless you rely on widgets. Basically, just look at whatever has more than 1 or 2 alarms or more than 1 minute.

When the drain can't be found in wakelocks/alarms, check the network:

10087 (Wifi) (com.fevdev.nakedbrowserpro.Browser NBPro): 3.0 MBytes 55.0%

10100 (Wifi) (com.sand.airdroid.AirDroid): 1.0 MBytes 20.1%

Airdroid - was the phone still connected to your computer during the idle period? If you checked stock battery usage you could see when the drain occured - early or late. If early, then the drain could come from what you were doing then.
[Android General] Celestial Fury:
What exactly is WiFi calling and how does it work? Basically, this is not how limited alarms/wakelocks work. If an app is manually run/refreshed, the alarms/wakelocks will force trigger.

If a service is not available then it's probably a service that's being disabled/denied rather than an alarm/wakelock that's been limited. What about normal data connection - does that work with com.android.internal.telephony.data-stall limited?
[Android General] Celestial Fury:
These haven't been limited accordingly. If they were they shouldn't appear. Multiple apps are using them.

NlpWakeLock

NlpCollectorWakeLock

Basically all your location alarms haven't been limited accordingly. Then we can look at others.
[Android General] Celestial Fury:
All these will affect, not break push notifications and basically anything with 'sync' in it and don't limit anything related to what you need to use reliably.

com.google.android.intent.action.MCS_HEARTBEAT

com.google.android.intent.action.GCM_RECONNECT

com.google.android.gms.gcm.ACTION_CHECK_QUEUE

I think you need a longer idle period until BBS shows drain. Otherwise it's hard to tell if the drain is acceptable for the dump or not.