yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Quist:
Just to add to the discussion here. I began seeing the Android OS problem creepng up as soon as I got the phone, but decided to try and break in the battery as usual.

Upon the first start of the device, I said I didn't want to backup/restore the phone through Google and still saw it.

I decided to update to KE2 and was still seeing it - ironically, after updating to KE2, it seemed worse. So I did a factory reset and removed my microSD card and formated the usb memory (on-board card). Everything was great until I copied a bunch of pictures from my server onto the SGSII over wifi. Since then, Android OS has been like it's on steroids - just gobbling up battery like no tomorrow, pulling the battery doesn't help, it keeps eating when I reboot.

A few thoughts:

From my other devices, I've always noticed that running wifi and 3G simultaneously kills things quickly, so I've gotten into the habit of toggling wifi off when heading out and toggling mobile data off when getting home and I also set wifi to not disconnect when the screen goes off. Also, I too use a DIR-655, have the name hidden and use WPA2 security passwords and MAC filtering. My 3G operator is 3 in Sweden, which only has a 3G network, no 2G.

I'm also wondering if there is something some of us are doing that is precipitating this, for instance, if regular Joe User who accepts all the defaults, logs into Google, Exchange, Facebook, Twitter, Kies air, etc. etc. etc. for some reason is less likely to run into this? Just brainstorming here...
[Galaxy S II Original Android Development] slyydrr:
I've been able to confirm also now that FastDormancy doesn't poll when Wifi is enabled and a connection is established. I'll update this in the first post as well.

It would also appear as though The_Revenge is likely correct in that FastDormancy is something the network controls now that I've done more reading on the subject.
[Galaxy S II Original Android Development] slyydrr:
That's an odd experience. I'm still trying to determine the true relationship between Android OS and FastDormancy. So far the only relationship that I've had time to check on is with data being turned off completely. This causes FastDormancy to stop polling and the Android OS usage was down considerably.
[Galaxy S II Original Android Development] DocRambone:
Its seems confirmed that the os bug halts when data connection is off.

And t seems that this bug came with 2.3.3.

Any change log for 2.3.3 somewhere?

Edit: and also halted when screen is lit or usb cable is attached
[Galaxy S II Original Android Development] slyydrr:
I haven't been able to determine if the issue is halted when the USB cable is attached as the battery stats don't update when it's receiving a charge. Also when the screen is on, I believe it's just masking the bug as running side by side, the display naturally consumes more power.

I haven't seen a changelog for 2.3.3 anywhere but then again I haven't look really hard either. :P
[Galaxy S II Original Android Development] earthdome:
I'm in Germany too and have a good battery life. Currently at 48% after 25 hours of light/normal usage

edit: I'm new to android. So i don't know how to do this log. I'll appreciate any guide. Thanks
[Galaxy S II Original Android Development] slyydrr:
Any chance you can download aLogCat from the market and check to see if you see this?

D/FastDormancy( 2822): before ======= ENTER DORMANCY =======

D/FastDormancy( 2822): [FD] ON default: true

D/FastDormancy( 2822): Before mDormFlag: true in getCapaDormancy()

D/FastDormancy( 2822): After mDormFlag: true in getCapaDormancy()

======= ENTER DORMANCY =======

Pay special attention to lines 3 and 4 where getCapaDormancy() returns true. It might be easiest if you filter aLogCat by "FastDormancy"

Thanks!
[Galaxy S II Original Android Development] earthdome:
Thanks! I let aLogcat run when screen is on and off. After saving the log to my computer, i didn't find line 3 and 4.

FastDormancy( 2856): [FD] INTENT ACTION android.intent.action.SCREEN_OFF

D/FastDormancy( 2856): [FD] mIsScreenOn: false

I/BatteryService( 3622): Screen goes off
[Galaxy S II Original Android Development] slyydrr:
Oh, do you have wifi on? If so, you'd have to disable that as well as wifi overrides FastDormancy. Sorry, forgot to mention that :P
[Galaxy S II Original Android Development] earthdome:
I see. hehe. No problem

D/FastDormancy( 2856): before ======= ENTER DORMANCY =======

D/FastDormancy( 2856): [FD] ON default: true

D/FastDormancy( 2856): Before mDormFlag: true in getCapaDormancy()

D/FastDormancy( 2856): After mDormFlag: true in getCapaDormancy()

W/FastDormancy( 2856): ======= ENTER DORMANCY =======

D/FastDormancy( 2856): ======= FAST DORMANCY Enter =======
[Galaxy S II Original Android Development] slyydrr:
Thanks man! It would seem as though German networks support Fast Dormancy then.

