yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] fossils-n-dents:
The option to salect 'Last Boot to Current' is available, but to simplify things, the option of 'Unplugged to Current' is best for all who may interpret a dump file. 'Unplugged to Current' gives the appearance of a device that is already running when you put it down at the end of the day, as when people do before they sleep, work, ect. Very few reboot their device before going to bed. While understanding from a developer standpoint to view 'Boot to Current', we don't need to do that here.

Turn off Location until you need it, or at least when your device is resting. Disable Maps until you need it. Turn off 'Auto updates in Google Play Store. Instagram and Facebook are grinding you into the ground, check their notification/ update settings. Get FB Lite, check your Sync settings to make sure there are no errors. If that fails, reset your app preferences, Apps> Three buttons on the top right> Reset App Preferences>. (I'm just throwing out things you can try, in no specific order)

'qpnp_fg_memaccess', 'qpnp_fg_update_sram', and 'qpnp_fg_update_temp' The combination of Android, GSAM and BBS may be polling your battery too much...Try using only one (BBS or GSAM) and test it out. 'fg' = Fuel Guage.

Get Greenify, use 'Shallow Doze' first, then try 'Aggressive Doze' and see which setting is better.

Stop uneccasary Google Play Services reporting, use this: https://xdaforums.com/showpost.php?p=73693320&postcount=32709

*Always make a backup before disabling services.

Afterwards, reboot to Recovery...Wipe Davlik and Cache...reboot. Let's see your updated log at your first convenience.:good:

Android is a system of compromise. You cannot do whatever you want with everything enabled and get away with it for long.

But, the best part about Android is we can root, and fix it ourselves. Learning your devices' behavior is the first step.

The specific problem in *job.delay* and *job.deadline* is apps that have to use data, keep the mobile radio active for too long. As in an action cannot be performed within a specific period, gets 'Delayed', then meets it's 'Deadline' to perform said action...and repeats the request over and over. Doze mode, a rouge app, or poor progrmmer coding could be the cause. Usually it's an app.

You can try SafeMode to see if the problem persists. If relief is found...It's an app. You can also check your Sync settings to make sure there are no sync errors with any apps, clear cache in Google Play Services, and just to double-check reboot to recovery, and clear Davlik/ Art Cache and Cache (5 times each). As your device does enter, and remain in Doze, it probably is an app gone mad.

Kernel wakelocks are very much needed in the analysis.

I was having problems with the current BBS (Both XDA and paid version), I downgraded to version 2.2.0.0 and have had no problems since. Worth a try.

The link isn't working (Please see photo below).
[BetterBatteryStats] fossils-n-dents:
Not really. every device will have them. With your device it's not a problem.
[BetterBatteryStats] wolframio0:
Thank you very much!!! :victory:
[BetterBatteryStats] uzadragos:
Thank you for your answer :D.

My location is always turned off, i don't use it. I disabled Maps but i dont think thats the problem. A week ago i did a clean install of this rom and i did not install anything....no social media apps, i've uninstalled most of the apps from google and i did the thing with the google play services. I've also used Naptime with aggressive doze but this thing does not want to sleep....I did the same with with the stock rom from LG, so it's not rom related.

Is it possible that i need to change my battery? I have the phone since 1,5 years ago, maybe the battery itself has some problems.
[BetterBatteryStats] fossils-n-dents:
Or...your battery could be malfunctioning. It's always my very last move when all is exhausted with fuel guage wakelocks. You could try a battery health app first, or simply purchase a battery. Hopefully, that will solve the issue.

On a small note, Google Maps is very well alive in your log:

com.google.android.apps.maps (com.google.android.apps.maps.Maps): Uid: 10077 Sys: 2 m 48 s Us: 54 s Starts: 1

Thanks for your patience.:good:
[BetterBatteryStats] uzadragos:
I will do again everything you said in the previous post and i'll wait a few days to see what's going on. If nothing changes i'll just buy a new battery.

Thanks again :good: !
[BetterBatteryStats] DB126:
Alternative -> https://xdaforums.com/showthread.php?t=1179809&p=72467976

Rational -> https://xdaforums.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588/post74191966
[BetterBatteryStats] iruleshtar:
The link should work now sir..

Or here the dirrect files.. Thank you :)
[BetterBatteryStats] fossils-n-dents:
Yes, the hunt for the mythical 0. 0% /h unicorn is always afoot. Just make backups in case things go badly.

