yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] jswclw:
As I said in my earlier post, I also am not convinced that the battery overheating is the cause of charge-death. I have several reasons -

I have never found the phone to be hot while charging.

The death is not a safe shutdown, but is stuck in a state where battery continues to be consumed. Seen this is the battery graphs after a death.

Only started happening to me with build 13. That's after 18 months!

Debug mode makes a difference (off for me now)

Wi-Fi always on seems to make a difference - no problem after 4 cycles now.
[Captivate Android Development] J0ESK0:
For all the people talking about new batteries and such.. just wanted to point out how amazing this ROM is on a stock battery, running stock kernel, UGKG3 Modem, Auto-Brightness.. this is my battery life.. over 3 hours of screen on time:
[Captivate Android Development] tj2469:
Just rebuilt clean, now get charge of death

I have been using this rom since build 9. When I first came over, I did not do a clean install, and though I would see if I could get by, which I did. No issues. Then, around build 13 upgrade,I had some issues with using gapps 7.1, but reverted to v6, and everything was fine. No issues. Keep in mind that this was a dirty install, without going all the way back to stock, or doing a factory reset.

Yesterday, I decide to do a complete install, revert to stock, load stock GB rom, load I897UCKI2_noBL_BoogsKernel, then build 15, gapps 7.1, gapps fixed, sufix.

Now I get charge of death. Never had any issue before the clean build.

I have read many many posts now on this, and I do not seem to see any clear answer. Should I try one of the test kernels, or rebuild differently? I am positive this COD has nothing to do with battery, or cables, because nothing has changed here in my charge process.

Please advise next best steps. I love this ROM, but would like to depend on my phone staying awake at night.
[Captivate Android Development] alphahere:
Very interesting post.

Never had charge of death until build 10 and then I did exactly like you did and the COD became worse. Only thing that prevents charge of death (COD) is connected to the computer with usb debugging turned on.

Do you remember how you installed cm9 initially or have you forgot?

Thanks
[Captivate Android Development] WickedNite:
Where can I find Modems that can be used on CM9?

Sent from my Captivate
[Captivate Android Development] Abaddon:
stickies in this forum

Sent from my Cappy
[Captivate Android Development] kangi26:
Use these:

http://soggycashew.weebly.com/cm7miui--ics-modems.html
[Captivate Android Development] ptesmoke:
for those of you with charge death...id be curious to see if you still have charge death on the rogers gb bootloaders. my setup is flash rogers stock gb with bootloaders, factory reset, flash a cwm kernel, enter in recovery,wipe everything,flash ths build 15 and gapps.

i have yet to see any charge or sleep death. worth a shot to see if it changes anything...
[Captivate Android Development] shaker2k:
I'm on i9000 bootloaders.

Rogers captivate

No problems on either cm9 kernel or glitch.
[Captivate Android Development] GGXtreme:
I'm on AT&T GB bootloaders. Running for 3 days so far, no charge death or sleep death with either the included kernel or Glitch kernel. Currently running the included kernel.
[Captivate Android Development] Silencer96:
Ok, I'm not too sure if this'll actually help anybody, but it wouldn't hurt.

So I've been using this ROM for about 2 weeks now, and not ONCE did I get a charge death. I'm also overclocked to 1.5Ghz using NSTools if that matters.

Here's what I did:

1. Odin One Click to Froyo 2.2

2. Use the CWM update.zip method to install CWM recovery

3. Install MIUI (the current version out in the XDA forums [by Proto]- not the ICS edition though).

4. Flash CM9 over MIUI after clearing cache (dalvik, cache, and data, etc.). I also wiped my battery stats if that matters.

5. Flashed IcyGlitch V14-b2.

6. Downloaded NStools. Set the min to 200mhz, max to 1.5. I also set the governor to the default GlitchOndemand.

Done. I haven't gotten any charge deaths whatsoever.