Out of curiosity, are you on O2 or T-Mo? And also, what is your Android OS usage like in battery stats? Both % and CPU Time used if possible, along with the total time of your current charge. :)
[Galaxy S II Original Android Development] earthdome:
I'm on O2. Android OS CPU Time : 2h 43m
[Galaxy S II Original Android Development] turborider:
+++++100% well said mate :D
[Galaxy S II Original Android Development] walda:
Hey

I´m on A1 in Austria, no national Roaming needed.

I have high AOS% in general, but only loose ~1.5% / h in Standby - so i am happy.

Cant screen you my battery now, because i unplugged it before and after that i was testing with JuiceDefender.

The Logcat is without JD, without Wifi and Data=On of course.
[Galaxy S II Original Android Development] slyydrr:
Thanks for the logs walda, you seem to be experiencing the same idle drain I am - 1-2% per hour, even with the high Android OS. So it's looking more like even with the high polling rate, that perhaps FastDormancy isn't directly related to the high Android OS usage.

However, thankfully due to looking in that area, it would seem that the Android OS usage is tied to the data connection itself. I'm currently logging about 5min CPU usage per hour with data enabled, regardless of whether wifi is turned on. I will turn off my data overnight and evaluate the CPU time consumed then. If it's as I experienced earlier, it should drop.

I'll report back w/ more details in the morning as it's now 3AM. Today has been a long day of reading/testing/more reading...
[Galaxy S II Original Android Development] sunilkaura:
Hey guys,

Been following all the battery related threads for a while now, thought it was time to contribute.

My battery life has been pretty good - even after updating to XWKE1, nothing changed. My rough usage as follows:

Usually 16-17 hrs of use

Display on for 3 1/2 - 4 hrs

Android OS CPU time of around 1hr

Lots of music - 2/3 hrs

Browsing, words with friends and engadget app

No fb updating - facez widget updated manually

Gmail at push, *but*

I use JDefender on customise, data enable every 15 mins and JD controls my wifi, and Android wifi set to sleep NEVER.

I had found that the Samsung control of the wifi was flaky, but JD switches it on and off with the screen within a second. This also means that when it syncs data in the background when the screen is off, it will check for wifi first before enabling the data connection.

I work from home, so there is generally always a wifi connection, but even when I'm out, the battery still lasts a good long time.

I am rooted and have frozen a list v similar to boosters apps, and my battery life is v acceptable.

I have my alogcat dump below, with JD off, wifi off, across a few minuted of screen on/off time. I'm on Vodafone, using a phone bought on O2 in the UK.

Guys I'm no expert but I really hope this helps.

Sun

05-15 08:59:48.225 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 08:59:53.235 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 08:59:58.239 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 08:59:59.475 2866 2866 D FastDormancy: [FD] INTENT ACTION android.intent.action.SCREEN_OFF

05-15 08:59:59.475 2866 2866 D FastDormancy: [FD] mIsScreenOn: false

05-15 09:00:16.780 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 09:00:16.780 2866 2866 D FastDormancy: [FD] ON default: true

05-15 09:00:16.780 2866 2866 D FastDormancy: Before mDormFlag: true in getCapaDormancy()

05-15 09:00:16.795 2866 2866 D FastDormancy: After mDormFlag: true in getCapaDormancy()

05-15 09:00:16.795 2866 2866 W FastDormancy: ======= ENTER DORMANCY =======

05-15 09:00:16.800 2866 2866 D FastDormancy: ======= FAST DORMANCY Already Entered ======

05-15 09:01:43.800 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 09:01:44.300 2866 2866 D FastDormancy: [FD] INTENT ACTION android.intent.action.SCREEN_ON

05-15 09:01:44.300 2866 2866 D FastDormancy: [FD] mIsScreenOn: true

05-15 09:01:48.824 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 09:01:53.835 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 09:01:58.845 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 09:02:03.854 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 09:02:08.865 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 09:02:13.874 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======

05-15 09:02:18.885 2866 2866 D FastDormancy: before ======= ENTER DORMANCY =======
[Galaxy S II Original Android Development] Miracle1980:
Im not expert but let's see if this could be related. I went to sleep yesterday with the phone at 80% of battery. I left aereo mode and everything was off (wi-fi,data,bluethoot...). This morning i had the phone shutted off (first problem). I switched on and the battery was at 36%!!!

What is this? It's this problem?
[Galaxy S II Original Android Development] DocRambone:
"Fast Dormancy is a mechanism that enables mobile devices to notify the

