yashsingh1/xdaforums huggingface dataset:
[Android General] DB126:
Nothing jumps out; battery age is likely playing onto the elevated drain rate during sleep. You may want to consider a tool like Greenify that can disable motion sensors while the device sleeps to increase the time spent in doze mode. This is especially important on Marshmallow based ROMs; Nougat has this feature baked in.
[Android General] iroshan:
Thanks.

Just installed naptime. Will see at a log again.

Thanks for the help again.
[Android General] habylab:
Hi all. 12% loss over 7 hours. Can't see any major wakelocks myself. On 7.1 on my OP3 (stock ROM), custom kernel with Naptime installed.

Any help appreciated!
[Android General] Portgas D. Ace:
Statistic Type: Boot to Current

Screen On (): 10 m 35 s 2.1%

Hard to tell from those stats. Set the stats type for BBS to "unplugged to current" and produce another idle log file. Save the log file right after you turn on your screen.
[Android General] habylab:
Okay, will do again tonight.
[Android General] Zulfi zee:
Using a stock MM ROM on vivo y55l .. Wifi+location+4G data(ON) .. I used to screen ON is only about 25secs but it showing some minutes.. I don't kbow how its possible ..
[Android General] DB126:
And we are supposed to do what without a log?
[Android General] githyanki:
I have seen some amazing things from you Davey, I'm sure you're up to this!!
[Android General] firefly2k3:
Hi All, I know Moto Z is not an endurance phone but I used to get surprisingly good life out of the battery (at least 4.5Hrs SOT watching series on KODI over WiFi/4G) before the Nougat update. Now it loses 4% per hour even during sleep. I am on stock unrooted 7.0.

I've attached the BBS logs. I couldn't find any glaring anomalies but then I am no expert in reading BBS logs. So here's hoping someone knowledgeable can have a look and let me know if they can find the demons chewing away on my battery while I'm fast asleep.
[Android General] DB126:
First thought (after dismissing the usual culprits) was a rogue sensor and it appears the fitness service was a bit busy. Might check to see if related app or setting is in play. Google Play Services also racked up CPU time but that may be related to first item. Finally, log contained 4+ min of active (screen on) time which dilutes any idle analysis. Try to keep that <1 min on future posts with total run time of at least 6 hours.
[Android General] firefly2k3:
Thanks for your initial analysis.

Regarding the rogue sensor, I checked the Moto Actions (gesture) settings and found that "Double karate chop for torch" and "Twist for quick capture" were turned on. I could have sworn I had turned them off long back as I don't use anything other than the Active Display. Well I've turned these off now. Will get another log tomorrow with <1 min SOT and 6+ hours run time
[Android General] jackyaway:
Hi all, I have a oneplus 3 with nougat resurrectionremix rom and since android 7.1.2 I have a very bad battery life. Tonight the battery lost about 20% in idle. If someone can help me to find a solution is much appreciated. Thank you all. Here are the link to batterystats log, dmesg and logcat. http://cloud.tapatalk.com/s/5913f2883cd8f/BetterBatteryStats-2017-05-11_063539947.txt

http://cloud.tapatalk.com/s/5913f2962f72b/dmesg-2017-05-11_063540274.txt

http://cloud.tapatalk.com/s/5913f29c8182b/logcat-2017-05-11_063540204.txt

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Android General] habylab:
Hi again - I've managed to do a proper log this time. Anything stick out? Otherwise I'm clueless as to why my battery life has plummetted recently.
[Android General] DB126:
Fair bit of background activity related to Facebook, Instagram, WhatsApp and the good old Google search box (Google app). Also noted AquaMail, Bluetooth and location services were active although none were major consumers. Not sure why Nougat isn't suppressing background activity on those apps; might need to use a tool like Greenify to quiet them. Make sure none are explicitly exempted from optimization in your phone/ROM settings.

Still a bit surprised at the 16% drop with 45 min of low frequency activity over 7+ hours. Suggests an overactive sensor that isn't revealed in the BBS log. Make sure things you are not using are disabled, especially motion related items (eg: shake to wake).
[Android General] WuNgUn:
I did a short, unplugged sample using BBS. Here is what I got...

Email, AppyGeek, phone (phone?) I understand, but I can't figure out what the others are to "tune" them.

