yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] thewaywardgeek013:
Ohh, ok, will update once tried it on my free time.
[BetterBatteryStats] ufdlim:
Anyone have experience with State Farm's Drive Safe and Save app? Seems like it is responsible for the vast majority of my wakeups and partial wakelocks...

But it's not an app I can completely disable from the background. I am getting $70 off my insurance bill this upcoming period due to its tracking of my driving habits (via Bluetooth).

I've tried to use the WAKE_LOCK ignore command but it hasn't reduced any of these numbers?
[BetterBatteryStats] DB126:
Wakeups and partial wakelocks are not evil. What happens afterwards determines if there is an issue that needs to be addressed. What symptoms (other than the presence of raw data) have you observed that suggests action is required? The included screen snips do not provide sufficient context. That said, the raw numbers are not exceptionally high; certainly nothing that rings alarm bells (pun intended) in isolation.

In a more generic sense any app that continuously observes/reports behavior is going to have a consequence on battery endurance. Driving/navigation apps are are one example. Social media (Facebook...ugh) and fitness apps are other examples. Me thinks State Farm is the least of your worries.

While you're at it take a hard look at the Join app. Probably the #1 culprit w.r.t. extended wake times and battery drain.
[BetterBatteryStats] ufdlim:
Thanks for the insight. I just couldn't figure out why my Pixel 2 barely lasts the whole day with just minimal use. The State Farm app is always high on my list of partial wakelocks and alarms I'll give deleting Join a try. I've already tried ignoring the wakelocks for all the other social media apps.
[BetterBatteryStats] DB126:
Ignoring wakelocks likely won't solve your problem; akin to taking two aspirin for a broken leg. You will need to do an idle study to determine which services and/or apps are chewing away at your battery when the device is not in use. You can find guidance in the first few posts of this thread; also here.

Pixel device are not known for stellar battery life. Lots of sensors and background activity. With effort (and rooting) those behaviors can be contained. In most cases whacking a few offending apps strikes an acceptable balance between battery endurance and becoming an obsessed {deleted} geek trying to optimize a gizmo that's suppose to make your life easier.

Edit: On a whim I decided to check up on the trending definition of a non-dictionary word used above that I have always associated with 'computer geek'. Yikes - turns out it has derogatory wartime roots. Clearly an apology is due to any one offended by such offensive language which has no place (zero, none, nada) in modern vocabulary. I will not be using that one again.
[BetterBatteryStats] Sygmasf:
hi guys, i don't know where i can look for to solve this abnormal alarm related to "android" process

thank you in advance for the help
[BetterBatteryStats] sharkyslo:
My Facebook Lite has numerous wakeups. I have tried everything, also with Greenify, but numerous wakeups are still present. With Greenify I succesfully turned off wakeups of all other apps, but not FB Lite... Any idea?
[BetterBatteryStats] strongst:
Without wakelocks you won't receive any message from that app... That's the purpose of a messenger app isn't it?
[BetterBatteryStats] DB126:
Beyond that what problem are you trying to solve? Facebook Lite isn't known for excessive (operative word) battery drain but does use some power performing core functions. If still too much uninstall the app and go for the web interface instead.
[BetterBatteryStats] sharkyslo:
I am not talking about Messenger. I am talking about FB Lite only. I don't want that FB is noticing me about everything. But Messenger I have enabled, if someone sends me a PM... Or maybe are Messenger and FB connected and the Messenger wakes up FB?

---------- Post added at 12:06 ---------- Previous post was at 11:58 ----------

None, but it is really strange, that here are so many wakeups, despite Greenify takes care of it. :)
[BetterBatteryStats] DB126:
Verify you are using the most aggressive Greenify actions available including ignore background free and working state. Consider installing/using island mode or switching to a tool that can toggle disabled state. Even that may not be sufficient if FB apps use a common shared service. I have no experience with FBL or similar services. When social media is a must I only use web tools in well insulated environments.

---------- Post added at 12:26 PM ---------- Previous post was at 12:22 PM ----------

