yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] zmore:
Misc notes since flashing build13:

Zero sleep deaths (never had any with any CM ROM anyway; did with Cognition, though)

Zero system FCs.

CAMERA: One crashboot whille using camera

CAMERA: When toggling between Picture and Video recording, Picture taking becomes extremely laggy - sometimes taking up to 10 seconds before the shutter clicks. Have to exit and (kill) restart the Camera app.

Bootloader hubbub: Still using the stock Eclair. BLs are boring and get too much false credit/blame for misc issues.

Voice-set alarms still not working

Other than that, a flawless build. Oh, my Fightclub wants to know: What's the ETA on a public beta? :)

(And I'm NOT using Glitch, unlike so many another bogus posts flooding this thread that the devs have to sort through)
[Captivate Android Development] slayp00n:
could my camera not working be related to Glitch>
[Captivate Android Development] baghera1979:
Camera works for me using glitch v14.
[Captivate Android Development] nimper:
Kernel screen is NOT supposed to do that. Order should be AT&T Logo -> Cyanogen splash screen -> Boot animation, with no repeating of anything.

What he's reporting is AT&T Logo -> AT&T Logo -> Boot animation, which is not normal.
[Captivate Android Development] slayp00n:
The app just opens to a blank black screen
[Captivate Android Development] know50:
Go back to stock kernel and see if it still happens
[Captivate Android Development] J0ESK0:
Ok so it's not normal then.. Well. It's been a loooooong time since I Odin'd back to stock and started fresh. Maybe it's time I give that a whirl with the next build that's released. I would imagine that would solve this problem. Thanks for letting me know that what I'm experiencing is not the expected results.
[Captivate Android Development] know50:
Try wiping everything including going into mounts and storage and wiping everything but emmc and SD and reflashing 13 and gapps before you Odin back to stock.
[Captivate Android Development] dillonc:
Ok I re-downloaded everything and still no luck. Its strange because I used the same download to put build 13 on my girlfriend's phone as I tried on mine and Im getting the red screen tint. Build 12 gives me the same problem. I have pretty much exhausted my knowledge of workarounds and things that I thought might work, so if anybody happens to replicate this and fixes it, pm me on how to fix it!

I would normally think this is a hardware related issue, but my screen looks perfect on anything other than build 12,13 and RC2. I guess ill just have to wait for build 14 to see if there is an improvement.

Im open to any advice from the community!

Thanks
[Captivate Android Development] J0ESK0:
Would that include formatting /boot as well? That's one thing in mounts and storage I've never touched when trying for a clean install.
[Captivate Android Development] know50:
Sorry I couldn't help more. I hope you get it worked out cause I know it would drive me nuts

---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------

Yes format boot also
[Captivate Android Development] J0ESK0:
I just wiped davlik cache, cache/factory reset, then formatted everything besides emmc and sd card, including /boot. Flashed Build 13, Gapps 7.1 and CMSettings. Stiil getting AT&T Logo -> AT&T Logo -> Boot Animation. Also, still not able to enter Recovery through the extended power menu. I'm beginning to think even flashing back to stock, won't solve this problem and I'd hate to go through all that just to find out it was a problem with the ROM and not my phone since others are experiencing this as well.
[Captivate Android Development] know50:
I hate to say it but I think Odin might be your only option. I don't know why you're getting the att splash screen twice. It sounds like the kernel isn't taking or something like that. Try flashing back to cm7 doing all of the same wipes to see if you can get cm7 to boot up. Remember that you'll have to flash cm7 and gapps twice when going back from ics. First time is just to get the cm7 recovery then wipe all and flash cm7 and gapps again fix permissions then boot. If you still see the splash screen twice then I would use Odin. By the way just throwin it out there, I love Odin. With every problem that I couldn't fix Odin did with ease. I know its scary but it hasn't done me wrong yet:-)
[Captivate Android Development] airtower:
glitch V14-preview5 (some mouthful) restores reboot to recovery from the power menu.
[Captivate Android Development] cyberbandit1998:
Can you post the link for preview 5
[Captivate Android Development] eliminat:
http://androtransfer.com/tk-glitch/CM9-kernels/Glitch/Captivate/

Preview 5

