yashsingh1/xdaforums huggingface dataset:
[Android General] DB126:
Yes, but you need to read as recommendations have changed over the years. Better yet submit a BBS idle log for analysis to help identify them culprits so you can target remediations.
[Android General] David42:
Sorry. I am new. Will use before I ask next time.

I will consider doing that. I need to do some more research first, though.
[Android General] ProudRed:
http://cloud.tapatalk.com/s/594c7537e703e/BetterBatteryStats-2017-06-23_072057034.txt

Lost 3% in 6 hours. Will the log be helpful now to detect the root of problems ? Have selected from charged to screen on. Most apps were greenified this time including play services. With play services not greenified, the device was staying awake entirely.
[Android General] githyanki:
Level lost [%]: Bat.: -3%(100% to 97%) [0.4%/h

Deep Sleep (): 6 h 41 m 53 s 99.1%

Awake (Screen Off) (): 3 m 40 s 0.9%

Your log says that things are running well..0.4%/h is a good number.

With that in mind, the top issue was firebase, followed by MacroDroid. If you find a way to get rid of those items, you can get a bit of improvement. If not, then 0.4% is still a good thing.
[Android General] ProudRed:
Macrodroid alarm has already been limited to 99999999. Is it safe to limit firebase alarm ? And yes I am losing almost 1 at idle time and if I receive an SMS device stays up for 3-4 minutes. Have greenified Play services and other system services for better results.
[Android General] Oswald Boelcke:
As far as I remember Amplify from the times when I used it, maximum number was 9999999 but I can't prove. Maybe, it doesn't work with 99999999?
[Android General] ProudRed:
The maximum number of 9 has been set lol.
[Android General] DB126:
Traveling for a few days - brief comments:

- did not look at latest log; that said 0.4%/hr is a reasonable idle fall-off rate

- small amounts of wake time is not especially important as modern devices idle efficiently

- impact of Firebase Analytics an be suppressed by stopping PackageMeasurementService (subcomponent of Google Play Services) with MyAndroidTools

- above service will periodically try to reenable itself; use MyAndroidTools Xposed (separate app) to prevent this

- most members report significant side effects Greenifying Google Play Services; if you can get away with it great!

- also note the above action simply masks the symptoms triggering excess drain vs addressing the core problem
[Android General] ProudRed:
Play services keeps the device awake. If there was a fix for it I would stop greenifying in. You can suggest me something if you know of.

I am open to finding out the symptoms of drain if the device can be putto deep sleep.
[Android General] Oswald Boelcke:
Did you ever consider to simply go GApps-free and to use microG? As long as you are on a ROM that already comes without GApps installation has become quite easily. Here I described how I did it on our devices in February, but now I'm using NanoMod (still with Magisk but that isn't a requirement anymore).

By the way and off-topic: Is that Liverpool with my favourite coach Kloppi in your avatar?
[Android General] :
[MENTION=5488402]Davey126[/MENTION]

You are awesome man. I learn a lot from your battery analysis review every day. :good:

---------- Post added at 05:41 PM ---------- Previous post was at 05:37 PM ----------

@ProudRed

Have you tried the "enable doze for Google play services" flashable script available on XDA? I am using it and can say that my device sleeps better now with aggressive dozing.
[Android General] ProudRed:
I dont mind, but I am on stock rom of Oos 3.5.4. Can it be done with stock rom ?

To the off topic question - I dont follow any small club from merseyside haha.

---------- Post added at 10:36 PM ---------- Previous post was at 10:32 PM ----------

I will check for the script. But does it really let the device sleep ? Have you checked your battery from settings section if there is anything that keeps the device awake after greenifying ?
[Android General] :
[MENTION=7081077]ProudRed[/MENTION]

