yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] :
Every rom I flashed today has messed up my home button, it stops working, and no, it's not the i9000 version or kernel. Everything works fine until after I flash everything, I wipe data and cache, and fix permissions, that's when **** hits the fan.

EDIT: Fixed after flashing back to stock, idk what's going on.
[Captivate Android Development] makelegs:
#gremlins...

Sent from my Galaxy Nexus
[Captivate Android Development] :
Sadly, you might be right ;)
[Captivate Android Development] lownox:
Everyone should be running these Kangs. I can now build these from source with cherry picks, but I am too lazy. Undoing cherry picks is still another story. lol
[Captivate Android Development] sixstringsg:
I smell some Ice-cream flavored bacon cooking....

Or would it be bacon flavored Ice-Cream?
[Captivate Android Development] boog:
Does that mean the device trees are out?!?
[Captivate Android Development] JiroPrinz8:
If I've read that somewhere else, that would be gross.. but that's great to hear! Lol!
[Captivate Android Development] killer23d:
New bug on 0215 build - choose wifi network from settings will cause FC on com.android.settings.
[Captivate Android Development] makelegs:
Not seeing that over here, on passion. Can anyone else confirm?

Sent from my Galaxy Nexus
[Captivate Android Development] pkadavid:
Wasn't able to replicate.

---------- Post added at 04:03 PM ---------- Previous post was at 03:59 PM ----------

Btw, also want to say a BIG thanks for the rotated in-call number pad feature in the newest build. That one was huge for me, personally, cause I have my phone horizontally placed in the car and make a lot of calls on the road.

I'm loving these builds and only regret only recently discovering them and the magic of CM.
[Captivate Android Development] RockRatt:
Just tried it here and no issue, can't replicate.

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] sixstringsg:
doesn't boot

CM9 kang. No idea if it boots, who wants to try it?
[Captivate Android Development] makelegs:
I'm jelly... ;)

Sent from my Galaxy Nexus
[Captivate Android Development] RockRatt:
I will give it a try when i come back from lunch and get my cappy. What is different than THS CM9 or CDA CM9? Just your own cherry picks?

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] sixstringsg:
It doesn't boot, I had already edited my post. And are you talking about CNA? because CNA is a hacky port at the moment on the SGS devices.
[Captivate Android Development] RockRatt:
Okay i vuess i didnt see the doesnt boot part. Thanks for letting me know before i downloaded it.

Yes I was talking about CNA dont know why i ty autocorrected to cda. What is wacky about it? I ha e tried it and it seems pretty good so far. As smooth as CM9 but has some extra options in it. So I am curious what is wacky? I did ask in the thread about it to see what is/was different than CM9. Is it not using a ICS kernel? Or is it something else? Inquiring minds would like to know. I do frequently switch between CM7, CM9, and have tried CNA. Thanks your insite would be very much appreciated.

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] Nick D:
Anyone having issues with the latest version? I was running the previous version with Glitch 13.1 installed and tried to update cm7 this morning. I installed the kang and then glitch and it kept hanging at the glitch splash. I restored a nandroid and left it at that. Now I'm home and trying again. I installed the kang and it sits at the cm splash. I installed again and it sits again. I've wiped cache and dalvik but no dice. Any words of wisdom?
[Captivate Android Development] makelegs:
Kill it with fire!!!! ;)

Sent from my Galaxy Nexus
[Captivate Android Development] sixstringsg:
Not CNA, but the SGS port. It is not built from source, its hacked together from different places. I'm not bashing the work they did, just saying that it neither clean, nor specifically built for your phone.
[Captivate Android Development] Cor-master:
It's good to be back! Loved these builds but figured since official gb was out I'd try some of those builds for a while. After experiencing nothing but headaches I've come back to these builds and on gb bootloaders, the rom runs like it's on crack! The ics animations are a nice touch. This is great work and I think I'm sticking with it till you start making CM9 kangs!
[Captivate Android Development] makelegs:
They always come back... ;)

Hopefully a cm9 branch merge is in the near future. I'm pretty bored with cm7, honestly...

Sent from my Galaxy Nexus
[Captivate Android Development] sixstringsg:
http://goo.gl/Fg5lj

Booting CM9 KANG ^^

No cherry picks, but is newer than build 16.

