yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] xelra:
This tremendous count isn't normal at all. At that count I would actually start looking into my net stats and check whether it's become a botnet.

You probably need to do that from a Linux pc and a network chip that supports promiscuous mode.

If all that chatter is dns related your network is most certainly infected.

OK, I actually did a bit of reading for your devices specifics. I'm guessing you are using a Samsung ROM for your Galaxy S3.

It seems like it is a device specific unresolved issue to have the 3 wakelocks multipdp, secril-fd and battery-monitor. I don't think there's anything we can do about it right now. You should go to your ROM thread with that.

Maybe check if your carrier supports fast dormancy. If not, deactivate it. Also try locking your phone to 2G. Maybe that will help a bit.

Apart from that your stats look good. You could still optimize Tasker.

Maybe chamonix has more insight into this problem. This is not an easy one.
[BetterBatteryStats] jeffreii:
After reading the great explanation I was thinking the high count was because I've had wifi on since I got the phone nearly 3 weeks ago and this was the first time I turned it off? Does that make sense?

Also on another note, as stated I've been using GSAM (Badass) Battery Monitor along with BBS. GSAM is reporting that in my latest test, a 25% drop in 2 hours (while mostly unused) had 6 minutes of screen on time...and it is linking that 6 minutes of screen on time to 45% of the drop (11.25%). It's hard to imagine that my screen, though large on the GS3, can use 11% of my battery alone in just 6 minutes of use (50% brightness setting). I'm beginning to wonder if this isn't a calibration or battery failure.

Another thing worth noting is that this started happening last week and a reboot would fix for a day or two. Now it seems to be getting progressively worse with the reboots only solving it for hours at a time.

Any thoughts? Thanks again.
[BetterBatteryStats] r29:
I am getting extremely high NetworkStats partial wakelocks.

I have maps cleared cache/data and forced sto..all three network gps stuff uncheck.

I'll post my dump file tomorrow after I let it run sometimes.
[BetterBatteryStats] fone_fanatic:
I have an issue where when I switch between Others-Kernel Wakelocks-Partial Wakelocks etc it will stay on Computing... for a really long time. But if I change the orientation of the device from portrait to landscape, it shows up right away. I've cleared the cache & data for BBS followed by an uninstal and reinstall and that seems to fix it for a while, but within a day or 2 it will start happening again. Any ideas? I'm running AOKP on my SGH-I777.

Also what app do you guys recommend for freezing apps and preventing apps from starting up on their own on reboot or when states (wifi on/off, 3G to HSPA, etc) change?
[BetterBatteryStats] yhrn:
Thanks for, yet another, detailed explanation (more KB material here?).

What still confuses me is the high counts I get for "sec-battery-monitor". What I'm getting at is that the battery cannot reach a critical level many times during the measurement period and the battery capacity couldn't change that many times (unless reported at a ridiculously fine grained level) so either my battery temperature changes like crazy (indicating that there is something wrong with it?) or it's just a side effect from something else waking the phone up.

The former would fit better as the wake count is almost the same as the count. (Or have I misunderstood what these counts mean?) If it is the latter, wouldn't that mean that this wakelock is grabbed before the wakelock that would identify the real reason for the wake up thereby masking the real reason? If that's possible then wouldn't that mean that using the exclusive/discrete KWL reporting model (as I am) the real reason for the wake up might not be present in the stats at all?

I'm turning of exclusive KWL during the day just to see what it looks like.
[BetterBatteryStats] Greedyfly:
That kind of ties in to what I was being told on another thread. As such I have downloaded and am preparing to flash the new Omega Rom

which is based on a BLFB as opposed to the Samsung ALEx ROM which I am currently running. I'll flash and then meantime report back.

As for Tasker I am having some issues getting it to actually switch WiFi on/off using anything other than Location. Have just set up a new 'Cell Near' profile that has turned it off this morning so I am hoping that it'll turn it back on when I am home and all will be ok but that's a little frustrating.

Will post back BBS later once reflashed.
[BetterBatteryStats] camspy:
I installed LBE Privacy Guard app and set to monitor all apps that have access to ACCESS_COARSE_LOCATION, it had to notify me when an app tries to get permission to it so I could allow or deny it. The interesting thing is that it didn't notify me and I already use it for 1 day.

I tried aLogCat app to filter logs by android.permission.ACCESS_COARSE_LOCATION but it didn't show anything.