Most of times when my device is awake, it would be due to Android System or Google Play Services or rarely due to some rogue app. Greenifying and denying background permissions eliminates the rogue app. Using the doze script allows Play Services to doze which is noticeable on battery stats. Strangely enough, dozing of Play Services somehow eliminated my Android System wakelocks too.
[Android General] DB126:
Submit an idle log (BBS Watchdog processing enabled; screen off -> screen on) with Play Services NOT greenified to help identify the culprit(s). Vast majority of devices sleep just fine without greenifying system services. At some point you'll experience issues including higher drain with Play Services greenified.
[Android General] DB126:
Yep - Google Play Services invokes a number of operations (eg: Firebase Analytics data aggregation and reporting) that involve Android core services. Correlation expected.
[Android General] Oswald Boelcke:
No, I don't think so. You require a ROM that comes without GApps.
[Android General] ProudRed:
One major issue I have noticed with my phone is that, when my Wifi is on and its not connected to an wifi - when I disable wifi and connect data. My battery stats in settings show wifi was on all that while from the time It couldnt connect to the wifi, till the time Wifi wasnt turned back on. Even after manually turning of both couldnt fix the problem. The only fix was when I turned on and my Wifii could connect to some wifi network this stat wouldnt show up. Anyone ever heard or had this issue with their phone ?
[Android General] peterlee928:
try this:

1) go to settings

2) go to location

3) click on 3 dot menu

4) go to scanning

5) if "wifi scanning" is on, then turn it off
[Android General] ProudRed:
These all are already done. Still cannot find the root to the problem across all my phones.
[Android General] DB126:
Wait..."all my phones"? If occuring on multiple devices you need to consider common items:

- same room and/or kernel?

- same router/wifi? consider setting a fixed IP or changing WiFi channel

- weak mobile signal?

- similar app suite?
[Android General] ProudRed:
No man both have been stock roms, and custom roms.

Even Wifis have been different. Similar app suite as in ?
[Android General] ProudRed:
Switched to Nougat RR - left the phone last night idle after charging full to 100% for little more than 4 and half hours. I know that's not the ideal time for BBS dump, still it can help me determine the problems for idle battery drain ? I do not have amplify anymore and can only block alarms, services and wakelocks. From the BBS dump its visible there were lot many alarms and wakelocks. Any suggestion as to which ones I can block ?http://cloud.tapatalk.com/s/594f360f3ea0b/BetterBatteryStats-2017-06-25_092838326.txt
[Android General] jlb1959.01:
can any please explain what could possible be causing the mobile radio draw???. is that do to kernel?. I'm on blisspop 6.4, custom gamma kernel.no other extra apps,meaning,greenify,etc.. thanks for any help...
[Android General] jlb1959.01:
sorry forgot pic.
[Android General] githyanki:
Your pics don't show the battery loss from cellular draw, so can't tell if it is high.

It is normal for cellular to be on, but there are several apps that will switch it off for you if you like. I don't use them since I like receiving calls.
[Android General] jlb1959.01:
thanks,I was curious as I am on MM blisspop6.4, custom kernel(gamma)) and exposed with greenify,nothing else,didn't know if its exposed,kernel etc causing my only draw.I've gone the route of extreme battery saving,and wasn't worth chasing alarms etc,so when I see my only basicly my only draw is mobile I was wondering what would cause it...BBS( too late now since I've been using the phone), didn't show much draws at all,gsam showed the mobile,so it caused concern...
[Android General] cristixperia:
My stats using greenify & force doze.
[Android General] ProudRed:
Has anyone experimented with L Speed for doze over NapTime ? I am getting better aggressive doze with L Speed over Naptime. With Naptime Device gets out of Doze pretty frequently.
[Android General] WuNgUn:
I'm using FD as well.... No need to use Greenify with it. I pair it with Leandroid.
[Android General] DB126:
Impressive - especially given 5MB Google Play Store download during idle window! Do you consistently acheive similar results on this device?

Be curious to see a mid-charge dump (enable BBS Watchdog Processing and set range to screen off -> screen on) as some battery packs artifically hover at 100% for an extended period skewing low draw numbers. Regardless, appears you have a good handle on idle performance.

Didn't notice any wakelock blocking. If accurate serves as further evidence that superior idle performance does not require aggressive alarm/wakelock management.

