yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] M@31:
Thanks so much for you guys' help!

I will try it with wifi off tonight...I actually didnt have my BW Toggles set up last night when I went to bed and when I woke up I had lost about 1% an hour......woke up with 92% battery left, just over 8 hours of sleep.

---------- Post added at 01:41 PM ---------- Previous post was at 01:29 PM ----------

I know Kakaotalk is bad for me.....it is an IM app, and the only one I use to communicate, so I kinda have to keep it.....

I just checked and usb debugging was on, so I switched it off.

I will reboot and take another reading tomorrow morning when I wake up.

You said to do it after plug/unplug....I am assuming you mean after a full charge back up?

Will do with CPU spy.....

Just confirm that I should do this over night (while I sleep) again so see whats happening?
[BetterBatteryStats] shinew:
has anyone figured out what "sec-battery-adc" under Kernel Wakelock is yet?

I've searched everywhere with no answer. I'm using Samsung Galaxy S II T989 on T-mobile and it is negligible under stock kernel(0.3% or so). But it take 32-35% Wakelock time in the Faux kernel ,and I heard that it's also in the Synergy kernel. Would really appreciate if someone could enlighten me on this.
[BetterBatteryStats] longfeng:
I do not see the need to charge fully 100% before testing. Feel free to run tests anytime as long as >20%.

You do not need to frequently reboot your phone. Rebooting needs 0.35A for my phone (excluding reading external SDcard) and itself is consuming battery.

Your consumption is normal. My usage rate is faster during the day given I don't play games or listen to music.
[BetterBatteryStats] sp8y:
Installed the latest release last night & I like the layout with the alarms on the main screen.

Not sure if it's just me but the stats don't refresh & update for example if I reboot then open up BBS whatever new stats are there don't update when I click refresh - even closing BBS then re-open & the stats still show the same values as before.

Have tried clearing BBS data & reinstalled but still the same - I'm running a MotoDefy on froyo 2.2.2.

Have gone back to previous version & all is good again.

Great app by the way it has helped me a lot & has narrowed down an issue I have with wifi.
[BetterBatteryStats] chamonix:
No need to charge, just plug/unplug usb to have a clean reference for 'since unplugged'.

Afaik Kakaotalk is proprietary but maybe it is possible to talk to the dev.

From what I read I guess the bottleneck will be the contact sync rather than the keep alive (like it is on whatsapp)
[BetterBatteryStats] chamonix:
Nvm, double submit
[BetterBatteryStats] cekerevac:
I want to know what can I do to reduce that kernel wakelocs? As you can see in the dump file, my phone was awake over one hour through the night...
[BetterBatteryStats] chamonix:
Google search shows quite a few hit on sec-battery. Could you please share more info?

Is that wakelock related to the charger or usb being connected?

What are the counts and time for that entry?

Does it occur when phone is asleep?

Does it occur when phone is awake?

From what I scanned and without having looked at the source that wakelock seems related to reading / calculating the battery info. That kind of functionality should not prevent the phone from sleeping or wake it up (that's why the counts and the questions if your phone sleeps at all are so important.

Sry for being picky but I need to remotely understand the whole context (or you send me you phone ;-))
[BetterBatteryStats] chamonix:
8

Could you please post a logcat where I could see the refresh?

I have changed something in that logic but it wasn't supposed to break anything so I want to avoid undoing blindly

Edit: I was able to reproduce, will debug later.

Good catch!
[BetterBatteryStats] sp8y:
Nice one thank you.

If you need any further logs give me a shout.

Sent from a MotoDefy.
[BetterBatteryStats] Macelangelo77:
Request

Hi Chamonix,

Thank your for BBS, definitely one of the most useful tools on my phone (HTC HD2).

I have one request: could you edit the thread title so it reflects the latest version number (if you release a stable version) and the date you updated it? That way I don't have to read through the thread to see if there's a new version.

Thanks in advance.

Sincerely,

Mac
[BetterBatteryStats] cekerevac:
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
[BetterBatteryStats] chamonix:
That IS a good idea indeed. I will and at the same time rename the thread a little. If you want to get in-between updates there is also twitter
[BetterBatteryStats] chamonix:
My question was aiming at finding out if you wanted to learn something and have already tried to understand what keeps your phone awake or if you are just interested in the results.

I understand it #2 so I will answer later once I am home
[BetterBatteryStats] chamonix:
Awake / screen on is pretty good but there is still potential.

There is a lot of location and sync activity going on.

