yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] DB126:
Stand up - I'm just an untrimmed slob with an opinion like most everyone else around here.

Outside special circumstances you don't need I/O or lnet tweaks on a modern device with the usual trimmings. Yes, each can demonstrate a numerical "benefit" under the right conditions. Switch to a less favorable environment and results follow.

Pull the lens back and all the knob turning might buy you a small (fractional) improvement when objectively measured. Kinda like what happens to the earth when you jump. That said, one can't discount the placebo effect of rocking a highly tuned gizmo. Everybody has a fish story. I love to tell mine around the holiday dinner table. Wide eyed kiddies suck up every word and beg for more.

Then I wake up ...

As for L Speed, look for scheduled or reoccurring tasks. Govtuner, boost (ugh!), cleaner and trim come to mind. Flip 'em off or use a less aggressive schedule.

Stepping away from the table after a nice (albeit short) visit. There's good work going on here. Enjoy the thread. :)
[BetterBatteryStats] mrjuniork:
[MENTION=5488402]Davey126[/MENTION]

I've been following this thread for a while now, learning from people like you, [MENTION=4138220]fossils-n-dents[/MENTION] (where the heck is he?) and many other smart folks.

I tried a lot... Amplify, ForceDoze, Wakeblock etc....

You should have seen my last amplify set up, blocked dozens of alarms, services and wakeblocks, according to many opinions out there....I always managed to keep the device running, but so often I encountered delayed push notifications of several apps.

Also I noticed, that blocking wakelocks, like you've mentioned so often, backfired and created even more needs of all those wakelocks to communicate constantly with play services and the operating system itself.

I've come to my conclusion, that amplify doesn't fit for me.

I deactivated and deleted it, then I switched over to Greenify, greenified the crap out of my device (especially the gcm push is amazing) and I'm so happy with the results. Greenify is amazing but most importantly, through trial and error I have come to have my perfect set-up.

In short: android is beautiful in its complexity and it is simply amazing to discover the depths of said complexity, craving for a deeper understanding of the underlying processes and behaviors.

Thank you for your highly appreciated input. I'm not bowing but I sure as s *** take my hat off for you :good:
[BetterBatteryStats] Nightshadow931:
How do I get BBS to work with LG(v20)?

Alarms shows nothing and kernel wakelocks shows only 1 thing..

I've installed it as a system app, but that doesn't help..
[BetterBatteryStats] patrickdrd:
have you tried the use api in the settings?
[BetterBatteryStats] kovacszj:
Hi,

I've created a new dump file with 17s sot, hopefully, this could help to find culprits.

Thanks in advance for the help.
[BetterBatteryStats] mrjuniork:
I'm not really the man for this and I haven't got much time, so I'm gonna give you my five cents..

From what I can see, you have installed a lot of apps, which means that most of them are constantly communicating with the operating system (Google play services e.g.).

I can't identify a main culprit that drains an immense amount of battery. 1.2% over a period of almost 10 hours isn't really that bad. Between 0.5 - 1.0%/hour is usually a normality (or something to reach for), except the individuals that go for the "0.0%/h" peak of the mountain.

Since GPS (Google play services) used 1MB of network, there were a lot of apps communicating with it, which again drains your battery and keeps the V20 from having less screen off activity.

- airbnb, Google+, hangouts, booking.com, yandex, momondo... To name only a few, do you need all of them?

You gotta ask yourself what is necessary and what is not. The more you put on your device, the more you have to expect a drain of battery. The apps you don't need, could be deactivated, so they can't intervene anymore.

Also it seems that your exchange accounts (emails etc.) seem to constantly wakeup the OS in order to get a hold of the email and account content.

Try to deactivate the push and it change to a scheduled or manual email fetching. Since I scheduled my email fetching to like once or twice an hour, battery life has really improved and I still don't miss important emails ;)

Your Health app seems to constantly wait for an activity in order to count your steps. Though the device is untouched (hopefully) the sensor itself was activated throughout the whole period. Motion detector was also for almost 2 hours active and sending wake-ups towards the OS.

Are you observing and tracking your sleep pattern?

So finally, I can really recommend Greenify for hibernating most of your apps and if you buy the donation package, you could also still receive notifications for apps that are using GCM services. For starters you could clear out your not needed apps, and also kill all the background processes and then create another dump.

Since you are already running a custom kernel, there is all good on this end of the road...

