yashsingh1/xdaforums huggingface dataset:
[Android General] kennyfool:
Does anyone know exactly what the RIJL wakelock does? It is my most active one. I've tried searching but haven't found a clear answer
[Android General] Celestial Fury:
Awake for 40 mins is not good. Some significant kernel wakelocks which Amplify can't reduce but let's work on the other stuff first.

I take it you don't use Greenify (with GCM) on Whatsapp? Greenify will help cut down on what needs to be limited by Amplify. My Greenified Whatsapp push notifications come through without needing to Amplify Whatsapp. Otherwise, limit these alarms but doing so may affect push notifications. The better alternative is to Greenify.

Alarms: 69, Intent: com.whatsapp.messaging.MessageService.CLIENT_PINGER_ACTION

Alarms: 69, Intent: com.whatsapp.alarm.CLIENT_PING_TIMEOUT

Alarms: 25, Intent: com.whatsapp.messaging.MessageService.LOGOUT_ACTION

Alarms: 11, Intent: com.whatsapp.MessageService.RECONNECT

Also:

Alarms: 32, Intent: com.google.android.intent.action.GCM_RECONNECT Doesn't affect push notifications as far as I can tell.

Same goes for Facebook, Greenify it and it won't keep trying to wake up when you're not using it. Else, you'll have to limit:

Alarms: 40, Intent: com.facebook.push.mqtt.keepalive.KeepaliveManager.ACTION_INEXACT_ALARM.com.facebook.katana but I don't use FB for messaging so I can't tell if push notifications will be affected.

In short, currently it's your FB and Whatsapp causing the most drain but for these two I Greenify them and not Amplify. Do either then take another reading.
[Android General] Celestial Fury:
A description of RILJ wakelock is given within Amplify itself. I am currently investigating if limiting RILJ can reduce "Radio-Interface" kernel wakelocks. The significance of this is if it's possible then Amplify can indirectly reduce kernel wakelocks although it was not designed to.
[Android General] aukhan:
Hi [MENTION=5401012]Celestial Fury[/MENTION]

I will Greenfly the Facebook and let Whats app be as it it as I would need reply them real time instead of delay.

Last night when I monitored them I dint have Google Play store setup it was not logged in, I shall Greenify the FB and few other user apps which I dont need real time updates and monitor them tonight and submit the logs and Screenshots again tomorrow so You could see and suggest what is the next step.
[Android General] aukhan:
https://www.dropbox.com/s/opq26xjig7j42ap/BetterBatteryStats-2015-02-12_094418981.txt?dl=0

New stats.
[Android General] Celestial Fury:
Well, the drain has slowed. Partial wakelocks are fine. Try limiting these alarms at 7200 seconds:

- com.oasisfeng.greenify.CLEAN_NOW

- com.google.android.gms/com.google.android.gms.checkin.EventLogService$Receiver

Whatsapp is still causing drain. See the attachment. It shows a greenified Whatsapp receiving push notification. You may want to try and see what delay if any you get.
[Android General] Mudahuda:
Any tip with this? The rest is okay.
[Android General] aukhan:
[MENTION=5401012]Celestial Fury[/MENTION] Thanks a lot for the help, I am gonna Greenify the Whats app tonight and monitor meanwhile can you tell me how can we avoid the wakelocks of Kernel ???
[Android General] Celestial Fury:
Well, the drain's not good. Nothing can really be done for kernel wakelocks but maybe this can help - it seems relevant to your kernel wakelocks. I can't see the rest of the alarms or how long the phone's been awake (under others). Maybe it's better to just post a Text Dumpfile - in BBS, --> Share --> Text Dumpfile and ATTACH (not post) the textfile.
[Android General] Celestial Fury:
Amplify can't limit kernel wakelocks. You have some generic named kernel wakelocks which I can't find anything about. I have added to Post #3 to further check what a particular phone / battery is capable off by ruling out certain things.
[Android General] urnamese3:
What do you think [MENTION=5401012]Celestial Fury[/MENTION]?

https://drive.google.com/file/d/0B8tpNiB7xja2azU2cV8tc1ZROXM/view?usp=docslist_api

Sent from my quantum computer yëyě
[Android General] Celestial Fury:
Awake (Screen Off) (): 8 m 7 s

1,25 GHz (): 8 m 51 s

com.facebook.orca (): Wakeups: 52 (6,2 / h)

com.facebook.katana (): Wakeups: 42 (5,0 / h)

com.instagram.android (): Wakeups: 42 (5,0 / h)

com.google.android.gms (): Wakeups: 24 (2,9 / h)

