yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] danigraham:
You can do a dump and log within BBS. Open BBS, click the share symbol on the top right of the app and choose log cat and dump file. Click SAVE. You will get 2 .txt files on your internal storage and you just copy and paste the text to someone here. Make sure to "hide" your logs as they are super long and create clutter on the thread.
[BetterBatteryStats] gd6noob:
Install the apk, then install as system app, reboot. Icon will be blue Companion app, reinstall the apk and it will work as normal. I even rebooted twice and its working fine...
[BetterBatteryStats] gaich:
Added a comment to #612

[MENTION=1330150]chamonix[/MENTION], what do you think about that?:confused:
[BetterBatteryStats] txtsd:
I installed, rebooted, reinstalled but it still doesn't work. And it says no permissions even though I've given it permissions in SuperSU.
[BetterBatteryStats] Dor-b:
After first installation you need to enter the app, grant access and install as system app. then reboot and install apk again.

Worked for me
[BetterBatteryStats] txtsd:
That's exactly what I did. Sorry I didn't make it clear.
[BetterBatteryStats] Dor-b:
Can you please upload a SS of BBS app info?
[BetterBatteryStats] chamonix:
I don't know yet but if it can be fixed I will try to get the info how.
[BetterBatteryStats] txtsd:
It started to work after I uninstalled and reinstalled again (for the 5th time) -_-
[BetterBatteryStats] bombadier:
You need to leave the phone idle for a longer period, at least 4 hours, do it and post another log
[BetterBatteryStats] Portgas D. Ace:
[MENTION=1330150]chamonix[/MENTION]:

I encountered a problem with 2.1.0.0_B3: Better battery Stats does not show stats for WiFi, Blutooth, GPS and so on in the main screen, although I have enabled those stats in the settings. Their related graphics (Settings -> Graphics) are showing the correct data, but it only shows Deep Sleep and Awake. I have wiped the cache, uninstalled BBS, rebooted and whatever I could do in any possible combination. Is it possible to "catch" this malfunction with a log file?

Edit: I (temporally?) solved this issue by uninstalling BBS as system app, rebooting and re-installing it as system app again.
[BetterBatteryStats] smwln:
I am getting this message after installing BBS as system app and rebooting the phone.

I have already tried uninstalling BBS using the zip that is supposed to be flashed in TWRP, and the removing the BBS application normally as any other app is removed.

What to do?

When this screen comes, hitting back won't do anything and uninstall returns 'Fail'
[BetterBatteryStats] Portgas D. Ace:
Uninstall BBS with Titanium Backup, reboot, again check Titanium Backup and uninstall the older version of BBS that is now being listed, reboot, install the newest 2.1.0.0_B3, reboot, open BBS and install as system app and reboot one last time. This solved the same issue for me.
[BetterBatteryStats] chcknsld:
Install BBS again.
[BetterBatteryStats] smwln:
Thanks guys, tried the Titanium method but it didn't remove the app completely, even after the second reboot.

The second method worked, and it's working now!
[BetterBatteryStats] Portgas D. Ace:
Could you do another reboot and confirm if your issue is properly solved? When I rebooted my device after re-installing BBS, I ran into the same issue again.
[BetterBatteryStats] smwln:
Yeah I rebooted the device twice, just to confirm because that's when it was showing this screen, after rebooting. Not anymore. :highfive:
[BetterBatteryStats] chcknsld:
If the companion app shows up, just reinstall BBS again.
[BetterBatteryStats] Portgas D. Ace:
I had solved this issue once for all long time ago by following the steps I described. As the companion app keeps showing up after some reboots while simply re-installing BBS again, just want to confirm that this issue would not come up again for [MENTION=4390696]smwln[/MENTION].
[BetterBatteryStats] marmale:
It worked for me too

Installed first then installed as system app

Then reboot and install again apk

and everything is ok, no more strange popups and errors as before

:o
[BetterBatteryStats] jmfinity:
when i try to check kernel wakelocks.. result is file could not be read..what's the cause of that error? thanks!
[BetterBatteryStats] aitvariux:
My dear friends,

no wake locks, but phone only 3 min deep sleep from more than one hour. I know that 1 hour is a short period, but with this ratio of deep sleep I think it is possible to track what kind of beast eating my battery almost one year! Shared all possible files from BBS, please help me to figure out this magic.

https://drive.google.com/folder/d/0B9deUgT65pOvTmkxRFBEdElFNEU/edit
[BetterBatteryStats] droidbits:
[MENTION=1330150]chamonix[/MENTION]

I am inclined to purchase your app through GP because I admire your popular work and to obviously support it.

