yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RootTheMachine:
I screwed up my external SD messing with partitions the other day, and when I put it in the phone, it said it was damaged and needed formatting. Instead of formatting the external SD, it formatted the internal one... just a heads up.
[Captivate Android Development] CheesyNutz:
looks like some hefty changing coming on the next nightly
[Captivate Android Development] Strugs:
Where is this 'changelog' you speak of?
[Captivate Android Development] LBCaptivate:
The list has been growing for the past few days. I think a lot of the changes are already in the latest nightly. Nightlies are coming out every day but the changes log dates have not changed in almost a week.
[Captivate Android Development] nimper:
There were some changes made to the build process so it's possible that the changelog site is not aware of the way things are done now. It's pulling in the changes from gerrit but it's not updating when the buildbot spits out new builds.
[Captivate Android Development] johnhazelwood:
Because the other changelog wasn't being updated, I've been using this one:

http://changelog.bbqdroid.org/#captivatemtd/cm9/next

Hopefully it's accurate.

---------- Post added at 01:01 AM ---------- Previous post was at 12:59 AM ----------

I noticed my bars go from blue to gray frequently on the more current builds (June builds) and I reverted back to 5/28 which seems to be better. Is this the wifi bug everyone is talking about? or is what I'm experience something else? I'll reflash and try again with a newer build if what I was experiencing wasn't the bug.
[Captivate Android Development] Katze Pavilion:
Has someone compared pictures quality from phone's camera between stock rom and CM9? :)
[Captivate Android Development] shane87:
The reason for the changelog not showing the more recent builds is due to the way the cm update packages are named. There was a change just before the builds stopped showing up that changed the build names from "update-cm-9--NIGHTLY-captivatemtd-signed.zip" to "cm-9--NIGHTLY-captivatemtd.zip". Because of this change, the changelog script is not seeing the newer builds. I have opened an issue on the github source for the changelog script, but I have not heard anything about an update to the changelog site.

[EDIT]I just checked on the github for the cm changelog script, and someone is working on fixing the code to pull in the builds wth the new build names.[/EDIT]
[Captivate Android Development] Katze Pavilion:
Hey guys! I found that the sim card inserted on the phone it made the wifi issues. Remove sim card before flashing new build and you never meet wifi issues. :)