As an aside, not a fan of using Force Doze and Greenify together as they are largely redundant for doze management (other features differ). Curious why you made this choice.
[Android General] cristixperia:
Yes, Idle drain is pretty low, event without amplify,but I can reach more than 5,5 hours SOT :(

Now I uninstaled greenify & force doze, I don't see a perceptibly difference, in my opinion most of these battery saver applications are just placebo and don't make a real battery improvement.:rolleyes:

How I can set watchdog service correctly?
[Android General] DB126:
- Watchdog setup looks fine (screen shot)

- make sure From/To References option is enabled under Custom Views

- perform idle run when battery is ~80% charged; set references before dump

Agreed on most "battery saving" apps (ugh) with exception to those that offer some refinement over native capabilities. For example, enabling 'Doze on the go' on Android 6.x (baked into Nougat). A light touch is often more beneficial with modern devices and ROMs. But folks love to turn knobs and dials ...

Although many will disagree SoT is a largely meaningless metric as it can not be reliably reproduced except in near labratory conditions. On most devices a 10-15% change in backlight level (actual lumes) will have a far greater impact on "SoT" than all of the other battery saving techniques combined.
[Android General] ProudRed:
Please have a look at my dump. Have lost 2% over 6 hours, Non Airplane Mode, but wifi/mobile data was off. My setup is Nougat and I am submitting the dump without greenifying system and play services for which I am loosing a lot of SOT than normal. Any improvement if I can work on ? Amplify not supported, but I can limit wakelocks and block alarms.
[Android General] DB126:
0.3% per hour average idle drain is a good outcome and about the best you'll get on Nougat. The ~5 min of non-doze time reflects normal housekeeping and did not trigger significant CPU activity or battery drain. No further action needed IMO.
[Android General] ProudRed:
For the doze interactive time I'll try with NapTime and see if its any less. And I saw gcm reconnect alarm, shall I let it be like that ?
[Android General] DB126:
Not a fan of limiting alarms/wakelocks so my response is predictable: leave it alone. There is little to gain by reducing doze interactive time as any savings (unlikely) will almost certainly be lost when the device wakes and 'catches up'.
[Android General] xXx:
my battery drain is totally fine but when I review battery usage on the time line I always have a usage peak at around 3am in the night. Does anybody know an app or special way to see which specific app or service is being active at this time frame?
[Android General] Oswald Boelcke:
Regarding your question: Negative. I'm sorry.

But for whatever reason, 0300 hrs seems to be a very specific time. In this thread, quite a lot of people reported unintended reboots at 0300 hrs i.e. something is really occuring at that time. My personal assumption: It's kernel and/or modem related, and I already took some kmsg logs but the reboot didn't occur on my device / setup.
[Android General] :
[MENTION=1030560]xXx[/MENTION]

WhatsApp is configured to take auto backups of messages (and upload to Google drive if account is linked) at 0300HRS everyday. :cyclops:
[Android General] Oswald Boelcke:
I don't use any application that doesn't respect my personal privacy requirements or is using servers in countries like the U.S.A., Russia, VR China etc.

But maybe that's the reason why I have neither reboots nor power drainage peaks at 0300 hrs. Thanks very much for this hint.:good: I'll remember it.
[Android General] jlb1959.01:
yes,I find 7.1 to be disappointing in regard to excess battery draw within the system,and for some reason using greenify doesn't help at all, in fact I wish I did a copy of my over night draw,greenify was the worst draw.I've gone back to MM( resurrection remix), with just greenify,I spent months after month chacing alarms,wakelock that made minimal difference..always appreciate your help mate.
[Android General] DB126:
My comment was not intended to be an indightment of Android 7 resource management. In contrast, I find Nougat to be equivalent to Marshmallow in power efficiently but only after latter has been tweaked to fix sensor issues that were ultimately addressed in Nougat.

What I do see is attempts to 'optimize' one aspect (eg: idle fall off) without considering the holistic impact on overall power utilization. Nougat sleeps efficiently on most devices using brief maintenance windows to perform routine housekeeping while consuming minimal power. Constraining those windows simply shifts the activity to immediatlely after the device wakes, sometimes introducing lag and further action to fix a self-inflicted problem.

BBS, GSAM and similar apps are powerful tools that expose details on how devices perform in various states. However, as with any tool understanding what is being presented and only acting on items that warrent attention remains a significant challenge.
[Android General] jlb1959.01:
don't get me wrong,I was not trying to take ur advise and swing it around make 7.1 better or worse than MM. was just pointing out that without playing with tools,kernels etc 7.1 is not a big improvement, if at all in battery life vs mm.
[Android General] DB126:
Na - understood your point. :)

