yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] neo_31591:
i guess all the problems are resolved....the Wifi issue is pretty random, quite surprising but its actually random..... first i flashed the latest nightly on my capy, got the wifi issue, using the same steps i flashed it on my friends capy, no wifi issue,

Again, i flashed my capy, again following the same steps, no wifi issue...so i mean if u get the wifi issue, just flash it again.... lol...
[Captivate Android Development] vileladelima:
I've flashed the devil kernel, with vodoosound and the volume off phone has a increse , tahat you can mannage using the vodoo app in the google play ,market.

Is very godd!

I thiunk you can try!

:laugh:
[Captivate Android Development] Katze Pavilion:
Thank Godness! Wifi issues has gone!
[Captivate Android Development] ap1618:
I dont remember where, I saw somewhere that flashing the Devil 3 kernel bricked someone's phone... BC :eek:

BC = be careful ...
[Captivate Android Development] melvinaury:
The only way to brick the phone is with a bad installation of bootloader.
[Captivate Android Development] ap1618:
found it:

http://xdaforums.com/showpost.php?p=27638065&postcount=1092
[Captivate Android Development] b-eock:
Thats not a brick if an Odin/heimdall flash can fix it...
[Captivate Android Development] flxdms:
Any zip file you flash has a chance of bricking your phone. It has nothing to do with Devil in particular.
[Captivate Android Development] daskanda:
Lol thats not a brick.... Its a boot loop lol.... A zip flash from cwm can't brick your phone lol
[Captivate Android Development] jerkysh:
i updated to the latest nightly and didn't see any way to adjust the back button kill app time, is there anyone that has managed to do/find it?
[Captivate Android Development] sa1yan:
Correction, there used to be a flashable zip that would fix the 3 button combo on phones that didn't have it on froyo. Flashing that overwrites bootloaders and could brick your phone...

Just saying :). I haven't seen any recent zips that flash bootloaders so yea for the most part, you can't hard brick by flashing a zip..
[Captivate Android Development] shane87:
Judging by the changelog, they have added the framework side of the customizeable timeout. Now they need to add the option into the settings app. Most options have to be implemented in multiple parts: one part to enable the option, and one part to allow the user to change the option.
[Captivate Android Development] jerkysh:
that sucks, i really hate to wait 2 seconds to kill an app!
[Captivate Android Development] shaker2k:
thanks for the short post! It only took me 1 second to read it.
[Captivate Android Development] wavemaster00:
Wow!

Bought an old Captivate for one of the kids and decided to put CM9 on it. For maximum effect I let her play with Android 2.2 for a few days, so I would look good for making her phone go fast.

She was already complaining that the phone was really slow compared with the Galaxy S2 she uses from her mother.

Just got done putting CM9 on there. Wow. This thing is fast. She is going to be really impressed. As am I.

Applause!
[Captivate Android Development] Gromlakh:
That was an Odin package, not CWM. You can't flash bootloaders via CWM, only Odin/Heimdall.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] comdei:
Anyone having trouble where ICS kicks my email off the phone because I logged in on my computer?
[Captivate Android Development] vileladelima:
Realise Candidate

It's true that the Captivate will have an RC of the CM9?

I've saw that the SGS II already have one!

Realised yesterday.

Thanks!
[Captivate Android Development] nkrick:
Looking at the jenkins logs, it appears that CM9 RC1 tried to build for the Captivate but failed due to a missing resource for "config_backKillTimeout" http://jenkins.cyanogenmod.com/view/All/job/android/3486/console

Hopefully they resolve the missing resource and we get a CM9 RC1 build soon.
[Captivate Android Development] lavero.burgos:
Wait patiently...

http://get.cm/

~ V
[Captivate Android Development] comdei:
Seriously this is annoying lol.

Every time I open my email on my PC it says that my email password has changed on my phone.

Any ideas?
[Captivate Android Development] lownox:
I changed it to 1400ms... much better. 2 seconds was driving me nuts too.
[Captivate Android Development] b0uncyfr0:
Any news on CM9 RC1? Im just about to try ICS for the first time and i saw that R9 is released. Maybe ill wait till it arrives for the old Cappy.
[Captivate Android Development] Primus76:
Anyone having issues with bln after the 25th build? I have none now.
[Captivate Android Development] ap1618:
can someone confirm that all the issues are gone away with the latest nightly?

