yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] nkrick:
Since the Captivate doesn't have a true notification LED people have created ways to use the capacitive buttons as notification LEDs. The problem is that since they are not true notification LEDs, features that actual notification LEDs have (such as blinking and changing colors) are not supported. A true notification LED can be told to "blink blue" and it will keep blinking blue until something tells it to stop. There is no need to run code and use the CPU to keep turning the LED on and off. Since the capacitive button LEDs were not designed to be notification LEDs, they don't have the ability to be told to "blink" and then just keep blinking. Instead, any app (like BLN) that has the ability to make them blink is a running app that consumes CPU and power as it runs and tells the LED "turn on...turn off...turn on...turn off..."

A not nice side affect (besides the battery/CPU usage of the app) is that the phone can't go into a complete deep sleep because the app blinking the lights needs to run which requires the CPU, which means that blinking capacitive button LED is draining your battery more than the power it takes to light the LED itself.
[Captivate Android Development] mbc663:
Well said.
[Captivate Android Development] RootTheMachine:
And, once all of the CM features are implemented, there should be a way to configure the notifications for each individual app, just like in CM7.
[Captivate Android Development] aHecticLife:
+1
[Captivate Android Development] Felixcm88:
Hello I've been using CM9 for a few days and think I've found some bugs, this is the right place to put it or I have to send a mail or something ?
[Captivate Android Development] Joecascio2000:
You obviously didn't read the OP. So I don't think you should be posting bugs just yet. Go back read the WHOLE first post and the last 10 pages of this thread. Believe me I bet it's already been said before.
[Captivate Android Development] pizz0wn3d:
It HAS been said before, multiple times. I don't post in a thread unless I've done AT LEAST that much reading.

Herp derp Captivate XDA Premium.
[Captivate Android Development] RaptorOne3:
Android OS keep awake battery drain...

While I'm experiencing great battery life, overall, I'm still very confused about this Android OS battery drain... It's a little disappointing honestly that there hasn't been much discussion about it in other development forums as it is a very well known issue in the Galaxy Nexus community.

It's CLEARLY draining the battery but gets written off as merely a "display bug". I fear this is more than just Android OS battery usage displaying incorrectly. This has been a well known issue with the Galaxy Nexus, and it's showing up on all devices with Android 4.0.2+ across the board and no one has stopped to think that perhaps it's the same bug the Galaxy Nexus is having issues with?

Hopefully Kang can shed some light on this!

It's clearly consuming the resources batt stats reports it is, the display is no error. After HOURS of just letting the phone sit idle, not turning the screen on except to check the battery level, I'm at 77%...

The Android OS keep awake battery drain bug, is a well known issue in the Galaxy Nexus community and has been for some time. They just updated the Galaxy Nexus to 4.0.4 and apparently fixed the issue. ( http://www.xda-developers.com/android/galaxy-nexus-gets-ics-4-0-4-update/ )

SO now I'm wondering if there are there any plans to address this issue for CM9 by any chance? No pun intended by the way, I'm just curious if any attention is being devoted to this based on the obvious implications?

Attached below are the batt stats of the issue I'm referring to -

As you can see, Android OS keep awake was pushing the phone out of sleep for 3hrs! That's definitely not normal!

​
[Captivate Android Development] Joecascio2000:
8 hours on battery and only down 27% does not mean it's draining battery. Plus I see you have poor signal and Cell standby is at 13%. Check what "Time without signal" is at? If it's high you found your drain.
[Captivate Android Development] RaptorOne3:
My cell signal is maxed out, all bars are lit up. The H is blue because I modded it myself, among other things (notice the battery mod and the blue alert icon in the status bar?). I have background data disabled so it's not connected to google otherwise the whole thing would be blue (hence the exclamation point in the status bar)... I did some custom modding. Forgot to point that out... I didn't realize it would cause any confusion.

Did you happen to notice the "keep awake" time on Android OS though? And the correlation with the Galaxy Nexus having this issue and it being resolved with 4.0.4?
[Captivate Android Development] Joecascio2000:
My keep awake is at 6h 0m 5s! Big deal, I still get easily 32+ hours with 3 hours screen on time.
[Captivate Android Development] RaptorOne3:
Dude... I already said I get great battery life overall... Did you even read my post? Perhaps you should RE READ it? I edited it for clarification purposes...

This is a big deal and I think it's silly for anyone who uses a custom ROM to just shrug it off... It should be even more of a concern for the developers of the ROM. They could improve upon the ROM tremendously by looking into this issue. I guarantee it. And now that it's been fixed on the Galaxy Nexus, perhaps it's a fix that could be implemented into CM9 or 4.0.3 in general?

It's a well known issue on the Galaxy Nexus and has been directly associated as an Android 4.0 bug and well documented, lets not forget that! Go read up on it over in the Galaxy Nexus forum...
[Captivate Android Development] b-eock:
It is a graphical bug, nothing more.... It is only displaying more than it should. In real life it has none to little impact on battery...
[Captivate Android Development] Joecascio2000:
I read your post very clearly. When I was on Serendipity (Some number I forgot) there was actually a keep awake bug if you kept your phone on for long periods of time without rebooting and if you didn't catch it and reboot, your phone would be dead in a matter of hours. It's clearly just a display bug.
[Captivate Android Development] ScottyNuttz:
It's not CM9, it's the Nexus S source. That's why (in case you didn't know) they stopped the update for that device.

