yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] Entropy512:
48 minutes out of 9 hours seems a little high to me.

I'll need to retest a few times, I almost always have my phone on wifi overnight nowadays.
[Galaxy S II General] chamonix:
has wifi off since boot and have 1.5 hrs of that wl out of 34.
[Galaxy S II General] ewok666:
Change the duration of the wakelock????

Anyone know how to " Change the duration of the wakelock"? This is suggested by Better Battery Stats but I have no idea how that would be done? I have plenty of svnet-dormancy locks and would reduce the lock from 6s.....if that's even possible.

TIA
[Galaxy S II General] Entropy512:
It's buried somewhere in this thread, don't remember where in sysfs it is off the top of my head.

If the BBS wiki is recommending changing it, it should also be warning that reducing this value could cause VERY strange side effects if made too short. (What is "too short"? No one knows. It could be that anything less than 6 seconds is "too short" in 1% of cases.)
[Galaxy S II General] chamonix:
Warning is included: https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/svnet-dormancy and for obvious reasons I didn't even try to find the exact instructions on how to change that timing
[Galaxy S II General] wolfkstaag:
Does it hide it from everything? Like, can Watchdog still tell me when the suspend process is going crazy?
[Galaxy S II General] don_alberto:
if I have high AOS % and i'm not using the device does it mean I have this bug?

because something needs to "eat" the battry somehow no?

I mean - if I have like 60 % AOS, and 15% screen is it ok under the condition I just used the phone for 5 min?

OR - should all the time the AOS should be low??? (even if not using the device!)

thanks!!!

Some details:

phone on for 28 hours (1D 4.5 hours) - 65% battery gone.

minimal usage:

wifi on - all the time

display 1 hour and 30 min - 14%

AOS - 60% - 4 Hours and 16 minutes.

not having a lot of wakelock.(biggest one is 4 minuets and related to my email which is defiantly OK )

(those are the heights battry consumers)

thanks guys!
[Galaxy S II General] BatterBits:
I would suggest with those useage figures, you don't have any huge problem(s). You may want to look at what you have running in the background (skype, viber, facebook) and how often stuff is "polling" for updates.

28 hours sofar, so roughly 42 hours from a charge, is not to bad IMO
[Galaxy S II General] Entropy512:
The suspend process isn't actually going crazy - it just gets "blamed" for time spent in interrupt handlers due to an IRQ time accounting bug. Unfortunately, getting IRQ time statistics in Linux is a bit of a pain in the ass, so the CPU time spent handling IRQs is effectively hidden.

/proc/interrupts is useless, it gives you the interrupt count, not the time spent in interrupt handlers, and it's unable to differentiate between interrupts that occurred during sleep and ones that happened during normal usage.
[Galaxy S II General] sohebq:
"tvout resume wo"

