yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] AndreiLux:
===========

Other Usage

===========

Wifi On (): 8 h 44 m 13 s (31453 s) Ratio: 100.0%

Awake (): 44 m 38 s (2678 s) Ratio: 8.5%

Screen On (): 13 m 4 s (784 s) Ratio: 2.5%

=========

Wakelocks

=========

DhcpHandler (Android System): 2 m 39 s (159 s) Count:144 0.5%

C2DM_LIB_TrillianReceiver (com.ceruleanstudios.trillian.android.Trillian): 2 m 10 s (130 s) Count:9 0.4%

AlarmManager (Android System): 47 s (47 s) Count:1530 0.2%

ActivityManager-Launch (Android System): 20 s (20 s) Count:127 0.1%

LockerService (com.teslacoilsw.widgetlocker.WidgetLocker): 17 s (17 s) Count:12 0.1%

sleep_broadcast (Android System): 11 s (11 s) Count:22 0.0%

RILJ (Dialer): 8 s (8 s) Count:215 0.0%

Checkin Service (Google Services): 4 s (4 s) Count:196 0.0%

Event Log Service (Google Services): 4 s (4 s) Count:59 0.0%

WidgetLocker (com.teslacoilsw.widgetlocker.WidgetLocker): 2 s (2 s) Count:23 0.0%

show keyguard (Android System): 2 s (2 s) Count:31 0.0%

SMSDispatcher (Dialer): 2 s (2 s) Count:1 0.0%

SCREEN_FROZEN (Android System): 2 s (2 s) Count:38 0.0%

GTALK_CONN (Google Services): 2 s (2 s) Count:174 0.0%

MediaScannerService (Media): 2 s (2 s) Count:2 0.0%

GTALK_ASYNC_CONN (Google Services): 1 s (1 s) Count:1 0.0%

keyguardWakeAndHandOff (Android System): 1 s (1 s) Count:335 0.0%

*network-location-cell-update* (Google Services): 1 s (1 s) Count:32 0.0%

=========

Processes

=========

tvout resume wo (0): Sys: 11 s (11 s) Us: (0 s) Starts: 0

system (Android System): Sys: 2 s (2 s) Us: 6 s (6 s) Starts: 0

suspend (0): Sys: 7 s (7 s) Us: (0 s) Starts: 0

com.aurorasoftworks.quadrant.ui.standard (com.aurorasoftworks.quadrant.ui.standard.Quadrant Standard): Sys: (0 s) Us: 4 s (4 s) Starts: 1

android.process.acore (com.fede.launcher.LauncherPro): Sys: (0 s) Us: 2 s (2 s) Starts: 1

mediaserver (1013): Sys: (0 s) Us: 2 s (2 s) Starts: 0

mmcqd (0): Sys: 2 s (2 s) Us: (0 s) Starts: 0

events/0 (0): Sys: 2 s (2 s) Us: (0 s) Starts: 0

skypekit (com.skype.raider.Skype): Sys: (0 s) Us: 1 s (1 s) Starts: 0

se.nena.nenamark2 (se.nena.nenamark2.NenaMark2): Sys: (0 s) Us: 1 s (1 s) Starts: 1

com.mhuang.overclocking (com.mhuang.overclocking.SetCPU): Sys: (0 s) Us: 1 s (1 s) Starts: 1

com.asksven.betterbatterystats_xdaedition (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): Sys: (0 s) Us: 1 s (1 s) Starts: 1

com.cooliris.media (com.cooliris.media.Gallery): Sys: (0 s) Us: (0 s) Starts: 1

​

If anything, this is how people should be reporting back. :p

The two red things are what are fixed now. The blue one is unchanged, and that one is now what contributes most to the "Android OS" package in the battery stats.
[Galaxy S II General] d3ck4rd:
Is it likely that this bug will be fixed in ICS?
[Galaxy S II General] staygold1gr:
very new to all this so please show mercy lads...

with you experts saying this is finally solved now

can someone point out to how install this kernel / rom without voiding the warranty?

I have been waiting for months for an official fix but I see that Samsung are a pile of ****. I recently had 2.3.4 from kies, GS2 on Thee UK

details on the photos enclosed. I notice watchdog lite does not show the suspend process - just base system - linux process, am I suffering from the bug discussed?

Thanks

Nick
[Galaxy S II General] KennyLegend:
Check in settings/ about / battery usage and see what % it consumes.
[Galaxy S II General] :
wow this is a great thread and very informative thanks to the OP...
[Galaxy S II General] staygold1gr:
It is always andoid os. Very high, 70% sometimes, display and everything else are fragments of it.

