yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] zmore:
You really don't see the 0427 there? Weird. What's wrong with your InterTubes? Never thought I'd be arguing this when I woke up this morning :)

(Attached below is a screenshot of the changelog site as I've seen it since this morning. (everything below the 0427.zip line made it in; everything above it didn't and goes in the next))
[Captivate Android Development] thangphysk48:
How to change /mnt/emcc back to /mnt/sdcard? I have a lots of apps data store in internal storage.
[Captivate Android Development] The_Wolf91:
Settings, storage, push first button from left of your Captivate, configuration, check the box you'll find.
[Captivate Android Development] AgileAssailant:
I don't know why it would be updated for you before it would be updated for me (and at least a few others), but there's really no reason to continue talking about it, lol. ;)

Speaking of the change log for the next nightly, what exactly is the toggle switch that is being ported from CM7? Is it added to the power widget or is it something in the settings?
[Captivate Android Development] thangphysk48:
Thanks for your advise.
[Captivate Android Development] cesierra:
Internet Call keep alive refresh interval adjustment: Has this feature been added in recent nightlies? I dont want to have to upgrade to find out.
[Captivate Android Development] nkrick:
but....they have a pink unicorn! ;)

For anyone who has not tried it, CM is awesome. Most of the kernel work that ends up in all the other Captivate versions of AOSP based ROMs (AOKP, MIUI, Fusion, etc) comes from teamhacksung, the guys who maintain CM for the i9000, i897, i9100 and i777. Back when everyone else was cooking Samsung based ROM's, teamhacksung was developing from source.

I don't have any reboot issues on the nightlies. Did you try doing a factory reset before flashing the first nightly? If you try it, do your testing before doing any TiBU restores. It seems that using TiBU to restore data from android 2.x can cause many different problems in 4.x.
[Captivate Android Development] tkjeeper:
All running good here guys. What else would I expect? Is anyone else running a different kernel, I was wondering if the glitch kernel would work here. It's what I'm used to. But I can stick with the stock kernel if recommended. Thanks for all the hard work!

Sent from the frozen tundra known as Canada.
[Captivate Android Development] Captain_Nero:
Running the stock kernal is always recommended, especially on Nightlies.
[Captivate Android Development] BigTortoise:
I get a status 7 error when I try to flash this in CWM

Also should we be flashing the galaxy s nightly or the captivate nightly? You linked to the Galaxy S nightly but I saw there's a CM9 nightly in the captivate section.
[Captivate Android Development] tkjeeper:
Thanks cap'n.
[Captivate Android Development] ThreeofNine:
Please use the captivatemtd nightly for the captivate. The 1st link is for the international Galaxy S.
[Captivate Android Development] The_Wolf91:
That link is for I900. Here is the link for the Captivate. Flash latest Nightly.