base stations when the radio resource allocated to the device is no

longer in use, so that the radio resource could be immediately

released other than waiting for a timeout event."

So i guess this is the "cell standby" in battery chart

Any god tool to analyse the data traffic from sgs2?
[Galaxy S II Original Android Development] NIK516:
i dont know how this will help but this is what happened to me.

I had the os issue with my os at a massive 90%.

I following and contributing to all the battery threads.

Then one day i said stuff it im going to watch as much video over wifi and play as much games and stuff that i can on it till the battery runs dead, i did this till the phone died then i restarted the phone and charged it till 100%, then i used the hell out of it again not till dead this time, then i charged it from 30% till 100%

Then all of a sudden my os started to drop down, now its at 11%.

I cant explain why im guessing that i needed to wear in the battery and maybe the hardware ? if that even makes sense? the only think i did do is update to ke1 but the os dropped before i updated and only got better with the update?

check my previous posts for my problems.

D/FastDormancy( 2820): [FD] INTENT ACTION android.intent.action.SCREEN_OFF

D/FastDormancy( 2820): [FD] mIsScreenOn: false

D/FastDormancy( 2820): [FD] INTENT ACTION android.intent.action.SCREEN_ON

D/FastDormancy( 2820): [FD] mIsScreenOn: true

D/FastDormancy( 2820): [FD] INTENT ACTION android.intent.action.SCREEN_OFF

D/FastDormancy( 2820): [FD] mIsScreenOn: false

D/FastDormancy( 2820): [FD] INTENT ACTION android.intent.action.SCREEN_ON

D/FastDormancy( 2820): [FD] mIsScreenOn: true

D/FastDormancy( 2820): [FD] INTENT ACTION android.intent.action.SCREEN_OFF

D/FastDormancy( 2820): [FD] mIsScreenOn: false

D/FastDormancy( 2820): [FD] INTENT ACTION android.intent.action.SCREEN_ON

D/FastDormancy( 2820): [FD] mIsScreenOn: true

D/FastDormancy( 2820): [FD] INTENT ACTION android.intent.action.SCREEN_OFF

D/FastDormancy( 2820): [FD] mIsScreenOn: false

D/FastDormancy( 2820): [FD] INTENT ACTION android.intent.action.SCREEN_ON

D/FastDormancy( 2820): [FD] mIsScreenOn: true

D/FastDormancy( 2820): [FD] INTENT ACTION android.intent.action.SCREEN_OFF

D/FastDormancy( 2820): [FD] mIsScreenOn: false

D/FastDormancy( 2820): [FD] INTENT ACTION android.intent.action.SCREEN_ON

D/FastDormancy( 2820): [FD] mIsScreenOn: true
[Galaxy S II Original Android Development] Kur0saki:
Did you have the screen on all the time? Or did u turn it on and off, while using alogcat?
[Galaxy S II Original Android Development] The_Revenge:
good morning xda :)

well, okay, since some people claim that this bug only happens when screen is off/charging is disconnected, i left my phone off the pc/charger while sleeping. i checked logcat again, getCapaDormancy always returned true, no difference between screen on/off or charging connected/disconnected. heres what battery usage gives me:

http://img155.imageshack.us/i/sc20110515114241.jpg

http://img189.imageshack.us/i/sc20110515114246.jpg

so the android OS is active only 23minutes in the whole standby time of 7 hours, seems ok/normal to me.
[Galaxy S II Original Android Development] Kur0saki:
How much battery did you loose while sleeping?
[Galaxy S II Original Android Development] The_Revenge:
8%. the google maps process kept my phone awake for a total of 35minutes.
[Galaxy S II Original Android Development] walda:
hm. maybe i'm crazy but i think as i switched off usb debugging the loglines are more less than before.

dont know if it affects aos%

sent from my SGSII via T*patalk
[Galaxy S II Original Android Development] Quist:
Yesterday, my Android OS went crazy after copying loads of media files from my server to my device using EStrong's file explorer over wifi and then killing the process because it was taking too long.

I tried pulling the battery, but nothing worked. It was eating 20-30% battery per hour. I was going to root and freeze loads of things, then realized I may have a screen issue and if I'm going to return this unit, I wanted to leave it unrooted.

Anyway, finally did a factory restore and formated the internal card. I refused Google's backup and restore and it was late, so I didn't install anything or set up wifi again. Over night my battery drained 1% over 3.5 hours and Android OS was well under control - still there, but a reasonable relative consumption.

