yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] dejanxxxx:
I hope that is dump file now good.
[BetterBatteryStats] fossils-n-dents:
SSP_Wakelock:

Humidity and Air Pressure

An app that controls a measurement of these values ​​is the problem. Weather app, maybe a health app.

Disable and / or delete.

Bluesleep: Something is keeping Bluetooth wakelock activated. Samsung Gear Watch, Pebble app, ect. Check any apps using bluetooth, and disable them. Or disable Bluetooth altogether in device settings when not in use.. If you are rooted there may be a kernel that eliminates this wakelock.

For further analysis, please submit a proper idle dump in accordance with the OP.

My friend, your 'Other Usage' stats and 'Alarms' sections are missing from your log. I cannot form an opinion about your device without them. See below photos for the needed information.
[BetterBatteryStats] dancrow:
Unhappy with deep sleep time. Any advice from you guys will be very appreciated.

http://cloud.tapatalk.com/s/59d9c7c3f1c42/BetterBatteryStats-2017-10-08_093231520.txt
[BetterBatteryStats] X46X:
Hi, anyone know what is job.deadline, job.delay alarms? I see lot of alarms from it but I can't find it in Amplify to stop it. Thanks
[BetterBatteryStats] mrjuniork:
Morning mate :)

Here comes my idle log.. As you can see the gms wakelocks are still there, in small numbers, but still there (although deactivated with MAT Pro)

Thx in advance, is really appreciated :good:
[BetterBatteryStats] mrjuniork:
Now :)
[BetterBatteryStats] elitistphoenix:
I'm interested in knowing this too.
[BetterBatteryStats] dejanxxxx:
I see, dont rooted phone. Ok, I check and delete app. I make dump file like on first page is writing for non-rooted devices.

I don't know why phone make wrong dump file.
[BetterBatteryStats] nalott:
My ancient Nexus 7 recently developed very bad behaviour: 100% of idle time PowerManagerService.Wakelock with NO significant Partial wakelock detected (all of them deeply below 1%). Any general idea of what may have caused this? The tablet is used in my car and I'm not aware of any change in configuration. I'm running rooted Autodroid (Slimrom based Kitkat).
[BetterBatteryStats] fossils-n-dents:
I have seen everyone's concerns. However, my job has some issues that require my attention.

I will attend to your requests within a few hours.

My apologies, as your issues are important to me.

Thank You for your patience.:good:
[BetterBatteryStats] PackElend:
I've just figured out that it shows me some log entries for the period between screen off and screen on when I deactivate BBS...Settings> Advanced> Network using API.

May the general description should by updated by read logs with 'BBS...Settings> Advanced>xxx API' activated and deactivated and look what settings shows more entries. Afterwards set options for maximum entries and follow:

But why do you ([MENTION=73965856]fossils-n-dents[/MENTION]) and [MENTION=5488402]Davey126[/MENTION] accept only idle dumps when [MENTION=1330150]chamonix[/MENTION] recommends otherwise:
[BetterBatteryStats] MACHEK:
Why would I have so much time on significant motion sensor and can I prevent that at all without root? On a note 8.
[BetterBatteryStats] fossils-n-dents:
Photo #1 is your 'Screen On' time.

Photo #2 below shows my device'' Screen On time afler 17 hours of idle. You cannot use the device while generating the idle log.

Something is keeping the Jobscheduler (In Android System or an individual app) from performing it's task(s). If you use Amplify, be careful limiting wakelocks. See [MENTION=2640294]elitistphoenix[/MENTION] question also answered below.

WhatsApp has taken 33mb of data in the 'Network' section of your log (A red flag), try lowering the update frequency. You have many apps that will wake your device while idle, but Android System is handling them quite nicely. Along with Location and Sync being enabled, your drain is correct. Actually, It's better than expected with the sheer amount of apps installed. Google play services seems to be under control also. You forgot to Greenify (Or maybe not).

Delete any app(s) you don't use (Force Stop> Clear Data & Cache> Delete). Reboot to recovery, wipe Davlik Cache &Cache (5 times each)...Reboot.

Disable Location and Sync when the device is not in use.

Somehow this is tied into a branch of Insight Analytics for Oneplus. The Mobile Device Management (MDM) branch. Possibly data collection keeping wakelock on your device to phone home.

While I couldn't track down those exact wakelocks you described, I think I nailed down the culprit for their existence. You decide...

https://www.zolldata.com/products/Insight/Insight-Analytics-FAQ/

https://www.chrisdcmoore.co.uk/post/oneplus-analytics/

