yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] kevindd992002:
What the?! Why didn't I see that, lol. For some reason, I skip the signature view when I read replies here, sorry.

Anyway, how were you able to get that kind of battery life with the S2?
[BetterBatteryStats] Karpfenhai:
Youre kinda lazy, arent you? ;)

Its all in the Thread ... But For you..

ROM Samsung Stock deodexed LP4 (4.0.3)

Phenomenal 5.5 Medium, Modem right now KH3

2000 maH Battery (Stock Samsung)

Flightmode during Sleep, else 3G on if no Wifi accessible.

No other tweaks beside screenfilter (looking forward to Hilmesh).
[BetterBatteryStats] kevindd992002:
Sorry, with all these info on this thread I tend to forget each info I read. Thanks.
[BetterBatteryStats] iamnotkurtcobain:
why is the alarm manager so high?

Gesendet von meinem GT-I9100 mit Tapatalk 2
[BetterBatteryStats] fuske:
Hopefully someone can help me with this:

I have a problem with the mipi_link wakelock its still on top of the kernel wakelocks and it drains my battery.

reinstalled the phone no luck

removed google talk and google+

running cm10 jellybro with franco kernel (latest nightlys) on my Galaxy Nexus
[BetterBatteryStats] chamonix:
Well here's an update: SignalCollector.ScannerThread seems to be yet another 'feature' implemented by Google. It runs awol on 3G whenever the connectivity is bad. I had a trip by train (a fast one) and clearly saw the overhead.

did Google implement something to map network coverage?

It's a pity Google apps are not designed for battery performance, it sends kind of a bad message
[BetterBatteryStats] chamonix:
Have you checked with cm10 stock kernel?
[BetterBatteryStats] chamonix:
Because of a high alarm related activity, possibly Wakeups. If your phone is rooted and you have enabled the root features I'd advise that you post a dumpfile
[BetterBatteryStats] Noed:
True. My FB app is frozen here. I only unfreeze when I want to post a photo to my timeline, then I prefer the FB app to upload.

Regarding alarms and wakelocks, just disabling FB autostarts doesn't fix it completely, it will still produce alarms. The only way is freeze or unninstall.
[BetterBatteryStats] hristopelov:
So i reverted my phone to complete stock last night, with all bloatware, didnt use Titanium Backup or Gemini, just updated all apps, charged the phone, and let it stay idle for the night while i sleep.

The "Event Log Service" still showed up w hours like before, so i will assume is something normal for 2.3.6 GB version of my phone.

The phone used a lot more battery with all those Bloatware apps, it dropped like 15% overnigt, no use at all, screen turned off, comparing to 3-4% for the same idle standby when i debloat it and stop the autostart on the Maps and such apps.

Heres how it looked:

And heres Dump if anyones interested:

Clean Standby BBS Dump File on Stock w Bloatware

And now on to Freezing like half of the elements the stock 2.3.6 ships with :) if anyones interested of extreme debloating, and list of apps you can delete of the OS safely (the best way to improve your battery - remove bloatware and apps you dont use) let me know, i know all thag can safely be removed...

mybe ill make ScreenShots of the Titanium Backup before i delete, and post them here, so is easyer for users to see which are those elements.
[BetterBatteryStats] Karpfenhai:
Mate, if you plan to stay on 2.3.6, i strongly recommend to switch over to Villain Rom, its fully Stock, only deodexed and debloated plus this event thing is not there ;)

Works great with Phenomenal 4.0 Extreme and served me well 7 Month ;)

Give it a try, plus, one the best devs on XDA made this rom (Entropy and Pulser G2).

Edit: HA ! i've just seen Carrier IQ is enabled on your device, this may be the reason for the Event Log mess!

Its disabled in villain rom, so another plus ;)
[BetterBatteryStats] fuske:
Yes, same thing..

Franco says its normal on a Galaxy Nexus but i dont think it is because some people dont have this isshe
[BetterBatteryStats] hristopelov:
Noo, the Carrier IQ is enabled just cus i left everyyhing stock for one night, all the Bloat. i do delete it when De-Bloat, and "Event Log Service" still shows, it realy seems to be something normal for some devices i guess, it does not takes battery, when i got 4% drop in battery overnight it was running for close to 4 hours.