(i like to venture beyond 5/16) thanks!
[Captivate Android Development] thanhtd1995:
I wondering why each day have a new rom, something new??
[Captivate Android Development] nkrick:
There is no reason to wait for the RC. Flash the latest nightly and when the RC is released, flash it. Flashing CM on top of CM does not wipe anything except for the caches, so there is no extra work involved. The "exception" to this is that everything that is part of the mainline CM build is included, so if you use TiBU to remove a part of CM, it will come back when you flash a new build, or if you use a 3rd party kernel, you will go back to the THS/CM kernel when you flash a new build.
[Captivate Android Development] jerkysh:
my phone doesn't get past the bootanimation after flashing the latest nightly, and i noticed that the .zip is a little bit smaller than previous
[Captivate Android Development] nkrick:
Generally yes, though you won't always notice anything new. Userdebug builds (nightlies) for CM are built every single night. These builds are primarily for the developers so they can test new functions and/or bugfixes they have implemented without having to build it themselves on their own machine. Since CM builds nightlies for each device, they allow all of us to run them and do our own testing, however, there is no official bug reporting allowed for the nightlies since they are not stable builds. You can find the changelog to see what has changed in each nightly for each device here: http://changelog.bbqdroid.org/

edit: it appears that the changlog is not getting updates since May 24th.
[Captivate Android Development] poprocksncoke:
Flashed the ROM last night for the first time, still poking around a bit but for the life of me I cant figure out how to get swype to work?
[Captivate Android Development] LBCaptivate:
Swype is not in this Rom. You have to dowload Swype beta.
[Captivate Android Development] shane87:
The BBQLog app shows updates for the 25th, 26th, and 27th.

[EDIT]I checked the website, and it doesn't show the nightly builds on the 26th or 27th. Very odd, since the app pulls the info from the same place, and, presumably uses the same functions to track the builds and which updates are in which build. I sense a disturbance in the force! Lol.[/EDIT]
[Captivate Android Development] nkrick:
I think they have their cache meta tags setup wrong. I had to do a Ctrl + F5 to get the page to refresh.
[Captivate Android Development] ap1618:
did anyone flash 6/29 nightly? any issues?
[Captivate Android Development] jerkysh:
i did, and didn't encounter any issue :)
[Captivate Android Development] Euzhan:
No issues for now :-)
[Captivate Android Development] Primus76:
My bln isn't working on my captivate any longer even though the settings say enabled. I installed bln control and it says the mod isn't installed. Anyone else having issues?

Edit. I put glitch on and it now works with the bln control test but not for email app. At least bln control says it is now enabled. Any ideas why not in cm9 stock?
[Captivate Android Development] nkrick:
Search the thread for BLN and/or LED Notifications. You'll find a previous post that I made that should answer your questions.

Since BLN is a third party app and Glitch is a third party kernel, if you have any problems with either, you should ask them elsewhere (like in the Glitch thread).
[Captivate Android Development] RootTheMachine:
I wouldn't bother with the app either

Sent from my SGH-I897
[Captivate Android Development] b0uncyfr0:
Im about to flash 6/29. Been a few days now and im very impressed with cynagenmod. It runs a bit faster than KK4 too. Only down side would be the battery, its draining faster than i expected it to.

Ive done the usual stuff like disable GPS and data. Are there any other things i can do to improve the battery life?
[Captivate Android Development] pixbuf:
I couldn't be happier with the battery life. After unplugging it in the morning, it's on for 16 hours. When I plug it in again at bed time the battery is generally at about 40 %. I do keep my screen pretty dim, though.
[Captivate Android Development] Primus76:
I will scan the thread again. Was just saying that the built-in light notification wasn't working any longer with the kernal that comes with the nightlies. Without third party kernal or app it worked perfect up until a couple flashes ago. The only way I could make it work again was with 3rd party.

Was just wondering if anyone else's was broke now.

I was just trying glitch and bln app to make sure the function still worked and it wasn't my phone. No questions regarding those here, just wondering if anyone else is having probs with the built in since I prefer to stay stock cm9.

Edit: OK I guess the better question is if led notification is broke. I always thought bln was "back light notification" and not "blink". My apologies for being confusing. So yeah the led notify doesn't work any longer even though it says enabled. Should I wipe and try again or anyone else having the problem?

