yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] DiamondJohn:
So I have done the log, hopefully I got it right. I have attached the dump. But also put it up on hastebin https://www.hastebin.com/fedaleloxa.m

PS: anyone reading this, there is no need to do a search, the instructions are in the OP :o
[BetterBatteryStats] hd-patsan:
Hi everyone. First of all sorry for my poor english, it's not my native language. I have dump here, and I've read it by myself, but didn't do a lot of conclusions of it except for this one - my phone doesn't get to sleep at all (2 seconds deep sleep of ~8 hours of screen off) mostly because of kernel wakelock called "sensor_ind". I do appreciate any person's time (especially the ones trying to help) and I have googled this problem before but didn't find any solution so I eventually decided to post here. Even if nobody out here knows exactly how to figure this out, who knows - maybe someone can catch another issue from this dump, maybe the "sensor_ind" isn't my main problem. Hope I didn't violated any rules of this forum posting that.

I sincerely sorry but I didn't get it how to attach a files here and as the warning says I can't post outside links until I reach approximately 10 posts here. Can anyone please help me to bring my dump here?
[BetterBatteryStats] strongst:
You need to reach 10 posts as you're aware of that. Have a look at the new user guide in my signature.

Otherwise you can post a link with spaces to the uploaded file(pastebin for example) ;)
[BetterBatteryStats] DB126:
Or here for the most accurate results. :)
[BetterBatteryStats] DiamondJohn:
Thats word for word of whats in the OP
[BetterBatteryStats] Oswald Boelcke:
...only because the OP was changed to exactly @Davey126's wording after he provided this specific guidance.
[BetterBatteryStats] hd-patsan:
Thanks for advice with the guidelines, I've bookmarked it, but if you and people around here don't mind I'd go for a second way 'cause I really need to recover my phone's normal condition to use it on the job. Here's my dump (I did my best to not bother you with too "spaced" link :)) - https:// pastebin.com/pXcxT24c
[BetterBatteryStats] DB126:
Yikes - didn't realize my humble musings had been integrated into the OP! :o
[BetterBatteryStats] peterlee928:
i have had this wakelock also. a couple of tips (not sure which one worked for me):

1) if your auto-rotate setting is on - turn it off. then see if that wakelock shows up. if it does, then turn on auto-rotate again for a few minutes, then turn it off again. then see again if that wakelock shows up.

2) make sure that you dont have any motion sensors on.

3) clear google play services storage.

good luck :good:
[BetterBatteryStats] DB126:
See previous commentary here. Your log also shows a 0.4%/hr drop which is excellent. Deep sleep status and random wakelocks are irrelevant. Enjoy your well behaved device.
[BetterBatteryStats] MrRob0t:
I'm not sure where in my post I offended you, but I'm just going to walk away now. You help out, and give good insight, I've never in any post said or hinted otherwise. I said to each their own and then ended my post with a thanks. Clearly, I'm not trying to stir anything up.

That is the point. To enjoy our gizmos.

Have a good one.
[BetterBatteryStats] DB126:
No offense taken. It would seem a deeper explaination of the benefits gained with "5 minutes" of effort will have to wait.

Enjoy tinkering. :)
[BetterBatteryStats] DiamondJohn:
Now that we have that sorted ;)

Anyone have an idea whats going in my logs?:fingers-crossed:
[BetterBatteryStats] peterlee928:
lol nothing to walk away from. [MENTION=5488402]Davey126[/MENTION] has forgotten more about phone efficiency than many of us will ever know. and his major theme (along with all the other smart dudes in this thread) is "less is more". 80-20, know what i mean? but if you have any thoughts to squeeze more juice out of the lemon, everyone here i am sure would love to hear about it :)
[BetterBatteryStats] MrRob0t:
It's back where our conversation started.. :confused:

It's nothing I came up with. Perhaps you didn't understand or was confused since I'm not andybones but I found and quoted a response that you gave to him. My fault for not making that clear.

I saw your response here.

As I asked, I was curious as to what you meant by 'lite touch' as opposed to tweaking and digging into all those deeper dials. You gave me your answer, I was appreciative, and that was that.

