yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] boog:
That was way too easy! Why was I making it so hard? lol
[Captivate Android Development] makelegs:
I like EASY!

Sent from my Galaxy Nexus
[Captivate Android Development] mnjm9b:
Lol... aside from the git/https fiasco....I must have nuked the repo like 4 times... but kept using the same local backup vendor repo without even thinking that changes were made there too...

It helps to actually read what is going on in the gerrit merges...lol
[Captivate Android Development] makelegs:
Look out!!!....

.....this build just got a lil bit SKANKIER!!!
[Captivate Android Development] anishz:


Thanks, the holo rings look cool.

Anybody here has the note, i was planning on getting it but the size worries me about day-to-day use.
[Captivate Android Development] Gromlakh:
Dude, I just flashed like three hours ago. YOU ARE NOT HELPING MY FLASHING ADDICTION!!!

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] makelegs:
#firstworldproblems

Sent from my Galaxy Nexus
[Captivate Android Development] Gromlakh:
#thisisnottwitter
[Captivate Android Development] makelegs:
#crackflasher!!!

Sent from my Galaxy Nexus
[Captivate Android Development] Gromlakh:
#icanstopanytimeiwanttwitchtwitch
[Captivate Android Development] lownox:
Nothing like a Bacon sandwich on a fine morning. THANKS!!!!!!!!
[Captivate Android Development] makelegs:
Can anyone comment on the perceived value of the BLN pick? Does this actually help anyone who might be running a kernel without BLN?

EDIT:

NVM.... I don't think I even got it in there correctly, and it looks like the frameworks part is jacked up, so I'm gonna leave it alone.
[Captivate Android Development] fatbas202:
I would love it if the LED notifications worked in the current KANG builds though. Glitch 13.1 has support for LED notifications, but it looks like the ROM is missing the setting to actually turn it on in the Device Settings (at least that's where it is on CM7 on my wife's SGS2). If it's convenient to add that then it would be cool. Either way, thanks a ton for building these ROMs.

Of course I could be an idiot and cannot figure out how to turn it on too, so someone please correct me if that's the case...
[Captivate Android Development] makelegs:
Turns out I need 2 picks, not 1, and one of them had issues merging, previously. I'll try again, tomorrow. It's not a pick that really matters to me, but I know the sgs folks seem to like it.

Sent from my Galaxy Nexus
[Captivate Android Development] apbthe3:
I haven't tried the latest KANG, but they work on the one before that both with the stock kernel and with Glitch 13.1. Settings / CM Settings / Interface / LED notifications. If you want them on for everything, just click on "Unconfigured" and pick "Use Application Settings." There are also overrides in the profiles, but if you didn't play with them before you won't need to change anything in there.

The settings are a bit quirky and vague, but with a little experimenting I got them working right. If you get stuck send me a PM and I'll help you if I can.
[Captivate Android Development] yguns76:
The KANG builds really add nice features to CM7. I like how the TV out is added. I have not noticed the new features added in the OP but I will look for it again.

__________________

Phone: Samsung Captivate i896

Carrier: ROGERS

ROM: Cyanogenmod 7 Nightly

Modem: JL3
[Captivate Android Development] mcala:
My leds work thru call settings/led.
[Captivate Android Development] JiroPrinz8:
How's the latest build guys? I see a 01/16 in there..
[Captivate Android Development] RichMD:
I loaded the 01/14 build yesterday and it is working great. I like having the MIUI bar back with custom colors, etc. I had BT issues with the 01/04 build but everything seems to work perfectly on 01/14. I don't know why but my GPS is even working better than it has in a long time (with KC1 modem in CT). Call clarity is good as well. I have made a nandroid backup and I don't plan to update anything until ICS becomes stable. Thanks for all the hard work. :D
[Captivate Android Development] makelegs:
If your **** is working that well...then these builds clearly ain't skanky enuff!!! :eek:

:D
[Captivate Android Development] skyxliner:
No problems so far. Better and better.

Sent from my SGH-I897
[Captivate Android Development] anishz:
Makelegs, your "will brick your phone'' warning doesn't seem to work :p.

More than 3000 downloads :eek: for 1/13 build.
[Captivate Android Development] makelegs:
I know, right??!!

Who are all those people and where did they come from??

