yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] diesel.:
First and foremost I'd like to thank the creator of this app. Second, I have a Motorola Photon unlocked/rooted on 2.3.4 as you can see from my log. Up until recently I was getting 2 days+ of battery life. My phone got a little water in it and I believed it to be dead. I got it dry and proceeded to turn it on; it seemed to be dead but then eventually it stuck on the boot screen. I can't recall exactly what the failed message was but I was able to flash another sbf on it to revive it. I have almost nothing of note installed on it to cause my drains. GSam and BetterBatteryStats, along with Autostarts. I have frozen a lot of things that have seemingly been deemed safe to freeze with Titanium Backup Pro.

Took this log overnight and while I didn't get a chance to take any pretty screen shots I think there's some good info in here. Lastly, I'm trying not to bloviate so much but after that fateful dip my phone took I purchased two batteries from Amazon. I've tried one of said batteries along with the previously moistened battery with same results. I cleaned the contacts with alcohol as well.

tl;dr; MoPho with 2+ days battery life. Phone attempted electronic suicide via water. Dried it out. New sbf. Tried wet battery and new (oem) battery. Now getting ~12-14 hours a day. ~40-50% drain over night.
[BetterBatteryStats] a1exus:
A big "thanks" goes to Sandy. This is my BBS dump, if there are any suggestions on what I can do to improve my battery life, I'm all ears!
[BetterBatteryStats] krishs3:
Techies,

This is my BBS dump. Can you please tel me what went wrong.. I lost around 30%-32% of juice in a span of 4 hours midnight. Every 2 mins once am getting a msg that Lightflow has been given superuser permission to read LOGS. ( i don't know why its coming again n again).

Please help me with knowing which is the culprit in draining my juice. Ill freeze that or uninstall using Titanium.

My awake time is 5 h 6 m vs screen On time of 30 m 19 s.
[BetterBatteryStats] haarsh:
Hi,

I am posting a DUMP taken from my vibe :) and added screenshots of BBS for further details. Please let me know what I can do to improve

Statistic Type: (3) Since Unplugged
Since 6 h 11 m 26 s
Deep Sleep (): 5 h 53 m 6 s (21186 s) Ratio: 95.1%
No Data Connection (): 6 h 11 m 26 s (22286 s) Ratio: 100.0%
No or Unknown Signal (): 6 h 11 m 26 s (22286 s) Ratio: 100.0%
Awake (): 18 m 40 s (1120 s) Ratio: 5.0%
Phone On (): 34 s (34 s) Ratio: 0.2%
Screen On (): 28 s (28 s) Ratio: 0.1%

Thank you

tc

edit: it says

[B]No or Unknown Signal[/B] (): 6 h 11 m 26 s (22286 s) Ratio: 100.0%

BUT I was on network (Airplane mode was OFF all the time even when charging)
[BetterBatteryStats] xelra:
Light manager and tasker.
[BetterBatteryStats] Hilmesh:
Hey Karpfenhai,

Can you please take a look at the dump and advise if it is OK or any improvement possible. I have tried to use my phone differently by keeping Wifi ON overnight along with Sync OFF and Wifi Sleep Policy set as NEVER. Whatsapp, Skype & IM+ Pro Are running in the background.

Before going in for this i had already set my phone IP address settings to Manual and made the beacon interval in the router as 150.

Hope to hear from you soon. Thanks.
[BetterBatteryStats] Karpfenhai:
Just disable tasker and this koo light manager app!

The test is data traffic related, post another dump afterwards.

Tapatalked from my Samsung GT9100

---------- Post added at 07:15 AM ---------- Previous post was at 07:12 AM ----------

Your dump looks decent, just change your modem and maybe the kernel.

Ignore the no signal, it doesn't count correct on all device.

Tapatalked from my Samsung GT9100

---------- Post added at 07:18 AM ---------- Previous post was at 07:15 AM ----------

Its your wifi, the only culprit, maybe you should setup a dedicated AP only for your mobile? I mean routers are cheap..

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Hilmesh:
Hey Thanks. So apart from Wifi it Looks OK. I will now try the same thing with 3G today to see the difference. Separate AP only for mobile ?Hmmm Yes routers are cheap , let me see. Tomorrow i will post the only 3G dump and if it turns out to be good then i will leave it as it is else go for separate AP.

