yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] cmdrmonkey:
I've been getting extremely slow i/o speeds when the phone is in usb mass storage mode of only like 500kb/s. Does anyone know what would be causing this and how to resolve it?
[Captivate Q&A, Help & Troubleshooting] ap1618:
which kernel?
[Captivate Q&A, Help & Troubleshooting] cmdrmonkey:
The latest nightly of CM9, whatever kernel that is.
[Captivate Q&A, Help & Troubleshooting] axl81:
Flashed the 07-16 nightly and found it to be blistering fast. Everything on the phone was very responsive; fastest it has ever been for me. Then I realized that I needed to flash gapps and sync my phone. After I did this the phone slowed down noticeably.

Is this related to the number of apps that I have installed on the phone, or is it related to google sync running in the background? Is there a setup that would bring me closer to the speed and performance I was experiencing before I flashed gapps and synched to my google accounts?
[Captivate Q&A, Help & Troubleshooting] shackwrrr:
I've been using the nightlies for a while and just upgraded to RC2, I have had these issues from the start and can't get them figured out.

The first issue is that I can't log into YouTube, When it pulls up the accounts page to select my Google account it force closes and I get the "android system has stopped" dialog. I've tried different ways of logging in but get that every time. If I open the accounts list from the settings menu it works fine.

The second problem is one of my apps, BeWeather pro. When I try opening the radar/maps it force closes the app. This App has no issues on other ICS phones.

Other than these I have no issues, Its like having a new phone. I upgraded from 7 because I thought I was having issues but it was just the /datadata partition was full.
[Captivate Q&A, Help & Troubleshooting] ap1618:
i just checked the youtube app on RC2 and it signed in ok. trying clearing your application data and signing in again.
[Captivate Q&A, Help & Troubleshooting] shackwrrr:
Tried this, tried clearing davlik, clearing cache partition. Tried uninstalling youtube and reinstalling.

It crashes before it even opens youtube. A screen that says android system with the little pulley in the corner pops up that is blank, then that closes and I get the "Unfortunately, Android System has stopped." I hit ok and it just goes back to the man homescreen.

I have managed to make it past this point but it hangs at the "Signing in" Dialog in youtube."
[Captivate Q&A, Help & Troubleshooting] falcon7204:
Trying to flash CM9 08-08 nightly

Hi,

This is my first post here, and I searched this thread and could not find the solution to this issue, so here goes:

My Captivate SGH-I897 had been running CM7 for several weeks almost error-free. But when I discovered that there was an MIUI ICS ROM for the Captivate, I jumped at it. My daughter's HTC Vivid runs ICS, and I like the look of it, so I wanted to give it a try.