I must ask however if through GP does the app install and it is ready to go on 5.1.1 (BlissPop) or will there be any further tricks to do for it to function like with the xda where one has to install the apk twice?

Also are there any major differences between the xda and GP? (this will not affect my purchase as I want the Official GP app).

Thanks. ;)
[BetterBatteryStats] -m3tac0rt3x-:
I bought the App from GP just to support the dev, because there are really no differences between what he releases here and GP.

I am still using it instead of some betas being released, and no problem at all. I'm on 5.1.1 - CM12.1+.

When I dirty flash a nightly the only thing I need to do after the ROM flash is to go to the GP and re-download the "update" that automatically appears from the [My Apps], the system one survives and if you open it it will tell you those warnings about being only a companion app. :good:

Oh and it also survives any reboot after installation! :highfive:
[BetterBatteryStats] droidbits:
Thank you so much for your reply which was most useful. ;)

I am going to buy it right now anyway just to support the work. It is a fabulous app and well worth having the work continue.

Just pondering about what you said about dirty flashing and how the system survives...

but what if I do a clean install and wipe system also, which I tend to do on official BlissPop ROM releases

?

Anyway, I am sure that any problem I will be able to solve it through here.

[MENTION=1330150]chamonix[/MENTION] I will leave a reference "droidbits" in my Google Play review so that you know it was me. Thank you. :D
[BetterBatteryStats] -m3tac0rt3x-:
If you clean flash and wipe system, it's re-install everything from scratch, so you install BBS App from GP, open it and "Install as System App" pops-up - it will request for a reboot once installed to activate and everything will be working as expected. (did a clean install just a couple days ago). :)
[BetterBatteryStats] droidbits:
Thanks so much for that. Getting used to this fabulous app. All my doubts were regarding the installation as it differs from the normal. To learn how to use it I will just read and learn from this thread.

Regards. ;)
[BetterBatteryStats] chamonix:
Thanks for showing support!

The current go version is identical with release 2.0 from xda as 2.1 is still in early beta stage.

Whether you will have trouble with the system app depends on the ROM, not on BBS. You den easily try by uninstalling and beta and installing 2.0 from xda. If it work fine you can install from gplay and update to xda 2.1 beta as they work side by side.
[BetterBatteryStats] droidbits:
No problem. Did it this morning.

Installation went smooth like Saudi Arabia black oil.

No need to thank me...I thank you for such work. Any doubts I should have I will post but the thread and the OP is full of info. ;)
[BetterBatteryStats] joshken.fn:
great :)
[BetterBatteryStats] crisava:
wakelock problem

Hi everyone,

I've a problem with my Meizu MX4 battery. I can use it only 2 hours (screen on time) in a day (it have 3100mah battery). I post here the screenshot from betterbatterystats.

I hope that someone can help me because EINT, CCCI0_peer and ttyC0 wakelock are killing my battery :(

Thanks,

Cristiano
[BetterBatteryStats] CRXed:
It's very ease to see in your logs.

Your top 7 wakelocks is all cause by *sync* so you should disable automatic syncing. You havve sync enabled for

-Google Currents

-Friendcaster

-Google+

-Gmail

-Google Talk

-Cooliris Gallery (I am not sure why you have to sync this?)

Probably syncing is taking a long time on 2G so that's why your phone almost never goes to sleep.

---------- Post added at 03:07 AM ---------- Previous post was at 03:00 AM ----------
[BetterBatteryStats] ZRong223:
Hey guys, I found that BetterBatteryStats can be "force close" even after exit it. Do I need to do that?
[BetterBatteryStats] rmean:
Hey there, some questions:

What is -

-activitymanager-launch

-RILJ

-sleep_broadcast

-alarmmanager

?

I'm asking for those because they reach an extremely high count over here (about 1.5k/day). i doubt if this is normal, so I'm asking :)

Regards
[BetterBatteryStats] superbobup:
i've had the phone for about 6 weeks, would it really be a bad battery? :confused::(

thanks for the kworker thread. i saw that earlier and will look into it.
[BetterBatteryStats] S873068:
Awesome!!

it works great on my device!!:D
[BetterBatteryStats] pikachu01:
Maybe you were in an area with bad signal?
[BetterBatteryStats] Hrithan2020:
Well, I have tried freezing tasker and it has not made any difference in the days of monitoring with it disabled. Have also checked in tasker forums where came to know that these locks don't really affect battery life. Similar to, say headsetobserver wakelock where the count can be very high.

I have already tried all I can do to minimize gsf wakelocks. Regarding maps, I am using it , hence had defrosted it. But haven't signed in to latitude.

