yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] adhammagdy:
Yeah I changed the kernel to the new Firekernel for N.. and uninstalled the speed monitor but still not fixed.. I purchased greenify pro and set it to shallow hibernation with aggressive doze and doze on the go.. and added all system and user apps to auto hibernation..

This fixed the issue for a few hours but returned after reboot..

I've been having this problem for a few weeks and tried different ROMs and they all have it.. maybe because all of them are based on Lineage which doesn't officially support my phone.. also I tried before with factory reset and safe mode but still not sleeping.. but sometimes the problem goes away randomly and returns..

I noticed something strange in the logcat..

There is an error related to sdcard keeps popping up every second.. and it goes like that all the time 24/7

Attached screenshot
[BetterBatteryStats] j1gga84:
Delete
[BetterBatteryStats] DB126:
Best take this to your device forum...not a BBS concern/issue.
[BetterBatteryStats] adhammagdy:
It is related to a previous reply and could be a cause for the non sleeping issue
[BetterBatteryStats] pjadec:
Probably sdcard handler error or something wrong in sdcard or phone rom not fully supported so unable to fix it
[BetterBatteryStats] Watanabe_You:
Anyone know what does the User CPU and System CPU mean in the processes list?
[BetterBatteryStats] DB126:
Exactly what is says: CPU time used by system processes (think OS/ROM) and CPU cycles consumed by user processes (think the apps you have installed). Realistically the division is not that clean but the stat remains useful for those seeking to optimize their device's battery consumption.
[BetterBatteryStats] zilan:
I dont know why i have this , my signal is ok. Even on airplane mode i still have this. I have wipe data, factory reset even clean install but still the problem persists. And it drain my battery so fast. Does anyone here know how to fix it? Thanks
[BetterBatteryStats] peterlee928:
hey davey, just wanted to give you an update.

so the doze/deep sleep did indeed work after your suggestion. but one thing i noticed was that i no longer received gmail updates. all my notification settings were on.

certainly that issue could have resulted from something else that im not aware of. but as far as i remember, i didnt make any tweaks to my phone after i followed your suggestion.

not posting to be negative in any way. spirit of my post is to share my experience is all :)
[BetterBatteryStats] hisee:
Hi i am getting 30%+ battery in 7 hrs (no wifi and no data, it's is sleep mode)
[BetterBatteryStats] Oswald Boelcke:
This is not the required idle dump. See:

Screen On (): 2 h 9 s 17.0%

Suggest to take a dump in accordance with this advice by @Davey126
[BetterBatteryStats] DB126:
Hi peterlee928 - it's unlikely clearing Google Play Services cache/data was the cause of missed Gmail notifications during sleep. As a test exempt Gmail from battery optimization (Nougat setting). See if that helps.

I am travelling the next few days with limited network connectivity. Will check in next week to see if condition persists.
[BetterBatteryStats] peterlee928:
thanks for the response and follow up :)

to be precise, im using inbox by gmail, not gmail (i originally misstated). tried to exempt inbox from battery optimization. also tried changing notification importance to 5 (max level). all no dice.

so i just reflashed factory image.

im going to do run my phone full charge tonight and check the bbs tomorrow morning.

safe travels :)

-------------------------------------------

EDIT

so after taking the steps above, the phone was not going into deep sleep.

so i deleted all data from google play services again and rebooted.

over the past handful of hours, i noticed the following:

1) phone goes into deep sleep mode for the majority of the time when screen is off

2) i am receiving email notifications without having to exempt inbox from battery optimization and/or changing the notification importance

going to do a bit more observing and testing. but my hypothesis is that i had some sort of [myandroidtools] settings before that caused my inbox notifications issues... and when i reflashed factory image and redid some settings again in myandroidtools, autorun manager, and greenify, i inadvertently left out those "bad guy" modifications that were causing the inbox notification issues.

and of course, the master [MENTION=5488402]Davey126[/MENTION] is spot on per the usual ?

i will provide a (hopefully) final, short conclusion after said testing/observation.

much thanks again ?

----------------------------------------------------------

EDIT #2

https://www.androidfilehost.com/?fid=961840155545577441

0.0%/h lost over ~5 hours.

no issues with email.

thanks again [MENTION=5488402]Davey126[/MENTION]. *bow down*

safe travels ?
[BetterBatteryStats] hisee:
Hi, I lost 30% in sleep mode 7hrs