Highlights the risks of exposing behind the curtain details that some interpret as a call to action. :rolleyes:
[BetterBatteryStats] iamnotkurtcobain:
Why is Runtastic waking my system up for 26 minutes? Didn't use it today.
[BetterBatteryStats] kemdroid:
Ask the developers. Block the wake lock and hibernate it.
[BetterBatteryStats] DB126:
There is no reason to "block the wake lock". Hibernation will accomplish that same thing without potential side effects.
[BetterBatteryStats] kemdroid:
Even better for him.
[BetterBatteryStats] iamnotkurtcobain:
Hibernation? How?
[BetterBatteryStats] kemdroid:
Greenify. Works great with magisk
[BetterBatteryStats] yochananmarqos:
I haven't had any issue with Join, however others like yourself have. Try the new beta, the developer has been working on it. See this G+ post.
[BetterBatteryStats] lazostat:
So I must share the log file here or just take screenshots on my alarms? Just to check if there is a problem or not.
[BetterBatteryStats] strongst:
The complete dump file please according to the information in op. Other it's hard to get a whole picture what's going on.
[BetterBatteryStats] Donkarz:
Since I installed the xposed framework betterbatterystats is not working anymore. Do I need to change anything?
[BetterBatteryStats] RASTAVIPER:
As a standard procedure no.

I had never any issues with my last 3 devices with BBS and Xposed.

Unleashed by my rooted OP3T on 8.0
[BetterBatteryStats] flyingtiger:
Thanks in advance to everyone for this amazing resource and committing your time!

I have been experiencing pretty bad standby time with my new Galaxy S9, and am trying to pinpoint the cause. It seems like my battery is just draining straight away during the day, whether or not I actually use the phone doesn't even change the trajectory of the battery graph, it's just a nosedive down.

Also, my situation is a bit specific because my daytime and nighttime setups are totally different - I work next to an airport, so I'm stuck with awful cell coverage and no wifi, but at night/home I have great signal and wifi. So I have included two idle logs, one marked Daytime and one marked Night, to show the difference.

Could you gurus weigh in on these logs? I would really appreciate it, as I really like the handset, just can't believe that battery life is worse than my previous one of almost 3 years (Moto X Pure unlocked). Thank you!
[BetterBatteryStats] Donkarz:
Ich changed back to magisk and it works again :)
[BetterBatteryStats] strongst:
For the dump file with the poor signal the following 2 apps causing wakelocks/alarms:

com.samsung.android.app.aodservice (*api*)

Google quick search box

For rom comparison: Samsung roms are very overloaded with apps and services by default. Your moto rom is far better, even on stock. My gf has the s8 and its battery won't survive half the time my op5 does... Hardware comparison will be not really possible ;)

For the good signal dump there's only the Google quick search box, nothing other to complain about as far as I see.
[BetterBatteryStats] TNSMANI:
As you yourself say, your major issue is the bad mobile signal at work. If you are on 4G/LTE, switch to 3G and if you are on 3G, switch to 2G while at work. Other than switching the service provider, there is little else you can do.
[BetterBatteryStats] m0han:
quick post to say changing provider (via mobile number portability scheme) has reduced my idle drain over a 6 to 7 hour period from 1.1% to 0.3%. of course, i'd need to test at my various regular locations. i'll be sharing dumps for more help from the fine folks here. thanks a lot.
[BetterBatteryStats] IanHodgson:
Can anyone advise me how to stop the really bad battery stats shown on attached screenshots (some from settings, better battery stats and also warlock detector). It looks to me like WhatsApp is keeping the CPU awake but I don't quite understand the numbers. I know enough to see that about 50% battery drain for less than an hour screen on time is really bad (it has only just started hastening). I'm on PE Oreo 8.1 on midi phone.

Thanks.

Ian
[BetterBatteryStats] drozo8o8:
At what percentage would you consider a wakelock draining, 3% ?
[BetterBatteryStats] DB126:
Insufficient information to make a determination. You will need to perform an idle sleep study (no active use) to identify the culprit(s). See first few posts in thread for details. That said, WhatsApp is a likely (albeit unproven) contributor to accelerated drain.

---------- Post added at 12:30 PM ---------- Previous post was at 12:14 PM ----------

Wakelocks do not drain. In fact most are benign. What actions are taken, if any, in response to the WL determines if a "draining" event occurs. Identifying root cause is the key to power management. An idle study is the best way to ferret out 'bad actors'. Setting arbitrary thresholds to arbitrary events will likely lead to unproductive and irrelevant actions with undesirable side effects.
[BetterBatteryStats] pantezuma:
Me.

Just tried to export and it's a no go.

BBS won't ask for sdcard permission.

I have latest version from Play Store installed.

This feature is really useful to me.
[BetterBatteryStats] nocturnoz:
Hi there!

I've got 40% awaketime while screen off.