It was an exaggeration when I said '5 mins'. For me, now that I know what I'm looking for from following that guide, it's more of about 15-20 mins. Unless I can just restore my backup, depending on the ROM. I haven't suffered from any negative effects and do see a large difference in my idle times. Could be the rom, the phone, or whatever that is giving me such great results. I can't say, I just know that it works, but was and am always open to trying other methods and testing the results. I enjoy tinkering, and that is the point. To play, have some fun while doing it and to learn.. Otherwise, mine as well be on an iCrap, or something that can't be unlocked/rooted.

Let's get this thread back on track. :cool:
[BetterBatteryStats] hd-patsan:
Thanks for advices, I'll try it, but can you explain what does mean "motion sensors"? I thought I only can control accelerometer via settings app. Is there a way to control others?

I completely agree on that, It's really not bad as I could think and I'll try to forget about this thing. My concerning started I think when I read a few kernel and firmwave reviews on my local tech-forum where people was talking like "0% per night! the phone sleeps more than good", so I (at the time having very very good battery efficiency as for me) was interested - does my phone "sleeps" that good too? And so here I am - spending my nights with BBS trying to figure a thing that never concerned me before. So yes, you are definitely right, but knowing myself it will take some time for me to get rid of this thoughts :)

P.S. Yesterday I moved from one kernel to another (4th kernel per week) and nothing changed, so I believe it's not the kernels causing the problem.

P.P.S. I just got realized that a few weeks ago I flashed a patch for /system/usr/keylayout/Generic.kl that enables my phone's fingerprints scanner to be able to wake up the phone from sleep mode. In other words I use my scanner as power button. So may it be the cause of "sensor_ind" thing?
[BetterBatteryStats] DB126:
Appreciate the response and clarifications. Many XDA members are tinkers at heart and learn from experiences both good and bad. It can also be enjoyable as are all passions of the heart. At some point there are diminishing returns in terms of knowledge gained and tangible benefits. That is especially true with power management on modern devices running Android 7+. Good battery life is a hot consumer item and thus became a major focal point for Google and hardware manufactures over the past several years. The gizmo you hold in your hand today is a different beast than what was circulating in 2015. There just isn't that much room for improvement (from a power consumption perspective) given a properly managed app portfolio and a little common sense.

I would be remiss in not highlighting your repeated references to backups. They are a lifesaver! Few make them and then spend hours or days unraveling and rectifying a poor choice. Welcome to the 5% club. Well done. :)

If you have time the community that follows this thread would likely appreciate any specific best practices you have discovered - especially those driving average idle power consumption from 1% to 0.5% per hour. The former is on the high side; latter rather low. Perhaps there is an undiscovered jewel in the rough.

---------- Post added at 12:13 PM ---------- Previous post was at 11:57 AM ----------

Surprised you need this as most integrated biometric sensors will perform a wake on demand function without mods assuming kernel support. As for 0% idle drain consider it on par with cryogenics. Cool movie fodder; not practical in the real world. :)
[BetterBatteryStats] nola mike:
Still haven't been able to figure this out. Almost afraid to post since it's still only .6%/hr drain. Except that something is wrong; this goes from all deep sleep to none, can't figure out what's triggering it, and nothing to my eyes seems to be doing anything excessive.
[BetterBatteryStats] MrRob0t:
Alright Peter, you see.. THIS post right here is EXACTLY why I would of walked away. Davey and I worked everything out with our adult words.. THEN comes you! 9 minutes before my post. I may not of been a member here for 10 years, but does NOT mean I haven't been following. What happened to treat others with some respect and how you'd like to be treated?

Davey is helpful, and very smart. If you bothered to read my posts, I've said this and NEVER hinted otherwise.

XDA has changed, and not for the better. :silly:

Obviously, he is well known here. But he is a big man. He can and DID respond for HIMSELF. Ya know, the guy I'm posting too.

I've already said the guide I follow. I'm not hiding anything, nor do I know why it helps so damn much, but coming here and fighting with the guy who helps everyone isn't my thing, nor to get jumped on by all those he's helped.. Not exactly the smartest of strategies..

Peace everyone. Best of luck tinkering.

And again this guide. Not every dial is turned, but a good 90% as not everything matched namewise. Period. I'm not doing nor hiding anything. If I had some magical key.. I'd share it. Davey responded appropriately and it's over.

Quite literally, all I did was ask for his lite approach. That's it.

High school sh*t right here.