Please can any one help
[BetterBatteryStats] hisee:
Can you look it
[BetterBatteryStats] adhammagdy:
I have the same bug with vibe p1 on aosp extended nougat and fire kernel 3
[BetterBatteryStats] cswithxda:
Does anyone experience "no stats have been collected" for only the Alarms? All other categories work fine.

I searched the whole internet and this thread. The last mention of this issue was back in 2014... The environment is 7.1.2 June Pure Nexus, root, and nothing else. In raw stats, it's the same thing - all show up except for Alarms.
[BetterBatteryStats] Freak07:
HTC U 11

Hey to all,

I can see no kernel wakelocks on my HTC U 11.

I installed BBS as system app.

Can anybody confirm this?
[BetterBatteryStats] Salty Wagyu:
Kernel Wakelocks and Alarms show as "No stats have been collected yet". I don't know if this because I moved to Nougat and/or started using Magisk instead of SuperSU.

Alarms work if I set "Alarms using API" in Advanced at least.
[BetterBatteryStats] dschense:
mntP=$(grep /sys/kernel/debug /proc/mounts | awk '{print $2}')

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

then

mount -t debugfs none /sys/kernel/debug

fi

Run this in terminal with su rights.

(I use tasker to run this on every boot with su rights on shell)
[BetterBatteryStats] j1gga84:
I upgraded my samsung galaxy S5 (klte) to nougat (ResurrectionRemix 5.8.3) some days ago.

I am quite satisfied with the runtime compared to MM, allthough it is not as good as RR 5.7.4

When I check the wakelocks in BBS I see that android is on first place and google play services on second place.

I have attached some screenshots. Is there anything I can do to reduce the android and google play services wakelocks to

get a bit better battery consumption?

many thanks and regards
[BetterBatteryStats] DB126:
Not (easily) on Nougat. And they probably are not impacting battery life to any significant degree. Big numbers don't always translate to big drain. But those numbers...ugh...they are sooo annoying to look at.

If concerned about drain submit an idle log as described elsewhere in this tread (first few posts).
[BetterBatteryStats] peterlee928:
DELETE
[BetterBatteryStats] rholm:
Having some battery drain issues with my Samsung Tab Pro S2 running RR 5.8.3. I'm losing about 3% /hr when doing nothing. Please have a look. It does seem like the device is sleeping. I've tried a bunch of changes, Greenify, CPU governors, and other battery savers. They've help some as the drain was about 7% to start with.

Thanks!

Cheers,

Rich

http://cloud.tapatalk.com/s/594f2dbec34e0/BetterBatteryStats-2017-06-24_221901440.txt
[BetterBatteryStats] DB126:
Device did not at all during monitoring window. Reason is not immediately evident but suspect Google Play Services may be a factor. Try clearing all data via settings->apps followed by reboot.
[BetterBatteryStats] rholm:
I cleared data for google play services and rebooted. Will collect data again tomorrow.

Thanks!

Cheers,

Rich
[BetterBatteryStats] Al Gore:
Hi guys I need assistance.

Phone S4 GT9500 LineageOS. Greenify, ForceDoze, some services disabled via MyAndroidTools, most of the apps blocked from running in background and running on boot via Privacy Guard. Location toggle is off.

I have attached 3 logs below:

1 - full night, phone slept well and lost 0.3%/h

2 - full night, same settings, phone slept well however it lost 2.0%/h which is unacceptable.

3 - me walking around with the phone, data, wifi and location are off, however the blasted NLP wakelock is very active.

Any thoughts on night logs? And any suggestions on how to fight NlpCollectorWakeLockand Intent: com.google.android.location.ALARM_WAKEUP_ACTIVITY_DETECTION? :confused:
[BetterBatteryStats] githyanki:
I see very little difference between the good and bad night. How old is the battery? You may have a bad point in the cells that cause a sudden drop around a certain level.

As for nlp, make sure scanning is off and disable the several options in Maps for nearby things, traffic, etc.
[BetterBatteryStats] Al Gore:
Scanning is off, battery is 2 years old and new one is being shipped from China atm.

Everything in Maps is turned off + Maps are Greenified, but with global location switch set to disabled I would have expected even with everything enabled in Maps to have no effect?
[BetterBatteryStats] j1gga84:
Anybody can tell me why the times under partial wakelocks are not correct anymore?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[BetterBatteryStats] rholm:
Updated log. I cleared data for Play Services.

Thanks for having a look!

Cheers,