android (): Wakeups: 22 (2,6 / h)

Your phone was running at max CPU speed for 8 mins.

*alarm* and *launch* - Post #3 Test Idle Battery Drain No. 6.

I think you didn't read Post #3 last line.
[Android General] atrix4nag:
This is my idle dump, with wifi on.
[Android General] hawkdown77:
hi, in the first post, i cannot find some alarms, why?? im using LP 5.1 stock XT1058
[Android General] Portgas D. Ace:
Then you should read post #2... ;)

If some of the alarms from post #2 are not present on your device, just ignore them. Some alarms won't appear on some devices, it depends on your personal setup.
[Android General] Ph0z3:
Not too shabby...

Still have some tuning to do, and other wakelocks to look up, but for just the values you've listed, I got this.
[Android General] louiscar:
Wakelock 1013 - audiomix

I ended up here as my Samsung tab s suddenly started using a lot of battery when turned off (mainly if wifi is left on).

So Amplify , Wakelock detector and DisableService installed.

What immediately shows up is that Audiomix is producing an insane number of wakelocks constantly - these show up in 1013 and Android system both together in 12 mins uptime they have taken up 3 mins of that.

I have no idea where to look on this as this drain didn't happen until a few weeks ago and I've not really installed anything new (that I remember ) in that time. I am on Kitkat and it seems like a lot of complaints arise from KK.

I decided just as a bit of mischief to limit audio fix to 9999 in Amplify just to see what would happen. Fully charged at 100% it took 30 mins before I saw 99% and I was using the tablet!! Touch sounds are on and they continued to work - I didn't see any adverse affects in the short time I disabled it but of course that doesn't mean it's safe to do so ideally would like to track down the cause.

I've enabled it and the wakelocks are just pouring through again.

Having followed some of the advice here it's not made much difference so if anyone knows what might be the problem. I don't want to disable touch sounds as this isn't the problem (I'm pretty sure since they've always been on and the problem has just shown up).

I cannot find a way to track down what 1013 process actually is or what app is causing. Typically Android system > audiomix accounts for about half of the 1013 > audiomix wakelocks so if the latter has 2 mins the former will be about 1 min.

Annoying - would be good to hear if anyone has the same problem particularly if it suddenly started to plague them and if there's a solution.
[Android General] Ph0z3:
Are any of these safe to limit? ..if so, what can I set the values to?

# WAKELOCKS #

*vibrator*

BaseIntentService

bugle_datamodel_service_wakelock

UlrDispSvcFastWL

bugle_background_worker_wakelock

dashclock_DashClockSer

RingtonePlayer

GCM_HB_ALARM

kpx

# ALARMS #

com.android.deskclock.ON_QUARTER_HOUR

com.android.server.action.NETWORK_STATS_POLL

com.google..apps.dashclock.action.PERIODIC_ALARM

# SERVICES #

com.cyanogenmod.lockclock/.ClockWidgetService

com.android.providers.calendar/.EmptyService

com.mycolorscreenthemer/org.zooper.zwlib.UpdateService

com.google.gms/.icing.service.IndexWorkerService

com.google.android.gms/.people.service.PeopleRequestProcessor
[Android General] MrBrady:
Just purchased the donation version of Amplify. I assume the guide on the first page is still valid for the most part. Any suggestion of things to add or remove?

I don't have an Android Wear device (yet), but I do use Google Fit and Google Maps Timeline frequently, if that makes any difference. Those are both use passive constant location.

Device: Nexus 6 running Pure Nexus ROM (Android 6.0)
[Android General] razvantudurache:
Pls can i limit somthing on this??

Trimis de pe al meu SM-N920C folosind Tapatalk
[Android General] Portgas D. Ace:
There is a solution: limit it to the maximum value possible. The only side effect: you will not receive audio notifications such as ringtones or alarms, as Audiomix is responsible for the audio notifications of your device ;)

Nevertheless, I would recommend to leave it as it is, because a high number in Amplify does not mean that the related alarm drains much battery. For this, you should use Better Battery Stats (available here on XDA) to identify the biggest drainers instead of Wakelock Detector or Amplify.
[Android General] Celestial Fury:
com.google.android.gms (): Wakeups: 16 (3.4 / h)

Does clicking on it in BBS screen show the individual alarms? For MM, the dump doesn't show it. Attach the screenshots for: IF Alarms & Wakelocks are already low.

You need to attach the BBS text dumpfile to show the draining alarms/wakelocks for the tuning.

Post #3 How to find problems with limited alarms/wakelocks No. 1.

If you find these two apps affected, don't limit the location alarms/wakelocks.