I hope this helps someone out there.
[Captivate Android Development] Nick0703:
Yeah I have Rogers GB Bootloader and never had charge death or reboots during phone call.
[Captivate Android Development] GGXtreme:
Are others here finding that "Android OS" is the highest battery user according to the Settings menu, with a "Keep awake" time almost as long as the time unplugged? I've noticed that while this ROM gives me excellent battery life under moderate to heavy usage (5 hours of screen time with over 3 hours of wifi usage, mostly time spent setting up the ROM, installing apps and web browsing), my standby results are pretty poor: around 10% per hour. None of my installed apps seem to be running or using CPU or battery, and CPU spy shows that the phone is properly going into Deep Sleep (no wakelock). I'm using the included kernel, although I will test my results with Glitch as well.

This is my first custom ROM on this particular Captivate, but my previous Captivates running custom GB ROM's (even AOSP ROM's like MIUI) had me getting 1-2 full days of use with better standby results and I don't want to blame the ROM for some setting/app/bad flash.
[Captivate Android Development] RockRatt:
I know I have said this before but if you keep uP with this thread it seems those that have sleep or charger death are on kk4 boot loaders.

I am on the first leaked ATT GB bootloaders 1007 build and HAVE NEVER had any issues with sleep or charge death or ANY other issue ever. My phone has been able to go up to 1.6Ghz with no freezes or issues on cm7. I do not use setcpu but use voltage control app. I have not used or tried any scripts. So on cm9 alpha I am completely stock kernel with no mods. Read back the last 20 pages or so and most if not all seem to be using kk4 boot loaders. Just my perception since I have been using this from the first build and all the way through since I came from cm7

Sent from My KickAss CM7 Captivate
[Captivate Android Development] b-eock:
No such things as KK4 bootloaders. They haven't been updated since KF1
[Captivate Android Development] Gromlakh:
Not trying to rain on the parade, but it's incorrect to say that most people having charge deaths are on KK4 bootloaders. In fact, it's not correct to say that they're on any particular bootloaders. I've been following this thread for about 300 pages, and people have been complaining about charge/sleep deaths for a long time. First someone mentions they're on Eclair/Froyo bootloaders, and people "diagnose" that as being the problem. Then 10 people pipe up that they're on the Eclair/Froyo bootloaders and don't have the problem, followed by several pages of people ignoring that and saying the problem must be Eclair/Froyo bootloaders.

This has repeated itself over and over again with people variously targetting the Eclair/Froyo bootloaders, pre-KK4 i897 GB bootloaders, KK4 GB bootloaders, and i9000 GB bootloaders. Each of these "diagnoses" are then followed by pages of people mentioning how they have the alleged "problem" bootloaders and don't have charge/sleep death issues, and several more pages of their statements being ignored.

I doubt very seriously the bootloaders have anything to do with the charge/sleep deaths. The people who have been reporting the issue have not reported being on all the same bootloaders. The problem is something else.
[Captivate Android Development] nkrick:
I have the i897 bootloaders that came with the Kk4 update through kies mini. When I decided to go to GB bootloaders I decided to allow kies perform the update (partially due to multi-upload going offline). I am using build 15 with the stock kernel and only QuickOffice restored from TiBU. My Captivate is a 1007 and I have never had a sleep death or charge death. My wife with a 100% stock 1105 Captivate with KK4 installed had a charge death Friday night / Saturday morning (for the first time ever).
[Captivate Android Development] simple man:
No problems here, I've ran several of these builds, early on I would occasionally get the reboot during phone calls but that's it. I'm on 1008 build, last stock flash was kk4 one click, and that was SEVERAL CWM zip flashes ago.

I've not had any SOD, or COD, I use a cheap Wal-Mart charging Cable at least 50% of the time, the other times I use the stock charger. While I sleep I charge my phone and have an app called Relax and Sleep running to drown out noise, I'm a day sleeper. It's very puzzling what could be causing the SOD, COD issues.
[Captivate Android Development] RockRatt:
Like I was saying these are from the last 10-20 pages with people with the issues that actually listed their boot loaders they are on.
[Captivate Android Development] Gromlakh:
Or we could go back another 10-20 pages with people listing being on the i9000 GB bootloaders, leading to the announcement that the i9000 GB bootloaders were officially being listed as "unsupported" due to their supposed involvement in the sleep/charge death issue.

Or another 10-20 pages with people blaming the Eclair/Froyo bootloaders.

Or we could just move on, find the real problem, and stop blaming the bootloaders.
[Captivate Android Development] shaker2k:
Or another 10-20 pages with people blaming the Eclair/Froyo bootloaders.