Thanks :)
[BetterBatteryStats] haarsh:
Thanks. I disabled MAPS using autostarts and also using KB5 modem. I doubt the signal bar (display under settings -> Battery -> and below the graph) is displayed green when signal streangth is OK and I gray means poor/bad signal.But, I didn't notice any instability of the signal. Signal bars are gray all the time when I am on 2G. But, when I switch to 3G it displays as green. All bars are filled sometimes and sometimes NOT.

I was on KA7 after flashing the ROM but it drained da battery as hell. I was on KB5 when running froyo and I flashed that. If you can please can you point some modems (links are not required. I'll search) to try. :) I am running ICS

Thanks
[BetterBatteryStats] Hilmesh:
KI4 is really good. try it
[BetterBatteryStats] Karpfenhai:
I would but i dont own a vibrant so i dont know which modem to suggest, i would read the desired thread and decide on other users experience..

Sorry
[BetterBatteryStats] Hilmesh:
Hey haarsh sorry i did not note your model and suggested. Please don't follow my post. As adviced by Karpfenhai check in the desired model thread. Sorry
[BetterBatteryStats] taz1458:
Here is the idle dump.

http://db.tt/DC1IceHK
[BetterBatteryStats] Tungstwenty:
Slide2Wake drain

For all techies and curious ones in general :)

The latest Siyah S2 release (5.0) introduced the slide2wake feature, something that was already available in some of the other kernels (not only on S2 AFAIK).

As a Siyah user, only yesterday did the question pop up: "what does it imply in terms of battery drain and BBS outputs?"

I thought I'd just leave here a few pointers since it could be useful for being aware that this type of hidden drains, which generally fall under the "there are no KWLs, alarms, etc. but I sill have a drain of X overnight" scenario.

In a nutshell, activating slide2wake makes the deep sleep transition not fully shutdown the touchscreen sensors, much like the modem, wifi chip (if active), etc.

There will therefore exist a constant battery drain to keep that sensor active even during deep sleep.

And, what's even more important from a BBS point of view, all that is completely invisible to the measurements of virtually all apps, BBS included. I doubt there is even any way to know it from inside the kernel, much like it's impossible to know (at least directly) how much power loss was due to the network signal fluctuating, how much due to WiFi, etc.

For a few pore details on this you can check this post.
[BetterBatteryStats] Rob2222:
@Tungstwenty:

Sounds like a nice power drainer if you have Slide2Wake enabled and you put the device in a pocket.

In addition to the constant power drain for the sensor, I think it will regularly (/permanently?) create wake_locks, too, by the gesture detection if you have the device in a pocket... Huh....

BR

Rob
[BetterBatteryStats] Karpfenhai:
Ty very much TT, but don't you think the surface linger will remain active then?

What's in the dump you made while s2w on?

Do you also have a logcat?

Tapatalked from my Samsung GT9100
[BetterBatteryStats] ZunRob:
No one? I'm quite curious about the source of:

GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 12 m 1 s (721 s) Count:836 0,6%

ConnectivityService (Android-systeem): 8 m 32 s (512 s) Count:839 0,5%

AlarmManager (Android-systeem): 7 m 23 s (443 s) Count:2367 0,4%

But also what is causing the DHCP to be this large...
[BetterBatteryStats] Tungstwenty:
Only if you manage to perform the unlock gesture involuntarily, which is somewhat unlikely I think (but not impossible). Only then will a KWL be very briefly held while the power is brought back up (check my detailed post), but then again the relevant drain will be the screen being on for a while until it times out and the device eventually goes back to deep sleep.

BTW, I think Gokhan added an additional check on Siyah so that the wakeup is only performed if you swipe from left to right without too much vertical variation. If you start in the top left and instead of a straight swipe to the top right do a sort of a V instead, finishing in the top right as well, it won't wake up. The likelihood of involuntary wake is lower.

---------- Post added at 12:33 PM ---------- Previous post was at 12:15 PM ----------

There will be no differences at all either in surfaceflinger, logcat, etc.

This is done at the hardware level: not powering down the sensor when the system goes to deep sleep (many of the sensors / chips do power off) and the CPU shuts down; plus, the IRQ for touch-triggered interrupts is kept on and that's the part that tracks whether to fully wake up or not.

In userland the only visible differences will be:

- KWL occurrences (the name will be something like 's2w' or whatever), but *only* if the wake gesture is used; even there, it will be a lock followed by an almost immediate unlock, and the device will then be awake anyway with the "main" (invisible, time=0) KWL which correspond to the time where the screen is on.

- in /proc/interrupts, the entry for the touchscreen IRQ (mxt224_ts for the S2) will increase the counter for all touch activity even when the screen is off, whereas previously it would never fire up unless the screen was on.

