yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] EnemyOfGlaDOS:
just the factory reset is the evil one ;) data cache and dalvik cache wipes are safe.. no need to restore anything :)
[Captivate Android Development] RockRatt:
Can't report on Glitch since I haven't tried it but I flashed this last night as soon as it was available. I was very surprised by the speed, placebo or not it just feels good. Well by the time I went to sleep I only showed 10% on my battery. Woke up this morning 7 hours later and thought my phone would be dead but it still had 10%. So going into sleep mode seems to be working really well.

I had no issues getting data after the flash, no issues installing it and I used rom manager to download and install along with gapps. I may just keep it stock for a day or so to really feel it out before OC/UV at all.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] skatcat31:
Now this intrigues me. Flashing 71 now to see battery improvements.
[Captivate Android Development] kmakiki:
Yeah, flashed good ole 71 this morning (and reflashed Glitch), battery life seems to be very much improved. Especially sleeping. Set my phone down and walked away for an hour, came back and the percentage was the same. :D
[Captivate Android Development] XsceneXhippieX:
what are you talking about? like the tegra 2 driver plugin for chainfire3d? i have been playing tegra 2 games flawlessly (maybe with a texture or 2 coming out white but still VERY playable) since around when cm7-rc1 came out on my cappy... just saying, the plugins not only are working currently, but also have been for quite some time, so go get that installed and dont waste any more time not playing tegra 2 games!!!!! lol :) gotta stay light hearted people!
[Captivate Android Development] born_fisherman:
great!

10char
[Captivate Android Development] Tiggles:
Between steps 6 and 7

am I suppose to still be in recovery? Download mode?
[Captivate Android Development] MisterAnthonyxD:
For the .tar file, yes.

Sent from my Captivate running CyanogenMod 7
[Captivate Android Development] theMaDHakkeR:
Im just wondering if its normal to only show 3G. My low speeds came from being on Edge but the phone was showing 3G, and never H although im getting H speeds and upload speeds. Using the JL3 modem.
[Captivate Android Development] ankitb4u:
I flashed the recommended voodoo kernel then resflashed the update and I am running flawless
[Captivate Android Development] michael.seltzer:
If I flash voodoo can I get back to the original kernel? is it just the kernel i flashed in Odin when I installed cm7?
[Captivate Android Development] nkrick:
KB1 has no voice processing because AT&T uses an Audience Chip for voice processing. The N1 also uses an Audience Chip. Any chance that in the future, the N1 audience driver (or some Captivate drivers after the 2.2 source drops) can be added to the Captivate/SGS CM7 kernel to allow us to choose either Audience or HSUPA? There is always a chance that AT&T will release a modem supporting HSUPA in the future which would give us the best of both if the Audience driver is available...
[Captivate Android Development] QuarkGluonSoup:
My phone takes a few minutes to establish a 3g signal after I turn it on, although the phone signal seems to be unaffected. What can I do to fix it? Also, the thread with the install instructions says we should make sure we haven't disabled our HSPA, and to check use the dialer code *#301279#. I did that and got the error message "connection problem or invalid MMI code". What does this mean?
[Captivate Android Development] n19htmare:
You have to flash a CM7 modem....not just any modem. Check the soundforge page for links to modems. link http://sourceforge.net/projects/teamhacksung/files/captivate/

I'm running the JK4 and been working well.

I followed every instruction to the Tee. And I have had no issues so far. No forclosures, Wifi works fine, Phone calls are fine... everything seems to just work. getting 3MB down and 1.6MB up on my 3G.

Just nada to complain about.

99.9% of the time the cause of the problem is user error and directions not being followed correctly. If it's not working, do another flash by following the instructions down to the last period.
[Captivate Android Development] blazin619:
I bet the carriers are pissed that i didnt have to buy a newer phone to get gingerbread. This is running very well. I haven't had any bugs to be honest but if i do experience some i am sure it wouldnt be as bad as the faults the captivate had with its initial firmware. I have absolutely no lag now. Its really amazing! I was gonna get rid of this phone too... also everything else works fine! My battery life is much much better than with any froyo rom really. I haven't put this phone down all morning with all haptic feedback and still got plenty of juice left and i didnt charge it last night... even though i flashed at 3am
[Captivate Android Development] tcortinag:
Try to lock and unlock few times, that should bring up back connection.

