yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] sixstringsg:
That is correct. There is the same effect on battery with either implementation, and it is very very little. Here's the difference if you're wondering: LED notifications is in line with upstream CM7. It was done by Kang I believe, and it is how CM7 implements it. The way I did it for Glitch with zach's help is BLN from Neldar, like the Froyo days. It uses either the BLN control app, or Blinky. One isn't technically better than any other, I just like BLN better because it can flash the lights.
[Captivate Q&A, Help & Troubleshooting] slayersabre5:
Thanks for the replys, but is there anyway to keep the soft keys from doing that?
[Captivate Q&A, Help & Troubleshooting] sixstringsg:
I don't know that there is a way to with stock kernel. You might be able to set the "quiet hours" to be all day long, but I don't know. But you can disable it in my kernel, just sayin :)
[Captivate Q&A, Help & Troubleshooting] havenfx:
Trying to flash CM7.1 Rom on my captivate - I should be able to just flash straight over my previous rom (2.3.5 rom, i9000, talon kernel)

When i go to install the zip, i'm getting this error:

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

E: Error in /sdcard/update-cm-7.1.0-Captivate-signed.zip

(Status 7)

Any ideas?
[Captivate Q&A, Help & Troubleshooting] jmtheiss:
I had the same problem. The fix is to go into your build.prop file (which is in the root directory, I think) and change any references to another build (e.g. I9000, i896) to i897. Reboot into recovery and give the installer a second try.
[Captivate Q&A, Help & Troubleshooting] havenfx:
Interesting. I wonder why this wasn't a problem when I flashed other ROMs in the past. Okay, trying this now, will report back with results :D
[Captivate Q&A, Help & Troubleshooting] sixstringsg:
Because this one checks to make sure you're flashing the right version, so for example you can't flash a fascinate version on accident.
[Captivate Q&A, Help & Troubleshooting] havenfx:
This is what my build.prop file contains:

don't want to mess anything up :\

---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------

gotcha, makes sense!
[Captivate Q&A, Help & Troubleshooting] jmtheiss:
Everywhere you see "GT-I9000", change it to "SGH-I897". I'd say don't change the lines after "# Do not try to parse ro.build.description or .fingerprint", though.

If you're nervous, just make a backup copy of your build.prop file to somewhere safe, and you can restore it later with ADB from the CWM recovery screen.
[Captivate Q&A, Help & Troubleshooting] havenfx:
alright thanks!
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Another option, if you're not comfortable messing with the build.prop file, is to flash a stock Samsung ROM first, then flash CM7 from that. There's a great Heimdall package here that includes stock KH3, no bootloaders (so no danger of a hard brick), and boog's modified kernel with CWM already in place. That's how I made the move from Obssession JVT.
[Captivate Q&A, Help & Troubleshooting] zeroonea:
I'm on nightly rom. My battery is bad compare with cognition 5v2, and my bluetooth cannot turn on :(.
[Captivate Q&A, Help & Troubleshooting] TheJareBear:
Ok, I understand now. :) Also I used to use your kernel for BLN, but I'm curious how to get better battery. I undervolted among other tips but still, it went too quick. For the last month or so I've been on the stock CM7 kernel which isn't too bad.

^I probably should've asked this in the Glitch thread, but this is convenient and ties in with CM7.
[Captivate Q&A, Help & Troubleshooting] the_cosworth:
So it doesnt look like there has been a fix. I was right back down to stock, flashed to CM7.1. Wiped and reflashed again. Then went about my way putting the data back together.

However my SD card isnt mounting (like has been mentioned). There was mention of this happening if you overwrite GB but I came right from Froyo.
[Captivate Q&A, Help & Troubleshooting] johnhazelwood:
I'm noticing the included mail client uses push mail instead of obeying my fetch rules. Anyone know a way to resolve? I think battery life would be better if push weren't being used.
[Captivate Q&A, Help & Troubleshooting] galakanokis:
Been running 7.1 on the i896 for awhile now and so far no problems and I really love it. Very few bugs and quite fast and responsive.

I was curious about playing with different kernels but I seem unable to flash Glitch. I get stuck at either the Cyanogen boot screen or the Glitch boot screen. I am loading through CWM as it is mentioned but no luck. Any tips or ideas what is up? I know this should be in another part but I am new and cannot post in the development portion and it is the only place I can find Glitch information.