This is irrespective of the 'truly deep sleep' state; the screen can be off and the cpu running, and in fact whenever interrupts occur they will wake up the CPU (at least), do some stuff, and if no KWL is locked it will go back to deep sleep without any BBS-visible reason other than cpu usage. Only /proc/interrupts and the CPU stats will reflect those brief wakeups, but not easily traced to a certain feature such as s2w, modem, wifi, ...

BTW, I monitored the average drain per hour using this app, to see the elapsed time after each 1% drop. I didn't use BBS dumps for this. But I'm confident that my response about BBS, surfaceflinger and logcats still holds :)
[BetterBatteryStats] drumhitz:
What is watchdog?

Hi all..

Been having this issue with supersu always granting access to BBS whenever i unlock my phone.

Tried searching for solution. And happened that someone told me to set off the watchdog in BBS.. Yeah , it did solved the problem. BUt i wonder what is watchdog means?

setting watchdog off will affect anything in BBS?

Thanks guys
[BetterBatteryStats] Tungstwenty:
Just look at the first page of this thread and you'll find the answers.
[BetterBatteryStats] superbobup:
Hi TT!

We have a similar application for slide2wake on the GNex and it works the same way I think. It loads a kernel module which does some processing when the screen is touched using interrupts. As you said, there shouldn't be any battery drain unless the screen is touched and from my few months of using the app, the overall drain from this feature is quite negligible. Just thought I'd let you and anyone else know in case some start to freak out about it :p:)
[BetterBatteryStats] seanpr123:
delete
[BetterBatteryStats] Tungstwenty:
Mmmmm, either you got me wrong, or I'm getting your post wrong :)

There IS drain even if the screen isn't touched. The sensors will be awake (which is not true on the S2 stock kernel, nor with Siyah with s2w disabled, as is default in 5.0 and always was before that). That's the only way they'll be able to interrupt when the screen is touched.

What I mentioned is that there's no visibility of that additional drain, i.e. there's nothing you can query to know if that additional chip is continuously draining power even with the screen off. IF the screen is touched with the screen off, you might get some glimpse of activity by seeing the interrupts counter being increased, not more than that. But the drain will be there permanently.

BTW, you're talking about the GNex stock kernel? Perhaps only at the bottom part of the screen, the "soft" buttons?

Or is it a custom kernel with this particular feature?
[BetterBatteryStats] superbobup:
Ah I'm probably wrong :p

So you're saying that the drain is always there (due to the sensor being on) but we can only observe it based on the interrupts counter as there is probably no other way to view it

I think interrupts and such are out of my knowledge scope, but I'll try to explain from how I think the app works. The app I'm talking about (called PGM Nexus in the marketplace) uses interrupts for the slide2wake feature. If I remember correctly, the app doesn't always keep the touch sensor on (though I'm not sure if this is true) so it shouldn't drain much battery.

To be honest, it's getting a bit over my head (I don't know any of these commands, only very basic ideas) but the thread for the all is here http://xdaforums.com/showthread.php?t=1721895 and the dev may be able to fill you/siyah in more :) just wanted to see if the implementations were different/can help each other

Also, it's not built into the kernel (stock or custom). The kernel is compiled with a config turned on (it's in page 4 or 5 of the thread I think) and the app is then able to work. It can work anywhere on the screen (softkey or no soft key) and has features like slide2wake, slide2screenoff and even slide2nextmedia :D

I hope any of this helps and that I'm not cluttering the thread :p
[BetterBatteryStats] taz1458:
Could anyone take a look at this please and make sure it's fine? Thanks
[BetterBatteryStats] Rob2222:
Hmm. When touching the screen, the device needs to check if its the S2W gesture OR not.

So this check can be made while the device is in deep sleep?

I assumed that for that check itself the device must wake up (I thought you need a running cpu for that check).

BR

Rob
[BetterBatteryStats] superbobup:
To follow up on my last post, this is what I found on page 4 of the pgm thread:

Additionally, here is the explanation for the digitizer/touch sensor:

I hope any of this helps explain since I can't :p:D
[BetterBatteryStats] Tungstwenty:
That's where the interrupts show up. If a physical component is in a "semi-awake" state, it will be able to raise an interrupt that will wake up the CPU and run the IRQ (driver routine) to handle the stuff sent by that hardware device. That routine can either do something basic and let the CPU go back to sleep (device deep sleep) or it can actually wake up the device, making the several drivers bring the respective hardware components back to full power.

