yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] havenfx:
been on the ROM for a little less than a day and it is truly stellar. havent come across a bug yet and it's so smooth. Terrific work, teamhacksung!
[Captivate Android Development] codyrt:
Not sure if this is the same issue, but in honeycomb on the Asus Transformer having google instant turnd on yielded the same kind of issue.

I'm not running the ICS build on my captivate yet, I just thought I'd try and help out.
[Captivate Android Development] abuthemagician:
I have the same problem, but when I try to uninstall it tells me the APK cannot be found.
[Captivate Android Development] civ122:
I am rocking this very functional ROM as a daily driver on my only Captivate.

The ONLY issue with this ROM has already been mentioned in the thread - I cannot seem to update or uninstall Google apps. They are not listed in the Applications screen and Titanium Backup is not able to uninstall them either

I cannot believe how functional this ROM was out of the box...It is night and day from the difficulties encountered with GB ROMs first hit the scene

I am loving this ROM and will be a loyal follower of this dev!

Thanks!
[Captivate Android Development] xella:
Install this Email update from recovery.

View attachment Email.zip

Apk's from Nexus port!

For me work! :)
[Captivate Android Development] ChuckDaEngineer:
Yep, tried that. I get the Google calendar to sync just fine. Jorte seems to be where the incompatibility is. Maybe I will try their website and see if there are specific ICS issues. TNX for the reply though.

There may be an issue with where the Google data is stored or my setup. My GoSMS Pro is not associating phone numbers with names from contacts. I have applied both the contacts fix and the calendar sync fixes and the Jorte doesn't see the Google calendars (Google calendar works) and the GoSMS Pro doesn't see my contacts names (regular messaging works fine) but sees the phone numbers OK. Weird. I will try to play around with any data settings I can find and report back later.
[Captivate Android Development] abuthemagician:
This also fixes the Exchange Calendar sync issue I was having
[Captivate Android Development] atinm:
Updated to Build 3 - link in the OP, as is the list of fixed issues.
[Captivate Android Development] gstern:
Seems like nightlies are back. Lol.