At the moment of picking up the phone, I lost 2% over roughly 6 hrs, however.
[Android General] DB126:
This shows nothing useful. Create a proper idle log as described in the linked post. That said, 2% loss over 6 hours (0.33%/hr) is not unusual and likely has no actionable items.

https://xdaforums.com/android/general/guide-extreme-battery-life-t3095884/post65025167
[Android General] jackyaway:
Thank you for the answer. I already use greenify with aggressive doze enabled and battery optimization is active only for aquamail.

Facebook and Instagram notification are disabled and also for Google app. Google location history disabled. I disabled gesture, tap2wake, etc.

I tried differents clean installations with differents gapps and root method but nothing change. Now i'm trying without rom encryption even if I know it isn't related, just because i'm trying everything...

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Android General] DB126:
- disable aggressive doze as it has been known to trigger the symptoms that you are reporting

- AquaMail can/will wake device if configured for push mail while excluded from optimization (also use AM and have suggestions if interested)

- recall GAppsless baseline suggested in previous post; really need that to conduct as well structured study

- regardless of notification settings FB and IG were active during screen off; disabling notifications does not quiet many/most apps, only mute the most visable actions. Same with Google App

- amount of activity exceeded what might be expected during normal doze maintenance windows; that said you might consider tweaking settings to reduce frequency and/or duration of those windows; I have no personal experience in this area as defaults serve my needs
[Android General] jackyaway:
So I disable aggressive doze and battery optimization for Aquamail. What do you suggest about aquamail?

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Android General] firefly2k3:
Hi! Here is the new capture with Moto Action disabled... still 4.1%/Hr drop while idle :(
[Android General] DB126:
There's obviously the option to sync on a schedule along with on-demand plus event driven such as when app is opening. Suspect you have considered that and prefer push mail (as do I). In that case consider disabling sync when the device is sleeping. By default AquaMail will respect that setting and not attempt any mail actions during screen off. Nor will any of Google's apps and any others that respect the devices sync settings. There are a bunch of smaller tunings that collectively can yield more efficient push mail but those are beyond the scope of this thread.

That said, you may not need to do anything following removal of AquaMail from battery optimization as mail will only be pushed/synced during periodic maintenance windows. See what happens and go from there.
[Android General] DB126:
Latest log is clean; thanks for that. Device was awake ~16 min over 6½ hours which is 3-4x more than one might expect. There was a 19MB download from the Play Store which suggest an app auto-update; might consider switching that off in Play Store settings. There was also 3½ hours of proximity sensor activity likely associated with Moto 'active' display. Typically that operates very efficiently; I have it enabled 16 hrs/day on stock Moto MM and have not seen significant drain (typically 0.2%/hr screen off with very few power tweaks). In short it's hard to understand where 4%/hr given what's shown in the log. I'd expect something on the 1% range.

Additional thoughts:

- WiFi was enabled during sleep; try switching it off (as a test)

- Might also consider disabling active screen (again, as a test)

- Also disable sync during sleep which *should* quiet Google apps/store

- Fitness sensor activity is still bothersome but I have zero experience with that sensor so don't know if it's a drainer

- Possible you simply have a bad battery that doesn't hold a charge; pretty rare on younger packs but it does happen

- Also possible nougat ROM isn't properly optimized for the X1650; I seriously doubt this is the issue but would be remiss is not mentioning the possibility...
[Android General] firefly2k3:
Thanks [MENTION=5488402]Davey126[/MENTION] !

Will try your suggestions and see how it goes though I don't have great hopes. Like as you said, from what we see in the logs, it should be much lesser in the range of 1-1.5% /Hr. I'm more inclined to believe Nougat optimisation issue as it used to be good before the upgrade to N.
[Android General] DB126:
One additional suggestion: reset battery stats from stock battery settings UI. This is normally used help find the bottom and (to a lesser extent), deal with non-linear drain. Possible cached stats got mangled during the Nougat update. I also noted a somewhat high fully charged voltage in BBS log along with a sharp drop off during initial discharge.
[Android General] WuNgUn:
Lost 2% over night.... But can you take a look at my log anyways? Thanks

https://drive.google.com/file/d/0B0EOPJak2Sf-ZmRjTGhsNmtnR3M/view?usp=drivesdk
[Android General] DB126:
- no need to compress small BBS log prior to upload; complicates access

- email app (stock Samsung) was biggest drainer; consider disabling 'push'

- bit of Facebook activity as well ...

- everything else looks fine (not optimal but good enough)
[Android General] WuNgUn:
Do you see which service in FB is the issue? Thanks for looking!
[Android General] githyanki:
Samsung email and Facebook were the largest drains, but even they were small. Unless you want to change over to Gmail app, and uninstall Facebook. I use Chrome to login there myself....

You could also turn off the play store checking for updates.
[Android General] WuNgUn:
Gmail is less of a drain, even with push notifications?

Thanks.
[Android General] DB126:
Try it and find out. Generally yes on Android 6/7 as Gmail observes doze rules.
[Android General] justjr:
Also try FB Lite instead of FB.
[Android General] SkaboXD:
I use Puffin FB, it's fast and it have more features then official Facebook app.
[Android General] Zulfi zee:
This s my bbs log on unrooted vivo y55l
[Android General] DB126:
Log is incomplete as special permissions have not been granted to BBS for use on non-rooted devices; see here for details. From the limited info available I could see device was active (screen off) for 41m which suggests excess background activity and associated wakelocks. That said, the 6% loss (0.9%/hr) is commendable given wake time. Can't offer any specific guidance due to lack of detail in the log.
[Android General] cristixperia:
My log without Wi-Fi or mobile data activated.
[Android General] githyanki:
Nice! Hope that carries over with them on.
[Android General] DB126:
Impressively low wake time and CPU frequencies even with network isolation. Appears you are using a combination of ForceDoze and Greenify. May have to try that. Any other thoughts/guidance in this arena (eg: options selected)?

I'm seeing my 0.2%/hr sleeping device with full network connectivity creep up to 0.3-0.4, primarly due to Google Play Services activity. I'm monitoring that to see if any action is needed. Might be an anomaly with the current build.
[Android General] cristixperia:
My daily setup is: grennify + amplify + force doze.

I have low wake time cause I use amplify.;)
[Android General] DB126:
Thanks for sharing. Not quite ready to resurect Amplify as I was able to score 0.1-0.2% per hour idle drain without it on a stock Moto MM ROM with minimal tweaks and all radios active 7x24. Many of the alarms and wakelocks noted in earlier thread posts don't result in significant drain on the device in question. I eventually may have to revisit that position if current idle drain rates (0.3-0.4%) continue rising. That said, I have been able to acheive similar outcomes on several other devices running LP and MM based ROMs (rooted/unlocked) using a combination of Doze and Greenify along with squashing a few egregious Google Play Services (eg: Firebase Analytics reporting). IMHO Amplify is a high maintenance tool that brings more trouble than benefit.
[Android General] :
While not a fan of blocking everything willy-nilly, I personally have found Amplify exceptionally useful just to limit the three system wakelocks: com.android.internal.telephony.data-stall, android.appwidget.action.APPWIDGET_UPDATE and RILJ. The first one gets crazily high, especially when on the move. It is really necessary to check / verify data connection that often? I do not think so. I have had no problems with it being limited either to 600s (as in the OP) or even to 900s. As far as the second one goes, I still do not understand why widgets are even updated when the display is turned off... That is why I have always blocked this one completely (when the screen is off, that is). RILJ has always troubled me with extremely high wakelock numbers which do not cause high drain one by one but all together equal to at least ~1 minute of awake time every hour or so.