Post #3

Test Idle Battery Drain No. 6

How to find problems with limited alarms/wakelocks No. 1
[Android General] atrix4nag:
MM is not showing detailed wakelocks. Screen shot attached.

Also I have attached todays dump. I lost 1% per hour in span of 7 hours. I have disabled everything except the once with cloud sign, because they may block notifications. I need notifications. If this battery is fine with my requirements? or can I get some more juice with it...
[Android General] kschang:
Very interesting and thanks for the initial guide. A lot of the initial ones are for Facebook (which I don't have) and I have Motorola so there's a bunch of Moto stuff in the background.

Still, with this guide I was able to sap background idle (i.e. phone face down doing nothing) to 3-4% per hour, which is a far cry from 10% per hour before, and this is on L, not M. I do have that new "Doze" app working though, and I haven't disabled any services yet. The lowest I've been able to do before was 8% and that's with GravityScreen / Greenify / Amplify (on basic stuff).

We need some sort of Amplify "repository" where we contribute to some sort of Android Genome (like Soluto for PC) and crowd-source what people did with the app / service / wakelock: limit, and for how long? Then we can choose to accept crowd setting or set our own.
[Android General] f0xy:
This sounds like a good idea!
[Android General] dasojie:
Hello ...

i got alarm wake up from com.android.keyguard(

com.android.internal.policy.impl.phonewindowmanager.delayed_keyguard)

it aosp lockscreen, maybe the problem is when i uninstall htclockscreen.apk odex.

do you thing i can limited com.android.keyguard?

regards

htc desire 601 kitkat 4.4.2 kofilakernel stock rom
[Android General] Celestial Fury:
As MM doesn't show detailed alarms, it's hard to tell if you can get more juice. Based on:

Awake (Screen Off) (): 3 m 17 s

300 MHz (): 2 m 39 s

which are quite low, I'd say there are phones which can get lower than your [1.0%/h] with similar stats. Besides alarms/wakelocks, drainage can also occur with reception, etc. so see Post #3 and Attach the screenshots for: IF Alarms & Wakelocks are already low.

3-4% per hour is high so attach a dump if you want to fine tune. This repository not good enough? The basic android draining alarms/wakelocks are in the guide. Anything else like FB (which I happen to use) and for privacy is just extra. The guide was started to help me remember/refer to what I had limited. I needed to put them down somewhere and if they help others then even better.

You can click on it in Amplify and it'll show you that Keyguard is part of the System UI and if you don't think that's important then be prepared for not being able to (un)lock your screen. I can also guess from your screenshot that you've been using your phone and have probably been locking/unlocking, hence the alarm. This is also an idle battery drain guide and the emphasis is on

idle

.
[Android General] hawkdown77:
I have noticed that after following the recommendations of the OP, my alarm is set for the 7:00 am but only plays if I switch on the mobile screen ... then he touches and pops up a notification of lost alarm. What service that is on the first page of the topic is connected to the alarm? Almost missed work time 2 times.
[Android General] Portgas D. Ace:
Whitelist your alarm app within PowerNap. If you use the built-in clock for alarms, whitelist Clock.
[Android General] hawkdown77:
But the clock is already on the whitelist. Some of the alarms/wakelocks on the front page has some connection with the clock/alarm? :crying:
[Android General] Portgas D. Ace:
Did you limit anything with the red cloud symbol? Maybe you have to whitelist Android System and System Framework, too.
[Android General] hawkdown77:
Yes, i did. I will try whitelist android system and system framework

---------- Post added at 09:08 AM ---------- Previous post was at 08:57 AM ----------

If I use an app for alarm and release him in the POWERNAP, still have to put the android system and system framework on the whitelist or not needs?
[Android General] Portgas D. Ace:
Yes, it is recommended to whitelist Android System and System Framework beside your alarm clock app. The developer of PowerNap hasn't integrated this by default or at least put a note somewhere about this, although this issue has been reported several times.
[Android General] hawkdown77:
Huum, ok.

Maybe if i whitelist android systema and framework i will increase the Idle drain i think.
[Android General] istweiter:
Cool!
[Android General] Ph0z3:
hey [MENTION=5401012]Celestial Fury[/MENTION] i had an idea...

You should add a date to the main thread title, so that way, when you add new items to the OP, others can see when it was updated.

Also, add some type of "new" sticker or emoji to said, new items.
[Android General] Bijuu:
What about that?
[Android General] Celestial Fury:
If you did a search [Ctrl-F] for alarm clock in the first page of this thread you would have noticed the DANGEROUS - DO NOT LIMIT / DENY section.

You would have also noticed that PowerNap is NOT in the guide. I assume you've been following another guide where it is recommended so I wonder why you chose this thread to blame.

No, because of Post #3 last line. No point of dated update if what was posted before isn't read. And no, because what's posted in this thread is shamelessly mentioned in other thread without a link to the original discussion (ex. WiFi calling, Post #2).

What about it? Nice pic.
[Android General] Bijuu:
[MENTION=5401012]Celestial Fury[/MENTION] what about com.google.android.gms.gcm.heartbeat_alarm ? I have this one instead of - "com.google.android.intent.action.MCS_HEARTBEAT". Can i limit that?
[Android General] Celestial Fury:
Sounds similar. On MM then? May be a new push notification method. You can try then check how acceptable the delay if any.
[Android General] garthybarthy:
It's new push I think, I'm on lollipop still and noticed it. Limited it and haven't noticed any problems yet but having been using WhatsApp etc to check for delayed notifications yet.
[Android General] Bijuu:
It's on lollipop. That's why i got suspicious if its the same :P
[Android General] albion93:
Hey guys i did a test..i think it's good

https://www.dropbox.com/s/0oqsssvt2olo864/BetterBatteryStats-2015-12-08_093041419.txt?dl=0

Inviato dal mio HTC One utilizzando Tapatalk
[Android General] mtwalther:
Appreciate all the effort that went into these investigations. I've been using PowerNap, alongside ApsOpsXposed, and Amplify. Battery life on my Moto X Pure has increased dramatically since I began tweaking a few days ago.

I have a few alarms left showing up in BBS, and really not too concerned about them, but wondering if there are any suggestions for the remainder of them. I've got it configured well enough that I'm still receiving notifications from Hangouts, and Gmail (which are the two most important) and don't want to hinder these two. Given the fact that the top alarm is still Google Services, I just want to be sure I'm not going to disable anything I need. My ApsOps and Amplify are both fairly extensive already but any suggestions would be great.

Mind you - the screenshot provided isn't really reflecting %/hr as I've had my screen on for the past couple hours...

Thanks All!
[Android General] Celestial Fury:
The top two alarms are general and can't be limited. You need to click on them and show the detailed alarms which can be limited. It's more difficult to limit something based on an active screenshot or log because you'll have to know what apps you were actively using and then limit the wakelocks/alarms caused by apps you weren't using or limit the ones that you don't need in the apps that you were using.
[Android General] helix139:
anyone know what causes the android.net.netmon.lingerExpired_###_######## random number alarms? or have a regex to get rid of them?
[Android General] nitishp7890:
[MENTION=5401012]Celestial Fury[/MENTION] can you make a titanium backup file of your amplify it will be good because we just have to restore this file thanks for this settings very helpful
[Android General] Portgas D. Ace:
As far as I know, this won't work due to different hardware/software. This results in different alarms/wakelocks for every device. Nevertheless, a little contribution by yourself wouldn't harm you ;)
[Android General] nitishp7890:
Ohh i didn't know that it is different for different devices my bad then i will do it myself
[Android General] :
Yellow. Can someone kindly take a look at my bbs? It seems weird. Always, the android system is "keeping the phone awake" all the time. However, the phone actually goes into deep sleep. And I don't lose much battery during idle hours. But I wanted an expert opinion, so here I am. [emoji2]

