yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Ajfink:
I would wipe cache / dalvik, it's nbd anyway and can avoid problems. I haven't installed RC2 btw, I'm sticking on the nightlies.
[Captivate Android Development] CheesyNutz:
i flash it like any other nightly
[Captivate Android Development] andrewdroid:
I've had some good gps results on RC2 but I think there's nothing short of getting a new phone that can truly fix that.
[Captivate Android Development] sansaman:
http://xdaforums.com/showthread.php?t=1541942
[Captivate Android Development] Primus76:
there is no revert but to wipe though. My phone got really laggy after running it. Also lost all gapps after updating a nightly after running it. Not sure if related.

But it did cause all apps to lag.

Happier without the script and am just managing apps as needed. Netflix moved to SD freed up a ton of room.
[Captivate Android Development] Primus76:
Did a cache wipe run just in case. Running very smooth for me.
[Captivate Android Development] RootTheMachine:
Keep in mind this is the old version of the script. The new version works much better and can be found at http://xdaforums.com/showthread.php?t=1665742 and the best version imo is the datafix_test found later in the thread
[Captivate Android Development] ap1618:
how about the datafix app in the market? thats the best one i suppose
[Captivate Android Development] account4me2:
Alternatively if you don't want to use a datafix, you could just open Terminal Emulator and type:

su
cd datadata
du -sm * | sort -nr

