yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Gromlakh:
Dude, you should *NEVER*, under any circumstances, use AIO to flash stock. Putting aside all the other problems with flashing stock in the first place, you really, really should read this post from Adam Outler, one of the most highly respected devs on these boards. Not only does he quote from the author of AIO that flashing around using Gingerbread is 100% not supported with AIO, but he also points out that AIO's "flash to stock" option flashes the secondary bootloader and nothing else. That is horrifyingly bad practice and a sure-fire way to 100% hard brick your phone if you end up with mismatched bootloaders. I don't care how "easy" AIO makes it; if you're insistent on flashing back to stock, find another way to do it or you run a very high risk of ending up with a paperweight.

Flashing to stock is also not a guaranteed way to get a clean install. The vast majority of the problems people run into when flashing new ROMS are bad flashes from CWM. There's a highly technical explanation for this that I won't get into (search function if you care enough), but essentially CWM flashes will always be less reliable and more prone to "bad flashes" than using either Heimdall or Odin. This is not a knock on CWM, it's just reality. That "bad flash" happens regardless of what's on your phone right now, it's entirely due to how CWM is "flashing" things. So flashing to stock JF6 won't make it more or less likely that you get a bad flash. All it does is add one more step to your flashing process, when you would have ended up in the same place if you'd just gone ahead and flashed the new ROM from CWM. The "fix" for the bad flash is just to head back to CWM and reflash, which again will be the same regardless of whether you'd flashed stock JF6 before the first attempt.
[Captivate Android Development] RichMD:
+1. Anything that flashes just a secondary bootloader is one of the riskiest things you can do when flashing your phone... It is like Russian roulette... :eek:
[Captivate Android Development] littlewierdo:
I dont use AIO to flash to stock, I use AIO to inject CM into the stock rom. Get your phone to stock in whatever method you choose, personally, I use Odin because I dont have GB bootloaders installed (and I dont want them until Samsung makes them official).

AIO is convenient because it gets the recovery menu installed without having to root, setup the market, instal rom manager, & install the recovery menu, all AFTER you have the phone at stock.

Secondly, say what you want, reflashing CWM did not (and does not) fix the garbly and quiet phone audio I get (usually happens every 2 weeks or so). And we arent talking about annoyingly quiet, we are talking about the other person barely being able to hear me in a dead quiet room (I tested this personally on a land line and 3 different brands of cell phones all on different carriers).

It doesnt fix it. Period, end of story. I can delete caches, fix permissions, do a factory reset and do all the voodoo bull**** in the world including reflashing CM to my hearts content and the audio is still unchanged.

I dont have the means to troubleshoot this like I would a PC, I just know basic things that are suggested to fix problems with Android (usually involves the deleting of temporary data). If I knew what was going on and had a way to fix it, I would. But for now, it is the only thing that works.

Oh, and fyi, I use the stock CM kernel and stock CM modem but I have tried flashing different kernels and different modems both BEFORE the problem arises and AFTER the problem occurs and it doesnt prevent or fix the problem.

I might also add, simply reflashing CM did not fix my other cappy where the alarm clock continued to force close after hitting snooze. This was a phone running stock CM & stock CM kernel & modem with NO APPS INSTALLED. It had all the voodoo nonsense tried, resetting to factory specs, deleting the caches, fixing permissions, even deleting the alarm data under settings>applications.

So, yea, you are entitled to your opinion. If you havent had problems, great. I personally have and a simple reflash is not always the answer.

I would prefer to avoid trying voodoo fixes to 'see' if they work and do what I know to nearly ALWAYS work which is a stock to CM install.

One more thing, Id love to use Heimdall except I cant find a JF6 image that works. The recommend samsungfiirmware website gives an xml error when I try to use it. So, if anyone has a link to a JF6 image that works with Heimdall (and preferably doesnt have the bootloaders included - I can remove these if I need to but it would be nice if they were not included), that would be great.
[Captivate Android Development] kimocal:
I thought mine wasn't working but mine took about 20-30 seconds to start the first time. Now it loads right away.

To go directly to the Band Selection use *#*#2263#*#*
[Captivate Android Development] magistrateee:
I've tried many reflashes, data wipes, to no avail. Did anyone else have this issue and get it sorted out?