Would be awesome if someone could take a look at it! :(
[BetterBatteryStats] strongst:
Seems you didn't post any log or forgot to attach it ;)

Edit: I'm too fast :silly: can you please set at least reference points so there will be no screen on time within the log or just unplug your phone without activating the screen and let it idle for 6+ hours to record the idle drain?
[BetterBatteryStats] nocturnoz:
I changed the logfile... You spotted it right after i deleted the old one :silly:

Yep, I'll deliver it tomorrow. Thanks in advance! :D
[BetterBatteryStats] TNSMANI:
Your mobile signal and wifi were the biggest culprits.

For the rest, we will await the fresh dump.
[BetterBatteryStats] Steajano:
Now i no what is keeping my phone awake when screen off how do i stop wakelocks?
[BetterBatteryStats] DB126:
Welcome to XDA. Always best to do a search before posting: https://xdaforums.com/showpost.php?p=76246960&postcount=34086
[BetterBatteryStats] Steajano:
Thanks for the reply. I did have a search but i couldn't find anything exsplaining how to stop/ignore/remove wakelocks? Sorry im new lol
[BetterBatteryStats] Steajano:
Now i have found what wakelocks are causeing my battery drain how do i stop them?
[BetterBatteryStats] DB126:
No need for multiple posts.

Prepare and submit an idle (screen off) study as outlined in the first few posts (or here) of this thread to properly identify root cause of supposed drain.

Alarms and wakelocks are not evil in isolation and typically are a symptom if a larger problem that will still persist after blocking the supposed culprits.

See here for a recent example of a typical misdiagnosis and actions that made things worse.
[BetterBatteryStats] lukaszsas12:
can anyone help?? I am looking for and I can not find anything about ts_wake_lock very much because I have no ideas anymore

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] strongst:
If you're using a custom kernel try to change it since the wakelock is kernel related.
[BetterBatteryStats] lukaszsas12:
I have the original soft, I have not changed anything

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] strongst:
Please, then please provide a full dump file according to op cause your screenshot gives not much details.
[BetterBatteryStats] lukaszsas12:
https://drive.google.com/file/d/1EUei8vr1FI-0BzuJ8m5ciO1P4DnXkh27/view?usp=drivesdk

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] strongst:
Nope, please read the section in op beginning with "Before posting a dump...."

I said it already ;) and also this dump file is not really useful. Thanks for understanding!
[BetterBatteryStats] lukaszsas12:
Now better? https://drive.google.com/file/d/1zmQK1kzTAqCjeouSlgS-0NDQEmiimNJH/view?usp=drivesdk

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] strongst:
Yeah, it's better. I guess it's something related to your wifi. You can try to repeat the same with wifi disabled.

Maybe someone other has ideas?
[BetterBatteryStats] DB126:
According to log average hourly idle drain rate was 0.4%/hr which is fantastic. Wakelocks without adverse consequence are not evil and do not need to be sourced or managed. Ignore was is not detrimental and enjoy your device.
[BetterBatteryStats] strongst:
You're right, the drain is very good(less) but he just wants to know what's that wakelock, he doesn't complain about battery life or drain at all ;) and that wakelock isn't normal at all...
[BetterBatteryStats] Wh1t3Rose:
I pretty sure it's a WiFi wakelock. I have the same on my Huawei Mate SE. I have it because I am using my WiFi Hotspot. Wakelock stopped as soon as I turned my Hotspot off.

He might want to make sure he didn't leave his Hotspot on or it could be a rogue device on his network.
[BetterBatteryStats] strongst:
Good to know, I already told him to turn off wifi and see if the wakelock is gone cause I'm thinking the same too! It's been also active for that time...
[BetterBatteryStats] lukaszsas12:
ok check but in the course I had used 4g and is still active this process

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] Wh1t3Rose:
Make sure your didn't leave your WiFi Hotspot on.
[BetterBatteryStats] lukaszsas12:
I had turned off the wifi and after every refreshing bbs the counter is growing

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] DB126:
Acknowledged. That said, such wakelocks are only if interest because a tool (eg: BBS) exposes them. "Normal" is both subjective and relative to some undefined baseline. I have seen devices that log tens of thousands of wakelocks per hour yet exhibit no adverse behaviors nor change any metric of concern when the wakelock is vanquished. If one wants to chase random anomalies a logcat is a great place to start. Usually hundreds of largely unexplained entries that do no harm.