Richhttp://cloud.tapatalk.com/s/595032350ad83/BetterBatteryStats-2017-06-25_164807823.txt
[BetterBatteryStats] Al Gore:
It literally didn't sleep at all. And weirdly almost all wakelocks lasted 9m42s.
[BetterBatteryStats] DB126:
- noted several active weather apps on first submission...always suspect when dealing with unexplained drains

- that said, agree with [MENTION=1631192]githyanki[/MENTION] assessment on battery age and possible asymmetric/unpredictable discharge pattern

- reboot device to see if that fixes consistent wakelock duration issue; suspect is is a reporting glitch vs accurate indication of actual wakelock activity

---------- Post added at 11:13 AM ---------- Previous post was at 11:09 AM ----------

- noted com.Elecont.WeatherClock.eWeather HD (ie: eWeather HD); ugh; uninstall that to see if sleep resumes
[BetterBatteryStats] Al Gore:
I have weather underground installed with all syncing disabled and weather timeline without notifications and updating once every 3 hours. It does run a bit more frequent than that for reason but I think it's mostly fine :)
[BetterBatteryStats] DB126:
Also cyanogen weather app/service (in bad log). FWIW I also use weather underground and weather timeline and generally find them to be well behaved. But neither runs in the background; only manual updates. That's not due to any detected issues with current releases but behaviors adopted over time. WU in particular had a run of poorly engineered releases that did not honor user preferences and consumed resources unnecessarily. Again reinforcing recent builds seem to be fine.
[BetterBatteryStats] fossils-n-dents:
[MENTION=3245036]rholm[/MENTION]

You have multiple weather apps, Evernote, Tapatalk Pro, Android Calendar Storage, Google Search Box, Android Email, Gmail, Google Play Music, Facebook, ES file explorer Pro (Why is your file explorer holding wakelock?), Twitter, Yahoo Sports & Fantasty Football , Android Sports, Ninefolders, SolCalendar, and Shiftyjelly Pocketcasts all holding wakelock.

And you expect great idle drain consistently?

Google device sensors were active 3 h 44 m... I take it you're not using Greenify to properly hibernate, nor ForceDoze (Or similar) to disable your sensors during sleep)? Your dumpfile doesn't even show 'Deep Sleep' at the top. It says your device was Awake (Screen Off) 4 h 33 m out of 4 h 43 m. And your phone 'Idled' at 900mhz for 4 h 12 m. Far from 'Sleeping'.

Your battery is being assaulted dude. You have some app choices to make, and some tweaking to do.

I would suggest you start by doing a proper Idle drain (6+ hours...please), and truly let Davey126 have a better look at your device.
[BetterBatteryStats] Al Gore:
@fossils-n-dents

You got a wrong person :P
[BetterBatteryStats] 'Akira:
Hello.

Since I downloaded this app (5 days ago) it has been unable to identify kernel wakelocks, aways displaying the massage "No stats have been collected yet".

The message persist even after the device remain " idle" for 8+ hours (every night I unplugged the device for the charger, immediately turn the screen off and live it for 8+ hours).

Everything else in the app seems to be ok.

It is possible that my device has no kernel wakelocks? Or is more probable that the app is failing to "read" then? Can anyone help me diagnose this?

I am using LineageOS 14.1 (Android 7.1.2)
[BetterBatteryStats] DB126:
Do you have root enabled (under developer options) in LineageOS and has BBS request and been granted root privileges? Above assumes you are using native root; if not identify method and management tool (Magisk, SuperSU, etc).
[BetterBatteryStats] 'Akira:
Yes. Using native root. Already give BBS the proper permissions...
[BetterBatteryStats] rholm:
I have most of that on other devices without issue. I'll pare back the apps and see what it does. I loaded NapTime and that helped. Is ForceDoze better?

Thanks everyone for the assistance!

Cheers,

Rich
[BetterBatteryStats] iroshan:
Could some help me to figure out what's causing this much battery drain?

WiFi, Bluetooth, data off. Connected to 2g network for calls.

Thanks.
[BetterBatteryStats] DB126:
Really shouldn't need ForceDoze, Greenify, Lspeed, NapTime or similar doze management tools on Nougat provided your app suite is well behaved (note previous comment on eWeather). However, if you believe they help I would lean toward Greenify followed by ForceDoze.

---------- Post added at 04:00 AM ---------- Previous post was at 03:48 AM ----------