:good: :cool: :laugh: :cyclops: :silly: :)
[BetterBatteryStats] andybones:
I've been holding off posting, but since it seems I started this whole fiasco with my initial post, I'll chime in. I was seeing about 0.1%/hr maaybe 0.2%/hr idle savings overnight and throughout the day, nothing ground breaking. But probably more around the 0.1%/hr idle mark. The payoff wasn't worth it for me. But if it works for ya and ya aren't seeing any negative effects, then by all means keep on doing what works. I've also found that less is more, but this is me. Who am I to question this guy? As I certainly am not as smart as [MENTION=5488402]Davey126[/MENTION], (also collectively we are more together than separate. :highfive:) with this stuff, or anything (we all have our strengths and weaknesses) nor was I the guy being spoken to.

Have a Blessed day, all!
[BetterBatteryStats] peterlee928:
one example is "lift to check phone". turning off display settings like that can be helpful.
[BetterBatteryStats] hd-patsan:
Actually they were performing this function when I was on stock MIUI ROM. However when I moved to AEX 5.7 Unoff. fp scanner only had been performing it's main purpose - biometric security, which I don't use, so I went for manual enabling its only function which I really liked. Anyways it doesn't matter already because I checked whether that lack of deep sleep problem is connected with this function assuming a scanner was waiting for touch all the time, especially in sleep mode (because the keycode for that "button" had "wakeup" value exactly), which was false - the problem haven't got disappeared, so I probably will leave it until I find something better than AEX for battery backup. Thanks for attention, people.

Oh yes, I got it. Thanks a lot!
[BetterBatteryStats] DB126:
Yeah, you are! We are all ignorant to 99.9% of the world around us with small (but powerful) points of light differentiating individuals. Anyone who claims otherwise is a fool by definition.

Truer worlds have never been spoken.
[BetterBatteryStats] peterlee928:
good luck! :good:

if not too much to ask, let us know if that worked out. then we can have it documented in this thread for future use :)
[BetterBatteryStats] andybones:
Thank you, kind Sir.

Very well said as well

Much love!
[BetterBatteryStats] DB126:
Nothing wrong; data collection anomaly. 0.6% is typical for this calibre device running Android 8.1. Lineage OS may be the culprit depending how well it has been optimized for platform. Enjoy your device; don't worry what happens under the covers provided vitals are good.
[BetterBatteryStats] TNSMANI:
Your post got buried in all that back and forth in the last three pages and XDA also failed to notify me, I don't know why.

First of all, you are running a very outdated version of BBS. Upgrade to the latest on PlayStore by joining the beta program.

On 8.1, you may not need Greenify. Please uninstall Greenify and take a fresh dump.

I don't know how many widgets you have but their update has a high number.

Are there other devices connected to your wifi? If so, disable them while taking the next dump. Also reset your router.

I am not able to find any other issue which will justify the drain.

After doing the above, take a fresh dump and post it here.

By the way, the attached dump doesn't contain anything. But the hastebin link does have the dump.
[BetterBatteryStats] DiamondJohn:
Yeah, I though that might of been the case, but didn't want to be pushy when asking a favor.

I previously downloaded the newer XDA version from the OP, but after running it for a day, I went to share the results, and it crashed every time:mad: I also took a logcat, which was also possibly lost in all the other posts https://xdaforums.com/showpost.php?p=77577722&postcount=34747 So I went back to the previous version. I'll update again, and try the save button. I also noticed my SDCard had a heap of BBS files saved in the root, so maybe even if it does crash, the files will be accessible :fingers-crossed:

Yeah, I would prefer not to run greenify if I could, so i'll give it a go without.

A lot! I have been gathering them over the past 5 or so years of using Android :D About 6 different widgets, but multiple instances of a few. Actually after my first run I saw one widget at the top of a list, so I froze it (actually hid it from system not just launcher) and ran the test again. I have also tried running with wifi off and the phone still doesn't appear to enter doze.

hmmm... this will be the hardest, as its my internet connection. I guess I'll have to search for my old cable :eek: to use on my PC.

That's weird. When I click on the hastebin, i dont always get something :silly:

Just for background, I have been running virtually the same setup for a number of years, nougat up to the week before last, and this no-doze issue started. My previous Nougat set-up lived in doze :highfive:, and it had all the same hoopla, with Greenify and widgets etc etc. that is on this 8.1 setup.