For stock applications Nougat typically outperforms Marshmallow in screen-off drain due to doze refinements. SoT is overwhelming influenced by panel density and backlight intensity followed by app suite (including sensors) and, to a much lesser degree, kernel optimization/tuning. Not to mention user behaviors. Picking the right device and keeping the backlight in check are far more important than ROM selection for most Android users interested in maximizing battery life while preserving device functionality and usability. Enthusiasts will clearly take exception...that's the nature of XDA and similar communities. Nothing wrong with that recognizing device manufactures and Google engineers are not blithering idiots. Android 8 will offer additional refinements as the market swings to more budget friendly devices with limited on board resources. Enjoy the ride.
[Android General] xXx:
thanks for feedback. It might have been Whatsapp even I checked setting and it's set to weekly updates. But I disabled it now and check tonight again. I also checked other aoos like titanium, email etc. but couldn't find similar things configured. When I find it, I will let you know. Anyway, thanks for your help.
[Android General] DB126:
Could probably use a tool like OS Monitor along with logcat/dmsg analysis to identify the culprit. Involves a fair bit of effort until you get the hang of parsing logs. Simply disabling apps (trial & error) until you find the culprit is probably more efficient for the initial cut.
[Android General] xXx:
you are right. I also thought to just freeze suspected apps and see if it makes a difference.
[Android General] DB126:
Disabling and freezing are the same thing.
[Android General] xXx:
as promised here my feedback. Whatsapp was configured to create weekly backups happening around 3am but my issue was that I got battery drain peeks every day at that time. So the first thing I tried tonight is to disable the backup at all. You guess it already, the peeks are gone.

So it seems, even the schedule was set to weekly something happens even though on a daily base.
[Android General] :
Guys, WhatsApp takes auto backup of your messages to a local storage pathway named "Databases" within the WhatsApp folder everyday at 0300HRS. This is NON CONFIGURABLE. This happens so that when you decide to uninstall and reinstall WhatsApp, it is able to recover your messages the exact way you left them. Without the databases (.db) files, when you reinstall WhatsApp from playstore - you won't get your previous message history. You will start afresh.

Since most of us simply use TiBu, we become unaware of this mechanism because TiBu also backs up data of apps which becomes independent of this WhatsApp db mechanism. Also TiBu can be carried over between different devices.

The databases along with media files (if selected) that are backed up are uploaded to Google Drive on a interval that is CONFIGURABLE by us. That is the frequency we keep changing as to "daily", "weekly", "monthly" or none.

This is the reason why you [MENTION=1030560]xXx[/MENTION] did not see a change in activity even after changing online backup settings but saw the change immediately after disabling the whole app.
[Android General] supermedo:
Is there any solution to *alarm*, *launch*, CMWakelock Icing and AudioIn wakelocks on a LOS ROM on nougat? (no Xposed) They're the main reason my Oneplus3 can't sleep well (18% awake screen off)
[Android General] DEVILOPS 007:
https://xdaforums.com/nexus-6p/general/taking-wakeblock-requests-t3583397
[Android General] supermedo:
That app doesn't work on my device.
[Android General] DEVILOPS 007:
What device?
[Android General] supermedo:
Oneplus3 LOS ROM (ResurrectionRemix)
[Android General] :
The first two should not cause any drain, even if they show up in battery stats. If they do, it may be a bug. I have seen such a drain once in a buggy ROM.
[Android General] AlemanSantos:
I'm using Zenity RR, works there, also without blocking anything it has very good battery life, EAS ROM with Spectrum support
[Android General] DB126:
They are NOT the reason but rather symptoms of whatever is holding your device awake. Submit an idle dump for analysis.
[Android General] DEVILOPS 007:
Some people have it working on oneplus 3 roms. When I get some free time I'll make a build for you and you can test it if you want to.
[Android General] broke86:
Hi guys.

This thing is bugging me from a long time and I want to ask if any of you have this issue.

Basically I've always got a lot of wakeups from the calendar storage, and as you can see the system read the calendar an insane number of times (I'm on Sultan's LOS14.1 for the Oneplus One from 5 days, but it's the same thing with every ROM since Lollipop).