As you said, it is probably related to WiFi communications and likely the result of a poorly coded, unsatisfied conditional in the kernel. Disabling the trigger may reduce the wakelock count which seems to be the attribute of concern. Moving on unless there is something more that needs to be addressed.
[BetterBatteryStats] lukaszsas12:
then the same ts_wakelock at the top of the internet switched off

https://drive.google.com/file/d/1GlAcZ_h2GbCqPJIpfSaF_f4cbQhgCk_v/view?usp=drivesdk

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] strongst:
It has really no impact on the battery as you can see. You didn't loose any percentage while deep sleep. God knows what wakelock it is, maybe you can ask on your device forum. I didn't found anything useful to explain this.
[BetterBatteryStats] lukaszsas12:
maybe someone else has an idea? for a short time I did not lose a percentage, which does not change the fact that this wakelock is bothering me

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] strongst:
As [MENTION=5488402]Davey126[/MENTION] already said: wakelocks are common and present. If you can't break your battery drain down to this wakelock you're bothering with, it's not the wakelock that drains your battery. And as we can see the wakelock doesn't drain your battery: don't care about:D

But i dig something deeper and found a code snippet that includes your ts_wake_lock.

It seems to be part of a touch panel driver!

https://github.com/twicejr/HUAWEI-P...er/include/linux/hisi/hisi_fpga_touchscreen.h

Line 570

Do you have some screen gestures activated during screen off?
[BetterBatteryStats] lukaszsas12:
I do not have any gestures on.

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] iamnotkurtcobain:
Is this normal? (Logd so high)
[BetterBatteryStats] Wh1t3Rose:
I have a theory. Could this be caused by a custom Rom not having proper drivers for the fingerprint sensor? Or at least badly coded drivers? Maybe the sensor is always active Especially while screen is off.

Huawei doesn't provide stock images or source code for some of their devices including my Mate SE which by some miracle is running Linage OS right now. So there's no telling what hacks are needed to get drivers working.
[BetterBatteryStats] strongst:
Not in his case. He has stock rom at all. It's not the fp sensor, it's the Touchscreen driver.
[BetterBatteryStats] donatinho:
Hello everyone. Surely it has already been asked, but I couldn't find a proper reply (again, surely my bad). I installed BBS XDA edition, but can't make it run since my phone is unrooted atm (Huawei P20 Pro), and adb command always fails. the error i get is Bad argument: java.lang.IllegalArgumentException: Unknown package: com.asksven.betterbatterystats

Of course adb works correctly, no issue between pc and phone. Any hint? thanks in advance.
[BetterBatteryStats] pedritopl:
The XDA edition of the app has a different package name. Add _xdaedition at the end of the package name.

And yes - you could have just Googled it...
[BetterBatteryStats] donatinho:
Yes, i agree; sorry for that.
[BetterBatteryStats] yochananmarqos:
[MENTION=1330150]chamonix[/MENTION]

Should we continue using the original HockeyApp or the new Microsoft release?
[BetterBatteryStats] lukaszsas12:
can not I do anything about it ??

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] strongst:
Please read the last 2 pages again. We did figure it out(according to your dumps/input) what that wakelock is(that was your initial question) and we figured out that you have an awesome idle drain of 0.4%! with that wakelock you're bothering with.

Again: this wakelock has no effect on your battery life.
[BetterBatteryStats] lukaszsas12:
And is this result good? deep sleep only 66% should not be more ?? 18% on 500mhz as if he wanted to sleep and did not let him

Wysłane z mojego BLA-L29 przy użyciu Tapatalka
[BetterBatteryStats] DB126:
Not unusual. Android devices often idle efficiently at low CPU frequencies without entering "deep sleep". Good chance the screen was on during some of that time but you were not directly interacting with the device (eg: reading vs tapping).

Please stop fussing over raw data presented out of context. Let it go.
[BetterBatteryStats] TNSMANI:
Of the total 15 hrs covered by the dump, for nearly 5 hrs the screen was on ie you were using the phone. Then how can the deep sleep be more? Don't worry unnecessarily when you have excellent results.
[BetterBatteryStats] Harrygsr:
Hi guys. I come here pleading for advice as I'm at my wits end. I have a HTC 10 firmware 2.41.401.41 and recently a kernel wakelock has appeared and I can't get rid of it. It's called ohio_wake_lock. It's keeping the phone awake 100%. The phone will doze but not deep sleep. It first appeared when I was running project fusion rom then lineageos, RR and also stock HTC os. The wakelock shows up in bbs but not amplify so I can't block it. Have you ever heard of this wakelock or can you give me any advice please and thank you.
[BetterBatteryStats] DB126:
Submit an idle sleep study per guidance in OP (first few posts in this thread) or here. Need a better understanding of what is happening to make relevant suggestions.
[BetterBatteryStats] Harrygsr:
Thanks for your reply. I'll do that. Just reverted back to an older firmware and going to take an ota and reflash twrp and root to see if it makes any difference. If it doesn't make any difference I'll submit the idle sleep study. If it solves the issue I'll let you know aswell. Thanks again for getting back to me :good:
[BetterBatteryStats] PeterImmel:
Hallo together.