Edit 2: went back to 20th and led worked fine. Went to 30th and no luck.
[Captivate Android Development] skyxliner:
It's only you.
[Captivate Android Development] Lertets:
I'm having the same issue with bln

Edit: also on June 29 nightlies stock kernel
[Captivate Android Development] RootTheMachine:
I see there was a change made to LED Notification in the 6/27 nightly. Perhaps it broke things.
[Captivate Android Development] shane87:
To the best of my knowledge, that change shouldn't have affected us. That change was in android_hardware_samsung, which contains hardware code for the exynos4 chipset. The captivate runs the hummingbird chipset, not exynos4. Exynos4 was introduced with the sgsii.
[Captivate Android Development] RootTheMachine:
Pretty sure this setting doesn't exist yet... in regards to the back button app kill timeout.
[Captivate Android Development] jerkysh:
He's a KANGer, he makes KANGs , i'm pretty sure he can make that.
[Captivate Android Development] ap1618:
anyone having slightly worse battery life with 6/29 or later?
[Captivate Android Development] nkrick:
BLN is "Back Light Notifications" and it is a specific solution to make the LED lights for the buttons light up and/or blink. BLN is not a part of CyanogenMod though due to the behavior of the application (as described in my previous post). Instead, CyanogenMod modified their existing LED Notifications to be able to be used for the button LEDs for the SGS phones (which do not have a notification LED). The BLN application requires kernel support, so it will not work on the THS/CM kernel. There are other 3rd party kernels that use BLN instead of LED Notifications. For those kernels, you must install the BLN application.

Too many people use BLN and LED notifications interchangeably, but they are completely different solutions and different implementations. Since this thread is only for CM9 with the included THS/CM kernel, there should be no discussion of BLN on this thread. BLN discussions belong in the threads of the 3rd party kernels.

The apparent problem with LED notifications does (of course) belong here, but we all need to use the correct terminology in order to not cause any confusion.
[Captivate Android Development] Primus76:
Yeah the wide spread use of "bln" is similar to saying Kleenex for any brand of tissue. Although it sounds backwards since led notification makes it sound like I should have an led present similar to a blackberry as opposed to "back lighting" my captivates "soft keys".

Either way you say it though, the darn buttons don't light anymore :).
[Captivate Android Development] ap1618:
flashed the latest nightly, and it reboots at the "android is upgrading" screen!! :eek:
[Captivate Android Development] Snorchblapp:
Flashed the latest nightly, coming from the 0524 build. All I can say is, WHOA WHOA WHOA! Slow down.

This thing was fast before, but jeez, now its a bullet. Vere nice job!! :good:

EDIT: LED notification is working on the 0703 build. Awesome job to all Devs! :D
[Captivate Android Development] ap1618:
dear experts, Im on latest nightly, stock kernel now (before it was Devil).

I have undesirable battery drain... Dont want to wipe the whole thing. SO, what if I flash the latest nightly on itself? would that address anything?
[Captivate Android Development] igorgomez:
Does anyone know if this update fixed the wifi issue? I'm on 26/05 version and I haven't the wifi issue. Only rare reboots and low storage. Aside from that, the system is running smooth!
[Captivate Android Development] ap1618:
yes I believe it has. Im not seeing any wifi issues...
[Captivate Android Development] ThreeofNine:
I'm on the 20120701 nightly and this morning I had 64% battery left (with 10-12 phone calls and email, Google+, Twitter, and Weatherbug updates every 15 minutes) after 25 hours!
[Captivate Android Development] ap1618:
you must tell us your secrets!
[Captivate Android Development] Snorchblapp:
Are you flashing everyday? I'm not sure if anybody else has experienced this, but whenever I flash it seems like my battery life takes a hit for the next 2-3 days. Afterwards, its either the same or better than before.

It's as if Android settles down and gets back into the groove of things. If you're flashing everyday, it could be as simple as that.
[Captivate Android Development] ap1618:
i do not flash everyday, but this time how went was like this...

I was on 5/16 nightly. forever. then updated on 6/29. crappy battery life. then updated again to 7/3. last night.