Thanks

G
[Captivate Q&A, Help & Troubleshooting] sixstringsg:
What version are you trying to flash of Glitch?
[Captivate Q&A, Help & Troubleshooting] galakanokis:
Tried the ones from your thread V12B3 (both HL/ML) and V11 (HL/ML). It seems so straight forward I must have something wrong on the phone.
[Captivate Q&A, Help & Troubleshooting] sixstringsg:
If you're on the latest nightly (or close) then V12B3 will work for you. V11 will not.
[Captivate Q&A, Help & Troubleshooting] galakanokis:
Thanks. I am on the stable 7.1 if that makes a difference. I will update to a nightly and try again with V12B3. Looks very cool and interested in trying it out.

Got it working. Problem was PEBKAC (Problem Exist Between Keyboard and Chair) all along. Working great and just playing with tweaks. Thanks to you sixstringsg and the CM guys for all the hard work.
[Captivate Q&A, Help & Troubleshooting] weaktight:
Is everyone's vibrate working? I can't get vibrate on anything except for haptic feedback which makes it kind of useless :(

Also, I'm not able to download MMS.

everything else is working perfectly.
[Captivate Q&A, Help & Troubleshooting] nonameputs:
I am running cm7.1.0. Overall, I love it. Super smooth and reliable. My only problem is with the app drawer for ADW, it's always super choppy. Is there any way to install a different drawer without going to an entire new launcher? Or possibly just boost the scrolling performance of the one it comes with? Why is the ADW drawer so much choppier than any other drawer? This isn't just an issue with cm7 btw, every time I have used ADW the drawer has had a very poor frame rate.
[Captivate Q&A, Help & Troubleshooting] tiuk:
I used to have this problem. I can't remember what fixed it, it was either disabling the wallpaper hack or switching from vertical 4D to vertical new.

Also check your setting for scrolling cache, mine is set to auto.

Sent from Captivate, CM7.1, Glitch.
[Captivate Q&A, Help & Troubleshooting] Mantu13:
I'm trying to develop an App and I prefer to use usb debugging and just run the app on my phone instead of the emulator. However, since changing to CM7, eclipse doesn't seem to recognize my phone to be able to debug on it and it launches in the emulator.
[Captivate Q&A, Help & Troubleshooting] tiuk:
Do you have the nexus a drivers installed? Samsung ones aren't compatible with CM7.

Sent from Captivate, CM7.1, Glitch.
[Captivate Q&A, Help & Troubleshooting] Mantu13:
Installing those drivers never crossed my mind. Thanks a lot. Worked like a Charm.
[Captivate Q&A, Help & Troubleshooting] takerfan:
Hey guys,

I'm running CM7.1 stable on my captivate and I'm having this weird issue with the browser. After having the phone on for a little while and using the web browser just fine..all of a sudden it begins to load pages really slowly and eventually it'll stop loading desktop pages all together. I've tried force closing the browser and trying again, tried several different web sites. And even going from wifi to 3G or vise versa, it's not a problem with the internet connection because other apps work just fine and I even tried running a speedtest and I had sufficient bandwidth with low ping. The only way to resolve it is to reboot and then it'll work for a few hours again.

Any suggestions?
[Captivate Q&A, Help & Troubleshooting] MarkWorsnop:
OK I guess I am dense, but cannot figure this out.

Some of these instructions do not seem to work for me. What am I doing wrong?

1. Start with a rooted Eclair/Froyo running Eclair/Froyo Bootloaders (do not ask us how to do this).

-- I reloaded back to AT&T default, but there is nothing that says what the bootloader is. How am I supposed to put the Froyo BL back on the Captivate?

Install ROMManager Premium.

Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 2.x).

-- There is no CWM installed at this point unless I missed something? If I pick the MTD and 2.x then reboot to recovery the CWM is not there.

Make sure you can reboot into ClockworkMod recovery from ROMManager. Reboot and get back into ROMManager Premium.

--- As I dont know what bootloader I am using I only can guess its not correct. I installed CWM using the Heimdall method and now have the CWM installed.

-- When I finally get to the install zip it goes about 5 seconds into the install and reboots and then goes into a reboot forever mode.

So my guess is the bootloader? I installed Froyo and looks like AT&T default but still cannot install CM.