Thank you in advance.

https://onedrive.live.com/redir?resid=BB14C58E8FA67B75!205&authkey=!ANmxO7eZucKxip0&ithint=file,txt
[Android General] Portgas D. Ace:
Search for Android MobileRadio bug. There is an Xposed module to solve this issue. Seems you are affected by this bug.
[Android General] :
I will try the above mentioned solution and get back to you. Although, I don't see my mobile radio as wreaking havoc in the bbs report. But still, I will give it a go. Thank you. [emoji10]
[Android General] leAndroid91:
Hi guys, by following the guide on the first page i was already able to limit my battery drain to 1% per night (7+h). So thanks for that awesome work :good:

But i would like to get your feedback if some more optimizations are possible.

Step 1 - battery/hardware only drain

Since my Nexus 5X is brandnew i didn't expect any hardware related drain.

So i charged it to 100% left in turned off for 3h, turned it back on and after booting and waiting for some minutes it still had 100% battery.

So i think this is fine.

Step 2 - airplane mode drain:

1% at 7+ hours

See BBS file "BetterBatteryStats-2015-12-10_080045394" in attachments and screenshots 1-9

Step 3 - idle drain (phone, wifi turned on):

also 1% at 7+ hours

See BBS file "BetterBatteryStats-2015-12-11_090030624" in attachments and screenshot 10-20