Edit: thanks to boog for figuring out our issue!
[Captivate Android Development] :
Is there any difference between this and build 16, or is it just built more recently?
[Captivate Android Development] sixstringsg:
Being built more recently automatically means changes. CM is changed at least daily, often hourly. Mostly, it's just a step in the right direction, because that is the first kang that has been compiled. Now I can start to work on porting AOKP and CodenameAndroid properly.
[Captivate Android Development] :
I completely understand, I was just wondering what the changes were. This is awesome as AOKP is the most beautiful thing ever!
[Captivate Android Development] boog:
'tis a good day to compile!
[Captivate Android Development] sixstringsg:
Honestly, I don't specifically know.

Yeah it is!

PS: I edited my post :)
[Captivate Android Development] :
Well anyways, thanks to anyone who worked on it :D
[Captivate Android Development] killer23d:
I am using Glitch 13.1 and I removed apps like Cyanbread, Androdian, CMWallpaper, ADW, all the LiveWallpapers.... the phone used to work without them and now it just force quit.

I tested with 0218 built as well.. Same thing. Since I am traveling, I will try to use stock kernel when I get home.
[Captivate Android Development] makelegs:
I don't recommend axing adw. Never hurts to have a stock launcher installed...on the off chance that your 3rd party launcher goes missing. Just a thought...

Sent from my Galaxy Nexus
[Captivate Android Development] Cor-master:
I usually do ax adw just because I have ex, no problems so far
[Captivate Android Development] bearnakedbrew:
Can I come over from Fusion ICS without formatting? Obviously factory reset. Your version of CM9 that is.
[Captivate Android Development] sixstringsg:
Should be able to, yes.
[Captivate Android Development] sixstringsg:
New kang: no idea if it boots

http://goo-inside.me/devs/glitch/CM9_Kangs/Vibrant
[Captivate Android Development] raz123:
Cool.

Though this seems like a Vibrant build, and the build in the Captivate folder is only 7kb.

Previous Kang broke rebooting to recovery.

Thankfully, 3-button combo still works.
[Captivate Android Development] billyjed:
Did you mean to post the vibrant link here?
[Captivate Android Development] RockRatt:
I am guessing it should have been this link? http://goo-inside.me/devs/glitch/CM9_Kangs/Captivate

Just flashed from the link I put above and it booted up and I am using it now.

Sent from My KickAss CM7 Captivate
[Captivate Android Development] dave1977nj:
so http://goo-inside.me/devs/glitch/CM9_Kangs/Captivate

is the latest kang nightly builds for CM9 right?

Also is there a place to see the changelog for this?

Thank You!!!
[Captivate Android Development] sixstringsg:
Oops, yes that was supposed to be in the Vibrant thread, but yea goo-inside.me will have the latest builds for cappy too.
[Captivate Android Development] Malorkus:
Do the CM9 kangs have the default volume media and bluetooth GPS patches? Those are the only things keeping me on Gingerbread now I think..
[Captivate Android Development] sixstringsg:
Unlikely.
[Captivate Android Development] boog:
You might have to format /system first. Make a nandroid backup!
[Captivate Android Development] Cor-master:
Alright first issue I've found with my cm7 installation, when I try to connect to an open wifi network, settings force close. I didn't use tb to restore settings I let Google sync do all that. Didn't notice the issue at home because it connected automatically to my network there. Possible solutions?

Edit: noticed someone else is having the issue with the 2-15 build, I'll flash the newest build when I get home, see if it helps
[Captivate Android Development] Cor-master:
Found a workaround for now, wifi manager, free from the market
[Captivate Android Development] makelegs:
Please report back with new build. There have been mixed results with the wifi pick. I almost dropped it.

Sent from my Galaxy Nexus
[Captivate Android Development] Cor-master:
Will do, I get off work in 2 hours I'll look into it
[Captivate Android Development] wickedninjalo:
i cant get any gps signal whatsoever on this cm9 build and ive tried everything. any ideas would appreciated thx
[Captivate Android Development] Cor-master:
Just flashed the newest build, and unfortunately no dice on the wifi, settings force closes when attempting to connect to a new network. I'll just make due with wifi manager for now
[Captivate Android Development] sixstringsg:
When posting, you need to post what version you are running. "Newest build" is first of all time relative. A new build could come out right after you post. Also, we have both CM7 and CM9 ROMs here right now.
[Captivate Android Development] Cor-master:
OK sorry, it's the cm7.1 2/19 build
[Captivate Android Development] bearnakedbrew:
Rom runs perfect with Glitch ICS. Did not format. Some app specific closes but that's it. Thanks for another good release!
[Captivate Android Development] Cor-master:
so you went straight from 7.1 to 9?
[Captivate Android Development] wickedninjalo:
Just my extra input on the cm9 version. Wifi and everything else works perfectly for me, just no GPS at all.
[Captivate Android Development] sixstringsg:
GPS won't work with stock kernel, FaultException hasn't gotten around to fixing it yet. It should work with Glitch though.