and it will list all the directories in datadata by size (http://www.howtogeek.com/wiki/List_Files_and_Directories_by_Size_on_Linux). I did this and then uninstalled a couple apps that I didn't care about that were using a lot of space, freeing up loads of space and avoiding getting messy with datafixes. Alternatively I think there's an actual app that will show you usage (DiskUsage?).
[Captivate Android Development] FaintPuppet:
When I flashed the RC2 and Nightly for 7/20, I touch the Android and it says, "Unfortunately, Setup Wizard has stopped." Am I doing something wrong? I wiped everything before and followed the instructions and everything. I came from RemICS if it matters. I wiped everything. Boot animation shows up, I'm given the option to touch the Android, I do it and I get the message I just mentioned. After the first time, I tried wiping data/factory reset, cache, dalvik cache and fix permissions and that didn't. Anyone have any ideas?

EDIT: Never mind, got it to work. I'm loving this so far!
[Captivate Android Development] zzmomo73:
Hi, sorry for the question but what is different in rc2 that's not in the nightlies?
[Captivate Android Development] account4me2:
Pretty sure it's essentially identical to the 07/17 nightly. If not, the difference would only be a small number of changes made on the 17th, 18th, or 19th. Probably nothing really notable.

You can view the changelog here: http://changelog.bbqdroid.org/#captivatemtd/cm9/next, although it doesn't show the RC so I'm not sure if what it says is entirely accurate.
[Captivate Android Development] metalfangs:
I've noticed haptic feedback is much softer now after flashing rc2. Anyone else experiencing this?
[Captivate Android Development] capefearless:
Reboots when USB Connected

I searched around and didn't see mention of this...

I am on RC2 - "stock" kernel and everything else. I flashed the ROM 2 days ago and everything seems to have been working fine since then. Today, I attempted to connect my phone to my PC to transfer some files but ran into an issue with the phone rebooting. I can't remember if I connected the USB cable to my computer since flashing RC2 (before today) but I don't think so.

Here is what I did and what happens...

1. Connected the USB cable

2. Pull down the menu and notice that Android Debugging is enabled and that USB is connected

3. Select USB Connected

4. Press Turn on USB Storage

5.Window Pops up warning that Applications will stop and etc.

6. Press OK

7. The spining circle thingy goes for a while and...

8. Phone reboots!

I've tried it several times and even tried different USB cables and a different computer and it does it every time.

I made a nandroid before the flash and since then (I was about to test drive CM10 unofficial).

Anyone else seeing this? Any ideas?

UPDATE: I transferred the files to my phone via Airdoid, flashed CM10 and now everything seems to be OK. Still curious though if anyone else experienced this and if so what was your fix?
[Captivate Android Development] ap1618:
CM10 is out for captivate??!
[Captivate Android Development] RootTheMachine:
It's unofficial and alpha... can't miss it in the dev section

Sent from a jelly bean
[Captivate Android Development] ThreeofNine:
sssooooooooooo..............with no new nightlies for 2 days, I guess CM9 for the captivate is done? Very very nice work devs!!! Wondering if the Captivate has enough resources to run JB or just put my phone into storage in a few months and get the SGSIII or Note 2?
[Captivate Android Development] CheesyNutz:
i would say its NOT done just all the devs are working on jelly bean
[Captivate Android Development] Ajfink:
Absolutely, but I'm happy for it. In terms of bugs not hammered out of CM9 (not many left, AFAIK), those can still be resolved once everything is transitioned to CM10. It will just take some work to get all the ducks in the row in CM10. It's thankfully not the massive jump it was from Gingerbread to ICS.
[Captivate Android Development] ThreeofNine:
You're probably right, but with the captivate being almost 2 years old and new phones have 2-4 times the ram and faster cpu, there might not be too many of us still using it. I can upgrade in September, but I'm holding out for late year discounts on a new SGSIII or maybe a Note 2.
[Captivate Android Development] theaudioguy:
There have been a few jb roms on here for the cappy. I'm running Monfro's v6 right now.
[Captivate Android Development] xK1LLSW1TCHx127:
abort

Hey guys I'm having an issue, I'm coming from darky GGB and I did the cache wipe/factory reset and my phone keeps aborting the installation, any advice?
[Captivate Android Development] shane87:
What error are you getting when the install aborts?
[Captivate Android Development] xK1LLSW1TCHx127:
I think I uploaded a picture. Apparently the error is in the zip file, as you can see it says error and has the location of the ROM, thanks for the quick response
[Captivate Android Development] shane87:
You are coming from a rom/kernel combo that reports your phone as an i9000 instead of an i897. You have two options: use a odin/heimdall one-click package to revert to stock, then use odin/heimdall to flash an i897 kernel that has cwm injected. Or you can open the zip and use notepad++ (assuming you are running windows) to edit the updater-script (located in the zip at META-INF/com/google/android/updater-script) and remove the lines at the top that start with assert(getprop, then save the file and rezip the install package.
[Captivate Android Development] xK1LLSW1TCHx127:
Ahhhh, I see thank you! I will use an Odin package thank you=)
[Captivate Android Development] simple man:
Me too, or maybe a new Nexus.
[Captivate Android Development] lordxentris:
Install a ICS supporting recovery first and then flash the nightly file. You must be trying to flash from a GB Recovery thats why it throws the error.
[Captivate Android Development] shane87:
I flashed to ics from gb recovery, the stock kk4 kernel with cwm injected to be exact, the first time I installed cm9 and it went fine.

The problem is that his prop files list his build id or device id as i9000, but the zip file is designed for use on i897/i896 only. Its a very common issue for people who are coming from ported i9000 rom/kernel, since the props reflect what the rom was originally designed for.
[Captivate Android Development] scythekain:
I've had this issue as well, you need to flash a compatible kernel. I would suggest the latest Devil Kernel. The will let you flash any i897 ROM.
[Captivate Android Development] Gromlakh:
Flashing devil kernel over a GB ROM would likely lead to an unbootable phone.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] xK1LLSW1TCHx127:
Gromlahk is right, its just I'm coming for an i9000 ROM with an i9000 kernel and cwm, I'll just flash an Odin. Maybe yoy can help me with this: I want a ggb Odin package without boot loaders correct? Boot loaders is only if I was flashing eclair or froyo, but since I'm on gingerbread I don't need boot loaders right? Thanks!
[Captivate Android Development] shane87:
Yeah, flashing devil over a gb rom would lead to an unbootable phone. However, recovery would still work, and that is all you need for flashing to cm9.

Visit http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide for links to heimdall and a compatible cloworkmod injected kernel, along with full instructions for flashing to cyanogenmod from stock gingerbread.
[Captivate Android Development] The.Se7enth:
I'm not gonna lie, I'm still somewhat new to this whole custom ROM scene, even though I've played around with it a bit and gone through several roms already. If I wanted to flash /back/ from the Slim ICS ROM to CM9, how would I go about doing that? Would I need to go back to stock with Odin first?
[Captivate Android Development] shane87:
No, that wouldn't be necessary. SlimICS and cm9 use the same partitions. Your best bet would be to back everything up, using tibu or your fave backup method, then reboot recovery, wipe data/factory reset, then flash cm9 + gapps, then restore your backed up apps.