When it comes to the other system wakelocks listed in the OP, I still limit them but I also do not think they cause any meaningful battery drain (at least not in my case ;)).

I am not talking about Google Play Services related wakelocks / alarms as I do not have them installed, but as far as system wakelocks go, just limiting the three listed above got me down to 0.1-02% drain per hour. Without Ampilfy the drain was double that. Still not high but definitely more noticeable.
[Android General] iroshan:
Can I block RILJ?

I thought it's related to mobile network.

Can someone tell me.

Thanks.
[Android General] firefly2k3:
Don't remember seeing this option to reset battery stats anywhere. Can you please tell me where to find this in Settings?
[Android General] :
I have always limited it and never experienced any issues. It is listed in the OP too!
[Android General] DB126:
Thanks for your excellent post; readers should review that in full (here) to get the full picture. I also see the wakelocks you reference on several devices but the raw numbers are relatively low and personally unconcerning. Suggests device, kernel, rom, carrier and/or environment (eg: signal strength) may be factors. For a while I limited data-stall and RILJ but observed no tangible benefits. Simply lowering raw numbers wasn't enough to justify continuing with Amplify. In the absence of benefits and/or side-effects it really boils down to personal preference. I need a reason for change; others are biased to abandoning change only when there is a reason. Seems you (and many others) obtain tangible benefits from Amplify without observable side-effects. Good stuff! There's another community that has had a different set of experiences, possibly due to the factors noted above.
[Android General] cristixperia:
[MENTION=5488402]Davey126[/MENTION]