About the 2.3.6, yeah i like it, probably will stoy on it for couple a months untill Samsung releases the JB for the SGS2, as for the ROM yoh sudgesting, im on T-Mobile, T989, i think you are reffering to another device. im ok w the stock, 23Mpbs DW speeds max i got :) and good battery... will just delete about 90 elements with Titanium Backup and disable Autostart on Maps mainly and 2-3 other apps.

Thanks, atleast now we know, cant get rid of the "Event Log Service" on T-Mobile 2.3.6 Stock ROM. Doesnt eat battery so we just leave it as it is :)
[BetterBatteryStats] cdzo72:
Good afternoon fellas. This is my first time posting my Battery Stats so please be gentle. I usually get pretty good battery but lately I'm losing a couple percents per hour...

Oops, forgot to post info... I'm on Neat UHLPY Lite v3.4 and running DorimanX v5.87
[BetterBatteryStats] N1XM1X:
love this app.. thanks for the hard work
[BetterBatteryStats] Karpfenhai:
In short terms:

-wlan overhead

-greenpower

-bln

-battery monitor widget

Get rid of it, change your kernel :)

Tapatalked from my Samsung GT9100
[BetterBatteryStats] cdzo72:
Hey thanks for replying! Ill have to do some more tweaking with router I guess and go back to Siyah. I already have the router configured for a static IP address with the MAC address of the phone. What I don't understand is why all the wakes with the battery monitor widget and GreenPower... I have the same two apps and the home screen widget on my Streak 5 and it will only lose about 2 or 3 percent in the same time span during the day and 1% at night with networks off...
[BetterBatteryStats] r2go:
Ok I did a newer check.

Here is the file. I know I only lost 9% over night but I try to learn how to get less.

Who can learn me to check and what to do?

http://db.tt/JKYNozcD

Verstuurd van mijn GT-I9300 met Tapatalk
[BetterBatteryStats] esseti:
that's very cool... bazinga..

any idea if we can disable it. i will use the phone a couple of hours more and then check if smt changed. yesterday i had others strange behaviours.
[BetterBatteryStats] chamonix:
Not yet but it's on my list. I have only limited time for a few weeks but will look into it
[BetterBatteryStats] esseti:
in the system setting, under location, there are three options: use gps. let google send anonimous data of wifi & others.. . use location data for the searching.

i removed all of them. let's see.

btw: 4.1.2 is out so going to flash soon :)
[BetterBatteryStats] Miche1asso:
Ok TT. I hope you're still reading this. Obviously this matters to Chamonix too. :)

So yesterday I finally worked on it. It was a bit more complicated than what I expected. The relevant files are the following:

net/netfilter/xt_qtaguid.c
net/netfilter/xt_qtaguid_internal.h
net/netfilter/xt_qtaguid_print.c
net/netfilter/xt_qtaguid_print.h
* net/netfilter/xt_socket.c
include/linux/android_aid.h
* include/linux/netdevice.h
include/linux/netfilter/xt_qtaguid.h
* include/linux/netfilter/xt_socket.h

The files marked with (*) are new versions from the 3.0.x kernel code and I did not actually modified them. It would have been a nightmare to make them fit with the source code for 2.35.6.7. Then obviously I had to change the Kconfig and Makefile in net/netfilter.

It appears to work:

bash-4.1# pwd
/proc/net/xt_qtaguid
bash-4.1# cat iface_stat_all
rmnet0 1 0 0 0 0 696812 846 86999 789
usb0 1 0 0 0 0 0 0 0 0
eth0 1 277496 745 137771 991 60 1 492 6
bash-4.1# cat iface_stat/eth0/
active rx_bytes rx_packets tx_bytes tx_packets
bash-4.1# cat iface_stat/eth0/*
1
277496
745
137771
991
bash-4.1# cat stats
idx iface acct_tag_hex uid_tag_int cnt_set rx_bytes rx_packets tx_bytes tx_packets rx_tcp_packets rx_tcp_bytes rx_udp_packets rx_udp_bytes rx_other_packets rx_other_bytes tx_tcp_packets tx_tcp_bytes tx_udp_packets tx_udp_bytes tx_other_packets tx_other_bytes