Sent from my Galaxy Nexus
[Captivate Android Development] tbrummell:
Agreed. People always ask me when I'm going to upgrade my hardware, I ask them why? My skanky Captivate out performs your stock Galaxy Nexus, and costs alot less I tell them! LoL

I'm to the point where my Captivate really can't get much more stable, as posted above, everything is working excellent (BT to 3 devices (2 cars and a headset), WIFI tether, and whatever else). I think it's time to Nandroid this thing and call it final (could I really kick the flash addiction?). Well, until ICS is as stable as this skanky build is.

Thanks Makelegs for all of the hard work, you sir, ROCK!
[Captivate Android Development] anishz:
True, i was also planning on upgrading to galaxy nexus, but when i tried build of ICS cm9, it was very smooth and fast. Waiting for it to become more stable, and then use it as my daily driver.
[Captivate Android Development] swimomatic:
Now I apologize if I'm wrong but now that At&t has officially released gingerbread for the captivate, does this mean that the source code has been released? Meaning that the lack of proper "sleep mode" that has haunted cm7 battery life since before the nightlies can finally be remedied?
[Captivate Android Development] Time_Zone:
Are you sure this has not already been fixed? I flip flop between CM7, KK4, and i9000 ROMS quite frequently and battery life is pretty much the same.
[Captivate Android Development] Cor-master:
I can testify battery life is same as stock.
[Captivate Android Development] swimomatic:
What have you done to get that good of battery life? I flashed back to original 2.1, then flashed cwm, flashed cm7 latest nightly and wiped the dalvik cache but still am not experiencing anywhere near the same level of battery. Perhaps if I flashed KK4 then flashed CM7 again this might help? Any help in the direction of better battery life would be awesome.
[Captivate Android Development] Time_Zone:
I notice poorer battery life on 2.1 bootloaders. Not sure why. Also am using Glitch kernel.
[Captivate Android Development] mcala:
How bout you start with a fresh battery like a new $10.00 Anker instead of all this flashing this and that. Not all batteries are equal! Try a new battery if it's older than 7 months.
[Captivate Android Development] RichMD:
To clarify a bit, the difference between stock and CM7 for quite a while has been dependent on how heavy your usage is. A heavy user could see better life on CM7 but if the phone sits idle most of the time then you could go for days on stock but not CM7 because they didn't have driver source code to be able to put certain components to sleep. If that has changed, I'd be surprised - at least up until Samsung released source a little while ago - but even the I didn't think driver source was included.
[Captivate Android Development] JiroPrinz8:
It's really just on how you use it, if you want CM7 performance then you'd have to compensate, i use my phone heavily for everything, i decided to.go back to CM7 simply because of its smoothness, so i have an extra battery, and i rarely.go anywhere where i can't charge, i.always have a car charger or a wall charger with me. I do like 3 cycles.a day.
[Captivate Android Development] makelegs:
ORLY???

....just gonna leave this right here
[Captivate Android Development] swimomatic:
Yeah I've replaced the battery and have 2 spares. Just will stick with that. Thought maybe the source code was waiting for att release but it's fine.

After switching back and forth a million times to satisfy my flashing frenzy I always come back to cm7. It's the best!
[Captivate Android Development] fatbas202:
From a couple of pages back, but updated so it will show up in search.

I could not get LED Notifications to work on CM7 with Glitch 13.1, though their kernel supports it. I reflashed to the stock kernel and now LED Notifications work great. Not sure what is going on, but BLN didn't work on my phone with Glitch 13.0 either. Likely a one-off, but may affect someone else too.

Thanks for the help apbthe3!
[Captivate Android Development] Phoenix-Lead:
Forget about it
[Captivate Android Development] Time_Zone:
BLN works on glitch. Just does not use the method employed by the BLN application. If using glitch, remove BLN app and you'll see the leds light up every time you get a new message.
[Captivate Android Development] fatbas202:
On 13 or 13.1? 13 uses BLN and 13.1 uses CM7 LED Notifications. I cannot get LED notifications to work at all with 13.1 even with BLN control removed. Weird.
[Captivate Android Development] Time_Zone:
13.1. I get emails from gmail, touchdown exchange, voicemails. Every time the leds light up for me. I'm even OC'd to 1300 mhz.
[Captivate Android Development] RockRatt:
Have you set up which items you want to get notifications from?