what did I miss?
[Captivate Q&A, Help & Troubleshooting] RockRatt:
Don't worry about WHAT BOOTLOADERS you have anymore. CM7 works with any of the bootloaders NOW.

What do you see when you boot to recovery? What does it say on top? RECOVERY IS cwm... The only time others have had issues with flashing is IF you still have 3e recovery, that is why I am asking what it says on top.

It sounds like you may now have cwm correctly. IF YOU DO have it working just get into recovery (cwm) WIPE DATA/FACTORY RESET. Once it is done CHOOSE ZIP TO INSTALL. THEN next screen pick the correct zip to install. Let it start flashing. When it is done you should STILL be in cwm recovery. NOW perform the steps again so that you are ACTUALLY flashing it twice before rebooting phone. Next while you are in cwm recovery flash the gapps you downloaded. THEN reboot phone. Once this is done you SHOULD HAVE CM7 working on your phone. If you DO have it working you should be able to use rom manager to download and install from that point on.

Again to refresh, DONT WORRY ABOUT BOOTLOADERS ANYMORE. FLASH THE ROM TWICE and you should be golden. IF you have 3e recovery then look up a post to get the CORRECT CWM and not the 3e recovery one. It is in the captivate forum somewhere, either general or dev section.

Sent From My KICKASS CM7 AT&T SGS2
[Captivate Q&A, Help & Troubleshooting] MarkWorsnop:
OK on the bootloaders, but still doesnt load

I have CWM working. I install from zip and find the CM zip file. It starts installing and then say its verifying "something" like this: "Verifying AAA/BBB". Its only on the screen for a split second and havent been able to read it, yet. Then it reboots itself.

Then its stuck in a reboot loop. Looks like it goes back to CWM and tries to install something (1 second or less) and reboots again.

I am going to try and different reset to factory Boog... http://xdaforums.com/showpost.php?p=17136611&postcount=1

I don't know if this is going to fry it completely or what, but best try I guess.

Last night I put another ROM on the phone, and all is good. But now I am determined to figure out why CM didnt work.
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Boog's Heimdall package in the thread you linked to is what I came to CM from. So, it should work. Be advised that if you're coming from a Samsung file system/ROM (which is what you'll be on if you flash the package from that thread), the CM install package will reboot your phone at least once during the install process and continue. The installer has to reformat and repartition your phone during the installation process because CM uses an entirely different file structure than Samsung does.

So, if you see your phone rebooting during the CM installation...that's normal.
[Captivate Q&A, Help & Troubleshooting] chalee76:
Gingerbread Bootloaders

I installed CM7 yesterday version 7.0.1. My phone had the problem where it won't boot to download unless you use adb. Now with CM7 I can't use adb to get to download mode. I was reading through the forum for a three button fix and came upon this post

http://xdaforums.com/showthread.php?t=812434

I tried designworks 3 button fix using CWM to flash it. This did nothing I'm guessing because o the different file systems on CM7.

Reading through the post it seems that the gingerbread bootloaders fix this problem. If I'm already running CM7 can I flash the bootloaders or do I have to reflash stock froyo then flash the bootloaders. I'm getting a jig for download but still and all I'd like the option of the 3 button boot. Thanks.
[Captivate Q&A, Help & Troubleshooting] FNPonderous:
First Time Flashing Troubles

I am getting 2 different types of errors while trying to flash this ROM using the 2 suggested methods. Any help would be greatly appreciated.

I have a rooted Froyo 2.2 cappy which i upgraded through Kies back when it became available to the public. I was able to flash CLockwork Mod version 2.5.0.4 by following the 3e Recovery Modded w/ No Verification post on these forums.

Problem#1 (Harder Way Method)

I boot into Clockwork Recovery by reinstalling packages in the 3e recovery. I went to a Nandroid backup and got an error that it couldn't mount the sdcard. So i rebooted into recovery a few more times and finally it took and made a backup. Next I wiped and then proceeded to install ROM from internal sdcard and have been getting this error everytime:

E: can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)

(device or resource busy)

E: can't mount SDCARD:update-cm-7.1.0-Captivate-signed.zip

I tried reformatting the internal sdcard through Clockwork Recovery and from my phone and still get the same error.

Problem#2 (Easy Method)

Followed the first few steps and then test to see if I can can reboot into ClockworkMod recovery from ROMManager. The phone boots into 3e recovery and spits out this error:

E: can't open /cache/update.zip

(bad)

Sorry for the long post, trying to be as thorough as possible. I would really like to unleash the beast hidden in my cappy so again any help or direction would be great. Thanks.
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Here's my suggested upgrade method. Not required, but personally I think this is easier than either of the suggested methods from the CM team.

0. If you haven't already, install Titanium Backup from the Market and backup all user apps + system data. You will want this to help put you back in order once you're on CM, because you won't be able to re-install your apps using the Nandroid backup you made from CWM Recovery.

1. Flash a stock Gingerbread ROM, with bootloaders, and with a CWM-enabled kernel.

Ordinarily, I don't advise flashing bootloaders because a screwup could hard-brick your phone. That being said, the likelihood of that happening is extremely small. I also advise doing it once to get to the Captivate GB bootloaders, and then never flashing bootloaders ever again. The Captivate GB bootloaders are backwards compatible with Froyo and can pretty much boot anything.

It also doesn't matter which GB ROM you flash, because you're not going to be using it for anything other than flashing CM.

I assume you're using Windoze, so here's a link to an ODIN 1-Click: UCKI2, from IlluminatedOne (use the link in post #2). Put your phone in download mode (power off completely, hold Vol. Up/Vol. Down and insert the USB cable) to flash.

2. Boot to CWM recovery, flash CM7.

I don't even bother booting the stock GB ROM. If Odin automatically reboots your phone after flashing (I think you can tell it not to), just battery pull. Reboot to CWM with Vol. Up/Vol. Down + Power, release all 3 when you see the AT&T white screen.

You should be fine from there. If it hangs for a bit on "Checking status of BML/MTD", reboots, and possibly hangs a bit there...don't worry, that's normal.
[Captivate Q&A, Help & Troubleshooting] nbell13:
that's all unnecessary. do this.

1. power off phone, pull battery

2. hold both volume buttons, plug in usb cable

3. re-insert battery while still holding volume buttons

i'm on cm 7.1 and this works every time.
[Captivate Q&A, Help & Troubleshooting] FNPonderous:
Actually I am using a mac with VMfusion to run windose 7. Using Odin is another problem I have. I was able to root using windose this way but when I put my phone in download mode odin does not see it.
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Oh goodie, even better! You can use Heimdall! ;)

I only didn't include links to Heimdall because I couldn't find a one-click package right away that included both the bootloaders and the CWM-enabled kernel. So...

1. Go here to get Heimdall.

2. Get the GB bootloaders from here (credit mrhaley30705).

3. Get this stock GB package: UCKH3, no bootloaders, with Boog's CWM-enabled kernel (credit Boog).

4. Flash the GB bootloaders with Heimdall.

D/L mode -> "heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs" from the command line. Or, if you don't want to use the command line, put each of those into the appropriate slot using Heimdall Frontend (available from the Heimdall website as well).

If it reboots, battery pull and go back to download mode.

5. Flash the UCKH3 package with Heimdall.

If you use Heimdall Frontend, it should be easy. Just load the package, don't repartition, and it should handle it for you. If you prefer the command line, extract the contents of the package and flash it manually. The commands should be self explanatory.

You should be able to flash CM7 now.
[Captivate Q&A, Help & Troubleshooting] FNPonderous:
Awesome thanks will try it out later.

IN section 4 you say "If it reboots, battery pull and go back to download mode."

Will it reboot to the ATT screen and then my phone?
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
After flashing, Heimdall might automatically reboot your phone.. When that happens, it will fully boot up unless you stop it (like with a battery pull). There's no harm done if it reboots, but if you just needed to flash again it's faster to just battery pull.
[Captivate Q&A, Help & Troubleshooting] type_2:
Non video files?

Hey everyone,

I just flashed CM7.1 on my Captivate and I love it except for one issue: My video files aren't showing up in the video player nor in any other 3rd party app. It's definitely there as i check the file explorer, but it won't play at all. Anyone have any ideas on how to resolve the issue?
[Captivate Q&A, Help & Troubleshooting] rcllcr:
Flashing New Modem

Hey all,

I am currently running CM7 and I am looking to flash a new modem. I just want to confirm that I would be flashing a i897 based modem and not an i9000, correct?

Thank you.
[Captivate Q&A, Help & Troubleshooting] tiuk:
You can use either.

