yashsingh1/xdaforums huggingface dataset:
[Android General] DB126:
I have no problem acheiving 0.2-0.3%/hr idle drain on Android 7.1 (LineageOS) without wakelock management or extensive tweaks on a modest handset. In my experience hardware, kernel and app suite are far more culpable than ROM or underlying version of Android. Likely Google Play Services and/or Firebase Analytics are driving screen-off wake time. That said, 0.50%/hr drain is within the expected range for most devices in absence of extensive/obsessive tweaks.
[Android General] Pvcabr:
I just installed xposed and amplify is not working :crying:

But you achieved this using social apps? Facebook, Twitter, whatsap, telegram, Tapatalk? Because the problem is with this apps and Google Play Services.
[Android General] DB126:
Let's see, five potentially chatty social apps and 0.50%/hr idle drain. Not bad. If you want better (err...why?) make sure all are 'battery optimized' in Nougat and supplement with Greenify as needed. Still not good enough?? Use automation to disable apps when the device sleeps. All that effort will, at most, buy you an extra 3-5% battery over 24 hours. Pick your poison.
[Android General] lollazzo:
Where can I find a guide to myandroid tools?
[Android General] DB126:
TMK there is no published guide. It's a tool for those who know their way around Android. Best source of information is probably forum posts and whatever the author offers.
[Android General] Oswald Boelcke:
My information are the same as the one of @Davey126.

However, this MyAndroidTools + Guide to disable some Play Services processes by @hastalafiesta may answer at least some of your questions.
[Android General] лацхезари:
Quote

Are you sure that this works?

* how to test *

Screen On needs to be less than a minute as we want to find out what's draining in idle mode. If you've used the phone then there's no way to tell what's acting up when it shouldn't be and there's no way to separate the active from idle.

In BBS Settings - Advanced

Untick Alarms using API & Kernel Wakelocks using API (it's less accurate) unless using API is the only way to show alarms & wakelocks for your phone.
[Android General] Oswald Boelcke:
I apologise I simply don't get the information in your post.
[Android General] speedy56:
Anything more I can do here? :)

The battery is about 1.5years old

(just ignore fstrimm wakelocks, I have it scheduled to trimm the memory every few days automatically)

Thaaanxss :fingers-crossed::fingers-crossed:
[Android General] Celestial Fury:
Sure. Post #2.

Alarms: 16, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_55376
[Android General] speedy56:
Thank youu :o

I have these 3 regex's set up, I thought the first one ([0-9]+) should block all of them :confused:

I'll set more of them (with [0-9]5,......etc) and see if it helps :)
[Android General] Celestial Fury:
One regex is enough. In your screenshot the 2nd one is the proper one but it's not displayed in whole. Just compare it with the one in Post #2.
[Android General] HeySora:
Hi, thanks for this very useful guide!

I'm still having battery issues (2.4%/h without touching the phone) that are coming from alarms (from "android": *job.deadline*, with 219 wakeups, and *job.delay*, with 74 wakeups) and from sensors (Google Play Services used the "Significant Motion Detector" during the ENTIRE Sleep, without any pause).

EDIT: Also, according to Amplify, an alarm coming from "Google Play Services" has been activated 347 times: com.google.android.gms/.lockbox.LockboxAlarmReceiver

How could I fix that? :/

(The dump is attached. As soon as I unplugged my phone, I just launched once BBS to be sure everything was right. And when I picked up the phone again, around 7 hours later, I instantly went into BBS to create a custom reference, to catch only sleep time in the stats/dump.)
[Android General] Celestial Fury:
There's a lot going on in your phone. I think you need to :

Establish Baseline (battery ONLY drain)

Establish Baseline (Airplane Mode)

See Post #3. Once we've established what those drains are like then we can move on to the next step.
[Android General] fridrik:
How can i improve?

Thanks for this brilliant tutorial
[Android General] Celestial Fury:
Level lost [%]: Bat.: -2%(71% to 69%) [0.3%/h]

Voltage lost [mV]: (4066-4066) [0.0%/h]

Level lost but no voltage lost which is not logical. Here's another reason to charge to 100% instead of measuring from a not fully charged phone. Don't mind if I link to this log from Post #3.

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

If you don't use widgets or use widgets that don't need to be refreshed frequently, you can limit this. Else, see Post #2.

Alarms: 1, Intent: com.google.android.gms.analytics.ANALYTICS_DISPATCH

See Post #2.