Anyway, will try with maps and tasker disabled and attach a BBS dump tomorrow, with auto sync and mobile data disabled.
[BetterBatteryStats] superbobup:
i'm usually in an area with decent signal...about -81dB on 2g. i'll try on airplane mode tonight.

i recently upgraded to AOKP 19 and have NOT disabled/uninstalled any apps (such as maps, talk, etc.). i'll sign out of everything and see how it goes with airplane mode. will post a dump tomorrow
[BetterBatteryStats] intulsa:
For me tasker can cause mine to drop from 1% to 6% loss overnight. I use tasker and I just accept that loss as part of wanting to run tasker. For max battery life though I have to shut down tasker.

I have maps that I use occasionally. I set up a titanium widget to freeze and defrost as I need it so it stays off most of the time unless I'm traveling.
[BetterBatteryStats] A$h x:
I'm getting pretty bad battery life... keep sync, wi-fi, and data off unless they in use. Currently running Checkrom V4 on my SGS2, and getting around 3 days. Used to get 5-6 days on Villain ROM :(

I have attached my log to this post, can someone please suggest how to stop my phone from randomly waking itself up when the screen is off?
[BetterBatteryStats] Hrithan2020:
Nice suggestion, will setup a widget and give it a try.

Regarding tasker, would it be possible to list out the the tasker profiles you have. I am having mostly automatic rotation enabling or other profiles, so don't understand why it should account for wakelocks.
[BetterBatteryStats] dcharleyultra:
As some others have told posters, some things jump out right at you. What do you see in your file, e.g. in the Alarms section?

Swyped from my Evo 4G using Tapatalk
[BetterBatteryStats] CRXed:
3 DAYS????:confused: Wow you should be lucky!

Anyway, the top of the wakelocks are easy to spot.

-Juicedefender is waking your phone.

-You have been using Audioplayer and GPS

But the worst is your Alarm count which is caused by:

-com.bluetornadosf.smartypants = Skyvi ??

-Juicedefender

-Maps

etc.

So remove Skyvi and Juicedefender and disable Location services when not needed.

After that, try to make another log without using your phone.
[BetterBatteryStats] intulsa:
Every time tasker wakes up my phone to check a profile according to the time table in the monitor settings. On mine, with the phone sleeping that's every 10 minutes. It takes a full minute for my phone to go back to sleep. How can that not use a wakelock and suck up some battery? The profile doesn't matter. It's still going to wake up. I have one profile that doesn't trigger except MWF, but tasker still has to wake up every 10 minutes, sees that it isn't one of those days and without even triggering it still uses power. Every wakeup uses power.

If you're running takser you'll be seeing tasker wakelocks in your BBS log and alarms. No way around it that I know of. The best tasker profile I came up with for saving battery was a profile to turn off tasker at night.
[BetterBatteryStats] Hrithan2020:
Hmm. Another thing I noticed, there were still wakelocks when tasker was defrosted with ZERO profiles.

Any idea how to reenable tasker in the morning automatically?
[BetterBatteryStats] intulsa:
if its on it'll wake just to check according to the settings you have configured, default is 10 minutes. I found that out myself. It's not as bad as most apps though. I don't lose maybe 5-6% overnight with tasker even with no profiles. Not much different with my profiles. I get less than 1%/hr drain with tasker running so I'm ok with that.

I used my clock to start it back up. But now I just leave it on and accept that it's worth a little battery to run it. I'd rather use my phone than have my battery last for days and days.
[BetterBatteryStats] chamonix:
I have received a really interesting log from tommmii showing how BBS stops working on KIUI that I wanted to share.

com.android.internal.app.IBatteryStats$Stub.asInterface
I/BatteryStatsProxy(29817): invoking getStatistics
D/dalvikvm( 1093): GC_FOR_MALLOC freed 720K, 44% free 8481K/15111K, external 0K/0K, paused 62ms
E/JavaBinder(29817): !!! FAILED BINDER TRANSACTION !!!
I/BatteryStatsProxy(29817): retrieving parcel
I/BatteryStatsProxy(29817): reading CREATOR field
E/TAG (29817): An exception occured in BatteryStatsProxy(). Message: Bad magic number
I/BatteryStatsProxy(29817): invoking android.os.ServiceManager.getService("batteryinfo")
I/BatteryStatsProxy(29817): android.os.ServiceManager.getService("batteryinfo") returned a service binder

At some late point in time after many calls to the service this error "bad magic number" occurs. It is consisitent to the behavior reported by users that on MIUI the data stops being displayed after some time. This only happens on MIUI.

