yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] pawitp:
There's technically no reason preventing it, but it's a nuisance for the user having their internal SD card wiped every time they want to switch to a different ROM.
[Captivate Android Development] tselling:
Custom recoveries were used that didn't wipe the internal emulated sdcard on the devices I used.
[Captivate Android Development] cannondaleV2000:
The recovery would just have to be modified to not wipe data media. I figure partition it like the note 2 si the sdcard and data partitions are one partition and your sdcard is in data/media and just modify the recovery and a few kernel related things and it should mount fine and then sdcard won't get wiped when you wipe data. Once I fix my cappy or replace it il eventually re lease a custome kernel with that implamented
[Captivate Android Development] pawitp:
I'm talking about switching between ROMs which expect a partitioned internal sdcard and one that expects /data/media.
[Captivate Android Development] sleeper994:
Installed this today, and all I gotta say is DANG THIS IS FAST!!!
[Captivate Android Development] cannondaleV2000:
O right all the roms would need to be modified too. Well there's a road block
[Captivate Android Development] tselling:
Has anyone else had the problem of the 2 included launchers losing apps from home screens on reboot? The apps lost seem to be the ones transferred to the sdcard. Before I download another launcher... wanted to hear about others experiences.
[Captivate Android Development] droyd666:
I'm on the 20131212 nightly and there's nothing nightly about it. I can't imagine it being more stable than this. No problems to report as of yet.
[Captivate Android Development] ManaSV93:
In Battery Info, My "Phone" app uses around 25% of the battery, that make a very fast batt drain on my phone.
[Captivate Android Development] Val D.:
Same here. No issues whatsoever. :good:
[Captivate Android Development] p.chi:
And you keep on keeping this Captivate alive ! Thank you pawitp !!

I don't use my Captivate as a phone, no sim card in it. I'd like to remove the Signal strength icon from the notification bar, is there or will there be a straight forward way to do it like before?

Also is there a way to stop the phone and related services (messaging) without it going bonkers on me?

Bonkers meaning = I froze them on 4.3 and upon reboot received a continuous popup error re: the phone services not running. It was a pain to navigate and unfreeze the app to stop the errors and make the 'phone' usable again. I don't want to go through the errors again so I thought I'd ask for some insight.
[Captivate Android Development] pawitp:
Customizations will be gradually added. I suggest you don't stop core services, even if you don't use them since other services may depend on them. You're on your own if you choose to.
[Captivate Android Development] remixkilla:
Can I remove apps like Google+
[Captivate Android Development] Klitoni:
I hope stable cm11 will be released soon :D
[Captivate Android Development] PxGold:
Just switched from CM 10.2 (stable) to the latest nightly - aside from loosing the icons on my home screen the upgrade went smoothly. Response times seem to be much better similar to when I first bought it several years ago. One small nitpick. If you choose the option to not have the Google search bar on each homescreen page you cannot remove an icon (app shortcut) on the homescreen. The removal of an icon works fine with the Google searchbar on all homescreens turned on.
[Captivate Android Development] sleeper994:
Only bug I've noticed is that incoming call sreen takes a while to show up. phone starts vibrating and ringing and it takes about 10 secs for incoming call screen to show. Doesnt matter if Im using an app or phones just laying down locked. Is anyone else facing this problem?
[Captivate Android Development] afaneh92:
Known issue, due to our old hardware.
[Captivate Android Development] aznracer62:
I searched the thread but couldn't find someone with the same problem. When i'm installing the zip, it gives me an error saying that the file is meant for an i897, and that my phone is an i9000. Has anyone ran into this problem? I swear i have a captivate lol. I'm coming from a slim rom.
[Captivate Android Development] pawitp:
You can, it's around that position and the icon will turn red. That, or just "throw" it off the top. Not perfect, but the Launcher is not my area.

