yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Gromlakh:
1. If it's working fine, then I see no reason to fix it.

2. The post you linked to is scary because it probably should be. Not because there's actually a high likelihood of problems (there isn't), but the only real way to hard brick your cappy is to have something go wrong with the bootloaders. Anything else can be recovered from using either recovery or download mode. Even if the likelihood is only 1%, it's there, so people should be warned. That doesnt' mean you're going to hard brick your phone if you do it; you likely won't as long as you're careful.

Oh, and ignore the whole "CM users STAY AWAY" stuff. Back when Cezar posted that, CM7 could not be booted from GB bootloaders. That's not an issue any longer.
[Captivate Android Development] b-eock:
But it is an issue if you try flashing those BL's while on CM7/MIUI/CM9 or any MTD based ROM, it will not boot afterwards, even with a reflash! you have to go stock then flash those then flash the ROM!
[Captivate Android Development] voldomart13:
Is there a way to unlcok the phone for other sim cards?
[Captivate Android Development] pizz0wn3d:
I'm using glitch, and with data turned off (i have a tasker profile that turns if off after 5min of screen off), I can get almost 2d of standby. Honestly, data is by far the biggest drain of batt life in standby. I get like 1%/hour with it off. I'm also OC'd to 1400mhz. I'm sure stock kernel is about the same.

Herp derp Captivate XDA Premium.
[Captivate Android Development] shaker2k:
Well I had the misfortune of losing my stock back up due to a computer crash. So I need to know how to get back to stock i896 2.3.3 gingerbread. without a backup. If you could post a link on how to get to stock from the setup I have now (cm9 rc15 with i9000 bootloaders) I will be very grateful.

I have an i896 rogers captivate.

Also my wife has an identical captivate that is not rooted. Is there anyway I can back up her phone and use that to get back to stock?

Again thanks so much.
[Captivate Android Development] b-eock:
Anybody know how to add 180 degree rotation to the screen? I am making different mods and want to add this in!

---------- Post added at 10:52 PM ---------- Previous post was at 10:52 PM ----------

No you have to use ODIN or HEIMDALL!

I896 GB One Clicks!
[Captivate Android Development] ptesmoke:
galaxy s unlock in the market. worked for me!
[Captivate Android Development] galakanokis:
TRusselo's stock rogers ROMs that beock linked to work great. Used them a few times and the 2.3.3 GB oneclick with bootloaders was the last thing I flashed before any cyanogen mod ROMs. I have had zero issues with any of the ICS flashes.

Sent from I896 running ICS
[Captivate Android Development] disellusional:
does stock rogers gingerbread have ATT bootloaders?

aka does it start up with the ATT screen or rogers?
[Captivate Android Development] ptesmoke:
as far as i remember it said rogers. but my memory isnt very trustworthy....lol
[Captivate Android Development] radicaleggnog:
Updated to build 15 from 13, and I can no longer connect via USB.

I have reinstalled the drivers from the OP. I have tried re-flashing the rom. I have tried doing a full wipe/flash. Nothing has worked. Any help is appreciated.
[Captivate Android Development] galakanokis:
Definitely no AT&T splash screens. Mine comes up with i896 and SAMSUNG before the cyanogen mod one.

Sent from I896 running ICS
[Captivate Android Development] mbc663:
Until u figure it out, mount in cwm for file transfer
[Captivate Android Development] radicaleggnog:
Unfortunately it's not mounting in CWM either
[Captivate Android Development] mbc663:
Try flashing the zip again?
[Captivate Android Development] radicaleggnog:
Done so several times with no progress
[Captivate Android Development] mbc663:
Revert to 13, try 14, then 15?? ://
[Captivate Android Development] thangphysk48:
Does anyone got problem with Gallery. When I mount/unmount USB storage, my Gallery missing some picture that I've newly capture.

And, when I restore from backup, it only display images/videos from time I made that backup.
[Captivate Android Development] zuN!:
I disabled everything but EQ and it still stutters when I turn off my screen. Two of us can at least reproduce this problem so I'm not sure if we're able to say it's a bug since you don't have this issue.

Same, but too bad there's no EQ.
[Captivate Android Development] drawde40599:
Calendar