Could you explain how to inspect XMLS and "permissions" - what tool is that?
[BetterBatteryStats] skivnit:
http://db.tt/QCaxDHAc

Someone please look at my stats

Sent from my GT-I9300
[BetterBatteryStats] xelra:
Have you read the Location without frustration article in the Tasker Wiki?

There are also a few pre made profiles for turning off and on wifi. Look at what was done there and how.

In general you should only use cell near for turning on wifi. Once connected it needs to stop polling. Then just let it turn off wifi on disconnect (you can use wifi conditions for that since wifi is on in this state). Start looking for cell towers again, when wifi is turned off again.

Once you made a "good" profile, Tasker should be easy on the battery. If it's still too much, you can tune its settings and reduce the polling count and stuff like that.
[BetterBatteryStats] Greedyfly:
Xelra. Thanks for your help with this.

I did look at the Wiki home page and imported a profile that was supposedly easy on the battery (link) but I found it difficult to follow. http://tasker.wikidot.com/low-battery-usage-wifi-enableing-profile-using-wifi-near

I then found this one which I could import (after I worked out how) but alas I got home last night and it hadn't turned the WiFi on. And that is becoming a theme....Tasker not actually turning the WiFi on unless I am using Location Near.

http://tasker.wikidot.com/yanawa

Any advice on these?

Further to my ROM point earlier. I have flashed that and the Phenomenal 2.0 Extreme Kernel and I hope to post some battery stats later today hopefully eliminating the problems from the stock.
[BetterBatteryStats] beatmania82:
My samsung captivate running AOKP rom is losing alot of battery. I ran the BBS overnight and here is the log. Could you please help me to figure out?

I have data/sync on.

2 gmail, calendar sync.

http://pastebin.com/RAhpygki
[BetterBatteryStats] ziotempa:
battery check

Hi, I think I have some problems with my phone, I mean I think I have too little battery life.

Just a little background: I'm on Omega 7.1 with Siyah 1.2.6 kernel

I'm under H3G Italy and use NELE4 modem

I think that's all, I attach the dump file and and image of today's battery consumption. Oh, this morning I've played about 40 minutes with a new game I bought... anyway that's not the problem. Even without that, usually during the night I lose more than 10% in 7 hours... it seems too much to me).

Anyway this dump has been done from about 7AM this morning

Thanks for your help

Vincenzo
[BetterBatteryStats] chamonix:
Could you please provide a logcat when it happens? It may be a refresh problem or related to the knowledge base cache update running into a unhandeld error.
[BetterBatteryStats] Insomaniac10:
Hi guys, I was wondering if someone knowledgable would be willing to look over my dump and see if they can understnd why myphone des not seem to enter deep sleep? Im sorry but my knowledge on this is almost non-existent, and i didnt even know this app existed until yesterday.

https://www.dropbox.com/s/zb6nctwkvb4djql/BetterBatteryStats-2012-07-17_193310771.txt?m

It would be greatly appreciated...not having deep sleep is a nightmare. Thanks ahead

I have a Sprint GNex running AOKP-M6 w/ Lean kernel
[BetterBatteryStats] Karpfenhai:
Your pocket cloud service (wyse) and this strange twofourfourtyam whatever app are tour main culprits.

Get rid of them first, then reboot and create another clean idle dump (alarms are missing)

Read the op with care!

Tapatalked from my Samsung GT9100
[BetterBatteryStats] wizard83:
Hi guys,

on my galaxy nexus (jb) do you know what is mean "audioout_2"?

Thanks!
[BetterBatteryStats] chamonix:
I have a bug with ALTitude related to compat. with JD and have to focus on that right now. Once I'm done with that I'll release the next RC with "discrete" KWL detect and a clean state for the logging (full trace as pref). I'm trying my best on the ANR when the watchdog is active and a fast off/on freezes the BBS dialog for a while but I'm not sure if a fix is that easy (concurrency is never simple).

Stay tuned and sorry that I have to take a little break from you guys

Edit: possible fix was pushed so hopefully I'll be able to switch my context back to BBS tonight
[BetterBatteryStats] Nightshadow931:
I have to quote myself since nobody had seen this. :P

It happens every time actually, seems like a bug to me.

