yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] Lebenita:
I would gladly do that, but I'm not sure what I could do. I have already completely uninstalled and then reinstalled and reconfigured BBS. The device is a 100% stock Xperia GO (with the exception of rooting).

BBS does process plug/unplug events all right. It recognises when the device is plugged in (=shows no stats), and it resets the unplugged counter when I unplug the device. So if there is a problem, it only relates to timing (which of course might be sufficient to screw up stats like screen-on times).

Please note as well that the CPU times add-up problem appeared on a completely different device as well (LG P970), so it's rather likely that the source of that problem lies in BBS code. The screen-on overstate problem might be Sony-specific unfortunately (but still it would be nice to get to the bottom of it).
[BetterBatteryStats] chamonix:
For now I haven't taken a look into the sum of the CPU states and I don't say that there is no bug in BBS either. I just commented on the logcat you provided and on the fact that the errors I mentioned could be a cause of the problem based on "since boot". Maybe you could provide the same observations based on "since unplugged" with a logcat so we can verify that there are no errors while writing the reference and focus on the figures from there.
[BetterBatteryStats] Lebenita:
I have attached a dump and a logcat that demonstrates both problems, (a) excessive screen on times and (b) CPU times higher than total time, with a "Since unplugged" reference.

===================

General Information

===================

Statistic Type: (3) Since Unplugged

Since 8 m 54 s

===========

Other Usage

===========

Deep Sleep (): 7 m 49 s (469 s) Ratio: 87.8%

Awake (): 1 m 5 s (65 s) Ratio: 12.2%

Screen On (): 1 m 27 s (87 s) Ratio: 16.3%

==========

CPU States

==========

200 MHz (): 1 m 1 s 11.2%

400 MHz (): 1 s 0.3%

800 MHz (): 1 s 0.2%

1 GHz (): 12 s 2.2%

Deep Sleep (): 7 m 49 s 86.1%

(adds up to 9m 4s)

Let me know if there is anything else I can provide to help you identify the problem.

Lebenita
[BetterBatteryStats] cyrax83:
Can anyone help me please??

The only thing I have installed is Gmail sync as push (as exchange email), and facebook app (no sync), nothing else and I went to bed at 90% Battery and woke up with 50% battery. Any ideas??

http://imageshack.us/a/img39/6816/screenshot2012101507245.png

http://imageshack.us/a/img717/6816/screenshot2012101507245.png

http://imageshack.us/a/img198/862/screenshot2012101507254.png

http://imageshack.us/a/img585/9270/screenshot2012101507255.png

dump file here http://codepaste.net/iq62zq
[BetterBatteryStats] chamonix:
Have you checked the dumpfile? Exchange and Facebook + notification are your drainers

Edit: and please remove those huge screenshots from your post and post the umpfile as attachement next time
[BetterBatteryStats] cyrax83:
sorry, i'll edit this in an hour when I get to work. Which dumpfile? I have pasted the batterystats dumpfile in the text...
[BetterBatteryStats] chamonix:
Yes that is what I meant. Add it as attachement next time please.
[BetterBatteryStats] xelra:
Why don't you use the gmail app?
[BetterBatteryStats] bobdoblo:
What uses less/is better, Gmail app or stock email app?

Powered by NeatROM
[BetterBatteryStats] gollyzila:
Here is my new dump. Screen was off for 10 h 3 m 49 s and Level lost [%]: 7 Bat.: 7% (100% to 93%) [0.7%/h]. That's pretty cool. Thanks to Karpfenhai for helping for my previous log and chamonix for the BBS.

My phone had a lot of wakeups through the night and it looks like it's Google Now checking my appointments, even though I disabled that feature in the app. The other large quantity of wakeups is from Tasker, but that's because my phone got disconnected from Wifi during the night.

Pastebin link: http://pastebin.com/raw.php?i=YQfYTaWM
[BetterBatteryStats] jaydoubleyou:
so i'm guessing that at the moment there is no real solution to event log service?
[BetterBatteryStats] indresh88:
i have multipdp says 46 minute wakelock......whats that??? attached dump file....
[BetterBatteryStats] gollyzila:
Check the How To... section in BBS. It's related to network usage.
[BetterBatteryStats] Torres_Spain:
Hi all¡ i need help by some wakelocks can help me please¿¿

Process audio out3

Process signal.collector

Thanks in avance :)

Enviado desde mi GT-I9100 usando Tapatalk 2
[BetterBatteryStats] Karpfenhai:
We need the context.. i which timeline does this happen??

Just post a dump please.
[BetterBatteryStats] msquared:
Folks can you please tell me what means the "secril_fd-interface" wakelock?