Is anyone still having this problem and if there is a possible fix? I have tried using nightly 149+ since there was apparently there was an sd card

fix.

"Conform and fix SGS SD card stuff inside Android OS (2/4) (android_device_samsung_captivatemtd)"

I don't particularly mind how it mounts as long as I can access my 32GB. If I am able to access it, it seems to barely last until a deep sleep or reboot mode then it disappears and give me the errors mentioned above.

Thanks for the help.
[Captivate Android Development] mystichobo:
Hey guys,

The only thing holding me back from switching to CM7 at the moment is the lack of TV out, has this been implemented yet?

Use my phone quite a bit as a portable media player :)
[Captivate Android Development] staplebox:
I have the same problem and have not been able to get either of 2 different 32g cards to work. I don't know when the problem started or what it may be, but it is there. We are not alone.
[Captivate Android Development] \/icious:
Not yet. 10char
[Captivate Android Development] Thesandlord:
Hey guys quick question. Is HD recording working for you? I still get tons of dropped frames. However when I did a complete reflash I got it to work, but once I installed a few apps and set up my phone it stopped working again. Any suggestions?
[Captivate Android Development] skatcat31:
Well guys, I love my cappy but I just upgraded to an att sgs2 and Sony tablet s. Sad to say I will be giving My cm7 cappy to my mom, but it was a fun ride while it lasted. Love and mad respect, Skatcat.
[Captivate Android Development] nightshack0:
Anyone knows why the changelog appears up to nightly 155 but in the downloads it goes to 157 (and it also skips 156) .. ?
[Captivate Android Development] michaelgening:
Sorry I have to "reply" you before I can leave a comment here, and since you are a senior member, may I ask you a question? I inserted the SD card, but under the folder of internal card, there is no shortcut to the external one, thus when I use app such as file manager or video player, they couldn't locate my media files on the external card, what can I do about that? Thanks a lot in advance!
[Captivate Android Development] sixstringsg:
It is located at /emmc.
[Captivate Android Development] anishz:
The album art for music on lockscreen is only available for the stock player, is there any way to get it to work with other music players (Ubermusic, miui) which support "Folders" category.As most of my music is comprised of singles rather than albums, right now, on my phone i have close to 1800 'Albums', and is very difficult to browse.
[Captivate Android Development] killsto:
Last time I tried CM7 on the captivate, the battery life was really bad compared to Samsung based ROMS and HD video recording didn't work. Have these been worked on/fixed?
[Captivate Android Development] jkl555:
I upgraded from 7.1 stable to nightly 158. It seems the external card is moved from /emmc to /sdcard and the internal becomes /emmc.

D:\Captivate\ROMs\CM7>adb shell

# df

df

Filesystem 1K-blocks Used Available Use% Mounted on

tmpfs 173052 32 173020 0% /dev

tmpfs 173052 0 173052 0% /mnt/asec

tmpfs 173052 0 173052 0% /mnt/obb

/dev/block/mtdblock2 192000 142120 49880 74% /system

/dev/block/mtdblock3 81920 36124 45796 44% /cache

/dev/block/mtdblock5 16384 14600 1784 89% /radio

/dev/block/mmcblk0p2 1935192 437220 1497972 23% /data

/dev/block/mtdblock6 176128 95632 80496 54% /datadata

/dev/block/mtdblock4 12800 5752 7048 45% /efs

/dev/block/vold/179:9

3868768 329824 3538944 9% /mnt/sdcard

/dev/block/vold/179:9

3868768 329824 3538944 9% /mnt/secure/asec

/dev/block/vold/179:1

13660864 2479136 11181728 18% /mnt/emmc

My external card is 4G in size and you can see it is mounted as /mnt/sdcard once I move up to nightly 158.