But it's fixed in the 4.0.4 release that leaked for that device, so now we have to wait for it to be included in the AOSP source code. Until then, just enjoy ICS.
[Captivate Android Development] RaptorOne3:
Oh really? Then how do you explain the images I posted? You're telling me that the "keep awake" time is erroneous and it's just some nonchalant graphical error? Could you elaborate on how you know this please?

And what about the whole realization that it's not just a graphical error by the Galaxy Nexus community? I followed the developments of this issue for the Galaxy Nexus very closely. It's not just a graphical bug on that device.

I'm sorry but I refuse to believe that it's just some nonchalant display calculation error...

If it is, why wasn't it fixed already?

Not to mention, again, the unexplainable battery draining while the device is in sleep mode...
[Captivate Android Development] b-eock:
What keep awake time, did you not see my post a few pages back, 1st cycle no calibration battery time. It is great, stop being a troll.

http://dl.xda-developers.com/attachdl/0b5f5f8be7a440a3f6fa9a96b206910d/4f30a566/8/8/9/2/1/2/uploadfromtaptalk1328486771851.jpg
[Captivate Android Development] RaptorOne3:
I'm aware of where our build came from. They stopped the Nexus S updates because of the same damn bug! That was also well documented... And it was not a display bug. It was actually keeping the device awake!

If it was fixed on one device, it can be fixed on another device... We just need to know what the problem was!

---------- Post added at 11:16 PM ---------- Previous post was at 11:15 PM ----------

What????? I've been running Build 15 for a lot more than 1 cycle man... :confused:

The keep awake time in the pictures I posted...

Lets not resort to childish insults now... I'm expressing legitimate concern and you aren't helping not one bit...
[Captivate Android Development] ptesmoke:
I would have to agree with you on this one. I ran an ics rom on my desire z before I sold it. it also suffered the same usage bug but was never dismissed as a graphical glitch. from what I understand they were still trying to fix it last time I checked in.

that said though I'm hoping the next build incorporates googles fix...even tho this is cm9 based...cm updates from source pretty quickly.

edit: he's not trolling...its a legitimate question...lets not be so harsh guys. ICS is still new...none of us are freakin experts with its quirks yet..
[Captivate Android Development] b-eock:
Well some of us have had experience on the ROM before the people came to this forum. Also others, such as my self, have more knowledge on things in this sense than a lot of you...
[Captivate Android Development] Joecascio2000:
Well either way, the fix is out and its listed in the known bugs. Its only a matter of time before they fix the drain/display issue. No reason to discuss an already known issue.
[Captivate Android Development] RaptorOne3:
Then please, enlighten us all mighty lord of the Android 4.0 operating system...