currently:

android as 62%

display 12%
[Galaxy S II General] s2d4:
so is mine man, I just posted the screencaps at androidmedia rom thread

.8 mins in like 18hrs...
[Galaxy S II General] KennyLegend:
Then you have the bug !
[Galaxy S II General] staygold1gr:
do i just need to flash this kernel with my unrooted stock room from Three UK or do I need to root and install some other rom too?

thanks

nick
[Galaxy S II General] AndreiLux:
Download Odin, select the .tar kernel file under PDA, don't touch any other buttons in Odin, and flash it. The kernel will auto-root the phone. It doesn't matter what ROM you have. This will technically void your warranty (since you asked about it).
[Galaxy S II General] staygold1gr:
ok, I will give it a shot, how do i back up what I have to recover to that if I need to?

link to the file please? :)

thanx

nick
[Galaxy S II General] borchgrevink:
Some questions:

1) Are there any drawbacks flashing this kernel?

2) Does flashing it increase the flashing counter?

3) When a new firmware update from Samsung arrive, can I just flash it over this new kernel?
[Galaxy S II General] AndreiLux:
1) You'll lose sound quality improvements if you're running on > KI3 stock already. Those will eventually come back when Samsung releases the new sources.

2) Not if you flash it from the phone, but there's no way around to having to use Odin at least once initially. That increases the counter to 1 at minimum.

3) Yes.
[Galaxy S II General] :
Please, would tellme some more about this fixed email.apk and mauve provider a link? Even on a 15mins schedule, email process gives me a real LOT of wakelocks, even though not for a long time (5mins and 140~ events in 20 hours)

Thank you :))
[Galaxy S II General] Molitro:
I definitely don't now what the hell is wrong with this phone.

I get rid of the AOS bug, I find a kernel + ROM combination (though the ROM has little to do with this) that has a good power usage while using the phone, that is, after 1 hour and a copule of minutes of screen, 2 hours since unplugging, I had 85% battery left, very good.

And then, I leave the phone alone with wifi, which should drain like 1% every 1:30 - 2 hours. Instead the phone drains 1% every 45 minutes.

I turn off wifi for the night, and drains 4% in 8 hours (again, almost twice what it should be).

None of the power monitors show me any excesive power consuming app, not better battery stats, not power tutor during the short time I had it on, not cpu spy, which shows deep sleep being the state 80% of the time, certainly not the stock monitor.

I have no explanation whatsoever to why the phone is draining twice as much as it should while being idle.
[Galaxy S II General] KennyLegend:
Flash the Rom and kernel again. That's not normal.
[Galaxy S II General] Molitro:
In the couple of weeks I had the phone, I flashed clean roms like 10 times...

I'm going to wipe and flash clean, without restoring anything one last time, and test every app one at a time for the last time.

If I don't find out where the problem is, I'll just shoot myself and be done with it xD
[Galaxy S II General] KennyLegend:
Are u restoring from titanium or something? try restoring apps only without data And NEVER restore system data.
[Galaxy S II General] Molitro:
I don't usually restore in general, and never changing version.

I do restore a couple of games because I don't want to lose the saves, but a lot of times don't even restore that.

I'm pretty sure it has to be an app, but no monitor tells me which one... Right now I have the phone almost without apps, and none that need any kind of sync or internet comunication... Lets see how much the system itself drains...
[Galaxy S II General] KennyLegend:
Good idea. Install as little as possible for a while and monitor. You'll see ur drain when u add back in the app.

I assume you've checked ur signed out of maps, latitude etc and disable all widgets ?

I always used to see maps as a running process on mine so I froze it along with a few others with titanium and my huge battery drain disappeared.
[Galaxy S II General] AndreiLux:
Molitro, can you monitor idle CPU frequencies? Take CPUSpy, reset the timers, and then leave your phone be for an hour. Also if possible screenshots of BBS process, wakelocks, other & Android battery stats. Set a custom reference in BBS just as resetting the CPU timers, and show stats from that point on.
[Galaxy S II General] Molitro:
I'll do it (by tomorrow), but as I said... deep sleep is fine, BBS doesn't show me any apps running wild...

Lets see how it goes tonight without any sync/internet needing apps.
[Galaxy S II General] Molitro:
2:30 hours with everything related to internet off, and still at 99%, so at least I now that there isn't anything wrong with my phone xD

Now I'm going to flash the last version of the rom I'm using (Exynos) with all my little tweaks and changes integrated so I don't have to flash a theme afterwards (as I pretty much always do with custom roms), and I'm going to leave the phone with the same apps as before but with network location and MS exchange email accounts on.

