yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] hypern0va:
I don't want to start a discussion in a thread which isn't appropriate for it but I want to say that this statement couldn't be more wrong. If that's the principle, we should also be glad to the constructors for every update they send to our phones, but that's not the case: when I pay for something I'm not buying just the product but also the support and updates (the ones which fix bugs in particular) that will come with it and if they became inexistent I have every right to complain about it.

Then maybe the Play Store payment for this app may be considered just like a donation since we also have the XDA version for free, and so what I previously said isn't valid in this case, but it is a general principle not referred in particular to this app.

BTW the current stable version does have problems, in my case it doesn't show any kernel wakelock and I've read about other people reporting it.
[BetterBatteryStats] TNSMANI:
In addition to what githyanki said, your mobile data is on and so when you curtail wifi, the background processes start using it, entailing more battery drain. If I were you, I would disable both data and wifi since I don't need them to be used while I/my phone sleep/s. If however you need the processes to run while sleeping, disable mobile data and enable wifi since wifi is the lesser evil.

Do you need automatic sync? I disable it and manually sync when needed.

The AOD also caused some drain. You also seem to have a lot of kernel wakelocks. Check whether you can use any alternate kernel that solves this issue.

Facebook, Viber, Samsung Cloud, lbe.parallel (whatever it is) also contributed by downloading via mobile data. Check these and other apps that you have and discard whatever you don't use and control what you need.
[BetterBatteryStats] jrbmed08:
Yes, I use ForceDoze. Tried disabling it and noted worse battery life, but I didn't have alarm data at that time. The really odd thing is that both BBS and GSam show my phone as dozing even though the wakelock graph is basically a solid bar. I'll try disabling ForceDoze again and looking at alarms at the end of the day.

In the meantime, I did an idle dump after last night, with my normal configuration (Bluetooth on and connected to my Pebble, ForceDoze on) and attached it here. I see the alarm data don't actually show up there though, so it's probably difficult to interpret. They do show up on the main screen of the app. Does that mean I need to enable the API in order to get them in the dump?
[BetterBatteryStats] chamonix:
How about checking post #2?
[BetterBatteryStats] TNSMANI:
You mainly have kernel wakelocks, especially related to wifi. Your wifi was on and running the whole time and it enabled Adguard to download about 4 MB and Antennapod to download about 3 MB. If I were you, I would disable wifi and mobile data during sleep. You can also try to assign a static IP for your phone and see whether things improve. You can also try an alternate kernel, if available.

Alarm stats are not recorded so try uninstalling and reinstalling BBS with a reboot in between. If still the Alarm stats don't populate, enable API in BBS's Settings.

Your sensors were also active especially Proximity sensor. Seems to be through Waveup. Control it.

Significant Motion Detector sensor was also active the whole time. On Android 8, it should not be. If you don't have any reasonable explanation for it, try a dirty/clean flash of your ROM.

Hope the above helps.
[BetterBatteryStats] jrbmed08:
Thanks! Couple of thoughts...

I'm not sure I want to disable data connections during sleep because I want to get notifications in the background during the day (and between data and wifi, wifi is probably the lesser of two evils). But a static IP should be a pretty harmless step to take. Unfortunately Sony makes it very hard to unlock the bootloader because they stop your camera from working if you do. Because of that, there hasn't been too much development; alternate kernels and ROMs aren't available for this phone.

I updated the app and now alarm stats seem to be populating without the API (just did a test dump to see). So hopefully that won't be a problem again.

Waveup uses the proximity sensor to wake the phone, so it's behaving exactly how it's supposed to. I use it because my phone lacks ambient display or double-tap/wave to wake. I turned the phone upside-down so it wouldn't accidentally get triggered, but maybe it's still happening despite that. I could always disable it for diagnostic reasons but I'd rather not go without it, because it's incredibly convenient.

I wonder if the significant motion detector sensor was due to ForceDoze? It's supposed to disable motion detection during doze, but maybe it's not working right. I've already done 4 clean flashes in the 2 months that I've owned the phone, so I'm not sure that will help, but at least a dirty flash won't hurt.