Thanks!
[Captivate Android Development] kjdoug:
Thanks I installed it but it still says waiting for sync :(

**edit: I got it working, thanks again!
[Captivate Android Development] nbell13:
Use Root Explorer to delete the system apps.
[Captivate Android Development] poolemit:
omg, i'm seriously in awe of you. BT media audio confirmed fixed! to be honest i wasn't holding my breath as it's not exactly a top priority item. not to mention so damn quickly!

how can i donate/support you guys?
[Captivate Android Development] ChuckDaEngineer:
Become an organ donor per the OP. I am.
[Captivate Android Development] uzbeque:
I used app protecting program named seal. now it is not working with this rom, is there an alternative program?

is it possible to enable battery life percentage?
[Captivate Android Development] SkitchBeatz:
I believe whats being worked on is getting the ROM functional with all of ICS' intended features. Themes will come.
[Captivate Android Development] RichMD:
I also use Seal since my kids use my phone sometimes for games. Please reply if you find an alternative that works well or a fix becomes available. At that point, I will try out the latest build and may keep it as a daily driver.
[Captivate Android Development] viny2cool:
Updated to Build 3...seems little faster now...Google TTS issue is solved and now its going to be my daily driver...Thanks to the CM team..
[Captivate Android Development] MJHawaii:
Awesome ROM it is really miles ahead of everything else with the flavor and functionality. The two issues I am having is the calendar will not sync or even catalog a new event and the email widget is slow in updating ott this is my new choice daily rom I can't wait to get all the little bugs out great job to the devs on bringing ics to the cappy
[Captivate Android Development] emcnelly:
Figured it out...

And awesome work on the port guys this is awesome!!!
[Captivate Android Development] spiritssight:
Possible Bug - Change Input

Hello All,

First I want to say what a great job the CM Team is doing! Next I may of found a bug, now I have not seen anyone post this or show it in the OP so I hope this is new and not a repeat.

Could anyone please conform that changing input by long press on input box is not working?

God Bless,

Christopher
[Captivate Android Development] kangi26:
There is a fix on the Calendar, look back about 4 pages or so http://xdaforums.com/showpost.php?p=19765116&postcount=336
[Captivate Android Development] Mauijpm:
Does anyone have their phone randomly search? My phone will just be sitting and it will randomly vibrate and the search box will pop up.
[Captivate Android Development] zmore:
Sometimes yes; sometimes no. A combo of finnicky capacitive buttons and computer<->usb charging. Haven't had the problem in a while, though (especially sucks in recovery)
[Captivate Android Development] devi59:
Wow fixed low storage

I have no idea what this is (appears to be the onecosmic guys) but there is a download here for DataFix.zip http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list and I used it on my Hacksung build 13 and poof, no more data issues. Thought I'd share it since it bugs me not being able to get my gmail because of "low storage":D
[Captivate Android Development] speedy_11:
It says icssgs in the corner so it for onecosmic build.

It's probably not best to be flashing stuff meant for a different rom.
[Captivate Android Development] devi59:
Thanks, I knew that. I'm not condoning anyone to blow crap up or anything, I'm just saying that whatever it "does" did not appear to "break" anything on this build and it DID fix my "low storage" problem. So whatever it does, I still consider it a "win" in my book. :cool:
[Captivate Android Development] TheEscapist:
It gets rid of the symlink in between /data and /data/data. One of the devs (iirc) said that this would fix the issue, but make things a bit slower.

Either way, its fine to flash on this rom, if you want. It just runs a script, doesn't replace any files or anything.!
[Captivate Android Development] MikalCarbine:
Any suggestions on possible location/GPS fixes?
[Captivate Android Development] kangi26:
I just ran a quick WiFi HotSpot test, I could NOT get a link with my laptop when I selected "Open" security on the phone, but my laptop picked up the HotSpot right away when I selected WPA2 and used a key. It worked great
[Captivate Android Development] shane87:
Ok, I have ran into the reboot bug. It has happened three times now, and all three times I was on a call when it happened. The phone shuts down, then reboots into recovery.

I know this has been reported a few times before on build 13, but I acctually have some more info on it. The last time it happened, the person on the other end reported that they heard a "low pitched hum" just before it cut off. Also, I dumped a log from the logcat radio buffer as soon as I rebooted after the last time it happened. The last two times may be on the log, since they happened less than 5 minutes apart.

One other note: after the last reboot, I had to toggle airplane mode to get my mobile data to connect again.

I will attach the log dump to this message when I get home. My setup is as follows:

Teamhacksung ICS Build 13, stock kernel

Gapps v7.1

Ugkg3 modem (stock for rom)

Setcpu with low battery profile - capped at 800mhz

Setcpu screen off profile - capped at 400mhz

Captivate build 1101

NOTE: The log will have to wait until I get home, around 9am eastern time, cuz xda app does not allow me to attach anything but images.
[Captivate Android Development] b-eock:
sorry...

10 char
[Captivate Android Development] Joecascio2000:
That can't be true. I was using JK4 before and now I'm on KG3. Plus I'm getting way better signal.
[Captivate Android Development] b-eock:
OK, my bad, when both ports started out, there was no modem included. I am sorry!
[Captivate Android Development] Kaik541:
incorrect, this is the exact same installation process as CM7 which has always included a modem (heck, open the zip and you can see modem.bin which has always been there, as far back as build 1 and the first CM7 nightlies)
[Captivate Android Development] b-eock:
My memory is gonna cost me soon... :/
[Captivate Android Development] alkiter:
You're kinda both right. Yes, there is a modem in the zip file. However, if you already have a modem installed on your phone, the modem in the zip file will not be installed, and the one you already have will be preserved.
[Captivate Android Development] shane87:
Are you sure? I had jv3 before I flashed, but the first thing I checked after flash was the about phone screen, and it said ugkg3 for modem.
[Captivate Android Development] alkiter:
Check updater.sh. It looks at the /radio partition. If modem.bin is already there, it will not overwrite. Maybe you wiped the radio before installation.
[Captivate Android Development] shane87:
I see that. The reason mine changed is because I came from non-mtd, so my system got a full re-partition, wiping out my old modem.bin.

Seems I learn something new everyday!
[Captivate Android Development] bentonhall:
Build 13 is as close to perfect as it gets for so far me, however I'm still having reboots during phone calls, is anyone else seeing this?

I'm running build 13 with the stock kernel. This started for me at build 12. It seems to reboot whether using bluetooth or not unless the screen is on. As far as I can tell it only reboots when the screen is dark. Also, on build 12 it would reboot and boot all the way back up on its own. On build 13, it reboots, the AT&T screen flashes twice and it boots into CWM recovery.

I have tried clearing data on the phone app and enabling Sensor Orientation in the Dialer settings as someone had mentioned previously and still get reboots. I'm going to try a different phone app and see if that makes any difference.

Thanks!
[Captivate Android Development] shane87:
Here is the logcat dump I mentioned earlier. I dumped it using the command

logcat -d -b radio >> /sdcard/radlog.txt

I quoted myself so that my setup and the log can be found in the same place.
[Captivate Android Development] torontoninja:
usb

Just wanna say thanks for the great rom. Have been running it for a few days with only the minor problem of it shutting it self off at times but thats no big deal.

What i was wondering is this....is there a way for me to be able to have the usb used as a mass storage device when i plug it into the laptop? I mean show up as both the internal and external drive not the way it is knbow which just shows up as the phone?
[Captivate Android Development] crecsky:
Hey Guys,

As compared to the other ICS rom that is for the Captivate is this one basically as ready for day to day use as that one? The reason I ask is because my Captivate is my work phone, so I would like calls to work if I got them. I'm just asking because there seems to be opinions on either side of the board as I was reading through comments of people troubles.

I also know the battery horse gets beaten alot, but has anyone tried this one and the other ICS rom and can compare the battery time differences?

Thanks.
[Captivate Android Development] cbasse:
Not sure if this is a known issue or not, but thought I'd pass along that I had my phone reboot (to recovery) while in the middle of a phone call. Happened just about 10 minutes into a call I was on. I'm on build 13, stock kernel & modem. I've done no mods to the rom.

This is really the first issue I've experienced, so overall loving build 13!
[Captivate Android Development] NightHawk877:
Thought I would post how awesome the battery life is with this ROM. This was taken yesterday before I went to sleep.
[Captivate Android Development] mbc663:
your battery sucks dood.
[Captivate Android Development] crecsky:
Not sure if fake battery stats...

Or awesome battery.

Seems crazy, I never got 24 hours, even on stock rom.
[Captivate Android Development] MikeyMike01:
Wow, this port has really improved. Went to GB for a while and skipped a few builds. Back on this and it's great.

Sent from my SGH-I897
[Captivate Android Development] mbc663:
this is good battery
[Captivate Android Development] Mauijpm:
What did you do? Turn it on, put it in airplane mode, and stick it in a drawer? ;)
[Captivate Android Development] :
Screen is 18%, I lol'd. :cool:
[Captivate Android Development] mbc663:
Just some light use maybe. 50 texts. Couple hours of music. Data off, sync off.
[Captivate Android Development] Keland44:
oh okay so your manually syncing your mail accounts?
[Captivate Android Development] mbc663:
i always keep sync off, correct
[Captivate Android Development] nate25:
had the problem with not being able to get pass the splash screen. was running build 3 i think then went to build 8. after build 8 i went to 10. then from 10 i tried going to build 13 and then i got the status 7 error. so last night i did a odin back to jf6 and then flashed cm7. tried flashing build 13 and still stuck at the splash screen. i have tried flashing multiple times and no go still gets stuck. now im doing another odin jf6 and gonna master clear again and do it all over but im gonna flash to build 10 first then build 13 to see if that works. ill report back to see if build 10 flashes fine or not