Could you please take another reading after unplugging and leaving your phone unused for a while. This may filter out some things coming from you using the phone during this reading (we don't need to bother about these)
[BetterBatteryStats] :
1.6RC looks good, the UI is great. The only suggestion I'd have is the size of the headers for the drop down boxes (Stat and Ref points) could be a bit bigger, i.e. taller. Given the broad spectrum of devices, and their screen sizes, that use your app however, it's likely not critical.

Edit: Graphs working perfectly on CM9
[BetterBatteryStats] mariotme:
Cant agree more :D

its a bit pain to select them if you have big fingers :)

other than that everything is running great till now
[BetterBatteryStats] githyanki:
I enable it. Like I said, try it and see if it helps your phone sleep more.

BTW, don't use the shallow hibernation, it doesn't seem to work. My phone stayed awake all the time with it on.
[BetterBatteryStats] Javi22:
Hello... My battery is awful with Android 7.1.1 Dp1 in nexus 5x (for other users too). Not 3rd party apps causes it, as I use the same in other roms

Do you have any idea of the cause, according to these stats...?

Could be

wake:com.google.android.gms/.measurement.PackageMeasurementService

? But didn't find anything in Google about that

http://cloud.tapatalk.com/s/582c5b5ccf310/BetterBatteryStats-2016-11-16_141132083.txt
[BetterBatteryStats] loginsvarios:
My battery drains extremely high as the phone never goes deep sleep.

The weird thing is that it don't happens always, maybe only 50% of the times after reboot.

-Extra Info-

• Clean ROM with only some apps installed

• Tried with 2 different batteries, same results
[BetterBatteryStats] infatality:
Does this works fine on cm14.1? Don't seems to have kernel stats working. And root don't get detected.
[BetterBatteryStats] pancomido:
Not working on Redmi Note 3 Pro

Hi.

I cannot get this to work on my Xiaomi Redmi Note 3 Pro (kenzo, Snapdragon 650). MIUI 8 Global Beta, Android 6.0.1

It installs correctly, but when I open the app I just get a blank white screen and after a while the system asks me to wait or close the app as it is not responding.

With the latest versions (RC), after a while the blank screen goes away, a toast message says: "Fallback to boot" and I get the "Computing..." message. But it never goes beyond that.

Version 1.16 doesn't work either (black screen instead of white).

I tried to give the app all possible permissions too.

Thanks!

EDIT: Reflashing ROM fixed it.
[BetterBatteryStats] TNSMANI:
Please post an

idle

dump for us to help you. The screen on time should be less than one minute.

---------- Post added at 03:02 PM ---------- Previous post was at 02:55 PM ----------

You seem to have kernel issues. Search for custom kernels.

You also have a lot of alarms which can be limited with Amplify.

There was also a background download of about 36 MB by Google Play Store.
[BetterBatteryStats] Cobalt765:
I can't get RC 3 working properly on my Sgs II running CM 11 Kit Kat 4.4.2

Its not showing the summary, it says 'No stats have been collected yet' I'd there anything else I need to do?

Rc1 works fine.
[BetterBatteryStats] Oswald Boelcke:
Did you convert RC3 to a system app? (Settings => Advanced Settings at the very bottom).
[BetterBatteryStats] Cobalt765:
Yes, did that. Also became beta tester on gplay and used that version. Got summary working then alarms didn't. Not to worry I'll just use RC1.
[BetterBatteryStats] Portgas D. Ace:
That's not what beta testing is about. Beta testing means reporting issues with a proper log file so that developers can fix it.
[BetterBatteryStats] Cobalt765:
Yes that's true but I did a search and thought I read it read was recommended to use the beta test version.

Either way couldn't get the RC3 xda or the beta versions to work.
[BetterBatteryStats] woodman:
I think Portgas D. Ace has understood you can't make RC3 to work properly, he said you need to provide logs in addition to your description to help the developer.

Btw, I had the same problem of 'No stats have been collected yet' in the summary and other sections running Android 4.4.4 and I already provided logs HERE.
[BetterBatteryStats] code2:
Could you tell me why is power consumption my Galaxy Note 4 is so high?

How I read in this txt files, I mean how I can find out problem?

Thank you!

There is files:

http://mysharegadget.com/986239602

http://mysharegadget.com/851123848
[BetterBatteryStats] rohitdave:
Plz check my BBS Stats

Hi

Hope I have posted in the correct way. If not my apologies.

I have a dramatic battery fall of around 5% regularly

Kindly have a look at my stats.

Thanks
[BetterBatteryStats] TNSMANI:
Your dump is garbled. I don't think that you saved the correct file. Hit the 'share' button, choose 'dump file' and hit OK. Then you attach it here. I hope you know what is an idle dump because that is what is needed.