You should checked this before installing CM7, so after you install CM7 HSPA is enabled (if it was disabled).
[Captivate Android Development] miahsoul:
Couple quick questions.

1. Does this support Custom Boot/Shutdown animations? When I shut down, there is no animation, just a notification that the phone is shutting down.

2. Can I turn off ADW launcher or get a Gingerbread/Vanilla Feel somehow?

3. Does SpeedMod work on this?
[Captivate Android Development] blazin619:
You people need to go back to school if you cant flash this rom with out help
[Captivate Android Development] Boobie Watcher:
any chance on a CWM flashable zip
[Captivate Android Development] citrit:
I had this same question and it was answered for me a while ago. What I did was:

- Reboot into CWM recovery and apply efsbackup.

- Somehow get into Download mode: This can be done from CWM or using key combinations.

- Flash cm7 initial kernel as described using odin without reboot.

- Unplug the usb cable and pull the battery and then put the battery back in and get into recovery using the button combo.

Short answer is yes, you have to get into download mode to flash with Odin. I have nightmares about download mode so I always take my time to make sure I understand what has to happen.

This worked great for me, the ROM was very fast and I never had a reboot or crash. The big pain is the battery life is very short. I didn't play with it enough to optimize, I was a bit nervous about getting back to other ROMS so I switched back to Cog 4.1.1. But now that I have made it there and back again I will try again soon.

And hey, if I can do this anyone can. ;-)
[Captivate Android Development] gocats7:
No Time soon if ever.
[Captivate Android Development] RockRatt:
So I am on the 20110303-01 and all went great and working without a hiccup. BUT no matter what if I take the 20110304 update and place it into the sdcard, 3button to recovery, install update, it does not give any errors, then I TRIED to use the reboot from cwm but it will just stays at the art screen. I redownloaded the update via a PC and placed it in the sdcard in case I just had a bad download, went through all the steps again and same deal. Also tried to apply the voodoo kernel from the open and same thing.

Am I wrong with how I am applying the update.zip? Am I missing a step? Or do I need to use the initial 110304 from Odin then apply the update 110304.zip in cwm?

I KNOW how to get back to my original nandroid and restore with no issues. But I would really like to figure this out for future updates. Any thoughts or ideas? I tried it many more times this morning with the same results and cannot figure out what I am doing wrong or missing.
[Captivate Android Development] tcortinag:
Well you install efsbackup.zip and cm7-captivate-initial-20110304.zip thru CMW so you have 2!!!!!

Read some pages back to find out about a CMW flashable zip
[Captivate Android Development] KreacherComfort:
So I flashed everything and it all seemed to be going well until after i had been using it for a few minutes. At that point the home button stopped working. I flashed the update and it still wont work. Anyone?
[Captivate Android Development] QuarkGluonSoup:
How do you lock and unlock it? Is this "sim lock"? When I go to "set up sim card lock" and click "lock sim card" it asks for a pin number that I never entered in, and I don't know how to lock the sim card otherwise.

So you are suppose to dial *#301279# to make sure you haven't disabled HSPA before you flash cyanogenmod? If the installation of cyanogenmod enables HSPA, why does it matter if you had it disabled or not before?
[Captivate Android Development] XsceneXhippieX:
can you explain the difference between 100mhz and deep sleep mode? i am still relatively new to the captivate as i am less than a month into owning it, and my previous HTC never said anything about a "deep sleep" state like control freak and voltage control mention. all i know is my custom lockscreen (ripple lock from the market, basically a combo of honeycomb/sense3.0/miui) seems to prevent deep sleep state and sits at 100mhz when the screen is off and locked, which im assuming hurts my standby battery life, but i would like to know the difference between 100mhz and deep sleep state for sure before i do anything
[Captivate Android Development] melbourne408:
My god, beautiful back tracking through the last 4 pages I haven't read after the hangover pt 3, lets now rabble rabble rabble about scripts and ideal placement and justification. I don't want none of that cop-out wishy washy, time to back up and hopefully pull a coreym and not a shaolin ;) with this 8-bit glitch encryption haha

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] EnemyOfGlaDOS:
definitely don't pull a shaolin.. whatever you do! :D
[Captivate Android Development] skatcat31:
Right downloaded 71, updated without gapps. Lost gapps. Installed gapps, market couldn't download. Reinstalling update with gapps. Will update as life goes down the pooper.