How exactly is this merely a graphical bug? Care to elaborate?

Straight from the post on XDAs portal/main page -

http://www.xda-developers.com/android/galaxy-nexus-gets-ics-4-0-4-update/
[Captivate Android Development] Felixcm88:
I read it, just wanna be sure if it's ok to post it here or if was better to send a mail to some one because I think is very hard to read a whole tread of 500 pages just looking for post with bugs.... And the bugs that I think I've found don't appear in the known issues ( yes I read it all before I wrote the first post).

It's the first time I do this, just wanna be sure that I do it right.

So this are the thing that I have found:

- The first time I've synchronized my Google account with the phone the pictures from G+ were downloaded to my gallery, then I stop that service, but the photos still are on my gallery and I can't remove them.

- There was one time that I turn on the phone but the menu only showed 3 or 4 applications, so I restarted and everything works fine again.

- The movie player always crash when I try to watch a video that I recorded with the phone, downloaded MoboPlayer but It's the same problem always crash.

- Twitter and Facebook doesn't synchronize with the phone.

Sorry for my bad english and if this aren't bugs, just wanna help the development of the rom...
[Captivate Android Development] RaptorOne3:
I was just curious if pawitp or any of the other developers had any idea if the fix implemented for 4.0.4 was something that could be implemented into the 4.0.3 build more than anything...
[Captivate Android Development] nakedninja42:
1) Not a ROM bug since its a Google application

2) Haven't had this issue.

3) I've been able to play back videos I recorded no problem with gallery.

4) Facebook does not sync, that is well documented through out the thread. Twitter - I always use manual sync so I can not comment on this.
[Captivate Android Development] Joecascio2000:
Also to add to the above.

If you unchecked Google photos under sync and then clear gallery data they will go away.

Twitter should sync through the twitter app.
[Captivate Android Development] ptesmoke:
much respect to you bro but tone down the arrogance a tad! ;-)
[Captivate Android Development] thecoolestcow:
Battery Issues

I have had terrible misfortune in the realm of battery stats. Ever since CM7 (and maybe even before) my phone is unable to figure out how much battery is left. Here is a common scenario:

Charge phone overnight, use phone throughout day, battery dies after 6-7 hours of moderate-heavy usage. I plug it in, reboot while plugged in, and then it reports ~60% battery left.

I know that this is a misreading of the battery and not battery drain or a rogue app because when I flash a new ROM the battery life is amazing for 1 day. The day after I flashed teamhacksung's ICS rom, I got almost 17 hours of battery life with 2.75 hours of the display being on and 30 minutes of Google Music. I was blown away! But even then it was dwindling around 5% not knowing when it would actually run out. The day after, it was back to its old tricks of misreporting the battery percentage.

Today I charged it to 100%, unplugged it, and shut it off. Then I plugged it in while it was off and let it charge to 100% again and wiped battery stats in Clockwork mod. I'm getting ok-ish battery with that, but it's not even close to how good it was when I first flashed ICS.

Anyone have any ideas what I could try?

Thanks!
[Captivate Android Development] b-eock:
I am done arguing with people that aren't worth my time. All I can say is that is a graphical issue on this ROM, if you look at the battery stats and compare to any AOSP ROM on the Captivate, you will see it is insanely better than those and STOCK!
[Captivate Android Development] Gromlakh:
+1

omg10char
[Captivate Android Development] Joecascio2000:
You know what I find arrogant? Is someone asking a question, receiving a clear answer and refusing to believe it. As if they know better. *winkyface to make it seem as if it's not an insult*
[Captivate Android Development] RaptorOne3:
I did not receive a clear answer. I was given what appeared to me, as an opinionated claim without evidence or an explanation of any sort to back up the claim.

He claims its simply a graphical bug. I asked politely, multiple times, if he wouldn't mind, to simply elaborate on HOW HE KNOWS this, at least...

He didn't seem to care about wasting his time arguing otherwise, so you'd think someone as experienced and as knowledgeable as him would have simply explained it in detail the first time and squashed the whole issue to begin with...