---------- Post added at 02:59 PM ---------- Previous post was at 02:54 PM ----------

You seem to have charged your phone before taking the dump. Plus it is better to take the 'unplugged' to 'current' dump than boot to current or any other.

So post a fresh idle dump.
[BetterBatteryStats] rohitdave:
OK will do thanks
[BetterBatteryStats] code2:
to: Chennai

I create the file again, please check it. Is it correct?

Many thx!
[BetterBatteryStats] rohitdave:
FRESH BBS Stats

Hi

I have reposted my BBS stats.

Hope I have done it right.

My main concern is the dramatic battery drop of around 5% at random.

Thanks for your help.
[BetterBatteryStats] tytnguy:
Hi I have a weird issue. On LP ROMs my phone behaves properly. (wake locks within 8%). But on (any) MM roms my wakelocks are very high in the range above 20%. The wakelocks go very high after boot then they drop low averaging around 15%. Can anyone point out what's happening. I have attached the log after the boot.

Thank you.
[BetterBatteryStats] km8j:
DELETE
[BetterBatteryStats] githyanki:
What's that?

BBS only monitors your battery, it does not have anything to do with Doze.
[BetterBatteryStats] ChelseaFan257:
Could use some help figuring out what's up with overnight drain on my S7E. A few days ago, it was typically 0.5-0.8%/hour. It is now consistently in the 1.3-1.6% range.

I have had Xposed, ForceDoze, Greenify, and L Speed running throughout, with the latter seeing a couple of updates in the interval. I also added Power Nap to the mix to see if I could bring idle consumption lower, and that (as far as I can tell) was when it ironically rose instead.

For the attached run (last night), I removed Power Nap completely. I also used Tasker to switch the native Power Saving mode on and underclock the CPU (as well as shift to the powersave governor) in Kernel Adiutor.

I suspect that the increased drain is a consequence of changes in some of the tweaks in L Speed, but I would like a second set of eyes if possible.

Thanks!
[BetterBatteryStats] pjadec:
Probably these keep your phone awake

vfsspi_wake_lock (): 7 h 38 m 53 s Cnt:(c/wc/ec)8/0/0 99.8% probably kernel problems ?

and

com.rageconsulting.android.lightflowlegacy (): Wakeups: 329 (43.0 / h)

but in log screeen on time is too much get it below 20 sec when you take log
[BetterBatteryStats] ChelseaFan257:
Definitely seems like it, I feel dumb for missing that, thanks! I've been using L Speed tweaks as well, and am looking for answers in its thread as well as in that of the kernel.

That said, apart from 2 other posts (with no replies) in this very thread, I'm unable to find any information on this wakelock. I suppose a kernel change and ROM flash might be necessary, but I can't afford a clean flash at the moment. :/

Forgot about that, will keep it in mind.
[BetterBatteryStats] TNSMANI:
Idle dump: charge your phone to 100%, unplug and don't touch it for 6+ hours. After that, unlock your screen, immediately open BBS and save the dump file, keeping the screen on time to less than a minute.

What you have posted is an in-use dump.

---------- Post added at 07:04 PM ---------- Previous post was at 06:51 PM ----------

As per the dump, you have attained nirvana?

0.0% per hour!

But you still had some alarms etc and so may be your BBS reading was stuck.

I think that you are using Amplify. If so limit the recommended alarms and wakelocks. If you have already done it, check that you have not missed anything.

Your WiFi and mobile data were both used by the phone. Mobile data normally consumes more battery than WiFi.

Check with one more dump and if you still get 0.0% or anything less than 0.5% per hour, thank your stars.

Regarding your issue of random drain of battery, we may not be able to help as we are concerned with idle drain here. You may require the expertise of others. I am not competent for that.
[BetterBatteryStats] rohitdave:
Thanks for the feedback.

Yes I am using Amplify Donor version along with Greenify Beeta latest version and the Greenify Donor version with Xposed, as my main battery saving apps.

Force Doze and Power Nap are also installed mainly as a comparitive for Greenify which I feel is in the lead.