(if anyone doesn't agree or has anything to add, pls don't hesitate, I'd be really glad if I got approach of looking at this)
[BetterBatteryStats] kovacszj:
Thanks a lot for the answer. I absolutely agree, my main problem is that I have a lot of apps, so I have to figure it out which of them I don't need at all.

I already use greenify, greenified almost every app. Right now I'm worried about the motion detector. However, I greenified LG Health app a couple of days ago, but I haven't noticed a significant improvement in battery drain, so I degreenified it. The other culprit with motion sensor probably is the alarm clock app I installed, but I don't use its sleep tracking part, maybe greenifiying could help.

I think I would start with deleting unnecessary apps, as you advised, and try to reduce motion sensor activity greenifiying the alarm clock app.

Hopefully, that would improve a bit my battery idle drain.

Thanks again for your help. Also, if anybody has another and better idea, don't hesitate to share with me :)
[BetterBatteryStats] Nightshadow931:
Yea, it helps..but not fully.

Alarms shows a bunch of 'android' alarms, without any information when you tap on it(it just shows 'android Wakeups 22(3.7/h)'
[BetterBatteryStats] DB126:
Well done. :)
[BetterBatteryStats] Ghan04:
Hi all,

I've been pulling my hair out trying to figure out why my device has abnormal battery drain. BBS has helped me get some good information, so thanks for the app! However, I'm still struggling to fix the problem.

OnePlus 5

LineageOS 14.1

I've been able to find out from BBS that the device never enters deep sleep. Never. It will do so for a while if I reboot it, but then at some point, it stops ever going back to deep sleep. I did a 6.5 hour run on battery overnight to get a clean dump file (which I can't seem to attach or link since my account is new): pastebin.com / SpSCVmuU

There don't seem to be any significant wakelocks, so I'm at a complete loss as to what the issue is. Can anyone else glean some information that my untrained eye may have missed?
[BetterBatteryStats] mrjuniork:
First off, you should fully charge your battery and then get your idle run over night. But before that I really recommend for you to flash a custom kernel in order to get in charge of those many Kernel Wakelocks. You've got a rooted OP5, so use TWRP for flashing a kernel of your choice (I recommend blu spark).

After that come back and post another dump, so we can continue our draining analysis :)
[BetterBatteryStats] freezindevil:
Apologies if this feature already exists or has already been requested, I have tried but can't seem to find it on this thread or the app.

For devices with big.LITTLE core configurations, the CPU States module of BBS only reports either the state of the LITTLE cores, or core 0 (unsure which is the case). Is there a way for to see what BIG cores are clocked at instead, or select an arbitrary core (e.g. 2 on quadcore SOCs or 4 on octacore SOCs) to view?
[BetterBatteryStats] Khotu:
Does someone has *job.delay* alarm in system? I still doesn't know what is it. I've disabled all cloud backup etc but ita still the highest wakelock:(

Also I still fight with 4-0048 kernel wakelock. What is it for?
[BetterBatteryStats] TNSMANI:
Kernel wakelocks seem to be a big issue. Try a different kernel and post a new dump.

Apart from that, most of your wakelocks have the same time which is not how it should be. Clear the data and cache of BBS and take a new dump.

Also, the screen on time should be as less as possible, preferably under a minute.
[BetterBatteryStats] mrjuniork:
[MENTION=8788593]Lou_Ford[/MENTION]

And pls post the txt file or the link for the dump, coz is really too much scrolling going on here ;)
[BetterBatteryStats] Ghan04:
Interesting. I didn't even know you could replace just the kernel. I had a look at Blu Spark, but it looks like it is only supported for the OxygenOS ROM, so I ended up with ElementalX for LineageOS. The new kernel doesn't seem to have helped any.

I got a battery dump from 97% to 68% this time, again around 6.5 hours in which it did not enter deep sleep at all:

pastebin.com / xDMvKXiH

I'm still quite puzzled at what's going on here. I've checked that all apps (except Google Play Services) are "optimized" so they should be dozing. I have noticed the ipc0000014e_PowerManagerSer wakelock appear a number of times, but while its time is significant, it's nowhere near 6 hours.

Appreciate the help!
[BetterBatteryStats] TNSMANI:
Wakelocks: Twitter (control it)

Alarms: wifi was on the entire time of the dump, try setting it to "never" during sleep, reset your wifi, check that scanning is off in Location and under Wifi; mobile connectivity related alarms, try switching data off