I have emailed the dev, and hope he can shed some light on your issue. I will notify you as soon as I hear from him my friend.:good:

'PowerManagerService' is the sum of all combined kernel wakelocks. I have no idea what your trouble may be. An idle log would help immensely. For the record, I have a rooted KitKat (No Rom, Wi-Fi only) Samsung Tab 4 running xposed. So, let's see if I can help, but you have to meet me half way.;)

Excellent find! Hopefully, the OP can notice this. Otherwise, it may help others which is a good thing. Thank You.:good:

I may be misunderstanding 'Accepting Otherwse'.

This is what personally I do when I submit a log:

Charge to 100%, then unplug the device.

*Let device idle for 6+ hours. No touching the device, just let it sit on a table and walk away.

Retrieve the idle log, and submit it.

*I was alerted by Davey126 that 6+ hours was the new standard even though not reflected in the OP instructions. Instructions which were created in 2011 when devices were less complex I assume. And [MENTION=1330150]chamonix[/MENTION] has never corrected Davey nor myself.

Head into Settings > Advanced Features > and turn off things like Smart Capture, Palm Swipe Capture, Direct Call, Easy Mute, and disable 'Smart Stay' in the display settings. These all use power and sensors inside the phone to work..

Post an idle log one day just to be sure.
[BetterBatteryStats] mrjuniork:
First off, thx for your time and personal investment into my stuff.

To clarify some things: that 30mb of whatsapp is being uploaded every night coz of the Google drive backup. Is something I can really live with :)

And yes, you are right, despite of having many apps, the idle drain is pretty acceptable...

Today, I think I put the gms wakelock on an even shorter leash, with the help of wakeblock app.

I'm not using greenify, coz I'm using naptime with some other apps to take full control of what's happening on my device.

I also couldn't identify the oneplus wakelock, but once I have, I'm gonna lock this **** down :)

It really took a while to get my device where it is right now (mostly of course with your precious help) and I have the feeling there is always room for improvement, like I can't never really settle to squeeze out every possible percentage ;)

Now, almost 7 in the evening, 66% left with almost 4 hours of SOT, that is acceptable :)

Thank you for your help, I really appreciate it.

Cheers mate :good:
[BetterBatteryStats] Mister_Diamond:
Hi fossils-n-dents,

This time, in 8 hours and 52 minutes of idle, I lost 6% of battery.

I'ts not a serious thing, but I'd like to know why this drain is happened :)

By looking at the following log, the most evident is

RILJ_ACK_WL (Servizi del telefono): 1 m 29 s Count:1627 0,3% [servizi del telefono = phone services]

I've done some research on Google, but I didn't find anything of specific.

In the log of BBS I also see the "Light Flow" app, which is useful for notifications, but I didn't set it to repeat notifications: during these 8 hours (phone set to DND) I just receive an email message.

Kind regards.
[BetterBatteryStats] ChevyNexus:
8h and 34 minutes idle log. I seem to have lost around 5-6% and it just doesn't seem right to me. Pixel XL on Verizon. Also battery kinda nose dives when I'm actually using the phone. Phone was at 95% at 10:18 am and now it's down to 90% at 10:40 and I'm just using the Samsung Browser app. Chrome was seriously draining my battery. All versions of it. (Stock, Beta and Dev)

Any help would be great!
[BetterBatteryStats] fossils-n-dents:
Light Flow is waking your device 5. 9 times per hour. Even if intervals are evenly spaced, it will suspend the cpu at multiple frequencies (Also coinciding with other background processes) before falling into doze. Even in DND, the app may search for a network connection before finally timing out. You could try lessening it's updating frequency in the app settings (if possible), or disabling the app when not in use. RILJ_ACK_WL is basically network location problems (Possible bad signal) which will lead to wakeups. Turning off location may provide some relief while in DND.

Your 'Screen On' time must be less than one minute for a proper idle log.

Photo #1 below shows your 'Screen On' time.

Photo #2 shows an acceptable 'Screen On' time. Using the device during idle invalidates all statistics.

1. Charge to 100%

2. Unplug the device.

3. Place device on table...walk away for 6+ hours.

4. Submit dump file to this thread.
[BetterBatteryStats] Mister_Diamond:
With "network location" do you mean GPS? If so, on my phone, I completely disabled the GPS, also by disabling location using bluetooth and wifi; furthermore the signal (LTE or HSDPA+) is always reported to the max percentage: what should I look for, exactly, to reduce RILJ_ACK_WL?