But BBS is showing nothing. Chamonix, is it something wrong in my code (for example I am not sure about that stats file. Should it contain any number?) or I need to enable something else in the app? I obviously gave root permission in advanced. Thanks!!
[BetterBatteryStats] chamonix:
I can't tell if something is wrong with your code but for sure an empty 'stats' would explain why BBS shows nothing as I get all the stats (interface, traffic, uid) from there. that is the only stat that matters to me as it's the only one delivering the traffic per UID and so cane be assigned to a package (=app).

This is how BBS works: https://github.com/asksven/AndroidC...sven/android/common/kernelutils/Netstats.java
[BetterBatteryStats] chamonix:
Basically the settings "Wifi and mobile network location" (.... Anonymous data will be collected and sent to google) says it all. And unfortunately there is no way to say: I want cell/wifi location but not those crappy data collectors.

Personally I wouldn't care about Google using my phone to collect data as long as it doesn't affect by battery life. But that crappy poorly designed code does affect my battery so I will do something against it.

Edit: maybe there will be some updates here
[BetterBatteryStats] Miche1asso:
Yeah, as I though, then. All right, I'll check. I am afraid that the empty stats is due to the part I had to comment out due to the xt_sockets not working in 2.6.35.7. Thanks!
[BetterBatteryStats] bdclary:
First, thanks to chamonix for developing this app, and for helping us diagnose our problems.

Context: The phone is a new Galaxy S3 from AT&T and is has not been modified from stock at all (factory image, not rooted). I am quite satisfied with it for the most part, but the battery has been an intermittent problem. Some days, battery life has been acceptable; other days, it drops about 1%/minute. For the past couple of weeks, I've been trying different combinations of settings (e.g., turning off wi-fi, LTE, etc) to see if I can identify/fix the problem, but I haven't noticed a pattern to help me identify the root cause.

How the phone is normally used: The phone is plugged in while I sleep with wi-fi on, and I use its alarm to wake me up. Once awake, I unplug the phone. About 1.5 hours later, I leave the house, drive 30 minutes to the train station, then ride the train 30 minutes to work. During the ride the work, cell signal is lost occasionally as the train goes through tunnels and some stations. As mentioned above, some days I turn wi-fi off during my commute; other days I've left it on in. I do not connect to any wireless network on the commute. Normally, I use my phone most of the train ride: listening to podcasts, surfing (Chrome), reading (Google Currents), and social networking (Facebook, Twitter, and Google+). A secure wireless network is available at work, but the reception at my desk is weak; the phone does not always maintain a connection to the wireless network. When I return home from work, I turn wi-fi on (if it isn't already), and I plug it in when I go to sleep.

And now for the dump. I've downloaded the app and have followed your instructions at the beginning of this thread in order to collect data for a useful dump. This morning the phone was plugged in and complete charged, then I removed the phone from the plug and have not used it for about four hours (I have not turned the screen on at all). When I turned the phone on to produce a dump, I noticed that the battery has only drained to 91% (2.2/hour), so I'm not how helpful the dump will be. So far, the only thing I've done differently today than yesterday is not use the phone after unplugging it. I did take a few screenshots yesterday when the battery drained 45% in 4 hours and 47 minutes; let me know if I should post those as well.

I've got about week left before I can return the phone, so I'd like to determine whether it's a software problem or if the phone is broken and should be returned. Again, I've tried to produce as much useful information as possible. Please let me know if there's anything else I can provide that would be useful.

Many thanks in advance for any help,

Brian
[BetterBatteryStats] Karpfenhai:
Hey there, you are suffering the usual candidates, Maps and a dirty Wifi.

For maps, try to disable all Autostarts and maybe freeze Google Now if you dont use it.