And thanks again for taking the time to look.:good:
[BetterBatteryStats] TNSMANI:
The latest XDA version is a debugging version. The beta in the PlayStore is the latest and doesn't crash, atleast for me.
[BetterBatteryStats] DB126:
Haven't looked at your log but will note 8.1 (Oreo) is not the best solution for all devices - especially those designed for/released with Marshmallow or lower. I have seen numerous instances of poor doze/sleep behaviors on 8.1 that don't occur on earlier builds. To be clear, there is nothing fundamentally wrong with Oreo; just many not be optimized for your hardware (or the kernel).
[BetterBatteryStats] DiamondJohn:
OK. I'll grab the one off the playstore.:good:

I hate to admit it, but when the ROM is flashed and left clean, this one dose like to stay in doze. so its something in my setup :o. But as I said, its a setup I have been basically using for a few phones/android versions, and have grown very accustomed to.

But your probably right or its just Oreo in general, even when I have got my phone to doze in Oreo, I think it still drains more than what I could get on Nougat. But its a price I can pay (to a point) to be running a newer OS:cyclops: And just for background info, its an unofficial crDroid Oreo, which I compiled from source myself.;)
[BetterBatteryStats] anyone23:
I think you have solved it. Ever since I disabled K-9 mail and rebooted the system a few days ago I now have around 1% battery drain per hour which was impossible to archive before. :)

Idle drain is still a bit too high for my liking but I think some of it comes from dual sim and of course the BBS watchdog service is still running.

Thank you for your help. I never would have figured it out as Android itself was barely showing any battery usage from K9-Mail. :)

I will let you know if the problem shows up again.
[BetterBatteryStats] nola mike:
I don't think so. It will sleep normally for a while, then something triggers it and it won't go back to sleep. I rebooted yesterday evening, and it was still sleeping normally at bedtime. Overnight my drain was 0.2% in deep sleep. I took a log if that would help.
[BetterBatteryStats] DB126:
Consistent 0.2%/hr avg idle drain isn't going to happen with your HW/ROM combo without significant tweaking which almost certainly would reduce functionality and/or introduce side effects. Post that log if you still have it.

Appears you are running Lineage 15 (which may or may not be optimized for your device) plus several GCM aware apps, including two mail clients, that tend be sleep disrupters. Not to mention three battery monitoring apps, an active weather app, dropbox and something titled "lonelycatgames". Plus a marginal mobile signal.

You are going to need to do some cleanup before one can get terribly excited about a 0.6%/hr idle drain which is what I would expect for your device. Use Greenify to quiet chatty apps or temporarily disable them one at a time. Start with Blue Mail.

Deep Sleep status is irrelevant; just a label that has little to do with overall idle efficiency. See: https://xdaforums.com/showthread.php?t=1179809&p=77567663
[BetterBatteryStats] nola mike:
Here's the dump of the .2%
[BetterBatteryStats] DB126:
Impressive. No lonelycatgames. Maybe that's the bad boy. :)

I still believe 0.2%/hr idle drain is not sustainable. Freeze/hibernate apps one at a time until you find the culprit that is yielding erratic 'deep sleep' results. Be interesting to see if that yields a meaningful reduction in average idle drain rates.
[BetterBatteryStats] nola mike:
Above.

Same behavior with AOSP ROM, FWIW.

Which section is relevant for that info? Where should I be looking?

Didn't even realize that the stock email client was doing anything, I didn't have it set up, thanks. Disabled now.

Bluemail appears to be waking <.7x/hour, which didn't seem particularly bad, although I have it set to fetch every 3 hours, so not sure why it's doing that. I took away run in background and keep awake permissions, we'll see if that helps.

