yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] yhrn:
I don't think there is such a thing as a normal ratio really. If you disable all auto sync/background data (or even put the phone in flight mode) and make sure you have no apps that are scheduled to do things in the background, etc. you should have very small difference between awake and screen on time.

However, having apps that do sync or do stuff in the background is really pretty useful for most people and worth using some battery for. You will just have to decide when the trade-off is worth it. BBS is a great tool for diagnosing if you have any app or setting (system or app) that causes unreasonable drain so you can take some action (basically remove it, reconfigure it, replace it or live with it).

In your case I think the wakelocks you should focus on are:

The partial wakelock "Managewakelock", which kept your phone awake for almost 3 hours in 30 hours. This is most probably some app you have. Try googling it and see if any of the hits points to any of the apps you have installed.

The kernel wakelock "deleted_wake_locks" - no clue what to do about it though.
[BetterBatteryStats] pakde:
this is very good app. I used this tool in combination with another app which provides the standard battery/process information.
[BetterBatteryStats] xuxuzao:
cant wait for it man

bbs is really an impressive app!!
[BetterBatteryStats] sohebq:
Thanks for your reply. Yes, "managewakelock" is something which is beyond my understanding and it is always there on every battery cycle. If you ever get to know the exact reason behind this , let me know. deleted_wake_lock is gone for the moment.

EDIT: I am feeling "handcent sms" might be causing "managewakelock". Am i right? I send around 300-400 texts per day and if i look into alarms, handcent is causing around 100+wakeups .
[BetterBatteryStats] hollal:
Shark For Root kept restarting my phone when I click to stop the capture so it never saved anything. I put tcpdump in /system/bin and ran it instead though and found nothing I could see as being wrong. I'd disabled background data and syncs in the settings menu and the only thing I found were lots of EAPOL packets and the very occasional ARP from the router. I found that my router was refreshing the WPA key every minute. I increased it to 256 as a way to test and the next time I checked, for about 30 minutes or so I was using 2mA. I thought I'd cracked it but afterwards it went back to 30+. Battery drain is still the same. When I check wlan_wake_rx wakelocks it's low, like 50, but wlan_wake is 1000+. I don't understand what's waking my wifi if it's not then going to receive anything.