Cheers :D

Sent from my GT-I9100
[BetterBatteryStats] Hilmesh:
It is to do with Fast Dormancy

---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------

Hey Karpfenhai,

While using Screen filter the standard brightness settings of the phone should be in Auto Brightness mode or Manual?

Thanks
[BetterBatteryStats] Karpfenhai:
I never use auto brightness.. :)

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Christiancs1969:
Lux auto bright might help;)

s2 RR 309 dori
[BetterBatteryStats] msquared:
Since my phone is on, it is 28 mins....

Should i worry about it?

Sent from my GT-I9100
[BetterBatteryStats] gigeaky:
I managed to stop maps using the 3rd post but I think that it's still a little high (5.2%/h) in stand by...
[BetterBatteryStats] Torres_Spain:
Ok i follow your instructions but ...Google now doesn´t work because i deactivated the location in settings :S thanks in advance...
[BetterBatteryStats] Markox89:
Reset References Bug

I've understood how to reproduce this.

I've fallback to "on boot" and "on boot" as default reference.

I turn on my phone, after a couple of hours I plug the charger and after some minutes I unplug, note that the phone has not been fully charged in these minutes. After I unplug I open for the first time since boot BBS, and references are resetted since the unplug time.

Here's the logcat, hope'll help!
[BetterBatteryStats] chamonix:
I can't find any trace of references being reset as you write so I guess I didn't get what you wanted to report. The refs as they were created:

I/StatsProvider(13880): Retrieved ref: Reference custom_ref created 0 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
I/StatsProvider(13880): Retrieved ref: Reference since_charged_ref created 0 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
I/StatsProvider(13880): Retrieved ref: Reference since_screen_off created 0 s (Wl: null; KWl: null; NetS: null; Alrm: null; Proc: null; Oth: null; CPU: null)
I/StatsProvider(13880): Retrieved ref: Reference since_unplugged_ref created 1 h 57 m 19 s (Wl: 0 elements; KWl: 25elements; NetS: 15 elements; Alrm: 7 elements; Proc: 0 elements; Oth: 5 elements; CPU: 17 elements)
D/dalvikvm(13880): GC_CONCURRENT freed 310K, 5% free 8347K/8775K, paused 2ms+3ms
I/StatsProvider(13880): Retrieved ref: Reference since_boot created 40 s (Wl: 7 elements; KWl: 4elements; NetS: 2 elements; Alrm: 1 elements; Proc: 0 elements; Oth: 6 elements; CPU: 17 elements)

You have no custom ref

You have no since charged ref

Since unplugged was created 1 hour 57 after boot

Since boot was created 40 seconds after boot

Can you please explain in more details what steps you did, what you were expecting and what happened?
[BetterBatteryStats] chamonix:
I definitely recommend that you enable the root features in the advances prefs to have all the power of BBS at your hands.

In that reading the biggest drain comes from wakeups due to Wifi being on.
[BetterBatteryStats] bdclary:
Thanks for the response. The Plummet issue sounds very similar to my symptoms. Is there a way I can confirm this with BBS?

More specifically, since the problem seems to show up several hours after the phone has been unplugged, would I be able to collect useful information if I did the following?

1. Unplug phone

2. Commute to work

3. If plummet shows up, create a custom reference in BBS

4. Leave phone idle for at least one hour

5. Create dumpfile

And more generally, are the dumpfiles from BBS useful if they were created from a custom reference point, not just from when the phone was unplugged?

Thanks again for all of the help,

Brian
[BetterBatteryStats] Markox89:
When I open BBS (just unplugged the phone) and saved the log the app says that the reference since boot was created in that moment, shows 0 seconds, increasing, instead of about two hours.
[BetterBatteryStats] ETW11:
Is anyone familiar with the kernel wakelock, "mmc1?" It appears on my phone about once a month, but it lasts until a reboot and really does a number on the battery. I would like to discover what triggers it to possibly prevent it from occurring in the future. Any help would be greatly appreciated.
[BetterBatteryStats] ziizy:
Ahhh gosh I hate this freaking syncing. Any idea how to shut this off?
[BetterBatteryStats] Karpfenhai:
we need more information (dump) to provide you a reliable answer but as a quick shot, emmc point either to your internal or external storage (sd card).

Possible reason can be a faulty card or a crazy media scanner, hard to say without context...

You can do all this action, but i afraid they are useless in this case, it seems the problem occurs right on the gsm / modem part of the device without showing anything in the wakelocks!

Maybe you can take a logcat and a dmesg reading, but who would be able you analyze it for you.. You should bring this topic up in the gs3 thread.