So confusing.
[Captivate Android Development] Gromlakh:
Don't know about the video recording, but I can definitely say that battery life is not CM7's strong suit. Hopefully this will change once Samsung finally makes an official GB release and gives us source code.
[Captivate Android Development] anishz:
Battery life on CM7 is totally dependent on the usage, if you use only for calls and some light use samsung roms are best but for heavy usage CM7 is actually better, just try screen time on both yourself then decide, rather than someone telling you. I definitely get upto 4 or more hrs of screen time with CM7 but standby is less whereas in samsung roms standby time is almost 2 days but screen time is just near about 2-2.5 hrs.
[Captivate Android Development] airtower:
Not for me, my internal is still mounted at /sdcard on 158. I'm not using an external SD card though.
[Captivate Android Development] shaolin95:
Same here. I have an external card and nothing changed for me with 158
[Captivate Android Development] jkl555:
Hmmm. That is so weird.
[Captivate Android Development] cbasse:
Same here as well... No change, still /emmc
[Captivate Android Development] loserskater:
Try going to Settings>CM Settings>Application and make sure "Use internal storage" is checked. If it already is, try unchecking it, reboot, and then checking it (and then rebooting again).
[Captivate Android Development] tiuk:
A few nightlies ago they fixed the checkbox and if you had toggled it before, you now have to do it again. Checking the box and rebooting will solve the problem.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] airtower:
This didn't change anything for me. Internal still mounts to /sdcard. Not that it matters, just sayin
[Captivate Android Development] cuban788:
Alright i have this problem since i flashed cm7 like 5 days ago everytime i reboot my phone it gets stuck in a bootloop. I have reflashed and i made sure to do every step perfect. Has anyone else had this problem i need help thank you in advance.
[Captivate Android Development] RichMD:
And... you are able to get by it somehow or has your phone been stuck for 5 days? Does it work if you have it powered off and turn it on but "reboot" from the extended menu causes the bootloop? What kernel are you using and do you undervolt? A little more info would help troubleshooting.
[Captivate Android Development] cuban788:
I have to reflash everytime to get it to work but then i have to make sure my phone doesn't die and then it works fine. I get bootloop from both if it turns off or if i do reboot from extended menu then it goes into a bootloop when i turn it back on. kernel is the default one that comes with cm7 and i do not undervolt.
[Captivate Android Development] RichMD:
When you reflash, have you done a factory reset/wipe data? Does it happen even before you restore anything via TB, etc? If you do a factory reset, flash the latest nightly, and then it happens before you make any mods or restore then I would suggest flashing stock first just to see if that helps.
[Captivate Android Development] cuban788:
Alright i try going back to stock thank you if it doesn't work ill post back
[Captivate Android Development] RockRatt:
No need to go back to stock. Just wipe data/factory reset. Then get everything working without using titanium backup. Once you have it working correctly then you can use titanium backup to restore APPS ONLY and not the associated data. Once that works without issue you can START to add some data back to your apps. This should fix any problem you are having.

Sent From My KICKASS CM7 AT&T SGS2
[Captivate Android Development] cuban788:
ok thank you im backing everything up right now.
[Captivate Android Development] sixstringsg:
Don't forget a nandroid either.
[Captivate Android Development] cuban788:
Problem solved Thanks to everyone that helped me :)
[Captivate Android Development] CougarBroker:
When I send a text it never arrives at the destination.

Where are the text message settings?
[Captivate Android Development] jkl555:
Thanks. That solved the problem.
[Captivate Android Development] Jemack:
@cougarbroker - Go to text msg all threads screen, hit menu, and settings.
[Captivate Android Development] FireRaider:
No incoming sound on first call

I am still having an issue with the first incoming call after a reboot. I have narrowed it down from what I thought was random to for sure its the first incoming call after a reboot, there is no sound from the caller until I call them back or they call me back. Once I have called out it doesnt happen again. And if I call out first I never notice it.

I posted this a few months ago and several others mentioned it as a random occurance also. I think I might have narrowed it down because I swap batteries about 3 times a day.

I follow this thread pretty closely and dont recall anyone else mentioning this as an issue? Nobody reboots as often as me, or is my phone just weird?

It has persisted through months of nightlies and several Factoryclear/resets.

The main drawback to this feature is my cussing loudly at my phone when it happens, my wife is not terribly impressed by this language when she calls nor was my boss. LOL

Obviously its not a big deal to me but I wondered if anyone else had noticed it or if there was a fix?
[Captivate Android Development] CptTwinkie:
Have you tried anger management counseling? :-P