However, given the recent evidence that suggests that this is NOT just a graphical bug and is indeed, much more, on TOP of his neglectful responses I'm not satisfied in the least bit with any of his responses. Quite honestly almost every one of b-eocks responses were quite insulting to say the least...

Again, this issue is not just some graphical bug on the Galaxy Nexus. It has been proven to be a real issue that really drains the battery and keeps the device awake... I have posted the link to the article, it's on the front page of XDA and Kangxi himself put this information forward...

Thus, I'm awaiting a logical response from someone a little less apprehensive towards legitimate concerns based on evidencial circumstances.
[Captivate Android Development] b-eock:
Well on our device, it has little to no impact. Why are you so worried, its not like your phone dies, like it would on CM7
[Captivate Android Development] Joecascio2000:
And I replied:

And your telling me you didn't get an answer out of all that???

1) As said many times, not only by me, ITS A DISPLAY BUG.

2) The proof is right in front of you. If the phone was kept awake that long in 8 hours you would have no battery left. I know this from personal experience.

3) My guess is THS already fixed the leak but couldn't fix the display.
[Captivate Android Development] RaptorOne3:
Well what about this? - http://www.xda-developers.com/android/galaxy-nexus-gets-ics-4-0-4-update/

Now, my concern here is if you compare the battery drain, Android OS "keep awake" issues, and the images I posted to those in the Galaxy Nexus forums, they're EXACTLY THE SAME...

You're telling me there's absolutely no correlation and this is simply just a display bug...

Yet, I'm experiencing the same batter drain, the same keep awake issues and I have the evidence to prove it...

Where's the evidence that this is merely a display bug?

Seems to me that all the evidence points to the contrary!

Care to explain?

PS- And I want to be perfectly clear, I'm not implying that this is a major issue or anything of the sort... It's just confusing. If it's a graphical bug, how and why? If Teamhacksung fixed the "keep awake" issue but didn't fix the display of that data within batt stats, how come and why not? I'm just curious... Just looking for a little more clarification on the issue considering the contrary evidence from other areas of development, not that I deserve it or that any of us mere mortals are entitled to anything of any sort, but I'm just curious given the evidencial circumstances.