(I think it is the same but could be in a different location on the cappy)

Menu, settings, cyanogenmod settings, interface, led notifications, unconfigured.

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] mcala:
Have you tried settings/call settings/led notification?
[Captivate Android Development] boog:
Anyone want to try building your own kang? I modified the cyanogenmod wiki directions. https://sites.google.com/site/jasonmossbarger/how-to-kang-captivate

original directions http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Compile_CyanogenMod_(Linux)

Not a huge modification, but will hopefully help someone.

Now does anyone want to do a how to on cherry picking?

EDIT:moved my how to over to google sites.
[Captivate Android Development] anishz:
Thank you for the simplification! It helps. How to on cherry picking would be great.
[Captivate Android Development] fatbas202:
Yep, configured both of those things and they work great on the stock kernel, just not on Glitch 13.1. I know that the devs said that they couldn't figure out why BLN worked perfectly on their phones but not on others, so maybe it's some type of variation in the hardware that I've got. I do know that I got my Cappy in the first month that it was available and I'm sure that Samsung has made some slight hardware revisions since (or my phone is just broken). Anyhow, thank you guys very much for your suggestions!
[Captivate Android Development] mcala:
For ****s & googles mine is a 1012 version & it works.
[Captivate Android Development] RockRatt:
Mine is a 1007 so it is an older model also, i sometimes switch back to cm7 when i want to test out the kang builds but i have it running ICS at this time. It is my backup/messing with phone since my sgs2 is my primary pjone now. I also have my daugbters phone running on cm7 without this issue. Try flashing the update again ON TOP of ypur build WITHOUT wipong anything (with the stock kernel first). Then freeze the bln app on your phone or back it up with tibu and uninstall it after. Then flash the glitch kernel and test it out. I havent used glitch in quite a while so i am not sure how the led notifications or bln with the app are suppose to work now. But i have seen that if i had an issue after a flash of a nightly and something didnt work correctly i will just reflash the update again and be back to everything working. Good luck

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] boog:
Interesting. it works just fine on my xubuntu 11.10

boog@boog-900HA:~$ sudo apt-get install sun-java6-jdk
Reading package lists... Done
Building dependency tree
Reading state information... Done
sun-java6-jdk is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

What distro are you running?
[Captivate Android Development] RichMD:
It is a fresh install (yesterday) of Ubuntu 11.10 in VirtualBox. It probably is something I didn't do, etc since I plan to fumble my way through this to learn linux and some development. I already tried sync'ing the repo but I don't think it finished. Do you have any suggestions for a "dummies guide" for this since I have to look up what each of these parameters mean?

Anyway, I just tried again and this is what I get:

rich@HP-Ubuntu:~$ sudo add-apt-repository "deb http://archive.canonical.com/ oneiric partner"

[sudo] password for rich:

rich@HP-Ubuntu:~$ sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool

Reading package lists... Done

Building dependency tree

Reading state information... Done

Package sun-java6-jdk is not available, but is referred to by another package.

This may mean that the package is missing, has been obsoleted, or

is only available from another source

W: Duplicate sources.list entry http://archive.canonical.com/ oneiric/partner i386 Packages (/var/lib/apt/lists/archive.canonical.com_dists_oneiric_partner_binary-i386_Packages)

W: Duplicate sources.list entry http://archive.canonical.com/ oneiric/partner i386 Packages (/var/lib/apt/lists/archive.canonical.com_dists_oneiric_partner_binary-i386_Packages)

W: You may want to run apt-get update to correct these problems

E: Package 'sun-java6-jdk' has no installation candidate

rich@HP-Ubuntu:~$

Sorry if this is off-topic a bit but it is about learning how to make our own Kang build... :)
[Captivate Android Development] mcala:
I could have sworn that sun-jdk was removed from Ubuntu repos. You have to go directly to the Java website & download the jdk. An easier way is to install the openjdk from the repos. It works fine plus open source alternative to Java.
[Captivate Android Development] boog:
It gave you the direction in it's output :D

Run

sudo apt-get update

then try again.

I updated my page to add the apt-get update