For Wifi, read / search the thread, its mentioned every second day..;)

For you Plummet issue... read this thread, maybe it can help you too?

..or at least confirm the same reason ..

regards.
[BetterBatteryStats] werked:
Ok....I need some help. My battery is being destroyed the last couple of weeks, I can't get through a day. Today, I didn't make it 7 hours before I was down to 2%. Also, doesn't look likes it has slept at all....please, see what you think....

Thanks in advance for any help.
[BetterBatteryStats] Karpfenhai:
Hmmm, did you even read the dump?

Disable google backup, restart you're phone and you will be good.

Update bbs to the latest version and provide another dump.

Regards

Tapatalked from my Samsung GT9100
[BetterBatteryStats] werked:
Yes, I read the dump.... Disabled everything,including Google backup, that wasn't critical.... Nothing, That's why I decided to post here. Thanks for the tip tho. Will update and dump again and see if there is any difference.
[BetterBatteryStats] Karpfenhai:
Nah, something must be wrong with the backup, what does the active app screen say?

Could you freeze these apps?

Just to see if the wakelock still appear afterwards.

Check also the process tab in bbs.

Tapatalked from my Samsung GT9100

---------- Post added at 01:52 AM ---------- Previous post was at 01:50 AM ----------

I think advertising like this is against xda rules, you should be careful!

Tapatalked from my Samsung GT9100
[BetterBatteryStats] irvelmobile:
I'm reporting a strange wakelock by RILJ.. as you can see its counts are HUGE (nearly 1000 in 1hour!), and never stop raising! i can update BBS every second, and they keep growing. This is causing me deepsleep troubles (you don't say?).

Any clue about fixing this? I've tried the reboot in plane mode a couple of times, with no results.

I'm on RootBox 1.8 with DreamKernel 2.7.5
[BetterBatteryStats] Anfa900:
Deleted
[BetterBatteryStats] azrash:
The image is too small, not legible. Why don't you take a dump and attach it here instead? Go to menu-more-dump to file
[BetterBatteryStats] Hilmesh:
Karpfenhai,

KI4 tests are done. Everything remains as mentioned in my post http://xdaforums.com/showpost.php?p=32605099&postcount=9294.

I had to take 2 tests as i lost almost 3% battery due to sudden signal loss and had to restart the phone. One test was for drain from 100% to 28% (almost 2% loss here even though NO SERVICE). Second was from 27% to 3%. The loss of 1% was shown straight after restart. Approx times are below,

Total Awake Time – 3h 28m

Total Screen On time – 3h 8m 8s

Phone Usage – 46m 55s

Good / Medium / Poor Signal – 14m 47s

Wifi On - 6m 3s

Wifi Running - 6m

Bluetooth On - 56s

Battery Loss – 97% and total Standby – 2d 16h 28m 40s

Although the Awake time / Screen On is not better than my other results but then the difference between both the times is the most minimal. Furthermore i feel the 3% -4% lost due to signal loss / restart somehow dampened the figure else maybe could have crossed the 3 days standby time. The only Cons i faced was that the 3G speeds were too low and sometimes dead. But then this Modem is really good as you mentioned. the Loss % for my first test was 1.4%/Hr and during the second test was 1.8% /hr the best i have got till date. (See attached BBS).

Right now i have moved to LP6 (Gives me the best Speeds in comparison with LQ6) with Screen filter (For First Time) set at 64%.

Thanks. :)
[BetterBatteryStats] r2go:
No extra tips for me how to try to reduce battery loss? I know it's not too bad but maybe it could be a little less.

Verstuurd van mijn GT-I9300 met Tapatalk
[BetterBatteryStats] chamonix:
Enable root features in bbs and repost a dumpfile please. Network and Alarms should be your main concerns
[BetterBatteryStats] r2go:
Ok thanks. I wil.

Verstuurd van mijn GT-I9300 met Tapatalk
[BetterBatteryStats] Rob2222:
Hello,

can anybody say me, if WLAN_WAKE

only