I haven't had the issue myself but you don't say in your post if you've tried going back to stock? I know it's sort of a last resort but if you've tried everything else then it's all that's left to try.

You could also check for the problem while you're on stock to make sure it is cm related.

Sent from my Captivate w/ CyanogenMOD 7.1
[Captivate Android Development] curti.nogg:
I have this issue sometimes as well. I haven't really paid attention to when it happens. If I'm unable to hear the caller I'll put them on hold, resume the call, and after that it seems to work fine.
[Captivate Android Development] CougarBroker:
I can't find anything there... anyone have an idea why I can't send texts? They just vanish.
[Captivate Android Development] Jemack:
What do you mean by.....they just vanish?
[Captivate Android Development] pandakh:
I flashed nightly 155 and my market fcs, already cleared Everything, uninstalled update, still... Any help?
[Captivate Android Development] CougarBroker:
I send them, they say sent, and no one ever gets them...
[Captivate Android Development] anishz:
Change the locale from US(hd) to US or something else.
[Captivate Android Development] Twicebak3d:
You probably deleted your smsc. I had this issue after installing an app called phone info. The messaging app CM uses doesn't allow you to modify it. What carrier you on? Btw you can test if it's the issue by using your sim in another phone. If it doesn't work with an alternate phone, it's smsc, as it's stored on the Sim.

If you're on Att, download phone info, open it, go to phone information, and scroll down to the input box for smsc.

smsc for ATT is "07913121139418f0"

Input that number and press update, then press refresh to see if it sticks.

Sent from a CM7 i897 that is quite possibly more than a few nighties behind.
[Captivate Android Development] magistrateee:
I am just wondering between the internal SD card and the external SD card.

Traditionally or what would be better if my internal 16GB SD card is set as:

/mnt/emmc/

or

/mnt/sdcard/

I wanna set it up to how it typically is so I can future proof for future flashes and such since I think i got my external SD card working.
[Captivate Android Development] RichMD:
Repeated Lockup when booting in airplane mode

I never post in multiple threads but my first post may have been in the wrong thread (glitch kernel thread). If anyone has any ideas before I wipe everything (without a current backup) please let me know....

I flashed CM7 #157 Sunday after a factory reset (so a clean install) and then installed the glitch app and V13RC. I then calibrated the battery - let it charge to 100% and then ran it until it died. For the last couple of hours I had it in airplane mode since I was at work. After it shut off, I let it charge until full overnight. This morning when I boot up (still in airplane mode) I can not unlock the phone. It boots up to the lock screen (no background which is odd) but everything else shows. I can't move any of the ringlock icons at all to unlock it though. I have rebooted several times and have the same result. I would just wipe everything and install clean but my last backup is before the 157 install...

Any ideas? Is there any reason that airplane mode would cause a problem if enabled at bootup when running V13RC or the new app?

Edit: I tried pulling the SIM card (to try something) and also I wiped dalvik, cache, and voltage settings by booting to recovery mode. No luck - the phone is locked solid every time it boots. I see an icon in the status bar like it is scanning the SD cards and it goes away but I get no response when trying to unlock the screen. After sitting at the lock screen for about a minute, it rebooted by itself... - still locked though.

Edit2: I booted to recovery, mounted USB storage and put V12B3 on my SD. I then used "clean kernel files" and then installed the V12B3 zip. After booting up - still locked. I was "guessing" this was kernel related but maybe not.
[Captivate Android Development] SweetwaterBurns:
Is your phone plugged in while you are booting? I've had some similar issues(no wallpaper, screen won't turn on) unless I boot with it running on battery.
[Captivate Android Development] RichMD:
Sometimes yes but I also tried booting off just battery in case that would help - unfortunately no, but thanks. I have since tried the Neo kernel - no luck and then I decided to try flashing 158 after wiping dalvik and cache. Still no luck. The next thing I will try is formatting system and reinstalling 158 since that would put me back on stock kernel (I think) to see if I can at least run a current backup and then wipe everything and start over...

Edit: Good news - My phone is back up and running. Bad news - Even format system and installing 158 (running on battery only) didn't help - still locked on bootup. I resorted to wipe data/factory reset and installed 158. My backup isn't too old so I won't lose much but my enterprise email (Good) is a hassle if I have to get a new pin, etc.
[Captivate Android Development] FireRaider:
I will try the Hold trick and see if that changes anything.