Wifi: Data download Google Services 2 MB, wifi 1 MB (these would have skewed the readings)

Apart from these, there is high cpu usage. There may be a rogue app or some processes might be stuck.

Sensors were also part of the problem, Proximity sensor was working for more than an hour and Significant Motion Detector sensor was working for more than half an hour.

Kernel change did not seem to have helped. Change again.

May be a clean flash of the ROM with a different kernel might help.
[BetterBatteryStats] Ghan04:
So I've tried a few things today.

- Uninstalling Twitter doesn't allow the phone to enter deep sleep.

- Setting the wifi to never connect while the screen is off, disabling wifi entirely, and even putting the phone into airplane mode don't allow it to enter deep sleep.

- I rebooted the phone after those tests and started watching the behavior as I would open an app. I would launch something, then reset BBS and check it a bit later to see if any deep sleep time was accumulating. I opened every app I use on a regular basis and none of them triggered the phone to stop entering deep sleep. The problem didn't reoccur until almost exactly 5 hours of uptime since the last reboot. I'm not sure if that has any significance.

How can I control the sensors on the device? I don't see anything for disabling the proximity sensor other than the setting to prevent accidental wake-up (which is off and has been off). Do I need a different ROM to control these settings?

At this point I'm not sure that a different kernel is going to help unless it just blocks/disables all wakelocks or something. I'd like to find out the root of the problem, but I don't really have any solid evidence to point me in the right direction at the moment. I'm thinking about flashing back to OxygenOS - I don't recall having the issue until I switched to Lineage.
[BetterBatteryStats] PokemonTotalWar:
For some reason, my BBS doesn't seem to be running in the background to collect stats, or something. Every time I launch it it gives me NO information, seemingly setting the reference point at that moment
[BetterBatteryStats] TNSMANI:
I didn't say that Twitter was preventing the phone from deep sleep. I mentioned Twitter only as a drainer and hence advised you to control it.

You mean after 5 hours the phone stopped entering deep sleep?

Sensors can not be controlled directly. But we can alter the settings of the app which uses a particular sensor. You have that info in BBS. Try altering the settings of such apps and see whether sensors behave. Do not touch sensors connected to Doze.

Kernel is still my favourite for your issues. That AND a clean flash. If you are not keen on a different kernel, try atleast a clean flash before moving on to another ROM.
[BetterBatteryStats] jrbmed08:
Hi guys, trying to troubleshoot some idle drain on my new Xperia XZ1 compact. Previously I noted especially high idle drain (like 3%/hr) with bluetooth on and my pebble connected. Since then I've done a factory reset and reflashed my firmware. Currently bluetooth is off and I haven't paired my pebble or configured the pebble app. I wanted to get an idea of how much it drains without bluetooth.

I can see there are a lot of kernel wakelocks. I'm hoping they can be traced to an app or something that I can do something about. Unfortunately I can't really root this device, and there are no custom kernels or ROMs available anyway.

I'm on stock 8.0 and using ForceDoze, but still have 1%/hr idle drain. Can anyone help me interpret this dump file? Thanks in advance.

Edit: Also I used unplugged to current because my phone does not show options for screen off to screen on. So instead of running down to 95% and selecting screen off/on, I unplugged it at 100%, didn't touch it for 6 hours, and used unplugged/current. Best I could do given the options.

This is the stat that really sticks out to me; any reason why android is causing so many alarms?

android (*api*): Wakeups: 4163 (41.4 / h)
[BetterBatteryStats] temo_O:
Hello,

Can anyone help with dump file? To discover why my Exynos Galaxy S8 drains the battery? Im running latest stock firmware. No root, no custom kernels or roms.

https://drive.google.com/open?id=1i1Hvxkv9AYc-mboOBeffPrVyvNX1ICQK

Thank you
[BetterBatteryStats] peterlee928:
for a proper idle dump:

1) screen on time needs to be less than 1 minute.

2) screen off to screen on (yours is unplugged to current).
[BetterBatteryStats] temo_O:
so i have to charge it to max again. wait screen off until 95 and then rest for 6 hours?

but what should i do in the app exactly? i have only screen off in drop down menu.
[BetterBatteryStats] TNSMANI:
For Unplugged to Current, you need to charge it to 100%, unplug and leave it idle for 6+ hours. Screen On to Screen Off is also ok.