Kind regards.
[BetterBatteryStats] fossils-n-dents:
I'm sorry for not clarifying.

1. Go to 'Location' in device settings.

2. Disable Location Reporting and Location History.

Afterwards, let's clear your devices' Davlik Cache and Cache by entering your devices' recovery menu for a fresh boot up.

1. Turn your device off.

2. At the same time, press the Power button and Volume down until your device vibrates.

3. Quickly release the Power button, but keep pressing Volume down. Clear your devices' Davlik Cache and Cache...Reboot.
[BetterBatteryStats] cpasoft:
First of all, thank you for all your help on this topic. All of us are learning a lot with you...

I have a simply question...

Why do you must to delete cache five times??

Enviado desde mi LG-H870DS mediante Tapatalk
[BetterBatteryStats] aeonix_05:
Seems like OnePlus is collecting usage data and sending it to their servers based on an article in GSMArena which is specific to net.oneplus.odm. For OnePlus users, you can set this off by navigating to ‘Settings’ -> ‘Advanced’ -> ‘Join user experience program’.
[BetterBatteryStats] RASTAVIPER:
Noooo!

Like no other big company doesn't do this.

Any other big news you wanna share?

Unleashed by ONEPLUS 3T rooted
[BetterBatteryStats] aeonix_05:
I'm pointing out the wakelock bro. Not the data usage collection. How bout you, what's up?
[BetterBatteryStats] Mister_Diamond:
Don't you worry: is my fault, since I didn't correctly understand :)

Well, I can't disable disable Location Reporting and Location History, because both was already disabled :) Maybe in my BBS logs did you see somethin specific to location active?

However, I often clean cache, but not dalvik cache. since my phone is not rooted...
[BetterBatteryStats] patrickdrd:
can anybody help with this?
[BetterBatteryStats] Sam Nakamura:
Strange thing, xposed was just updated up to android 7, so unless you're already turning android 8 it's definitely compatible, as long as you have a custom recovery (starting with Android 5).

Anyways, I granted those permissions via ADB on 2 different devices of my wife flawlessly, on what android version you tried the "PM command"? I know this error only from people who tried the ADB method on Android 4.4.4 and below, this method works only for android 5 and above..
[BetterBatteryStats] Geofferey:
*job.delay* *job.deadline* solution?

[MENTION=4598239]Callliope[/MENTION] [MENTION=5026482]xander59[/MENTION] [MENTION=7375615]RiDEN_1[/MENTION] [MENTION=6864507]charirma[/MENTION] [MENTION=4043335]RASTAVIPER[/MENTION] [MENTION=927026]X46X[/MENTION] I found out what was causing the MASSIVE amount of android system alarms *job.delay* & *job.deadline*! It turns out Google Connectivity Services was causing it on my Pixel which also explains the periodic wifi scanner alarm as well. Once I disabled Google Connectivity Service those alarms reduced drastically (job.delay/job.deadline). I should also note that I am running Pure Nexus 7.1.2_r24. I spent a freaking week tracking this down because BBS wasn't accurately representing the impact of GCS. I need to test over a longer period of time but I am positive that's what was causing my 15%+ drain overnight and lack of deep sleep/doze. I tested by doing a factory reset and checking alarms before and after updating apps. If this is truly the problem we need to start hitting Google up to get them to iron out whatever is causing the drain. I really hope this helps anybody who has been tearing their hair out over those two alarms.
[BetterBatteryStats] patrickdrd:
4.4.4 max, so nothing can be done for us with kitkat? I'm root as well
[BetterBatteryStats] Adamask:
Someone can look at my dump. Same old battery. =D

Moto G 2013, RR 5.8.5 Nougat, stock RR kernel and Xposed 88.1.
[BetterBatteryStats] rjm831:
I've 4.2.2 jellybean phone w/locked bootloader (ie no custom recovery) but rooted w/Kingroot. Xposed installed & works fine. BBS will not show kernel wakelocks but I've no computer access to attempt ADB.

Anyway, Xposed will install in your phone. It sounds between all your difficulties that perhaps your phone itself has some problem?
[BetterBatteryStats] patrickdrd:
I wouldn't think so, it's a custom Rom though, cm11
[BetterBatteryStats] kevindd992002:
Can BBS be also useful to detect which apps are draining the battery when the screen is on and you are using it?
[BetterBatteryStats] Sam Nakamura:
Sure, give BBS root privileges and done... This "PM commands" solution was introduced from Lollipop as the Android permissions system changed from there on... There's no need for this on Kitkat or rooted devices
[BetterBatteryStats] patrickdrd:
I have but I still can't see kernel wakelocks
[BetterBatteryStats] Sam Nakamura:
Then it's a ROM issue, I had this too and found out that the ROM developer hadn't made sure to reliable mount /sys/kernel/debug, only a notice to the ROM developer helps, he needs to update accordingly...