So I flashed the MIUI ICS over CM7 (after first making a Nandroid backup - I'm not a total n00b :laugh:) and tried it for a week. It seemed stable enough, and I like the ICS look, but I did not like the fact that all of the apps showed up on the home screens (a la iPhone) and I missed the presence of an app drawer. In addition, since MIUI is done by a group of Chinese developers (who do great work, BTW), there are some language issues with the interface and a couple of instances where the only text available was Chinese. So, after a little while, I decided I wanted to go back to Cyanogenmod, but I thought I'd try CM9. I d/l'd the latest (and apparently last) nightly build and the most current Gapps for CM9, backed up all my apps and data (so now I have two backups) and proceeded to flash.

And this is the error message I got (forgive me, but it was transcribed from the screen as I was restoring my CM7 Nandroid backup):

assert failed: getprop("ro.product.device")=="captivate" || getprop("ro.build.product") == "captivate" || getprop("ro.product.device") == "captivatemtd" || getprop("ro.build.product") == "captivatemtd" || getprop("ro.product.device") == "SGH-I896" || getprop("ro.build.product") == "SGH-I896" || getprop("ro.product.device") == "SGH-I897" || getprop("ro.build.product") == "SGH-I897"

E:Error in /sdcard/cm-9-20120808-NIGHTLY-captivatemtd.zip

So, does this mean there's an issue with the latest nightly? Should I stick with the CM9 RC or try an earlier nightly build? From what I can tell, the nightlies seem to break as many issues as they fix. Or should I go with another ICS ROM (this may be a dangerous question to ask in this thread :p)?

Thanks for any help you can provide, and I'll keep plugging along in the meantime since I have a workable backup.

UPDATE: Never mind. Discovered the reason why it wouldn't work before was because I was trying to flash over MIUI. When I restored my CM7 ROM and tried it then, it worked. Seems like CM9 is pretty responsive and faster than Gingerbread, and the Cyanogenmod folks responsible for CM9 are to be commended for their work.
[Captivate Q&A, Help & Troubleshooting] Deegan87:
I'm having the same error on mine updating cm9 stable over cm9 RC2. Now the phone is stuck on the cm boot animation. Anyone know how to fix it?

UPDATE: Fixed. Formatted the boot and system partitions. I blame semaphore.
[Captivate Q&A, Help & Troubleshooting] kangi26:
Your issue is actually pretty simple. It's the kernel; if you install a CM9 Kernel, then install the ROM, then gaaps, you'll be good to go
[Captivate Q&A, Help & Troubleshooting] Ikonomi:
Hi, I'm trying to clarify the modem situation for myself. You're saying the I9000 modems WILL take advantage of HSUPA and will NOT use the Audience chip, while the I897 modems WILL use the Audience chip (but the chip is not supported in CM7/CM9) and will NOT get HSUPA speeds? This is my first non-Samsung ROM so I'm a little unclear of the particulars, but that's how it worked on the Samsung builds.

So the best bet is to use an I9000 modem?

I have tried a couple I897 modems and I'm told the call quality is very bad on the other end. If that's the case for everyone I'm wondering why bother packaging all the I897 modems for use with CM7/MIUI. My unique problem is that, near my office, data speeds on I9000 modems slow to a crawl, while I897 modems work fine. I have a hunch that if I disable HSUPA to restrict the phone to normal 3G, the I9000 modems will work at my office. I thought at some point I saw a menu that let you do that, but I can't find it right now. It may have been a menu accessed via the dialpad.

Edit: Duh, found it -- it resides in the Galaxy S Settings shortcut now. Hopefully this fixes my data problems!
[Captivate Q&A, Help & Troubleshooting] kangi26:
You are correct in your first paragraph. Generally, you will take a little bit of a hit on voice quality on the i9000 modems, just because of the audience chip. But you'll get better DL/UL speeds.

Something to check into is, what frequency band is in your area. That COULD be causing some of your signal issues.

Take a look at http://soggycashew.weebly.com/modem-location-map.html

Try to find a point in your area on the map, you can usually find a recommended modem to try

Edit** The Houston area, seems KP1, and the JL3 are recommended
[Captivate Q&A, Help & Troubleshooting] shanmanz:
Check WCDMA Band

How do I verify if I am using 850 Mhz? *#0011# doesnt seem to work:confused:
[Captivate Q&A, Help & Troubleshooting] devi59:
My first question about the Captivate. I've only had it for a few months, and I've been on this rom now since build 4. It works as smooth as expected but I have a question about TV-Out. I have a set of cables and they work fine as far as the menus and I've played angry birds on my tv no problem but when I try to play any video it only seems to play on the Captivate and the audio comes out of the TV. Is this because of the Rom or is this normal for the captivate? I've never had the cables for any other Rom to test so I was just wondering what the problem might be. I'm leaving for christmas to my in-laws and I have my sons christmas program I was going to show everyone there from my phone but I'm testing it at home right now and it's not showing the video to the tv. Whats really weird about it is say YouTube or something that has a video overlay for the controls shows up on the TV but the video only shows on the phone. Any immediate help would be great!
[Captivate Q&A, Help & Troubleshooting] rpr69:
ICSSGS issue, no Q&A thread?

I am using the ICSSGS RC1.0.1 build, I can't post in that thread because I am a 'noob' (not really, just never posted here before) but I have an issue with Gmail, every time I try to start it, it closes with 'Unfortunately, Gmail has stopped'. I can see in the sync status that it has synced up, but I can't launch the app. I am pretty sure I installed correctly:

wipe data, wipe cache, wipe dalvik, flash rom, reboot , flash rom again, flash kernel (3038), boot

Everything seems to work well, with the exception of Gmail. On hacksung build 10 I could never get Google calendar to sync, now that works, but Gmail doesn't. One step forward two steps back.... :)
[Captivate Q&A, Help & Troubleshooting] kangi26:
I have run both and I've had no problem with either ROM's synching Gmail or the calendar

Sent from a autonomous device
[Captivate Q&A, Help & Troubleshooting] robertomguimaraes:
ICS i897

I flashed both teamhacksung 10 and onecosmic rc1, THS with lag and more bugs, onerc1 is very clean and fas, no lag transitions and all resources functional.

We need a fusion onecosmic&teamhacksung to a perfection ICS!:)
[Captivate Q&A, Help & Troubleshooting] daskanda:
did you get a chance to test?.... i switched to onecosmics RC1.0.1 and still no vibrate when i recieve a text message only pulse notification.... i wonder if theres a setting im missing