I think I'll do another idle dump with ForceDoze and Waveup disabled to see if they're the cause of the sensor issues, and with a static IP. Thanks again for the help; it's much appreciated!
[BetterBatteryStats] chamonix:
2.3-197 is up on gplay. This is the same as 193 from HockeyApp, I just need to stop incrementing build numbers to avoid confusion.
[BetterBatteryStats] Nekromantik:
Running latest from hookey and on pixel 2 XL all of a sudden I get no stats. No error messages or details. Attached screenshot.
[BetterBatteryStats] TNSMANI:
Regarding switching off wifi and data and still get notifications during day time, you can use LeanDroid from Play Store which has the option (among others) to switch off wifi and/or data during particular periods (like nights) and still have them running at other times.
[BetterBatteryStats] bobby janow:
Why not just turn the phone off? You're basically doing the same thing. I'm not sure why you would do either. Isn't there a plug around?
[BetterBatteryStats] rootlinux:
This is what I use. Days of charge with everything on.

https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/282689723888
[BetterBatteryStats] TNSMANI:
It depends on what you need. I don't need any notifications during night when I/my phone sleep/s. But I do want the phone itself to work for SMS and calls, in case someone wants to urgently contact me. So turning off the phone is not an option.
[BetterBatteryStats] RASTAVIPER:
Any idea if I should get worried because of getting 12hours of "Significant motion Detector" as part of Google services, in total use of 20 hours?

Unleashed by my rooted OP3T in 8.0
[BetterBatteryStats] bobby janow:
Oh I see. I was thinking you were going into airplane mode but you're just turning off data and not network connections. It still seems like overkill, however. I mean how long would it take to top off the device in the morning? 10 min, 5? I like to pay attention to idle drain overnight to see if anything is run amok. Plug it in during my morning coffee and I'm good to go.
[BetterBatteryStats] 93fuelslut:
Hey I bought the app yesterday and know to post logs of my usage. But before I do that, I just wanna know if this usage is even normal. My cell network and wifi just seem high for just sitting on the table
[BetterBatteryStats] jrbmed08:
[MENTION=5656100]tnsmani[/MENTION] - thanks for the help so far. I usually charge my phone overnight, so that's not a major problem. But I bet I could set up a Tasker profile to turn on Data Saver and turn off Wifi overnight if I don't want to charge it, or look into LeanDroid.

Here's another dump after implementing some of your suggestions. I've done the following:

-Switched location from Device Only to Battery Saving

-Set up a static IP for home networks

-Disabled WaveUp for diagnostic purposes

-Disabled ForceDoze for the same

-Dirty flashed my firmware

I can still see there are a lot of wakeups and alarms. The alarm snoozehelper.EVALUATE is still all over the place, and Google Play Services is still keeping my significant motion sensor active all night. I'm at a loss for why; if you know of any reason why an app might be doing this or how to improve it, I'm all ears. I think I'll start by clearing cache/data from Google Play services.

Otherwise the idle drain seems acceptable considering I have Bluetooth connected and location on, but I'd still like to figure out why those 2 issues (snoozehelper and significant motion) persist.

Edit: Oops, forgot to attach the dump file.
[BetterBatteryStats] jrbmed08:
I have the same issue if I reboot. No stats at all show up unless I plug in and unplug (and then it creates a new set of stats at the unplugged reference). Luckily that means unplugged to current still works for me. Everything worked fine prior to yesterday's update.

Unrooted Sony Xperia XZ1 compact on 8.0.

Edit: I do get "fallback to since boot" and the "selected from/to references could not be loaded" error, but nothing loads after a refresh.
[BetterBatteryStats] Nekromantik:
Its annoying.

Hope they fix in new stable release.

Had to install GSAM for the time being as BBS is not 100% usable at the moment.
[BetterBatteryStats] chamonix:
Happy new year to all of you!
[BetterBatteryStats] Nekromantik:
happy new year all!
[BetterBatteryStats] yochananmarqos:
That graph tells us nothing.

By the way, that graph does not show cell or Wi-Fi network usage. It shows cell network quality and if Wi-Fi was on, nothing more.
[BetterBatteryStats] 93fuelslut:
Thanks, I had no idea it was about quality. Now it's odd that there is a gap.
[BetterBatteryStats] TNSMANI:
*net_scheduler* (com.google.android.apps.wallpaper.Wallpapers): 4 m 2 s Count:7 0.7% - one of the drainers.

Some more:

[timerfd] (*api*): 13 m 46 s Cnt:(c/wc/ec)25063/0/0 2.5%

alarmtimer (*api*): 12 m 30 s Cnt:(c/wc/ec)376/0/0 2.3%