I just charged the phone, I'll attach a bbs log later!

edit: i disabled keep awake, run in background and start at boot (and calendar sync on the account settings) trying to minimize the issue. not very effective :(
[Android General] DB126:
While a bit unusual wakelock *requests* do not always equate to actual wakes or delays resuming doze. Need a BBS dump to assess true impact.
[Android General] githyanki:
As Davey said, will need a BBS dump to asses actual impact, if you use google calendar be sure to disable the calendar that comes with ROM. IE, if you have 2 calendars under apps in the settings menu, disable the one that doesn't say google.
[Android General] broke86:
here's a first dump.

I'm using business calendar 2 but the same thing happens with aosp calendar and google calendar.

I'll do another dump if you need it.

Thank you!
[Android General] peterlee928:
in order to give you proper feedback, the good folks are going to need you to do an idle log in accordance with the directions in the post below:

https://xdaforums.com/android/general/guide-extreme-battery-life-t3095884/post72734867

??
[Android General] broke86:
I'll do it asap! thank you!
[Android General] Oswald Boelcke:
You possibly achieve the best log by applying this procedure by @Davey126 who's THE expert.

And as far as I know all contributors at XDA nobody requires a "thank you" post - simply hit the thanks button in the bottom right corner of @peterlee928's post above yours.
[Android General] DB126:
Na - it's all an elaborate ruse. Simply leveraging the selfless contributions from so many talented members in this thread and others that enhance the body of knowledge that we all benefit from. If you have helped someone acheive better battery life by sharing a bit of experience give yourself a quick pat on the back.

tl;dr? See Clark's third law. Explains everything. :)
[Android General] Oswald Boelcke:
OT, I apologise. Please help me out.

tl = too long? dr = didn't read? Or does it mean something different?

What is "Clark's third law?
[Android General] peterlee928:
British science fiction writer Arthur Clarke.

Clarke's three laws, of which the third law is the best known and most widely cited:

When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong.

The only way of discovering the limits of the possible is to venture a little way past them into the impossible.

Any sufficiently advanced technology is indistinguishable from magic.
[Android General] DB126:
Yup!

[MENTION=6089972]peterlee928[/MENTION] covered that one nicely.

Crappy humor aside no one here is great. We are all ignorant about 99% of the world around us with small points of light distinguishing individuals. Magic is just seeing another's point of light for the first time. Actively seek them out. :)
[Android General] supermedo:
I don't know, the device is awake 20% of the time and drains +1%/h, the main kernel wakelock is powermanagerservice, and those ones are the main partial wakelocks.
[Android General] DB126:
You will need to submit an idle log for a more detailed analysis. The wakelocks mentioned in an earlier post are either benign (not drainers) or symptoms of a larger issue; wakelocks themselves are not the problem.
[Android General] broke86:
Ok this is funny: of course when I decide to take a proper log there is no issue with the calendar... :crying:

Anyway, I lost 8% overnight, is there something I can do to save some battery?
[Android General] githyanki:
Your location services kept the phone awake a lot.

com.google.android.gms.persistent (com.google.android.location.places.service.PlaceDetectionAsyncService)

Active since: 7 h 55 m 56 s

Last activity: 55 m 59 s

If you have things like trusted places to keep phone unlocked, or nearby activities in Maps on.

Go through settings to turn that stuff off, put GPS into device only and get another log.
[Android General] nhatlong1231:
Hey guys, I've used search bar i saw that *alarm* and *launch* don't drain battery. I just want to be confirmed again, because it wake too many times and i didn't face it in almost rom i used before
[Android General] DB126:
They don't - and nothing you can do about them anyhow without impacting device functionality. Submit an idle log (6+ hour duration with <1 min screen on time) to identify potential culprits. Keep in mind small amounts of wake time does not always equate to excess battery drain, especially on newer devices.
[Android General] adrxano:
Guys I jus wanna know what whatsapp alarms and wakelocks can I limit but still have messages pushed to me instantly cause I've noticed I have a very high amount of wakelocks from whatsapp..
[Android General] DB126:
Don't worry about wakocks (or wake time) unless demonstated to cause excess battery drain. Need an idle dump/log to determine that. In most cases the default config is fine unless you want to spend more time managing your device than using it.