What are the side-effects of amplify? :confused:
[Android General] DB126:
Varies by ROM. Bring up the stock battery panel under device settings. If not an overt reset button check under gear and/or overflow (three dot) menus. If still no joy install a jack-of-all-trades utility like 'L Speed' and reset from there (author/developer claims to use the stock reset mechanism).

---------- Post added at 02:54 PM ---------- Previous post was at 02:00 PM ----------

Well documented in this and similar threads. Most common include unstable device behaviors, inconsistent mobile operation (eg: device screen goes dark during calls; dropped/stalled data conmections), slow/no location acquisition, app stability issues (typically self inflicted by over-aggressive or inappropriate limiting) and extended wake times and increased battery drain from Google Play Services due to over-aggressive limiting of core services. Many of these side-effects can be avoided by carefully following the guidance outlined in the OP (plus first few posts) and subsequent refinements posted throughout the thread. One also needs to be cognizant of unpredicted side-effects and use proven problem solving methodologies to identify and eliminate sources of conflict.
[Android General] cristixperia:
I never had these problems :silly:

Take a look at my last bbs log.:eek:
[Android General] DB126:
Effectively no drain (zero wakelocks) on a fully network isolated device. Impressive result but how is that useful? During the same period I'll loose 1-2% with everything enabled. All radios, full location services, push mail, real time messaging, etc. Guess our objectives differ. Given this thread is titled "extreme" the discussion and followers likely favor that perspective.
[Android General] :
The RILJ does seem to be network dependent. I have crazy numbers on 3G but almost nothing on LTE. Everything with the same carrier. It does not seem to be phone dependent though as I have had similar numbers on three different devices (Nexus S, Galaxy Nexus, Galaxy S4).
[Android General] vagkoun83:
I have set RILJ to 7200 and I haven't notice any problem last year.

Sent from my LG-D802
[Android General] cristixperia:
I used Rijl at 1600 without problems.
[Android General] DB126:
By chance did either of you run a quantative study to see if limiting RILJ wakelocks improved doze/sleep time and/or reduced screen-off drain? Wakelocks in isolation are benign; receiver is what determines actions. If nothing is listening no action is taken.
[Android General] Bewildered Wolf:
Well at least for me, increasing Rilj time did nothing to improve the battery life.
[Android General] DB126:
Same for me but I rarely use 3G (only when LTE isn't available/reliable). See this post by [MENTION=5038522]tomasz86[/MENTION] for context.
[Android General] kk-ftp:
Hi guys,

Finally done a BBS dump file, this was overnight with wifi and data on sync on (for emails) . Please can you have a look and let me know where I can improve if at all.

Thanks!
[Android General] DB126:
There's a lot going on in the log. Weather widget, BBM, email and some other apps (eg: eBay) contributing to nearly 90 of wake time. Suggest installing Greenify to help identify and quiet background apps. You'll obtain even more control and longer/deeper doze windows, including doze-on-the-go, using Greenify's Xposed extensions. Marshmallow needs a little help falling into doze and staying there. An app like Greenify (there are others too; no specific endorsements) can make big difference without compromising device functionality. Many of these capabilities were added to Nougat based on learnings from Marshmallow. Good luck.
[Android General] kk-ftp:
Thanks for the reply. I should have mentioned I have greenify (with aggressive doze) and amplify installed. I did try installing powernap but found that I lost more on standby when I was using it compared to when not.

I'm thinking the weather app i use is using too much power and has too many alarms (which I've limited). So I'm thinking of removing it completely and trying a different weather app. My IM apps i like to keep so i receive push notifications for. I'm not sure why Ebay is causing my phone to wake. That has been greenified automatically and by normal battery save mode.