Any clues ? :)
[BetterBatteryStats] phishie:
Hey chamonix, would you mind take a look at my log when you get a second? I'm having a hell of a time trying to figure out what is causing my NetworkStats / AlarmManager partial wakelocks. I've eliminated quite a few wakelock violators over the past few days tracking with BBS and GSam battery monitor but can't crack this NetworkStats / AlarmManager nut.

Some context for this log: I dumped to file only after an hour or two so it's not extensive but still pretty indicative of the behavior I've been observing over the past few days. Typically my Awake Time is 2-3x that of my Screen On time and NetworkStats and AlarmManager are my leading Partial wakelocks. I'm running with an AT&T HTC One X in true 100% stock fashion.
[BetterBatteryStats] superbobup:
For anyone running JB or Google Now on ICS, do you know how to reduce the overhead of the Network Location setting? You need it enabled to use Now and I've found it useful for Voice Searching local things, but it's the biggest battery hog on my phone. Any suggestions anyone? :)
[BetterBatteryStats] fone_fanatic:
Ok will do. I wiped BBS's cache and data followed by an uninstall & installed RC8 right after that post.
[BetterBatteryStats] xelra:
AlarmManager is an aggregator for Alarms. You need to root your phone to see what those 600 and something wakelocks consist of.
[BetterBatteryStats] Insomaniac10:
Thanks for responding...ill have to learn how to make a full dump....it's my very first time using the app so thanks for being patient with me....twothirtyfour is Locale haha, surprise surprise

Sent from my Galaxy Nexus
[BetterBatteryStats] chamonix:
The problem with this post is:

- the screenshot is so small that I can't see anything on it, just guess a blue bar across the screen

- you did not provide any info about what you saw

- you didn't provide any info on the version of BBS you have

Thanks you for completing that info, it may ba valuable
[BetterBatteryStats] phishie:
Thanks - I'm going to try to do that tonight.

Do you think the NetworkStats is not worth worrying about? It amounts to 1.6% versus AlarmManagers 0.1%. Or do you think they are related?

Also is it worth paying any attention to any of these?

RILJ (Count: 745 - 0.1%),

