yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] singlebeam:
jenkins successfully built cm-10-20120818-NIGHTLY-captivatemtd.zip

md5: c9cf2e3db0394a8d1b704d7425da0192

get.cm
[Captivate Android Development] johnnyrichter:
Will he be making a new thread here in the captivate dev section? I'll probably wait for that to happen just in case the install process is different.
[Captivate Android Development] lavero.burgos:
Is ready:

http://get.cm/get/jenkins/6349/cm-10-20120818-NIGHTLY-captivatemtd.zip | md5sum: c9cf2e3db0394a8d1b704d7425da0192 | 144.21 MB

~ V
[Captivate Android Development] pennex1:
how do you flash cm10 if you are on cm9? is it just a simple full wipe using cwm of the cache and delvek and then flash cm10?
[Captivate Android Development] lavero.burgos:
Full wipe and flash the ROM twice, then gapps addon . Same if you come from belly bean just to be safe. Is what I did and no problems.

~ V
[Captivate Android Development] pennex1:
thanks for the helpful info. is this still the link to get the gapp? http://goo.im/gapps
[Captivate Android Development] johnnyrichter:
CM10 Nightlies thread is now up!

http://xdaforums.com/showthread.php?p=30388049

Contains install instructions, link to nightly build, and link to gapps.
[Captivate Android Development] Majin Kaioh:
After rebooting it a few times, I can confirm that the only thing that happens is that the brightness of the screen goes up after the flicker.

Its running the 3.0.8-g54d09f2 inky-ghost@cyanogenmod #1 kernel. Should I flash a different kernel? This one seems to work well.
[Captivate Android Development] shane87:
I don't think it has anything to do with your kernel. The white att logo is handled by the bootloader. It could be that you still have eclair/froyo bootloaders, but I'm not sure. I've had gb bootloaders since about a month after gb launched for the i9000. However, as long as it boots fine, I wouldn't worry about changing bootloaders unless you know what you are doing. It is very easy to brick your device if something goes wrong during a bootloader flash.
[Captivate Android Development] JigsterNL:
Hello,

I'm running the stable version of cm9 now and I'm very happy with it. Though, since I switched from* Vodafone NL to Tele2(runs on T-Mobile NL), my data doesn't work well,it sometimes lags and disconnects. I need to have roaming enabled when I use data, I use data roaming+national data roaming. I'm running the Devil kernel,but I also had the problem when I was on the stock and semaphore kernel. Is this a problem with my modem or is my provider just giving me bad coverage?

Thanks in advantage

* In the time I switched, I wasn't using my cappy,but my HTC Titan(didn't notice lag or anything on it)
[Captivate Android Development] gramme66:
Using Root Explorer I see /emmc that you say is the external removable card...answers why I was NOT able to find my pictures...

I do my titanium backup in a folder in: /sdcard/external_sd thinking this was the removable card..what am I NOT getting here?

Thanks, hope you can clear this up for me. :confused:
[Captivate Android Development] n311.dunkle:
Tried to keep my mouth shut but I hate that response. Do you have any idea how many pages of posts I read before asking. I use the search feature all the time. Doesn't always make the search easier. If someone asks a question and you know the answer, it only takes a few key strokes to help them. Answering a question more than once isn't as bad as searching for the one time it was answered buried in hundreds of posts in a very populated forum.

However, thank you for the suggestion. Facebook synced just fine on 2.3.6 so I guess you are saying Facebook hasn't updated to ICS compatibility?
[Captivate Android Development] jgchaval:
Hi everyone,

I just flashed the 20120819 nightly build on my Captivate. Also, I'm using the Devil Kernel 1.1.3.