Email again is another killer. Is there a way for me to kill its wakelocks between specific times? I think powernap has this function but when I've tried it. It didn't really work!
[Android General] DB126:
I would dump (temporarily disable) Amplify and dial back Greenify to 'normal' doze. Also make sure Greenify is operating in boost (preferably) or privileged mode and 'doze-on-the-go' is enabled. Don't add apps to Greenify unless they are demonstrated drwiners; the overhead may be contributing to wake time. Finally, consider *temporarily* disabling email and/or IM apps during sleep to get a device baseline. With those gone it should sleep like a baby.
[Android General] zulfi984:
sorry for this nooby question.. how can i control battery lagging using on 3G & 4G networks.. it drains 15 -17% per hour .. so im getting only 5-6 hr of charge..i use only WhatsApp, imo, Instagram
[Android General] githyanki:
We could spend weeks guessing and having you try things, or you could get a bbs log. Read the OP for the directions on making one.
[Android General] Arstoien:
Hi there. Could anyone give me a hand? I'm typically getting about 1.5% screen off drain during the day, sometimes even higher. In the night it's usually 0.8–1%. I think things could be improved. Any advices? Sorry for the 3min sot, hope it doesn't interfere much.

Log was taken in the night, on wifi and 3g. In the day I'm usually running 4g only. I could make another log with only 4g.

PS: it seems most of the time Google sheets has been doing some syncing. If that's the only major thing, I'll see if I can sort that and see how it goes
[Android General] XDevOS:
Nougat users, how do you guys save battery?
[Android General] :
Use wifi, don't turn on data and gps, adaptive brightness. Power saving is already quite good, no need for Xposed.
[Android General] DB126:
Agreed. On one device I enable hardware GPS (only gets activated/used when by apps with location permissions explicitly enabled) and often disable Google Location Services which can generate NLP wakelocks. Another device idles nicely with Google's location services enabled 7x24 (0.2%/hr). I also find keeping data enabked is not a big consumer if the signal is strong; disabling in weak areas makes a noticeable difference. Overall Android 7.1 does a good job on its own as noted by [MENTION=6318692]AutumQueen92[/MENTION].
[Android General] Bewildered Wolf:
Can't use Wi-Fi all the time bro :P What should be done in that case?
[Android General] :
Turn on data when you need to, or leave it on until you get to a wifi area. It's up to you though, just use the phone as it should be used. Caring too much about every % battery life will just limit the capabilities.
[Android General] Bewildered Wolf:
But the screen on time has been reduced from Marshmallow to Nougat. Like on MM it used to be around 6-7 hours and on N it is maximum 4 hours with almost the same settings. Everywhere it is written that N is more battery optimized than MM then why the SOT has decreased drastically?
[Android General] :
Probably depends on their usage, or it could be a placebo effect. Ignore those claims, and just choose what suits you best. You said you're the proof that N doesn't optimise for everyone, so no need to beat yourself up tackling the problem.
[Android General] justjr:
Adaptive brightness is so bad? I hate have to change my screen brightness all the time, find it totally impracticable when I go outside and can't see nothing, and have to change it, then change it back.
[Android General] DB126:
A BBS study is required to identify potential drainers. ROM (especially kernel) must be optimized for device to acheive maximum battery endurance. Need a comparitive BBS log to make recommendations specific to your situation and device.

Panel brightness can have a huge impact on SoT. Slider position and perceived brightness level are not a reliable indicators, especially across different ROMs.
[Android General] Bewildered Wolf:
Btw do you use any battery saving apps on Nougat? Like MyAndroidTools or Greenify (all it is Magisk supported now)?
[Android General] :
Nope, my Redmi Note 4 already has amazing battery life so I just ignore all those crap. The closest thing I have to battery saving is an app to reduce game graphics and some kernel tuning.
[Android General] Bewildered Wolf:
Well, you don't need much on a 4100 mAh battery :P
[Android General] DB126:
Device/kernel/ROM dependent. Some change brightness levels continuously and are biased toward higher intensity for a given light level. Xposed mods allowed tweaks to brightness scale on some devices; not aware of an Android 7.x equivalent.
[Android General] :
Well if life gives you disappointing SOT, just get a bigger battery.

:3