fires on incoming packets? If yes, I would use the wake count of WLAN_WAKE to determine, how often a unit is woke by a incoming packet, right?

Can someone confirm this?

This is from a 8h dump, from a (I assume) dirty Wifi network:

2900 wake counts on WLAN-WAKE.

"battery-monitor" (): 53 m 20 s (3200 s) Cnt:(c/wc/ec)3220/0/3220 10,3%
"wlan_ctrl_wake" (): 46 m 15 s (2775 s) Cnt:(c/wc/ec)2790/0/2790 8,9%
"l2_hsic" (): 29 m 18 s (1758 s) Cnt:(c/wc/ec)3339/35/3339 5,7%
"wlan_wake" (): 14 m 1 s (841 s) Cnt:(c/wc/ec)29954/2942/0 2,7%
"alarm_rtc" (): 10 m 25 s (625 s) Cnt:(c/wc/ec)1506/10/46 2,0%
"wlan_rx_wake" (): 9 m 39 s (579 s) Cnt:(c/wc/ec)516/0/516 1,9%
"PowerManagerService" (): 6 m 8 s (368 s) Cnt:(c/wc/ec)1067/0/0 1,2%

And this is from a 8h dump of a "good" network:

64 wake counts on WLAN_WAKE

"battery-monitor" (): 6 m 58 s (418 s) Cnt:(c/wc/ec)412/0/412 1,4%
"PowerManagerService" (): 5 m 21 s (321 s) Cnt:(c/wc/ec)529/0/0 1,1%
"l2_hsic" (): 4 m 18 s (258 s) Cnt:(c/wc/ec)470/66/470 0,9%
"wlan_rx_wake" (): 4 m (240 s) Cnt:(c/wc/ec)186/0/186 0,8%
"alarm_rtc" (): 2 m 39 s (159 s) Cnt:(c/wc/ec)412/121/38 0,5%
"alarm" (): 2 m 18 s (138 s) Cnt:(c/wc/ec)522/4/0 0,5%
"wlan_wake" (): 15 s (15 s) Cnt:(c/wc/ec)6099/64/0 0,1%

I just wonder if WLAN_WAKE count can raise on outgoing packets, too?

But I think, NO, cause if I have an outgoint packet, the unit must be awake already.

Whats the best way to divide a dirty wlan network from a unit with "only" much wlan activity?

BR

Rob
[BetterBatteryStats] xelra:
You should try BVLPE.

rx stands for received transfer.

Your assumption is wrong. The phone also produces wakelocks while active. Even more so. That's why we need idle dumps to determine anything useful.

Just check it yourself. When you actively transfer data, like e.g. downloading apps from the market, your data transfer related wakelocks will rise rapidly. On WiFi that's the wlan wakelocks, on mobile data that's multipdp and RILJ. I think RILJ also on WiFi and all other types of data transfers, like USB, but I'm not 100% sure.

And l2_hsic.
[BetterBatteryStats] Ludus7:
Hi everyone,

after following the advices from this thread, i want to show you my result with my phone. i'm very satisfied :)

Phone: Samsung GS3 stock battery

Rom: Checkrom v5.5 Jelly Bean

Kernel: Phenomenal 4 Medium

i've removed some other samsung bloatware from the rom (like all share and so on) or freeze come service useless (lcd test and so on), like i learned from this thread and some other thread about app that could be removed.

i disabled google now (useless for me and cause me the location wakelocks)

i block autostart of google maps with autostarts app

clean recent apps after use too much apps to have more free ram that i can

i use automatic blacklight, battery saver enabled

i use wifi when i can, data and sync always enabled

i have whatsapp, google, haxsync, facebook and dropbox like account, but only whatsapp, google have "push" enabled and haxsync* do it one per day. facebook and dropbox have sync frequency disabled.

* great app to sync fb photo with contact (hd quality) and calendar (birthday and events)

this is the result

2d 7h 52m phone on

4h screen on

if someone have some other advice, will be great. :good:

the partial wakelocks "media download", maybe it is cauded by the download of 2Gb data app (games file)