does anyone know how to stop this, it is causing high drain of battery :(
[Galaxy S II General] crzchn:
Hep with understanding wakelock dump?

I am currently on stock EK02 on my Sprint Samung Epic 4G touch. Battery life has been less than what I see others getting. So I am trying to understand the wakelock dump but the original post has me confused. I sorted the following dump by total_time. It looks like CarrierIQ is a burden, but was wondering about the audioOUTLOCK.

(I am waiting for the next Sprint update which will hopefully have nociq before resorting to keeping a hacked rom.)
[Galaxy S II General] tylerdurden83:
Just out of curiosity, have you guys noticed that all ICS official leaks have the same aos huge consumption? So yea, ICS will not magically solve it....
[Galaxy S II General] jose.celestino:
According to teamhacksung that just shows higher, it's not really higher.
[Galaxy S II General] tylerdurden83:
I was hoping it wouldn't show at all tbh
[Galaxy S II General] Entropy512:
Over in I777-land we actually found the first case of high Android OS usage that is actually caused by a firmware bug:

In the UCKK6 firmware base, Samsung changed something that causes an oddball feature of the wifi chip (Broadcom Bluetooth AMP) to go bat**** insane on an intermittent basis, waking the phone at 1 Hz. This occurs even with the stock UCKK6 kernel, and regardless of kernel used.

This may also affect recent I9100 bases such as XWKK5 (need more data).

To confirm you are suffering this issue, you need to take a capture using Shark for Root and look for patterns like this:

4392 3734.030532 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4393 3735.259603 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4394 3736.487913 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4395 3737.715492 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4400 3738.944645 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4401 3740.174807 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4402 3741.401890 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4404 3742.631117 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4407 3743.859426 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4411 3745.090096 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4412 3746.112760 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4413 3747.137515 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4414 3748.161862 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4415 3749.185961 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4416 3750.210275 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II
4417 3751.232426 9a:0c:82:63:72:56 SamsungE_63:72:56 0x886c 74 Ethernet II

Main things being:

Protocol 0x886c, and the source MAC differing from the wifi chipset's destination MAC by only one bit, and happening at 1 Hz.
[Galaxy S II General] stennett:
I have only just been affected by this last night my phone lost 50% power and the only battey uasage was apparently the OS!
[Galaxy S II General] shahulvm:
Hi Entropy512 , does this mean that high AOS usage is attributed partially to WIFI. with KK5 i had wifi off and 3g on always. Calendar app was connecting to the net inspite of me configuring it not to sync. After these changes (removed most of default apps and replaced with my prefered/tested ones), high AOS usage came down. I go with the earlier opinion that High AOS usage is due to some rogue apps having unnecessary wakelocks or connecting to net for odd reasons and this gets accounted as AOS.
[Galaxy S II General] igalan:
In my wife's SGSII (stock) if I enable WiFi it will burn the battery fast, even when it's sitting at home connected to our access point. So WiFi is off at all times and data is being pulled from the mobile network. For the last few weeks this has enabled the phone to last one full day with about 45-65% battery left (depends on usage pattern, off course). AOS use is always on the top of the list, but battery seems to last as much as you can expect from a phone like this (finally).

Isn't there a way to reliably send feedback to Samsung? I mean, you guys have traced the source of the bug very precisely, surely devs at Samsung can get a fix really quick with all this data. So all that's needed is a communication channel...
[Galaxy S II General] androidkid311:
Im pretty sure smasung know about the bug. Questions how bothered are they ..??? :-/

looks like an iphone but powered by android baby!!!!
[Galaxy S II General] Entropy512:
Please read more - there are MANY possible causes of this, only ONE of which is actually a firmware bug, and that has (so far) only been confirmed on I777 UCKK6.

There are many possible causes of high AOS percentage reporting (which is almost always due to frequent device wakeups). Many are due to rogue apps driving data to the phone, the issue above is one of the first cases to actually be the fault of a firmware bug somewhere.

For example, when AndreiLux had high drain and AOS problems, the culprit was Skype.

As I stated above - the firmware bug is so far only confirmed on the AT&T I777 UCKK6 base. I suspect it may be in other bases but so far have no confirmation.

If you're on XWKK5 (or another recent base) and receive high drain only when wifi is on, follow the steps for obtaining a Wireshark capture as described at the bottom of the first post here:

http://xdaforums.com/showthread.php?t=1308030

Post the .pcap here.

Note that if you see high AOS reporting on UCKH7 or XXKI3 bases, you are NOT experiencing the bug described above. You probably have a rogue app driving data to your phone.

In short, as far as the BT-AMP bug described above:

The following bases are NOT AFFECTED:

I777 UCKH7

I9100 XXKI3

The following bases are CONFIRMED AFFECTED:

I777 UCKK6

I997 (Infuse) UCKJ2 and later up to UCKL2

Anything else is unknown - but later builds are more suspect than earlier ones.

No, they claim to have an improved bug feedback process on developer.samsung.com, but the reality is that they don't.

As stated above, there are multiple potential causes of high AOS. If you only see major drain on wifi, then please obtain a Wireshark capture as described above to confirm. (Take it at a time when you are actually experiencing the drain, as it's intermittent.) Make sure to follow the packet truncation instructions in the post above for your privacy and to reduce the file sizes.

I don't know if Samsung is. AT&T is aware of it at stores, but they keep on just giving people free batteries, which will NOT fix the problem.
[Galaxy S II General] htc9420:
ICS KP8 battery screen shot

Speaking of rogues apps...take a look:

I know this is not relevant since KP8 runs with the 'old' TW launcher, but anyway...9hrs till battery flat.

Look at the wake up times vs screen on, voice calls were like 10 at max.

Also this doesn't count as this is a beta build but anyhow...
[Galaxy S II General] Deosneos:
Codeworx' android OS is a lot lower than that of people really experiencing the bug. He assumes it's because people who have the bug don't use their phone for other things enough, thus pushing up the android OS %. I still have huge android OS usage even with a lot of screen-on time, so I'm going to assume he's wrong here.
[Galaxy S II General] Entropy512:
AOS reporting in ICS is COMPLETELY different from Gingerbread.

https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT - Originally intended to discuss batterystats, in the end there is some discussion of Android OS reporting in ICS.

Two things:

1) Unclaimed wakelocks (primarily kernel wakelocks) are included as part of Android OS reporting. How much this is weighted depends on power_profile.xml - which I believe is completely broken in this regard for Samsungs (or at least it was in Gingerbread...)

2) In early ICS versions, a bug caused screen-on time to be ADDED to the unclaimed wakelocks instead of subtracted.