EDIT: Right it's dead. Fresh install here I come... Any idea why this would happen? Or any ideas on how I could fix it if it happens again?
[Captivate Android Development] FireRaider:
#71 broke my Bluetooth just like #69 did. It wont even turn on bluetooth on. The first time I tried it just rebooted the phone. Now it does an odd double boot-up and still doesn't work.

Back to #66 again I guess. Its been my stable go-to nightly.
[Captivate Android Development] insaneturbo13:
Hmm. That's odd. Bluetooth works fine here. Scans and pairs fine. I'm using glitch kernel though. Maybe just stock doing it?
[Captivate Android Development] FireRaider:
If thats the case I will flash #71 again and then add glitch to see if it fixes it. Although I had the same issue with #69 and nobody else reported it.

I always flash from recovery and wipe cache and dalvick-cache to keep my programs and data intact.
[Captivate Android Development] FireRaider:
Are you running Glitch v11 with the HL, ll, or ML version?
[Captivate Android Development] insaneturbo13:
Version 11 hl
[Captivate Android Development] melbourne408:
Glitch working well with the latest and greatest, am I the only one who hasn't had to flash gapps while flashing the og way-keeping everything intact.

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] FireRaider:
I had everything but the bluetooth flashing from recovery. All my apps, market, etc.

sent from XDA app
[Captivate Android Development] EnemyOfGlaDOS:
Everything intact here bud!
[Captivate Android Development] kmakiki:
Yep, didin't need to reflash anything other than glitch. Market and gapps work fine.
[Captivate Android Development] FireRaider:
Weird. Not sure what fixed it but I reflashed #71 from recovery, then flashed glitch v11 HL right after and Bluetooth seems to be working fine this time.

The only thing I did differently was add Glitch (which I had tried without success for Bluetooth problems on the #69 version), and also this time I went into settings to turn on Bluetooth instead of doing it from the drop-down bar.
[Captivate Android Development] dangerdan:
I'm getting no service when I flash the KB1 Modem. Is there something wrong?
[Captivate Android Development] jhernand1102:
Yes, CM7 doesn't support Captivate modems.
[Captivate Android Development] Delwyn:
Is anyone else having root issues with 71? For example, I can't use use df in terminal emulator but when I revert to 69, its fine. Also all apps needing root permission is a hit and miss with 71. Tibu is fine but Root Explorer won't load and ROM Manager can't fix permissions because it can't get root privileges even though it has in Superuser.
[Captivate Android Development] dangerdan:
Didn't it used to? I have the CM7 KB1 modem but it doesn't work. So I'm out of luck on CM7 if I have one of the Captivates that can't use non-captivate modems?
[Captivate Android Development] RockRatt:
Just tried out root explorer, terminal emulator with "df", and rom manager and had no issues with any of them.

ALSO looks like #72 is up already and appears to have a bt fix.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] nkrick:
KB1 is supported, but voice quality is very bad due to the missing audience drivers.
[Captivate Android Development] melbourne408:
Haha just went to sup up my homies phone and was hella ####?

I don't use lightbulbs....are my peripherals dulled out huxley status didn't see this an hour ago haha

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] dangerdan:
I know this, but on the newest nightly when I flash the CM7 KB1 Modem and restart it just stays at No service.
[Captivate Android Development] XsceneXhippieX:
I have everything intact as well, all data is there and such, my wallpaper did change to cm's default blue nexus though oddly enough, but i unpacked the .zip downloaded from cwm, added/deleted junk to my liking, repacked the .zip (all using root explorer, i do this every nightly i flash which is about every 5-10 nightlys) and all my Gapps are still in place including the "new market" that i place in system/apps, only wiped dalvik and made a backup because i flashed through cwm but the only setting up i ever need to do (or choose to do, rather) is flashing Glitchv11, reinstall all my boot scripts (ie 3 supercharger scripts, a ram script, voltages, custom screenstate scalings, etc. and fix all their permissions via root explorer) reinstall chainfire3d, and then reboot 2-3 times for good measure and everything settling down. I only ever have problems if I do something stupid lol