I have an idea of a possible workaround I will provide in the next days so we can see if it makes a difference
[BetterBatteryStats] chamonix:
I like the idea but I need to be carefull. BBS is known to be a non intrusive tool with ne overhead and I don't want to jeopardise that. Waking up once an hour shouldn't be a problem but I need to be carefull about the processing that would happen. Anyway, here's the feature request for that: https://github.com/asksven/BetterBatteryStats/issues/92
[BetterBatteryStats] chamonix:
Tampering with GSF is something you should not do. I suggest unfreezing them and taking another run.
[BetterBatteryStats] chamonix:
kworker are the kernel worker processes. What issue are you talking about and what leads you to believe that kworker are related to battery drain?
[BetterBatteryStats] mdamaged:
Read the OP, follow it and post a BBS dump after following the procedure outlined there.
[BetterBatteryStats] crisava:
Ok, thanks and sorry for the post! I will post the dump in one hour :)
[BetterBatteryStats] crisava:
Here the dump file! I leaved the phone alone for one hour, and there is also this time the EINT wakelock that i don't know what is it... :( and also if you look the screenshot that i have uploaded the EINT wakelock is the first one, followed by CCCI0_peer and ttyc0.

Can you halp me please :)?

Thanks in advance

Cristiano
[BetterBatteryStats] mdamaged:
You did not really read the OP completely, as 44min is not really what is suggested in it. Anyhow, wakelocks are not an issue, they are needed for operation of your device, this is about battery usage, and I see none. Nothing here to do, enjoy your device.
[BetterBatteryStats] crisava:
You right, I'm sorry but after 45 minutes i restart to use my phone and i uploaded the dump immediately. If you tell me that EINT wakelock is not a problem i beleive in you. But can you tell me why in my "old" oneplus one i didn't see anytime this wakelock? :)

Thanks for the help :)
[BetterBatteryStats] mdamaged:
Different device, different hardware, different kernel, different rom.
[BetterBatteryStats] crisava:
Ok thanks for all!
[BetterBatteryStats] ahsengah:
Hey Guys,

Have been a fan of Better Battery Stats for some time now and just had a quick question.

I am using BlissPop ROM on my OnePlus One phone, and I am getting excellent battery life. In the past, my top wakelocks were the usual suspects, NLPWakelock etc.

However, whenever I loaded up the app, and checked partial wakelocks, it always seemed to be *alarms* showing up. Can anyone please clarify what this may be? Is this a good or bad thing?

Please find my screenshot below:

https://lh6.googleusercontent.com/-hEaouIngkO-9_QQc2bzT-2FZzJHh4kGa0IG-ZWz5dRz=w273-h485-no

Cheers
[BetterBatteryStats] arubamon:
msm_hsic_host Wakelock