In this particular scenario, touching the screen will briefly awake the CPU to run the IRQ code and go back to sleep, but after some touch sequences the IRQ will trigger a full wake up that will bring the full power back up, including the screen.

Unfortunately, /procs/interrupts does not distinguish the IRQ executions that started while the device was deep asleep versus while it was already awake. I still haven't given up hacking the kernel to expose those granular metrics, out of curiosity :)
[BetterBatteryStats] Rob2222:
Do you think/know how much drain you get, when having S2W enabled and having the same time the phone in a pocket which leads to continously touches on the screen?

In this case at least the cpu fires up regulary, right?

I could imagine, that even when its not a full wakeup this is a good drainer, or?

PS:

Made my day. :laugh: :good:

BR

Rob
[BetterBatteryStats] kevindd992002:
I'm not sure what I did or install in my phone but it is having excessive drain. About 5% in about 30 mins. Here's an idle dump and logcat taken overnight:

http://db.tt/Bj32QNOv

http://db.tt/DouPvPjP

Please help.
[BetterBatteryStats] superbobup:
Even if it's in your pocket touching your fabric, it shouldn't register/allow the interrupt since fabric probably wouldn't show up as a "touch". For example, trying to scroll with gloves on often doesn't work because it needs the touch to be skin-digitizer (well, skin may be a generalization but I think you get what I mean) and that shouldn't happen if it's just idling in your pocket :D
[BetterBatteryStats] abcrndm:
anyone have any thoughts on this? i can't find anything on these wakelocks on google.
[BetterBatteryStats] wolfenn:
can you help me with this?

thank you very much!!
[BetterBatteryStats] Rob2222:
You have to disable fast dormancy.

Try this app:

https://play.google.com/store/apps/details?id=com.gokhanmoral.fastdormancytoggle.i9300&hl=de

Should work on SGS2, also.

If not, try dial *#9900# and disable FD.

But the linked app should be the way to go.

BR

Rob
[BetterBatteryStats] danielckw:
Can somebody tell me what does the widget 1x1 representing?

It contains one green bar and one battery icon , but i don't know what do they mean, and i cannot found out where is explaining it.

Thanks!
[BetterBatteryStats] It_ler:
In post #3 there is a short description, a link to the online help and this picture for the small widget => https://github.com/asksven/BetterBatteryStats/blob/master/BetterBatteryStats/graphics/Doc_SmallWidget.png
[BetterBatteryStats] Karpfenhai:
You again!! ;P

As first measure, disable all autostarts from Ebay App.
[BetterBatteryStats] Karpfenhai:
After disabling fd, please update to the most recent version and provide a clean idle dump, tante grazie.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] superbobup:
Thanks TT! That makes much more sense now :thumbup:

If I understand correctly, without s2w, the TS sensor is off and touching the screen won't do anything. With s2w on, the TS sensor is always running and touching the screen will cause an interrupt. This interrupt can either be ignored (CPU sees it and goes back to idle) or the CPU can do something with it. In the case of s2w, the CPU may choose to ignore the interrupt unless the specified path has been swiped, only then will the CPU wake up and perform some action.

The biggest battery drain here comes from the TS sensor which, at least on the gnex, seems to be ignorable compared to the S2. Overnight, I tend to lose about 0.8% per hour with sync and WiFi on, so I'm guessing the TS sensor has maybe 0.3% per hour on the drain. I think the thread suggested 3-5% extra battery drain in a whole day and for a 10-12 hour day off charger seems about right.

Hopefully I can test tonight in airplane mode and that can give a better idea of the TS sensor drain.

Cheers and thanks for all this great discussion so far :beer::D
[BetterBatteryStats] justinliu:
Can someone decipher what these wakelocks are? Are they the things that are causing faster than normal drain on my N7105?

"mdm_hsic_pm0" (12.7%) 3H19m

"fast_dormancy" (10.6%) 2H47m

"PowerManagerService" (6.5%) 1H42m

"battery-monitor" (4.5%) 1H11m

Partial Wakelocks

AudioOut_2 (6.4%) 1H8m
[BetterBatteryStats] Tungstwenty:
Yes, it's very possible that the touchscreen sensors have different consumption in different devices.

If you do that test, remember to test under the same conditions with s2w and without. If you use flight mode on the next test, it won't be comparable to the 0.8%/h you mentioned. Leave sync and wifi on, or do 2 new tests with everything off.
[BetterBatteryStats] JoeCastellon:
thank you!