Device never slept during 6+ hour monitoring window (simply idled); cause is not immediately evident from log. Google Play Services can sometimes block sleep if the data store has become corrupt. Suggest clearing all Play Services data (not just cache) followed by an immediate reboot. May or may not help.
[BetterBatteryStats] Andiii:
i have received my new xiaomi mido and just unlocked the bootloader, flashed Slimrom + Gapps and rooted with supersu. I have installed the v2.2.2 but cannot turn it into a system app. The app tells me i should flash via .zip. I also tried with titanium backup but it freezes. Is it needed to run as system app? If yes, is it enought to copy the APK to /system/priv-app via root editor ?
[BetterBatteryStats] 'Akira:
From the 3# OP:
[BetterBatteryStats] DB126:
No need to run BBS as a system app as developer has reinforced on several occasions. See 3rd post in this thread.
[BetterBatteryStats] Andiii:
wow that are good news - thanks a lot....

should i ignore the Info that it is not possible to read the dump?

The Text states it has tobe installed to system. Maybe this should be fixed then.
[BetterBatteryStats] Darayavahus:
Hello again

Once again I'm back with annoying battery issue on my Galaxy S7

Let me write it straight:

Phone was lying still for 6h 33m

Deep sleep: 6H 14min

Screen on time : 10m 44s

Awake [screen off] 8m 20s

WIFI ON, Data signal shows 100%off, but I have the range in home due to in-country roaming provided by my carrier. Strange, but fck it.

No mobile data in use / turned off

Using greenify to hibernate most of the apps

Using naptime to force doze the sht out of my cell phone.

Every "useless" common stuff like location, nfc, and so on are OFF

There were no calls, actualisations, messages for the time being.

I even called my wifi provider to change my wifi IP assignment to be fixed, and I have changed wifi settings as well in my phone from DHCP to static [not sure if that changes anything though, I read somewhere that it does, but I dont see any improvement]

Wi-fi signal strength was at 30% when he was lying for this period of time [yeah,low]

How the hell a phone can drop 1.5% of battery [:EDITED:] every hour [:EDITED:] while doing NOTHING. I don't see anything to point out any specific wakelock. The logs are kinda gibberish for me though, so I post them below for someone to validate it.

I will be very grateful for anyone, who tells me what's going on with my phone, or if this normal and I'm being paranoid - I don't know. My former phone had much better battery management :G

Thx in advance and have a good night..
[BetterBatteryStats] fndpena:
Is this working with Android O?

I can't find any info about this in the thread...
[BetterBatteryStats] fossils-n-dents:
You had a 'Screen On' time of 10 m 44 s. That altered your statistics accuracy greatly.

You must leave the phone untouched for at least 6 hours. Then Davey126 and the guys can get a better handle on your situation.

You're not paranoid, the phone IS really out to get you.:laugh: But with sound advice, and and a little discipline, you can gain the upper hand.

But it all begins with a proper idle run, dump, and maybe some research. Knowledge is power.
[BetterBatteryStats] DB126:
Log contained 10 min of screen on time which invalidates use for idle analysis. Your accompanying comments mentioned a 1.5% drop over 6 hours or ~0.25% per hour which is well within the 'normal' range for an idling device running an Android 7.x ROM. During that time your phone was far from doing "nothing". At least one radio was powered up and struggling to hang on to a weak signals. A small amount of power is required to maintain memory contents and respond to user commands (eg: button presses). There was 8 min of screen-off activity, most/all of which was devoted to doze maintenance windows. This is not wasted time; most of those activities would take place all at once when your device was summoned from sleep, possibly introducing lag.

You'll need to submit another dump (bbs log) with <1 min of screen on time for a proper idle analysis.
[BetterBatteryStats] Darayavahus:
that was 1.5% every hour mate. Nevertheless I will make a dump today without any screen on time.
[BetterBatteryStats] Darayavahus:
Here is updated dump from my phone, created after 3h 47m of unplugged state.

3H 40m of which is deep sleep

5m awake [screen off]

Screen on: 25s

0,8% drain per hour without doing a ****, just WiFI on. Rest is off

Is this a wifi fault? Damm, logs don't point to anything particular. I'm really concerned. From my POV, battery should be drained by half of the given amount.

Any advice would be much appreciated.

Logs below:

/sorry for spamming the thread./
[BetterBatteryStats] DB126:
Observations:

- no red flags in dump

- screen-off wake time was a little high but not unusual for device and ROM

- both radios (mobile; WiFi) struggled to maintain a stable connection

- modest GPSD wakelocks extended screen-off wake time (mobile radio):

https://xdaforums.com/showthread.php?t=2623112

https://www.reddit.com/r/GalaxyS6/comments/3h8wir/wakelock_gpsd_watch_out_for_this_one_this_is_what/