I'd feel the drain as logged will be more accurate if phone was charged to 100%. Also, see Post #3 for: IF Alarms & Wakelocks are already low.
[Android General] DB126:
For most devices the most accurate (and repeatable) drain representation comes in the upper quartile of remaining capacity with a starting value of 95% or less. That said, I recognize configuring BBS for mid-discharge capture is a hassle and camparing results across devices is less convenient with variable start points.

Convenience vs accuracy/repeatability is often a compromise with the former becoming more important at very low drain rates (0.5%/hr or less). Doubters only need to observe run time at exactly 100% immediately after pulling a device off charge. Pretty big variation which plays heavily into the calculated per hour drain rate on an idle device.

Not looking to start a debate. [MENTION=5401012]Celestial Fury[/MENTION] is the curator of this thread and has a different opinion. That's fine.
[Android General] Celestial Fury:
Nice to see you back [MENTION=5488402]Davey126[/MENTION]. If you mean the drain is less consistent if measured from 100% than from 95%, that's true according to Battery University.

Lithium-ion

5% in 24h, then 1–2% per month (plus 3% for safety circuit)

This means the battery drains faster from 100% (5% in 1 day) than from 95% (4-5% in 30 days) which means the total drain from 100% in 1 day more or less equals the drain from 95% for a whole month. :eek:

BUT apart from the fact that it'd be so much easier to achieve [0.0%/h] if measured from 95% (which would seem to be kind of cheating to me), we're also not just measuring drain - you'd be missing out on all the wakelocks/alarms that trigger between 95-100%.
[Android General] sohebq:
I am using customized Yowhatsapp. I have not limited any of its service. Also it is removed from power saving of System. Still at times it goes to deep sleep and i Don't get any messages until I Open it.

Now which service handles this beahvior?
[Android General] Celestial Fury:
Instructions are in Post #3 How to find problems with limited alarms/wakelocks.
[Android General] DB126:
Just a brief visit and response to something we are both passionate over :)

No cheating or trickery; just measuring total drain over a fixed period from a different start point (95% vs 100%). The same alarms/wakelocks will trigger with the same frequency/count regardless of when measuring begins. What will likely differ is the % lost during the measurement window and the often cited %/hour idle decay rate. Starting from 100% can yield less repeatable results on many devices as small overcharges/undercharges still show as 100%. Also, older batteries typically suffer an immediate 3-5% voltage drop when disconnected from the charging circuit before stabilizing. That can cause a quick decline in reported battery charge level which is erroneously attributed to background activity.

If the intent is to assess average hourly drain rate (as the thread title suggests) then starting at 90-95% charge as reported by Android will yield more accurate results. However, if the intent is to determine average hourly falloff from a "full charge" on a specific device then starting at 100% is obviously the only choice.
[Android General] NeEkOg:
There are times I get 0.0%/hr for the first 5-7 hours but it always ends up at 0.4-0.6%/hr. I always have gps(high accuracy) +wifi+sync(app+contacts+chrome+Gmail) on. My network mode is at GSM only since I never use mobile data at all. Please help me achieve the lowest possible idle drain with GPS+sync+wifi on at all times. Thanks!

Baseline Battery Only drain 2% @ 12hrs

Baseline Airplane Mode attached dump

Test Idle Battery Drain attached dump
[Android General] ytgbg:
Hi mates,

I was wondering and wasn't able to find any reliable info about the google services CHIMERA is waking my phone like crazy. I see in other people screenshots also.

It is fairly recent addition to google play services...

Does anyone know what this service do and is it safe to limit in Aplify, if yes by how much seconds?
[Android General] DB126:
Recent experience with a NEW (untuned) device reinforces this point. Starting from a full charge device remains at 100% for 12-15 min of steady use before settling into a steady 1% decay rate every 4-5 min. If I unplug this device while sleeping it will remain at 100% charge for hours then quickly fall to 99% upon waking. The average hourly drain rate over a 6-8 hour window would look very different depending if the sampling period began at 95% or 100% charge.
[Android General] b00dymoon:
I got 4% drain within 6 hours screen off any recommendations for stop drain.
[Android General] ipredatorv:
Does anyone have an idea how to limit Wechat's drain? I know the OP says it can't "be tamed", but that was a while ago. Did anyone find a clue how to get it under control?
[Android General] Celestial Fury:
(battery ONLY drain) [0.1%/h]

(Airplane Mode) [0.1%/h]

Idle Battery Drain [0.6%/h]

Idle Battery Drain log

Awake (Screen Off) (): 1 h 48 m 49 s

Alarms: 217, Intent: com.google.android.gms.gcm.HEARTBEAT_ALARM

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

10015 (Wifi) (Google Play services): 6.0 MBytes