Thank you so much for making this available to XDA members!!

I tried buying the app first because someone recommended it on another thread. That thread said something like "search XDA to get it free", but thinking that sounded like piracy (I know, should've known better), I went straight to the Play Store instead. Thing is, my credit card was declined (transaction is still pending though so as soon as I fix this with my CC I'm happily supporting you! :good: ) and then on another thread I read that you actually are giving it to XDA Members :D Now I can start benchmarking my battery to see why the battery life is so darn bad!

How bad? Well I keep reading here and there that people are getting more than a day on their Samsung Captivate with moderate to heavy use, when my battery will drain to about 14% in just under 6 hours. I hope BBS will help me find the culprit and I'll be sure to post it here!

Thanks again!!!
[BetterBatteryStats] rainbow99:
Hi all, for some strange reason, on my note 2 n7105, my better battery stats can't read any data. Any advice on what I did wrong? Or is my phone not supported? Thx in advance for advice.
[BetterBatteryStats] kevindd992002:
Yes Sir :) I haven't had time to optimize my phone yet but suddenly I noticed unusual battery drain compared to before. I guess it's ebay then. I'll try that.
[BetterBatteryStats] StonedEcstasy:
Hi everyone..

I seem to have a weird problem from a couple of days. The network stats partial wakelock is high. Android System seems to eats a lot of battery and is making me go nuts as if the screen wasnt enough. Can anyone help me hunt this down?

GT i9100

RR 2.7[4.0.4]

Dorimanx 7.11

Thanks a lot!
[BetterBatteryStats] Lotteee:
Desperately need help. First time android user.

My battery has been draining quite badly when I'm asleep. Hence I downloaded better battery stats.

Please help me with what I captured! Totally don't understand a thing at all. :(

Thanks!
[BetterBatteryStats] Hilmesh:
Well just from the snapshots it is difficult to make out much. You have Wifi ON for the entire duration. if you read a few posts back you will notice that Wifi usually does not eat so much battery but if there is network issues with router, etc then it may happen. There are steps to clean up the network advised by Karpfenhai like Setting a Manual IP on your phone or allocating your phone MAC to an ip address in the router in short address reservation, then setting the beacon interval in your wifi router to anywhere between 150 - 200. i will try to get you the specific posts.

http://xdaforums.com/showpost.php?p=32569075&postcount=9266
[BetterBatteryStats] rab1412000:
bbs after jb upgrade

hi there can anyone help me decipher my logs?
[BetterBatteryStats] rainbow99:
Hi can any bro help to advise please? Phone battery performance has been poor. Need to install bbs to find out why. Thx
[BetterBatteryStats] hpa88:
I need some help. I noticed an abnormal power drainage during airplane mode, and a high percentage of a "sleep-broadcast" wakelock. Can anybody help me? What is sleep broadcast related to? thanks
[BetterBatteryStats] xelra:
It's hard to tell what's eating your battery just from that screenshot. If you provide us with an idle dump (a dump taken over night), I am sure that we can further advise you.

EDIT:

And please attach the dump file to your post and don't just paste it in plain text. It's just painful to read.

Actually I'm overscrolling all plain text posted dumps and just ignore them. ;)

EDIT2:

Sleep broadcast is the good thing that happens after the bad. It's a symptom and no reason.
[BetterBatteryStats] hpa88:
thank you for your help. Could you please be more specific about this?

Edit: since I am totally noob about smartphones and android, is there a way to know what drainage over night is to be considered "normal"? a chart or something?I own a Xperia U, and I heard that drainage should be, in deep sleep airplane mode, about 1% per hour.
[BetterBatteryStats] xelra:
1% per hour sounds reasonable. Of course that depends on the size of your battery.

One of the first 3 posts of this thread explains how to take the idle dump.

It's really simple though. You charge your phone and before you go to bed you disconnect it. Then in the morning you go to BBS and click on "dump".

The point is that during that idle time your phone is supposed to do close to nothing and approximate 100% deep sleep.

If it wakes, we can see what has woken your phone and identify the culprits.

If you provide us with a dump file that doesn't show idle usage, it might be impossible to see anything useful because of course there are wakelocks when you actively use your phone.
[BetterBatteryStats] umermajeed:
Idle logs here..can someone please take a look
[BetterBatteryStats] chamonix:
As your device is rooted why do you not enable the root features?

What I see is that most of your awake is caused by network traffic so it would be nice to have the network stats active