nvm it was just a setting i didnt see lol
[Captivate Q&A, Help & Troubleshooting] bumbernut:
Can I assume the the recent app list/task manager is just slow ? It sometimes force closes system ui. Is this pretty common ?
[Captivate Q&A, Help & Troubleshooting] rpr69:
Well, I re-flashed after clearing everything again, and now gmail works, the calendar says it is syncing, but nothing is showing in the actual calendar. Man, I just can't win for losing, I can get either mail or calendar working, but not both, it seems. I'll let it charge up, reboot, and check it again, hopefully it works. Also after the reflash the screen lock works, it didn't before.

Having said all that, I'm still loving ICS!
[Captivate Q&A, Help & Troubleshooting] modmyphone:
Use

*#*#0011#*#*
[Captivate Q&A, Help & Troubleshooting] pixelens:
Not sure if this is a bug - thought I'd post here first. Running Photoshop Express app on Build 9 and when I save an image it does save but it doesn't appear in the gallery. The only way I can access it is via usb on the computer.

Anyone else seeing this behavior?
[Captivate Q&A, Help & Troubleshooting] rpr69:
Following up on my previous message, after leaving it overnight, mail and calendar are working perfectly.
[Captivate Q&A, Help & Troubleshooting] axel4401:
Post got deleted from the development thread, so here it is.