For some weeks now my battery is so bad. Like before I lost 5% over night, it is about 40% now. I also clean flashed LineageOS again and only installed some apps fresh from play store. Still the same. Can someone please help me out? I have the feeling that my battery got physically worse perhaps. Its 2,5 years old now.

Here the log:

http://txt.do/dfrlp
[BetterBatteryStats] strongst:
No wakelocks at all that would explain that behavior, but the file is cut off. The lines with cpu frequencies are missing. Can you please attach the dump file here directly?
[BetterBatteryStats] TNSMANI:
Your mobile signal is patchy and that could be one of the reasons for the drain. As stated by strongst, the dump is not complete, it doesn't contain alarm stats too.

You may have to do a fresh dump after clearing data and cache in BBS or even uninstalling and reinstalling it.
[BetterBatteryStats] PeterImmel:
Here it is

https://www.file-upload.net/download-13105951/BetterBatteryStats-2018-04-30_075033761.txt.html
[BetterBatteryStats] ssjkakaroto:
Hello, can someone help me figure out what's wrong with my phone?

For a while now it can't enter deep sleep mode because of mmc2_detect kernel wakelock. I've read that it could be related to a faulty external SD card, so I reformatted and ran h2testw on it, but there were no errors at all.

Could it be related to the phone's internal memory?

Thanks for any help.
[BetterBatteryStats] DB126:
Download site lacks integrity; won't touch it.
[BetterBatteryStats] PeterImmel:
Sorry, I don't get you.... :silly:
[BetterBatteryStats] DB126:
No evidence mmc2_detect wakelock is root cause. Me thinks the ambient light sensor (possibly aggravated by telegram app) is the culprit. Try disabling auto brightness.
[BetterBatteryStats] ssjkakaroto:
Thanks, I'll try it.

Don't you think those thousands of counts for mmc2_detect could be triggering suspend_backoff and preventing the deep sleep?
[BetterBatteryStats] DB126:
Could...but probably not.
[BetterBatteryStats] ssjkakaroto:
[MENTION=5488402]Davey126[/MENTION] I think you hit the nail with that one. I had Telegram's Auto Night Mode turned on. As soon as I turned it off my phone was able to go into deep sleep again.

I'll do another idle sleep test tonight to make sure, but thanks for your help!
[BetterBatteryStats] strongst:
There's no real problem that's recorded by bbs hence it can be the battery itself, like you mentioned. Testing can be done with an usb charging meter to see how many capacity is loaded during recharge.
[BetterBatteryStats] chrisclaytonnz:
Hi,

I've got an ASUS 3S 10 tablet. I've got zero deep sleep for some reason. I'm not rooted but have used ADB commands to enable features of better battery stats.

I can tell that I have no deep sleep and the culprit apprars to be Google Services.

I have a wakelock for MPL Significant motion but can't work out what could be causing this wakelock as tablet is idle 22 hours per day.

I've linked dump file for last 24 hours if someone could look and let me know? I'd appreciate any help.

http://pasted.co/f329dbfa

I've searched in this thread and Google and there are very few and not relevant comments.

Chris.
[BetterBatteryStats] DB126:
Dump contains 66+ min of 'screen-on' time so no useful for idle analysis. You'll need to redo the study minimizing screen-on time (<1 min). See here for suggested procedure or follow guidance in the first few posts of this thread.

Google Play Services probably isn't the culprit. More likely performing functions on behalf of another app. That said, it's always best to flush Google Play Services storage from app->settings followed by an immediate reboot to reduce the chance of internal corruption being a contributor.
[BetterBatteryStats] TNSMANI:
What he means is that the site where you uploaded the dump is not a reliable one and downloading from there is risky. So he won't attempt it.

While I tried to access the dump file, I got a blank page. So Davey's observation seems to be right.