The push email use to drain a lot in SGS with froyo, but as of gingerbread that was fixed, and I haven't seen any specially high drain in the S2 either, so, I'll know tomorrow if it's any of those two things.

Right now I'm kind of hoping that beautiful widgets has nothing to do with it (it never has given me any problems, but neither has everything else)
[Galaxy S II General] borchgrevink:
Does the fix increase the battery life accordingly? Is battery that much better?
[Galaxy S II General] rvenes:
The SiyahKernel kernel flash did nothing to me.

Still high battery usage.

I also have the problem, that sometimes when i turn my phone on now, all my homescreens are empty.

Will try to reflash the latest NEE firmware that's out there, even if i loose root.

Just to see how long battery life i have almost stock.
[Galaxy S II General] Denwa:
What governor were you using?

sent from a faster than light sub-atomic particle
[Galaxy S II General] chemical1979:
I'm still running on stock firmware (not rooted! all stock) and was affected dramatically by this bug. After upgrading to latest KI4 via KIES, this got even worse.

So I tried something. I disabled WLAN permanently (and only activate it if it is really needed) and removed my microSD card.

THAT did the trick! Don't know which one or if both help such a lot. Maybe this works around the bug (at least for me) that causes Event/Suspend to race.

I had some mp3s for ring/sms tones on that card (in /media/notification) and Android silently moved apps to that SD (not the internal flash).

That means that Android somehow always needed to access the card (->Android OS), for playing tones (sms) or ringtones. Or even for loading icons in the menu from the SD.

When I removed the microSD card/stopped my WLAN my battery lifetime instantly went up from 12-18h (Event / Suspend -> Awake) to 3 days!
[Galaxy S II General] AndreiLux:
It's known that disabling Wifi will drastically reduce this bug. But to be honest that's one hell of a ****ty fix / work-around if you ask me.
[Galaxy S II General] KennyLegend:
Its kinda weird this AOS bug.

On cf-root 4.2 i got 2 days battery usage but high Android Os. (35%)

I flashed siyah 1.8 and got 5% AOS and about 38 hours battery with similar usage.

My point being even though it shows high in the stats ...is it actually draining the battery? Initially i thought it did but now im starting to wonder.
[Galaxy S II General] TheFirstBen:
I'm thinking the same here.

With Siyah the AOS usage is low, but the battery does not seem better at all, i would even say it's worse in my case.
[Galaxy S II General] vinvam:
Could OP or the dev of Siyah shed some light on how Siyah kernel fixes this issue?

Maybe other devs could use that info and apply it in other kernels or create a patch for all kernels?
[Galaxy S II General] KennyLegend:
Ya it was worse for me too. It almost seems as if Siyah is masking the problem instead of fixing it.
[Galaxy S II General] oyebto:
perhaps now that the android OS bug is fixed, Siyah's stock cpu governor maybe more battery intensive than the kernel is KI8? i am currently playing with diff governors to see the difference..
[Galaxy S II General] rogers73:
Agreed. The problem is only masked. A higher percentage goes to other entries in the list like display etc. The phone functions in exactly the same way and uses the same amount of battery.

Another point is that battery used by wlan is not shown as an entry on the s2. On my last phone, HTC legend, wlan had its own entry. So wlan has to be added to some other entry on the s2. Maybe this is part of the "bug"?
[Galaxy S II General] Molitro:
I don't think it's masking it.

The suspend process has much less calls and wakes and whatever it does.

It probably just spends the battery elsewhere.

I think in idle state gains battery, though, but still, pretty much the same for me too. I can't seem to achieve a decent battery life.

Right now I'm on 79% after 19 hours with 30 min of creen. Maybe slightly better than usual, but then again I have been with email and network location out for half the time the phone's been on.

I'll upload some screens tomorrow to see the progress through the day and a half pretty much idling.
[Galaxy S II General] xyzulu:
So.. I took the plunge any installed CM7.1 on my GS2. After flashing the #80 nightly with this patch: http://review.cyanogenmod.com/#change,8766 for me at least, this bug is resolved.

That being said, while this bug I do think contributes to poor battery stats, I do think it contributes less than some people make out. Just my viewpoint anyway..
[Galaxy S II General] NickoPulver:
Well......for me batterylife has gotten way much better with cm 7 nightly 80.......

Atleast when phone is idle and on over a nights sleep.....now i am down to an 1% an hour drain or less instead of 3 to 4%......if phone is used nonstop without sleep battery life wouldn't be that much changed.....cause the os drain for me and i would believe all is when phone should be idle and in deep sleep before drained battery but no more for me.......
[Galaxy S II General] xyzulu:
Yes, battery life on CM7.1 #80 is the best I have had on any SGS2 rom.
[Galaxy S II General] yhrn:
Many thanks to OP for this thread!