3) It's unknown how ICS on Samsungs handles reporting of IRQ handler time - IRQ handler time during suspend/resume is the primary contributor to Gingerbread AOS CPU usage reported.
[Galaxy S II General] gaddy888:
deleted_wake_locks

I've been struggling with my phone battery issues for quite some time now.

Can anyone tell me what deleted_wake_locks are and why the count is so high?

Android OS is almost invariably my highest battery drainer. But I don't know what's causing it.
[Galaxy S II General] Robotic4:
I installed the battery app from the start of this thread. Im using the 2000mha extended battery from Samsung. This app shows the battery as the 1650mha version. Is this normal? Thanks
[Galaxy S II General] atua:
Are you talking about "Battery Monitor Widget" app? That app assumes you're using a standard 1650 mAh battery. You'll need to change it to 2000 mAh if you're using the extended battery in Settings->Monitoring->Battery Capacity.
[Galaxy S II General] MatangaChanga:
What I really think is that Samsung, knowing that there are so many capable and intelligent customers and users of the phone that are trully looking for a solution (say XDA people), they are sitting in their butts waiting for those costumers and users to solve the problem. I can't believe that such a common problem that is affecting so many Samsung customers has not been address and solved yet by Samsung, to me this is a disrespect and lack of professionalism of the company. :mad:
[Galaxy S II General] Entropy512:
*sigh*

You clearly didn't read anything. It's not a bug... In almost all cases except two, it's a rogue app. There are only two cases where ROM bugs come into play. One showed up sometime around XXKI3 and was gone by XWKL1. The other was in XWKK5, but not XXKI3 or XWKL1. XWLA4 also does not have any of the bugs.

If you're still getting drain that involves high Android OS, your problem is either due to an app or a new bug that hasn't been seen before.

People need to stop lumping 30834283240 different bugs that just happen to have the same high-level symptom, nearly all of which are misbehaving apps like Skype, as one "bug".
[Galaxy S II General] Pixiewave:
What helped my batterylife a LOT.

I went into settings -wireless networks - mobile networks -

toggled mobile data (unchecking it and then checking it again),

toggled roaming (checking it and then unchecking it again).

I came from draining 7%/hour to 2%/hour.
[Galaxy S II General] MatangaChanga:
Believe me, I read everything.

Many people are reporting high battery drain in stock factory reset settings. Whether it's an app or a bug, how is it possible to have a "malfunctioning" phone with factory settings, no added apps? It's Samsung's fault. You can't release a product without thorough testing. And in this case, Samsung should have fixed this problem a long time ago.