It's got quite a speed boost as well.
[Captivate Android Development] FireFriend:
Amazing!! Well done. I use it for day to day use. That's how stable I believe it is.
[Captivate Android Development] nkrick:
I just flashed directly from CM7 "stock" nightly 181 to ICS build 13. I also get the AT&T Logo -> AT&T Logo -> Boot Animation, but everything seems to work just fine. Until/unless one of the Dev's mentions that it is an issue that needs to be fixed by doing something specific, I am not going to worry about it.
[Captivate Android Development] rye&ginger:
Only different I have noted from 12 to 13 is radio connections seem flakey.

12: wifi and cel network on and off's were quick, never really spent time in the grey/not connected to Google mode.

13: wifi seems to take a while to connect, both wifi and cel network spend more time in grey signal mode.

using stock 13 with Gapp fixer.
[Captivate Android Development] J0ESK0:
Thanks for going thru this before I decided to. I also experience no problems with the ROM itself.. just the reboot to recovery doesn't work. Everything else is pretty much flawless.. so I'm just gonna stick with the dual At&t screens even as much as it pains me to see it twice heh.
[Captivate Android Development] speedy_11:
This should be in the glitch thread not here.

I've always got att boot screen booting twice then boot animation, since updating to ics . But recovery commands works fine (i don't use glitch Kern). Not that big of an issue for me
[Captivate Android Development] RootTheMachine:
Exactly... That's why I said you shouldn't worry about it. You can't do anything to fix it besides flashing glitch kernel

Sent from my ICS i897 Captivate
[Captivate Android Development] nkrick:
The double AT&T boot screen and problems rebooting into recovery are not related. I can reboot into recovery from the power menu just fine.

My best guess is that a file is missing from build 13 (or permissions are wrong), so if you didn't already have it from an earlier build, it fails to load the file and ends up showing the previous boot screen/file instead (but I could be completely wrong).
[Captivate Android Development] havenfx:
Hm, coming from MIUI. Formatted data and installed ICS build 13. Stuck in a boot animation loop now. Help?
[Captivate Android Development] nkrick:
3-button back to recovery and flash again.
[Captivate Android Development] havenfx:
Nevermind. Went back to recovery, cleared data, and it worked. hnnnggg ICS is awesome.
[Captivate Android Development] richsale:
I'm on build 12 and want to go to 13. I still have the problem when in recovery when I choose 'choose zip from sdcard' it does not bring me to my sdcard but back to 'install zip from sdcard'.

On the list of 'choose zip from sdcard' is 'choose zip from internal sdcard' which is actually my external card. I know you are not suppose to flash from the external sdcard.

This leaves me with no way to flash new builds that I know of.

My questions is is there a way to change a zip to a odin flashable tar ?
[Captivate Android Development] galakanokis:
What does your home button do? When I was on another ROM /kernel (the other ICS I believe) the power button was a back button so I had to use the home button.

It acted funny, the way you describe anyways.
[Captivate Android Development] evanstapler:
I posted this in the Q&A thread, but since school is starting tomorrow I need a fix for my phone asap, and unless I can come up with one my phone's close to unusable (unless I have access to a power source).

I decided to try out build 9 a bit ago, and I loved it. Two days ago I updated to build 12, but about a day after installing it the side button (power/unlock button) on my captivate stopped functioning. It won't work in recovery or during normal use. I can access my phone by plugging/unplugging power sources, but it's getting tedious... Would this problem be related to updating to build 12? Can I fix this? I can't use my phone without a power source nearby, and it's becoming an issue.
[Captivate Android Development] richsale:
The home button does nothing in recovery. The power button works it sends me back in a loop.
[Captivate Android Development] Mauijpm:
Someone posted a file in this thread over the weekend that would allow your volume rockers to wake your phone. Search for that and I believe it is a flashable zip. That should solve your power button issue.
[Captivate Android Development] evanstapler:
s

So I found the zip file I need, but without the power button working how can I flash it?
[Captivate Android Development] shane87:
You SHOULD be able to flash it by using rom manager.

NOTE: I have NOT tried flashing anything in this manner, and so I can't tell you for sure that it works, but it is an idea to try.

Open rom manager, choose "Install ROM from sdcard." This will give you a list of files on your internal sdcard. Choose the zip you downloaded, and answer yes to all warnings/confirmations. That should reboot you into cwm, and start the flash without needing to use the power button.