In the app, you simply click the share button and save the dump for Unplugged to Current or Screen Off to Screen On, whichever you get.

The main thing is the screen on time should be less than a minute and the dump should be for 6+ hours.
[BetterBatteryStats] temo_O:
My dunp was unplugged to current but i was told its not ok
[BetterBatteryStats] EvilMegaDroid:
There's an xposed module to disable sensors but I'm sure that will not help much. Only if you have a bad kernel or sensor which keeps it active. Try it and see. Sensor Disabler on xposed modules.
[BetterBatteryStats] jrbmed08:
After reading some of this thread, I think it's OK as long as you don't use your phone. Take it off the charger, don't touch it for 6+ hours, and record the dump from 100% down to whatever it is after 6 hours with unplugged to current. As long as you have less than 1 min of SOT, it should be OK. That's what I did at least, because the spinners on my app don't have options for screen off/screen on.
[BetterBatteryStats] chamonix:
Can you guys please give me feedback on the latest build from hockeyapp (2.3-149) running on a rooted phone? I have made some changes in the root access and can not test as I have no rooted phone at hands: either the change broke something or everything still works the same.
[BetterBatteryStats] TNSMANI:
It was not ok because the screen on time before the dump was more than 18 minutes whereas it should be less than one minute.
[BetterBatteryStats] yochananmarqos:
BBS is being granted su rights, however nothing is loading at all. Tested on my 6P and 5X (see sig).

EDIT: Nevermind, it's working fine now on both devices.
[BetterBatteryStats] temo_O:
new dump: from 100% to 84% in 4 hours and 38 minutes.

https://drive.google.com/open?id=1_6EY_OvSQeMJJy1uXc-5zPNzIYg1qwO5
[BetterBatteryStats] TNSMANI:
It is still not ok because the dump file is for 1 hour and 20 minutes despite your saying that it is for 4 hours and 38 minutes (should be for 6+ hours).

Are you not able to get stats without invoking API in the app's Settings?

Though your wifi is shown as "Running", mobile data was used. Did you switch off the modem? Change wifi settings to run "Never" while sleeping or "only while charging".

And post another proper dump.
[BetterBatteryStats] chamonix:
Next 2.3 build has full alarm info on non-rooted devices!
[BetterBatteryStats] chamonix:
Happy holidays everyone!
[BetterBatteryStats] kaLuta:
U probably have a button that is always pressed, that was my problem. When i fixed the button everything was fine.
[BetterBatteryStats] chamonix:
Build 2.3-152 is up with full alarm support on unrooted devices, enjoy! If this build has no issues it will probably go to gplay this week, starting with beta.
[BetterBatteryStats] j1gga84:
Many thanks, where can we find v 2.3?

Regards

Sent from my SM-G900F with Tapatalk
[BetterBatteryStats] fhem:
rooted Pixel 2xl --- 2.3-149 working great. 2.3-152 not working w/ root. see attached below.

Thanks much for your continued hard work and support.

Merry Christmas and Happy Holidays to all.
[BetterBatteryStats] yochananmarqos:
The information about beta testing is in the OP.

Yep, same here using Magisk 14.0. I added the READ_PACKAGE_STATS permission with my Privileged Permission Whitelist module with the same result.
[BetterBatteryStats] fhem:
I'm actually using Magisk 14.6 and I didn't add any modules.
[BetterBatteryStats] taxi92111:
which button was urs? is there a way to narrow it down? I removed the volume button's connection off the motherboard but the problem still exits so I am assuming it is not volume button. I might have to try with power button.
[BetterBatteryStats] chamonix:
Thanks! Typo found and fixed, re-building and uploading in a few

Update: building

Update: uploaded to hockeyapp
[BetterBatteryStats] RASTAVIPER:
Do we have to register at hockeyapp for getting the beta?

Unleashed by my rooted OP3T in 8.0
[BetterBatteryStats] yochananmarqos:
Yes.
[BetterBatteryStats] chamonix:
Unfortunately yes. There are some changes going on at hockeyapp and I hope this will change but for now registration is required. If you don't want to register you can still download the binaries for selected betas and final builds from post #2.
[BetterBatteryStats] mesqueje:
Hi. My phone is samsung j5 2016, and my rom stock nougat. Because so much battery consumption? Thank yo.

es.tinypic.com/r/30mv31x/9

es.tinypic.com/r/24gu1hz/9