I have had the ICS Build 10 for a bit now. About 3 days ago I started not being able to send text messages. I can send them and make/receive calls. Everything else works great, just no sending of texts :( . thanks for any help
[Captivate Q&A, Help & Troubleshooting] pixelens:
Are you using the stock messaging app? I use Go SMS (am on Build 9 though) and am having no problems. I recall reading that someone else was using Go SMS and had uninstalled the stock messaging app and started having issues. He reinstalled stock app and from what I recall his issues disappeared.
[Captivate Q&A, Help & Troubleshooting] axel4401:
I am using stock. I wiped then reflashed. Still notta. I just tried GoSMS and still nothing. I don't know if I mentioned I'm using the ugjk4 modem. I tried a few more too.
[Captivate Q&A, Help & Troubleshooting] kangi26:
I guess my first question is, when you first flashed Build 10, did you come from stock, then CM7? Did you upgrade from a different version?
[Captivate Q&A, Help & Troubleshooting] axel4401:
I flashed over a gingerbread rom. I did not come from stock I came from apex 11. Everything worked after the flash. I'm not quite sure what I did to make the texting not work after that. I wiped and reflashed yesterday.

Also, I just tried to MMS my email and it worked. So now I'm just extra confused.

Just a recap:

-Can't send texts, but can receive

-Can send MMS

-Everything else works
[Captivate Q&A, Help & Troubleshooting] kangi26:
Wow, I just don't have a answer for that one, sorry. If it were me, I'd be flashing back to stock/master clearing installing CM7 and starting from a clean slate
[Captivate Q&A, Help & Troubleshooting] s25verma:
Updated, now brick

So long story shortened:

1. Updated to ICS 4.0.3 Passion v13.1

- worked perfectly, except, that this is meant for vibrant. So I tried to restore from back up and start again.

2. Went back to CWMR to restore back up--which is an Eclair back up.

3. Tried to restore back up -- MD5 checksum error.

4. Rebooted through CWMR menu.

Consequence: I am stuck (a brick) in AT&T splash screen. Won't access download mode, won't access recovery mode.

I believe the JIG won't work because this is an updated bootloader (am I right?). Is my phone good as dead? :(

Any help--even if it means "Yes, your phone is dead" will help. I could send it in to Samsung (out of warranty) but they say they'll charge me about 200 dollars--might as well get a new phone.
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Your phone is not bricked if you can get to the ATT splash screen, and there is nothing wrong with your bootloaders. If there was a problem there, you would see nothing at all when you turn the phone on.

You should be able to still get into download mode. Try leaving the battery out when you try it, out if that fails a jig should work just fine.
[Captivate Q&A, Help & Troubleshooting] kangi26:
No your phone is not dead. A couple of questions for you though. Pull your battery, under it there should be a sticker that shows a text that says, 10.06, 10.07, 10.08 or so on, what number does yours show? (I suspect it's low based on the fact you were at Eclair) 10.07-10.12 is best, don't do the following if it is higher than that

You'll want to flash back to stock.

1. Go here

2. Download "I897UCJF6 - Odin3 One-Click Downloader". It's a Odin 1Click, which will take you back to Stock JF6.

3. Make sure your USB cable is connected directly to the back of your computer, not a USB hub or to a front connection and all of your drivers have been properly installed

4. Do not connect your USB cable yet.

5. On your phone, go to ; Settings/Applications/Development/and check “USB Debugging”

6. Turn your phone off

7. Remove your SIM card and Micro SD if you have one

8. Open Odin One Click

9. On your phone, press and hold the Volume up and the Volume down buttons. Do not touch the power button. If you have a ROM that supports a extended power menu, just press and hold the power button until the extended power menu comes up. If you can't get into DL mode, insert your JIG, it'll put you into DL mode. Remove the JIG, insert your USB cable and go to #11

10. While holding them, or after you select DOWNLOAD mode, insert your USB cable, wait for a couple of seconds and a yellow triangle with the Android figure will show up

11. You’ll see in Odin, that your phone has been discovered

12. Press “Start”

13. ***VERY IMPORTANT*** Do Not mess with your phone at all. If you lose your USB connection, you could brick your device, and will possibly have to make a jig

14. When it is done, your phone will reboot and Odin will display “Removed”

15. Unplug your USB cable from your phone

16. If you are proceeding to Master clear, you must close Odin BEFORE Master Clear

Master Clear:

1. Ensure you have backed up all of your information onto your Micro SD or your desktop BEFORE doing this. IT WILL ERASE EVERYTHING ON YOUR INTERNAL SD!!

2. Make sure to remove your SIM and Micro SD if you have one

3. With your USB cable disconnected from your phone, open Odin One Click

4. On your phone, go to: Settings/Applications/Development/and check “USB Debugging”

5. Connect your USB cable to your phone

6. You’ll see in Odin, that your phone has been discovered

7. Click “Master Clear”

8. When the Master Clear has completed, your phone will reboot.

9. The phone is now as it was when it came from the factory
[Captivate Q&A, Help & Troubleshooting] s25verma:
I can't actually access anything on my phone. It will stay on the splash screen only. So I can't go into any menus or anything.Can't get to download mode--I know how to. Waiting on the jig. I did make one myself--300k and 301k resistors. Didn't work. Blaming my inability to get it touching the right pins for long enough. It would only turn the phone on, not go into download mode. Waitin gon the manufactured jig to come in

I read somewhere that baseband vesion 2.3.4 or higher don't work with the jig though. And I remember that ICS 4 is definitely higher than 2.3.5 (o r the equivalent).

Not detectable by the computer either -- Odin will not see it.

---------- Post added at 05:54 AM ---------- Previous post was at 05:49 AM ----------

Can't get to download mode even with what you said. Waiting on the jig. Did try the homemade jig and didn't work.

I read somewhere that 2.3.4 and higher doesn't work with the jig as Samsung changed something regarding resetting the binary reset count (i'm not sure what this is exactly). This is why I believe maybe my phone won't be save-able. Is this not true?
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Captivate doesn't have a reset counter. That's the SGSII. I'm not aware of any changes that have ever been made to the Captivate that would affect a jig being able to get you into download mode. It's also unaffected by the version of Android you are using. Download mode is accessed via the bootloaders before the boot process is even handed off to the kernel. The kernel takes over right about the time you see the white splash screen, which is why I said that if you can see that your bootloaders are working just fine. You can still get into download mode.
[Captivate Q&A, Help & Troubleshooting] hednik:
Would I have an issues flashing from due truefel's (sp?) CM10 build with devil kernel 3 back to CM nightlies again ?

It's not quite as stable as I would like it to be and I miss some of the flashed out features on CM9.
[Captivate Q&A, Help & Troubleshooting] kangi26:
You might get a status 7 error. Flash a kernel for CM first and then flash the Rom

Otherwise you should have no issues
[Captivate Q&A, Help & Troubleshooting] hednik:
I'm still fairly new to flashing an CM 9 is really easy to flash and I never had to install a CM kernel because it never stated to. Which one would work best ?
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Just flash it. You don't need to install another kernel. If you get a status 7 error, then flash DerTeufel's ICS kernel and try again. But I highly doubt you'll need to.
[Captivate Q&A, Help & Troubleshooting] hednik:
Thanks. I was only worried since I was going from a JB kernel and then flashing a ICS rom.
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Status 7 errors don't come from you flashing a different number version of the OS. The installer reads your phone's build.prop at the time of installation to see what your phone identifies itself as. The installer is written so that if you are flashing a package on a phone that the package is not built for, the installer will quit. This causes problems for us sometimes, because of the high amount of crossover between the Captivate and the i9000. If you are running a ROM or a kernel that has a build.prop that identifies your phone as an i9000, that will cause a status 7 error until the build.prop issue is fixed (usually by manual editing or flashing a kernel with a correct build.prop file).

As far as I know, DerTeufel's Helly Bean has a correct build.prop file that identifies your phone as a Captivate, not an i9000, so I doubt you'll have an issue.
[Captivate Q&A, Help & Troubleshooting] Baconrules21:
I'm having this very weird bug with CM9 when I first flash it, the IMEI number is shown and everything is fine. Once I pull out the battery and put it back in, everything turns into unknown.

Would any of you know why that is?
[Captivate Q&A, Help & Troubleshooting] hednik:
Thank you for the clarification. This really helped me understand the possible issues. It went off without a hitch though.

One more issue is that no matter what steps I follow it seems like I can never get a clean install. Its like its just installing over my previous nightly install. I've searched around here and a few other places and the steps it tells me to take say that I need to clear cache, davlik cache, wipe/reset data and do this 2-3 times and then run the installer in CM recovery. It's as if it doesn't erase anything and leaves folders, files, data, etc from old install lying around. Its like a windows install that you didn't format the hard drive first. Any ideas on a good step by step procedure to really wipe it clean this time ?

This could be the whole reason but when it says do a factory reset does that mean I need to do it like I would if I was selling an un-rooted phone and go into settings and do it or is the wipe in CWM recovery sufficient ?
[Captivate Q&A, Help & Troubleshooting] dcs95:
Best CM9 Kernel?

I just flashed cm9 stable and I want to know the best kernel to go along with it, any help?:)
[Captivate Q&A, Help & Troubleshooting] hednik:
The one that CM uses is just fine.
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
There is no need to do a "clean" install. The nightly installer is specifically written to only wipe /system for a reason. Wipe cache, wipe dalvik (once is enough, anything more is a total waste of time), then flash. Anything beyond that and you are only creating more work for yourself 99% of the time.