Temporary workaround (you would have to repeat this every reboot) is to take a terminal emulator and execute fallowig command:

mntP=$(grep /sys/kernel/debug /proc/mounts | awk '{print $2}')

if [[ "${mntP}" != "/sys/kernel/debug" ]]

then

mount -t debugfs none /sys/kernel/debug

fi

But it's actually not worth the hustle IMHO because you can't modify kernel wakelocks anyway, even it would bring some enlightenment to see kernel wakelocks there's no way to adjust them, except changing the kernel altogether..
[BetterBatteryStats] ChevyNexus:
Oops sorry about that. Let's try that again then.
[BetterBatteryStats] Oswald Boelcke:
I personally have really no idea how to achieve better on an unrooted (I apologise for my personal opinion: Google polluted) Pixel.

This are great statistics.
[BetterBatteryStats] DB126:
You don't assuming wipe is initiated from a creditable stand-alone recovery environment or tool such as FlashFire.
[BetterBatteryStats] shaggyskunk:
I'm not sure if it's related to a OTA update from my Carrier on Stock Unrooted Samsung Galaxy s8+ But it seems that the OTA broke the adb command that enables BBS - I wasn't getting other than something like - No stats available right now - Anyway - Running the adb command for BBS and it's working properly again - Just an FYI to anyone else who's using BBS on Stock Unrooted ?☺️

Sent from my SM-G955W ??
[BetterBatteryStats] fossils-n-dents:
Of course not, location is already disabled. What was I thinking?

The specific problem is that apps/ processes that have to use data keep the mobile radio active for too long. Google Cloud Messaging (GCM_CONN_ALARM) enables developers to send messages between servers and client apps. Your data radio is used for such transactions using RIL (Radio Interface Library), plus the normal background data from other apps. RIL, and RIL related wakeups will occur while transferring/ waiting for data transfer/ poor reception/ location issues, ect.

That said, limiting the interaction of apps using the network is your best bet. Light Flow, WhatsApp, and Google Package Measurement Service are your data/ radio/ battery hogs. If you are using DND, the Greenify app may be your best bet, or possibly get an instant Doze app which can enabled through ADB permissions, and whitelist any apps you truly need.

If no relief is found, the semi-nuclear option may help:

1. Clear data in Google Play Services, Google Maps, and Google Play Store.

2. Go to Settings> Power> Battery Optimization> Reset App Preferences...Reboot

Not having root severely limits our options when dealing with wakeup issues.

---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------

Because I wipe cache from TWRP, and I just wish to make sure. Doesn't take long to do.

DAVEY!!!:good::good::good:

---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------

Try this...

https://xdaforums.com/showpost.php?p=73693320&postcount=32709

It cuts down on the GMS issues.

Clear Davlik and Cache in Recovery...Reboot.

Create another log , and come back.
[BetterBatteryStats] 'Akira:
Can anyone take a look on this dump and advise me?

Link -> https://share.riseup.net/#i6lxKAWNequDMM5b3tzXDw
[BetterBatteryStats] fossils-n-dents:
Umm...Your device runs beautifully. The amount of apps combined with Google Play Services, and their interaction with Android System is quite harmonic. Even the CPUs' descent into doze is enchanting. Your device is fine.

For a lighter touch, you could try to Greenify, or disable any apps you do not need. Make a backup first...just because.

But, I would simply relax, and enjoy the device.
[BetterBatteryStats] kevindd992002:
Anyone?
[BetterBatteryStats] fossils-n-dents:
Whoa! Before we start, boot to recovery and clear Davlik Cache and cache.

Your network is switching between data and Wi-Fi also. Did you create this dump while walking?

Is it possible to do another idle run while the device is near a steady Wi-fi or data connection?

If so, please post another dump file while the device is stationary. This idle log leads to more questions than answers for myself.

My apologies.

Yes, if you submit a proper idle dump, we can try.
[BetterBatteryStats] 'Akira:
Thank you for your prompt answer.

I believe the dump was taken in a stationary position, but it was not created by me or came for a device in my possession.

I was really hoping for some help with this dump, tho, because it was taken by a "non-tech" person after some tries and a lot of exchanged instructions by text messages.