I can only tell you the same thing as the other guy, try all available modems until you find one without the plummet issue.

I'm sorry!

Tapatalked from my Samsung GT9100
[BetterBatteryStats] chamonix:
You are right, Wifi is your main but not only cause of drain. These kernel waelocks are caused by incoming traffic waking your phone.

To resolve that issue you can:

a) turn off Wifi when not needed

b) if you have access to the network it may be worth sniffing the network traffic with wireshark and trying to identify and resolve the cause

An overhead that comes with Wifi being on is also a pretty high amount of maps overhead cause by caching (see FAQ for possible solutions)

pa

The second cause of wakeup is android.phone (see above):

1. you are using the SIP integration: a search on XDA should tell you if there are known remedies

2. because of bad network coverage: maybe another radio module can help but there is no guarantee
[BetterBatteryStats] gymsta:
Galaxy Wonder CM9

Hi all,

since Update to CM9 i think my battery drain is very fast.

Here is a overnight dump of my phone.

I hope you can help me.
[BetterBatteryStats] loth77:
i'm not very happy with my battery stats...

i don't know if it is just because of the netowrk signal being not much constant or if i have some troubles that drains my battery

galaxy s2 with resurrection remix 2.7

kernel dorimanx 5.84 with a little bit changed battery profile

and 2000mah battery

i attach the dump, i hope it is correctly done :)
[BetterBatteryStats] chamonix:
The web.de sync service is your main problem
[BetterBatteryStats] xbiggyl:
Hey folks,

Looking for a little help :)

On my HTC One X, I have been facing this issue lately.

BBS shows that my Bluetooth is ON even though I have switched it OFF.

It happens all the time. A reboot fixes it, but as soon as I turn it ON and then OFF, it remains to appear as ON in BBS.

Any thoughts? Thanks
[BetterBatteryStats] danielo:
HELP:High kernel usage

Hello,

I have a problem with quite high kernel usage, even at time I going to sleep and I turn off all radios and syncing like WIFI, cellular data and BT. I tried to figure out what is keeping my device active at that time (23:00 - 7:00) but it seems that my knowledge is not good enough and I need help of somebody experienced. As you can see at the provided screenshot the usage of android kernel is the highest of all other processes. I try to undervolt CPU by -25, but not visible difference in battery life, I also undervolted GPU and again no visible difference. I disable almost all startup processes, no go I still haven't found what keeps my device awake at night, as you can see at last picture. I also attached logs and my extweaks config. So I hope that somebody can read it and propose some hints/tips I can try. My signature is up to date, but just to be sure I'm on DorimanX 5.88 and my rom is WanamLight 12.5 - XWLPX(ICS 4.0.4) and modem is XXLQ6.

Thanks in advance.
[BetterBatteryStats] It_ler:
Just a suggestion:

Try to disable the Cortex brain service in ExTweaks.

Then check again.

I am experiencing also many alarm wakelocks with DorimanX v5.88 (and v5.87 before), but my phone has relatively good battery life.

Have a look at my kernel test results here => http://xdaforums.com/showthread.php?p=26775950

You are welcome to report back your experiences.

Good luck !
[BetterBatteryStats] Rob2222:
Hello all, hello Tungstwenty,

thank you very much for that information.

I made some tests with BBS and "Shark for Root" and analysed the data via cloudshark.org.

Two things I have found out regarding WLAN Standby drain:

1)

Speedport W303V dsl router sends 60 IGMPv3 packets per hour, Fritzbox 7170 dsl router sends 30 IGMPv3 packets per hour.

These packets are needed for IP-TV set top boxes.

These IGMP packets wake the Galaxy S3 with stock kernel. So you have in this case around 30-60 wakeups per hour just cause the routers send multicast packets.

I think it can be even more, when you have more multicast sending devices in the home network.

Siyah and Persues kernels have packet filters, that block that kind of traffic.

2)

Galaxy S3 still can suffer from the BT-AMP bug with that typical 0x886c protocopl packets.

See this and this.

If that bug triggers, you get a wakeup each 10 seconds which are 360 wakeups per hour for nothing. On S2/S3 each wakeup cost almost 1s CPU cycles at 800MHz. See this.

You can prive this bug when you do a 10 minutes shark for root capture, upload it to cloudshark.org and you find around 60 packets which protocol is 0x886c.

You can also see this bug when your "wlan_wake" kernel wakelock wake-count (wc) field raises contininous with 6 times per minute.