Probably because your ROM is probably misrepresenting your phone as an i9000. Revert to the stock ROM or flash to another kernel which properly presents itself as a Captivate before flashing (don't ask me which one though).
[Captivate Android Development] rcsredmage:
When i try to use my cappy as AP, it's trying to run, but then writes error in status. After that i cannot turn on wifi until reboot...
[Captivate Android Development] pawitp:
Logcat please.
[Captivate Android Development] rcsredmage:
That's what i've got...
[Captivate Android Development] pawitp:
You need to be root if you want to take logcat from your phone (not using adb), otherwise you won't have any useful information.
[Captivate Android Development] rcsredmage:
Now with su... Sorry for previous...
[Captivate Android Development] rcsredmage:
One more: once i boot the location notification toggle is active, the other time i reboot it' inactive. In options it says it's activated in low battery usage...
[Captivate Android Development] pawitp:
Did you ever restore any /data? I think the SELinux permission is wrong (CWM doesn't handle them too well yet). Run this in a root shell to clear all wifi data and reboot.

rm -rf /data/misc/wifi

I'm not sure what you mean
[Captivate Android Development] rcsredmage:
That's it. I restored the data. Now, after cleaning, all is ok.
[Captivate Android Development] afaneh92:
My phone turned off while charging at night, need remove battery to turn it back on.

Was on stock kernel.

Phone lost some updates when its boot like Google mail or Google+ etc.

PS: happened on my kernel when use cm ramdisk.
[Captivate Android Development] CuriousTech:
1215-1217 had the battery missing in settings, and stayed at 100%, but 1218 works again, now with the separate percent option.

Just a headsup and that may have just been for non-clean updates.
[Captivate Android Development] PxGold:
I installed the latest nightly (12/22) and tried the camera app. When I tried to switch to the movie camera it forced close the app. I have not tried the movie camera on the previous nighties of CM11. I tried deleting the cache and data of both the Camera app and the Gallery but that did not help. I switched to CameraMX from the Google Play and it works without any problems. I guess I will stay with that app until the problems with the CM camera app is resolved. (Also the CM camera app does not allow saving to the external SD card that feature was available in CM 10.2.

One other minor problem when I update to the latest CM nightly after about 10 minutes CM does a soft reboot - it only does this once and after I do a reboot it is stable and I do not get any more reboots as long as I stay on the current nightly.
[Captivate Android Development] desiromeo719:
Im running this rom with Neat Kernel and am having problems using the cm ota. It downloads the new nightly, but on reboot into recovery gives me an error (status 7) i think....Also unable to update manually in recovery...What can I do to update?
[Captivate Android Development] pawitp:
Revert to the stock kernel and try again. Custom kernels come with their own recovery which may not be supported.

See first post on how to report a bug.
[Captivate Android Development] desiromeo719:
I guess what I'm asking is... How do I revert to stock kernel when it won't let me install the rom to go back to stock kernel? Can the kernel alone be found somewhere or can you please tell me how to extract it?
[Captivate Android Development] Nihar:
You will have to flash another kernel and try again...

Because the neat kernel is based on the sources of vibrant, the update script thinks our phone as a vibrant..
[Captivate Android Development] PxGold:
I assume you are writing about the soft reboot. Do you also want a report on the camera app?
[Captivate Android Development] pawitp:
You can extract the boot.img from the zip and install it with heimdall, or install other kernels with working recovey which doesn't check the device model before installing (don't ask me which).

Both reports, separately.
[Captivate Android Development] PxGold:
For the random reboot the instruction states:

"If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)"

I found last_kmsg using X-plore (I could not find it using ES File Manager) although both had root access. Do I need to wait for just after a reboot to give this to you? Never mind I found the answer - see below.
[Captivate Android Development] desiromeo719:
I have extracted the boot.img from the latest cm rom but am unable to flash it using flashify as it doesnt seem to support this phone. Is it possible to replace the boot.img with the neat kernel zip? Is there any other way besides heimdall? Can I try to install semaphore kernel for 4.3 just long enough to flash the update?

edit - figured it out...flashed gear kernel then did the update. All good now. Thanks!
[Captivate Android Development] PxGold:
What is your--

Phone model:Captivate

Radio (baseband):

CM version:11-20131222-Nightly-captivatemtd

CM Download url:from CM updater

Gapps version:gapps-kk-20131208

Did you--

wipe:no

restore with titanium backup:no

reboot after having the issue:yes

Are you using--

a task killer:no

a non-stock kernel:no

CMSettings/Performance settings (other than stock):stock

ART Runtime:no

other modifications:no
[Captivate Android Development] PxGold:
I answered my own question the log contains entries since yesterday and I updated my system this morning.

What is your--

Phone model:Captivate

Radio (baseband):

CM version:11-20131222-Nightly-captivatemtd

CM Download url:from CM updater

Gapps version:gapps-kk-20131208

Did you--

wipe:no

restore with titanium backup:no

reboot after having the issue:yes

Are you using--

a task killer:no

a non-stock kernel:no

CMSettings/Performance settings (other than stock):stock

ART Runtime:no

other modifications:no
[Captivate Android Development] pawitp:
Please describe your problem in detail when filing a bug report even though you might have described it already in a non-bug-report post, otherwise I have no idea which is which.

- If you're taking a logcat on the device, you need to do it as root otherwise it won't have any useful detail. You need to take it right after the force close.

- For a soft-reboot, last_kmsg is not relevant. You need to take a logcat the very moment it reboots using adb on your computer. Normally, it'd be pretty hard, but you've said that it happens quite consistently after installing a new nightly, you can leave it hooked with adb logcat running and recording until it reboots.
[Captivate Android Development] PxGold:
What software do I use on my PC running Windows 7 to do an adb logcat? Generally up until today my Captivate would not come out of the soft reboot and I had to force a hard reboot. Today with a little prodding I was able to do the soft reboot.
[Captivate Android Development] pawitp:
http://wiki.cyanogenmod.org/w/Adb
[Captivate Android Development] sleeper994:
How do I add lockscreen widgets? Im running a 20131212-NIGHTLY versiona of CM. There is no that plus sign when I swipe from left on lockscreen.
[Captivate Android Development] pawitp:
Read FAQ
[Captivate Android Development] PxGold:
this is for the Camera application. I booted in the Safe Mode to help avoid interactions with other programs. The camera works fine taking pictures but when I attempt to switch to the movie camera the program crashes. You should have several attempts to switch to the movie mode with crashes.

What is your--

Phone model:Captivate

Radio (baseband):

CM version:11-20131222-Nightly-captivatemtd

CM Download url:from CM updater

Gapps version:gapps-kk-20131208

Did you--

wipe:no

restore with titanium backup:no

reboot after having the issue:yes

Are you using--

a task killer:no

a non-stock kernel:no

CMSettings/Performance settings (other than stock):stock

ART Runtime:no

other modifications:no

Their are several people on the S I9000 CM11 thread also reporting the same problem with the camera when going into video mode.
[Captivate Android Development] PxGold:
I downloaded and installed the Google adt bundle but I could not find a terminal program that I could use with Windows 7. I tied a few but they would crash or not function correctly (or possibly beyond my technical understanding). Since the soft reboot only happens on my first launch of the latest OS and then it is stable I guess I can live with it. I also tried on one occasion to reboot the kernel before launching a the latest nightly an on that occasion I did not have a soft reboot. I will try that again on my next nightly.
[Captivate Android Development] pawitp:
Should be fixed in next build

http://review.cyanogenmod.org/#/c/56220/
[Captivate Android Development] p.chi:
Great work, I'm now on nightly 1224. Boot loop (1219 nightly) is gone for me. Camera is working fine for me also with no force close when changing to video.
[Captivate Android Development] cell2011:
Everything is great for me except when i make a call it goes dark? Pulled away from ear still dark. Worked fine on stock 2.3.5. Call goes through and everything but i have to pull the battery to end the call. Im on 20131119 gapps kk zip
[Captivate Android Development] PxGold:
I believe the problem may be in the updating software. I always do a manual update (I download the update from the CM updater option in the setting menu but I do not use the CM updater to do the update. Instead I manually reboot into recovery and do the update.) This morning I tried the CM updater to do the update and I did not get a soft reboot!
[Captivate Android Development] winning0308:
Hi, my Captivate got the problem with internal storage so I've edited the Vold.fstab file use the method at this thread. Now I'm using CM10.2, is there any way to edit the path of internal and external storage like that method so I can use CM11? Thanks :o
[Captivate Android Development] Nihar:
You can use the neat kernel with inverted SD..

You can fond that on its thread..
[Captivate Android Development] cesierra:
the deal breaker for me was:

1. No Flash support

2. No bookmarks sync

3. No App sync

Has any or all of this has been fixed?
[Captivate Android Development] falcon7204:
Using the latest PA-Gapps mini modular package, my apps synched just fine. Dunno about the other two, but i use Firefox and sync bookmarks between devices with no problem.
[Captivate Android Development] PxGold:
I finally figured out how to do a ADB logcat. I didn't realize you could launch it from the command prompt in Windows after installing the Google adt for Windows. Also I was in error about my Captivate not doing a soft reboot if I used the CM updater. I tried it again today and it did a soft reboot after about 10 minutes - also before the soft reboot my Captivate starts to become unresponsive, but as I have previously stated after the reboot the Captivate works perfectly (until I do the next nightly). I don't understand why it didn't do it the first time I tried the CM update installer - perhaps because their was only one update in that nightly. Hopefully I can provide you with ADB logicat in the next day ot two.
[Captivate Android Development] droyd666:
I get a few sleep deaths like once or twice a day and sometimes none for a while. I restored apps with titanium backup and I'm using default performance settings.
[Captivate Android Development] johan8:
I also have the similar problem.

The default min. freq. is 100Mhz, this will cause sleep deaths. Even in stock rom also have sleep deaths.

by set min. freq. to 200Mhz, no more sleep deaths, but phone will reboot after couple hours of idle.

If set min. freq to 400Mhz, it looks better sometimes phone will reboot after over 10hours of idle.

So I believe it is hardware problem.

Another problem is CM11(android4.4.2) not that smooth.

Compare with Dirty Unicorns(android4.3), DU rom is much more smoother, even the free ram is more or less the same, also 5MB~50MB left after bootup.

I don't know it is CM or KITKAT problem.

Anyway this is already an old hardware.
[Captivate Android Development] PxGold:
I finally figured out how to do a ADB logcat. I didn't realize you could launch it from the command prompt in Windows after installing the Google adt for Windows. Also I was in error about my Captivate not doing a soft reboot if I used the CM updater. I tried it again today and it did a soft reboot after about 10 minutes - also before the soft reboot my Captivate starts to become unresponsive, but as I have previously stated after the reboot the Captivate works perfectly (until I do the next nightly). I don't understand why it didn't do it the first time I tried the CM update installer - perhaps because their was only one update in that nightly. Hopefully I can provide you with ADB logicat in the next day ot two.

After the soft reboot I let the adb logcat run for about 15 seconds.
[Captivate Android Development] pawitp:
You need to run it like "adb logcat > log.txt" not copy from cmd.exe, otherwise it will only contain the very last pages with formatting jumbled up.
[Captivate Android Development] PxGold:
I will try it tomorrow if their are enough changes to trigger a soft reboot, I did the logcat using the warnings and above filter.
[Captivate Android Development] PxGold:
What is your--

Phone model:Captivate

Radio (baseband):

CM version:11-20131222-Nightly-captivatemtd

CM Download url:from CM updater

Gapps version:gapps-kk-20131208

Did you--

wipe:no

restore with titanium backup:no

reboot after having the issue:yes

Are you using--

a task killer:no

a non-stock kernel:no

CMSettings/Performance settings - stock

ART Runtime:no

other modifications:no

I was in error about my Captivate not doing a soft reboot if I used the CM updater. I tried it again today and it did a soft reboot after about 10 minutes - also before the soft reboot my Captivate starts to become unresponsive, but as I have previously stated after the reboot the Captivate works perfectly (until I do the next nightly). I don't understand why it didn't do it the first time I tried the CM update installer - perhaps because their was only one update in that nightly. Hopefully I can provide you with ADB logicat in the next day ot two.

Instead of waiting for the Jan 2 update I reverted to the 12/30/2013 update which also caused the soft reboot. (Originally updating from 12/30/2013 to the 12/31/2013 update did not have enough changes to cause a reboot).
[Captivate Android Development] pawitp:
It may be due to having too many apps on your SD card for the system to handle within the time limit.
[Captivate Android Development] PxGold:
I had the same number of apps with the same amount on the SD card under CM 10.2 and never had the soft reboot problem. Also why would this happen only on the first boot after installing an new nightly but if I reboot again with the same nightly I never have the soft reboot problem?
[Captivate Android Development] pawitp:
The system has to load every apps on a new install to "optimize" them (generate dalvik-cache). As for why it didn't happen in CM 10.2, I'm not sure. Maybe the code was changed to be more time-sensitive.
[Captivate Android Development] PxGold:
If the system has to load every app into the dalvik-cache then in theory if I wiped the dalvik-cache (and the regular cache) and then rebooted it would simulate installing a new nightly, yet when I do this the system will boot and no soft boot ten minutes later occurs.

PS I sincerely thank you for looking at this problem and the fantastic job you have done and are doing maintaining this smartphone!
[Captivate Android Development] pawitp:
It's simply what I could see from the log. It's hard to debug it further without having the device with the problem. IMO, just do a data wipe or ignore it
[Captivate Android Development] Nihar:
CyanogenMod 11.0 M2 Release has been uploaded....

:laugh::laugh:

:good::good::good:
[Captivate Android Development] 7he8ob:
3G issues

Hi everyone! Im wondering if you all are getting 3G? I all I get is the E. Every rom I've flashed from JB to Now i haven't seen the full 3G. It flickered on JB but never stayed. I have trouble receiving texts sometimes. When i had Eclair i had perfect 3G everywhere. I haven't seen it on KitKat. Im on cm-11-20140103-NIGHTLY right now. Any help guys? Thanks!
[Captivate Android Development] juntoa123@hotmail.com:
Did you try going to settings > more (under wireless and networks) > mobile networks > preferred network type > change to 3g?
[Captivate Android Development] 7he8ob:
Ok I went to mobile networks and it was set to 3G but i set it to 2G then back to 3G and now i have the H symbol for HSPA

From what im reading online, the H means 4G but im sure this phone isnt new enough for all that.
[Captivate Android Development] Nihar:
H is the symbol for the 3G

E is the symbol for 2G
[Captivate Android Development] Val D.:
I'm currently using CM10.1 based ROM and the phone is constantly showing H on Canadian Bell/Telus HSPA network. Download speed is about 2.5-3Mbps, more than enough for most applications.
[Captivate Android Development] 7he8ob:
Ok, Thank you all for the speedy reply! I was just wondering about the 3G since it has the symbol but it only flickers but if H is 3G then all is well! Thanks again!
[Captivate Android Development] PxGold:
I decided to to a system wipe - no more reboot after 10 minutes and the phone is working a lot smoother!
[Captivate Android Development] Klitoni:
Anyone flashed latest snapshot ?
[Captivate Android Development] ManaSV93:
Me, but on battery stats "Android OS" show me around 55%, so, battery life isn't good.. at least for me
[Captivate Android Development] PxGold:
Just installed the 1/11 nightly and after about 10 minutes the phone did a soft reboot. The phone does work a lot smother so the wipe was useful. I guess I will just have to live with it, but as long at the phone works smoothly I am happy.

Thanks again for your work with this phone!
[Captivate Android Development] Val D.:
Is there still a lag with Phone app?

In early nightlies when someone calls you or you call someone the screen was going black for 2-3 seconds.
[Captivate Android Development] pawitp:
Waiting for the fix to be merged

http://review.cyanogenmod.org/#/c/57224/
[Captivate Android Development] PxGold:
Keep InCallUI in memory should be in the next nightly (1/21/14)!
[Captivate Android Development] sleeper994:
Would you mind letting us know if this happens? Thanks in advance
[Captivate Android Development] PxGold:
It is in the 1/21/14 nightly.
[Captivate Android Development] sleeper994:
Dirty flashed latest nightly, InCallUI is fixed indeed.
[Captivate Android Development] sleeper994:
Does OC work well with stock CM kernel? Has anyone tried it yet?
[Captivate Android Development] PxGold:
I am using 1.2ghz which is the maximum OC option CM offers for the CPU without any problems (I set the minimum cpu speed to 200mhz). Every CPU is different an while some may OC without any problems others may exhibit glitches.
[Captivate Android Development] rj101:
hands free "Okay Google" command

Has anyone got the "Okay Google" working from the homescreen? I loaded CM11 Snapshot on my Galaxy S3 and got it working fine, but on the Captivate, I can't figure out how to repeat the success. I've tried reloading the ROM, wiping, different GAPPS, loading the search, the Google Experience Launcher, the Google Home APK, and not a darn thing works. That's really the best feature on CM 11; anyone else had success on the Captivate?
[Captivate Android Development] sleeper994:
http://xdaforums.com/showthread.php?t=2526478 read the FAQ