As a note, be careful if you use tibu to backup/restore. Some people have had issues using batch restore in tibu. It causes the datadata partition to fill up faster. Personally, I manually restore all of my backups. Its more of a pain, but compared to the headache of datadata getting full its the lesser of two evils.
[Captivate Android Development] Gromlakh:
The Tibu issue can be easily avoided by simply not wiping data or doing a factory reset. That isn't necessary at all unless you are having issues. The only thing you should be wiping are cache and dalvik.

You also do not need to flash gapps every time you flash. They do not get wiped out by the flash, at last not if you are only wiping cache and dalvik.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] nkrick:
CM for the Captivate is definitely not done. Pawitp maintains CM for both the i9000 and i897 and he has confirmed at least twice in the i9000 CM10 thread that everything is in place for the Captivate to get CM10 as soon as nightlies start coming out. He just doesn't have time to compile unofficial Captivate CM10 ROMs himself so only the i9000 crowd is getting teamhacksung CM10 alphas this time (at least between the i9000 and i897). You can follow the progress of CM10 on the i9000 here: http://xdaforums.com/showthread.php?t=1778526
[Captivate Android Development] The.Se7enth:
Hm. Well, I did the full wipe (data and cache both), even formatted /system, and when I tried flashing CM9, it gave me an error. Since I was having issues with that, I tried resolving my problem on SlimICS by reflashing it. Seems to have worked, but in case I decide I want to try CM9, I'm baffled as to how to pull it off.

And, I believe the issue I had with SlimICS related to TiBU as well. I had a keyboard glitch that I believe was caused by restoring the app+data with TiBU instead of manually redownloading it from the website. I decided to manually reinstall everything from TiBU still, one by one, without the batch option, and only selected two apps to restore data from with the app (SMS Backup and Zedge). That worked without a problem, so I'll keep that in mind. I'm glad you mentioned that or I'd probably still be doing the same batch thing and potentially getting errors out of it. Much appreciated.

To me, it's a safe bet to go ahead and reformat everything. I do the same when upgrading my operating system. Even though I could potentially upgrade from Vista to 7 and retain all my applications, I feel it's safer just to back all my data up, and reformat the entire hard disk, and reinstall everything from the start again. That cuts out all risks of any errors.

Maybe I'm just overly cautious, but since I've had my phone for over a year now, it's out of warranty, and I absolutely cannot afford to replace it. Plus it's been a fantastic phone so far, with all of these custom roms, and I just don't see any appeal in the Galaxy S III even if I could afford it.
[Captivate Android Development] simple man:
If you flash the Icy-Glitch kernel while on SlimICS, it will let you flash CM9, that's what I did to flash from SlimICS to CM9.
[Captivate Android Development] The.Se7enth:
Awesome. I'll keep that in mind then.

I'm hoping to eventually find another rom that I'll keep for months on end. I actually kept Miui for 8 months, from November until just now. But I felt out of date and it was starting to run a little sluggishly, so I wanted to try something new. Not sure if I'll find that in ICS roms, but, it's worth a try.
[Captivate Android Development] simple man:
That's funny, I have been on ICS for the most part since miui.us quit supporting the Captivate, but just yesterday I flashed the last miui.us-GB release again, just because I missed the huge selection of themes, and a few other features. It really is a fast, bug free rom. I do miss some of the ICS enhancements though. It's nice to have so much development for this two year old device.
[Captivate Android Development] The.Se7enth:
Yeah, I really loved the themes. I also loved the "firewall" app to screen out calls so I never had to check my phone every time it rang to see if it was the same telemarketer or not. It was remarkably smooth, and I'm sad to see that it's not supported anymore. It was a fantastic rom, and I'm glad I stuck with it for as long as I did. I'd really love to see an official ICS Miui, but oh well.