Your 'Screen on' time in the 'Other' section of your log must be less than one minute. This alters the stats of a device being idle.

===========

Other Usage

===========

Deep Sleep (): 4 h 11 m 22 s 89.1%

Awake (Screen Off) (): 28 m 9 s 10.0%

-------------------------------------------------Screen On (): 2 m 37 s 0.9%-----------------------------------------------

Doze Interactive Time (): 2 m 35 s 0.9%

Sync (): 3 s 0.0%

Screen dark (): 2 m 37 s 0.9%

You must let the device idle for a minimum of 6 hours (Do not use the device during this time).

Clear data and cache in Better Battery Stats, take another idle run, and post your dump file.

Sorry for your inconvenience.
[BetterBatteryStats] iruleshtar:
Oh my god.. I guess im late taking the Log right?

Okey I will try it again :) thank you.
[BetterBatteryStats] fossils-n-dents:
You can post your log whenever you're ready, just make sure to follow my instructions so your time is not wasted.:good:
[BetterBatteryStats] topbasework:
[MENTION=7344957]fossils[/MENTION]-n-dent

Can u take a look my dumb file

Anything need to be improved

http://cloud.tapatalk.com/s/59e6b2faa36da/BetterBatteryStats-2017-10-18_082628572.txt
[BetterBatteryStats] nomad47:
Hi,

I am using better battery stats on my OP5. However only stats available are since boot. The options for last unplugged etc are not there. And whenever I open the app it shows "Fallback to since boot". Can anyone clarify how to get since last unplugged in the app.

Edit: figured out the problem. Need to connect disconnect charger once for the stats to be there.

Noob me
[BetterBatteryStats] murti52:
Kernel wakelock shows "no stats have been collected" any solution to it..?

Device OnePlus One 7.1.2

SuperSu installed and given root permission

Installed BBS as system app

Reboot several times

Still no luck.

Thanks
[BetterBatteryStats] PackElend:
so making a long story short :), these settings determine the extend of the dump files. They set the start and end (in the sense of time) of the dump files.

That is quite interesting, that should be posted somewhere in the beginning of the thread.