Edit, oops. Wrong thread. I'll look into the GPS issue I was thinking Vibrant.
[Captivate Android Development] Raul77:
sixstringsg : is there a change log? i am just wondering how much is the CM9 kang different from Build 16 ? and if i decide go with CM9 KANG, i should use Glitch or GPS will NOT work? (unlike Build 16 that GPS works with stock kernel)

Thanks,
[Captivate Android Development] sixstringsg:
Github.com/cyanogenmod changelog.

As for GPS, read my edit above.
[Captivate Android Development] Cor-master:
GPS is so gawd awful on our phones anyway i often forget we have it!
[Captivate Android Development] sixstringsg:
+2000

10char
[Captivate Android Development] Raul77:
hmm perhaps its the phone? i have been using it since day 1 with no problem really, what is the major issue you got with it?
[Captivate Android Development] bearnakedbrew:
I came from Fusion ics. The themes got to be too much. Really nice rom though.
[Captivate Android Development] boog:
Anyone feel brave?

Wanna try my initial working kang of getting Codename Android over to the cappy?

looks like the lockscreen isn't working, not sure what else....make a backup, might possibly need a wipe. Remember, this is a wip, probably not a daily driver.

http://dl.dropbox.com/u/33609688/cna/full_captivatemtd-ota-eng.boog.zip
[Captivate Android Development] mcdroid:
Downloading now.....
[Captivate Android Development] wickedninjalo:
Thx looking forward to your ideas
[Captivate Android Development] mcdroid:
When the rom first loaded there is a red border that flashes around the screen. Keeps popping up randomly when going to menus and hitting apps.

I did a backup and a full wipe before installing....

Since it is running my phone is running pretty hot (actually decided to shut it off). I have not install Gapps yet so i did not get any tools to test from the market.

Wifi working.

Camera takes pictures and video records but when trying to hit back or home it stops responding and have to force close.

Update:

Letting the phone cool off (yup, that hot!)

Gonna restore back to sixstrings kang for the moment and will test further tom. Need to call the wife...hah
[Captivate Android Development] sixstringsg:
The red borders are because it's a debug build, they won't always be there.
[Captivate Android Development] boog:
seems the home button isn't working
[Captivate Android Development] bearnakedbrew:
Having SOD issues, gonna reflash for stock kernel. Otherwise still good.
[Captivate Android Development] lownox:
Well, after running these KANGS for a while... I built one. If you don't know how to flash these... learn. :)

LINK EXPIRED

Thanks to sixstringsg, makelegs, Boog, cyanogenmod team/contributors... etc... etc... etc... existz, zachmd, and others... etc... etc... etc... oh and y3tt3r. (I know I spelled that wrong).

This is build includes only one cherry-pick... otherwise it is a straight CM7 build. Normally I run Glitch kernel 13.1... but I figured what the hell. :D

captivatemtd: Update prebuilt kernel

Revert "Apply increased mmc drive strength to Captivate as well (user feedback)"

Change-Id: I60968c0088c27c17fc5b0da5dcc78229e920beaf
[Captivate Android Development] Cor-master:
well it'll pinpoint my location fairly well, and it's handy for finding things around me, ie banks, restaurants, bars etc, but the turn by turn is worthless. Granted yeah its come along way, but basically it won't stay locked on my location. It'll have my location jump around, I'll get "GPS signal lost " etc, typical captivate issues really, mine is no exception, it's my understanding it has something to do with the way the GPS is integrated in the soc and we can tweak it and get it to work better but underneath it all its a hardware issue and no software will ever completely fix it.
[Captivate Android Development] Phoenix-Lead:
One thing that works for some is by bending the pin under the back cover. By bending it up you get a more firm contact with the phone case which is used to help with the signal. It is worth a try. It worked on one of my many Captivates.
[Captivate Android Development] apbthe3:
I can confirm this as well with the 2/15 CM7 build.