es.tinypic.com/r/zk5ws3/9
[BetterBatteryStats] hypern0va:
Can anyone help with this please?
[BetterBatteryStats] githyanki:
I would try the latest beta, it addressed a lot of these issues.
[BetterBatteryStats] deitrich:
Hey! where I can find information about the doze mode

I use android 7.0

Wysłane z mojego SM-A510F przy użyciu Tapatalka
[BetterBatteryStats] yochananmarqos:
The Alarms are not calculating correctly in the newest build, see the attached screenshots. The one with lower numbers is using the API method and seems to be accurate as it agrees with Wakelok Detector.
[BetterBatteryStats] murti52:
I am still facing "no stats have been collected yet" in the latest beta from hockeyapp. I have tried, both the normal and the forced method, but it's still not showing.

One Plus One, 7.1.2. (Neon kernel)

any log required? If yes then which one dumpfile, logcat or dmesg?

Thanks for the help.
[BetterBatteryStats] Tendor83:
Hi guys. I have a new and steady partial wakelock on my oneplus 5, called DdsCardSelectionController.

I have only and in this thread too, but no relevant information was shown. It seems as if this process in not raising any problems to anyone, except me.

Cold you please help me out with this issue?
[BetterBatteryStats] Gesuino:
I have this one too, with Imssenderrxr: the first one appeared even on Nougat but it went away after a clear cache and data; the second one appeared on Oneplus 5 Oreo Official and it seems to be related only to movement or light doze.

The solution for the second one (disabling com.qualcomm.qti.ims 1.0 and org.codeaurora.ims 1.0) didn't worked.
[BetterBatteryStats] chamonix:
Can you please confirm after a reboot. Switching modes in the middle of a run may cause things not adding up properly due to naming differences between both sources
[BetterBatteryStats] yochananmarqos:
Yep, rebooting did the trick. It's reporting Alarms properly without forcing the API method.
[BetterBatteryStats] temo_O:
I guess this one is proper.

https://drive.google.com/open?id=1Us0C8-luZCDCU28z8Y4LV70MeX6Cv7O8
[BetterBatteryStats] Icetea:
for normal users the last version of BBS is nearly one year ago! When we will get a newer version here or at the market?
[BetterBatteryStats] githyanki:
Join the beta channel if you want new shiny things.

---------- Post added at 05:01 PM ---------- Previous post was at 04:54 PM ----------

Samsung DeX home and parallel space seem to be your biggest issues. Look through all of your apps and decide what you don't need, try Greenify to tame the rest while phone is off.

Hope that helps some.
[BetterBatteryStats] Icetea:
No, i have paid in store for it, and so I expect a new version in store also !

don’t want to be a beta tester or anything similar!

I think, one year should be enough to give again support to all other user too!

...otherwise i also will be able to live without that app.

see 3. of my signature!:D
[BetterBatteryStats] Watanabe_You:
The version here and in the Play Store is the same. Threatening to not use the app is not much of a threat either.
[BetterBatteryStats] yochananmarqos:
Please don't feed the troll. Let's not clutter the thread with pointless discussion.
[BetterBatteryStats] IronTechmonkey:
Even though questions like this are considered inappropriate in development forums I'm going to answer it seriously to address an underlying misconception.

It is a common misconception that because active development may not be visible there is some limitation to the app, but in many cases this actually represents a mature and stable app, especially in the case of BBS.

To that point, we've seen BBS grow from requiring extra steps on many systems, to installing without those steps across a wide range of OS variants, and other improvements. I've even seen it work fine after being restored via TiBU from a different device running a different version of Android.

Your purchase entitles you to nothing more than what the app was when you purchased it (which is still a good value) and you should be glad for any app that continues development after your purchase. If there is something particular you want to see in future development you could try making viable and productive suggestions.
[BetterBatteryStats] jrbmed08:
Does anyone know what the alarm snoozehelper.EVALUATE does and where it comes from? I have an obscene amount of wakeups from this. This screenshot is from a day of normal use, not an idle dump, but it gives you an idea of how ridiculous the numbers are. I am planning on posting an idle dump soon but could use any advice you guys have, since I've found next to nothing about it on a Google search.
[BetterBatteryStats] yochananmarqos:
Sounds like Android is having trouble dozing. Do you have Greenify's Agressive Doze enabled or have Naptime or Force Doze installed? If so, try disabling them.