- Gmail and WhatsApp both performed check-ins during doze maint windows

Regardless when acquired device was released 3 yrs ago with a kernel likely not optimized for Nougat (original ROM was KitKat based). Radios and other sensors from that time frame did always enter reduced power states or idle efficiently. Low signal strength and battery age are likely playing a significant role in the observed drain rate.

All things considered 0.8% per hour is not unexpected. Half that is probably unrealistic.
[BetterBatteryStats] prosnz:
Hey Davey. Could you please have a look at my nightlog?

For me 0,8% is ok. The problem is at work, Its draining a lot. I would post a log for daytime, but I first have to figure out how to get it done, since I need it at work.

But maybe you can find something in the nightlog :)

Device: sony xperia z3+ running LineageOS
[BetterBatteryStats] ichigo696:
There's something could i improve? (I know it's not a 6h dump but only 3h, it's the max time i could let it idle)
[BetterBatteryStats] fossils-n-dents:
I would love to know what that "com.android.internal.telephony.data-stall" is at the top of your 'Alarms' section in your BBS log. Interesting.

Dude... You want the doctor to give you a complete physical, you take off your shirt, yet refuse to drop your pants?

Help Davey126, and the guys help you. But, you must go about it correctly. Put the phone down:D ...get it over with.

6 hours minimum (Give BBS a chance to detect rogue processes, or a battery draining app). Submit your proper log, await the diagnosis...Profit.:good:
[BetterBatteryStats] ichigo696:
I know how to read a dump so i only wanted to double check just in case i was missing something in my personal diagnosys. By the way 3h is a reasonable time in order to identify serious drains. Thank you :)
[BetterBatteryStats] fossils-n-dents:
Then you know there is a system level difference between a 3 hr idle run, and a 6 hr idle run, as per the OP requirements regardless of what you personally feel may be a sufficient idle run. Knowing how to read an idle dump, (As do I know how to read), and submitting one to a highly respected/ well regulated forum for diagnosis are two different things.

Not very fair to the integrity of the OP, other members, the gentlemen who give their time freely, or the high standard of the forum itself. IMO

I was not building animosity, I only tried to infuse humor with simple truths about how the forum is operated. The very same rules in which I, and others must abide.

My sincerest apologies if you were offended.
[BetterBatteryStats] DB126:
No smoking guns but lots of small drainers that are not easy and/or practical to contain. Age of device and potentially battery health may be contributing factors. Seen several older Sony devices that don't acheive stellar idle results on Nougat. Poses the question whether a device/kernel originally supporting Lollipop is properly optimized for Android 7.x.

If drain increases significantly at work it is likely due to poor signal quality either on WiFi or (more likely) mobile. Not much you can do about that other than shutting down radios. Probably ok for WiFi but you'd likely loose critical functionality (eg: voice, SMS) killing the mobile radio.
[BetterBatteryStats] Andiii:
Here my first logfile from this night. Is there anything i can do to get less %/h in idlehttp://cloud.tapatalk.com/s/5955d079c6a5e/BetterBatteryStats-2017-06-30_055914440.txt

Gesendet von meinem Redmi Note 4 mit Tapatalk
[BetterBatteryStats] DB126:
Short monitoring window can be misleading. That said a 1% drop over 3 hrs (including 6+ min of screen-off wake time) is respectible. Surprised to see YouTube at the top of wakelock list. Usually that pup is pretty well behaved. Likely a fluke or subscription based activity; something to keep an eye on.

---------- Post added at 05:32 AM ---------- Previous post was at 05:16 AM ----------

Looks good overall with a modest 3% drop over 8 hours (~0.4%/hr), especially given start point in battery charge state (27->24%). Several minor drainers but nothing that warrants immediate attention IMO. Unclear what caused device to zoom along at a high CPU frequency for a cumulative 2 min. Possibly Google location services activity (guessing you have it set to 'High Accuracy'). Might consider 'Device Only' which should stop the NLP wakelocks but will also reduce location services performance in locations where satellite reception is weak.
[BetterBatteryStats] House_of_Ka-el:
Hi, I'm having very unusual high battery drain on my device.

My device is hardly in a deep sleep state when left idle. Kindly assist in checking my BBS stats.
[BetterBatteryStats] ichigo696:
I was not offended :). I do respect OP and his work. I pushed up a 3h log only because it was the best i could do yesterday and, considering my setup, usage etc. IMHO, because 3h were sufficient to me. My apologies to you and to OP.