also after trying to flash again i just went back to cm7 and left it and my home button stopped working. just flashed back to jf6 and it works again
[Captivate Android Development] Keland44:
that's coo it probably doesn't help that i'm syncing 8 google accounts whatsapp groupme and twitter :-S

sounds like you might wanna download build 13 again just to make sure it was a complete download and then put it on your device and install it
[Captivate Android Development] nate25:
ya i just started over again to eliminate anything wrong. jusr rooted it now im doing cwm and then gonna flash cm7 again and then build 10. since you said that im gonna go grab build 13 again and delete the one i have now. ill report back. all the other builds were working great before
[Captivate Android Development] bentonhall:
Ok, did some more testing, tried a different phone app and that didn't make a difference. I made a test call from my phone to my work cell and made sure the screen stayed on for about 10 minutes. After that I allowed the screen to dim on its own without using the sensor and it rebooted into recovery again. I used catlog to record the logcat of the main and radio categories and have posted a link to the logfile since the txt file is too large to be attached. I edited the phone number in the log so I wouldn't be getting prank calls. ;)

Logcat

EDIT: Using JL3 modem
[Captivate Android Development] Keland44:
coo yea with you saying all the other builds you tried worked okay that's why i was kinda leaning towards it just being a bad download of build 13
[Captivate Android Development] nate25:
woot build 13 up and running. dont know what happened but its working now. made a big no no though lol. forgot to copy my titanium back up folder last night and lost all my stuff from doing the master clear lol
[Captivate Android Development] Mauijpm:
Before I flash, I always do a MD5 check to ensure I have the correct file. I have never had any issue thus far and I attribute it to this check. Just a heads up because when you take the extra 2 minutes to do this, you can save yourself a ton of headaches. :)
[Captivate Android Development] Keland44:
yup same here
[Captivate Android Development] shane87:
Has anyone else gotten a message on boot about "Android System Upgrading"? I just had a reboot, durring a call. Well, at the end of a call, really. I got done talking, and tried to hang up, but the screen wouldn't come back on. This happens to me sometimes, from the sensor getting dusty, thanks to my otterbox. After wiping the sensor, the phone rebooted to recovery. Since I was in recovery, I went ahead and flashed the alpha cmsettings app from the op, since I forgot to flash it last time I wiped and reflashed. After the bootani finished, a window popped up, saying that the android system was updating, and it was starting apps. On another odd note, after everything settled down, I checked in about phone to see if there were any changes, and my modem is now back to tljl3. Very strange.
[Captivate Android Development] nimper:
The upgrade thing is just the Dalvik cache rebuilding, nothing to worry about.
[Captivate Android Development] shane87:
Ok, cool. I just hadn't seen it before.
[Captivate Android Development] evanstapler:
Thanks for the reply! I've got a new problem, though: When I choose "Install ROM from sdcard" it reboots and shows an android guy with a red triangle alert icon coming out of where his heart would be (haha). It consistently does this... Does anybody know of any other options? My phone is pretty much out of commission until I can solve this.
[Captivate Android Development] gstern:
+1 for that, check-sums save a lot of hassle.
[Captivate Android Development] silvertag:
Sounds like your last flash package got a different cwm version of something alike (i'm no expert). I had the same issue with a kernel flash. Re-wipe, reflash your rom would be my solution to you.. at least that's what i did when the issue happened.
[Captivate Android Development] nate25:
next issue. had megastunt mayhem on and went and got my kid a cup and came back and its in cwm. gonna try again and see what happens

edit: just started it back up and this time it just restarted it
[Captivate Android Development] MikalCarbine:
I can't compare it to the other ICS rom as I haven't tried it but I've been using this as a dd for personal/work with few problems. My battery life is on par with older roms but I guess I'm a heavy user to all these posting 24 hrs of battery without ever using the phone :-P I average 15-20 hours depending on use. I have yet to under volt.
[Captivate Android Development] NightHawk877:
It's a new battery. I found one that didn't need a new door.
[Captivate Android Development] shane87:
Yeah, I would guess the same thing. The onpy problem is that his power button has quit, so he can't do much in cwm.

This is my suggestion. Launch rom manager and choose "Flash Clockwork Mod Recovery", then choose "Captivate (MTD)" on the next menu. Accept all of the warnings, and confirmations.

That SHOULD get you back to a working cwm. Then you can try flashing the package to let the volume rocker wake the phone up thru rom manager > install rom from sd.

I really wish we could get a recovery where home selects, instead of power. I know it is possible. The version of cwm 4 that was included with Cognition 5 used the home button to select. Of course, everybody that didn't read the op closely freaked out and thought something was broken, cuz power button was go back. If we could get a cwm package where home OR power selects, that would be awesome! Thise used to/more comfortable with using power to select wouldn't freak out, and users whose power button is dead could still flash without issues.
[Captivate Android Development] theyurtingyeti:
What is the check sum and how do you do it?
[Captivate Android Development] evanstapler:
Perfect, that worked! Thanks a lot for your help, I can finally use my phone again.

So on a related note, how do captivate owners with a broken power button deal with this? Is there an app I can use that can let me use my volume buttons to lock my phone as well? I'm imagining an app that will let me toggle between my using my volume buttons as a volume rocker and using them to lock/unlock, etc.

And one final question: I guess this means I can no longer use my phone in recovery mode, just use ROM manager to update? And no more booting into recovery via the three button combo?

EDIT: So far I've tried ButtonRemapper (the normal one and the SGS one) as well as Galaxy Tuner, but both of them crash.
[Captivate Android Development] silvertag:
en.wikipedia.org/wiki/Md5sum

http://www.pc-tools.net/win32/md5sums/
[Captivate Android Development] theyurtingyeti:
Ahh, so basically if I do a checksum of the file I download, if the md5 i get does not match the one supplied with the file, 1) something may have happened or 2) I have the wrong file...