/I was wrong :( Remove sim card just help me not to meet the wifi issues on first boot, after a reboot, I meet it again. So sad because after all of my try, the wifi issues still follow me.

/Semaphore kernel is good. No wifi issues any more.
[Captivate Android Development] nkrick:
This bug is clearly documented in the Known Issues link from the OP as bugs 3 & 4 (located here: http://teamhacksung.org/wiki/index.php/Experimental:GT-I9000:Known_issues ). Ignore the fact that it says GT-I9000. The i9000 and i897 share the same code base and the bugs are the same (though some are not applicable to the i897, such as the RM radio bug).
[Captivate Android Development] ap1618:
does volume+ work as expected on CM9?
[Captivate Android Development] boog:
To turn the volume up? Yes. Not sure what else you would expect out of it. :confused:
[Captivate Android Development] nkrick:
LOL!

I think he is probably referring to the Volume+ app (which I have never used): https://play.google.com/store/apps/...51bGwsMSwyLDEsImNvbS5URVNULmFuZHJvaWQubHZoIl0.

CM includes DSP Equalizer which I think does much of the same thing that Volume+ does, but it is free & included.
[Captivate Android Development] CheesyNutz:
Newest nightly and no troubles
[Captivate Android Development] Udonitron:
I keep getting an error 7 when trying to install the latest CM9 onto my I897 from 2.3.3 (rooted etc).

Any ideas?
[Captivate Android Development] daskanda:
Nvm......
[Captivate Android Development] sa1yan:
Everything working awesome here.

Sent from an Ice Captivate Sandwich.
[Captivate Android Development] Udonitron:
Thanks?
[Captivate Android Development] daskanda:
You gotta use the search button dude, status 7 error has been discussed many times.... You can probably google it and find your answer in alot of threads
[Captivate Android Development] CheesyNutz:
search its been talked about
[Captivate Android Development] rocketcuse:
Dumb app questions

I know we all have our favorite apps and like them included into CM9 builds. Would there be any issues if I removed some of those apps via something such as Root Explore?

Example... Apollo Music player? I don't care for it and prefer the music player I am currently using. I would like to remove that and some other non ICS (framework) apps to free up storage space.
[Captivate Android Development] nok6100:
Just freeze them with Titanium Backup, in case you need them back for some reason, works great for me. :)
[Captivate Android Development] truckmann:
I've been having some serious battery drain and a possible memory leak with the latest nightlies. Currently on 2012/06/15 version. I'm maybe getting 8-9 hours out of a charge with minimal use and I'm having to restart a lot. It keeps getting a really bad lag and apps start hanging up. I guess I'll try going back to an older version and see if it helps. This sucks.
[Captivate Android Development] nok6100:
I have had pretty darn good battery life with cm-9-20120612-NIGHTLY-captivatemtd combined with Devil3_0.72_cappy_CFS_BLN_CMC_20120610 kernel. About 1% per hour on standby, about 10% (maybe a little more) with screen on while gaming or surfing the web, with a 1800 MAh Epic battery. Of course, your mileage will vary, I have a pretty light setup, not much running in the background.

Last night I tried out the latest CM9 and newer Devil .76 kernel and noticed higher battery drain (2%-3% per hour standby), so I went back to the setup that I first mentioned. Nandroid backups are a life saver, lol. :D
[Captivate Android Development] StickFigs:
If I try to use any of the nightlies past version 'cm-9-20120609-NIGHTLY-captivatemtd' I get a bug where wifi will constantly toggle on and off and on and off by it's self. Happens on a fresh wipe install too.

It MIGHT not happen on the first 20120610 build because I haven't tried it but it did happen on the second 20120610 build and up to the newest build as of the time of this post too.
[Captivate Android Development] CheesyNutz:
welcome to beta testing 101
[Captivate Android Development] bitnerd:
StickFigs -

Yeah, I have the same problem. Tried wiping, removing all known wireless connections, anything I could think of but it didn't help once the wireless gets to that state. I just went back to an older version.
[Captivate Android Development] Katze Pavilion:
Many people here have the same problem. I don't know why and how to solve it, but if you use a 3rd-party kernel such as Semaphore or Glitch, you will not meet wifi issues. But to use BLN feature on 3rd-party kernel, you need NStool or BLNtool.
[Captivate Android Development] Primus76:
Odd. I put glitch on to use the 90 vol script since my audio was really low on line out/headset and handset but I still have my softkeys light with not on notifications. no bln app on board.
[Captivate Android Development] melvinaury:
You can also try Devil Kernel.
[Captivate Android Development] sf777cop:
I had same problem (no ring volume) and tried same fixes, nothing. then found blue icon in settings Volume Control that fixed problem. now low and clear
[Captivate Android Development] CptTwinkie:
If 3rd party kernels fix the wifi issues then my question is was the cm kernel updated at the time when the wifi issues first started?

Sent from my CM9 Captivate
[Captivate Android Development] thehyecircus:
I installed this ROM, and when I click the Android it says ""Unfortunately, Setup Wizard has stopped". Any help?
[Captivate Android Development] Gromlakh:
The wifi issue is almost certainly not kernel related. For every three people that say they have it there are ten who don't. If it was kernel related we'd all be suffering, and I for one am not.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] mcnutty:
Wifi is very much kernel related, and it is possible that changes there could affect some and not others. Just like with processors where some run better at certain voltages than others, wifi chips can have better tolerance for sleep/wake commands and other such stuff.
[Captivate Android Development] BumRush:
Hey, I'm having some trouble with the toggles in some of the apps and in the browser. I am referring to the ones on websites such as Facebook where you would check off "remember me" or something like that. The entire box is missing so I cannot toggle anything. Is there a way to fix this?
[Captivate Android Development] Primus76:
OK you two. You know the rules. I want a clean fight. Keep it above the belt and out if the corners!

*ding* round 1, FIGHT!
[Captivate Android Development] RootTheMachine:
I feel like it's not kernel, since I can achieve the same effect by modding the framework.
[Captivate Android Development] VirtualNobody:
Same issues here. I had rock solid service with 05/07. Moved upto 06/06 and WiFi started sucking. Now on 06/15 and WiFi and battery suck.

I think someone posted that 05/27 was the last good build?
[Captivate Android Development] Katze Pavilion:
Too many people have problem with wifi. Hoping the dev guys fix it soon.

05/28 and the first 05/29 (there was two 05/29 builds) are the builds which I never meet problem with wifi, but it now not available on CyanogenMod Downloads. I'll upload them and share for everyone who need.