I have that bug on my Galaxy S3 with Stock XXLIB JB Firmware with stock kernel AND even with Siyah kernel 1.7b6, when I am connected to the Speedport W303V dsl router. As soon I change the the wlan network to my Fritzbox 7170 router, the bug is gone. I didn't even have to reboot or something. Just switch the wlan network.

Another S3 owner has this bug on his S3 with perseus kernel on Fritzbox 7390 router.

I have no idead how to solve this bug, at the moment. When reading Entropy512's statements in the postet links, its a tough one.

I only know it happens on some networks and on some network it doesnt happen. And even the multicast packet filter in some custom kernels doesnt help.

PS: If you have a clean/good working WLAN, WLAN is more energy friendly than 3G.

I've made plenty BBS dumps with my SGS3 with siyah kernel over night with WLAN on my good working FB7170 router and via 3G.

WLAN_WAKE wake count with this configuration is for me around 50-100 wakeups per night.

Drain/hour value with 3G is mostly around 1-2 times higher as the drain/hour value with WLAN.

WLAN drain over night is on average 0.5%/h, while 3G drain is on average around 1%/h.

But for sure both values will increase, if you have more communicating apps installed. So it still depends on how much the installed apps communicate/how much traffic they generate.

BR

Robert
[BetterBatteryStats] bdclary:
Thanks again for the help! So if I do provide a dump after I notice the plummet, and the dump does not show an excessive amount of wakelocks, would that help confirm that the plummet is related to the 4G bug mentioned in the other thread you referenced? (Basically, would a dump help confirm whether it is the 4G?) If this is the case, I'll create a custom reference once I notice the plummet, take dumps and logcats, and see if wakelocks are the problem.

I apologize for the multiple questions. I'm just learning about wakelocks and such, but I want to make sure I'm interpreting everything correctly and coming to a reasonable conclusion before I decide whether to take the phone back.

Again, thanks for all of your help,

Brian
[BetterBatteryStats] Karpfenhai:
Yes you can do it this way, i hope we can prove the absence of suspicious wakelocks then.

No need to apologize, at least you are willing to learn! :)

I'm keen for your logcat too.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Empty Hand:
I removed the main offender apps, and got my idle drain to 1.2%/hr,which is much better than before. I know Exchange is the worst for now, but I changed the sync schedule from push to every 5 minutes hoping it would help. My signal at home is horrible, which is why my wifi is always on. Is there anything else you can see from this dump that may help? Thank you!

I am running Franco r290 and AOKP build 4.
[BetterBatteryStats] Rob2222:
Yes, one more thing to mention is the bug itself.

This is some really strange behaviour.

The phone is using its own MAC address, with ONE bit changed as packet source and sending the packets to its own MAC address. See here.

So the device is sending data with a fake source MAC address to itself?!?!

WHY?! In these packets I saw my own wlan-ssid.

Maybe this is the behaviour the broadcom engineers wanted, that the phone sends information to itself. But I think at least the device should not wake up at least.

And one more thing I've found out regarding this:

The bug is existing on my S3 with stock JB with stock kernel and also with siyah kernel. Even so the bug is existent on the S3 of a friend, 100% stock ICS.

WHEN using the Speedport W303V wireless DSL router.

The interesting thing:

We have connected a FRITZ WLAN Repeater, which extends this W303V-WLAN. (Same SSID)

Now as soon as our S3 switch from the W303V over to the Repeater, the bug is gone. Even that is the same WLAN.

So it really seems to depend on the access point hardware. Maybe something with the beacon that triggers this? I mean, these strange packets include the ssid from the wlan (at least sometimes).

And yes, a counter in BBS how often the device woke up, would be really nice.

Best Regards

Rob
[BetterBatteryStats] Maxxon2k:
I am still trying to figure out why my partial wakelocks show the AlarmManager responsible sometimes for a lot of wakeup time (e.g. 1 hour phone uptime, 58 minutes deep sleep, 2minutes awake time, but alarm manager 30 minutes - which does not make much sense to me at all) while at the same time the actual alarms add only up to a few minutes (which then fits the reported times for time awake).

Can someone please explain to me:

how to find out what causing the wakelock on that specific time. Or am i looking in the complete wrong location?

I have another question about the logcat

i have uninstalled already com.sonyericsson.android.wakeup. Does this log entries mean that the events are still occuring but cannt be delivered?
[BetterBatteryStats] Karpfenhai:
You're main problem is still your wifi network, followed by exchange, if you set it up to five minutes, you can stay on push....

15 mins as minimum, better 30.

Define a sleep period if possible.