I don't know if it is related to the wifi pick or not, but I am also having an issue where I lose connectivity when I go from wifi to mobile data. It's weird, some things seem to work (like the browser, Speed Test, GMail push, and Foursquare push notifications), others (the actual Foursquare app, Facebook, and BeWeather) don't. Toggling airplane mode usually (but not always) seems to fix it. It started about the time that the wifi pick was added in, but I don't know if they are actually related.

I have had issues in the past of losing all connectivity when I turn off wifi while connected, which I believe is a known issue. This is a different problem though.
[Captivate Android Development] Cor-master:
I actually have been having that issue too. Oddly my web browser will always work, but other things won't such as the xda app. Usually turning on flight mode fixes it. Here's the kicker though, I've had this issue ever since I reverted to stock froyo and ran Kies to upgrade to kk4. Bootloader issue perhaps?

It's actually gotten alot better since I went back to cm7, on kk4 roms flight mode did nothing I had to reboot, one of the many reasons I gave up on kk4
[Captivate Android Development] apbthe3:
Glad to know I'm not completely insane. I don't think I have ever had KK4 on my phone, I've been on CM7 for as long as I can remember, with the exception of a brief voyage into CM9. I flashed back to CM7 in January (I used the 1/28 build I believe) and I don't remember having the issues then. They seem to have started when I updated sometime in February. I'm on glitch, but it seems to happen with the stock kernel as well. I haven't downgraded because I keep hoping it will get fixed with an update (and because the swipe notification bar lockup is really, really annoying and has been fixed since January).

I am on GB bootloaders, but have been for many months so that doesn't seem to have been a trigger for me.

---------- Post added at 08:42 PM ---------- Previous post was at 08:08 PM ----------

Although now that you mention it, I flashed back to KK4 to get from CM9 to CM7. And I used Weatherbug initially after flashing back but stopped using it because it would "randomly" stop working, which now that I think of it was probably this exact issue. As much as it pains me, maybe I'll go back to 2.1 and flash from there to see if it resolves it.
[Captivate Android Development] Cor-master:
Yeah I've been debating reflashing bootloaders myself to see if it helps, I know I've had all kinds of problems since I updated, though at this point my phone is rocking the latest cm7 kang and running ultra stable so it might be worth just living with the issue for myself
[Captivate Android Development] apbthe3:
I understand completely. It kills me to wipe again, but I'm back and forth with wifi all day every day so it's driving me absolutely nuts. I don't think it's the bootloaders, I've been on GB bootloaders for at least 5 months and the issue just started for me. It has to be something else. What else it could be, since it repartitions and therefore should wipe everything, I don't know.

I'll let you know how it goes.
[Captivate Android Development] apbthe3:
Still have our intermittent internet issue after flashing to stock or with going back to the 1/29 build.

I'm frustrated. Anyone have any ideas for us to try?
[Captivate Android Development] Cor-master:
I seem to have the issue at work more often than at home, i'm wondering if it's network related

Edit: hey did you restore everything with titanium backup? I did and for instance the xda app, I uninstalled it and reinstalled from the market and it's worked alot better since
[Captivate Android Development] Cor-master:
BTW I just flashed the CM7 9/22 build, still having the wifi settings issue. Force closes when attempting to connect to a new network that isn't already remembered.
[Captivate Android Development] apbthe3:
I only install the programs that I need the user data from. Oddly enough, none of those give me any issues. I have uninstalled an reinstalled all of the offending apps with no change. I flashed back to stock and to reflash CM7 from scratch and, although I only played with it for a minute, I'm pretty sure I recreated it there. I flashed back to a completely fresh install of CM7, toggled the wifi once, boom, no data.

So today, I decided to take a new approach. I one clicked back to eclair, bootloaders and all, everything worked fine. Then I updated with kies mini (gag) with the official updates. Everything works perfectly on KK4.

Which brings us back to your original suspicion of it being bootloader related. I dismissed it last night, but I'm starting to think that you're on to something. The only thing that changed between last night and today was that I flashed bootloaders today, something I haven't done since I originally went to Gingerbread (KB1 I believe, it could have been anything, but it definitely wasn't KK4).

What are the chances that KK4 uses different bootloaders than the other GB ROMs, and running it on old bootloaders monkeys something up?

---------- Post added at 09:09 PM ---------- Previous post was at 09:08 PM ----------