I'll eventually upgrade to the Galaxy Note II once I have the money to afford it in the first place, but I'm not sure if that'll even be supported by Miui at all. I guess I'll have to wait and see. Hopefully, at the least, there'll be a custom rom scene for it. I'm not sure how big people are on the Note as opposed to the S series. I've been more impressed with the Note than the S myself though -- S3 was a letdown in my opinion.
[Captivate Android Development] Gromlakh:
Ok, I can appreciate wanting to be safe, but at this point you're way past the point of overkill. In fact, I'm quite positive your decision to format /system before flashing caused the last error you mentioned. The CyanogenMOD installer has to read your build.prop file before it starts flashing, which is located in /system. You format that, you kill the installer before you start. Not to mention that the very next step the installer does is format /system, so there is absolutely no point at all in trying to do it before hand.

Plus...seriously bro, all that formatting and wiping is only making more work for you. It does not help in any way, not does it protect you from errors. Android is nothing like Windows, and the actual changes made to your phone by the installer are minimal. Cache and dalvik wipes are needed when you flash a new nightly, anything else is a complete waste of time. The possibility of an "error" coming by not wiping more is pretty much zero.

I've had this phone nearly a year, and in that time I've been a major flashaholic. I've tried nearly every ROM out there stuck with CyanogenMOD for probably the last eight months, and I always flash a new nightly every 3-5 days. In all that time, I've never once done a master clear, data wipe, or factory reset. And I've never once encountered a problem.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] shane87:
Nah, wiping /system won't kill your props. Those props are read by the kernel at boot time and stored in ram, so that even if the prop files get deleted, you can still check the current props. I know that I have reformatted system through recovery and I was still able to install a cm9 nightly.

As far as wiping data/factory resetting not being useful, I beg to differ. Back a few months ago, I had an issue with not being able to send or receive mms. I tried flashing new nightlies, and I tried flashing old nightlies from before the issue started. Nothing worked. Until I did a wipe data/factory reset, then reflashed the latest nightly.
[Captivate Android Development] Gromlakh:
If there's another way to read the props, then great, that must not have been the specific cause of the error. The point is, though, it's overkill and there's no reason to do it.

This is the point I'm trying to make, and the point I've tried to make several times. Flashing is designed to actually be a rather painless and easy process. For the most part, the install package does the work it needs to have done. If it needs /system wiped, it wipes it. If it needs /data wiped, it wipes it. 99% of the time you should be able to flash the package and be done. If there is a problem and the problem doesn't fix by simply reflashing the package, then perhaps wiping more stuff could be in order. But there's absolutely no reason that stuff should be standard procedure.

People read around these forums and they get the impression that it's actually required that you practically brick your phone just to prepare it for a flash. I see thread after thread and comment after comment of people saying "OK, to flash, first wipe cache/dalvik/system/data, then master clear, then flash back to stock Eclair, then master clear, wipe, flash to stock Froyo, wipe/master clear, reflash bootloaders, turn your phone twelve times counterclockwise, wave chicken bones over the phone, master clear/wipe again JUST TO BE SAFE..." When it should say "Step 1: Flash. Step 2: There isn't a Step 2." Unless you actually observe a specific issue after reboot and that issue does not resolve by simply flashing again, 99% of the time you are completely wasting your time and only causing more work for yourself by doing all of that nonsense.

Cache/dalvik wipes I don't mind, because the only result of a cache/dalvik wipe is your phone will take a little longer to boot the first time. You haven't actually lost anything. But factory resets/data wipes/master clear? Waste of time, unless again you're seening specific problems and cannot resolve them any other way.
[Captivate Android Development] shane87:
I agree with you 100% that most steps are overkill. I just wanted to make the point that wiping data is not pointless, IF you are seeing issues. And I only recommended a data wipe in the first place to make sure the database structures didn't get messed up in the flash, as I am not sure if slimics uses datadata. The error he was getting in regards to prop asserts is that slimics identifies as an i9000 instead of i897, which messes up the cm9 flash script.

And just for the record, I take issue with people recommending unnecessary wiping, too. If you need to revert to stock, a heimdall/odin one-click to kk4 gb is perfectly sufficient, as that performs all of the wipes you need, and there is absolutely no point going back earlier than gb, since gb bootloaders will load every rom made for the cappy, from eclair to jb. And wiping cache and dalvik after a wipe data/factory reset is pointless, since wipe data/factory reset formats data, which is where the dalvik cache is, and it also formats cache as well.