First of all, you posted everything asked for in Post #3 and then some with nearly a whole day's worth of an idle log. If this phone is your daily driver, I'm going to have to call you out for - dedication.

Your battery ONLY drain can be safely assumed to be [0.1%/h] with the slightly higher actual drain due to the process of starting up the phone. Your battery ONLY drain and Airplane Mode drain highly discounts the possibility of a weak battery but it's also possible the manifestation of a weak battery could only be seen when processes (in the general sense) are acting on it. The fact that the phone is on KitKat could mean a battery as old as KitKat but I don't think so because:

960 MHz ():

25 m 10 s

(in airplane mode) that drains

only

[0.1%/h] = not likely a weak battery.

For further testing, you need to turn off automatic Google Play updates to remove the drain caused by downloading and it should also reduce your notification alarms. Save an idle log. If it's still high, limit the 2 notification alarms above (see Post #2) and save another idle log taking note of any push notification issues.
[Android General] Celestial Fury:
Chimera is a sort-of package management system for Google Play Services components, allowing Google to flexibly and independently upgrade each one.

In Google Settings, there is new option called Chimera Modules (you can enable it by taping 3 dots and then choosing “Show debug items”). I don't see this module. Might be only on Nexus phones.
[Android General] Celestial Fury:
Nearly 3 years actually. Amplify can't tame it but Greenify hibernates it very well. Not sure what its push notifications are like in hibernation. Not really using it and don't know what it's alarms look like these days but Amplify's regex limiting may now help so you can post an idle log or see Post #2.
[Android General] decebal12345:
Same problem. Do you have oneplus?

I can't find "job.delay" or "job.deadline" in amplify.
[Android General] NeEkOg:
I have been using my phone less and less nowadays so now is the perfect time for these tests. Hopefully I figure out the best possible configuration with your help!

The battery I'm using is a zerolemon 10,000 mah battery for note 3 with a year of usage to be exact. I have recalibrated the battery before doing any tests and after booting up straight to 99% after a full charge, it takes around 2-4hrs idle on average to drain from 99% to 97%. At around 90% below that's where I get a 0.0%/hr drain at around 7hrs or so but it's mostly hit or miss because the drain for next 7hrs will push it towards 0.4%/hr.

As for turning off Google Play updates, everything has been turned off when I did the tests so I don't know where that 6.0mb downloaded came from. And one more thing, what's the best Greenify setting to pair up with this setup? I currently have Deep Hibernation and GCM push unchecked btw. Thanks alot!
[Android General] Spegeli:
I'm a new Amplify User and i followed your and this thread: https://xdaforums.com/android/general/guide-extreme-battery-life-t3095884

The last 6 hours i done a Airplane Idle Test and i got a drain of ~2,7% per Hour (totally about 16% over 6 Hours)....and i dont know why and how to stop it.

Here is the BBS Log: https://pastebin.com/1ESewf0L

alternative i attached it to this post with a screenshot.

i hope someone can help me.

//Edit: i made now a small video with my Greenfiy / Amplify / PowerNap Settings: https://streamable.com/hf76x
[Android General] Celestial Fury:
Wow, and here I am lugging around a Power Bank. Looks like it was Play Services being updated which is automatic and has no setting. For Greenfy settings, it's more how you use the phone than its setup. For aggresive apps like FB and others, just greenify them and can even cut off their paths especially if you just use FB to browse.
[Android General] Celestial Fury:
See Post #3 last line in red.
[Android General] Spegeli:
No posting for help in multiple threads at the same time (unless you didn't get a reply or want a different opinion).
[Android General] DB126:
Posted same item in two different threads within 40 min. Give it 24-48 hours (min) before reposting.

https://xdaforums.com/showthread.php?p=74288453#post74288453

https://xdaforums.com/showthread.php?p=74288145#post74288145
[Android General] Celestial Fury:
That's an oxymoron actually since posting and getting a reply needs to happen at the same time. This will make better sense: No posting for help in multiple threads at the same time unless you didn't get a reply after a few days or want a different opinion). The rationale being a matter of courtesy.
[Android General] DivyanshuJ:
Can anyone help me understand what is going wrong in my phone. I am losing around 2% battery per hour idle drain at night. Despite using greenify.

I am attaching bbs dump. Taken last night. Phone was on airplane mode. I think it's the wakelocks.
[Android General] Celestial Fury:
It shouldn't drain this much in airplane mode. Would you mind charging to 100% before taking another idle log? Things don't make sense like the voltage lost.

Voltage lost [mV]: [90.1%/h]