Thanks!
[Captivate Android Development] XlAfbk:
could anyone please provide me with a ODIN package that flashs build.prop? I broke mine and now can't access recovery, stuck in bootloop :-( Only mode I can access is download mode but no local backup of a build.prop I could flash with ODIN.
[Captivate Android Development] Slayer_b:
ADB...

Reboot to recovery, mount /system, connect phone to PC, start ADB, copy build.prop from phone to PC, modify it as you wish than push it back to phone, reboot.

Or you can extract build.prop from archive matching your installed build and simply push it to the phone via adb, I think both methods will help to solve the problem.

Edit:sorry, did not notice that you can't boot into recovery, than you have to use adb while bootloops, it should work anyway.

In attachment an original puild.prop extracted from build 13
[Captivate Android Development] XlAfbk:
Recovery mode is not available, the bootloop hits before that.

edit: nope, adb never becomes available :(

edit2: found cm7-galaxys-initial-kernel.tar which got me back into CWM, from there fixing should be easy
[Captivate Android Development] shane87:
No problem! As far as locking via volume rockers, I don't know if that's possible. As a workaround, go to the op and get the cmsettings file. Flash it just like you did the package to enable volume rocker wake up. After reboot, you should have a new app, called Cyanogenmod Settings in your app drawer. Open it up, swipe to the third screen, which should be titled Interface. Tap the Notification Power Widget option, it should be the only optiin available. Make sure you click on the text and not the on/off switch. That will bring up another menu that let's you customize your notification toggle switches. Scroll to the bottom and select Widget Buttons. In this menu are all of the available switches to add to your notification drop down. Tick the checkbox beside the one labeled "Go to Sleep." That will let you lock your phone by pulling down the notification bar and hitting the go to sleep button.

As far as using recovery, unless someone builds a compatible cwm that uses home as the select button, you are out of luck. Of course, most of the recovery options can be accessed through rom manager, including an option to reboot straight to recovery. Of course, getting to recovery would be pointless without a working power button. And download mode can always be accessed by holding vol down + vol up and insert usb while the phone is off.
[Captivate Android Development] J0ESK0:
Just an fyi...

I was bored today and decided to ODIN back to stock, re-partitioning and all. Still, after a complete back to stock and following all installation instructions, I am getting the following issues on Build 13, Gapps 7.1:

Extended power menu:

Reboot to Recovery -> Normal reboot, does not go to recovery, I have to use 3-button combo.

Boot sequence is:

At&t Logo -> At&t Logo -> Boot animation

Hope this helps anyone else having these issues.
[Captivate Android Development] Minor723:
I use my phone all the time. This is the best battery life I have ever seen!
[Captivate Android Development] Minor723:
24% left after 28 hours
[Captivate Android Development] evanstapler:
Thanks so much for all of the advice you've given me, it's been a huge help! Sounds like my phone's completely usable, just slightly inconvenient to get used to.
[Captivate Android Development] Joecascio2000:
Moving to SD Card

I can't get any apps to move to the SD card. I click "Move to SD card" and it turns grey and says "Moving" but nothing happens after that. Also, everything says "Computing" and never loads. Any ideas?

Also, after I try to move an app, I can't install or uninstall any app until I reboot.