Update: here is the link for 2012/05/28 build

As I said, there was two 05/29 builds, I call it "the first" and "the second" as the time it released. So "the second" 05/29 is the first build that I meet wifi issues. I've tried all the later builds after 05/29 and I met wifi issues with all of them. Back to "the first" 05/29 (or earlier builds) and the wifi issues gone! I've tried Semaphore kernel with some recent builds and I don't meet wifi issues. So I think problem is from the stock kernel.
[Captivate Android Development] SkyboneNoya:
Yeah, same here. Those builds exactly for me also. Wifi issue. I go and flash the devil kernel (link in sig) and wifi works fine! I don't know if its kernel related or not but this fixed things for me.
[Captivate Android Development] VirtualNobody:
Going back to earlier builds?

Can I go back to an earlier CM build by just flashing?

Or do I have to follow the procedure of doing a Nandroid restore from the current rev, then once I'm back at the old rev, restore that backup again?
[Captivate Android Development] Katze Pavilion:
Just wipe cache and flash it normally.
[Captivate Android Development] CheesyNutz:
wifi worked perfectly fine for me on Cm9 newest nightly
[Captivate Android Development] lordxentris:
hmm... you got to flash an ICS kernel compatible with CM9 such as Devil3 / Semaphore / IcyGlitch and then install CM9 (via recovery of course). Have Fun!!! :)
[Captivate Android Development] ap1618:
I havent dared to venture beyond the 5/26 nightly.

Given all the issues, I guess I will stay put until news of any fixes are out. :)

thanks.
[Captivate Android Development] ScottyNuttz:
I'm not having wifi issues on the latest builds, but I can't connect to Foursquare for the life of me. It sucks, I was in a fierce battle for mayorship and now I'm finished.
[Captivate Android Development] jerkysh:
I don't know what you're dreaming guys, but i'm always running the latest nightly, and never had issues! Even if i encounter issues, i backup my apps(they're backed up everyday) and do a clean flash (wipe data/factory reset, wipe cache and dalvik cache). Now running the latest + the Devil kernel , wickedly fast! I'm not even thinking of an update to the GS3! I think i'll wait for the next Nexus! And the Nexus Tab ^_^
[Captivate Android Development] Katze Pavilion:
Every phone look like the same, but each of them can work different from the others. The issues can appear to some people but not to some others. We all have tried to flash by many ways and hoping the issues can be solved but unlucky it keeps stuck. We don't dream and imagine about the issues.
[Captivate Android Development] nimper:
I was having problems too but it looks like there was a change merged in the recent builds that addressed the issue.

http://review.cyanogenmod.com/#/c/17773/
[Captivate Android Development] VirtualNobody:
Stick a fork in it...This ROM is done?

After 3 weeks of WiFi and battery drain issues, I went back to 05/28.

There seems to be little traffic in this thread lately. My guess is the devs have rightfully moved on from this 2 year old phone.

My S3 is arriving Thursday and my Cappy will be given to the kid...
[Captivate Android Development] truckmann:
I've luckily not had any wifi problems, but my earlier problems with the apparent memory leak and battery life have been working much better on the 6/18 nightly. Still using the stock Kernel.
[Captivate Android Development] zmore:
FWIW, the latest nightly (6/19) has fixed the WiFi issue (for me) in the last dozen-odd nightlies that required an extra reboot to fix. WiFi was finally working after the post-flash first-boot.

Ditto. I just have to train my toddler to only steal my Cappy off my desk and NOT the shiny new S3 that'll be "hidden" behind it. :)