Again, I have not tried this method out personally, but it is at least an idea to try, and should work. I hope it helps!!
[Captivate Android Development] galakanokis:
What kernel are you on?
[Captivate Android Development] voldomart13:
Thanks that helped also I updated to the newest version which has further support to ics =)
[Captivate Android Development] RootTheMachine:
Make sure the back button is disabled by pressing Vol up then Vol down in recovery

Sent from my ICS i897 Captivate
[Captivate Android Development] richsale:
What came with the rom build 12

---------- Post added at 09:19 PM ---------- Previous post was at 09:11 PM ----------

Did that.

The problem is when I choose 'install zip from sdcard' it goes to 'choose zip from sdcard'. I than choose 'choose zip from sdcard' and it goes back to 'install zip from sdcard' back and forth never to where I can choose something to flash.

I came from Illuminance with no problem and today went back to Illuminance and back to build 12 and still have the problem.

Can a zip rom be made into a odin flashable tar?
[Captivate Android Development] theyurtingyeti:
MORE THAN USER DATA in /datadata

I have 51 apps installed under build13 and root explorer shows 66MB of data in /datadata. That'd be an over 1MB average per app...

Looking at the data listed in 1-tap cleaner, I'm way under that average. I had read that there was a bug in an earlier build that was saving app data (non-user data) to the /datadata partition.

Could this bug be back / not fully fixed? Any troubleshooting I (or anyone else) could do to confirm this?

____

Ok, things aren't as they appear... I just installed a few more apps and now root explorer only lists 34 MB of data in /datadata and the /data partition went down by quite a few MB as well. Perhaps the phone moves stuff around more after the install (temp files or something?)
[Captivate Android Development] RichIrish:
Cannot restore contacts

Hi everyone,

First off.. Build 13 is awesome. No troubles so far. I've been on it for about 24hrs.

I do have an issue with restoring messages and contacts. I was on Android 2.3.3 prior to ICS Build 13. I used TiBu to backup everything on 2.3.3. But now I am unable to restore contacts and messages. Any help in this regard is greatly appreciated, else I might have to consider going back to 2.3.3. :(

Thanks in advance.
[Captivate Android Development] shane87:
This is caused by the difference in db structure between samsung-based roms and cm-based roms. As a work around, go back to a samsung-based rom and restore contacts and messages. Once you have your contacts and messages back, there are other apps on the market that will backup contacts and messages, and they work differently from tibu, so they can back up accross incompatible roms. For messages, I use sms backup/restore. I can't remember the app I used for contacts, but it doesn't restore. Instead, you can use it to import your contacts into your gmail account, so that they will sync regardless of what rom you use. Then you can flash back to ics, and use the apps to restore messages/sync contacts.

Its a PITA, but at least it gets your messages/contacts backed up and restored.

I hope this helps!
[Captivate Android Development] Joecascio2000:
Yeah I have 125 of 168MB. It seems really high. The first time I flashed I got a phone space running low message too. But I flashed again and its gone. Now datadata/ seems to be getting too high again.

Edit: 89 User Apps
[Captivate Android Development] fishfingers15:
I'm on Build 13, but my sync is not working. I receive emails on my exchange email, but my calendar doesn't sync. And when I go to my account and sync, It says there's a problem with my sync and it'll be on soon.

Any suggestions.
[Captivate Android Development] Joecascio2000:
Did you read this??

Also, sometimes that just happens. Try to wait it out and see too.
[Captivate Android Development] fishfingers15:
Thank you Joe, I did try that Fixer program I think. I'll probably try to reflash this thing and see if it works
[Captivate Android Development] Joecascio2000:
Well in regards to the above, I've had that happen many times when sync is just down. It normally syncs when ever it can. You can try and make it manually sync by unchecking calendar and rechecking it.
[Captivate Android Development] fishfingers15:
Hi Joe, just to be sure, I logged into CWM and reflashed the Apps fixer program again and tried the Accounts and sync. I can sync everything from contacts, emails but just not calendar. If I manually sync it by unchecking, it just says Sync is experiencing problems and it'll be back soon.
[Captivate Android Development] Joecascio2000:
Yeah just give it some time. If it's still like that after 24 hours then it might be something wrong. Like I said sync is sometimes spotty like that.
[Captivate Android Development] torontoninja:
ok i have a problem maybe some can help me with....i am currently on another ics rom and when i tried to flash this a bunch of stuffed popped up saying something about getprop and something about e:error in /sdcard/teahhacksung_captivatemtd-ota-eng.BUILD13.zip

what did i do wrong?

i wiped everything
[Captivate Android Development] MrOpportunity:
re-download the zip file, that always solves it for me. i think its caused by an intermittent data connection, or losing reception if you're downloading the build over 3g. if that doesnt help, wipe again, download from a computer, copy the file over, and flash that one. if that doesnt solve it, then you'll have stumped me...
[Captivate Android Development] torontoninja:
actually I did dl it from the computer and tried to install it 3 times already.....weird....

thanks
[Captivate Android Development] Joecascio2000:
What rom were you on before. Try doing it the CM7 way.
[Captivate Android Development] torontoninja:
i was on icsgg i think it was called and i used the clockwork way
[Captivate Android Development] Joecascio2000:
Yeah but supposedly it's more successful to flash from CyanogenMod 7. So if your having problems doing it one way, why not try another way?
[Captivate Android Development] slow_DC4:
I don't think you can flash cm7 or this rom through cwm from icssgs because icssgs shows the phone as an i9000, and cwm won't flash because they are captivate roms. I was having the same problem and it would give a status 7 error, if I'm not mistaken. What I did was flash to a stock captivate rom, I used ki2 no bootloaders, then flashed cm7 then this rom.
[Captivate Android Development] Moronig:
I've seen two bugs that apparently no one else reported. I'm on build13, with gapps7.1, flashed on top of build12. These bugs happened on build12 as well.

1) Occasionally I turn the screen off, and the button backlights stay on, indefinetely. Unlocking the screen and turning it off again maked them shut down. I've tried changing the timeout settings, but it doesn't seem to make a difference.