Could one of the dev please tell me how get calendar sync working?? I came from 100% stock 2.1 then to cm7 now this cm9 never flashed different bootloader, everything else works just fine. Yes I installed the .zip/ fix from first page, but it don't really say when to flash so what I did was flash rom flash gapps flash gapps fix, didn't do anything still fails to sync calendar I've also tried leaving unchecked and flashing.....I've tried uninstall both calendar .apks, and flashing, I've tried gapps from my nexus s (Kali cm9) nothing is working, full wipe only thing I can think of that I have not tried but since there is known issue don't no if that's even going to help . Thanks but if a actual dev of this version cm9 could reply, read to many different opinions no real .......
[Captivate Android Development] AtoZ0to9:
Never had a charge or sleep death in the yr+ of ROMs

Only bug I've ever had is the dialer freezing and not working until reboot if T9 is enabled... so I leave it disabled...

I've tried all the other ROMs and get mad when I do cause I just have to set all my stuff back up when I come back to this one...

Excellent work THS...
[Captivate Android Development] jerkysh:
i would love if the features from the ICSSGS RC4 would be available on CM9. I mean Facebook sync, Camera effects, Picture editing in Gallery ...
[Captivate Android Development] alphahere:
ICSSGS also had death charge problem that is worse than CM9. :rolleyes:

---------- Post added at 07:58 AM ---------- Previous post was at 07:31 AM ----------

Previously filled out a charge death report.

Captivate Model Build 1010 with KF1 bootloader and now with KK4 bootloader. My cappy has had charge death without fail on every build since build 10 and every kernel expect nushor's kernel. Also had charge death with icssgs rom. Yes I do a full wipe before install and using the rom without any apps installed. This is my experimental phone to play with.

I have used all the CM9 builds starting with the first one.

I reviewed all my posts and noticed that I started reporting charge death problems starting at build 10. Well I went back and installed build 9.

Build 9 - no charge death episodes after 24 hours on charger. Wow!

Now for the interesting part nushor's kernel was compiled about the same time as the stock build 9 kernel. Battery life sucks with nushor's kernel. Another interesting point is nstools will not work with stock build 9 kernel or nushor's kernel. When I click on the voltage control tab nstools crashes hard.

I did try to use the stock build nine kernel with build 15 but it would not boot up. Whatever.

My two cents but I think it has nothing to do with the bootloader. I have read this thread and charge death can occur with any bootloader. Probably has to do with the hardware and kernel interaction. I had this problem with some of the early cm7 builds but it was resolved with later cm7 builds. One last note could folks please report the captivate build number which is under the battery when reporting charge deaths.

Thanks
[Captivate Android Development] RaptorOne3:
So go flash their build man...

BTW, image editing works just fine in Gallery.
[Captivate Android Development] malbolgias:
Im on captivate gb boot loaders and have has charge deaths with every build from 10 up. All the tests kernels gave me the same problem. Never before on cm 7 had I had this problem. Just on some early gb releases.
[Captivate Android Development] alphahere:
AT&T Service Bulletin

http://www.attdroids.com/forum/sams...letin-random-shutdown-issues-t-captivate.html

I am one of the unlucky ones. Yes my cappy has been out of warranty :rolleyes:

Yes my cappy fits the description and imei number for this problem. Lucky me :)

Anyway with CM7 and anything before CM9 build9, I did not have this problem. Only with cm9 build 10 thru 15.

Apparently samsung fixed this problem in software with later rom releases. See this post for details. Don't know if the fix was in the kernel or the rom.

http://xdaforums.com/showpost.php?p=20041358&postcount=1288
[Captivate Android Development] GRACO:
No charge deaths here, since using glitch ...
[Captivate Android Development] chasesavestheday:
Does wifi sleep work on any of the other builds? Killing my battery when the screen is off.
[Captivate Android Development] alphahere:
With glitch 14 my cappy develops charge death about 10 minutes after connecting to the charger. I have to pull the battery to boot. Also with glitch my cappy has sleep death without being connected to the charger. Never have any sleep death without being connected to the charger on CM9 stock kernel.

So at least for me glitch is not the answer.
[Captivate Android Development] theyurtingyeti:
INPUT METHOD Doesn't come up