Since I flashed, I've noticed that my battery drains quite quickly, and that didn't happened before. (I was on a teamhacksung CM9 build, can't remember which version but it was released around February or March of this year probably).

Now, my battery never reaches 100% even if it has been plugged all night long. After 1 hour of being unplugged, the battery dropped around 8%, which I think is too much for just 1 hour.

A friend of mine who has a Captivate too, is using the 20120816 build and has no battery drain issues like mine, and he is also using the Devil Kernel.

Could it be some sort of "bad flash"? Should I reflash the kernel, or flash again the CM9? Any ideas what could it be?

Thanks in advanced!
[Captivate Android Development] snowake:
Did you do data/sys wipe rather than dirty wipe (not simply wipe cache/Dalvik) b/f flashing the nightly? Also, did you keep default option (always stay on) in WiFi advanced menu? I only ask b/c if you have been using the same ROM since March you likely forgot to re-enable a power saving option in CM9 or Devil (i.e. BLX set at 97%). You can always reflash kernel first, but full wipe and flash after several months of use is like a shower after camping out in a humid, hot area for a few days in full gear.
[Captivate Android Development] jgchaval:
Yes, I did the data/sys wipe, plus the cache/Dalvik wipe both before flashing the ROM and after flashing it.

I'm gonna redo the wipe of the data/sys and the Dalvik, re-flash the kernel and then do the wipe again, just to see if that improves something.

I have the default option in WiFi advanced menu, althought I barely use WiFi at all. I mean, it's always off.

The BLX is set to 100% (default value). I'm gonna switch it to 97% to se how it goes.

I'll post my findings later. Thanks pal!
[Captivate Android Development] tmroy:
Sync stopped working as of Friday August 24th!

I just noticed that my calendar hasn't synced up today, neither has anything else.

The little wheels in the sync setting window don't turn at all and they give Aug 24th as the last

time everything synced. I've tried reinstalling the latest nightly cm-9 rom, gapps-ics and gapps_fixer to

no avai!.

Thanks,

Todd
[Captivate Android Development] truckmann:
I have started to get the "Warning, low memory conditions have been detected" message. Started out out off the blue. Was working fine until today.
[Captivate Android Development] n311.dunkle:
Try this script. It worked for me.

http://xdaforums.com/showthread.php?t=1541942

Instructions are in original post.

Also, I believe I read that cm 10 doesn't have this problem and its available now so worth a shot ? I haven't tried it out yet so don't hold me liable.
[Captivate Android Development] truckmann:
Thanks. I tried that yesterday and unfortunately it didn't seem to help. It's just odd I've never had this issue before and haven't changed anything recently and it started doing this. I was running the stable release, but now I'm installing the latest nightly. I'll see how that goes and try that script again to see if I can get it to stop warning me. I was hoping to wait on CM10 for a while until it has some more development time.

I'm planning to update to an S3 sometime before the end of the year anyway. I was kind of waiting for the new iphone release to see if that drives the price down on the S3, if I can deal with this old thing that long... :D
[Captivate Android Development] melvinaury:
My recomendation to you is to move some apps from internal to sd and if you use chrome just clear data.

That will free the /data and the problem will go.

---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------

For cm10 yiu don't have data, but internal memory is only 442mb, that means that you have to install almost all you're app in the sd and not on internal memory
[Captivate Android Development] ThreeofNine:
I got the low memory error message yesterday and I moved some of the apps that were 10MB or larger to the sd card and the message went away. The message appeared a few days after I installed Chrome. I was on CM10 but I had to go back to CM9 Stable. Just too many issues with CM10 on my Captivate:

1, Camera would close when I tried to go back to the camera to take another picture after looking at picture in the Gallery that I just took.

2. Touching anywhere on the side of the Home or Back button that is near the center invisible button opens the Google search/Google Now screen, or it tries to. After a minute or two of a white screen it eith auto- reboots or an error message pops to ask if you want to wait or close the Google search process

3. Using the Phone app to find a contact to call lags for a very, very long time. screen advances lag, then when the contact phone number is selected there's a log delay before the phone call is started.

4. When the phone is awakened, the notification drawer stays blank for 20-40 secs before it's populated with message, or missed call notifications.

5. There was a long delay when going from one app to another or switching homescreens

6. The wallpaper would return to the default jb wallpaper after every reboot.

I even tried the Semaphone kernel and it was even worse.

JB is looks great from what little I could use, but my phone doesn't like it I only have a few more weeks to wait before I get the GS3 and then a month or 2 before the AT&T JB version arrives. Then maybe I'll turn my Captivate into a "Samsung Galaxy Player".
[Captivate Android Development] johnnyrichter:
Yeah it's gonna be quite a while before I upgrade from cm9 to cm10 due to all the issues. Plus there's no one in the cm team that has a captivate so they're not really developing for our phones, they're just working on the port. This leaves the door open to known issues such as the OEM partitioning leading to low space errors and the first-gen sleep deaths.

Would be nice if someone would focus on the captivate a bit more, but it's an aging phone so I can't blame them for considering it obsolete when it comes to rom development. Heck, I'd probably be willing to foot the bill for a used captivate if one of the hacksung/cyanogen guys were willing to work on it for cm10.
[Captivate Android Development] truckmann:
Ugh. I moved several apps to the SD card and uninstalled a couple. I just use the stock browser, but I cleared the data in it and the Low memory conditions warning is still occurring. No idea what is going on here or what has changed that is making it think it has low memory.

Edit: It may have something to do with the latest NoLED update. That seems to be the app giving the warning message. Will test farther.
[Captivate Android Development] account4me2:
If you go into "Storage" in Settings, and everything appears to have plenty of space, then your \datadata folder is getting full.

Get the app called "DiskUsage". Open it, click "[Root required], open the "/datadata" folder, and see which apps are using the most memory. Chances are there will be a few that you don't care about that are hogging a lot of memory - just uninstall them, and your problem will be solved, without needing to use any dodgey hack scripts. :)
[Captivate Android Development] ThreeofNine:
FYI CM9.1 Stable is available now!

http://get.cm/?device=captivatemtd&type=stable
[Captivate Android Development] Snorchblapp:
Just curious, are you using Devil Kernel? I had the same issue when I installed the latest CM9 nightly with Devil Kernel. When I reflashed the nightly, the problem disappeared. When I flashed CM9.1 (out yesterday), I didnt flash Devil Kernel and I havent had the message yet. Maybe theres some sort of conflict between the two?
[Captivate Android Development] truckmann:
I'm just using the stock kernel. Turned out it was NoLED that was creating the message. Seems to be an known issue that can be dealt with easily, by turning off that notification. Downloading CM9.1 now!
[Captivate Android Development] truckmann:
I think my phone is going to crap. I put 9.1 on and everything lags badly.
[Captivate Android Development] azunino:
Have you tried wiping data/cache? Or you can try going back to stock and then flashing cm9.1

I've upgraded from cm9 (no wipe) and it works ok.
[Captivate Android Development] truckmann:
I went ahead and wiped cache's and it seems to be working better today. Although some apps are still really slow at times. Took forever for gmail app to load first thing this morning, but now it seems to be working okay. Just have to keep it working a little bit longer until I can upgrade... ;)
[Captivate Android Development] phoneturf:
I am trying to get CM9 on my cappy but having a hard time finding a CWM with 3 button combo. I tried it with a 2 button combo since I currently have an i9000 kernel, but that caused a bootloop. Are there any cappy 3-button CWMs still available to download?
[Captivate Android Development] Gromlakh:
If you currently have a custom kernel, do you not have an option to reboot to recovery from the power menu?
[Captivate Android Development] phoneturf:
Yes, but did not know if that would cause a problem or not. I will give it a try. Thanks!
[Captivate Android Development] billyjed:
Go to this thread:

http://xdaforums.com/showthread.php?p=18370235

It Judas a while mess of stock with root stuff. If you flash a no bootloader package and you still don't have 3 button combo, then you probably don't have i897 bootloaders and you need to flash the package that had them. Be careful flashing bootloaders, that is just about the only way to brick this phone.
[Captivate Android Development] Gromlakh:
All you need is to get to recovery. It does not matter how you get there.
[Captivate Android Development] phoneturf:
I was trying to download the 2.3.3 Kernel with CWM from that thread but it looks like all the designgears files at ponack.com are gone. This is the main problem I am having in trying to restore my Captivate - I can't find the correct files any more. I had a folder of them on one of my computers but inadvertently deleted them, and it has been challenging to find them again. Many of the links to these older files that are necessary to upgrade a cappy from stock are no longer valid.
[Captivate Android Development] iosmonster:
Just odin one click to jf6 and use kies to upgrade to latest kk4 and then heimdall flash the kernel zImage from mtcareys corn kernel and u will have recovery and latest bootloaders and it's much safer imo
[Captivate Android Development] phoneturf:
I think it does if I don't have the three button recovery. I tried rebooting into recovery, master reset, and flashing CM9, but it quickly bombed out and got into the same bootloop where I thought I had to reflash from scratch in download mode.

But the phone would not go into download mode, just to the battery screen. So I tried doing a few battery pulls with vol up down while plugging in and on the third try, amazingly, it did not go into download mode but instead it resumed the CM9 ROM installation and did not bomb out.

So now it looks like I still don't have a three button recovery, and I guess I still have the i9000 bootloaders since I get the i9000 splashscreen before I get the one for CM9, but it's installed and working.

I now have the CM9 kernel, but should I install the mtcarey kernel to get it to cappy bootloaders and 3 button CWM, then go back to CM9? Thanks for everyone's help!
[Captivate Android Development] Srikar_NBK:
I have the i897 bootloaders and am currently running Super Bean 2.8.17 JB. Its unstable on my phone and I want to switch to this ROM. Just wanted to check if I can just wipe and flash or are they any other measures that I need to take ? Thanks
[Captivate Android Development] johnnyrichter:
The latest CM9 stable seems to be working fine for me so far. Still have the occasional sleep-death but I've gotten used to that by now.

I'm pretty sure this has been your problem the entire time. I think you need the GB/i897 bootloaders before running any GB or JB kernels/ROMs. A quick search of the forum will turn up the Captivate bootloader sticky that includes guides and links.

ETA: If you look at the "One-Click back to GB KK4" in my sig that thread gives you two options to go back to stock GB KK4...with or without bootloaders. You could use the one-click method w/ bootloaders to get back to stock, then "Easy-Root GB KK4 to Corn 7.0a" in my sig, then wipe/reset/wipe cache, then flash the latest CM9 nightly or stable, and then flash the latest GB gapps.

This is the method myself and many others have used and the only problem I ever experienced was during the step for flashing CM9. It would go about 15-20% and then the phone would restart and bootloop until I 3-buttoned in to recovery and flashed CM9 again which would work fine that second time. No idea why it did that or if anyone else had a similar problem using that same method.

I don't know if there's an easier or quicker way to get you the bootloaders you need, but this ground-up method doesn't take too terribly long and those two links in my sig should definitely be saved in your bookmarks if you own a Captivate. ;)

Have you considered trying Helly Bean or CM10 nightly before going back to GB? Personally I'm gonna wait until the CM10 nightlies get along a bit further before I jump in and try it out.

Anyway, you should just be able to do a wipe/reset/cache wipe and then just install the latest CM9 nightly or stable + the latest GB gapps. Any nandroid backup you made on JB won't be compatible with ICS and vice versa.
[Captivate Android Development] Srikar_NBK:
Wait, I thought CM9 was ICS, not GB.

I haven't tried Helly Bean or CM10, as they were nightly builds and I thought they would be unstable. Will give them a try though. My feeling was that CM9 might be more stable on old hardware like the Captivate, as it would have more time to iron out issues, compared to bleeding edge JB roms

Edit: I think Helly Bean is not an option. Their HB OP says it needs GB bootloaders and I can't risk bricking my phone switching bootloaders now :(
[Captivate Android Development] johnnyrichter:
You're correct about CM9 being ICS. It's 2:30am here and I've been up since around 6-7am yesterday morning, haha. I corrected my last reply.

CM9 will be more stable/usable than Helly Bean and CM10 but some users are liking those while others have complaints. If you're interested in having JB right now they're worth a try, otherwise just jump back to CM9 and wait it out.

If you follow the method I wrote up for the other guy your phone shouldn't brick and during the process you'll get the GB bootloaders back.
[Captivate Android Development] Srikar_NBK:
Thanks for ur suggestion. I will prefer taking the easy route and try only 897 bootloader compatible ROM's as I'm in India with a US Captivate. Any brick will effectively make it a paper weight.

So the question is can I flash CM 9 on 897 bootloaders ? :o

Too confused about the labels of the bootloaders. The bootloaders I'm using are from this thread

http://xdaforums.com/showthread.php?t=1129821
[Captivate Android Development] johnnyrichter:
The "unable to install to..." error has returned with this latest stable. I applied the fix in my sig and that didn't fix it this time. Uninstalled an app i rarely use in order to install the xda app.

Any other fixes for this problem?
[Captivate Android Development] jetpuck73:
I click on my messaging app and it opens and closes right away.
[Captivate Android Development] johnnyrichter:
Still being told that I'm unable to install anything to internal or external.

As of the latest beta I now have several new issues...

-Phone is VERY sluggish. Lags constantly.

-Now 90% of the time I do a sweep with my GO Task Manager it doesn't actually kill apps(settings, play store, haywire, etc). I have to open up the task killer and kill them one by one, refresh numerous times, sweep numerous times, etc until those apps stop trying to run. Refresh > sweep > refresh always worked flawlessly before this build.

-Sleep deaths stopped happening for almost a week after upgrading but have returned today and it's shut off about 5 times in the last 12 hours.
[Captivate Android Development] truckmann:
Ugg. My Cap was running really badly and locking up a lot. So I did a factory reset, got all my apps re-installed and it is running much better, but now it keeps loosing the data connection. It says I'm on the KG3 modem, but I tried to re-flash it anyway to see if it would help and it just gives me and error and aborts the flash. This thing is really pissing me off. Wish they would get the black SGS3's out soon on AT&T. I'm ready to move on, but don't want a red white or blue phone.

Edit: I'm an idiot.... Had i9000 modem zips instead of CM7-9 zips. Trying out a new modem now to see if it solves the data disconnect issues.
[Captivate Android Development] truckmann:
Okay so I flashed another modem and now I can't send text messages. I just get a "message not sent" error. I tried flashing it back to the previous modem and it won't send them either. Everything else seems to work fine. I can receive messages and calls work fine. Anyone have an idea how I can fix this?

Never mind. I fixed it. Lost the smsc number.
[Captivate Android Development] uhm:
pawitp,

After successful flashing of the CM9.1 rom on my i897, when I power on my phone the screen becomes heavily tinted with dark blue color after the initial boot animation and then stays that way afterwards. I understand it's related to Nexus S Framebuffer. Would you please look into it and fix it if possible? Thanks a lot in advance.
[Captivate Android Development] demoicurn:
i have been running CM9-stable on my cappy for 3 days now. Loving it. No issues. Like a kid in a candy store with all the theming options. Thank you to all who contributed
[Captivate Android Development] diminished5th:
I apologize for not checking there first.
[Captivate Android Development] bsieron:
hi everyone,

i have updated from CM7 (using the method shown in the first post) but unfortunatelly i have encountered a problem. an update went smoothly but after the phone started i keep getting an error "android.process.media has forced to close" and that the clock was forced to stop as well.

i searched on forums for solutions but most of them tell to navigate to some folders. problem is i can't do that. in application list i don't have any flie manager and whenever i try to download something from google play the "android.process.media..." error closes the google play.

is there a solution to this issue ?
[Captivate Android Development] The_Wolf91:
Thanks for the answer, but I don't understand why on ICSSGS and all builds before the release of the first Nightly (including the first nightly) worked without any reboots??
[Captivate Android Development] scidon37:
Perhaps the damage occurred since flashing the first nightly. Try reflashing back to 100% stock and see if the problem persists.
[Captivate Android Development] The_Wolf91:
The damage occured since flashing the SECOND Nightly and I already tried reflashing back to 100% and reflashing last Nightly, but the problem persists...
[Captivate Android Development] Minor723:
I didnt have to reinstall gapps. They were still there after upgrade.

---------- Post added at 01:04 PM ---------- Previous post was at 01:02 PM ----------

http://xdaforums.com/showthread.php?t=1300843

I like the KJ3 version.
[Captivate Android Development] spotdog14:
I have been running one of the nightly's for about 4 days now and overall I think its pretty damn good for being a nightly. Here is what I am still having problems with:

1.) Either car mode is not present or it immediately crashes upon plugging it into a car dock.

2.) GPS takes a lot of time to get a lock but I find that when it does get a lock that it is a lot more accurate than the previous GB releases.

3.) Can you make the icon dock at the bottom of the screen any small? That thing is HUGE

4.) LCD Density changer does not work, it screws everything up, any idea on this?
[Captivate Android Development] Minor723:
How come these are called nightlies but not released nightly? I was looking in the vibrant section and they are released much more often.
[Captivate Android Development] Primus76:
allshare replacement?

Loving CM9. Can anyone recommend a good DLNA server since I lost Allshare? Have Samsung TV's through the house and use it quite often to push videos recorded of our daughter to the family. I know there are a few out there but Allshare worked so smooth I wanted to pick your brains.

Thanks in advance!