I tried to boot an old BackTrack 5 CD so I could watch all the management packets in the air but I can't get it to load up successfully - it's always been a case of multiple boots to get it working because it doesn't like my graphics card, but today I've not had a single win out of 20 boot attempts :(

I can't think of any other way of checking what's causing this drain when on wifi when it seems that the device isn't receiving any packets directed to itself.
[BetterBatteryStats] hollal:
Weird. I've just done another packet sniff over a few minutes and I'm getting a single packet every 10 seconds. The strange thing to me is that the originating MAC address is almost identical to the phone's MAC address, except for the very first character!

xy:yy:yy:yy:yy:yy sending to yy:yy:yy:yy:yy:yy

y represents a match with the phone's MAC address. So it's a different device with an almost identical MAC address on the network? None of the other devices on the network have that address. I thought the first few characters of the MAC was manufacturer specific. Anyway, the contents of the packet is an unknown protocol in Wireshark and on has a 'data' field which doesn't seem to change much. I've attached it to the post anyway if anyone wants to see it (it's truncated to 68 bytes).

Maybe the next step for me is to block EVERY app's access to wifi and see what results I end up with in the same test. I'll do that now.

Also, I apologise to chamonix for this unrelated topic, but it seems that a lot of people experience this drain with wifi and the 'go to' thread for investigating it is always BetterBatteryStats! If you would rather, I'll create a new thread elsewhere.
[BetterBatteryStats] hollal:
Blocked EVERYTHING with DroidWall and the results are still the same. The same packets are still there.

I give up :(
[BetterBatteryStats] chamonix:
I don't mind :-) as long as the posts are related to understand the stuff bbs reports there is no OT
[BetterBatteryStats] chamonix:
Forget about the times, the count plus the overhead explains the difference. If you are not logged on to latitude your maps is obviously misbehaving, especially check-in. I'd suggest that you clean maps data and make sure you're on an up-to-date version
[BetterBatteryStats] Yarox:
First of all thanks for your devotion in keeping this project running after so long. I installed the app on my Galaxy S II, and after a bit of tinkering (MIUI sure doesn't like it), I managed to get a good dump.

From what I see, on my phone the Music player is a major issue. Any insight would be appreciated.

Note: I'd have posted a dropbox link but apparently I don't have enough posts. I guess that's just about what I get for lurking and not participating in discussions =/
[BetterBatteryStats] jeremysherriff:
I can't find anything useful, I run MIUI but don't have the same wakelocks from music. I wonder if it's continuously scanning your sdcard for media? Do you have it plugged in via USB often, or anything else that might account for such scanning?
[BetterBatteryStats] Yarox:
I can't think of a reason to justify this behaviour. That being said, could the Music player be the cause of additional battery drain? I'm unfamiliar with how BBS stats reflect in real time, as I just got the app and am still in the process of familiarising myself with it. (is the entry in bold unnaturally high?)
[BetterBatteryStats] jeremysherriff:
Hmm I want to say yes, but then looking at the snippet I realize it's over a very long time, and you've charged at least once in that period. Get another dump, this time post (as attachment) the whole log. Ideally, the log needs to be overnight while you sleep, having been fully charged and then disconnected.

Also, with MIUI, you'll need to disable the battery info service to clear the stats, and then re-enable it once you disconnect the charger in order to allow the stats to start collecting.
[BetterBatteryStats] Yarox:
I'll post a log tomorrow. What I did do though was freeze the Music app after fully charging the phone. With network connectivity on, it spent 3% over an 8h period, which is acceptable.
[BetterBatteryStats] gurpal91:
thanxx man...............................:prop:
[BetterBatteryStats] richua:
I've attached my dump for review. I've frozen many apps and prevented others from starting on boot but my drain still seems fairly high. Also, my "Awake" bar in system stats could be less filled.

For this dump, I booted fresh and left it overnight without touching it. Only Lookout and TI Backup ran for a virus scan and backup, respectively.

Known issues:

Kik has lots of wakelock errors. The dev acknowledges this.

I use network location and sync a lot so I'm OK with that drain.

I've frozen GTalk but still see it in the dump. Is there anything else I can do short of deleting it?

Let's see if we can tackle this together.
[BetterBatteryStats] Hedied4me:
Not sure if this has been mentioned and I'm far too tired to look. Has anyone else noticed on the new widget (with the pie graph) that if you press the refresh button in the upper right corner it doesn't update? I have to open the app with it to update it. Could be just my phone and I did notice if in the last few beta versions as well. Just curious

Sent from my Virgin Mobile HTC Desire 601 zaraCL cdma
[BetterBatteryStats] IronTechmonkey:
Then take a nap and look later ;). It takes less time than making a post and you may find an answer. There have been issues with parts of the new widget updating.
[BetterBatteryStats] lakshmish:
So i have gone through the large part of this thread and i am still not able to figure out why i am not getting full info on alarms and it turns out that some one has already posted about this problem few pages back and no one seem to have found the solution.

http://xdaforums.com/showpost.php?p=63075939&postcount=29454
[BetterBatteryStats] chamonix:
Thanks for your feedback: this is a tricky topic be you can follow the developments in that regards on feature request #607(see post #1 for the github issue/feature request link
[BetterBatteryStats] chamonix:
As you didn't post a dumpfile+logcat this is pure speculation but I bet with you that BBS falls back to API mode because samsung has borked android with its half baked knox implementation. Even if unsupported at this point because I can not buy every device that has an own incompatible implementation of android you can search this thread for a patched bbs version that seems to solve the problem by not requesting for SU when asking for detailed Alarms where bbs would fallback to compat mode because of the mentioned samsung's own rolled code
[BetterBatteryStats] IronTechmonkey:
I'm stumped....but notice that person also has a Samsung. On my Moto with CM12, SuperSU 2.46 or 2.52.those stats are OK. I did once have a similar sounding (if not technologically similar) issue with partial wakelock not having any available stats in stock Moto, rooted with native CM SU, but an incidental clean flash to a different nightly, a tidier BBS installation and switch to SupeSU set it right. A different scenario so... just for what it is worth.
[BetterBatteryStats] yahyoh:
why this happening ? on cm12.1 is it because cm superuser ?

edit : i tried with supersu and the same :\

edit : installing it again seems fixed it
[BetterBatteryStats] Hedied4me:
Meh, fair enough.

Sent from my Virgin Mobile HTC Desire 601 zaraCL cdma
[BetterBatteryStats] IronTechmonkey:
That is a well known and reported issue addressed by a particular installation work-flow described earlier in the thread.- install - install system app - reboot - install app

---------- Post added at 11:46 PM ---------- Previous post was at 11:39 PM ----------

... and what you find out may be of help to others (seriously - this issue seems to be a moving target or at least I just don't fully understand it - the more people testing it, the better), and there might be opportunities to practice finding the thanks button as well :).
[BetterBatteryStats] austinpinto:
hi all.

i am finding a heavy battery drain in android m.

almost 30% to 40% in 8 hours.

so i installed the app and will do what is said in the first post.

i cant root my phone as there is no root for it on android m.

so will a non rooted phone give me all the info i need to roughly pin down what is causing this drain?

gsam battery moniter says that wifi takes 6% and keeps the phone awake all the time
[BetterBatteryStats] IronTechmonkey:
There are limitations - depending on your OS some important stats like "partial wakelocks" may not be available without root. Read the original post and search it for the word root for more details about that.
[BetterBatteryStats] devil-kin:
Any idea how long it'd take to deploy completely through the play store? Still waiting for the update to come through.
[BetterBatteryStats] Nick_101d:
I'm facing the same battery drain problem and my phone is rooted ,what can I do to fix it?
[BetterBatteryStats] [Gorgasm]:
Hi !

I would like to know if it is normal if I can't see the detail of my alarms, like in the screenshot below (I'm using a Nexus 5 running Marshmallow) ? It was not the case in Lollipop.

Thanks ! :)
[BetterBatteryStats] mdamaged:
Just grab it from the OP.
[BetterBatteryStats] devil-kin:
Unfortunately, you then end up with two versions. Yes, I actually paid for it on the play store.
[BetterBatteryStats] [Gorgasm]:
I forgot the screenshot, sorry ^^
[BetterBatteryStats] mdamaged:
Uninstall the one you paid for, install the one in OP, then it's only one version. The one in OP has full functionality.
[BetterBatteryStats] devil-kin:
Good man. Don't think you read my question, though. But I'll leave it at that.
[BetterBatteryStats] mdamaged:
Oh See Dee?
[BetterBatteryStats] IronTechmonkey:
You may have gotten mixed versions by doing part from play store and part from XDA or using 2 different version from the XDA thread. Please don't take this as sarcasm as it is just an "if P then Q" logic equation. If you must use playstore as source then you must wait for the update to hit playstore. Your alternative is to run through the installation process using the material from this thread and use the same version of the installer for the initial installation and for the second app only installation.

Also, for people who have had issues with cross version system/app installations of BBS, it may be worth noting that the latest version which is "2.1.0.0", when viewed in an alphabetized list of recent BBS installer versions in a file manager will sit near the top of the list where it can be mistaken for an older version, rather than sitting at the end of the list... since it does not have any suffix like "_RCx". I once accidentally installed a mixed version as a result of that... for what that is worth to anyone.
[BetterBatteryStats] meyerweb:
Unable to install BBS?

I've finally upgraded my device (LG G3) to Lollipop. Had an older version of BBS on it before, and now trying to install the newest version from XDA. I've tried a couple of different file managers, click on the apk, and at the bottom of the screen are two buttons, Cancel and Install. But the install button doesn't work. I can tap cancel, and back out, but tapping Install does nothing at all, not even highlight the button.

Has anyone seen this before, or have any idea what the problem might be?

Thanks.
[BetterBatteryStats] IronTechmonkey:
Most likely the effect of a third party app. Lot's of info about many apps that cause this can be found by searching web (not just XDA) for Android AND app AND install AND button AND not AND working. There is even an XDA thread about it somewhere.

[EDIT] - as an alternative you could try using a file manager such as ES Explorer or MiXplorer to try installing it without the native package installer...although it might be better to sort out the package installer and continue using that.
[BetterBatteryStats] cdzo72:
If you have Lux Auto Brightness installed then temporarily disable it
[BetterBatteryStats] cLogic:
back in sept I posted the script that I use in /system/addon.d for bbs here: http://xdaforums.com/showthread.php?p=62997639#post62997639

it references the xda version file, but it is a simple matter to add the play store version file to the list

cheers,
[BetterBatteryStats] meyerweb:
Weird! Thank you very much!

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

ES is one of the things I tried. You're right that it was a 3rd party app, and CDZO72 was right about it being Lux.

Thanks.
[BetterBatteryStats] chamonix:
this problem is pretty common with all kind of apps using overlays that sometimes mask buttons
[BetterBatteryStats] meyerweb:
I still don't understand why it masked one button, and not the other, but.......

Next time I run into a similar problem I'll remember to turn Lux off.
[BetterBatteryStats] mondohow:
You don't have to keep turning Lux on and off. Just go into Lux Settings > Advanced > scroll to the bottom and select Use Alternate Overlay. That should fix the issue without you having to disable it each time.
[BetterBatteryStats] nicesoni_ash:
Better to add package installer in lux's sleep list.

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[BetterBatteryStats] mondohow:
If you check the Lux thread you will see that method doesn't work for a good set of users. As Lux is OT this'll be my last comment on this.
[BetterBatteryStats] anthonypiccolo:
Does installing BBS as a system app then prevent future OTA updates from occurring on my Nexus 5 or will they still happen?

My phone is rooted but doesn't have a custom recovery and I've been able to get OTA updates in the past by doing this. I'm wondering if I'll still get them with BBS as a system app.
[BetterBatteryStats] bombadier:
The OTA will fail as the system is not the same as stock(surprised that the ota will take if you are rooted)
[BetterBatteryStats] anthonypiccolo:
OTA's have always worked for me when rooted, I'm guessing because I don't use a custom recovery.

If I uninstall it as a system app I'm assuming that would then make the OTA update doable?
[BetterBatteryStats] bombadier:
Yeah uninstall to take the OTA,
[BetterBatteryStats] chamonix:
I must say Marshmallow feels really good from a batter perspective on my N6. No major drainers and overall less consumption per hour. That said I have location history off and use no Google now
[BetterBatteryStats] mdamaged:
FWIW, I've everything on and it's still phenomenal, looks like they got it right this time.
[BetterBatteryStats] maigre:
You could always try to take the OTA with BBS installed as a system app. If it fails, uninstall it. Then you should be able to take the OTA at that point. I don't see much risk in this, at least based on my history with the devices I've used.
[BetterBatteryStats] [Gorgasm]:
Does someone here have the same problem ? Thanks :)
[BetterBatteryStats] paulr24:
Sorry if this has already been asked, I wasn't able to find much about my exact situation. I'm running stock 6.0 with Franco kernel r32 and I've granted the app permission in SuperSU. When I open the app it shows the following:

BATTERY_STATS not granted

DUMP not granted

SELinux: Enforcing

I've tried installing it as a system app and rebooting but I get the same screen (with the difference that it now says "UNINSTALL SYSTEM APP"). I tried flashing a zip via recovery but that didn't work either. Anyone know how I can get it working?
[BetterBatteryStats] Nimueh:
That's been said a million times already:

Install BBS

Open it, install as system app

Reboot

Install BBS again

Done
[BetterBatteryStats] paulr24:
I tried that too actually, didn't work :/
[BetterBatteryStats] FernBch:
Try again only before installing as system app use a file explorer and set /system to R/W. Then reboot and install again.
[BetterBatteryStats] m0han:
this worked for me:

- copy the apk to /system/priv-app

- rename it as 'com.asksven.betterbatterystats._xdaedition.apk'

- set permissions as rw- r-- r--

- set owner & group set as root

- reboot the device

edit: screenshot
[BetterBatteryStats] paulr24:
That worked, thanks!
[BetterBatteryStats] swat4samp:
I too have it. On stock 6.0 as well as custom rom, on enforcing and permissive too :|
[BetterBatteryStats] Sir_gpm:
Is 1%/hour that bad In stand by mode?.
[BetterBatteryStats] Perseus:
Some roms have a forked selinux core. This could be one of those cases. The other steps listed are next best alternative. (Copying to priv-apps and rename)
[BetterBatteryStats] ygoralmeida:
... Playstore is still on 2.0 version ( didn't update ) ... even if i paid for :(

Anyway, i love the app
[BetterBatteryStats] Perseus:
Due to certain playstore requirements, there are issues & / or delays in updating App version in store. Best to get it from here.

This has been explained before in this thread.
[BetterBatteryStats] IronTechmonkey:
It is within a reasonable range but this depends on battery capacity, background activity, wake locks (good or bad), the nature of the hardware and the nature of charging cycles. In other words it can vary a lot. Something else to consider is that the battery indicator can vary wildly over short spans of 5%-10%.

A real example of some of these factors in concert:

On one device, after a full charge the device would stay at 100% for an the first hour (and this got longer as s I continued a habit of charging frequently across the top of it's range 85%-100%)

On another device, after a full charge the battery seems to dive to 98% or 97% within 20 minutes

On both devices, over longer time spans and larger quantities of battery consumed over those spans the battery usage and duration was consistent and similar between the 2 devices.
[BetterBatteryStats] FloydF:
Is there some reason this now needs access to call logs, pictures, wifi connections and browser history? I am seeing this in a couple of other apps this week as well. Access the apps shouldn't need this as far as I can tell.
[BetterBatteryStats] Primokorn:
Android Permissions are a mess since you don't really know what the app needs or uses.

A summary of what BBS used on my device since this morning:

• Serial nb, /proc

• Internet > inet

• IPC > Binder

• Phone > Configuration MCC / MNC and Network country

• Shell

• Storage (dumpfile)

• Uid of packages / running app / running services / intent activities

No call logs, no pictures, no browser history... There's nothing to worry about :)
[BetterBatteryStats] azuk94:
Hi

Is there any avantage adding BBS to Xposed?

(I already have Xposed to use Amplify)
[BetterBatteryStats] Primokorn:
BBS isn't a xposed module.
[BetterBatteryStats] azuk94:
I saw something about xposed in BBS, tought it has something to do...

Thank you.
[BetterBatteryStats] vobiscum:
Guys but BBS support octacore devices? Because on CPU STATE show only frequency of 4 core at 1,5 Ghz..

Many thanks
[BetterBatteryStats] chamonix:
I appreciate your concerns and you can find a detailed description of why perms are required in the google play app description. If you have question about a specific permission token please feel free to ask. I can assure you that BBS does not spy on you and that these perms are required for doing all the low-level stuff that BBS does.

Also BBS is open source and available on github for anyone to audit the code.
[BetterBatteryStats] chamonix:
BBS reads the cpu info from the kernel so the info you are looking for is not exposed at the level of the linux sub-system. I would be more than happy to have a conversation with a kernel dev to see if there are ways to work around that.
[BetterBatteryStats] gekkehenkie11:
Should this work on Android 6.0 ? Install failed on v2.1 here
[BetterBatteryStats] Tylonhh:
I don't know what is causing this HwCustPowerManagerGCM wakelock. Any suggestions?
[BetterBatteryStats] kewinhdorff:
[MENTION=1330150]chamonix[/MENTION] hey dev! i have used your app a pretty long time. but now i upgraded to cm12.1 android 5.1.1

but it wont install. the install fails :/ and i have to flash the bbs removal zip. what do i have to do to make it work? and also is there a way to not have to install it as a system app everytime i upgrade to a new nightly ?
[BetterBatteryStats] m0han:
check this post and also this.
[BetterBatteryStats] kewinhdorff:
how can renaming the apk help :eek: ? just curious because knowledge about software is interesting to me hehe.

and is this something that [MENTION=1330150]chamonix[/MENTION] has stated that it works? if i do this way do i just download the apk, and dont install it just copy it to priv-app? and set root permissions?

i just want to hear what [MENTION=1330150]chamonix[/MENTION] thinks i should do as he is the developer hehe

thanks for your reply :)
[BetterBatteryStats] kewinhdorff:
okey i just installed it the way you said [MENTION=4620757]m0han[/MENTION]. it is something weird with my phone. i have the oneplus one with cm12.1 android 5.1.1 and the lowest that my cpu goes to is 1.57 ghz :eek: why is it like that ??

okey now after 10 minutes it shows all the cpu states and it went back to the 300- mhz mark does it really take that long ? the wakelock i believe was poermanagerservice.display and powermanagerservice.wakelocks does any one know anything about those wakelocks?
[BetterBatteryStats] drezz2:
with the new version, now what it stays in memory?

In version 2.0 appeared, but the closing of the foreground app, would disappear (attached screenshot)

with 2.1 it stays although not always in the foreground (attached screenshot)

it's like that?

(I not have active monitoring functions)