Looking at my bbs stats for the past 2 hr (I know that 2 hr probably isn't long enough to get a good analysis, but maybe someone can still give me some feedback), I notice msm_hsic_host is wakelocking my phone 94% of those 2 hours w/ the screen off, causing my battery to drain 4%/hr. A week or so ago I got my phone to sleep for over 14 hours, and I was only losing 0.3%/hr. If someone could take a look at my logs and help me figure out what the problem is, I'd appreciate it. Thanks
[BetterBatteryStats] chrismalla:
I've attached a well made log: Custom reference, untouched for almost 10 hours, log immediately exported. I have done the logging two times, with consistent results. Almost 4%/hour, which is significant on a phone with a 3100 mAh battery (OnePlus One). Please take a look at the log, the "only" interesting I could find was under "Kernel Wakelocks", more specifically: "radio-interface".

PS: Why do you (OP) want me to attach the log instead of placing it in a spoiler?

EDIT: I found what was causing the problem. The setting [Settings/Mobile networks/Preferred network type] was set to 4G which is causing signal loss and battery drain for me (in Sweden, Tele2 carrier and one of their subscription plans). 4G doesn't work globally...

EDIT_2: It seems like it was the COMBINATION of the two settings "Preferred network type" and APN that was the problem in my case. It turns out Cyanogen had set the wrong APN setting as default (in my particular case), which caused a conflict related to "Preferred network type" being set at "LTE". Now, I have the correct settings for both APN and "Preferred network type" and everything works as expected, no wakelocks, no signal drops. I had to contact my carrier about which APN to use, there were no good info on that on the internet or on their website. So if you're unsure, contact your carrier.
[BetterBatteryStats] ondrejvaroscak:
PS: Why do you (OP) want me to attach the log instead of placing it in a spoiler?[/QUOTE]

Because it's easier to save it for analysis than copy paste it from spoiler.
[BetterBatteryStats] ilnessuno4691:
Why i cannot use bbs after having installed it as system app? Dont understand...rom CM 12.1 by Justarchi S3 kernel stock

Sent by a crapsung S3
[BetterBatteryStats] droidbits:
After you install as system app, you must install the bbs apk a second time on the top for the app to work.

You can then open bbs and it will run fine.
[BetterBatteryStats] xonelith:
Or install it in system/priv-app:thumbup:
[BetterBatteryStats] tangcla:
Hi, did you ever get this resolved? I just noticed the same problem with my new phone.
[BetterBatteryStats] amjath:
Guys can anyone help?

I use oneplus one running cos12 with render kernel.

http://pastebin.com/R0M5MA8A
[BetterBatteryStats] W&Man:
Hi,

No, the problem is still here.
[BetterBatteryStats] chamonix:
Please post a dumpfile, a logcat (with BBS debug advanced prefs enabled) and a short description of what you are seeing / missing and I will have a look. Ideally you should try accessing the alarms from raw stats as it makes the analysis easier. Also I would be interested in knowing if enabling the 'Alarms using api' changes anything. If yes that would point to a change in the format of 'dumpsys alarms'. If this is the case the result of 'dumpsys alarm' would be helpful as well as this would point to a different format requiring changes to the parser and some testing.
[BetterBatteryStats] amjath:
Can someone help.

This is latest BBS

http://pastebin.com/E8J2WZWP

7% drain in deep sleep.

Amplify says it is because of RIlJ wakelock
[BetterBatteryStats] parkedraccoon:
All right, this one's stumped me. It's seemed to be with me both on BlissPop and AICP, and on both PA and Banks gapps. It's the *alarm* wakelock, on multiple apps, including Greenify. I have a lot of wakelocks limited through Amplify, and I also have Greenify running. I'm noticing the *wakelock* process on all the apps that also have *alarm* going on them, and I also noticed there's somewhat less apps with the *alarm* today, when the only thing I changed was adding a few more things to Amplify.
[BetterBatteryStats] aitvariux:
Am I doing something wrong or I need to write to other thread to figure out battery drain from logcat?
[BetterBatteryStats] chcknsld:
Install it one more time after the reboot.
[BetterBatteryStats] tangcla:
Hi [MENTION=1330150]chamonix[/MENTION],

I've tried enabling alarms via API, and viewing the 'raw stats' for alarms still doesn't show any detail as to each of the wakeups.
[BetterBatteryStats] chamonix:
Then I am afraid we need the full programme.

Please make sure to go back to non-api, enable the debug logging, go the raw stats - Alarms and save a dumpfile + logcat.

After that open a shell, run 'su' and 'dumpsys alarm > /sdcard/alarms' and attach (no spoiler as this will change certain caracters) /sdcard/alarms with the rest. With all that info I should be able to diagnose and test.
[BetterBatteryStats] tangcla:
First two files attached.

I ran into a problem doing the shell from adb:

shell@trlte:/ $ su
su
root@trlte:/ # dumpsys alarm > /sdcard/alarms
dumpsys alarm > /sdcard/alarms
Can't find service: alarm
root@trlte:/ #
[BetterBatteryStats] sonygoup:
Getting the grey screen just after installing it as a system app on my One Plus ( this app has no functionality)

Anyone knows how to fix
[BetterBatteryStats] chamonix:
wow!

that explains the missing alarm stats.

could you please attach a plain 'dumpsys'?

edit: weirdly enough I see Alarms data in the dumpfile.....
[BetterBatteryStats] tangcla:
How do I do this?

If it helps, it's a Samsung Note 4 with stock Lollipop 5.0.1 firmware. It did this on my Lollipop S5 too (I think it was fine on Kitkat).
[BetterBatteryStats] Perseus:
That's an option from within the BBS. Look under Sharing Options. Otherwise you can use Syslog if you're more comfortable that way.
[BetterBatteryStats] RogueCoyote:
Hi, I previously had BBS running great on CM12.1/Lollipop 5.1 but after updating to 5.1.1 I keep ending up with the screenshot attached. I gave it SU permission when it first installed but then after installing as system app and restarting I get this screen. Could this be an SELinux issue? I think it might have been changed in the latest update to the ROM i'm using. I have uninstalled BBS, wiped cache, and re installed a couple times with the same result. Any advise on how to fix this or what other info or dump files I can provide to help fix this would be greatly appreciated. Thanks!
[BetterBatteryStats] :
Please read the thread ... http://xdaforums.com/showpost.php?p=60687497&postcount=28370