I have never flashed a modem before, but if i get amazing reception, really fast data speeds, great voice quality, and amazing battery life already should i even try out a few? and if so does anybody in lower central USA have a prefered modem?
[Captivate Android Development] dangerdan:
Anyone have any ideas? The Baseband and all of that info is missing after I flash the CM7 KB1 Modem.
[Captivate Android Development] FireRaider:
Nicely done with noticing that BT change. I am downloading now. :)
[Captivate Android Development] XsceneXhippieX:
OMFG! bln is totally working using glitch kernel for the first time ever using nightly #71! I am not only excited, but also happy with said revelation :)
[Captivate Android Development] kmakiki:
Is there any where we can go to mess with BLNs?
[Captivate Android Development] RockRatt:
Glitch kernel and The Escapist kernel le hour both have/ have had them working for a LONG time. At least for the escapist kernel you just use bln app to set it up.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] scottlinux:
#71

I cannot seem to join a WPA wireless network for some reason.

From the router side it looks like it is rejecting the login.

Android just quits trying after awhile and says 'Wi-Fi disconnected' (but checked!).

Anyone else have any wifi probs?
[Captivate Android Development] XsceneXhippieX:
I knew le kernel du jour had BLN working, because it worked every time i flashed it, but even with the BLN app ive NEVER gotten any BLN working on glitch until today when i flashed the nightly #71, i havent even gotten a buggy half ass BLN working on glitch until today personally! I didnt do anything special, didnt even re-download glitch, and the fact that my personal captivate has working BLN on glitch now makes my day :) now the only thing i need to figure out is how to get the softkeys to stay lit up during only the duration of the screen being on and BLN on cm7 using glitch (i know the escapists kernel is the only one without a timer set to the softkeys, but le kernel du jour just isnt up to par with glitch on my device)
[Captivate Android Development] montavious:
Trying to help a friend of mind this has been going on for two months. We flashed cm7 nightlies a while back and since then basically we are stuck with it, completely unable to flash any other ROM. My thought was to flash to stock with odin however even though the phone says its in debugging mode, the pc and odin say its not.

Any ideas how we can flash back to stock or another Rom from cm7? We've tried different cords and pc's and still have the same issue. Thanks in advance!
[Captivate Android Development] Kaik541:
debugging mode and download mode are NOT the same thing, even a little bit.
[Captivate Android Development] scottlinux:
I did it - back to original stock ATT. So it is possible.

I used Heimdall in Windows XP. (Couldn't get it to work in Linux).

Had to locate original samsung captivate rom from the interwebs. It is out there if you search.

http://www.glassechidna.com.au/products/heimdall/
[Captivate Android Development] montavious:
Thank you ill give that a try later tonight. Been bugging us for a while and though I know my way around this stuff I've only had HTC phones before...no download mode or other nonsense to deal with. Thanks again for the link
[Captivate Android Development] shaolin95:
Hey! :mad:

At least I am consistent cause I installed #72 and I algo got the reboot issue! :D

I did not try the cache thing until I get confirmation that it wont erase apps and it any case, installing Glitch fixed the reboot but it left me wondering that could be wrong...:confused:
[Captivate Android Development] insaneturbo13:
Sorry. I didn't know you were looking for confirmation. Clearing the dalvik cache. And cache partition will not delete your apps or any data from the apps... Other Than The useless cache
[Captivate Android Development] shaolin95:
Cool then I am going to try it again. Just because I dont feel good knowing that it did not run correctly :-)
[Captivate Android Development] Johnston212:
Hey, I'm trying to find out if anybody is having issues with bluetooth as of #71. It just crashed on me as I went to connect my headset and since then I cannot enable bluetooth whatsoever. I also went ahead and flashed 72. I do not know what caused the crash or what is causing this problem, but it's a major issue for me. Any suggestions I can get will be extremely helpful
[Captivate Android Development] melbourne408:
:(

sorry shaolin, many can't read my sarcasm waivers as well as you. Interesting tho, have to look into what's up with that. One thing I learned, a setback is a setup for a comeback :)

