I am getting really tired of having to reboot to "fix" this battery eatting bug. The phone will not sleep like this and it sucks battery extremely fast when this happens. The phone gets into a loop trying to suspend. This also seems to commonly be a big part of the loss of signal issue. Please please please get this fixed! This is supposed to be your flagship phone that we just spent big money purchasing. Unfortunately, your 14 day return policy kind of limits options at this point.
Please read more carefully when attempting to troll. Those images are from phones NOT experiencing the bug. "Android OS" doesn't work like you seem to think it does and should never be more than 20ish% even if you aren't touching your phone. The bottom line is that the "event/0" and "suspend" processes are bugging out and the phone is not working as intended. It's not at all unreasonable to expect a 600 dollar phone to work correctly, if not out of the box, with timely updates.
Samsung can fix this. It's a problem with their kernel. Samsung has been known to not support their devices very well. We are simply asking that Sprint put some pressure on them to at least address the problem. They fixed this exact problem once with the original Galaxy S (though it took them many months). It should take less time for them to fix it again for the S2.
I am sure you will get far in life with your "good enough" attitude. Sorry but as a programmer there is no such thing as "good enough" it is either programmed correctly or there are errors (bugs) which need correcting.
Those screen shots arent mine either. They are just examples given by the person who programmed the kernel with the bug removed.
I think the trollers here would be the ones who have 2 posts on this forum. Bright guy.
Look I was trying to understand the issue. I posted actual screen shots of my battery usage which showed more than 50 percent OS usage with 20+ hours off the battery.
In return, we get a battery usage display screen that shows two days. Big deal, I could do that. Where is the OS usage display on that example then? What does this screen shot demonstrate?
You guys are evidently too important (or lazy) to provide evidence of your problems other than to make cracks about going far in life with a "good enough" attitude. I suspect that this entire thread is making a little tiny mole hill into a mountain. You complain, but offer nothing other than "I don't need to explain how I use my phone or how much battery I get." Why even post a thread with an issue if you don't want to post up your usage?
Talk about a useless thread!
I'm not sure what other evidence or explanation you want since it's all there in the post at XDA. You'll see that the bug affects phones that are used more often since it tries and fails to go into sleep mode more often, meaning the bug hits the users who need the most battery life the hardest.
Your second set of screenshots show that you barely used the phone during those 2+ days which means it would be much less affected by the bug while your first set of screenshots show that you were affected by the bug. Your awake and screen on times should generally correspond with each other but this bug causes the awake time to be much greater than the screen on time. The less you wake the phone the less chance it has to suffer from this bug.
While I'm not sure if battery life would be substantially improved if Samsung decides (highly unlikely it seems) to fix this bug, I'm betting that getting rid of an extra hour or so of full load during the day my phone suffers from would let me squeeze out a bit more from the battery.
The worst part is the original Galaxy S suffered from this bug, or one very similar, and Samsung has done nothing about it, leaving the only option of rooting and flashing a custom kernal to fix it.
Thank you. I appreciate your explanation. The XDA thread was certainly focused on those who had experience with the issue of awake time, but really didn't offer an explanation to those of us who have not looked in to this in detail. The problem with starting a thread and assuming everyone knows what the issue is results in confusion and some apathy on the part of those who cannot understand the concept displayed.
I was attempting to see what the issue was so that it could be discussed in reference to the OP's problem. It is clear now that the intent was simply to publicize the issue, and not to actually seek a solution. Unfortunately, an understanding of the concept is necessary before one can expect a groundswell of support for a bug fix. The OP and others came on this forum with a different set of expectations than what you normally see here.
Perhaps Samsung will address this issue, but I'm not sure if this forum is the place to seek that support. XDA is a technologically oriented forum. This forum; not so much.
No problem. The only way for Samsung to ever consider fixing this problem is to get Sprint, AT&T, and T-Mobile to get them to which means the users on those networks have to complain about it to their providers. However, this is one of those problems that most people just won't notice. Most people will just charge their phone when it gets low and if they think their battery isn't lasting long enough they'd probably just get the phone replaced by their carrier. It's too bad more people don't do a bit more research since many more people would be complaining about this which might just be enough to get the carriers to make Samsung fix this problem.
Rumor is the Nexus Prime is going to be using a Qualcomm SoC and not Samsung's SoC which might mean that upcoming phone won't suffer from this problem. That being said, it'll be interesting to see if T-Mobile's version suffers from this problem as well since it's also not using Samsung's SoC.
As indicated my reason for posting to these forums as this seems to be one of the few if any ways to get Sprint to pay attention. Talking to customer service people won't get us anywhere unfortunately. I wasn't coming here for support so much as to say hey, there is a problem and this needs to be addressed. I don't agree it is a minor issue. Here is my phone today after about 5 hours where it lost around 40% from doing nothing. I can't make it a day with this issue and I barely used my phone.
Another thread: http://forum.xda-developers.com/showthread.php?t=1271765
Seems they may have found the reason. Waiting for the fix. Mine use to die within 6-8 hours, but now its lasting 8-12 hours with the SD format. Still Android OS is not sleeping right and events/0 and suspend linux processes burn up the CPU
Aha. Unintentionally, I probably fixed my phone at the outset. I purchased a 32GB card and formatted it in the phone when I first got my phone. That would explain my superior battery life all this time. Also, I do experience periods of awake time when the phone should be sleeping. It would be nice to receive an explanation from Samsung regarding why this occurs when logically it should not.
Is there any more news on a fix? Yesterday my phone died after about 8 hrs. and the android os used over 70 % of the battery. It seems that this problem is intermittent so it should be fixable with an UPDATE.
I commented on this thread a while ago because I was having the "bug" issue all the time. Some how the issue went away after I restarted. I would recommend downloading an app that can track this rouge bug ( I used watchdog), and if you see it's happening... Restart. If it happens again.... Restart. Keep restarting until it stops.
I hope there is an update and a fix for this, but for now I believe its just bad luck that makes it happen.
Since it "went away" I've had great battery life. See below. This was from last week, my best battery life yet. Normal/light usage. This is much better then before.