I also had this issue on that build.
[Captivate Android Development] lownox:
KANG for this evening...

Cherry-picks are... updated stock kernel, option to change over-scroll glow color, and prepare for CM 7.2 RC1.

LINK EXPIRED
[Captivate Android Development] Mike S.:
Music Apps "Forget" where Music directory is

This is an interesting issue that I haven't seen discussed here.

My current setup:

Captivate

Mod Version: CyanogenMod-7.2.0-RC1-Captivate-KANG (via makelegs 2/09/12)

Kernel: 2.6.35.13_Glitch-V13.1-REL-Captivate+

Using 32Gb SD Card mounted in /emmc

Music directory: /emmc/Music

So what happens is every couple of days or so my music apps (Music Player and Amazon MP3 player) lose sight of the Music directory. I'll open the app and nothing is there.

The fix is to unmount /emmc via Settings - Storage and then remount. It works okay again after that, until the next time.

I verified that the same behavior occurs if I change CyanogenMod Setting - Application to "Use internal storage" and placing the Music directory within /sdcard (essentially swapping how external storage is mounted.)

Any ideas? Or anything else I can do to help troubleshoot?
[Captivate Android Development] makelegs:
Lots of devices have had issues with 32gb sdcard performance. Have you tried to reformat the card lately, and then compare reliability? (just the first thought that came to mind)

Sent from my Galaxy Nexus
[Captivate Android Development] Mike S.:
No, I haven't done that. And it could be related. I know that when I was on the stable CM7, before your Kang, I did not have the issue at all. But that could be coincidental.
[Captivate Android Development] lownox:
Here is a clean CM7.2 RC0 KANG build with no cherry-picks. This was built as of about 18:16 EST today.

LINK EXPIRED

Fruit-filled build coming later this evening. :D

And... here it is.

CM7.2-RC1 KANG with the following cherry-picks.

+Added option to lock Action Buttons in main dock

+cm: Prepare for 7.2.0-RC1

+Fix battery charging detection in NotificationManagerService

+update pre-built kernel captivatemtd

+settings for custom over-scroll glow color

LINK EXPIRED
[Captivate Android Development] Cor-master:
Just flashed the 2/25 build of Makeleggs cm7.2 kang and still having the same wifi issue.
[Captivate Android Development] lownox:
Clean KANG for today... no cherry picks. I will pick fruit tomorrow. Today was SO busy. Trying to finish my son's Eagle project with him... and we finished this afternoon.

LINK EXPIRED

CM7 FTW!!! I just can't get into CM9 just yet. :(
[Captivate Android Development] thangphysk48:
Any CM7 Kang without wifi problem, or gapps process problem. I've try Makeleggs build, but having issue, so I'm back to CM7 nightly, but they stopped at build 181.
[Captivate Android Development] anishz:
Did you try the one above your post, it is also kang by lownox without any special picks.
[Captivate Android Development] Nick D:
So this is basically a clean cut nightly, just not actually a nightly because they don't do that anymore?
[Captivate Android Development] thangphysk48:
I've try, but unfortunately, Wifi cannot obtain IP address.
[Captivate Android Development] Nick D:
Perhaps download to PC, move to phone via usb and flash from recovery?
[Captivate Android Development] thangphysk48:
Sorry for give you complex infor, I mean that I've flash that build, then use wifi, but my phone cannot get IP address. Then I'm back to cm- nightly 181, my phone's wifi work.

I don't know why, and I wonder there's some problem with cm7.2 code (??)
[Captivate Android Development] anishz:
Yes that's right, but as i read in the cm blog, they have setup their servers and the nightlies for cm7 will be back. But i think major development will happen in cm9 and it will be available soon for our device (hopeful):).

EDIT: Just saw that nightly for 26th (today) has been posted, but i am getting 403 forbidden error. Will try later.
[Captivate Android Development] Cor-master:
Mines doing this too, and I don't have a 32GB sd card, have a 16GB class 4 Kingston. Mainly noticed with my notifications sounds.
[Captivate Android Development] lownox:
If stuff isn't working... try wiping data. If you have been flashing KANGS over KANGS for a while, I have also had apps freak out and not seem like they will use data/wifi. Wiping data fixes this for me.

Anyhow, here is another straight build from around noon today. No cherry picks.

LINK EXPIRED

I am not lazy. I installed a garage door opener today, so I had no time to pick fruit. :D