Sent from Captivate, CM7.1, Glitch.
[Captivate Q&A, Help & Troubleshooting] rcllcr:
Is there a way to see which modem you are currently running?

Also, would you recommend any in particular?
[Captivate Q&A, Help & Troubleshooting] FNPonderous:
Tried to flash the bootloader. I get this: Failed to detect compatible device.
[Captivate Q&A, Help & Troubleshooting] Raikia:
CM7 is working great for me! My only problem is that apparently the vibration for text messages and calls is significantly low. I've messed with the "Haptic Feedback Tweaks", but all that does are button presses (and it does increase/decrease vibrations for those).

Is there a way to increase vibration intensity for calls and texts?
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Well...I can only be of limited help at this point because I don't have a Mac. I did some quick searches, and all I could find was that it may be one of two things:

1. Something about needing "codeless kext", whatever that is; or

2. Apparently there was some mention of some versions of the Froyo bootloaders causing Cappys to not be visible to Macs. This CWM be fixed with new bootloaders, but you may need a Windows or Linux computer to flash them.
[Captivate Q&A, Help & Troubleshooting] hyosungv2s:
hello, I have the 168 nightly rom in my captivate, and I have problems

1. anyone know how I can activate the option of auto answer, because when I ride in my bike, I need answer the call, but I cant with the bluetooth headset, anyone know how activate this funtion.
[Captivate Q&A, Help & Troubleshooting] FNPonderous:
Gonna try using heimdall from another account on my computer and if that doesn't work gonna try using the PC i used to update my phone from 2.1 to 2.2 through KIES. Thanks again for your efforts.
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Any time. Glad I could help. If you can't get it to work on your Mac, I should at least work on a PC. Just make sure you have the appropriate drivers installed for whatever method you choose. I believe Odin needs some "official" drivers to work, whereas Heimdall uses a different set of drivers (I believe you can get them from the Heimdall website). I've heard they're not compatible with one another.

I've also heard that you may need to run either Odin or Heimdall with administrator privileges on Windoze.
[Captivate Q&A, Help & Troubleshooting] weaktight:
Anyone have a problem turning on their phone?

Sometimes I can only turn my phone on if its power adapter is plugged in. (Battery at 68% in the last case)
[Captivate Q&A, Help & Troubleshooting] chalee76:
Still no go. My jig should be in today. Hope that works. So can I flash the GB bootloaders without going back to stock.
[Captivate Q&A, Help & Troubleshooting] apbthe3:
Yes, I would start with a Gingerbread one click and go from there.

---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------

No issues here. You could always flash back to stock to see if it is a hardware issue.
[Captivate Q&A, Help & Troubleshooting] FNPonderous:
Flash was a success. So much easier using your method. Feels like a completely different (better) phone. There are 2 things that I have noticed missing. One is speed dialing but I am gonna try dialer one for that. The other is the TV Out mode setting which looks to not be supported yet.
[Captivate Q&A, Help & Troubleshooting] Gromlakh:
Yes, I believe TV out is not supported, but I've never used it so I didn't notice. For speed dial...I use Go Launcher EX + Go Contacts/Dialer. Go Dialer has its own speed dial settings, so you could always try that. I would assume there are other free dialers you could get that would also include speed dial capabilities if you don't want to use Go Launcher.
[Captivate Q&A, Help & Troubleshooting] ruagun:
cant wait for the devs to use the new source engine hopefully better battery and framework apps
[Captivate Q&A, Help & Troubleshooting] josiuk:
Hi! i have the same problem with motorola Defy CM7.1, the only way that i could use it with WMP 12 (windows 7 64bits) is deleting from sd card all music... then conect again (always in mode SD Card Mass storage) and WMP "read" the device again....

This metodo is not de best.... but works for my...
[Captivate Q&A, Help & Troubleshooting] twoferflinching:
32gb SD-Card

has anyone experienced and issue using a 32gb SD card with this ROM?

i've used MiUi in the past (which is based off of CM7) and had repeated issues with the SD card unmounting or showing up as corrupt....even though it's not.

i've tried multiple kernels and tweaks to no avail...

looking for some feedback before i take the plunge to CM7 ..
[Captivate Q&A, Help & Troubleshooting] FNPonderous:
Would your method work for other phones, like an Atrix?