(^ one of my waivers I pass out daily haha)

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] comdei:
any problems with 72?
[Captivate Android Development] singlebeam:
Running great except I can't get my Google Talk app to start. It starts then closes without any FC notification.
[Captivate Android Development] sixstringsg:
Make sure that you have the newer Modem zip. Try redownloading it from goo-inside.me.
[Captivate Android Development] Johnston212:
Alright, I'm going to give this a shot. I'm going to flash back to 69 since BT was working then and if it is working, then flash forward to 72. Hopefully this will give me BT again.
[Captivate Android Development] Delwyn:
Thanks for checking, I guess it was just a bad download. 72 resolved all issues.
[Captivate Android Development] Johnston212:
Ok, so I have flashed back to 69 and still no BT. I went into recovery and cleared cache and dalvik, still no BT. I'm now backing up everything and I"m going to flash forward to 72, backit up and clear everything. I can only hope this will work.
[Captivate Android Development] RockRatt:
Have you done anything else lately, like flash a modem? Or install anything that may have messed up the BT for you? Did you restore ANYTHING via titanium backup that may have caused it?

I will test my by right now and see if I have issues at all. Maybe you are not alone.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] Johnston212:
Thank you. I thought I was going to be alone on this whole situation. No, I've done nothing like that. It's completely broken, like when Mobile AP was broken. I go to enable BT in ANYTHING (Settings, Quickbar, Quick Settings) and all it does is say it is turning on. It does not enable I'm just finishing up a TiBu backup and I"m about to flash to 72 with a full clean, so we will see what happens.

In all honesty, even though I know this will simply flame, CM has been a bit glitchy in this last week. My phone up and decided to delete my text messages, the last 2 times I've flashed Glitch I've had it reset SU, so it's been an interesting week. I just hope I can get this fixed tonight.
[Captivate Android Development] skatcat31:
Threatens only one thing you can do to truly test if things don't work after you're tried everything, flash a sammy rom.

Sent from something from somewhere
[Captivate Android Development] melbourne408:
Just me or with glitch, on xda premium and #72 using wifi when I go back a page it redirects me to the main OP march page, the page number reading correctly but wrong. So far none of that has been a problem all today.

Sent From My Swaggin 1.6 Son of Glitch
[Captivate Android Development] insaneturbo13:
I cannot reproduce that... Wierd problem though.
[Captivate Android Development] FireRaider:
I had the same issue with 69 and 71. Flashing the glitch kernel fixed it.

I am on 72 now but stayed with glitch.

sent from XDA app using
[Captivate Android Development] nkrick:
Post Glitch problems to the Glitch thread

Seriously, this thread is for CM7 problems, NOT problems with the Glitch kernel. More than half of the recent posts have been about flashing Glitch. If you want to talk about Glitch, go the the Glitch thread.

Problems with Glitch != Problems with CM7. I have never used any kernel except the kernel provided by team Hacksung and I have NONE of the problems that people have been complaining about with losing apps, losing text messages, losing bluetooth, etc. Post your problems to the Glitch thread, or flash back to stock, reflash CM7 and test using the team hacksung kernel. ONLY if you can reproduce your problem with the team hacksung kernel (after flashing to stock to remove all traces of non team hacksung kernels) should you post your issue here.
[Captivate Android Development] Malorkus:
#72 is working well for me. Thanks to everyone who puts time into these builds.

Are there any plans to update the Music app and associated music controls/widgets/etc to the new Google Music app? I really like the "listen to" voice command that the new version supports.
[Captivate Android Development] nkrick:
Google apps cannot be pre-installed on CM due to an agreement between Cyanogen and Google. If you want the new Google Music app, you need to install it yourself. If you look around on the internet, you will find instructions on how to install it.
[Captivate Android Development] z28james:
Not to mention that using a 3rd party kernel is essentially reverting to whatever happened to be current at the time the kernel was released. Its essentially saying that I fixed the problems in #72 by reverting to #60 (or whatever nightly was current). This does nothing to help fix the current code base.