Just flashed build 15 and it's working great so far. One small bug though:

When in a typing screen (SMS, for example) I could always hold down in the typing area and the "input method" prompt would come up. This way I could easily switch b/n swype, android, whatever.

This worked in build 14, but does not seem to in build 15. I was able to go the back routes and implement the keyboard of my choice, but I found it odd that I could no longer hold down and get the prompt.

Again, small bug but thought I'd bring it up.
[Captivate Android Development] bentonhall:
I think this is how ICS is. I havent been able to do that in any of the builds but if you have more than one keyboard installed and are on a input field, you can change the keyboard by pulling down the notification bar and choosing select input method.
[Captivate Android Development] theyurtingyeti:
Huh... I could have sworn I could do that in build 14... perhaps THAT was the bug :)

I at least know why i always had that little keyboard in my notification section whenever I was typing! I thought it was swype related so I didn't post about it.

Thanks!
[Captivate Android Development] galakanokis:
I can still select input method from the pulldown while running build 15. Are your new keyboards selected settings?

Sent from I896 running ICS
[Captivate Android Development] theyurtingyeti:
Oh, I can do it from the pulldown... I thought I could just hold down on the texting area and get the "input method" prompt. I could have swore I could in build 14.

But I see they've replaced that with the keyboard in the notifications so I'm all good now :)
[Captivate Android Development] nkrick:
You linked to a post that I made. I don't know details, just that from the information available, there was a software fix in November 2010 that took care of the issue on at least some phones. If you read the forums about the sleep death issue, you will see that some people still have the issue running stock KB1, etc, so the software fix did not fix every phone. I don't think anyone knows the details besides Samsung and possibly AT&T. But, if you do have the issue, I do recommend reading the two threads about the issue.

What I know about sleep death comes directly from the threads about the issue and based upon that information I have made my own educated guesses about the cause. I am not an authoritative source on the problem though.
[Captivate Android Development] jerkysh:
if i wanted, i would..

but i love CM, and i'm not gonna flash anything else!
[Captivate Android Development] jayjr1105:
Do you guys have a recommended way to do a clean install after going back to stock? Which bootloaders to use?

My method involves going back to stock 2.2 Using Icezar1's method without bootloaders, Master clear with odin one click, download mode, flash current CWM kernel with Odin, reboot into recovery, add ROM & google apps to SD, Clear cache/wipe, install ROM.

I'm currently on GB bootloaders, Are there ICS bootloaders or more recent ones that I should flash?
[Captivate Android Development] AtoZ0to9:
Everyone seems to have their own way of doing things... I personally try to keep it minimized... Here are my steps, but feel free to do what you want...

I already have i897 GB bootloaders, so I don't flash those

For stock:

I ODIN flash I897UCKI2 Android 2.3.5 Gingerbread With no-BL With CWM Injected Kernel from Boog from the stock ROMs sticky

Wipe SD from ROM

Wipe Data / Factory Reset

Wipe Cache

Wipe /system

Flash ROM, gapps, gappsfixer, reboot

Wipe SD from rom

The SD wiping is probably not necessary, and I only flash back to stock every 2 or 3 builds... usually I'll just flash the new build doing nothing else...

And no, no ICS bootloaders, only I9000 GB, i897 GB, and i897 eclair, I9000 GB being deemed unsupported recently...
[Captivate Android Development] nkrick:
You got an extra thanks (hit the wrong button).

If you do not have the KK4 bootloaders, I'd odin to a KK4 stock ROM (if you can find a package) to get the KK4 bootloaders, then flash a CWM injected kernel. If you can't find KK4, what I would do (what I did late last week) is the following:

1. flash a stock KB1 or KB2 odin package

2. use kies mini to install KK4 (to get the latest KK4 bootloaders)

3. use odin to flash boog's KJ3 Kernel with CWM

4. boot directly to CWM recovery and flash CM9 Alpha (follow instructions from OP)