At least that is what i feel about Samsung. A little disapointment. :(
[Galaxy S II General] eep2378:
Really? It's entirely possible to have a "malfunctioning" phone with factory settings. See ATT's KK6 OTA update......possibly one of the worst firmwares ever released! I'm not what you mean by "malfunctioning" but aforementioned firmware have massive battery drain and it was "stock" with "factory settings".
[Galaxy S II General] MatangaChanga:
That's exactly what I mean, I totally agree with you. When I say "malfunctioning" what I want to point is the fact that the phone works, but with a major flaw (high battery drain) even in stock settings. So, you can't blame anyone but Samsung about this, be it a rogue app or bug the phone sould work perfectly in stock settings.
[Galaxy S II General] Entropy512:
No, you didn't read - you didn't even read my post that you replied to, where I state that certain Samsung firmwares are affected by one or both of two bugs, both of which were fixed in XWKL1.

So yes - you will have problems with stock XWKK5 and XXKI3, but likely not on XWKL1 or XWLA4. If you have high Android OS on KL1 or LA4, you either have a misbehaving app or there's a new bug no one has seen yet. There's no excuse for lumping all of these various bugs under the same system where methodology for determining root cause (check kernel wakelocks for high wakeup counts, then use Wireshark if it's wlan_rx wakeups) exists.
[Galaxy S II General] igalan:
I still believe my wife's Samsung has a software problem. I always see Android OS on top of the list of offending processes, no matter the usage pattern (heavy or light). Battery life in standby is bad to really bad compared with my HTC Desire S (which have pretty much the same programs). And if I enable WiFi things get much worse. Unfortunately it's so bloated that it could be anything: the voice recognition constantly running, even if you don't want it; the people hub that is all the time running even if you have no use for it and so on.

But at least it makes it through the day, so we'll live with that. But I won't trust Samsung for my next phone unless I see reviews which clearly indicate that new devices have great battery life.

BTW, I don't have time to learn how to safely root it, freeze programs and tweak it endlessly just to perform the way it should out of the box. Besides ICS is around the corner, there is hope that Samsung can fix it.
[Galaxy S II General] Entropy512:
You don't even specify what firmware build you're on, which makes your report worthless. If you're having problems with XWKL1 or XWLA4, this would be interesting as they have seemed immune to the firmware bugs. If you're having problems with XWKK5 - time to update, that release is documented as broken and newer updates fix it.

Oh yeah - don't run Skype, it's an app that is clearly documented to drive frequent network wakeups, which shoots AOS through the roof even though Skype is to blame.

The GS2 has excellent battery life, as long as you're not running one of the broken firmware releases. My phone is at 94% battery life after leaving it overnight on wifi for 11 hours.
[Galaxy S II General] igalan:
It's on XWKI4. The phone is operator free and that's the latest firmware available, at least through Kies.

It doesn't have Skype, I've read the whole thread and knew about the issues it causes. But it has WhatsApp, however it seems to work well as I can't see problems with it on BetterBatteryStats.

If I leave it all night unplugged (no WiFi) it will burn about 16% battery in 9 hours. With WiFi enabled it's even worse (weird), but I don't have the numbers here. I'll re-test overnight power use. I know the phone stays in sleep mode for much of the time if WiFi is disabled; in this case I only see a few marks here and there on the activity graph. With WiFi enabled the phone remains awake most of the time, only going to sleep mode for brief periods.
[Galaxy S II General] brendan_r:
I seem to be having the problem as described above and I'm on

XWLA4 base running CheckROM RevoHd V6. From other posts I've read this was only occuring on earlier roms, but it definitely seems to be happening for me.

The problem I think started occurring after I left my house yesterday seemed to be getting considerably worse drain even though phone was supposedly idle. I've attached a small dump from better battery stats and a truncated shark dump.

I only restarted today and the problem seems to have gone away for the moment...

Any ideas on ways to solve this?

I9100

XWLA4 base

CheckROM RevoHd V6

XXKL1 modem
[Galaxy S II General] Entropy512:
I'll take a look at it when I get a chance... Are you running CheckROM's included kernel, or a different one?

I know that gokhan was mucking with wifi drivers in SiyahKernel and that seemed to cause a lot of problems for people.
[Galaxy S II General] brendan_r:
Thanks Entropy much appreciated. I'm running the stock kernel from CheckROM.

I've only had CheckROM for a few days, but I've moved to it as it is using the latest base and I was having a few issues when I leave my phone on idle overnight and battery drains more than I would expect given I've done a lot cleanups of sumsung apps and other apps / system settings that were causing drain. Have taken a lot of advice from the various forums which has helped a lot...

Last night was fine only drained from 100% to 96% in 7 hours. But have had some other episodes such as the RILJ dialer waking my phone about 3am in the morning and keeping it in a constant wakelock until i restarted after I gave up trying to pinpoint the problem. This occurred about a week ago on stock XILA2.

I somehow suspect one of the issues I'm having is related to my crappy Billion 7404 router which seems to disconnect and restart randomly fairly often. I'll often find when i wake up in the morning I'm connected to 3G and then have to toggle Wifi to get it to connect again. I find this quite odd considering the phone should be able to restablish the connection without me doing this.

Anyway i've gone on a bit... will keep monitoring it in the mean time, but appreciate any help :)
[Galaxy S II General] Entropy512:
Hmm... That might somehow be connected to the issue. One thing that people seemed to notice in the Infuse forums was that it was more likely to occur after they left their home wifi network without turning wifi off.

So it's not completely gone from XWLA4 but it does seem to be significantly reduced.
[Galaxy S II General] darkredemption8:
I have only 1 question.

Hello.

I have most of 54 pages of this wonderful post.

I appreciate very much all your work.

I did not understand if the BUG is present in ICS stock rom out 2 days ago.

It is?

:confused::confused:
[Galaxy S II General] Mekoa:
I still notice it in XXLP6 build I have at the moment, however my friend uses final XXLPQ build from here and does not have the same Android OS usage as I have.

One thing I have noticed, to reflect an earlier post, is that I tend to see slightly less after disabling Wifi and going on to HSDPA.
[Galaxy S II General] Entropy512:
There is no "bug" in most Gingerbread firmwares. Only XWKK5 had the BT-AMP bug, and only XXKI3 through XWKK5 had broken packet filters. In all other firmwares, high AOS is almost always caused by an app. (I've seen the BT-AMP bug trigger once in XWLA4, but it took over a month.)

Also, AOS reporting is COMPLETELY different in ICS - In fact, IRQ time during suspend/resume isn't seen at all.

I haven't tried seeing if pingdrain is less brutal on ICS, I'm waiting for kernel source before playing with it.
[Galaxy S II General] azulgranas:
Don't know whether it exists or not, because they could hide it while it was still there. But it is clear that ICS drains your battery so much faster than GB. So I assume that ICS still has this bug. They didn't know or consider this matter.
[Galaxy S II General] tylerdurden83:
Mine actually lasts longer, so I'd not resurrect this based on that tbh
[Galaxy S II General] JJEgan:
[QUOTE=azulgranas;24419784. But it is clear that ICS drains your battery so much faster than GB.

It reads that way judged by posts but as so many ICS flashers are noobs that dont have a clue and may not have modem and CSC for their region i reserve judgement on ICS and battery life .

jje
[Galaxy S II General] clonski:
I came across this thread while trying to get to the bottom of why my S2 uses so much more battery than my HTC Desire did. I've read the entire thread (which is fascinating) but am still stuck for an answer.

S2 is running exactly the same applications as the Desire. Sits idle in the same place when I'm working from home but consumes 4 times as much battery.

I'm running XWKI4. Is it likely I have the broken packet filter issue?

If so, how do I confirm or should I simply flash a later version and hope it goes away?
[Galaxy S II General] Entropy512:
To confirm:

1) You can dig up my old Fecality kernel from the Development forums. It has a feature to print when these filters are disabled.

2) You can try the following from a Linux box (there may be a Windows equivalent):

arping -b <ip address of some machine on the network OTHER than your phone>

This should shoot your Android OS and drain through the roof if you're broken, and do nothing if you're not.

XWKI4 is likely affected though.
[Galaxy S II General] clonski:
Thanks. I ran arping. Android OS and drain increased slightly but didn't go through the roof. I think I'll flash the latest firmware and/or try some different ROM - ICS maybe - and see if that has any effect :)
[Galaxy S II General] froggydoddy:
I seriously don't have time to go through 55 pages on information. I also have a hard time understanding the OP in detail. I'm a noob.

I've tried a few ICS Rom's on my GS2: 5 versions of the stock including LP7, A few Winam ROMs, Resurrection Remix 1.1, 1.3, latest VK ROM.

They're all great, except one thing: Terrible battery life. Android OS is chewing up my battery. It happens in all the ICS ROM I've installed. If I go back to Gingerbread, battery is a little better and I DON'T have "Android OS" up there in my battery stats.

Seems like this isn't a very common thing. When I check my battery consumption stats, Android OS is ALWAYS up there in second place after "screen". In Gingerbread, it's always near the bottom.

I wiped the phone and cleared both Caches. I have betterbatterystats but I don't find it very helpful.

So this "bug" is present in ALL versions of ICS? Shoot me.