I will post a fresh dump shortly after having restricted Wakelocks and Alarms.
[BetterBatteryStats] ChelseaFan257:
Quick update in case anyone is interested (I know at least a couple folks haven't gotten answers for wakelock issues like the one I have):

vfsspi_wake_lock is a fingerprint sensor wakelock. In my case, as I understand, it was caused by incompatibility between GravityBox's fingerprint launcher (which targets Android's native API) and the Samsung Pass API. There is no straight fix, because GravityBox does not (and isn't expected to ever) officially support TouchWiz.

There are two alternatives on the Play Store:

1. Fingerprint Quick Actions is the same as GravityBox in terms of compatibility with Samsung devices, per reports (I have yet to test it).

2. Fingerprint Gestures, meanwhile, could work, as it targets both APIs. However, for what it's worth, when I switched it to Samsung Pass, I had issues getting gesture actions to fire quickly and reliably.

After I disabled the fingerprint launcher, last night, my overnight drain was 0.3%/hour. :highfive:
[BetterBatteryStats] Javi22:
Ok here it's a night idle stats

Doesn't seem bad, during the day idle time is much bad

Nexus-5x

http://cloud.tapatalk.com/s/58360b4b8cf47/BetterBatteryStats-2016-11-23 4g location on.txt
[BetterBatteryStats] rohitdave:
4% Drain Overnight

Hi

I have posted fresh dump with 4% drain overnight.

Kindly have a look

Thanks.
[BetterBatteryStats] vEChLj3Cwk06oDam:
Computing

I bought and installed the app from the play store.

Upon launch I am presented with a loading icon and the message "Computing" which never goes away...

I cannot interact with the app in any way because of the loading popup.

Restarting and reinstalling did not help.

Im on a Xiaomi Redmi 3 with globeROM 8.2 based on xiaomi.eu 6.11.17.
[BetterBatteryStats] x.trinity:
Read about BBS how it works. Check Manual. Its everything Ok.
[BetterBatteryStats] vEChLj3Cwk06oDam:
ok, so I downloaded the zip from here (better.asksven.org/bbs-systemapp) and flashed it via twrp.

after that play store said there was an update for BBS so I installed it and rebooted.

But the app is still stuck loading. The permission manager shows me that BBS can access battery stats...

So I do not know whats wrong
[BetterBatteryStats] mitchdickson:
Why didn't you just download and install the latest version in this thread?
[BetterBatteryStats] IronTechmonkey:
It seems like you are not reading the original posts of this thread or searching the thread for answers (both expectations, in fact XDA rules). If it's a known issue you might find an answer that way. Beyond that, it would help if you provided details about your device. ie Android version, ROM variant and version, root method, SU method.

---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------

D'oh... and this Thanks [MENTION=4452264]mitchdickson[/MENTION] but then the download link is aaaaaaaall they way down at the bottom of post #2.
[BetterBatteryStats] Diablo_692:
I have an unlocked RS988 LG G5 running Marshmallow 6.0.1 and it is not rooted. Kind of a noob question, but if the G5 RS988 variant can't be rooted, how can I even run BetterBatteryStats?
[BetterBatteryStats] githyanki:
Post 4
[BetterBatteryStats] Icetea:
is it necessary for the functionality of BBS to be protected against finishing after screen is off?

I have installed BBS to /system but i am not sure, what i have to do now.
[BetterBatteryStats] jdegreef:
Hi,

I'm testing RC3 on a Moto G LTE/4G (Peregrine, xt1039) with latest snapshot of CM13.

The sensors page is empty although I can see raw data both with normal install and system install.

I made a search on "sensors" through the 3143 pages and found this post but plugin/unplugin my phone didn't solve the problem.

Did I miss something ?

Let me know what dump file/logcat I can provide to help understanding what's the problem.

Thx
[BetterBatteryStats] DB126:
While I can not answer your question (sorry) I wanted to comment on the qualities that make this a great post:

- question clearly stated

- device make/model and ROM specified

- thread search performed (thank you!)

- offer to provide dump/logs as needed

Excellent example for others to follow. :)
[BetterBatteryStats] CryNickSystems:
Can anyone please have a look at my log from BBS? I'm suffering from quite some battery drain over night, even though Wifi, Bluetooth, etc. is off.

Thanks very much in advance!
[BetterBatteryStats] TNSMANI:
You have a lot of alarms which can be limited by Amplify, provided it works for you (since you are on N).

Some others which are under your control are appwidgets, WhatsApp, Tapatalk, Instagram, Tasker etc. Check their settings and reduce the frequency of their wakeups if possible.

You were also using mobile data and not WiFi. There was a download of about 1MB by Google Play Services. Considering everything, I think that your drain is acceptable.

---------- Post added at 02:30 PM ---------- Previous post was at 02:25 PM ----------

I think that this is the best you can hope for. I have no more suggestions.
[BetterBatteryStats] Benderis:
Mh, thank you for that solution for without root-users... but I still get the message "permission BATTERY_STATS is needed".
[BetterBatteryStats] Bradco:
Hi everyone,