---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------

CM9 stock kernel is good, if you want more options go with Devil (link in sig).
[Captivate Q&A, Help & Troubleshooting] hednik:
Seems like I still have vestiges of old roms and files hanging around. With every install android gets a bit slower.
[Captivate Q&A, Help & Troubleshooting] kangi26:
Here's the "good" thing about FTS/MC(Flash to stock/MasterClear) it erases EVERYTHING except the base install. Any old files/folders from previous ROM's are gone. Just make sure if you do one, to save anything you might want to keep. I would put all of my pictures, music, wallpapers, TiBu backup onto my extSD and run it all from there
[Captivate Q&A, Help & Troubleshooting] kangi26:
That is (IMO) mostly true. Even with the wipe data, caches all original files are still present in the sd. If you take a look at the sd after running a Master Clear(I use Odin 1Click) there are only 4-5 folders left. It literally wipes everything. Removing any possibility of remnant files/folders. AS far as additional time, maybe 10 min tops.

For myself, as I was testing ROM's A LOT, I would always FTS/MC for that exact reason, I didnt want any possible corruption to interfere with the rom I was testing. If I found a rom I liked, and am just upgrading rev's, then I would just do a wipe
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
I understand the function of a master clear, but it's still a complete waste of time in almost all cases because it is not possible that anything on your SD card could have an effect on the operation of the ROM. If your SD card was unusually filling up and you couldn't find the specific cause and just want to start over...OK, makes sense. Selling your phone? Sure. Otherwise? Waste.

Super-clean flashing/FTS for ROM testing? I don't see any problems there.