HtcPhoneSensorFunctions (Dialer) (Count:1279 [Holy **** I didn't notice that before] - 0.0%),

sleep_broadcast (Count: 837 - 0.0%),

SyncLoopWakeLock (Android System) (Count:1272 - 0.0%)
[BetterBatteryStats] Tungstwenty:
Sorry, I missed the post. Here are some thoughts:

PWL's should not be added to KWL's. They are userland WLs and they reflect in a combined way in the "PowerManagerService" KWL.

If you look at the regular/non-discrete KWLs you'll notice that both the total time and the total count of PWLs is smaller than the PowerManagerService entry. This is due to the fact that there are also overlaps in the partial wakelocks engine, the PM Service.

So, you should look at the KWLs alone if you want to compare them to the total awake time. An in order to eliminate the overlapping in KWLs, look at the discrete list.

The fact that the total KWL time (162s) is smaller than the total awake time (616s) might have something to do with the interruptions that don't trigger KWLs, which I posted about here.

While you might monitor the differences in /proc/interrupts before and after, it will only give you the number of occurrences of each of them, not the total time. Also, I think it will include interrupts that occur while the device is already awake doing something else - a good example is the CPU clock ticks for preemptive multitasking.

The total of KWL wc's is 116 but I'm sure the phone woke up a lot more times, although only in 116 of those times did it acquire a KWL after waking up (to make sure it had the time to finish responding to an interrupt asynchronously before going back to sleep).

Well, I think the bottom line is that there will never be a match between the KWL time - even the discrete one - and the total wake time, because of a number of factors:

- The device sometimes wakes and goes back to sleep without resorting to KWLs

- Even when it does use KWLs, there is some delay between the moment it wakes, handles some initial stuff, and the KWLs finally kick in and start counting time. The same when the last KWL is released and it goes back to sleep
[BetterBatteryStats] sewe:
Here's my stats for the last 2 nights.

It sleeps well but can i improve it or should i just leave it as it is?
[BetterBatteryStats] mzaur:
What does it mean when the deep sleep percentage is off? Look at ss. Deep sleep should be higher percent
[BetterBatteryStats] Nightshadow931:
Sorry about that.

Here it is
[BetterBatteryStats] phishie:
Done and done, see attached for my log from last night (post root). To my surprise the battery drain was incredibly low overnight, just my luck when I'm trying to log it.

Most of the log seems self explanatory - I just turned off Foursquare notifications, uninstalled United Airlines app - but the ones I'm not sure about I've listed below:

Do these "android ()" alarms look normal to you?
[BetterBatteryStats] Stolper:
Hey guys,

I hope someone can help me out with this one. I have a SGS II and i'm pretty happy with it, but one thing bothers me. Instead of having screen as biggest consumer it always is my Android system. In the screenshot below it is 58%, but sometimes it goes up to 75%.

I tried different kernels and rom's, but it wont go away. I also tried reading the BBS dump but it didn't clear things up for me. Five months ago i dropped my phone in the water, i was able to quickly recover it and let it dry for around 30 hours. It did work again but i have the feeling that my battery life dropped and the android system "bug" appeared, altough it seems hard to me that this would be the cause.

If anyone could figure this out, or sees it directly from the dump i would be very thankful!
[BetterBatteryStats] razorseal:
Hello, this is the CM10 for galaxy 3... something is keeping my locationservices on like crazy... I have jellybean on my xoom as well, and this is not happening. I was told it could be google now, but I don't believe it because xoom is not doing this with google now (or nexus 7)

any ideas what's going on here???
[BetterBatteryStats] Karpfenhai:
You have way to much wakelocks..

But later..

could you enter this code, next time your phone has fully charged (after unplugging)

*#*#4636#*#*

then tap on battery info, is there anything suspicious?

I think you USB Board may be corrupted due to water, on NON Sammy roms this is not visible by the system UI, on Sammy roms you get voltage to high notifications.

Hit google for this!

This would explain why your phone thinks the charger is still connected and it does not enter deepsleep under a certain amount of charge left.

Therefore AOS has this high amount.

But, Your dump looks not really good..

Maps, Location Service and Sync..

Disable BLN!!

Good luck!

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

Location, Facebook, HD Widget.. its so obvious! Do your Homework man! :laugh:

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

Youre good, everything is fine, 2 mins out of 4 hours! Enjoy your phone!

---------- Post added at 05:12 PM ---------- Previous post was at 05:08 PM ----------

Sync, Facebook gosms and some weird htc specific stuff, repost a dump after rebooting and a certain idle period!
[BetterBatteryStats] razorseal:
problem is, this is the SAME setup I run on my xoom, and it's NOWHERE near this. so I don't believe that. just look at my xoom, i'll post in a sec....
[BetterBatteryStats] Karpfenhai:
Not fully true, it has almost the same excessive amount of wakelocks!

But maybe the Battery is larger, the CPU smaller... The signal reception better ;) Who knows, the setup is worse..
[BetterBatteryStats] razorseal:
perhaps. xoom has a 'passive location collector' and that's at 3m29s. the highest thing is signalcolletor at 3m53s right now...

on the sgs3, it's hitting 48m20s right now for networklocationlocator

I don't see how that can be because of better signal, or bigger battery....
[BetterBatteryStats] yhrn:
Thank you for the explanation. I will try to dump /proc/interrupts at some points but what do you think is a reasonable approach? Taking one snapshot and then leaving the phone idling for an hour or so and then take another one? Maybe a BBS dump for the same period (using a custom ref) would be useful as well?
[BetterBatteryStats] chamonix:
Thanks for reporting. That bug was fixed in RC8 (see post #2 for changelog)
[BetterBatteryStats] razorseal:
chamonix, could you have a look at my galaxy 3 one when you get a chance? I just don't see if it can be the apps i'm using because my other device is using them, and it's not causing this many wakelocks.

they are both alpha builds though, so I guess it can be related to that as well...
[BetterBatteryStats] chamonix:
Release 1.9RC9

New RC is up, check post #2 for the changelog.

Happy testing!
[BetterBatteryStats] chamonix:
Sure, just port the dumpfile and e'll have a look
[BetterBatteryStats] chamonix:
I am not sure I understand your question. Deep sleep would be higher if your device would sleep more...
[BetterBatteryStats] wizard83:
Chamonix, please, can you take a look at my report?

Thank you very very very much!
[BetterBatteryStats] Tungstwenty:
The interrupts list does not provide directly useful information, at least I don't imagine any good conclusion just by looking at a delta from one moment to another.

What it might help bring some insight into on the issue you mentioned, where there were lots / too many wakes caused by the battery KWL, is if that snapshot difference is compared to a "normal situation" (???).

If you take 2 snapshots 1h apart, for instance, and then do the same again on another phone or in another period where the battery KWL for some reason is much quieter (assuming it's not always like you said), comparing the 2 increments could bring some clues - if there's a big difference on one of the IRQs counts that could point to one of the hw devices ...
[BetterBatteryStats] uf21:
Hi,

I made a dumo file off bbs. Can you please look at it and tell me whats causing so many wake-ups. I also Attached a screenshot showing how many wake-ups I had overnight. I lost 19% overnight cause of all these wake-ups.

Thanks.
[BetterBatteryStats] chamonix:
Leaving wifi on causes the biggest part of your Wakeups, Facebook is #2
[BetterBatteryStats] jeffsf:
I would like to be able to

Get into bed

Unplug my charger from my phone

Have BBS do a "dump 'since unplug' to file" at 06:00

Have my phone's alarm ring after BBS has dumped the night's information

This way I can see an "untouched" battery discharge, without the corruption of my wake-up alarm and fumbling to find BBS.

Is there a way to do this already? (I can handle setting my wake-up alarm ;) )

Is there a way to trigger the action from cron?
[BetterBatteryStats] yhrn:
BBS has a Tasker plugin that dumps to file. So using that you should easily be able to configure what you want.
[BetterBatteryStats] uf21:
Thank you.

Would leaving wifi off but 3G on be better?
[BetterBatteryStats] yhrn:
Cool, this sounds like a job for the BBS and Command Center Tasker plugins. I'll make a Tasker profile that executes once an hour and do the following and see if it leads to anything interesting.

BBS: Dump to file (since custom ref)

Commad Center: redirect /proc/interrupts to file (with timestamp in filename)

BBS: Set custom ref
[BetterBatteryStats] chamonix:
In your case yes, a more elegant way to solve the problem, assuming you can control the access point, would be using wireshark to find the source of traffic waking up your phone and fix it.
[BetterBatteryStats] uf21:
Thanks, I will try wireshark.
[BetterBatteryStats] jeffsf:
I'd prefer to know if there is an intent that can be called through # am start <INTENT> or the like. The source code that I can see is pretty dated. While I understand the attraction of Tasker, I don't have enough of a need for its features to purchase for this single objective.
[BetterBatteryStats] jeffreii:
Still troubleshooting my issue and found kernel wakelocks: "bam_dmux_wakelock" and "smdcntl0" as possible culprits. Does anyone know they do? Thanks.
[BetterBatteryStats] mzaur:
If you look at the screenshot here do you see that it says Deep sleep 3hr 14m of 3hr 21m ? But it says 87%. It should be 96.3% (11668 ÷ 12112)... So I don't understand where the 87% comes from?
[BetterBatteryStats] asg.srtw:
I have a problem with WifiStateMachine, on some point it starts to behave weird, keeps my phone awake, can You guys tell me whats wrong and help me fix it?

Screenshots and dump attached.
[BetterBatteryStats] Lownita:
Hi

I could use some help! I am loosing about 11% in 8 hours screen off time. Bit too much isn't it? I am on CM9 RC2 with siyah 3.4 (exclusive wakelock stats enabled in extweaks).

I can't find any suspicous wakelocks by myself, but as you can see, the phone was awake over an hour without being touched. Latitude is not enabled, although maps caused a lot of alarms. Please check! :)

I find it a bit suspicious that facebook app/messenger did not cause any alarms, but I guess they don't show up because of exclusive wakelock stats enabled in extweaks?
[BetterBatteryStats] Rob2222:
@Tungstwenty / All:

I have made another exclusive/non-exclusive comparison.

Can it be that I have 217s multipdp KWLs in non-exclusive but at the same time adding _all_ KWLs in exclusive mode just gives 171s?

That wakelock time does not equal wake time is clear now.

But according your description of the exclusive mode, I assumed, that the overall amount of time of KWL in exclusive mode should be >= than the biggest KWL in non-exclusive mode. Is that right?

OR ... which maybe also could be ... in this sample the non-exclusive dump has rough 1 minute more KWL time, cause I needed 1 minute more to create the dump (switching mode in Extweaks).

Which means for 1 minute more screen on time I got rough 1 minute KWL time by multipdp. Don't know how the chances are, but well, could be.

Best Regards

Robert
[BetterBatteryStats] wizard83:
Sorry for quoting myself, but anyone can help me for my Wakelocks? Thanks!

Inviato dal mio Galaxy Nexus con Tapatalk 2