Deciding on what to limit based on on a phone that was already in used before an idle drain log was taken is not something I would do and the log you posted does not look like an airplane mode log.
[Android General] DivyanshuJ:
Thank you!

I will take another log from 100% today.

I can assure that the phone was in airplane mode though.
[Android General] DivyanshuJ:
Edit:

This is the latest log, taken from 100% with Airplane mode.
[Android General] Celestial Fury:
Level lost [%]: Bat.: -7%(100% to 93%) [1.5%/h]

You can't get a lower drain in idle than your airplane mode. With your airplane mode this high, you might want to also take a battery only drain to set realistic expectations for this phone.

Awake (Screen Off) (): 55 m 46 s 19.3%

Kernel Wakelocks

fp_hal_wl (): 26 m 29 s

Seems related to fingerprint sensor.

Processes (requires root / system app on Android 4.4+)

fingerprintd (Android System): Uid: 1000 Sys: 2 h 17 m 55 s Us: 21 s Starts: 0

msm-core:sampli (0): Uid: 0 Sys: 1 h 19 m 7 s Us: Starts: 0

system (Android System): Uid: 1000 Sys: 1 h 6 m 45 s Us: 2 m 50 s Starts: 0

irq/248-tsens_i (0): Uid: 0 Sys: 41 m 44 s Us: Starts: 0

Alarms/wakelocks/services are mostly software related and don't usually cause such a drain in airplane mode. Your problem seems driver-related which means hardware-related. While custom ROMs are usually better security-wise than stock ROM, they aren't as battery-optimized as stock as seen from the logs posted in this thread. If you knew what your stock drain was like it would make a better comparison as to whether this is a custom ROM issue or a ZUK2 z2_plus issue. Or maybe wipe clean your fingerprint sensor.
[Android General] Taracair:
Could someone check my log?

Sorry it wasn't 100% fully charged, but 99% but I think it doesn't make so big difference in this case.

I always get around 5%-8% battery drain during the night. The log is created during airplane mode.

I think it's rom related. I have tried two different custom kernels and the results are the same.
[Android General] cristixperia:
Greenify only.;)
[Android General] DivyanshuJ:
I will clean flash my rom once and then will observe the issues again like fingerprint.

Otherwise I'll have to live with it.

Thank you so much for your help.
[Android General] Celestial Fury:
Voltage lost [mV]: (4028-4183) [-19,7%/h]

Another weird voltage 'lost' (negative) from an incomplete charge which makes it harder to compare drain from voltage lost with other logs. Comparing drain from voltage lost isn't usually done but I think something can be gleaned when we have a mental picture of what such drain is/should be like.

Level lost [%]: Bat.: -5%(99% to 94%) [0,6%/h]

An airplane mode only can certainly be lower. You might want to also take a battery only drain to set realistic expectations for this phone.

com.facebook.orca (): Wakeups: 15 (1,9 / h)

FB Messenger (?) can wait to get back online? I don't see any other (online capable) apps as eager in the log.

Alarms: 4, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_51823

Post #2.

OS.VERSION: 3.4.113-ArtxKernel-gb3a18d9-dirty

Finally, a dirty kernel as opposed to clean probably means you're working on the bleeding edge of software too.
[Android General] Celestial Fury:
(52% to 52%) Mid-used log.

Voltage

lost

[mV]: (3795-3827) [-3.3%/h] Voltage

gained

.

(See Post #3) Probably stucked. :D
[Android General] drotaru:
Is there a diference between using greenify in priviledge mode vs. Xposed mod ?
[Android General] cristixperia:
Without xposed you won't have access to "xposed-based features"(see attached screenshots).

Deci,este o diferență.;)
[Android General] Jrhotrod:
Are your Xposed-based features working in Greenify? Mine are not, maybe it's because [MENTION=4376588]oasisfeng[/MENTION] hasn't gotten Nougat support yet.
[Android General] jelive:
Are u using latest from playstore and activating in xposed modules.
[Android General] cristixperia:
Yes, working without any problem. My device is Xperia Z2 running android 6.0.1
[Android General] gvsukids:
https://pastebin.com/Tsw6tpWX

Log from overnight
[Android General] Jrhotrod:
Yep. Probably should have mentioned that I'm on Nougat 7?0.
[Android General] DB126:
Working fine here. Greenify 3.8.x, AEX ROM (Android 7.1.2), official Xposed Framework 88.2 w/installer 3.1.3. Your issue resides elsewhere.
[Android General] Celestial Fury:
I have to say I've never seen a null log before.
[Android General] galvao10:
Hello everyone, can someone give some tips on my overnight log? If need sceenshot let me know. Thanks
[Android General] gvsukids:
I'll try again
[Android General] silverstream:
I noticed that whenever I am roaming, I get extreme battery drain. Captured this log overnight, with Wifi and Mobile Data switched on. Dropped 32% overnight.