I've had the AOS bug, as described here, since day one (often >60% AOS, suspend and events/0 going through the roof) but mainly when on wifi (15-20% per hour on wifi, 2-3% on mobile data, auto sync always on, very light usage). If I disabled data I got <1% per hour drain. Tested a bunch of stock ROMs with CF-Root.

After reading this thread I flashed SiyahKernel and things changed. I now get about 5% drain per hour on both wifi and 3g, around 25% AOS and "tvout resume wo" showing up at the top of the BBS list. I read in the first post that this is another issue and I've searched like crazy for more info on this but found nothing. I don't even have a clue what "tvout resume wo" is.

I'd be deeply grateful if anybody could point me in the right direction for this problem.
[Galaxy S II General] Molitro:
Tonight, with everything off, and I mean everything related to data conections except for gmail, leaving the wifi on, I almost got nearly 1% every two hours.

From 75% at aprox. 10:30 p.m to 69% at 8:30 a.m.

I think that as soon as anything push related is on, it starts draining just too much.

Now I switched on network location and whatsapp, and will see what happens.

Edit: Well... Unspected, but it has behaved well with whatsapp and network location.

The worst thing is defenitely email on push.

I guess I'm happy with about an hour and a half per 1% on wifi... Not great, as it was on SGS, but at least isn't the horrible thing it was a couple days ago.

The only thing left is hoping samsung fixes this soon, and wait to see what Siyah becomes when samsung releases the source for the 2.3.5 kernels (and therefor it has the newest drivers).
[Galaxy S II General] AndreiLux:
I updated the post to reflect the most recent observations.
[Galaxy S II General] Jun Hong:
go through steve kondik's Google+ to tell him? since he is the founder of cyanogenmod and also working in samsung currently?
[Galaxy S II General] Molitro:
On the 800 MHz thing explained on the first post.

May it be dependant on the governor used?

I don't see the 800 MHz state being used more than it should in my case, and I use ondemand.

The couple of times I tried to use ondemandx, aside from suffering two forced reboots, I saw that the processor jumped to 800 much more often than on ondemand.

That pic was after the first night, with wifi on and both network location and push email. It was at 93%, if I recall correctly.
[Galaxy S II General] nicolajkl:
Seems like mine worked itself out after the first few days in use..
[Galaxy S II General] carlos67:
@ Andreilux

First of all, let me say good on you for the determined/tenacious way you have gone about investigating this "bug". Bravo.

Let me ask you this though.