We all had to start somewhere. Once you get the hang of apt, it will come easier.
[Captivate Android Development] boog:
It is in the partner repository.
[Captivate Android Development] mcala:
Never tried the partner repo. I'm satisfied with the OpenJDK from Ubuntu restricted extras. Thanks Boog for your updates to the wiki. I want to try building but it takes way too long to sync the repo. Is there a way just to sync for captivatemtd? It took almost an hour doing it's updates for phones I don't care about before I canceled it!
[Captivate Android Development] boog:
After your initial repo sync, it will be faster to update, just the initial takes forever.

But, we did a test that appears to work.

if you open your ~/android/system in nautilus and press Ctrl+h (to show hidden files) open .repo then manifests folders.

make a backup of your default.xml, then open default.xml in gedit (text editor) then you can remove the lines of devices that you don't want,

eg: <project path="device/commtiva/z71" name="CyanogenMod/android_device_commtiva_z71" />

If your not sure about one, leave it! If in doubt, don't!

Don't delete device/common, or any of the other stuff in there, just the unwanted devices. If things fail, you can restore your backup.
[Captivate Android Development] makelegs:
CCL Hack...

Ok, guys....this is a little hacky, but here goes.

I updated POST #2 to include a link to a mostly barebones build that has custom carrier label (CCL) fully in tact. As it stands, now, the current build allows existing CCL's to be maintained without the ability to change/enable/disable the function. The settings part conflicts badly with both MIUI battery and Skank Style rings. So....instead of squashing 2 to achieve 1.....or 1 to achieve 2....I chose to include the frameworks aspect of CCL, so that existing settings could remain in use without having to kill MIUI or Skank Style.

Long story short....if your CCL is already working, and you are happy with it, then do nothing. However, if you do not currently have it in use, or wish to change the label somehow, then you can flash the hack build, set the label, and then update to the current build.
[Captivate Android Development] rocketcuse:
How to download

I started using CM71 nightlies. it was suggested to use KANG builds. I have been looking at this thread and thought I was ready to move to KANG builds..

I click the link to the site..I see the zip files available for the Captivate, but when I click on the zip file, it won't download.

Are the zip files not like Nightlies where you download them and copy to phone and run recovery to install?

sorry new to the KANG.
[Captivate Android Development] anishz:
it's working fine for me, just downloaded the 26/1 build.
[Captivate Android Development] apbthe3:
Maybe the site was just down for a minute, it seems to be working now. You are correct, they install just like any other nightly.
[Captivate Android Development] Gromlakh:
I had some issues with the site as well a couple of weeks ago. It's the new php system makelegs is using for downloads on the site. It may be more or less fixed now.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] belyle:
I just installed the 1/26 full build. I'm getting force close of status bar on the first unlockafter a reboot. Sometimes if I go into cyanogen mod settings, the status bar will relaunch. I'm also getting constant notification that my sd card is being scanned for errors.

I tried clearing cache, dalvik, rebooting, reinstalling the ROM. No dice.

Had to revert back to earlier Kang to get the status bar to behave. Sd card notification went away, too.
[Captivate Android Development] RockRatt:
+1 had the same issue. Wiped all data three times and reinstalled still same problem. Thiz was a phone being flashed for the first time to cm7 from stock( my daughters new cappy). Next I tried just going to advanced a clear dalvich and reinstall the kang. Ended up going back to a known good one she had on her old cappy before it was stolen. No issues on a older kang build.

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] pkadavid:
+1

Same thing here. Status bar completely disappeared for me after the first FC and hasn't come back. Tried fixing permissions and reflashing the build without luck.
[Captivate Android Development] rocketcuse:
Site is working now for me thanks!
[Captivate Android Development] phlunkie:
status bar force close

I had the same problem with the status bar. tried permission fix, cache wipes. Had to roll back.
[Captivate Android Development] makelegs:
New build should run nicely. Had to drop transparent bar, for now.

Sent from my Galaxy Nexus
[Captivate Android Development] phlunkie:
Sooooo far so good on new build.
[Captivate Android Development] RichMD:
I see that "should work" is listed for the custom color battery bar. Can anyone confirm? I was going to flash 1/26 but saw all the problems and waited but will flash 1/27 if the custom color battery bar works. I like customization options :)
[Captivate Android Development] makelegs:
I would be shocked if it didn't work, but have no way to confirm other than you #crackflashers' reports. Nobody has weighed in yet, though.