2) When auto brightness is enabled, and I'm on a dark room (brightness is low on the screen) the screen gets a little *brighter* before shutting off due to timeout.

-----------

Bugs aside, is there any way I can install gtalk with video on top of build13?
[Captivate Android Development] TonyStark R.I.P.:
Hi guys, thought I could get this going before I headed out for the day.... No love. I cleared everything twice prior to install. All works good until splash screen (ICS color spectrum) the phone won't come out of it. Last evening it continued for more then an hour. This morning I tryied installing the rom again # butt>Recovery>flash rom. Once again (now for a 1/2 hr) still just ics color screen. I realize it says in OP and in CWM first flash will take longer then normal.... In all my flashing, I've never seen one this long.
[Captivate Android Development] cyberbandit1998:
No it should only take about 10 min at most. Did you go into recovery and wipe data. If not try that and then reinstall ics
[Captivate Android Development] TonyStark R.I.P.:
Yes my friend delvik>cache and data/factory.
[Captivate Android Development] devi59:
After going to build 13, it seems the low space problem is back for me
[Captivate Android Development] shane87:
You might try reboot to recovery, select Mounts and Storage, then choose the options to format everything except for /sdcard and /emmc. Then flash the ics rom, and gapps if wanted, and see what that does.

If that doesn't work, you may need to odin/heimdall one-click to stock (jf6 is recommended) and start over, going to stock, then cm7, then ics. It can be a PITA, but it will usually fix most problems.
[Captivate Android Development] richsale:
Some nice mods here:http://xdaforums.com/showthread.php?t=1425183
[Captivate Android Development] TonyStark R.I.P.:
great call. Thank you sir and good morning
[Captivate Android Development] cyberbandit1998:
You may have to flash back to stock and start all over.
[Captivate Android Development] MikalCarbine:
So far build 13 has been solid for me minus some known issues. However I noticed my location settings don't work at all. I can't get a general location while browsing or in maps nor GPS. I have gapps 7.1 and the fix installed. Did I miss something or is this already a known issue
[Captivate Android Development] lothos:
My general location is way off from what it used to be. It's playing hell with Locale. I might go back to CM7 temporarily to see if that is really the difference.
[Captivate Android Development] lpfansether:
Flashing gapps fixer fixes the alarm clock plus and the voice alarm issues as well.
[Captivate Android Development] theyurtingyeti:
From my massive dealings with /datadata, I found that the folder contained 'system data' that took up far more space than the user data did. EX. Of 172MB, 111 was system data and 38 was user data. That caused occasional low space errors.