I've had a good 22-month run with my Captivate: Stock Touchpiz Eclair 2.1 -> Cognition 2.2 -> CM7 2.3, and finally CM9 4.0, but it's time to move on (since every month you don't upgrade on a subsidized carrier is money down the drain).

I donated a few bucks to the TeamHacksung S3 devphones fundraiser to help get that kickstarted and they've already met their $1K-something goal. The i9300 experimental cm9 rom is already out, and Samsung just released the AT&T & T-Mobile source, so CM9 for the U.S. variants shoud soon follow...
[Captivate Android Development] VirtualNobody:
Sounds like I was having a different WiFi issue. My WiFi was working fine, except that once in a while I would pick up the phone and the WiFi icon would be grey instead of blue. In order to get it to reconnect, I'd have to toggle WiFi on and off. I didn't have any WiFi issues for the 30 days I ran 05/07 build.

Where can I donate for the SIII work? I'm guessing the SIII is going to be my last Samsung phone. Hopefully Google will get Motorola to make an awesome phone with a pure Google experience within the next couple of years. Samsung makes awesome hardware, but I'm sick and tired of waiting for updates. My Tab 7 plus and 8.9 still don't have ICS, yet I can buy a $60 tablet from Alibaba that has ICS on it.
[Captivate Android Development] Tsaukpaetra:
I was having odd issues with wifi as well, almost any communication would cause the driver to hang up, while other times it would be almost fine.

I went back to the 5/28 nightly and came back, and all is well? Dunno if it was a bad build somewhere, but I'm tentatively saying it's resolved for now.

Sent from my SGH-I897
[Captivate Android Development] Katze Pavilion:
On the latest nightly, I don't meet the wifi stuck on/off issues, but everytime I turn of and turn on the wifi again, it can't find any access point in range.
[Captivate Android Development] whipps:
Devil kernel

Well, I just flashed the Devil 3 kernel and now I can't get past boot image. Can't even get into CWM. :mad:

Now what? Any ideas . . .

Now I can't get in to download mode.
[Captivate Android Development] Katze Pavilion:
Using UCKK4 Odin one Click package. If the computer can detect your phone (by a yellow COM even though you can't go to download mode) you still can flash and back to stock 2.3.5.
[Captivate Android Development] whipps:
No luck. I got into download mode, but the computer/Odin wont see phone. It wants to install "Gadget Serial". What the hell is that

I'm sooooo screwed, because I need my for for work.
[Captivate Android Development] takeoutttt:
You can try flashing a KK4 stock ROM (zip file) on CWM
[Captivate Android Development] gstern:
Not sure that would work- different partition layout.
[Captivate Android Development] boog:
It is the device that odin can see to flash from download mode. You'll need to install the drivers. I haven't done it on windows in a long time (heimdall "just works" on linux).
[Captivate Android Development] whipps:
Computer has the right drivers, but still nothing. It's like the phone doesn't even know who it is any more.

MobileTechVideo.com here I come.
[Captivate Android Development] johnhazelwood:
If it's trying to install the serial drivers, you probably don't have the right drivers. Try plugging into a different USB port, or re-install the generic Galaxy drivers that support CM (the Captivate drivers don't).

Have you been using CM for a while, or just flash recently? Also make sure you are holding down the volume up/down and try connecting to USB instead of using the power button. I'd suggest a jig, but figure you probably don't have one handy or you would have used it already.

In the FAQ about 5 down is a link to the drivers, try them along with Odin. http://teamhacksung.org/wiki/index.php/Experimental:GT-I9000:Frequently_Asked_Questions
[Captivate Android Development] whiteguypl:
Pull phone battery, Reboot pc, open Odin, plug in USB, hold volume buttons, reinsert phone battery.
[Captivate Android Development] SkyboneNoya:
this kernel? http://xdaforums.com/showthread.php?t=1642460

follow the OP and it should work! I just bought voodoo sound and running the latest vd Devil3_0.79 kernel

I guess if you don't have kk4 bootloaders and cm9 installed, that might cause an issue. Try and flash the kernel again if boot loop?

Other than that I'm sure its been stated, go and odin back to kk4.

For odin I sometimes I have to pull the battery and switch usb ports after restarting my computer for it to be recognized. Even installed the samsung drivers again. Be sure your on 32 or 64bit.
[Captivate Android Development] Katze Pavilion:
Ahhhh! Why why why! Everything so far so good until the 05/29 build but after that is worse than ever. Wifi issues, FC and reboot suddenly. I'm dropped from heaven to the hell. Now using stock 2.3.5 and live with lags. :sad:
[Captivate Android Development] nok6100:
I just flashed the 6-20 build, saw the wifi issues I have been reading about, so I wiped and reflashed 6-20, then flashed devil kernel build .72 and everything works fantastic :) Good battery life too.

So I suggest that you flash 6-20 again and then flash devil kernel .72 and give it another shot so you don't have to deal with ginger.
[Captivate Android Development] whipps:
THANK YOU!!

I would have never thought it was the drivers for Nexus.

Odin can now see my phone. One step closer to getting my phone back up and running.

Going to try the FixRecovery.tar right now.

Thank you Thank you Thank you

Well, the FixRecovery didn't work, but I found Semaphore ICS kernel in a tar file.

I'm back in business.
[Captivate Android Development] VirtualNobody:
So to try and fix my WiFi issues, I flashed back to 05/28. Still had WiFi issues, and now had Cell modem issues as well! Flashed back to 05/07 which I knew was stable for me, and same issues. ARGH!

So I wiped data/factory reset and did a Nandroid restore to the 05/07 backup I had made 6 weeks ago. Restore went fine, but the phone would never complete booting...The boot animation continued forever.

What did I do wrong?

So finally gave up, did a factory reset, flashed 05/07, TiBu restore on my apps+data and the phone is running great again! Battery life seems a lot better and WiFi and Cell are stable.

For those that are having issues, why not just go back to a mid May build and be done with it? I really saw no changes from 05/07 through to 06/18 when I gave up.

I'll stick with what's working. Kid gets the phone when my SIII arrives anyway, and she's not going to care if it's the latest CM9 nightly or not.
[Captivate Android Development] shane87:
I have ran 06/03, 06/07, 06/10 and 06/11(what I'm on now) and I have had zero issues with WiFi, cell data, fc's, or random reboots. The only issue that I have seen is the inability to send or receive mms. When I receive mms, it tries to download (sometimes for hours) then I get a message saying "failed to download <unknown subject> from Unknown Sender". When I try to send an mms message, the stock mms app crashes after I select the picture. If I use Handcent SMS, it simply dumps me back into the conversation log without attaching the image. I'm not sure how long this has been going on, as mms is a feature that I rarely use. However, since I noticed it sometime in May, I have checked it on every nightly that I download, and it is still broken!

Also, I know mms did work back on the cm9 alphas, as I used one of the earlier alpha builds, I think 13 or 14, to send a screenshot showing that I had android 4.0.
[Captivate Android Development] thangphysk48:
I've got alot of issue when upgrade rom, ex: lost baseband, lost imei, lost signal.

Then I do some step with rom from 01-06

1. Back to stock by using Odin.

2. Flash Talon kernel.

3. Wipe all

4. Flash rom. Phone will be reboot (1) to install new recovery, then it will install new rom. When progress complete, phone will be auto reboot (2), PLEASE TAKE OUT BATTERY, it very necessary.

5. Boot to recovery, wipe all again, then, install gapps. If not, you'll got alot of problem, I'm sure that.

6. Reboot your phone.

Simple THANK if you think it help solve your problem with new cm9 build.
[Captivate Android Development] johnhazelwood:
I've noticed the only way my restore works is to install new ROM and do an Advanced Restore of the data partition only.
[Captivate Android Development] nok6100:
Throught the CWM "mounts and storage" menu you can try to select mount data, and then mount datadata and then you should be able to do a nandroid restore as usual. I noticed data and datadata are not mounted by default.
[Captivate Android Development] Fallon:
I updated a weekish ago before checking on the latest info. Was greeted with 2-3 hours of battery.

The 6-19 build brought things back to normal all day battery life however.
[Captivate Android Development] jerkysh:
updated to the latest 24/06 and everything's great, except the hold back button to kill app, i have to keep it for about 2-3 second until it kills the app..before this i had to hold it for about half a second/a second...
[Captivate Android Development] SkyboneNoya:
Ah, it works at least. I thought the feature was gone!
[Captivate Android Development] shane87:
Yeah, they adjusted the timeout for the back-button-kill-app feature to two seconds instead of the default value. I'm glad, because I keep that option enabled, and with the default value I would sometimes kill an app when I just meant to back out of the on screen keyboard.
[Captivate Android Development] jerkysh:
is there any way to edit that time? i liked how it was before :(

edit i did a quick search and found that in the next nightly there will be this option, to set the time, via a app , source
[Captivate Android Development] shane87:
I'm glad they are putting that option in. Until they add the option to change it from an app, the only way to change it is to modify the source and build your own.
[Captivate Android Development] ap1618:
one way is to flash a kernel with init.d support (glitch is an example), and edit the 90call_vol script located in /etc/init.d. that will boost both earpiece and speaker phone in-call volume. (NOT media or alarm or anything else)

---------- Post added at 05:31 AM ---------- Previous post was at 05:30 AM ----------

BTW so all the wifi and other problems are fixed now in the latest nightlies?

(I havent gone beyond 5/16)
[Captivate Android Development] vileladelima:
So, i was lookin at bbq log an i was curious...

The cm9 for captivate yil have a RC1?

Thanks!