If anyone would care to elaborate and explain this a little more, it would be awesome, otherwise you're just adding to the nonsense.
[Captivate Android Development] Joecascio2000:
First of all this isn't the Galaxy Nexus. It isn't developed by the same people (even though it's based off of AOSP) and they don't even use the same kernel.

And if THS says it's the display, then it's the display. Like I said again and again, battery life is a hundred times better that Stock or any other GB ROM. That is all the proof you need. If your phone was really kept awake that long you would know for sure. So get over it. If your so desperate for facts, e-mail the devs. This thread is for development and posting of UNKNOWN bugs, NOT for complaining or seeking the truth.
[Captivate Android Development] Spartoi:
Is there a flashable .zip of just CM9 kernel?
[Captivate Android Development] RaptorOne3:
Then why are you complaining? You're definitely not helping. I never said I had an issue with the battery life. Yours and B-eocks nonsense is far worse than me asking my simple question, which you SHOULD HAVE simply ignored if all you're going to do is argue with me without explaining it. I would have been more satisfied with no answer at all! Sheesh...

You two have turned this into a nonsensical mess. I'm just looking for a logical answer given the evidence...
[Captivate Android Development] Lollipop_Lawlipop:
I haven't seen any battery drain myself, but I've seen the process "Android OS" pretty high up the battery use list.

Whether or not this actually prevents deep sleep by the phone though, I can be certain to say no for my phone.

You can check if your phone spends any time in deep sleep by checking with CPUSpy. My phone spends 85% of total CPU time in deep sleep.
[Captivate Android Development] reynaldoj:
Been using build 15 for about a week now. No CoD/SoD Issues. The only issue is the stock video player, it cant read the AVI format. While Some third party video player apps like MXVideo Player, Mobo support AVI Format but it suddenly crashes during playback.
[Captivate Android Development] wildnux:
while the discussion is going on with the battery issues, i would like to add my experience also hoping it might be helpful.

When i first installed build 15, i did so clearing cache (but i did not clear the dalvik cache from inside the advanced section in recovery. I was experiencing 8-9 hours of battery regardless of light or heavy use. So after a few days i charged my phone to the fullest while it was on and then turned it off and pulled out battery, put it back and then charged full while its off. I repeated the latter multiple times. The went to recovery and wiped out battery stats as well as dalvik cache also. Then when it booted up i let it charge till 100% and after that i have been able to use my phone for a longer time than before. I would not say it is better like what others have been saying/ showing but is definitely an improvement for me. Also this battery is getting old and i have used my phone heavily before so i cannot complain.

I also see android os on the top of my list for battery usage. I thought that android simply shows the battery usage of internal library calls (even calls initiated by using other programs) as android os's usage. This is just my personal thought though. I felt like so when i used some app to download a big file and the battery usage of android os was bigger than that of downloader which i started right after a fresh boot. I am probably wrong though. :D

Here is my battery usage i captured a few days ago.

Sent from my magical wand!
[Captivate Android Development] b-eock:
Not to burst your bubble but your screen on time is terrible...
[Captivate Android Development] AtoZ0to9:
im beginning to wonder why I read more than the OP anymore... just read 5 pages of crap...

personally I could care less what's using the battery, so long as it lasts... and when it gets low, my solution is the charger...
[Captivate Android Development] wildnux:
I know i only got a little more than an hour of screen on time.

I have my brightness set on auto. But there is an issue i have. My auto brightness does not change the brightness instantaneously, it does so mostly after i turn off screen and turn on again. If i try to cover the sensors on daylight it does not lower the brightness unless i turn off the screen and turn back on.

But still this is the best i have ever got since i bought this phone.

I should also note that i have 2 exchange mails, two gmail accounts, and twitter on sync always on. I do use wifi all the time and keep gps on all the time. I do disable bluetooth and gps when my battery is low.

Sent from my magical wand!
[Captivate Android Development] Kaik541:
to everyone who has been participating in this back-and-forth, late-night *****fest. Cut it out.

it's not entertaining, it's not enlightening, and no one is gaining anything from it. we at teamhacksung look at our battery life and notice we're still not having trouble making it through a day even when Andriod OS is showing up as high as 40-50% sometimes, so we ran under the assumption that it was just lumping "everything else" into this category since that would sorta make sense. the alternative to this is that something actually is draining the battery to this and if the fix is actually there in 4.0.4 source once it's released, hey, maybe we can all expect to double our battery lives.

of the two options above, which seems more logical for us to pass on to the user? to tell them "maybe the phone is just being silly" or "maybe google screwed up and it'll all be better in a few days"? by placing blame on anyone or anything, we're implying there's the possibility that it even is broken and since we're not sure what's causing it, we go with the slightly safer option because the other seems remarkable implausable (if I start getting 48 hours out of my captivate with my usage without problems, I will be beyond impressed with google).

as for you... who the hell are you? why do you go on like you're king of this thread and forum? I know every member of teamhacksung, yet your name remains an enigma to me. I've seen you before on the forums, yet I don't feel like you have any access to our internal discussions, so I'm not sure why you're going around white-knighting your way through this thread. we don't need you to rescue us, especially not with your current attitude. you're a test for glitch kernel? congratulations, it shows you listen to exactly ZERO PERCENT of what we tell people using this ROM. if anything, I'm going to mentally place you below the average complainers of this ROM because you just decided to up and ignore our opinions. yet you somehow think that when you spout yours, everyone should take your word as gold and take it for granted that your voice is the most informed amongst the pack.

TL;DR - everyone stop complaining, hopefully the Android OS bug will be something fixable (and we can dream it'll make our battery lives better too), and everyone stop pretending to be the all-knowing-everything I've seen run through this thread more than once. there's a reason most of us don't frequent the forums much anymore.