Have now gone through and reinstalled most things. I finally decided to throw caution to the wind and reinstall EStrong's and set up my wifi and the reading hub. After 8.5 hours on battery, I'm at 46%. The three top battery consumers are Display 44%, Android system 15% and Android OS 13%.

Having only had the phone since Thursday, I've not properly given the battery app a chance to acclimate to my usage pattern nor gotten the battery in shape, so I'm throwing caution to the wind and will use as best I can for the next few days to see if things improve on their own. At this pace, however, I should be getting about 17 hours usage, which is adequate for now.
[Galaxy S II Original Android Development] ignign0kt:
I updated to the newest firmware and Android OS is using more than the Display after a couple hours of light use

Display was always higher on the old firmware

So it looks like the newer firmware actually made mine worse...
[Galaxy S II Original Android Development] xdadroid88:
Of course it is network dependent.

In the SGS1 FD was disabled for O2 Germany. I don't know whehter this is still true for the SGS2.

Just check out the customer.xml in the CSC section:

<Settings>
−
<Main>
−
<Network>
<NbFastDormancy>2</NbFastDormancy>
−
<FastDormancy>
<NetworkName>o2 - de</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
</FastDormancy>

So it shouldn't be a problem to disable it in the SGS2 for your network for further testing.
[Galaxy S II Original Android Development] earthdome:
i have checked the file. and it's all off for all network providers listed

edit: my guess is, for unlisted network providers, default is on

- <Settings>
- <Main>
- <Network>
<NbFastDormancy>10</NbFastDormancy>
- <FastDormancy>
<NetworkName>O2 UK Postpay</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
<LCDStatus>on</LCDStatus>
</FastDormancy>
- <FastDormancy>
<NetworkName>O2 UK Postpay</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
<LCDStatus>off</LCDStatus>
</FastDormancy>
- <FastDormancy>
<NetworkName>O2 UK Prepay</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
<LCDStatus>on</LCDStatus>
</FastDormancy>
- <FastDormancy>
<NetworkName>O2 UK Prepay</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
<LCDStatus>off</LCDStatus>
</FastDormancy>
- <FastDormancy>
<NetworkName>H3G</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
<LCDStatus>on</LCDStatus>
</FastDormancy>
- <FastDormancy>
<NetworkName>H3G</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
<LCDStatus>off</LCDStatus>
</FastDormancy>
- <FastDormancy>
<NetworkName>H3G IE</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
<LCDStatus>on</LCDStatus>
</FastDormancy>
- <FastDormancy>
<NetworkName>H3G IE</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
<LCDStatus>off</LCDStatus>
</FastDormancy>
- <FastDormancy>
<NetworkName>O2 IRL</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
<LCDStatus>on</LCDStatus>
</FastDormancy>
- <FastDormancy>
<NetworkName>O2 IRL</NetworkName>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
<LCDStatus>off</LCDStatus>
</FastDormancy>
<AutoFastDormancy>on</AutoFastDormancy>
[Galaxy S II Original Android Development] DocRambone:
You also has this line :<AutoFastDormancy>on</AutoFastDormancy>

in sgs 2 customer csc
[Galaxy S II Original Android Development] The_Revenge:
i checked the xml files in the csc section on my phone, and i saw there are only UK networks listed (my phone came from UK), so that may be the reason why FD is enabled here.
[Galaxy S II Original Android Development] bigmo7:
Display should be the thing that takes up the most battery in most cases....
[Galaxy S II Original Android Development] slyydrr:
Yep, I came to this conclusion last night (noted in my "additional findings" section in the original post) regarding network dependency. However the csc info is good. I'll look through this file and see if I can control it being on/off for AT&T USA. I'll dig through an SGS1 CSC file. I'm still curious if this value is controlled through the CSC file or set upon connecting to the actual network.
[Galaxy S II Original Android Development] RogerPodacter:
I'm not sure that is normal. Right now my nexus one has been unplugged 10 hours, 80% battery left, and android OS only shows 1 min 23 sec CPU usage. And android OS is at the bottom at 2%.
[Galaxy S II Original Android Development] DocRambone:
Its clear that this bug is deeper down in the android core.

Only 100% sure way to disable it is by shutting down data connection.

Or background data connection.
[Galaxy S II Original Android Development] slyydrr:
That's what I suspected but I disabled my data connection last night and my Android OS usage rose to 60% by morning.

I agree that it's likely in the core and still believe it to be data related but I'm a bit puzzled at the moment.
[Galaxy S II Original Android Development] kaassema:
It has been said before, but:

You can NOT use percentages usage to see wether the bug is there - Don't you think it is pure logic for a device to be spending 60% of all power consumed on core processes, when idle (e.g. during the night)?

It would have been a hell of a lot weirder if Android OS would be at 2%, and Display at 40%, wouldn't it?

You should either look at the graphic of the battery usage, or the CPU-time consumed per process
[Galaxy S II Original Android Development] Arthur Hucksake:
Just checked my phone now.

6h 8m on battery.

Android OS is 7% and 10m 8s total.

Not a problem I assume? lol

Mind you, down to 51% battery and that was just from 20 minutes of surfing the web, couple of short calls and few texts. What I would call light use.

Compared to my previous iPhone 4, the battery is shockingly rubbish.
[Galaxy S II Original Android Development] Sanchless:
My power usage, That's 2h30m of display on time and CPU time on Android OS is 1h20m.

Don't know what Earth is doing there cause I didn't use it at all, but it hasn't gone up since I force stopped it.

This is on totally stock firmware nothing uninstalled and KE2 firmware. Data on but inactive cause I'm connected to wifi.
[Galaxy S II Original Android Development] kaassema:
Here are some battery graphs of my SGS2 experiencing the bug...

The first 2 screenshots are after 10 hours and 33 minutes, the second 2 screenshots are 2 hours later

It has been on juice for all night, untill I got up.

The graph:

The first 3 hours everything is cool (some mild usage, all kinds of backgroundsyncing activated of course). Then I used some more stuff (in particular wifi). Afterwards, wifi got disabled again... But then the battery-drianing starts.

Almost 11 hours after disconnecting from the charger, I checked the graph - see screenshots. App usage for top 3:

-Display, CPU-total: 1u 44m 15s

-Android-system, CPU-total: 41m 46s

-Wifi-sharing, CPU-total: 27m 28s

-Maps, CPU-total: 24m 50s; CPU-foreground: 6 seconds; GPS: 9 seconds; Staying awake: 1u 9m 45s

Since I specifically disabled wifi-sharing in the settings, the latter was a bit suspicious. I immediately forced-stopped Wifi-sharing from within the batterygraph. The other thing that sparked me, was Maps: using up 24m of CPU-power, and keeping the phone awake for over an hour??

Anyway, next two screenshots are from 2 hours after forced-stopping wifi-sharing; The graph finally seems to level, taking a slow pace from 30 tot 27% in 2 hours time...
[Galaxy S II Original Android Development] voodoochild2008:
Has anyone tried getting through to Samsung to see if they even accept there is an issue, if they do then a fix could be due, if they say all seems fine to them then looks like its down to some clever person on here to sort.
[Galaxy S II Original Android Development] BoogWeed:
I was going to say the same thing.

Maybe someone who knows what they are talking about should try to get in contact with some Android engineers at Google as this is obviously an 'issue' with Android.
[Galaxy S II Original Android Development] NitroOnTheRocks:
While looking at the customer.xml file from the csc folder on my SGS2 i recognized these values, remembering them from this thread.

Maybe this could help.

<Network>
[COLOR="Red"]<NbFastDormancy>1</NbFastDormancy>
<FastDormancy>
<FastDormancyEnableStatus>off</FastDormancyEnableStatus>
</FastDormancy>[/COLOR]
<NbSOSNumber>1</NbSOSNumber>
<SOSNumber>112</SOSNumber>
<NbSOSNumberNoSIM>1</NbSOSNumberNoSIM>
<SOSNumberNoSIM>112</SOSNumberNoSIM>
<AutoProfile>on</AutoProfile>
<AutoVoicemail>off</AutoVoicemail>
<AutoEmailAccount>off</AutoEmailAccount>
<AutoBookmark>off</AutoBookmark>
<AutoLink>off</AutoLink>
<AutoSyncML>off</AutoSyncML>
[COLOR="#ff0000"]<AutoFastDormancy>off</AutoFastDormancy>[/COLOR]
</Network>

PDA: KE1

PHONE: KDJ

CSC: KD3 (XEN)
[Galaxy S II Original Android Development] xdadroid88:
Why? This is a well known GB problem independent from Samsung: http://code.google.com/p/android/issues/detail?id=15057

Take a look a the status in the top left corner...
[Galaxy S II Original Android Development] mosd:
really strange that not everyone suffers from this bug?!
[Galaxy S II Original Android Development] DocRambone:
Its Samsung's task to fix the problems, they sell the phones and should deliver a fully functional unit. As now, some users has severe problems and Samsung should make a swift action, or recall the affected units.