Looking at the log, I noticed that:

- The phone is awake for 72.6% of the time

- CPU stuck at 729.6Mhz for 68.4% of the time

- No significant wakelocks

Can some experts help me decipher the log ? Anyway to reduce battery drain while travelling ?

Note: I get 0% drain while not travelling.

THANK YOU
[Android General] Celestial Fury:
Don't really see anything to cause such drain on a relatively idle phone. Take an airplane and battery only idle log to get a narrower picture by eliminating online and phone/battery design sources of drain.
[Android General] Celestial Fury:
================

Kernel Wakelocks !!! wakeup_sources !!!

================

event0 (): 1 h 54 m 16 s

event16 (): 35 m 55 s

event18 (): 35 m 47 s

resume_wakelock (): 29 m 2 s

Roaming is for data and not wifi so turn off wifi. You don't need both on at the same time. When you travel you switch radio signal stations a lot. I imagine roaming would be more so. The drain is coming from the operating system that handles your cellular network.
[Android General] silverstream:
Thank you, I am surprised that having the phone on the table, overnight will drain that much despite not using it at all. "Surviving" the day travelling with a heavy draining is no fun....
[Android General] Celestial Fury:
If the log is from the phone on the table overnight rather than travelling then compare what other logs from the same phone+Lineage OS with your same conditions are like. If you need a full charge for the next morning, turn off the phone or put it into airplane mode the night before.
[Android General] Aniket Ghodake:
Hi, I am using Mi4i ...

battery drain is too much in standby(sleep) ..I have used all things greenify,amplify.

Battery drains 30% in 6 hours of sleep.(even airplane mode)

Help plzzzzz
[Android General] Taracair:
Log or didn't happen
[Android General] Aniket Ghodake:
Tonight I will charge my phone to 100% and keep it in airplane mode...will post sc of ( better battery stats)
[Android General] galvao10:
Thanks for your help [MENTION=5401012]Celestial Fury[/MENTION], Tonight I am going to take a airplane mode log, but this log show that a have Doze interactive time 28 seconds isn't it strange?
[Android General] silverstream:
Did a second night observation, this time,I have WIfi switched off, but mobile data is on. Interestingly I get 6% battery drain overnight as compared to 38% previously. Seems like the drain is from Wifi instead of roaming !
[Android General] mrjuniork:
Hello guys...

Could someone pls take a look at my BBS dumpfile? It'd be great :)

Thx in advance
[Android General] anon1135:
should those wifi scan alarms be showing up? even though wifi and Bluetooth scanning is disabled
[Android General] gvsukids:
Overnight, https://pastebin.com/7SLNqYJx
[Android General] galvao10:
Here's a airplane mode log, thanks for your time.
[Android General] Celestial Fury:
Not really idle since there are some downloads. Turn off Play Store auto updates. You also have both WiFi and data on. If you have root, get an automation manager to manage your connection. Otherwise, turn one off manually.

You can limit this (see Post #2):

CONTEXT_MANAGER_ALARM_WAKEUP
[Android General] Celestial Fury:
They shouldn't. Either you have the option "scanning is always available even with WLAN turned off" or applications on your phone other than android are trying to make connections.
[Android General] Celestial Fury:
Voltage lost [mV]: (4321-3783) [44.1%/h]

How old is this battery?

Phone On (): 8 m 43 s 1.2%

Can you explain this?

Screen On (): 15 m 45

See Post #3 first sentence.
[Android General] anon1135:
thx. might be all the different messaging apps thought I greenified or blocked all of them during doze/powernap. I'll test another night
[Android General] Celestial Fury:
Alarms: 556, Intent: *job.deadline*

Alarms: 1133, Intent: *job.delay*

JobScheduler running wild due to rogue app(s)? If BBS decides to explain Services stats properly there might be clues there.

"sec-battery-monitor" (): 10 m 7 s

Does Samsung have some battery monitor that can be turned off?
[Android General] galvao10:
I will investigate these *job.deadline* and *job.delay* but I might be related to HEBF optimizer app that has a doze function on it ( see sceenshot)

About "sec-battery-monitor" I have no idea. Is there any way to find out?
[Android General] galvao10:
I forgot the sceenshot.
[Android General] gvsukids:
Battery original.

Nope, nope. Except to grab the log