The only way I was able to get rid of the system data (for good) was to flash back to stock and do a master clear.

As I've added apps back I've been monitoring all the data storage (my original post), and I thought I saw a large amount of user data stored, but when I checked later, it was back to what I'd expect.

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

Awesome... I had installed fixer yesterday so that might be why everything worked well this morning :)

---------- Post added at 10:17 AM ---------- Previous post was at 10:14 AM ----------

Open disk usage, and under Root Options select /datadata. Is there a section under /datadata that is 'system data'? If so, how many MB is it? Unless your apps are super data creators, 89 apps should not be posing a problem for low storage.
[Captivate Android Development] Mauijpm:
For item #1, go to display and make sure pulse notification light is unchecked.
[Captivate Android Development] zmore:
A 'factory wipe' in clockworkrecovery will also format /datadata, so flashing to stock isn't necessary.

Move (or uninstall) as many apps as possible to the external SD to reduce /datadata usage.

To see what your datadata hogs are: du -sc /datadata/* | sort -rn | head -20

Google+ is by far my biggest hog, but can't be moved.
[Captivate Android Development] theyurtingyeti:
That's not entirely true. Both from factory reset and manually formatting /datadata, i still had 100+ MB of 'system data' on a completely clean install with no added apps. I'm not sure where it came from, but something latent sticks and couldn't be gotten rid of - believe me, I tried all options.

It wasn't until I flashed stock that the 'system data' went to less than 3MB.

I would try all the other options first as they are easier than going back to stock, but it took me forever to find a solution, so I want it out there as much as possible :)

Perhaps one day I'll understand where all that latent data came from and why I couldn't get rid of it, but I'm happy it's gone now!

Oh, as for moving apps to the external SD card, that only works for apps that have user data stored in their own folders in /datadata. It didn't do anything for me because none of my apps had more than 3MB of user data (app average was less than 1MB = total of 38MB). Virtually all of my space was being taken up by the aforementioned 'system data', which was unaltered by moving apps to the SD.
[Captivate Android Development] Saint Wacko:
I've noticed the second one when I'm reading. I have the brightness turned down in my ereader app, and when it's about to time out, it gets brighter. It must just be set to go to a specific brightness before timeout, no matter what brightness the phone is currently on.
[Captivate Android Development] krisvek:
You can change this brightness level in cmsettings I think, defaults to 20
[Captivate Android Development] kusabikuri:
I had this issue since build 10 even with the gapps fixer. I just stuck with 5.3 and location services all work now.
[Captivate Android Development] Saint Wacko:
Nice find. I just wish someone would make the Crysis battery mod for ICS
[Captivate Android Development] zmore:
Notification bug?

Has anyone noticed that over time some apps have had their notifications stop working?

I play WordFeud like a bad habit, and suddenly I'm no longer getting notifications when it's my turn. I've tried toggling notifications in the app settings and rebooting, with no change. (going to try wiping the app data/cache next to see if that helps).

(Missing notifications for a few other apps too)
[Captivate Android Development] SkitchBeatz:
that seems to happen to me when I upgrade to a new build. I often have to reinstall Twitter if I want push notifications.
[Captivate Android Development] eliminat:
Everytime I reload WordFeud I have to re-change the notification sound in WordFeud settings.
[Captivate Android Development] jerkysh:
I noticed this in the build.prop , is this still gingerbread?? :D "ro.build.id=GINGERBREAD"
[Captivate Android Development] rye&ginger:
Im quoting a few posts here as they are all related, I was also having this problem.

As mentioned by someone yesterday, it seems TiBu batch restore may be the problem.

I have been able to view /datadata status in Ghost Commander and selecting info for that folder.

The warning seems to come when there is ~20mb of space left.

TiBu had restored some game data there which took a massive amount of space. Try using an app like DiskUsage to visually view /datadata, which may show some bad boy app causing the problem. ( https://market.android.com/details?...wOSwiY29tLmdvb2dsZS5hbmRyb2lkLmRpc2t1c2FnZSJd )

On b13 I am now able to install more apps to Internal, so that is better than it was on b12 for whatever reason.