I don't know how soon, if so, I could get another one...
[BetterBatteryStats] fossils-n-dents:
I understand perfectly. The switching between data and Wi-Fi in the 'Network' section of the log may have introduced other kernel network problems that wouldn't exist from a stationary device with one data source. Preferably unplugged from 100%, left unattended to idle for 6+ hours.

Thank You for your patience.
[BetterBatteryStats] vasujahagirdar:
Hi, below is my new idle BBS. Plz look into this & guide

Even though I turned off Bluetooth, it's having wake counts!!
[BetterBatteryStats] kevindd992002:
Would you happen to point me to a guide to be able to do that? Sorry, I'm new to BBS and I'm not sure how to properly produce an idle dump that will be useful to you. I know how to take a dump when my phone is not being used overnight but I'm not sure about an idle dump with my screen is on (being used). Thanks.
[BetterBatteryStats] fossils-n-dents:
Looking good. I would turn off Location, and disable Candy Crush Saga when not in use. Do you have ForceDoze set to 'Disable Sensors While In Doze'? Do you really need Google Quick Search Box? if not, remove it. Wake counts aren't always indicative of a problem. Usually apps drive up the wake counts.

Also, try this to cut down on those 'com.google.android.gms' alarms (If you have not done this already). *Always make a backup before disabling services.

https://xdaforums.com/showpost.php?p=73693320&postcount=32709

When completed, reboot to recovery, and wipe Davlik Cache and Cache...reboot.

With the amount of apps you have installed you are doing well with your device. Anything under 1. 0% /h drain is great.

When time permits, return with another idle log.

---------- Post added at 10:57 PM ---------- Previous post was at 10:48 PM ----------

The proper dump is the one overnight while the phone is not used. Using the phone invalidates the stats. 'Screen on' time must be less than one minute.

'Unplugged to Current' , let idle (6+ hours)

Submit the 'Dump File' from within BBS to this forum. Good Luck.:good:
[BetterBatteryStats] githyanki:
You can use bbs to analyze your data while in use. Unfortunately, we cannot without being there to see how you used your phone all day. You will be the only one to know if you were on Facebook for 2 hours and played a game for 30 minutes. You can see that something is happening that you did not do, we will not know what you did or did not do.

Try it and if you see something that seems out of place, ask what it means.
[BetterBatteryStats] kevindd992002:
Ok, I'll try this first and will post back.

Do you, generally, recommend following your post here to improve battery life though?

I see what you mean. I usually use my phone only for web browsing using Firefox and some forum apps like Tapatalk or Reddit. I never play games and don't have an FB account although the Facebook app is installed by default in my Galaxy S8. I also use messaging apps like Viber and Skype. I know all these contribute to battery drain but yeah let me try and check the BBS data analysis during device use on my own first.
[BetterBatteryStats] fossils-n-dents:
1. 'Unpair' all Bluetooth devices.

2. Turn bluetooth off.

3. Go to Settings>Applications> Application Manager> All> Bluetooth.

4. Clear the Cache in Bluetooth.

5. Next go to 'Bluetooth Test' and clear Cache.

6. Turn Bluetooth back on.

7. 'Pair' your devices again. (But leave Bluetooth off until you require it.)

I would also suggest tracking down any app, watches, music players, In-car features, (All use Bluetooth Share Services). and disabling it, or it's Bluetooth connection. It may be holding a wakelock despite Bluetooth being disabled.

The issue may have be resolved in later system updates from the manufacturer.

*Pertaining to the Google Play Services Guide:

'PackageMeasurementService' and 'PackageMeasurementReceiver' will automatically reset itself on any reboot/ power off. You must re-enable these two services upon every reboot. Very important (Unless you have done so).
[BetterBatteryStats] vasujahagirdar:
Thanks, trying to follow about Bluetooth.

Regarding Google Play Services I do as per your advice always.!!
[BetterBatteryStats] MACHEK:
Attached is a new dump from me. I usually see lots of wakes during the day but here is the overnight one
[BetterBatteryStats] MACHEK:
This is also how much Gsam shows my phone is active even during sleep
[BetterBatteryStats] fossils-n-dents:
Your device is running flawlessly. The only way you could conserve more battery is to turn your device off.:D

Your GSAM shows Light Doze descending into Full Doze about 13minutes later. The constant broken line denotes device maintainenence periods (This is normal for background activity), followed by you activating the device to prepare your dump file in the end, thus breaking Doze mode. Perfect.

If you use your device during the day, many stats will be increased during usage. Your GSAM will look differently.

Your device sleeps like a baby. Enjoy your device.