http://get.cm/?device=captivatemtd
[Captivate Android Development] BigTortoise:
Okay then I figured. But I still get the status 7 error.
[Captivate Android Development] shaker2k:
If you came from the semaphore kernel you might have to flash glitch before installing nightly.
[Captivate Android Development] ThreeofNine:
I searched the teamhacksung CM9alpha threads and found this (#4422):

"This is a common/known issue with the CyanogenMOD installer. Apex is an i9000 ROM, so your build.prop file identifies your phone as an i9000. The installer reads that, thinks you're trying to flash the Captivate version onto an i9000 phone and craps out. Your solution is to either manually edit your build.prop, flash any Captivate-based ROM first (then build 14), or return to something stock with a CWM-enabled kernel.

Any of those should fix your build.prop file, and you should be able to flash without issue then."

This may be your solution if you're coming from an i9000 rom. If your rom is an i897 you may simply have a bad download.
[Captivate Android Development] Austin Ag06:
Wow, I'm not the one with the problem, but thank you for the research....
[Captivate Android Development] pawitp:
Fixed. Too much copy pasting :p
[Captivate Android Development] voldomart13:
Servers down =( Last I saw they were working on a new nightly.
[Captivate Android Development] b-eock:
D: I will wait then :P
[Captivate Android Development] ptesmoke:
latest nightly working fabulously well!
[Captivate Android Development] b-eock:
Its back up
[Captivate Android Development] voldomart13:
Nope now its saying bad gateway =(

Ive got a problem. my moms cappy's ringtone volume isnt working. The volumes all the way up and I know the speaker is working. Any help? Please I appreciate it.

Mine isn't working either anyone else experiencing this?

I checked the profiles and I changed them so the volume would be loud on the ringer and still no sounds just vibrates.

Anyone have a package for the kernel for the newest nightly?

Even on the stock cm9 kernel still no sound.
[Captivate Android Development] daskanda:
Check if a ringtone is set
[Captivate Android Development] voldomart13:
It is, Can anyone report that there ringtone is working? If everyone elses is working what should I do?

I put it back to stock ICS with the newest nightly still no ringtone but notification works. Do you think maybe my ring tone could be corrupt?

Not sure what I did but everything seems to be working now.
[Captivate Android Development] br0adband:
If people are having issues with the get.cm URL they can always get the build from the full URL at:

http://goo.im/cm/captivatemtd/nightly

Been running it for a bit tonight, so far so good, it's been working great. Only concern at this point is GPS sensitivity but I can't test that at this exact moment, but I have high hopes it'll be just fine.

Anyone notice that volume (overall) is low, or seems that way? I went back to the stock KK4 earlier for some testing and I swear, when I set the system click on touch it's like... loud in the KK4 GB stock ROM but, in all the ICS ones I've tried (about 10 in the past 3 days) none of them get anywhere near the volume level the stock GB ROM manages. Guess it's not a huge thing but I actually do prefer hearing that click-click-click when I'm tapping the screen.
[Captivate Android Development] vercro:
Try checking the change log to see if it's there.

http://cm-nightlies.appspot.com/?device=captivatemtd
[Captivate Android Development] p1gnone:
cm noob

Moving from other GB projects to CM9 has been a joy. Early weeks seemed not to have a fast burn thru the battery --warm phone but now the nightlies are having this issue for me..

So am I a noob needing to learn how to kill processes so to shut down the problem, or is this just the cost of access to the benefits of these current ICS ports?
[Captivate Android Development] RootTheMachine:
Killing anything isn't going to help unless you actually have a rogue process that is out of control. The rest all depends on your usage and setup
[Captivate Android Development] Jesterdtm:
I experience this in excess if i don't do the occasional Factory Data reset every 5 or so nightlies. i think it is just something to do with cumulative updates.
[Captivate Android Development] p1gnone:
Thanks, truth be told I havent always done the FactoryReset especially with the 'nightly' frequency. I'll give it a try.

To the point of korockinout13, the battery drain can be dramatic where with no use I lose 10% in an hour, phone sitting idle in my pocket.. SO then what setup aspects can affect batt-life..

_______________________________

Factory data reset seemed to do the trick.
[Captivate Android Development] voldomart13:
Are phone calls working in the newst nightly?
[Captivate Android Development] ConeyKiller:
I've been using THS Alpha Build 13 for quite sometime. Seems to work great for me with the occasional force close or glitchy video. Not big issues IMHO. How do you guys think this would compare? I know its a different Android build....just wondering if it would be worth the hassle.
[Captivate Android Development] billyjed:
Yes. Do it!
[Captivate Android Development] AgileAssailant:
Yes, but I've never experienced the problems other people have had with phone calls.
[Captivate Android Development] ConeyKiller:
Ya that's the thing. Until that's fixed I might hold off. Its my daily driver.
[Captivate Android Development] ConeyKiller:
NM....miss read the previous post. I'll probably flash tomorrow. Wahoo
[Captivate Android Development] Sword_of_a_1000_truths:
hmmm just flashed update-cm-9-20120429-NIGHTLY-captivatemtd-signed.zip and getting weird erratic behavior with touch screen. when using swype or swiping in general it jumps around a lot. scrolling thru menus isnt as smooth as before it screen jumps up and down and cant even swype correctly. looking at the swype trace it looks like some of the gesture isnt registering. did a factory wipe after flashing too

EDIT: seems to have gone away after another wipe
[Captivate Android Development] dave1977nj:
On YouTube I can't adjust the volume any fixes for this or is it just me?
[Captivate Android Development] voldomart13:
NEW NIGHTLY!!

http://get.cm/?device=captivatemtd

http://cm-nightlies.appspot.com/?device=captivatemtd
[Captivate Android Development] br123:
Extremely slow WiFi performance

For some time now my Captivate's been showing extremely slow WiFi performance on the university's T3 connection. A speed test result is attached, but basically, I get:

Download: 59.2kB/s

Upload: 842.3 kB/s

And these results ARE repeatable - I've done tests many times and these are the numbers I get.

It's not the network though; on my computer AND my HP TouchPad, I consistently get download rates of 10Mbps and upload rates of 18Mbps.

Does anyone else have this issue? I've searched through this thread and found nothing related to slow WiFi performance....

Also, I'm on the 04/25 nightly, so I'm pretty up to date.
[Captivate Android Development] wormat22:
I'm getting a sleep of death with the latest nightly build, any suggestions?
[Captivate Android Development] voldomart13:
I'm just gonna come out with this because if its someone else they might be a douche bag about it. Are you on the glitch kernel? If so you need to ask in the glitch thread.
[Captivate Android Development] daskanda:
Try increasing you arm voltages for the 100 step a bit or set min frequency to 200
[Captivate Android Development] wormat22:
I'll try that, thanks.

No, I'm on the stock kernel.
[Captivate Android Development] wash23:
Ringtone volume inadequate

This may or may not be a bug but it seems that it is impossible to get the ringtone volume loud enough to hear in all but the most silent surroundings. It has never been what I would call loud but it did seem louder when I was running Cognition v5. It seems that Samsung does not want to be overbearing. If anyone has this problem and could recommend a solution, I would appreciate it.
[Captivate Android Development] Jesterdtm:
I noticed this behavior on 4-27 nightly, but only when the phone was plugged, in and charging. It stopped when i unplugged it.
[Captivate Android Development] Joecascio2000:
This happens if you use a charger other than stock or higher than .7 amp output.
[Captivate Android Development] bentonhall:
Yes. I've noticed this on the nightly builds too.
[Captivate Android Development] nimper:
Can you reproduce the same problem on other wifi networks?
[Captivate Android Development] megarific:
can i install cyanogen mod 9 from froyo using clockwerk recovery or i have to port to ICS first?
[Captivate Android Development] nimper:
Just follow the directions in the first post, that will get you to CM9 the easiest way.
[Captivate Android Development] Jesterdtm:
I hadn't thought of that. I am not using the stock charger, but I've been using the same one for over a year. Perhaps I just hadn't noticed that behavior before.
[Captivate Android Development] br123:
Yep, happens on any WiFi network I use.
[Captivate Android Development] nkrick:
You can use DSP Manager to increase the volume, but the default values *should* be loud enough (obviously this is subjective). I know there was an issue way back in CM7 on the SGS phones where if your volume was too low, you could flash back to stock, put all the volumes to max value, then reflash CM and it would fix the problem. I don't know if that will help anymore with CM9, but it might be worth a try.
[Captivate Android Development] skyxliner:
IM just waiting for voodoo sound to come to ics. Current dsp manager is nowherr close
[Captivate Android Development] whyareyou:
Voodoo is already built in, it is called WM8994 under DSP Manager app.
[Captivate Android Development] ConeyKiller:
What any easy flashing process. Nutty. Gonna see if video playback works for me.
[Captivate Android Development] skyxliner:
I'm saying it's not good enough compared to CM7 with voodoo
[Captivate Android Development] speedy_11:
Voodoo sound app compatibility is coming back soon

http://review.cyanogenmod.com/#/c/15245/
[Captivate Android Development] ConeyKiller:
So I flashed over THS Alpha 13. I'm familiar with flashing and all that jazz. I read the instructions. Calendar sync is not working. It says to wipe and reflash if you were not previously on a THS for sync to work. Am I missing something or should I just wipe data and cache and reflash? I have no problem reflashing. Just curious if maybe this is a different issue.
[Captivate Android Development] galakanokis:
Flash the gapps package immediately after flashing the ROM. No reboot in between. I don't think you need to wipe, but can't remember 100%.
[Captivate Android Development] Wakamatsu:
Keep in mind that you're jumping to Android 4.0.4. It's probably a good idea to do a wipe.
[Captivate Android Development] shane87:
Wipe data/cache, then flash latest nightly, then gapps, all without rebooting. Your calendar sync should work then. I ran all of the THS builds starting with 13, and for the first few I had no problem with calendar sync. After the update from 4.0.3 to 4.0.4, however, I ran into the calendar sync issue. Since I don't use the calendar, I just disabled sync on the calendar to get the other apps to sync. After a little while though, the issue started to bug me, so I did a wipe and reflash, and I have had no problems since.
[Captivate Android Development] RootTheMachine:
Have you tried gapps fixer?

Sent from my ICS Samsung Captivate
[Captivate Android Development] ConeyKiller:
Ya I flashed the matching gapps right after. Didn't do a data wipe before it all though. I guess I'll do it when I get home from work. Wonder why calendar is such an issue. Oh well, I'll let you guys know. This will be my process. wipe data/cache reflash nightly then flash gapps. No reboot between. We'll see.
[Captivate Android Development] t-readyroc:
No, not just gapps. GApps Fixer. Fixed calendar sync for me. Hope you haven't wiped yet.
[Captivate Android Development] skyxliner:
Thank God the voodoo sound volume boost is at least 2x what it is now
[Captivate Android Development] baxim:
Im on Android froyo 2.2 can i flash? or i need android KF1 first?
[Captivate Android Development] nimper:
Check out the instructions in the first post. No need to flash any newer version of samsung rom, just root and install clockwork then you're good to go.
[Captivate Android Development] baxim:
I tried to install directly with clockwork but always gives error "signature"
[Captivate Android Development] nimper:
Actually it doesn't sound like you correctly installed clockwork recovery. Might wanna give that a second try.
[Captivate Android Development] baxim:
clockwork dont appears captivate to install. im on KF1 2.3.3 appears Nexus S - Nexus S 4G - Epic 4G - Galaxy S i9000 - whats happened?

;~~
[Captivate Android Development] nimper:
You need to flash a rooted CWM kernel with odin or heimdall, such a kernel can be found in this forum.
[Captivate Android Development] baxim:
im using I897UCKF1-AutoRoot-DesignGears.tar i try now one with CWM (cognition v2 but get error) and i back to I897UCKF1-AutoRoot-DesignGears.tar kernel. i cant do that ;~~ its something wrong
[Captivate Android Development] ConeyKiller:
I had gapps fixer didn't know it was still used. I just erased it off my phone lol. Didn't wipe anything but the cache partition. I'll try the fixer.

EDIT: gapps fixer worked. Thanks!
[Captivate Android Development] daskanda:
There's instructions and links in op.... Just read a little
[Captivate Android Development] Wakamatsu:
From what I understand, all this does is root your phone and install su. You need to install Clockwork Recovery. ROM Manager will not do this for the Captivate. You need to start at the beginning and flash a kernel with CWM.
[Captivate Android Development] vileladelima:
Same Changes!

It's my impression or we had same changes on last nightly update?

Tha custom cm9 boot screen is missing!

The option when you plug the usb is crazy!

Tell that is as a camera, and apperas the 4g icon in notification panel.

Is only me, or my cellphone is realy crazy?

Thanks!
[Captivate Android Development] Kaik541:
sounds like you installed a third party system UI modification (i.e. like the Reloaded package or a theme) that messed up your drawables. don't flash/install these if you want support.
[Captivate Android Development] vileladelima:
So its the reloaded package!
[Captivate Android Development] james.arroyo:
Its been awhile since my last flash. I'm currently on Fasty KI2 2.3.5 with AT&T GB bootloaders. I really would like to go to an ICS ROM so I went with CM9 one since everything else is based on it.

I saw in the instructions that I can just download, wipe, and flash....is that correct? I just don't want to have a brick. Also would it be best if I went back to 2.3.5 stock first?
[Captivate Android Development] RootTheMachine:
Download, wipe, flash, gapps

Sent from my ICS Samsung Captivate
[Captivate Android Development] nkrick:
Just follow the instructions in the OP. Flashing CM will never brick your phone because it does not flash any boot loaders. CM also does not require any specific version of boot loaders, i897 eclair/froyo, i897 gb, and i9000 gb will all work. If the flash fails, you can use three button recovery and flash again, or in worst case scenario, boot to download mode and use odin.
[Captivate Android Development] sa1yan:
I tried flashing a dif kernel on the latest nightly, and the phone won't recognize my internal sd card? :(
[Captivate Android Development] daskanda:
Did you get the encryption unsuccessful screen?
[Captivate Android Development] Ikonomi:
Has anyone else experienced flaky cellular data on nightly 0429? Since flashing, my data connection will occasionally stop working, though the blue highlight says I'm still connected to Google's servers. A reboot or toggling flight mode seems to restore the connection. At first I thought it was a service problem but I've had it happen in several parts of the city.

This was on modem KP1. I'm currently using KG3 to see if there's any change.
[Captivate Android Development] GuitsBoy:
I hate to ask a lazy question here, but it seems my google-fu just isn't up to the task today.

How can I get all video types to play again? I am getting a lot of "Media Error, Sorry, cannot play this video." messages. It seems that the mp4 extension is having better luck than mkv, avi, or wmv, but I even have trouble with some mp4 files that used to play.

Any suggestions? Is there a codec pack or something I need to install?
[Captivate Android Development] mnjm9b:
Try bsplayer...

Works pretty good.
[Captivate Android Development] nkrick:
Do you seriously expect THS to help you figure out why an alternate kernel doesn't work? Post in the alternate kernel's thread, this thread is only for reporting and discussing problems when running "stock" CM 9 nightlies.
[Captivate Android Development] GuitsBoy:
Good call, this seems to work. Still, Im perplexed why the other three players all worked in GB land... Just the same, thank you very much.
[Captivate Android Development] Jesterdtm:
Ditto:

i am using znkp1 for ics which historically has done well in W. Washington.

However it bounces up to H/3G i think it's ATT actually, each time I've thought it was the phone they were doing something with their towers. in several places.
[Captivate Android Development] ThreeofNine:
umm...maybe they haven't been updated to ICS specs?
[Captivate Android Development] GuitsBoy:
The applications worked, they would only play select files. If the application was not ICS ready, Id imagine it would result in a FC.
[Captivate Android Development] Wakamatsu:
That's not the only outcome of incompatibility.
[Captivate Android Development] GuitsBoy:
We're talking ES player, quickpic player, and the stock included video player. I would imagine that these are fairly popular programs and would have been updated in short order. But to be honest, I cant verify or deny that.

Anyway, BS player is indeed working, so all is well in movie land again.

Thanks guys.
[Captivate Android Development] nkrick:
I've had data issues on my captivate for 8 or 9 months now, especially in specific areas (as in a 1 mile radius of a location). For example, in the office, I get a H logo normally, but data almost never works. This problem is consistent on a daily basis and for about 1 mile around the location where I work (I just use wifi now at work). However, my wife's Captivate (running stock) does not experience the same issue at all. I have compared signal and frequency and both phones will be on 1900 Mhz with similar signal strengths (her's is generally a little better). So the issue does not seem to be AT&T. But in most other locations, including home, I don't have any issues connecting to data, so it is hard to blame the phone.

Flashing an AT&T modem on my phone doesn't make any difference as long as I am running CM. The last time I flashed the stock AT&T KB1 ROM, the data was working fine, but that may be purely coincidence since it occasionally works with CM also. I just tested now using CM9 + JL3 modem and was actually able to connect to data, but my connection was dropped in the middle of running speedtest.net, even though it still shows H with full blue signal bars.
[Captivate Android Development] MagicArc:
Still seeing SOD

Still seeing SOD randomly. Thought it was fixed but last night during charge it SOD during middle of night. Ever since i've been getting random SOD throughout the day. Forced to redownload Captivate Keep Alive to keep system from shutting down randomly.

What is your--

Phone model: SGH-I897

Radio (baseband): I9000UGKG3

CM version: 9-920120427-Nightly-captivatemtd

CM Download url: http://get.cm/?device=captivatemtd

Gapps version:gapps-ics-20120429-signed.zip

Did you--

wipe: Yes

restore with titanium backup: Yes

reboot after having the issue: Yes

Are you using--

a task killer: No

a non-stock kernel: No

CMSettings/Performance settings (other than stock): Min Freq 200mhz

other modifications:

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed: Every since day 1 of captivate ownage experienced SOD. no warranty, no return option.
[Captivate Android Development] singlebeam:
Yes, I'm experiencing similar behavior. It has been only for the past 2 nightlies but I will lose data connection and need to reboot in order for it to work again. My bars turn white which indicate no connection to google servers.

Everything is stock except for the JK4 modem which I have been using for over a year.
[Captivate Android Development] Ikonomi:
I reflashed the ROM and am now getting the white/gray bars when it disconnects.

There's a new nightly up at http://get.cm/?device=captivatemtd which may fix the problem. I haven't had a chance to look over the changelog yet.
[Captivate Android Development] nimper:
The new nightly basically only has translation/localization updates, so unless you have your phone language set to Russian or Italian it won't be any different.
[Captivate Android Development] whyareyou:
From what I can see, no significant changes, just translations.