so i may not have stayed long enough to see battery life improve perhaps?!
[Captivate Android Development] Primus76:
Still broke for me. Went to 0703 and nothing. Went to 0625 and nothing but went back to 0703 to check and nope. Went to 0620 and it worked then to 0703 and it broke again :(

Maybe Apple patented 'light' or 'notification'
[Captivate Android Development] VirtualNobody:
Still running the 05/07 build....Does your MMS messaging work? It works fine when I have a TMOBILE SIM in it, but not when I have an ATT GO Phone SIM.

Any ideas?
[Captivate Android Development] justmart:
I had the same issue. You have to go back stock with odin... then try again. This did the trick for me.
[Captivate Android Development] justmart:
Just download rescan media from the store.
[Captivate Android Development] solarpenguin:
I get sleep/charge death nightly. Also get the haptic fade on occasion.

Other than that, I've got to say cm9 is awesome.

Any ideas on what could cause death on a nightly basis?

Using 4/12 cm9 with fresh factory wipe before/after load.
[Captivate Android Development] RootTheMachine:
Those aren't captivate modems, they're for the Nexus S and I cannot guarantee that they work at all. They don't work very well for me. You need an i9000 modem from here. The default one for cm9 is KG3.
[Captivate Android Development] chmcke01:
Nightly...so not for long term use?

A friend of mine has an AT&T Samsung Captivate completely stock, and he asked me to install a custom ROM for him....I have used custom ROMs on my SGS2 ever since I got it so I don't think it will be a problem, but it isn't as easy to tell which ROMs are the best and stable.

I am here because someone told me that usually the best way to find the best ROM is to see which thread is the longest (which at the time I looked appeared to be the Alpha before it linked here at the end).

So, since this is a nightly it probably isn't the best option if I am just wanting to flash it and it just work for me? Essentially, I want to flash a ROM that has everything working, can do anything the stock can do (or better), and is stable enough that I should just be able to flash it the first time and never have to flash anything else again.

Is this ROM the one I am looking for? If not, can anyone recommend a ROM that will suit my needs? I know this isn't the best place for this, but I couldn't find a place where it was right to ask for ROM recommendations. Thanks in advance for any help anyone can give!
[Captivate Android Development] maizein:
I got 2 cappy, both running cm9. One has charge death every night, the other one never has.

The solution I found was use a charger with less amp. No more charge death after that
[Captivate Android Development] johnhazelwood:
Go with a gingerbread rom, as it sounds like you want something that's very stable. One of the kk4's would be good, and if thread length indicates quality to you go with that. This rom is very stable, but still under development and you may still want to flash a newer version later. That's my $.02.
[Captivate Android Development] solarpenguin:
Interesting idea...I'll give it a shot. Thanks!!!
[Captivate Android Development] bentonhall:
I pretty much know the answer to this but I'm going to ask anyways..... right after flashing the nightly 0412, my power button quit working to put the phone to sleep and wake it. I'm pretty sure its a hardware issue as it doesn't work in recovery either so before I tear this apart and attempt to clean it, is anyone else having this issue after flashing the nightly?
[Captivate Android Development] fireflyv2:
Even the modems from that link don't seem to like my phone much..

Have tried the ugkg3, ugjk3 xxjk9 modems without any luck...

My old modem was a uckb1, dunno if that info is any use.
[Captivate Android Development] account4me2:
I always play internet radio when I go to sleep, and have never had charge death on any ROM/kernel I've ever flashed.

Regardless, I'd be full-wiping + going back to stock just to be sure before you start messing with the hardware (use download mode + odin).
[Captivate Android Development] dannb:
I'm having an issue installing the last couple of CM9 nightlies. I keep getting an error that seems to be related to the fact that I'm trying to install it on a Canadian Roger's Captivate (the I-896 I believe). Are any other Canucks getting this issue?
[Captivate Android Development] voldomart13:
OK this is weird I wanted to try a bigmem kernel with the 720p fix. It didn't work for some reason so I went back to glitch. I went to play my music over my speaker and its super quiet and I can't even adjust the volumes. Same for my headphones. Any ideas on how to fix?

EDIT: Fixed after reboot just another weird occurance. Well just bookmark it for anyone else with this problem =\
[Captivate Android Development] tkjeeper:
No
[Captivate Android Development] daskanda:
No, what error are you getting exactly?
[Captivate Android Development] bentonhall:
It started working again on its own. :/ I haven't changed a thing. Seems to me like its just dirty. It hasn't been that long ago that I did revert to stock but I may try your suggestion anyways since it doesn't take that long if it starts acting up again.
[Captivate Android Development] The_Wolf91:
A new Nightly is out: http://download.cyanogenmod.com/get...cm-9-20120415-NIGHTLY-captivatemtd-signed.zip

:)
[Captivate Android Development] JayFReaZy:
I was curious do the nightly's have to be installed consecutively in order? I have the initial nightly release from 04-08-12. I know a nightly was released after that on 04-12-12. I was wondering can I skip the 04-12-12 release and install the latest version (04-15-12)?
[Captivate Android Development] rjyanj:
Yes, you can skip and install 4-15.
[Captivate Android Development] airtower:
No you can install any nightly at any time. The nightlies are complete builds, not delta files
[Captivate Android Development] whiteguypl:
He doesn't actually use his phone.
[Captivate Android Development] Snorchblapp:
The only thing I would recommend is to check your APN settings. I had to enter mine manually a while back.
[Captivate Android Development] ThreeofNine:
Well, I didn't play any games or stream music and I don't use Facebook. I made 6 or 7 calls about 1-2 minutes in length and received 5 calls about 3 minutes each. I get weather updates every 15 minutes, Google+ and Twitter messages constantly, and sync 4 email accounts every 30 minutes. And I used Chrome a few times for about an hour total. So it wasn't heavy use, but the secret really is to fully charge the battery and leave it on the charger for another 2-3 hours for a deep charge, and don't stream videos or audio nor play games until you're ready to put it on the charger overnight. It works for me!