Or we could just move on, find the real problem, and stop blaming the bootloaders.[/QUOTE]

Great point. And one thing we have to remember. Flashing bootloaders

Is one of three more tricky procedures, and from what I've read one of the 2 ways to hard brick your phone if done wrong.
[Captivate Android Development] DaNaRkI:
Can the OP/Dev(s) designate/provide a set of bootloaders that everyone must use for the time being? It will eliminate a lot of back seat "problem solving". Anyone who is uncomfortable changing bootloaders can sit out until this issue is fixed or at least isolated.

Or as a group lets all pick a set to run, go a few days post results and try the next set. We have 3 sets, so if everyone agrees to something we can get this sorted out in about a week (since we probably only need to go 2~3 days a set).

Also, this ROM is just now at the alpha stage. Can we stop with the foreign kernel BS already. Anything you people post is useless, this is not an RC build it's not even beta... There is no reason to be tweaking something that is not a "finished" ROM, your just confusing yourselves and others. If you don't like how a pre-RC pre-beta ROM runs go use something else!

leaked from my

semi

- FUSED SGS I897 contaminating you via XDA app.
[Captivate Android Development] singlebeam:
I have followed this thread from the start and have read every single post. I agree with your observations and I'm glad you pointed it out - I've wanted to say something similar for a few weeks though I never feel like my views are credible like a Developer's would be. I mostly just sit back and listen to all 472 sides of these conversations :D

Also, on a side note, I wanted to ask where the term "charge of death" came from and why everyone is using it? I noticed this about 50 pages ago and everyone seems to have followed suit. What does that mean? Charge OF Death? That doesn't make sense. If one wanted to coin a term it would more appropriately be Death of Charge.
[Captivate Android Development] wash23:
Confused here; once the phone boots successfully, are the bootloaders any longer relevant??
[Captivate Android Development] brianray14:
This term is being carried over from the DOS and early windows days when the BSOD (blue screen of death) reared it's ugly head
[Captivate Android Development] shane87:
I would have to agree. I am not an expert in bootloaders, but from what I have read on adamoutler's threads about bootloader development, the bootloaders should have no effect on charging after the phone is booted. The only time the bootloaders deal with charging is when the phone is powered down. The bootloader should simply activate some memory, find sbl.bin (in the case of the primary bootloader) or zImage (in the case of the secondary bootloader), load the required file into memory, pass control to the file they loaded, then die. So, it seems to me, that unless the problem is with charging the phone when it is off, the bootloaders should not have an effect.

This is just my understanding of the subject, and I may be way off on this one. However, I know that the kernel has the code built in to handle charging, so having the bootloader involved seems redundant and unnecessary.

If I am wrong here, feel free to let the scathing comments begin, lol.
[Captivate Android Development] singlebeam:
I understand and was around for all of that nonsense....the term "Charge of Death" just sounds silly. As far as I can tell, someone used it quite a few posts back and now everyone seems to think it's appropriate. None of this is important - I just cringe when I see it. Not a very good correlation between the two.
[Captivate Android Development] raz123:
Is "reboot download" working for anyone else? Definitely broken here; performs a regular reboot.

"reboot recovery" works, though.

*Either typed in the terminal or through adb :( -- b15.
[Captivate Android Development] pizz0wn3d:
Confirmed via terminal. Just performs a regular reboot. Though I'm gonna post this in the Glitch forum too because I'm on that kernel.

Herp derp Captivate XDA Premium.
[Captivate Android Development] raz123:
Thanks for confirming.. leaves me unable to get in Download mode; key-combo on boot stopped working here.

EDIT: Nvm this msg, all good now :) [still unable to get in Download mode using software-only means]
[Captivate Android Development] b-eock:
Here, no cycles it is the first time off the charger
[Captivate Android Development] Smasher816:
reboot download has never worked on asop. Not cm7, not cm9.

I believe they said its impossible to control that low level stuff without an params.lfs mod or something.
[Captivate Android Development] Gromlakh:
Your understanding is spot on.
[Captivate Android Development] singlebeam:
Thank you for this insight. I love learning anything and everything I can about android. Which AdamOutler threads are you referring to? I would love to read up on those.
[Captivate Android Development] shane87:
I am referring to these threads by AdamOutler:

[UnBrickable Mod] Running Nexus S Bootloaders and hopefully porting AOSP the easy way

The Captivate Development Platform mod AKA UnBrickable Mod

[HOW-TO]UnBrick the UnBrickable Captivate

[RELEASE] One-Click UnBrick updated 10july11

Especially the first three. The first link has an awesome explanation of the bootloader process by rebelos in the second post. The third one also has some good bootloader info from rebelos in the second post. And they all have tons of info in general!

[EDIT]In the op of the second link, there are a bunch of links to outside sources of info on the Captivate/Galaxy S/Hummingbird SoC.[/EDIT]
[Captivate Android Development] GGXtreme:
Are you using data/location services/wifi/auto sync at all? I can't squeeze 12 hours out of this ROM with only 2 hours of screen time, and I leave wifi off when I'm not using it, no background apps like Facebook, etc. :(
[Captivate Android Development] b-eock:
Wifi and data.
[Captivate Android Development] Joecascio2000:
This is the best battery life I've got since being on ICS. About the 5th total charge cycle (for the battery) but the 1st since updating to Build 15. (I was waiting for build 16 but flashing is addictive.:D)

* 1800 mAh battery

* Wifi Always On

* 2 Email Accounts

* And virtually everything syncing (FB, Twitter, Weather, and everything Google)

* With horrible signal (which imo, has the biggest impact on battery, I've tried every modem, my house is just the biggest dead spot in the world.)
[Captivate Android Development] motiv8d365:
Change boot animation?

I try to change boot animation and every time it just shows the flashing silver android text with black background...so no boot loop but Im wondering if you can change it
[Captivate Android Development] scrypt:
Is anyone getting a force close on fruit ninja? Everything is perfect but this is slightly annoying :( Is there a list of supported apps that I can check?
[Captivate Android Development] wickedninjalo:
Fruit ninja works for me, and read the OP there's a link for exactly what you ask for.
[Captivate Android Development] DarkisFever:
Agreed, I am still on build 14 and am getting superb battery life! I am getting around 2.5-3 days on a single charge. I posted a pic a few pages back:

- Stock Battery

- Wifi Always On

- Gmail Sync

- Facebook, Weather, etc Syncing as well.

- Perfect signal as I live right in a major city.

I am highly impressed by the quality of this ROM and cannot wait to jump to 16 when it arrives.
[Captivate Android Development] alphahere:
Charge of Death Update

I had my doubts about the battery getting hot during charging but some nice person here referred me to a battery app that could monitor battery temp. Below is data collected while connected to a samsung 700 mA travel charger and using stock battery.

Captivate Battery Temps ranged from 30 to 38 C while charging and once charged ranged from 29 to 32 C.

Galaxy S2 never went above 29 C when charging and dropped to 27 C after charged.

Nexus S after charged was a steady 22 C, don't have figures while charging.

I guess long term battery life will be shorter the hotter the lithium battery gets during charging.

I then tried a lower mA charger. I have a plantronics 180 mA charger used for bluetooth headset. Confirmed that the charge of death occurred with the standard charger and then before going to bed connected the captivate to the plantronics 180 mA charger. With the 180 mA charger I had NO charge of deaths occur and it was charging the phone - battery temp while charged was 27 C. Temp was definitely lower than the 700 mA charger.

So at least on my captivate the battery is getting too hot with stock samsung charger. I would assume that the code to manage charging is in the kernel. I would like to note that I have never had charge of death until build 10 and can duplicate charge of death consistently by connecting to the stock samsung charger or any other standard phone charger. I guess I should install build nine and check the temps again.

I will continue to use the 180 mA charger to see if I have another COD (charge of death). I don't like the term COD because it also means cash on delivery.

Phone specs:

Phone build 1010

CM9 build 15 with stock kernel

GB Bootloader

Hope this helps.
[Captivate Android Development] pawitp:
The bootloader plays a role in the initialization of certain hardware and the kernel expects them to be initialized in a certain way. The difference between bootloaders is hard to figure out due to its closed-source nature, but in the past, there was a problem where users with GB bootloaders on the I9000 would not be able to use the external sd card until the kernel was patched to work with GB bootloaders.
[Captivate Android Development] ThreeofNine:
Originally Posted by pawitp

How to Report Charge or Sleep Death on BUILD 15

- Did you have the problem on BUILD 14?

- Did you have the problem on BUILD 14 + test2/test3 kernel?

- Are you running Captivate GB bootloader? (If not, what bootloader are you running?)

Also report if build 15 fixes charge death for you (and mention your bootloader)

Note: It's not trivial to check what bootloader you are running, but it's the version of the latest ROM you've flashed via Odin which contained boot.bin and Sbl.bin.

You may want to add another question to this list: Did you wipe data/factory reset + wipe cache partition when installing this build over the last build?

While researching this topic outside XDA forums I found this from iFixit.com http://www.ifixit.com/Wiki/Samsung_Captivate_Troubleshooting Their logic is that "If you've ever rooted or have done any other kinds of modifications, they sometimes become corrupted awhile after they have been installed." Their solution is to wipe the data cache if the battery is not defective. I haven't had the problem of not being able to re-awake my phone after charging or letting it sit for awhile.

One other item I saw was that changing the Display Sleep setting to 2 minutes of inactivity. I've always had my setting at 2 minutes anyway, so I'll change it to other settings to see if that really does create any problems.

Hope this helps some!
[Captivate Android Development] jammin1911:
Hi there,

I was just wondering if there is some method of donating a little bit of money to the developers? I'm not a regular user here so I apologize if the answer is out in the open somewhere.

Thanks for all of your hard work!
[Captivate Android Development] Raul77:
I am having an issue not sure if its something on my end or a bug, when i play MUSIC (Mp3) through my car stereo which has Bluetooth receiver the music is VERY choppy, gets cut for half a second every 3-4 seconds, i used CM9 and PowerAmp both same results. I try streaming internet radio over Bluetooth and not still gets cut but FAR FAR less, like half a second every 10-15 min ! which is not a problem at all. anyone else experienced this at all?
[Captivate Android Development] joedon3:
If you go to the main DEV site: http://www.cyanogenmod.com/ At the bottom, there is paypal embeded, you can make donations there.

And Atinm requests that you become an organ donor if you aren't already.
[Captivate Android Development] nakedninja42:
I haven't had any issue streaming bluetooth to my car stereo. I used both the CM Music (http://www.seeingpixels.org/2012/01/cyanogenmod-9-music_16.html?m=1) and Google Music. I haven't used PowerAMP yet.
[Captivate Android Development] Raul77:
Where do you store you music? external or internal SD?
[Captivate Android Development] nakedninja42:
External SD. 32 gb class 4 with 28.5 gb of music.
[Captivate Android Development] tungers:
Backlight notification and Camera storage

Is backlight notification currently supported, or will it be supported in future builds of CM9? I don't think any of the supported kernels for CM9 currently support BLN, but please correct me if im wrong. Right now I am settling with the app 'noled' to provide me with screen notifications, but this seems less optimal than having the backlight on the softkeys light up with notifications.

Also, is there any way to change the default storage location of the camera to an external sd card? Right now it seems to default to the internal sd on my captivate and the only way to change the storage location is with another camera app.

Thanks in advance for any insights!
[Captivate Android Development] nkrick:
Only some people are calling if "charge of death." The rest of us have called it simply "charge death" since the beginning.
[Captivate Android Development] airtower:
BLN is pretty much dead these days. Replaced by LED notifications. Effect is the same, but the implementation is different. Yes, CM9 supports it. Check under settings -> Display -> Pulse notification light. Individual apps may need to have LED notifications enabled as well.
[Captivate Android Development] mbc663:
Only thing is it doesn't blink. Just stays lit.
[Captivate Android Development] wash23:
Requires "DOT" (Depth Of Thought).:D
[Captivate Android Development] Raul77:
thats the most missed feature of BLN for me :(
[Captivate Android Development] nyciz:
Am I missing something, when I go to "settings -> Display -> Pulse notification light" its just a checkbox.

If i miss a call or get a txt msg while the screen is off, the softbuttons light up. Is there a way to configure more apps to lite me btns?

just curious.