edit: wait just a bit. Gonna build with transparent bar fixed.

Sent from my Galaxy Nexus
[Captivate Android Development] apbthe3:
It works for me. Flash away!
[Captivate Android Development] belyle:
This is a really stupid question, but I haven't figgured it out yet: how do I change the battery color?
[Captivate Android Development] apbthe3:
There are no stupid questions! Alright, that is certainly not true, but yours isn't one :)

If you use the battery bar, you can change the color in settings / cm settings / status interface / status bar tweaks, under battery bar color.

If you use a regular icon, the color can only be changed by changing themes in Theme Chooser.

And to answer the next obvious question, the reason there is a choice for the battery bar and not for the icon is that themes generally don't theme the battery bar because it's not an official CM thing, so you end up with a bar that doesn't match your theme.
[Captivate Android Development] apbthe3:
Alright, my turn for a stupid question: I went to the dark side for a month or so (CM9) before coming back to the light. I'm on the newest KANG which, unsurprisingly, is still amazing. Now that I'm back, my volume rockers are back to controlling my ringers. I know there were some issues getting it to work at one point but I'm pretty sure it was working beautifully when I left. Is there a toggle that I'm missing somewhere?

Also, I see you added a transparent status bar mod. Is that theme specific? Mine still seems to be the normal level of non-transparency.

Now that the curiousity has passed, I'll be here for the foreseeable future. Thanks for all of the hard work, it really shows :D

Edit: I should mention that I'm using Glitch 13.1, which very well may be the cause, I honestly don't know.
[Captivate Android Development] simple man:
@ apbthe3 go to cyanogen mod settings-input-volume-rocker wake.
[Captivate Android Development] apbthe3:
I'm sorry, I was very unclear. I was asking about the default volume control controlling the media volume instead of the ringer.

Thank you, though. Your answer was the correct answer for what I wrote, but it wasn't what I meant.
[Captivate Android Development] makelegs:
IIRC....go to settings> sounds> volume...(or something like that; not cm settings)...and there should be a checkbox for default media......

Sent from my Galaxy Nexus
[Captivate Android Development] apbthe3:
That's where I remembered it too, but I don't see it. I checked on a friend's phone with the stock kernel also, but no luck. It's no biggie, just curious if I was missing something obvious.

Thanks again!
[Captivate Android Development] makelegs:
Sooooo.....anywho.....I'm pretty sure the reason you can't find it, is because the settings commit isn't in the build. It's one of those that used to get picked, but started conflicting, so I dropped it. Guess I forgot to drop it from the pick list. #falseadvertising

The frameworks part was merged, but the CMParts wasn't, for some reason. So if you had it working, it prolly would still work. But if you didn't, or wiped your phone, there's prolly no way to even turn it on. Sorry for the confusion. I'll try to add it back in for next build. Not sure exactly when that'll be, though.

Sent from my Galaxy Nexus
[Captivate Android Development] apbthe3:
Thanks for looking into it, glad to know I'm not just going crazy. It's really not a big deal to me at all, I was just curious.

I'm just glad to be back!
[Captivate Android Development] ldmelo:
I am running the latest version, 0127-2215. Everything is fantastic, great rom!

However I would like to report that the clock on the status bar sometimes shows wrong values. It seems to take some time to get updated, specially after waking up the phone, while the clock app shows the correct value.
[Captivate Android Development] makelegs:
I'm definitely gonna need more than just 1 report of that issue from folks. Transparent status bar messes with clock orientation, so that would be a prime suspect. But if that's the worst problem we got..... ;)

Sent from my Galaxy Nexus
[Captivate Android Development] ldmelo:
Yeah, everything else is working fine.

Something I noticed is that changing the orientation of the phone will update the clock on the status bar.

Screenshot attached.
[Captivate Android Development] makelegs:
FC fix... (disable lockscreen)

New build includes the FC fix, along with all the usual extras. I remembered to dig back up the settings pick for default media volume. Now you should be able to actually turn it on again. :)

As before...had to manually resolve the transparent status bar pick, due to MIUI batt. Seemed to work fine on the last build, but lemme know if it has ceased.