Its not a big enough problem to go back to stock, and I suspect that wont fix anything anyway.
[Captivate Android Development] APE992:
Any particular reason the home button (as of last night's (10/25) nightly) doesn't do anything anymore?

That is, beyond flash upon being pressed. Seems the PIN input doesn't come up anymore either. If I didn't know any better I'd say something is broken...

Possible I messed something up but I follow instructions to the letter and beyond the above nothing HUGELY wrong has cropped up. Just a handful of small things. Almost like it erased my customizations and started from stock settings enumerating my installed applications as well as personal data. Very weird.

EDIT:

Seems to be a problem with my end of things. Restored my backup from before the installation and it still had home doing circles with all of the stock widgets up and running. Bah. First AT&T cuts off my service and hasn't restored it in over 15 hours and now this.
[Captivate Android Development] cbasse:
I flashed 158 and I'm not having any issue with the home button.

What did change, though, and made me search all over before figuring out what happened, was the sound and brightness increment selection mode. If you use these, you'll need to go in and make some selections.
[Captivate Android Development] tiuk:
Same, those and I had to select percentage battery indicator, it went back to icon. Home button is fine for me.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] johnhazelwood:
I flashed 158 and noticed I can't install apps or updates to apps (insufficient memory). I tried unchecking the expand memory option in cm settings, rebooting, rechecking, rebooting but no luck. I reinstalled version 152 and all is well again. Anyone else?
[Captivate Android Development] APE992:
That happened to me too.

Just restored my second latest backup from early October and everything was as it should be, sans a month of text messages that will be restored shortly.

Installed 158 over it without bother with 157 and it appears to be 100% back to normal, at least with the battery icon being an icon rather than percentage but I'm pretty sure that was by design and not because of another fault. I'll change that out later.
[Captivate Android Development] loserskater:
Traditionally you're internal sd (built-in) is set to /mnt/sdcard and your external(removable) is /mnt/emmc
[Captivate Android Development] CougarBroker:
Thanks, it worked perfectly. Since CM7 has dial codes now, you can use *#*#4636#*#* 4636 equates to "info"
[Captivate Android Development] nkrick:
It could be that your PIN was reset (purposely or accidentally) by Good, or that your phone was administratively locked by Good. Most of the enterprise messaging applications have options to give the admins ways to completely lock people out of their phones. Usually it is triggered by too many bad PIN/password attempts, but it can be pushed manually also.

---------- Post added at 10:52 AM ---------- Previous post was at 10:50 AM ----------

Actually, *#*#4636#*#* is the one dialer code that I know was working previously. Since "info" is not part of the Samsung service mode, but is more generic, it was working all along (or at least since April/May timeframe).
[Captivate Android Development] zeroonea:
I cannot turn on my Bluetooth :(
[Captivate Android Development] evanstapler:
Was the option for the battery percentage and bar removed? I can't find it in the options anywhere.
[Captivate Android Development] CptTwinkie:
It's still there. It took me a while to find it again. CM settings>interface>status bar tweaks>battery status style

Sent from my Captivate w/ CyanogenMOD 7.1
[Captivate Android Development] RichMD:
FYI that there is an open change being debated to add a "MIUI-Style" battery bar which personally is one of my favorite UI tweaks of MIUI. Apparently, it is considered "ideologically wrong" to add that.... ??? Everyone agrees the code is fine - I think it is a problem with "copying" an idea...

Does anyone know if there is any way for users to "vote" whether they want an option to be merged/added?

http://review.cyanogenmod.com/7677
[Captivate Android Development] :
Is anyone having trouble with text tones not playing?
[Captivate Android Development] tbrummell:
Most informative post ever!
[Captivate Android Development] Klyentel:
So when is the TV out settings going to be implemented into the CM rom? I really missed that feature, that and battery life would be the only two reasons to flash anything else other than CM
[Captivate Android Development] shaolin95:
For me , I rate CM7 at 99% perfect and the 1% is that TV OUT. I cannot wait to get that working :-)