[Captivate Android Development] kataishin:
See, now the hilarious thing about this is that a lot of the members here all ran to the defense of the rom when it's clearly not fully operational [which is ok]. You can deny your bugs all day long, but the truth is that after flashing the rom ever since I found this rom and even with using a normal method of flashing, as described... things still started out this way. But thanks for your suggestion. But lately I tried flashing back to stock using odin, and then used it to flash speedmod and then CM9. If that is at fault then I will be surprised because this is only the latest method I tried and I am still noticing bugs.

People are concurring with a couple of the bug issues and you suggest the problem arises from something I personally did. While some of that may be true; The truth stands that if the rom was developed successfully "with the proper testing" and such, then we wouldn't be having any of these problems in the first place here, right? And honestly, I'm gonna tell you flat out; if I got half the flack back from Cyanogen himself when I was trying to report bugs, CM7 for Captivate would still be in the nightly stages.

NOW to re-list the un-discussed and under-appreciated bugs in this build:

Scrolling anything too much makes browser and gallery, etc etc crash.

Changing non-stock wallpapers soft-crashes from time to time.

{it's kinda the same thing CM7 did; If you took it out of a couple of it's stock settings, the whole phone crashes. The main one for CM7 was, If you changed the theme color from within the Theme Manager, the phone would act buggy, and still does from what I recall}

It usually takes a day or so for the ringtone crashes, but it does happen and we ARE talking about custom ringtones, NOT STOCK...

All of the sudden you start seeing everything crash like gmail, etc etc.. and I might add that it's sort of hard to notice what causes it.

Oh and also I can't change the page indicator in the preferences without Trebuchet crashing, If I turn the page indicator off then Trebuchet crashes instantly after trying to scroll pages so the scroll functionality def has something wrong with it, right? Could this be a correlation with the scrolling crashes?

Messaging crashes when text messages are too full instead of auto delete working which also leads to the horrible lag when trying to open messaging, for some reason the phone's limit on the cap doesn't work when you import using SMS backup+. This reason is because if you backup without setting the SMS backup+ settings to limit, your phone has no idea what to do and can't handle the heavy load when calling upon the message bin.

As far as the browser goes, it could stand to be optimized a tiny bit. The pages do take a bit longer to load than normal, but that's to be expected when it's meant for a larger capacity phone.

Thanks to all the developers who are looking into this and know that I appreciate all of your hard work as most of the users here do too. And I would also like to give credit to the user who mentioned the scrolling issue because I was having trouble describing the issue I mentioned earlier and you helped bring it to a possible definition. In short, We love this rom and just want to see it at it's best, whether it's on our phone or not(Although some only express what goes on with their phones). I would also like to take the time to apologize to Kaik and anyone else I have offended on the way, I just want to throw that out there because I feel like we need a fresh start to make this work the way it's intended to. Thanks again for everyone's help and hard work on this. Oh, also I will generate a logcat when I notice my phone acting up again in order to expedite this stable build.

Sorry if these issues are repeat but I just want them all to get noticed so we can move past it, our goal is a stable build right now and we are all important to getting it there.

Thank you,

Chance Trahan