To everyone else, sorry for the slight derailment of the discussion of cm9 nightlies. This info is important to anyone looking to flash, but it is not cm9 specific, so i apologize for taking the thread off track. Your regularly scheduled programming will now continue.
[Captivate Android Development] The.Se7enth:
Just to say, but, um.

You can say it's not necessary, but I still feel safer following directions exactly as they're stated. I don't like to cut corners because even if someone says the odds of encountering a problem are low, it can still happen, and I'd rather be safe than sorry. I've had this phone for OVER a year, and have also flashed numerous roms. I've soft-bricked my phone a few times and managed to recover by wiping everything in CWM and flashing back to stock, and then trying to install the rom again. And considering I actually hard-bricked my phone when I first got it, even following AT&T's instructions when the official upgrade to 2.2 first came out, I'm definitely not taking any risks now that my phone is out of warranty and I have no possible way to replace it, and it's a pretty major lifeline to have right now.

I appreciate your opinion and all, but, even if it's an "unnecessary step," it's not as though it does any damage. You can say it's a waste of time, but it's my time to waste. So long as the job gets done, isn't anyone technically allowed to do it how they want?

Sorry if I'm coming off rude or anything. Not trying to, just, I don't see why it's a big deal honestly. I'd say it's better that I'm following all of the instructions, and asking for help, than not following /any/ instructions and then asking for help.

I have to admit though, your example instructions cracked me up a bit. I don't think I'm in possession of any chicken bones, but I rather like the 'turn your phone twelve times counterclockwise' part. Just brilliant, absolutely brilliant.

I know it's supposed to be easy, but since I have run into issues, I try to take that slight extra step of precaution. And formatting /system has never really caused more problems, so it's a safe step to take when I run into issues like that. Otherwise, I don't bother with it. I never did it before with any of the previous roms, I only tried it when going back from SlimICS to CM9 when it didn't work the first time -- and it still didn't work, regardless, so it seemingly didn't make a difference either way. No help, no harm. It was still worth the try though.
[Captivate Android Development] whipps:
(post deleted by user)
[Captivate Android Development] mms6:
does this work on my Rogers i896 ?
[Captivate Android Development] beall49:
I just flashed this and I'm having this 'Server Error Retry' error in Google Play, I'm unable to get in at all.

I've cleared cache, reflashed the ROM and the gapps, tried that market faking app...nothing seems to work...any ideas?

Edit: I didn't have the correct gapps, I had to go to the wiki and get the correct date.
[Captivate Android Development] Ok_Kaleidoscope5109:
Guys, so I was running CM7.2 Final up til now, and I flashed CM9 today after a FULL WIPE...

Well in the middle of flashing the phone restarted itself on its own, and now I'm stuck in a bootloop where I see a dead Android (as if recovery were attempting to start) for a flash second before it reboots.

I got a USB Jig and got back into download mode, flashed some stock firmware with CWM, and retried CM9. SAME THING

I tried nightlies 0730, and 0729.

Note: This is my friend's phone and Captivate flashing isn't my expertise (I do regularly flash my Nexus S and SGS2 though). She got her phone in June 2011, and using some method on this forum I rooted and put CM7 on her phone. I updated her to CM7.1 and 7.2 whenever I saw her across the time she's had her phone and it's worked flawlessly flashing through CWM.

Can anyone tell me what's going on? Is this a known bug? Am I missing something crucial?

Edit: Tried again. I flashed a stock ROM with CWM, flashed CM7, rebooted flashed CM9. I noticed that in the middle of flashing it rebooted itself, and it looks like CWM6 started? Then it continued to flash.

Looks like that's what it was doing when bootlooping but I guess it couldn't continue flashing. The only difference I can see is I removed her SDCard. Could that be causing the bootloops?
[Captivate Android Development] carlosgardel:
Sorry Im not an expert by any means but If you got to Download mode how you get to CWM to flash to stock. You have to Odin or Heimdall to stock. Use a Gingerbread stock with bootloader. I think you need Gingerbread bootloader for CM9.

Here is a good explanation http://xdaforums.com/showthread.php?t=1350266