NETLINK (*api*): 12 m 3 s Cnt:(c/wc/ec)107561/0/0 2.2%

Apart from the above, System, Play Services, wearable, BT etc also contributed.

SnoozeHelper may be related to alarm, see whether you can disable it. AppWidget Update was another which fired too many times.

Since Location was on, some of the alarms are inevitable.

Alarms: 88, Intent: com.sonymobile.smartcharger.chargingintelligentservice.START_LOGGING

I don't know why you are getting this while the phone is not charging unless something is stuck. I don't remember to have seen this in the earlier dump. Clean Dalvic and cache and restart.

Once again Adguard and Antennapod caused downloads of 3 MB and 1 MB respectively.

Significant Motion Detector was on for only about 16 minutes which is a huge improvement from last time when it was on for the entire time.

Having said all that, on Oreo or for that matter on Nougat, you can't get less than 0.4 or 0.5% drain per hour unless you shut down your phone. So given that Location was on and Pebble was connected, I would say that this drain is acceptable (as you yourself have realised).
[BetterBatteryStats] poincare:
Hello, I didn't see a clear answer to this through back posts or on OP, but new year and a new Android phone to install this app on. I understand there is an xda edition vs Google Store one. Im not sure where the download link for xda edition is but.... Is the release candidate test app from the HockeyApp the same as the xda edition?
[BetterBatteryStats] Sami Jildeh:
No, XDA is 2.2
[BetterBatteryStats] yochananmarqos:
Everything you asked about are in the the first couple posts of the thread.
[BetterBatteryStats] jrbmed08:
Got it! Since most of what's left is kernel-related, this is probably the best I can do without turning off location, BT, and radios, unless I decide I want to do that overnight rather than charge nightly.

That Sony charger alarm is weird. Thanks for pointing it out; I'll see what I can figure out about it. I can't seem to figure out how to clear cache/Dalvik in oreo...maybe by restarting in Safe Mode and then back to regular?

Adguard is a VPN so it's showing all the network traffic from all apps except Antennapod, which I've whitelisted since it's an ad-free app. I was too lazy to whitelist the rest of my ad-free apps. If I turn that off, it would theoretically show which app is actually downloading 3 MB overnight, but that doesn't seem too bad either way.

How can you tell that the significant motion detector was only on for 16 min? This is what I see under sensors/Google Play Services:

Sensor: Significant Motion Detector(24), wakeup=true, Time: 8 h 53 m 26 s

Thanks again!
[BetterBatteryStats] kirkalldritt:
For some reason on my Note 3 this crashes a few of the apps (SlimRom)

Kirk Alldritt
[BetterBatteryStats] SteveYoungs:
Post #2. And yes, HockeyApp version is xda edition.
[BetterBatteryStats] TNSMANI:
Sorry, I stand corrected on Significant Motion Detector. I saw three lines below where you got that and failed to see the elephant in the room. May be I need a change of glasses:eek:
[BetterBatteryStats] RASTAVIPER:
So what is the outcome regarding this Detector?

I have a similar concern at post 33479.

Unleashed by my rooted OP3T in 8.0
[BetterBatteryStats] Rinoceros:
But only Hockey edition is now getting updates.

On Hockey, you will find 2.3-193

Little bit odd, you need a Microsoft account for Hockey, where Android is for Google.

And why on earth, do need Hockey app access to my email?
[BetterBatteryStats] ralfbergs:
No, you don't. A GitHub account is also sufficient, or Facebook, Google, Twitter.

It doesn't. It just needs your email ADDRESS. They need a means to identify you.
[BetterBatteryStats] DB126:
Wow - faux drama! Email access? Microsoft account requirement?? Whew, sounds bad. Almost hashtag worthy. :confused:
[BetterBatteryStats] Bajanman:
Stated right on the first page of the Op...

Release candidates on the hockey app only! And if you don't want to latest (test) version then wait for it to show up here if you feel using your email is bad. I find it a little odd Microsoft was the only thing you noticed. Added a pic below to show everything you can sign up with!

I'm sure most here have 2-3 email accounts for different things, use one of those instead of your main account for testing purposes.

Exactly that.