Ok, seeing dropbox use as well (I'm looking at the processes section, here? "Sys: 4 m 37 s Us: 7 m 53 s"). Disabled keep awake/RIB there as well.

Lonelycatgames is x-plore file manager--didn't see in the logs where this is a problem?

The phone was in the same place for the marginal signal.

I was hoping I wouldn't need greenify and amplify with the improvements in power management. I'll see what this does. I still can't get my head around the relevance of deep sleep. I don't know why it seems to be working fine, then for no reason tell me it isn't going back to sleep. Would you agree that if I consistently get the same improvement in numbers when it's sleeping, that I have something that could be improved?

Thanks for the help.
[BetterBatteryStats] DB126:
Amplify and Greenify are completely different beasts. The former targets alarms and wakelocks (which are not evil) while Greenify is an alternative to doze. Amplify is disruptive, produces unwanted side-effects and often results in increased battery drain. Greenify is generally benign but usually not needed with newer Android builds given the effectiveness of doze. That said, it still serves as a nice control vehicle if one suspects an app is exhibiting unwanted behaviors. I have it installed on all my devices and usually have a half dozen apps in the watch list including such gems as Google Maps which pays far too much attention to location changes and camera use.

Don't get wrapped up in minutia. You would probably never know your device was not entering 'deep sleep' if not for a geek peek tool like BBS. Idle battery consumption remains reasonable even when the device is supposedly awake.
[BetterBatteryStats] vasujahagirdar:
Report_wake_lock

Hi guys, since 3 days I'm having 0 deep sleep & battery drain in my Viperone 6 rom htc 10 device, BBS showing report _wake_lock 100% attached dumpfile. Can anyone suggest the solution?

Thanks
[BetterBatteryStats] DB126:
Log includes 53 min of screen-on time; unusable for idle analysis. Reread OP and resubmit an appropriate log.
[BetterBatteryStats] rievna:
Thanks for the info, in that case, I definitely don't use Touchdown. I'm just frustrated because my awake time is almost double that of my screen on time, and the biggest offender is this *overflow* thing. I just noticed it has the number "1013" under it, I'll try to attach a screenshot.
[BetterBatteryStats] rmean:
hey guys, I'm having an extremely high amount of wakelocks caused by 'syncloopwakelock'. what exactly does cause these wakelocks? anybody had experienced this?

regards :)
[BetterBatteryStats] The1Shark:
Well,

It is a stock Rom .. so if there is a bug, it is not in the Rom.. sorry
[BetterBatteryStats] Karpfenhai:
hmm, in that case maybe its simply what its written and a Stack Overflow? 1013 could be the PID but I'm just guessing, could you provide a full dump from BBS and do a logcat? google doesn't really help on this, the only hint is touchdown, do you use any other mail client? Maybe they are using the same api..

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] LegendZenify:
Thank you for your analysis.

I didn't notice that bmw was taking a sample every minute.

How do I change the sample time on bmw? (changing the history update rate does not change that, just the time gap between history data)

As for sync, I did not set auto-sync.

My email (1 hotmail account), facebook, beautiful widgets are all set to poll every 4 hours.

Colorize widget (facebook) polling every 1 hour.

Should I disable gmail as well? No idea how to change settings on that, but I do not usually use my gmail account anyway.

I have 140+ app elements (when I view the market), I presume I should disable most of these to more accurately pinpoint the problem?

I will take your advice, do you have any recommendations for email app?

If it helps, my phone is the SGS2 (stock 1650mah battery), running Checkrom V6, Siyahkernel 2.6.12, modem DXKL1.
[BetterBatteryStats] chamonix:
You wouldn't find overflow except in the android source. Overflow isn't a wakelock but the indication that an internal counter in android's batteryinfo service went wrong. So it basically means that the reading is not accurate for one part.

Possible workaround: shorter reading
[BetterBatteryStats] rievna:
*facepalm* That makes perfect sense, actually.... I'm guessing that's from time I went into recovery and made a backup, since I was planning on messing with some things... overflow probably refers to the "gap" in the graph while to the phone was in recovery mode.

Thank you!
[BetterBatteryStats] sohebq:
Anyone using "handcent sms"? , it always causes high awake time. When a message is received, it will appear as pop-up. If you don't check it and turn off the screen, it will keep the phone awake. This usually happens with me when I receive text while I am sleeping. Strange issue :(

_________________________

I added cool smileys to this message... if you don't see them go to: http://s.exps.me
[BetterBatteryStats] superbobup:
+1 on 'syncloopwakelock' however it does not happen every time I pull a dump (pretty much every morning for the past week) but has happened about 3 times. I have sync turned off for everything. One thing I did notice is when I go into Gmail it will automatically refresh (I can't press the refresh button because it is in the process of refreshing) even though my sync is off. This happens under wifi, 3g or 2g...any ideas on it or anything I can do to help?
[BetterBatteryStats] qualitymove13:
3 plus hours wake lock

I realize this log is from two days on battery but is this log show normal activity? Thanks for taking a look.