besides, thank for you great support
[BetterBatteryStats] patrickdrd:
2.2.0 says no stats have been collected yet, both in summary and in kernel, almost an hour has passed since install, so my hopes are limited, at least with 2.2.2 I was able to view summary, with 2.2.0 I lost that too (besides kernel) :(

anyway, I have a suspicion that my battery needs replacing as well, such a shame that there isn't a way to detect that, a friend of mine suggested that I should discharge it and plug it to an external charger using a cable to connect to and view the capacity from empty to full, but it feels a bit troublesome I should say, is there any other way?

also, what's your opinion (and others) about adguard?

I installed it lately, my (old) phone was lagging and decided to switch to "browsers only" mode, they claim that they don't soak battery, what do you think?

edit: ok, I found your opinion "uninstall it" - classic :D

furthermore, regarding that "famous" post, where's the reference to adactivity you said that you would add?
[BetterBatteryStats] pokipokipxorn:
What about microG?

Here are the list of running services & broadcast:

SERVICES

microG DroidGuard Helper

RemoteDroidGuardService

microG Services Core

AdvertisingIdService

AnalyticsService

CarService

CheckinService

ClearcutLoggerService

DriveApiService

DroidGuardService

DummyService

FeedbackService

FirebaseAuthService

GService

GamesStubService

GeoDataService

GeocodeServiceV1

GetToken

GoogleHttpService

GoogleLocationManagerService

GoogleLoginService

IndexService

LightweightIndexService

LocationServiceV1

LocationServiceV2

McsService

NetworkQualityService

PaymentService

PeopleService

PlaceDetectionService

PlayLogService

PushRegisterService

RemindersService

ReportingAndroidService

SafetyNetClientService

SettingInjectorService

SignInService

WearableLocationService

WearableService

microG Services Framework

PushRegisterProxy

BROADCAST

microG Services Core

PackageReceiver

SendReceiver

TriggerReceiver

TriggerReceiver

UnregisterReceiver

Thank you in advance.
[BetterBatteryStats] patrickdrd:
I don't think anyone can get a worst wakelock graph than this one:

I will not rest till I find the [MENTION=7982030]ssho[/MENTION]le that's keeping my phone awake!!!

should I begin unistalling (trial and error)?

edit: 1st step: adguard (culprit) uninstall :cool:

edit2: I don't think so,

anyway, I have the same configuration/installations on my other phone,

where BBS works fine, so can somebody tell me how to generate (and save) this idle log?

edit3:

the thing is that besides the graph (and history),

I don't see anything strange in alarms, partial wakelocks and even phone's battery stats:

the phone with around 10 minutes of screen time (I've got mobile data on though all the time)

is losing 4% of juice per hour!

could it be a faulty battery draining fast or something else?

and if it's something else, why isn't it detected in BBS?
[BetterBatteryStats] brokich:
Thanks for your response! I am using Battery Stats to check this regularly, and *net_scheduler* seems to move between apps very often. After updating to AQI7 on my S8, GPS started going super high in drain stats. It is sitting at second place today, while I've had it sit down at the bottom with 1-2-3% usage daily for two months now. It's really a sad day if this marks the time when I will have this problem again with the new phone, after having it on my previous ones.

Today, net_scheduler was listed as coming from Google Services. I do have BK Disabler, but as I am not rooted - it will not allow me to stop services from it, and I also do not see the ones you listed (in a list of 360+ services inside GPS). I don't think I will be rooting soon either.

Tried wiping app cache (dalvik too), re-installing GPS updates, installing the BETA GPS update, and re-logging from my accounts. The drained seemed to continue. Now I am charging and will continue to observe the device in the next few hours and maybe tomorrow as well.

I'm afraid I might have to factory reset, which is such an unfortunate solution. Android battery drain continues to be a complete screw-up. :/
[BetterBatteryStats] Pandawg:
Just downloaded the app after a while of not using it. I installed it because I left my device unplugged overnight, and the Android OS kept my device awake for 7 hours. I was hoping the app can help me find what might be keeping my device awake. I just post the dump file here right, and someone might be able to help me?

Also I have a Note8, and it is recognizing the app as a game lol.
[BetterBatteryStats] fossils-n-dents:
To have your dump file read:

Set Better Battery Stats to 'Unplugged and 'Current'.

Device must be left to idle for 6 or more hours. (Do not use the device during this time)

Submit your dump file, and someone may be able to help you.
[BetterBatteryStats] topbasework:
Can someone take alook my dump file bbs.right now only using MyAndroid Tool pro to disable service
[BetterBatteryStats] RASTAVIPER:
BBS lately is freezing and lagging all the time and I suspect that maybe Amplify could create this problem.

Is there any wakelock/alarm connected to BBS that maybe I limited though Amplify?

Unleashed by ONEPLUS 3T rooted
[BetterBatteryStats] Pandawg:
Hope someone can help me. Left the device idle for about 7 hours.
[BetterBatteryStats] Oswald Boelcke:
Are you convinced that Xposed on Nougat isn't the culprit for the freezes and lags?
[BetterBatteryStats] fossils-n-dents:
You're doing great! Once your device sleeps below 0. 5% /h, there really is no cause for alarm. If you wish to make a small gain, disable Bluetooth whiile your device is sleeping.

Amplify possibly is the source of your problem. You may have indirectly limited BBS through it's use, if you have not specifically limited BBS itself.

Hopefully, you have created a backup of your setup before using Amplify. If not, I would suggest disabling Amplify, and starting over...carefully. But make a backup before re-starting Amplify.

'Screen On' time in your dump file must be under one minute. (No using/ touching the device for 6 hours).

Photo #1 below is your device.

Photo #2 is the correct way.

If you use your device, it is no longer idle, and your stats are no longer valid.
[BetterBatteryStats] Oswald Boelcke:
Just for your information but you certainly know. Simply like to share own experiences: A lot of issues might be Xposed driven. I'm sure everybody is very familar with the extremely deep impacts of Xposed to your system.

As an recent example I experienced crashes of applications (for me mainly Nova Launcher) while running RR-N-v5.8.5 with Xposed but I was able to drag it down that Xposed eventually was throttling my engine up into afterburner (or for our British friends "reheat"), CPU always on max, and the device heating up to allow frying of eggs. There wasn't any resources left for other applications to function.

Despite having been pretty happy with RR-N, I reverted to RR-M yesterday also for above mentioned reason; however, primary reason was M66B doubts that his XPrivacy is able to ensure privacy on Nougat, and he as the dev will know. By my own observations, I share these doubts - and recognised for my device that none of the available Xposed frameworks is currently yet far enough developed.

EDIT: @Paragon X: How about to hit @fossils-n-dents's thanks button instead of an additional post?
[BetterBatteryStats] topbasework:
You're doing great! Once your device sleeps below 0. 5% /h, there really is no cause for alarm. If you wish to make a small gain, disable Bluetooth whiile your device is sleeping.

Thanks for yr promp rply
[BetterBatteryStats] fossils-n-dents:
Well said, as is why I have not stepped up to a Nougat Xposed/ Xprivacy solution myself. I will wait for it to mature. (Hopefully)

Amplify, while awesome can, and sometimes will bring your system to a screeching halt if one is not careful, which will lead to troubleshhooting headaches for those who use Amplify, but don't understand what Amplify actually is, and what it does.

That you pinpointed the problem, and made the necassary adjustments is a testament to your technical prowess. Cheers [MENTION=7408621]noc.jfcbs[/MENTION]!!!:good:
[BetterBatteryStats] DB126:
FWIW I do believe this is device specific if referring to the framework itself vs the behavior of specific modules. On a personal note I have yet to experience an "official" (rovo89 built) framework issue on a half dozen+ different devices running near AOSP ROMs representing Android 4.4 to 7.1. But my application soup kitchen looks a lot different than yours - in addition to HW/kernel/ROM variations.

(Greetings to all; just a brief visit before returning to hibernation)
[BetterBatteryStats] Fif_:
Problem: Screen off and on references are seldomly created.

I'm running BBS 2.2.0 on a OnePlus 5, OOS 4.5.13 (7.1.1 Nougat) and Magisk 14.3.

BBS is installed as a user app and has root access. Watchdog is on, and I have "Watchdog on Unlock" on as well.

Most of the times BBS will fail to create a screen on or screen off reference. I have attached two screenshots taken seconds apart. On one you can see that the the unplugged reference was created 6h ago. Yet the screen off reference is close to 16h ago. The screen was turned off and on many times since the phone was unplugged, but BBS has missed all the screen on and off events.
[BetterBatteryStats] parser:
I rebooted once after I woke up but all alarms are from last night's 4-5 hour idle .

I know how to stop play services alarms but I don't know how to stop *job.delay* alarm and what causing it.
[BetterBatteryStats] DB126:
Food for thought:

https://xdaforums.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588/post74264522

https://xdaforums.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588/post74220260
[BetterBatteryStats] fossils-n-dents:
1. Set BBS to 'Unplugged to Current'.

2. Charge your device up to 95%

3. Unplug your device.

4 . Idle time must be at least 6 hours. During this time do not use the device at all.

5 . Re-post your dump file.
[BetterBatteryStats] Allfor12:
I realize that this says 3:26 minutes of screen on, but right below that it says 3:26 of screen dark. I didn't use it for anything in the night between 100% and 64% when i woke up.
[BetterBatteryStats] pjadec:
Probably these:

AudioMix (1041): 5 h 44 m 18 s Count:1 73.5% audio loop "?". Is V4A installed or something?.

NlpWakeLock (Google Play services): 1 h 53 m 14 s Count:558 24.2% Location?.

Try wipe caches in recovery.

Probably try clean flash.

My phone use in same time about 0,2-0,5%.
[BetterBatteryStats] Allfor12:
The ROM has V4A as a default and I've always left location, WiFi, and BT on overnight and until a week ago been under 1%/hour.

Can you tell from my other two logs last week what is still causing my drain?

Thanks, I'm probably going to try a clean flash this afternoon, but would love to know what's causing it.
[BetterBatteryStats] fossils-n-dents:
That 'Screen On' time is problematic.

Have you tried taking a log while in Safe Mode?
[BetterBatteryStats] X46X:
Hi guys, is there something which I can improve? Thank you
[BetterBatteryStats] fossils-n-dents:
I have written an email to BBS developer Sven Knispel concerning some non-rooted members missing statistics, he was very responsive to help us with a possible solution.

My initial message:

"If I may trouble you...I have a fellow members who use BBS but are non-rooted. I have every indication the proper ADB command(s) are being followed, yet they still have problems with entire dump file not displaying Other Usage, Kernel Wakelocks, and 'Alarms' stats on multiple occaisions."

In order for the dev to see what the issue(s) are behind the lack of statistics, a 'Logcat' will be required. From 'Boot to Current' should suffice with the same 6+ hour idle time frame.

You can post your logcats here, and I will forward them to Sven. Only proper logcats will be forwarded.
[BetterBatteryStats] rjm831:
Thank you both! I have been trying for 2 years. Will post soon.
[BetterBatteryStats] fossils-n-dents:
I would venture to say with the amount of apps you have, and all your devices' features enabled (Sync, Location, Bluetooth), plus Google Play Services own processes, your device is behaving right in line with normal behavior as evident by your configuration.

*job delay* and *job deadline* are but a hint that an app(s) is holding an open data connection until it is allowed to complete it's data 'Job', and has missed it's 'Deadline' multiple times. It will continue until A: The 'Job' is complete, or B: You find the app(s) firing off the alarm(s). Hence, the various fluctuations in your 'CPU States' section of your log showing the trouble app(s) are giving your device before settling into doze.

While your device is operating normally, you are beginning to cross the line of diminishing returns concerning battery life.

Meaning, your configuration values convenience over power saving. And that's okay. But, to get where you may want to be, you have some serious app/ device settings choices to make (or modify their settings), you need to get Google Play Services in check, install Greenify, and find an app to augment built-in Doze. You have root, it's time to become a responsible admin for your device.

If you wish to hear my suggestions (Which you probably won't like), just ask. I have a hardline stance against certain apps and device settings.
[BetterBatteryStats] X46X:
Thanks for your reply, I have Greenify (donation package), Aplify too. What can i do with Play Services? What Can I do more?
[BetterBatteryStats] jeremysherriff:
Please post dump files, not screenshots.

The issue is at the top of your first screen - fuel_alerted kernel wakelock.

Google:

http://xdaforums.com/showthread.php?p=22522525

http://xdaforums.com/showthread.php?p=22056515#post22056515

http://android.modaco.com/topic/348227-official-gary-crutchers-rom-discussion-thread/page__st__120

I'm gonna suggest you change kernel, or update to a later version - it looks like the issue was fixed in CM about 4 months ago?
[BetterBatteryStats] pilililo2:
Im using chainfire kernel :S

Sent from my badass Samsung Galaxy SII :)
[BetterBatteryStats] jeremysherriff:
Post in that kernel forum, it looks to be a reasonably well-known issue.

Also a reboot would resolve it temporarily. But it's definitely a kernel issue, and the links I posted have further links to the source code where the issue is.

Or change kernels for a bit, you might find something you like ;)
[BetterBatteryStats] californicated:
I find my "screen on" time quiet low. Could someone pls take a look at it?

It looks like k9 Mail caused some battery drain. Is it because of using push for my three mail accounts or the app itself?
[BetterBatteryStats] jeremysherriff:
Definitely K9 in push mode.

Do you need instant mail? Can you set it to scheduled hourly checks instead?
[BetterBatteryStats] californicated:
It's at least much more comfortable. Especially because I get facebook notifications via mail and don't need a fb app for fp push anymore.

Maildroid and other clients wouldn't cause less battery drain with push enabled, right?
[BetterBatteryStats] :
27 min, on push, over 24+ hours sounds about right. It will be draining your battery more than 27 minutes of wakelock worth, it's also transferring data back/forth as well. So 27 minutes + more "work".

Have you tried the default Samsung app set on push for comparison?
[BetterBatteryStats] californicated:
The default email app doesn't work with my email accounts :(
[BetterBatteryStats] jeremysherriff:
I use Touchdown for Exchange, and gave up on push mode eventually. They have even implemented the new c2md (or whatever its called lol) method of push, and although its better the drain is still significant.

If you need push mail, no problems. Just be aware of the sacrifice.

If you want to check your battery usage further using this app, then charge it and remove from charger just before you go to bed. Leave the phone idle overnight, then dump the stats to file in the morning. And for you, to avoid confusion, disable push in K9 during that night (you'll be asleep, so no need to get mail ;)) which will let us focus on any other issues rather than push email.
[BetterBatteryStats] californicated:
I don't know if you can see it in the log, but I use airplane mode at night (8 hours). There are no mails, wakelocks, .. in this time. I just deactivated push and setup to check my mails every hour. If the battery consumption should be significant lower I might leave it like that.
[BetterBatteryStats] chamonix:
You may also want to revisit you mail settings. The log shows push on both k9 and gmail. Is this on purpose?

Also the wakelocks are caused by syncing your invoice but also your draft folder. The second may be overhead and k9 has some advanced settings to selectively sync certain folders with push
[BetterBatteryStats] chamonix:
Upcoming features:

- prefs to remove certain chapters from dump

- dump with full details on alarms as looking into these deliver important info on behavior, esp Gsf and android