Try to clean your network.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Empty Hand:
I've got a network extender on the way. So, if I have a decent 3g connection, it is better to turn off wifi during idle times?
[BetterBatteryStats] loth77:
sorry for asking again... but i had no answer... not a single word... not complaining, just let me know anything, even if there is nothing strange or if i have i taken a bad dump or done something bad or if some more informations are needed ;)

since some time i'm not happy with my battery stats

i don't know if it is just because of the netowrk signal being not much constant or if i have some troubles that drains my battery

galaxy s2 with resurrection remix 2.7

kernel dorimanx 5.84 with a little bit changed battery profile

and 2000mah battery

i attach the dump, i hope it is correctly done
[BetterBatteryStats] Karpfenhai:
Not necessarily, better to "clean" your network, try wireshark to identify the polluters and set your device to a static IP to prevent dhcp overhead.

Tapatalked from my Samsung GT9100

---------- Post added at 10:03 PM ---------- Previous post was at 09:42 PM ----------

Hmmm, its a tough one..

There is only a bit of overhead visible in your dump most is network related plus some sync and location stuff..

I would suggest to use another modem and maybe another kernel, since 26 mins awake out of 7 hours should not consume that amount of battery..

Good luck.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Empty Hand:
Thank you. I will try, but that may be above my noob tech skills.
[BetterBatteryStats] loth77:
what modem would you suggest for lower battery consumption?

i know it depends on millions different parameters... but you for sure can give some hints to someone who doesn't know where to start :)

if it can be useful... i'm in italy, my network is wind
[BetterBatteryStats] Christiancs1969:
http://db.tt/SpKogf07

Good for batt. Fullbars;). Nice.nice modem say thanks if you like

s2 aopk 412 dori 73 pitch perfect
[BetterBatteryStats] Karpfenhai:
I would start with ki3 or ki4, in case of signal problems or slow data rate kl1 or as mentioned bvlpe.

I wouldn't use an 9100m modem on a i9100 model.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Christiancs1969:
Its cool:D

s2 aopk 412 dori 73 pitch perfect
[BetterBatteryStats] loth77:
what's the difference with i9100m?

it is the first time that i read of that

i'm having troubles to find the modem that has been suggested...

in the tread with the list i can find just some
[BetterBatteryStats] xbiggyl:
Anyone?
[BetterBatteryStats] villain_allain:
I just want to know if my device is in normal condition.

I charge the phone to 100% then idle it for around 6hours. I lost 9% battery.

WiFi ON / 2G Signal only / autosync off / network locations off.

I will post my logcat. Im using a s3 with rom paranoid android.

Thank you.
[BetterBatteryStats] xelra:
1.5% per hour is ok. Maybe you could save a bit by not using voip and freezing Google now and Google search stuff.
[BetterBatteryStats] villain_allain:
1.5% per hour screen off is ok? hmm..

Thank you for the reply.

Why is there are many awake on my devices? and what is that googlesearchbox?

Can you point me the apps that uses it? Thanks.
[BetterBatteryStats] catskin:
I can confirm this, on an HTC One X (running ViperX 2.7.0)
[BetterBatteryStats] noorzaquan:
Hye guys. I have observed on my kernel wakelocks that multipdp is the main cause to my battery drain. it looks abnormal to me. can you guys help me for the solution. I have attached the dumpfile. Thanks in advance
[BetterBatteryStats] Karpfenhai:
Wrong Thread, both of you..

---------- Post added at 08:35 AM ---------- Previous post was at 08:32 AM ----------

Multidpd and l2 hsic are related to background data transer / data transfer in general, to bring this down, you need to decrease your data hungry apps somehow.

Check the network tab within BBS to figure out which app(s) is the culprit.

Good luck!
[BetterBatteryStats] Hilmesh:
Hey there Karpfenhai,

Can you just take a quick look. I am on LQ6 modem now with Siyah Kernel (Wanted to try something new :).) does the dump look OK / Good/ Bad / or can be improved?

Thanks.
[BetterBatteryStats] Karpfenhai:
Mate, your dumps are perfect, they are always, a kernel or modem switch should not influe the dump result, i only recommend kernel and modem change in case of invisible / unexplainable drain. (or high ril wakelock).

You are doing a great job.. You should teach others, not ask.. :D

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Hilmesh:
Hey there, thanks for the quick and nice response. :)

I follow the thread and will surely keep trying to help as much and wherever possible.

Thanks :).
[BetterBatteryStats] xbiggyl:
Please explain why you claim it to be the wrong thread?

BBS is showing Bluetooth to be ON while it's OFF on HOX. However, the native battery usage monitor does not show BT to be ON.

Wouldn't this be counted as a BBS related issue?