My battery drain is excellent - I get about 4 days with light to moderate use (Leomar ROM ki3 / CF-ROOT 4.2 agressively undervolted to 825mV@200mHZ / all sammy bloat frozen or removed / sync apps on 3 hour schedule / screen brightness at 20%........ok, now,

as you can see my battery life is very good and I'm happy with it, however, my AOS % is high ranging from 15% to 60% (15% with lots of screen on time and 60% after long periods of sleep), so I guess I have the famous Android OS "bug"

But, here's the rub, my battery life is excellent. How can you square this circle??
[Galaxy S II General] AndreiLux:
I also tested with different governors with no effect in "buggage". You have to provide more information on your screenshot, I don't know what to say simply by looking at those statistics. Do you have screen-off profiles? You said it was left overnight like that, so I guess it means that you reset it before going to bed and made the screenshot in the morning.

If that is so I can see that your device was awake for about 60 minutes of that ~9+ hour period. If you substract the screen on time from those 60 minutes you get the awake-while-screen-off time. BetterBatteryStats already has statistics on this so you can see that there under the "other" tab. If you also take the sum of the duration of all wakelocks provided by BBS then you can again substract that from the awake time. If the remainder of that is small (<2 minutes) then you don't have the bug. However if the awake period not justified by wakelocks is too long, then it is caused by this bug.

Depending on your connectivity and use of the phone, everything might vary. You're using Tegrak for undervolting? 4 days is quite good indeed. Same as I explained above, the issue does not happen at all when *all* connectivity is cut; at least that's what my experience is. Again, you need to provide more information to really assess your usage.

The rub for you is that "excellent" is relative to your perspective of what a smartphone should drain. This phone has components that have not been used on any other device before, much of them brand new. Usage is relative to every consumer and it's a imprecise science, but what we can say for certain and that's what for this issue matters and inflicts the most damage is idle usage.

We already know that the hardware itself is not at fault of anything and is capable of very long battery life. For example you can collect drain statistics with Battery Monitor Widget (you don't need the widget); it'll log your mA drain. Keep in mind that the SGS2 doesn't use a proper fuel gauge to measure it, but if your battery is properly calibrated then the estimate calculated is quite accurate for itself.

​

The mA values are estimated mAh usages for that moment in time, and as you can see it took one hour to lose 1%, and that's not the lowest I've had recorded. This is with Wifi on GSM network (80dbM signal), basically what you would and should have when you're at home. Without any data connectivity at all on plain GSM I'm using up 2mA.

The screenshot at the right is the bull**** I'm having right now, no wakelocks or anything and that should increase the idle usage, but I'm draining 80-90mA as it is like that. There are people which are luckier than me, but then again there are also people who never had at all high AOS usage, so screw them :D
[Galaxy S II General] goldbergx:
CF Root 4.2 is based on the latest Kernel released by Sammy, it has optimized drivers and some optimizations on the frequency used when using the touchscreen (I am sure there are others too).

This kernel's source code has not been released yet and because of that the battery life without the AOS bug on Siyah 1.8 (based on older sources called Update 2) is similar to CF 4.2 which has the AOS bug.

We are just waiting for these sources to be released and the devs can then make the required patches and I think that you'll get even better life on Siyah 3.0 (or whatever) than what you get now.

(I am looking forward to Saturday's match too ;) )
[Galaxy S II General] Molitro:
These are all the pics I took.

It was left at full battery, wifi on, network location and email on push (when I say email, I mean accounts other than gmail, since gmail doesn't seem to drain too much) (and wiped batterystats.bin)

I had to reflash my rom, so I'm gonna calibrate (again, I was around 60%) decently, and I let it configured as I think will be the best drain/functionality ratio.

Let's see if there are really any improvements.
[Galaxy S II General] carlos67:
hehe, yes looking forward to beating the scousers (again :rolleyes:) :D, but on a serious note, I agree with what you say. But can I pick your brain a little?

I used to use ninpo 2.0.5 & also 2.1.3 and noticed that cpu went to 1Ghz just on touching the screen (could tell this using SetCPU). However, now I'm using cf-root 4.2 with Tegrak o/c app (not for overclocking, but just for undervolting) I don't have SetCPU anymore and was wondering what speed the cpu now jumps to (on cf-root) when simply touching the screen?

Would be grateful to anyone who knows this.

btw, aren't you being a little presumptious that cf-root 4.2 still has the AOS "bug"? How do you know Samsung didn't fix it? :)
[Galaxy S II General] Molitro:
KI3/8 it's been around for a while. It's more than tested.
[Galaxy S II General] carlos67:
Yes, using Tegrak succesfully to u/v. Notice from your current draw stats that there is a direct correlation between battery temperature and current draw ;). I discussed this at length with Nobnut over on betterbatterystats thread and we were both of the opinion that, although it's a complex issue, there is definitely some sort of correlation between the two stats.

Hot climate=high drain / cold climate=low drain in it's simplest terms. I have seen evidence of this on my own phone too.

btw......that's the thread where you unceremoniously flamed me to death:eek: for my post about why I believe the AOS "bug" to be nothing more than a misinterpretation of statistics. :p
[Galaxy S II General] AndreiLux:
If those screenshots are taken at the same time, then it's bad. You barely have 2minutes of wakelocks, but 16minutes of awake time for 1min30 of screen on time. The thing that perplexes me is that you have 55 minutes out of deep sleep, but it's not recorded as awake by BBS, did you really reset them both at the same time? Its also easier to set custom references in BBS than to use the "since charged" period. I haven't actually checked if BBS awake is the sum of all time out of deep sleep for me, so I'll keep that in mind. But as far as I can tell the only explanation would be the suspend bug, but only in a light case for you. Wiping batterystats while doing such testing is *bad* since you don't really know if those 7% are really 7% on an uncalibrated battery.

Well because the drain and high AOS is still there with stock kernels, lol. Kind of a silly question.

As for that screentouch frequency bug: it's an issue with overclocked kernels not adjusting the touchscreen driver to the increased number of frequency states. I explained the issue here.

Uhhh, the temperature is just from a temperature sensor. The battery itself doesn't get too hot when you drain it in normal usage. The whole body of the phone gets warm when using it under load, and most of the heat is given off by the SoC. Of course if you have it in your hands or in your pocket it'll get warmer... the human body is 37°C. In that screenshot of mine it's just that I was using it before and then left it on the table, and my room temperature is about 25°C.
[Galaxy S II General] Molitro:
I'll do it again (properly) after the calibration.