My phone goes into deep sleep (73%) but in alarms i have in first position com.google.android.gms with 68% ( wakeup: 126 (8.3/h)

It is not a lot ?

thank you in advance
[BetterBatteryStats] j1gga84:
Hi together,

I have an "issue" with latest BBS but maybe it is only a wrong setting.

I can't see any useful data under partial wakelocks like you can see in attachment, what could be the reason for that?

concerning kernel wakelocks, what are these wlan wakelocks for example about? (screenshot 2)

under alarms I have quite a lot wakelocks for com.google.android.gms (screenshot 3 and 4), anything I could remove here?

thanks & regards
[BetterBatteryStats] jdegreef:
Thanks, I guess I've win the fact I'll have to answer my question myself :D

Well, after a few days I see data from the sensors, just a bit :o
[BetterBatteryStats] Benderis:
Someone could help me to get it run... Now, I get all information, but no "Alarms".
[BetterBatteryStats] OmegaBlaze:
What do I need to uninstall to get rid of this?
[BetterBatteryStats] Kzyw:
Thanks a lot!
[BetterBatteryStats] DB126:
WiFi Manager. That said this particular app does not wake the device or impose a significant drain when triggered (when device is awake). Wakelocks and how usage information is presented by Android and various battery/power management apps often distort what is really happening. An idle BBS dump will yield a better picture of items that may need further action.
[BetterBatteryStats] TNSMANI:
Don't uninstall anything. I think that you have enabled WiFi to scan always (Device>Settings>wifi click the three don't menu on top right and then 'advanced'.

Disabling that may solve the issue. Check the settings in Location and ensure that WiFi and BT scanning are off.

---------- Post added at 08:25 PM ---------- Previous post was at 08:19 PM ----------

Partial wakelocks: that is how the info is presented. However, you can ignore the *launch* and *alarm* since they are said not to drain.

Kernel wakelocks: wlan: WiFi issue. Try setting a static IP for your phone.

Alarms: some of them can be limited by Amplify.
[BetterBatteryStats] Perseus:
In the Log you posted, do you see the Line

Screen On (): 20 m 45 s 3.9%

That indicates you used the phone for 20 minutes. This is going to Skew the Analysis. Here in this thread, what we try to do is to reduce Idle Drain. Drain that happens when phone is on but unused. Such usage as above interferes with that analysis. Having said that, From rest of the log, I see that there is some Chatty Device on your Wireless Network, such as a Wireless printer or something else. I'd suggest assigning a static IP from your Router to this phone. Also Family Locator does wake the phone some. I guess that's a necessary evil. In addition to this, there's Facebook, some Widget on homescreen or Lockscreen is drainer. Reuters' refresh over Net caused quite some Drain.So did the other 2 news Outlets WSJ and Economist. Can you reduce their refresh frequency so they don't refresh this often ? Please post another log after these changes are made.
[BetterBatteryStats] Javi22:
Ok mate. Thanks a lot :good::good:
[BetterBatteryStats] OmegaBlaze:
Wifi was set on always.

What about these two?
[BetterBatteryStats] mkr2511:
this happens everytime after dirty flash of any rom. i dont know how to solve this. tried delete reinstall, wipe data etc but same happens.

im on RR N oneplus 3

ps: i know its only few sec before i took screenshot. but the same is shown even after hours.

few posts back i saw someone had the same issue and provided log but no solution was given.

just bringing this into your attention
[BetterBatteryStats] Perseus:
Pay Attention to the alert messages that pop up when you open BBS for first time after a boot. Quiet possibly SEL might be interfering or SuperSU's namespace separation.
[BetterBatteryStats] mkr2511:
thank you so much for your reply.

i always keep SEL to permissive and namespace separation turned off. i use supersu SR4.

this issue is solved only after a clean flash. what might be the problem here?

and if i click 'raw stats' tab, it show 'batteryinfo service could not be contacted' at the bottom
[BetterBatteryStats] TNSMANI:
Aren't you using Amplify? The drainers in the first screenshot can be limited by it.

I think that the second screenshot was taken before you switched off WiFi always on.
[BetterBatteryStats] OmegaBlaze:
I'm not using amplify. Nougat doesn't have Xposed available. I wish there was some form of App Ops available for 7.1.1.
[BetterBatteryStats] Perseus:
Your clue is in that message. The unreachable service. Make sure you're using the latest beta of the app from op. If the error still occurs, please review the adb tutorial linked in the OP Post #4.