Maybe go look at the hockey app/site and then you'll see it's not only Microsoft. Please don't feed the need and check on the subject matter thanks.
[BetterBatteryStats] Bajanman:
XDA Labs double post.
[BetterBatteryStats] DB126:
Hum - not sure who this was directed at but given I was quoted will simply reinforce the need for fact checking before posting FUD which was the mutual point [note to self: skip the sarcasm].
[BetterBatteryStats] Lughnasadh:
I understood the sarcasm. Pretty evident... :good::)
[BetterBatteryStats] DeeZee3000:
I am unable to grant this particular permission.

The response from ADB is that the app did not request the permission.

But the app seems to work without it. Is it still required?

(I did try to search for the answer, but had no luck)
[BetterBatteryStats] chamonix:
It seems that there are yet again dependencies between Google libs and permissions even Google does not understand. Anyhow it seems that on pre 8.1 (or 8.0) that permission was not needed.

It would be great if you could report what version you are on so that I can complete the doc once we have found the first version where that perm is required.
[BetterBatteryStats] jrbmed08:
I was unable to find any kind of solution for this. Same with the snoozehelper alarm, which is still running wild whenever my device is idle. Both issues have persisted across firmware installs and factory resets, so I really have no idea.
[BetterBatteryStats] DeeZee3000:
Of course, I forgot about that. I'm on 7.0
[BetterBatteryStats] -iHackerz-:
Recently I've been having problems with my battery life so I turned to BBS to try to pinpoint the problem. Now I'm not sure if it's just my old battery or if there really is something that's draining it, but I made a log if anyone can help me :confused:. I hope I did it right as I've never really done one before, left it for around 6hrs during night with >1 min of screen on time.

It all seems normal to me, lost around 2% overnight, but as soon as the screen's on, it starts dropping like crazy, barely makes it to the end of the day with light use (Wasn't like that before).

I have location on high accuracy and wifi's always on.

Also, used latest test BBS and I see kernel wakelocks are not visible in the log and in the app, why so?
[BetterBatteryStats] chamonix:
Can anyone confirm that the perm starts from 8.0?
[BetterBatteryStats] RASTAVIPER:
What do u mean?

Unleashed by my rooted OP3T in 8.0
[BetterBatteryStats] githyanki:
https://xdaforums.com/showpost.php?p=75052269&postcount=33506

Only applies to unrooted devices.
[BetterBatteryStats] jrbmed08:
I found out why I was having so many snoozehelper.EVALUATE alarms. It was caused by the "hide running in the background notification" app. Uninstalling the app brought my alarms and awake time into the manageable range. PSA for anyone on 8.0 who uses that app!
[BetterBatteryStats] TNSMANI:
Classic example of remedy worse than the disease.
[BetterBatteryStats] DB126:
The disease in this case was actually an indicator of the real illness that recipient opted to hide vs. address head on. Akin to removing the 'check engine' light bulb when it pops on. Problem solved! Err...no.
[BetterBatteryStats] jrbmed08:
I don't think it's quite fair to say that. XDA itself recommended that particular app as one of 3 ways to stop that annoying persistent notification:

https://www.xda-developers.com/hide-app-running-background-notification-android-oreo/

The apps I keep running in the background, e.g. Pebble, won't work without continuing to run in the background. So I'm aware that they are running. I keep it that way intentionally and don't want the notification to continue taking up space on my screen. Furthermore those apps have their own persistent notifications; I don't need another. The option to turn it off is greyed out in 8.0, but apparently in 8.1 that has been fixed (http://www.androidpolice.com/2017/1...kground-notification-without-third-party-app/). I've restricted background activity and background data on plenty of other apps, so it's more akin to a check engine light that keeps turning on even though I've already checked the engine. Sure, the remedy was worse in this case, but the notification itself is the disease.

Anyway, I'm now testing out the recommended method described on that page (joao's AutoNotification), and it doesn't seem to cause the same alarm.
[BetterBatteryStats] DB126:
Fair enough. You have obviously done your homework, know what is happening behind the curtain on your device and are agreeable to those activities. So yeah, in that case temporarily suppressing the notification makes sense until a better solution becomes available.

As an aside, one of our personal vehicles is rocking 325K miles and is in relatively good shape. As might be expected the 'check engine' light pops on with increasing frequency as various engine/emission management components age and need attention. Once I understand the problem and have parts on order I will artifically 'clear' the error to turn off the light - even though the fault technically still exists. However, it that case the light will still illuminate if a different error occurs. Suppressing the android notification is an all or nothing choice.