I know that it's said that i can't get any better hen in step 2 airplane mode drain.

But in BBS i see a lot of alarms from instagram. But i don't find instagram on amplify? Neither on Wakelocks nor on Alarms :confused:

If you see any additional potential to safe battery - without losing any features - please let me know or do you think everything is fine.

Thanks for y'all awesome help :good:
[Android General] leAndroid91:
for the completion screenshot 19 and 20
[Android General] deepu458:
Hi Folks,

please help me in getting this battery life better i dont know what i did wrong from past week onwards the Battery dying faster on me just Updated Kernel thats it. So kindly go through the attachment and help me wht Wakelock or Alarm Or service is the cause of the drain. So that i can fix that.

P.S Edit: I had cleanly observed the logs and it shows that all my services are running from 8 hours but where as i had this log been created because of unplugging the device around 3 hours after How come services run 8hours? Are these services running because as i dirty flashed the ROM and Upgraded the kernel last night ?
[Android General] cartman_73:
Do you have BT, location, Wi-Fi always on?

Inviato dal mio X9006 utilizzando Tapatalk
[Android General] deepu458:
Thx for replying, yes i have Location & WIFI always on but not the BT. I haven't switched on the bluetooth since from past 3 to 4 weeks.
[Android General] cartman_73:
Your BBS log shows that the phone was booted since 8 hours, it is because you have 8 hours of service. Try to charge your phone to 100% in the evening then reboot and take the phone to sleep. Tomorrow morning when you wake up save your log and post it.

Inviato dal mio X9006 utilizzando Tapatalk
[Android General] deepu458:
Thanks cartman, will do that tonight. But is there any wakelock or Alarm or services or Kernel you think of thats draining my battery ?
[Android General] entonjackson:
I can recommend you a nice app.

Disable Service.

I have around 30 Google services disabled. Only 2 are left and messaging and navigation still works. If you like to see my settings for it, let me know.
[Android General] cartman_73:
You have this in log

PowerManagerService.WakeLocks (): 3 m 7 s Cnt:(c/wc/ec)342/55/0 1.8%

wlan (): 2 m 6 s Cnt:(c/wc/ec)76/29/39 1.2%

And the max alarm are for gms, if you have Wi-Fi scan on turn it off, if you have greenify, include the app that uses gcm, if you don't use.

The first warlock is related to system, maybe is a cyano's issue.

I'm not an expert [emoji4] test and verify the result.

Inviato dal mio X9006 utilizzando Tapatalk
[Android General] EzerchE:
Hello, can you share your disabled services? Thanks
[Android General] deepu458:
That would be a gr8 help if u can tell me wht services u have disabled.

Edit: i have attached the log now from last night. Please see and let me know wht i can do.
[Android General] Celestial Fury:
Mobile radio "bug" is for the mobile radio active which does not appear in BBS and has nothing to do with the draining *alarm* that seems to plague some custom ROMs. As your drain is already low, see Post #3 IF Alarms & Wakelocks are already low...

com.instagram.android (): Wakeups: 43 (5.8 / h)

com.facebook.orca (): Wakeups: 41 (5.5 / h)

android (): Wakeups: 21 (2.7 / h)

Fix these 3 and you should get [0.0%/h]. There's something different about the way Amplify and BBS count the alarms. It's mentioned in Amplify OP.

Basically, your push notification and Google location alarms that you haven't limited according to the guide that's causing the most drain.
[Android General] entonjackson:
Attached my settings for Disable Service.

What you need to know, the following things probably won't work properly with these settings:

Google Play Games

Any Wearable and Fitness crap from Google

Backup Crap from Google? (Don't know what this is for, anyway...)

As already mentioned, what still works for me:

Messaging

Navigation

Google Sync for GMail

...

Have fun and enjoy more battery time.
[Android General] hawkdown77:
Hi, did u disabled these services with what APP?
[Android General] edwardob:
playstore disable service by wangqi
[Android General] hawkdown77:
I like used whatsapp and facebook messenger... Can i follow your disabled services or i will get problem with notifications in whatsapp, fb messenger and viber?
[Android General] edwardob:
not sure why your asking me.... it's not my disable services.... I wouldn't know
[Android General] hawkdown77:
Oh sorry..i made mistake...

But do u use this app too??
[Android General] edwardob:
yes but I'm only trying it out.... any it's easy to use.... just re-enable something if it's not working out
[Android General] Acxjet:
Thanks for this guide! It's really amazing and the guide is helpful. +1