i apologize for my bad english.
[BetterBatteryStats] jaydoubleyou:
Is there something I can do about "Event Log Service"? I've tried looking up solutions and unchecking the Google Backup, but it didn't do anything. These are my stats from airplane mode and event log service kept popping up.

my phone is a t989 running cm10 official nightlies 10-10
[BetterBatteryStats] Hilmesh:
Thanks. I already tried BVLPE, and it is good. But surely KI4 turned out the best. :)
[BetterBatteryStats] Rob2222:
Which assumption is wrong?

I know that wakelocks can occur when the device is on. But as far as I know wake counts (wc) can not occur when the device is on already. At least the name would sugget that.

So I wonder if a wlan-wake WAKE-COUNT(!) increase can only be cause by incoming data transfer?

BR

Rob
[BetterBatteryStats] chamonix:
I have a theory about "Event Log Service" but I'll have to write a test app to validate it: my theory is that from a certain amount of debug output from an app this overhead occurs. To validate that I'll write an app writing a few thousand "Log" statements in "debug" mode and a few hundred in "normal" mode per hour and see if the wakelock concur. In that case that overhead would be related to apps not being optimized for production. But again, this is speculation and requires a proof of concept.
[BetterBatteryStats] chamonix:
I'm not specialist enough and certainly no kernel dev but my understanding would be that wlan_rx_wake only occurs when the wifi stack receives a packet that triggers the phone to wake up. Following that understanding a packet of the same kind (e.g. multicast) received while the phone is running would not trigger that kwl.

I'd be interested in this being confirmed (or not) by someone experience enough in that area.
[BetterBatteryStats] chamonix:
Please post the dumpfile as attachement the next time. This reading is not conclusive as you have been using your phone for 50 minutes and made a 20 minutes call. There are still 20 minutes of awake that seems to be overhead but because of the high usage time the cause can not be read. Please read the first posts about providing an idle dump and post again
[BetterBatteryStats] chamonix:
It seems that finally BetterWifiOnOff is gettings stable and complete enough to get released to gplay. I will start another increment on BBS next week so make sure that all your feature requests and bugs are in git. If something is missing please feel free to add directly there or to post here for me to document it.
[BetterBatteryStats] Rob2222:
@chamonix:

It seems that wlan-wake wake-count(!) indeed fires only at incoming packets.

I captured 5 minutes with shark for root and analysed it via cloudshark.org.

I had 3 incoming packets (destination phone, some seconds before no activity) and I had a wlan-wake wake-count 3.

Seems to match.

BR

Rob
[BetterBatteryStats] xelra:
I was just about to test this myself. Thank you for saving me the trouble. Your effort is much appreciated.

I never gave it too much thought up to now and am sorry for giving you unfitting advice about wakelocks, when the question was about wake counts.

I just went to BBS equipped with this knowledge and checked the wc of wlan_rx_wake. It's 0 and that's what it should be. Even when using the network. If you have something running on your phone that causes traffic, it should always fire an alarm first and wake the phone.

I'm postulating now that the wc of wlan_rx_wake is the safest way to identify a dirty network. 0 is the value it should always have. Like it is here in my home network.
[BetterBatteryStats] Rob2222:
@xelra:

No problem at all. ;)

But I think its the wlan-wake wake count, that indicates how often the device woke up by incoming wlan packets.

Wlan-wake WL then (maybe/always?) leads to wlan-rx-wake WL but wlan-rx-wake did not get an wake count, cause the device is wake then already.

At least I assume thats the way it works.

BR

Rob
[BetterBatteryStats] wadokai:
Hi everyone,

Okay so i took an idle dump and it's attached.

Please provide your feed back. Thank you.

I'm running SGS 3 i747, on wanamlite rom
[BetterBatteryStats] nobnut:
It would make some difference, but to be honest, the difference would be very small, possibly to the point of irrelevance.

The ideal is that when the screen is off, the device is sleeping. Therefore why the need to limit the CPU when the battery is low? It should be drawing virtually no juice when the screen is off anyway.