The point is I fully understand your knowledgeable/informed actions - been there, done that. :)
[BetterBatteryStats] jrbmed08:
Would be nice if there were a per-app way to clear the notification, so I could tell it to shut up about Pebble running in the background while still letting it monitor rogue apps that might be popping up. That would be more like your car example. ;)

Edit: Actually now that I think about it, the app that was killing my battery life can actually select which apps to block from the notification...but that doesn't help me.
[BetterBatteryStats] alireza_simkesh:
Hi everyone,

I am getting massive wakeup alarms by the name of job.delay and job.deadline.

I tried searching this thread for an answer on how to reduce wakeups caused by job.delay and job.deadline, but I couldn't find an answer.

Does anyone know how I can reduce those? Do they have anything to do with Google backup?
[BetterBatteryStats] adm1jtg:
Anyone else have this happen?
[BetterBatteryStats] kingbri:
How can someone obtain a dump file? I want to post it here
[BetterBatteryStats] Lughnasadh:
Its outlined in the OP.
[BetterBatteryStats] BillGoss:
Thanks for this. I was getting one hour of Awake (Screen Off) overnight. After removing the app I'm back to 4 minutes and my overnight battery drain has dropped from 0.7%/hr back to 0.3%/hr.

I too, like you, am now trying out AutoNotification (the second option in the XDA article).

Update: with AutoNotification the overnight drain was 0.4%/hr and Awake (Screen Off) was only 6 minutes - excellent!
[BetterBatteryStats] chamonix:
New build is up, fixing an ANR
[BetterBatteryStats] alireza_simkesh:
Anyone had any experience with Job.delay and Job.deadline?
[BetterBatteryStats] RASTAVIPER:
I have been also asking about this months ago.

Do you have an Oneplus like me?

There is no solution as far as I know.

Unleashed by my rooted OP3T in 8.0
[BetterBatteryStats] borisboing:
Could anyone give me some advice re the attached dump - charged to 100%, allowed to drop to 96% then left alone until I heard the notification that battery was at 15%--which was a little under 18 hours.

During that time it managed a whole:

Deep Sleep (): 23 s 0.0%

The offender being:

NETLINK (): 7 h 45 m Cnt:(c/wc/ec)908543/897713/0 44.3%

I can't seem to find anything online about what that is; I've uninstalled most things, wifi on and off, I've tried in aeroplane mode, I have it set to 2G and have a good signal but have also tried 3g & LTE with the same results (see attached screenshot for the period that the dump file is from: 2G voice, data disabled, wifi on).

This is the only device I have that has this problem (all running Lineage/CM)--I get standby time of weeks from everything else so advice would be greatly welcomed.
[BetterBatteryStats] TNSMANI:
Except for wifi, Android System and Netlink (may be protonmail also), others seem to be under control. No reasons jump out for the drain and for keeping the phone at higher frequencies.

Try the following: A different kernel, if available. A clean flash of the ROM. Wifi setting to never keep on while asleep. And then report with a fresh dump.

You can also wait for somebody more knowledgeable than me to comment.

EDIT: Also try without Xposed.
[BetterBatteryStats] DB126:
Responding as I own this device (XT1607 variant); bootloader unlocked rocking...wait for it...stock kernel and MM based ROM. Average drain 0.2-0.5% per hour with all radios powered up, location services set to 'high accuracy' and push mail (AquaMail) handling dozens of messages in the background during doze maintenance windows. Not to mention the usual array of real-time notifications and Moto live display illuminations. Xposed framework v89 active with Greenify being the only 'power saving' module in play. Left untouched device will end the day with 90+% remaining on the battery. Hardware is willing and capable of idling very efficiently.

[MENTION=5656100]tnsmani[/MENTION]'s analysis is spot on. I believe LOS 14.1 for G4P bundles a custom kernel. Might consider returning to stock or going with one of the two stand-alone options. Clearly your device never/rarely enters deep sleep which suggests a kernel problem.

Oh yeah, do yourself a huge favor and dump Amplify. Mucking with wakelocks and alarms is a fool's errand for 95% of the use cases that have come across my short desk. There is a small community of advocates that tilt at windmills; the mental satisfaction brought on by a stiff placebo and rose colored glasses is intoxicating. There are rare scenarios where highly targeted WL and Alarm control is warranted, mainly on pre-Android 6.x based ROMs. A crappy app can also wreak havoc. That's what the uninstall button is for.