A possible variable for those with short battery life might be the battery itself. Some just don't hold a charge very well. Good luck out there!:cool:
[Captivate Android Development] shane87:
You may need to use odin/heimdall to go back to stock. I had a similar issue a few weeks ago, where I couldn't send or receive mms messages. I finally got smart and went through my messages to see when I was able to send/receive mms messages, which was in late march for me. So I went to a build from mid-march, and I still couldn't send/receive mms, even though I was able to send/receive mms the first time I ran that build. A heimdall flash to kk4 followed by a fresh install of the latest cm9 build fixed it for me.

On another note, I would avoid data fix scripts. I have no proof of it, but I started using a data fix script right around the same time as when I started seeing the mms issues.
[Captivate Android Development] VirtualNobody:
Thanks guys...It appears MMS is actually working, just very slow and timing out. Maybe due to week cell signal?

Does MMS data go over cell network or data network?

I can't seem to get the GoPhone SIM to connect up with my ATT microcell. And yes, I added the number to the microcell access list.
[Captivate Android Development] whipps:
I'm on build 17 with Icy Glitch V14 B6 and I'm thinking about flashing the latest nightly, but it seems like a lot of people are having issues. Is there really that big of a change from the old build 17 to say the cm-9-20120703-NIGHTLY for example?
[Captivate Android Development] brandon_L:
Build 7/3/12 is crazy faster than the last build I flashed. 6/29/12
[Captivate Android Development] Katze Pavilion:
I'm the one who had serious wifi issues, but recent builds are very good. It can't better.
[Captivate Android Development] sansaman:
[deleted]

---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------

Are you using 7/02 or 7/03 build?
[Captivate Android Development] Snorchblapp:
Build 0703.
[Captivate Android Development] sansaman:
Thanks. It is snappy. Just completed it at work. Will use for a few days to test battery. Seems to drain a bit right now.

But that's probably because I keep using the phone out of amazement.

Another thing, I can't wait until CM10 (CMX??) comes for Captivate.
[Captivate Android Development] Saint Wacko:
Has anyone else had trouble with their sound being extremely faint? It seems to be random when it does it, and when it stops. Yesterday I was able to fix it by plugging in my headphones then unplugging them, but that no longer works.
[Captivate Android Development] ap1618:
It maybe the speaker hardware issue. you can press down on the speaker area, and check using the volume buttons to see if it fixed it. if you hear the volume maxed out click ok, then you fixed it. (or easier, you can have a song playing and press on the speaker)
[Captivate Android Development] Saint Wacko:
I'll have to try that next time it goes quiet.
[Captivate Android Development] igorgomez:
No more reviews? When the rc1 arrives?!
[Captivate Android Development] ap1618:
maybe never. lets hope we all jump to jelly bean nightlies!
[Captivate Android Development] skyxliner:
It's been pretty snappy with no problems. Nearly perfect.