If you have KK4 bootloaders (or other i897 GB bootloaders and don't want to bother getting to KK4), then I'd follow B-Naughty's instructions in the post above.

Aside from getting the GB bootloaders, I'd never flash a stock odin package unless you are in a bricked state and that is the only way out. Once you have GB bootloaders (I recommend KK4 since those are the official ones), you can use "factory reset" in CWM which should have the same affect as performing a flash to stock and flash back to CM9. Unless your partitioning is messed up, the extra steps to flash to stock and back to CM9 probably is not going to gain you anything.

You can find the Stock Rom OneClick Odin package thread here: http://xdaforums.com/showthread.php?t=1300843
[Captivate Android Development] shaker2k:
Ok I've been doing a little bit of investigating into this sleep death, and charge death issues that people have been experiencing.

I haven't had the problem but, Pawtips post:

"So it seems like everyone who started experiencing charge death on BUILD 15 are running I9000 bootloaders. BUILD 15 includes kernel changes which fixes stuff for Captivate users (with Captivate bootloaders), so I hereby declare that I9000 bootloaders are unsupported and unrecommended". got me wondering if I should flash back to stock with cappy boot loaders.

I am using the i9000 bootloaders and have had no problem what so ever. But if the above is true... Well it got me nervous that the problems are laying in wait to attack me.

So using google search. (I know amazing right using the search function) I found this

http://www.attdroids.com/forum/sams...letin-random-shutdown-issues-t-captivate.html

So I have to respectively disagree with Pawtips statement that the i9000 bootloaders are the problem. It is more likely due to the fact that your cappy was manufactured on or before November 2010

I'm not trying to cause a ruckus here only trying to help make this ROM great and contribute. Maybe not with my mad hacking skills(of which I have NONE)! but with my OCD and paranoia that I don't have everything perfect.

Please let me know if I am helping or if I am being a paranoid n00B.

Edit:

Seems like model numbers lower than: IMEIs manufactured before November 6, 2010: 352982040855394 or lower - 5393, 5392, etc. are the culprits. You can find this number under your battery.
[Captivate Android Development] kangi26:
Well, I can throw a monkey wrench in your theory. I have a 1008(Aug 2010). The only time I have ever had a SOD, was on GB rom's. I never had it on Eclair/Froyo/Miui or ICS. Although I did have a issue waking from sleep when I tried Glitch kernel on THS build 14

Sent from a autonomous device
[Captivate Android Development] mbc663:
I could duplicate this post. Same exact thing with me. SAME.
[Captivate Android Development] Gromlakh:
As I noted in a (semi)lengthy post a few pages back, there's way too much redundancy in that approach. If you're wanting a "clean" install of CM/ICS, there are exactly two steps involved:

1. Return to anything stock (KK4, KH3, literally anything, it doesn't matter in the slightest) with a CWM-injected kernel.

2. Flash the CM/ICS installer from CWM.

That's it. CM uses a completely different partition structure than Samsung ROMS do. When the installer detects that you're currently on the Samsung partition structure, it destroys your partition table a writes a new one in the CM format. It then writes everything you need from there.

That rewriting/recreating of the partition table will pretty much complete wipe everything on your phone but the SD card and the bootloaders. So, wiping {data/dalvik/cache} while on stock but before flashing CM/ICS is a waste of time because those will all be completely deleted by the installer. Master Clearing is basically factory reset (not needed) + wiping your SD card (NEVER needed or advised). It also does not matter at all what "stock" package you use, because everything will be deleted anyway.

So, for best results, Odin/Heimdall a stock package that includes a CWM-injected kernel rather than the stock kernel to save time(check the sticky at the top of the forum, there are tons of them). After doing that, boot straight into recovery and flash the ROM/gapps. You're done, and you've accomplished exactly the same thing you accomplished with the method you listed.

Except you cut out like 6 steps and you don't have to put everything back on your SD card (which should never be wiped unless you're selling your phone).
[Captivate Android Development] anjosautomotive:
I've been on THICS since build 3.

I've only had sleep death twice, and it was with an earlier build, maybe build 5

Went from build 9 to 15. After soft brick (bad flash maybe) went back to stock and now on build 15 for two days. no sleep death.

I beleive I'm on I9000 bootloaders.
[Captivate Android Development] shaker2k:
Well if we can get everyone who is experiencing the death issues and running either Captivate or i9000 bootloaders to check their model number and post whether they are having the death problem, we can completely eliminate the manufacture date of their captivate as an issue with CM9 and the death issues.
[Captivate Android Development] Clark Joseph Kent:
I always use quick pic app (free)..for all my devices and roms...finds all my pics even those i don't wanna see...lol... far better than default gallery (no offense)....and has all crop/resize functions.... IMO
[Captivate Android Development] TheSoaresan:
Mines 1102 and I'm on i9000 boot loaders...and I have never seen a charge death or sleep death etc ever
[Captivate Android Development] Nick0703:
It doesn't say Rogers. It says "I896 SAMSUNG"
[Captivate Android Development] jayjr1105:
Thanks for clearing that up. I believe I have i897 GB bootloaders, so I just need to be flashing to a CWM-Injected Kernel and simply flashing the ROM.... got it. Excuse my ignorance, I have been out of touch with the forums lately but what is Heimdall?
[Captivate Android Development] mcala:
If I run a full scan using Dr. Web the phone reboots around the 4min. mark. It can be replicated, it has done it 3 times so far. A quick app scan works fine. I will try to email the developer of Dr. Web but I'm sure they will just tell me "too bad, an alpha build is not supported"!

Please keep your negative comments about malware scanners to yourselves!
[Captivate Android Development] Gromlakh:
np

Link in sig...
[Captivate Android Development] anjosautomotive:
Had it once while charging with wall charger and once plugged into laptop.

Pulled batery and rebooted both times.

I don't know if that helps but thought I would add that.
[Captivate Android Development] ralphreyes:
I think those that have had charge deaths need to post more specific information regarding their boot loaders and their setup. Probably indicate if you're using:

i9000 vs i897.

GB vs Froyo vs Eclair.

Modified (those that allow you to change boot splash) vs stock.

This may help further in finding the charge death problem. Just my 2 cents.

I've had no charge deaths on any ICS ROM. I can't remember if I've ever had a charge death for that matter. My details:

1010 i897 gb kk4 stock boot loaders.

Sent from my SGH-I897
[Captivate Android Development] alphahere:
Wow your specs are identical to mine! I have charge death on every build since build 10. I went to stock KK4 before installing cm9. Strange?

Sent from my SCH-I500
[Captivate Android Development] nkrick:
If you read all the posts in the thread linked above and the two threads in XDA about the same issue, you would see that the IMEI range is only a list of devices that are "potentially" affected. Not all early IMEI's have the hardware problem that leads to sleep death, but they potentially have a bad hardware component that can lead to sleep death. Several people have sent their affected Captivates to Samsung to get them fixed and in every case a particular component (I forget what the cryptic name is) has been replaced and the sleep deaths have stopped.

The reason many people are confused by this "internal notice" is that it mentions a November 6, 2010 software fix in i987UCJH7. This only fixes a software glitch that caused sleep death. All evidence (including reports by people who have actually talked to Samsung and send their phones in to be fixed) points to the fact that there is also a hardware problem that COULD exist on any phone manufactured before Nov 6th, 2010 that can be fixed by replacing a bad component. Even the memo was dated on Dec 20th, 2010, after UCJF6 was available. If this was solely a software problem, the resolution would have been to update the firmware on the phone, not to exchange the phone.

I have also read that there could be phones manufactured post Nov 6th, 2010 that can have the issue also due to a bad hardware component, though it appears to be less likely.

---------- Post added at 03:01 PM ---------- Previous post was at 02:57 PM ----------

A lot of evidence suggests that charge death is caused by an overheating battery, so unless you have the exact same battery and charging circuitry (not just same batch, the same actual battery, charger, and charging components in the phone), the fact that the specs are identical don't necessarily mean much.
[Captivate Android Development] mbc663:
Ambient temperature and surface is also a big factor.
[Captivate Android Development] airtower:
Did we lose the backlight tweaks when cmsettings was merged into build 15, or am I just having one of those days and can't find it?
[Captivate Android Development] Joecascio2000:
Its in advanced now.
[Captivate Android Development] airtower:
Sorry, I should have said screen brightness instead of backlight (soft buttons)
[Captivate Android Development] Joecascio2000:
Not sure if this is what you mean but Display and click automatic backlight it brings up a bunch of settings.
[Captivate Android Development] airtower:
derp...there is it. thanks