yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] GRACO:
Same here.

I removed calendar using Titanium Backup. I don't remember what calendar I removed (there are 2, doh!) , but make sure to backup, because if you remove the wrong calendar will not sync, the good news is that you have a backup so you just need to restore and remove the OTHER calendar...

worked for me.
[Captivate Android Development] Geoff-dev:
Flashed over Build 15 on Friday. No issues, great battery life. Only thing is I too have the two calendar apps and they are different versions but doesn't seem to affect anything.

Did switch my modem from JVR to JVS yesterday as I was having issues at the house. Don't think that was a result of Build 16 just the crappy AT&T service.

Good job guys!
[Captivate Android Development] topiratiko:
whatshappnin guys....I'm on icssgs 4.2 and glitch 14b3 kernel totally satisfied but a curious mind can't help but wonder if the grass is greener on the other side....what are the major differences?
[Captivate Android Development] Cor-master:
So is the encryption unsuccessful bug fixed yet?
[Captivate Android Development] TheSoaresan:
Check this thread out buddy. He posts somewhat of a fix...

http://xdaforums.com/showthread.php?t=1447303&page=4
[Captivate Android Development] simple man:
What he meant was, is this still a hazard of this rom, not what can I do if the encryption failure happens, there's a big difference. If that happens it ruins your internal sd, and you lose all the data on it. Then it's a pain to fix it. I've been wondering if the issue's been fixed myself.
[Captivate Android Development] zuN!:
Changelog under build 13. Is that the confirmation you're looking for?

Sent from my SGH-I896 on Pre-CM9
[Captivate Android Development] Cor-master:
I saw that, I just mean to keep the phone from telling you you need to reencrypt. I'm actually on saurom kk4 gingerbread right now, kinda waiting on that issue to be fixed before I make the ics jump, just don't wanna destroy my internal sd card.
[Captivate Android Development] Cor-master:
Sweet deal, I might flash this next week!
[Captivate Android Development] WindRunnerXC:
Has anyone saved the gapps package out of ROManager? For those of us who would prefer to flash manually than worry about the aforementioned issues with the app, it'd be nice to have around as a backup.
[Captivate Android Development] theytalkalot:
Forgive me if this had come on this build ....but I just had a phone death last night...this whole time I thought I was getting change death... last night had a full charge and unplugged, half way through the night, phone dead. turned it on, still a good charge too...I was thinking of getting a new battery to see if that would help....but I don't think it will..or would it??
[Captivate Android Development] ptesmoke:
i just had a charge death for the first time ever with a 3 week old anker...dont think its the battery personally. i will test again tonight and report back. been on a plane last two days so couldnt test really...
[Captivate Android Development] Nick0703:
Is there anyway that I could increase the stock mms app vibration intensity? Because it's too weak.
[Captivate Android Development] Jesterdtm:
Hi,

build 15, the battery percent % display worked partially (rather than icon), just displaying text. build 16 it does not.

Not sure if there is something i should being doing differently. if this is already addressed, i apologize in advance.

Just do the standard flash of build, plus gapps. Is there a reason that we should not use 7.1 gapps?
[Captivate Android Development] ThreeofNine:
One is Build version : 4.03-eng.pawitp.20120210.202835 and the 2nd is 4.0.3-239410 I don't see a difference in how they're working so I don't think having two or more are hurting anything. You'll only have one active anyway if you're not using another calendar/agenda app, right?

I flashed build 16 over 15, the alternate gapps zip file, and rebooted (no wipe of data or cache) and everything is working great! (FYI: I came from CM7.1 to build 12) 14 hours plus on battery with 74% battery remaining! This CM9 is getting better and better! Great job as usual DEVS!!!
[Captivate Android Development] n0stalgia:
No sub-bass preset for bass boost on DSP settings' "voodoo sound"!

Also, do you need to pre-download gapps and flash it simultaneously with the ROM so that your google account settings won't be lost?
[Captivate Android Development] bryman27:
Yes, that's been my experience.
[Captivate Android Development] ThreeofNine:
Here's the one from post # 5456http://dl.dropbox.com/u/26095738/gapps-ics-20120207-signed.zip
[Captivate Android Development] nyciz:
Pawitp, again much thanks for looking into it. I figured as much but thought I'd share anyway. Any ideas on any other logs I could get? To share a little more info, if I change the Display screen time out to 2 mins and make / recieve a call the phone reboots.

If I change the Display screen time out to 10 mins, it does the same thing. Are there any pther logs I can pull?
[Captivate Android Development] ppmz:
Can ClockworkRecovery 2.x install this ROM?
[Captivate Android Development] b-eock:
Yes as it will be replaced almost instantly, then you will have to battery pull and boot into recovery. Flash again and Viola
[Captivate Android Development] WindRunnerXC:
Thanks, searching for "gapps 20120207" didn't turn that up, for some reason...
[Captivate Android Development] sNoxious:
Thanks for this, I'm looking for this package as well. :)
[Captivate Android Development] TheSoaresan:
(Anker 1800) Battery stats from b16. PM me for other details:
[Captivate Android Development] pandakh:
I need help...already tried flashing 3 times, and still no luck. It gets stuck in a bootloop, the at&t logo shows twice, then the cwm recovery screen appears and runs some commands quickly and boots again... I flashed from cm7 and stock and no luck. Wiped all wipeable stuff...any help?
[Captivate Android Development] AtoZ0to9:
Mine also did that, when it never has before... I pulled the battery, entered recovery, and again wipe data / factory reset, wipe cache, wipe /system... and the flash took... see if that works... if not, youll want to flash to a stock file, preferably with cwm already inserted...

edit: just saw you said flashed from stock... see if it'll take this time... go into recovery, wipe those three, and try another flash, don't flash between
[Captivate Android Development] pandakh:
My phone won't reboot into recovery...even after i entered recovery using the 3 button combo to flash it the first time...Once the bootloop is in action it will not boot using the combo...
[Captivate Android Development] AtoZ0to9:
remove the battery and insert it so its an off phone, hold all three, and let off of power as soon as you see the at&t logo come up, continuing to hold both vol keys...
[Captivate Android Development] goabunny:
Clock works fine for me.
[Captivate Android Development] goabunny:
Running build 3 and experiencing lot of lag between the screen navigation such as opening the app drawer, phone dialer, contacts and etc. Wondering if the lag can be avoided with OC and setting different governor?
[Captivate Android Development] Kaik541:
just as a little warning/advisement:

the next build will require you to wipe everything.

that means going into recovery->mounts & storage->format /system, format /data, format /cache, and format /datadata

then install zip

I know this kinda sucks, but this combined with using the (even newer, unreleased) gapps package will hopefully alleviate all the issues. Including the issues with trying to purchase apps on the market (I ran into this last night when I wanted world of goo).

basically, the gapps we've been basing all these packages on are complete and utter crap so we started over fresh.

Things I've personally tested:

Calendar Sync

Google-photo Sync (both G+ and Picasa I believe, I do not have a Picasa account)

Gmail

YouTube

Android Market (downloading large apps and purchasing apps--hooray world of goo)

Google Voice Search

GoogleTTS

Things I didn't test:

Exchange and/or hotmail email
[Captivate Android Development] Jeff Kirvin:
I'm seeing the exact same issue.
[Captivate Android Development] squishy5:
this is a dumb question but the face unlock add onn is or isnt for the cappy?
[Captivate Android Development] everest.deth:
Not for the captivate, no ffc = no face unlock :(
[Captivate Android Development] singlebeam:
Thanks for the heads up. I noticed that the exchange account doesn't enforce the client security with a password screen.

...fairly certain that my exchange admin didn't change any of the security policies. Suddenly I was able to use the stock exchange service with build3 and not encounter a password requirement. To good to be true?
[Captivate Android Development] pizz0wn3d:
I always get a little bit excited when I see these kind of notices because it means we're getting some big changes :)

I don't really mind the wipes considering TiBu gets me back up and running within an hour or so.

Herp derp Captivate XDA Premium.
[Captivate Android Development] SkitchBeatz:
Seriously? this question happens like every other page. Why would there be face unlock with no front facing camera?
[Captivate Android Development] nbell13:
TGFTB... Thank God for Titanium Backup :p

---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------

I personally think it's silly anyway, and will never use it on my Galaxy Nexus (when I end up getting it)
[Captivate Android Development] pizz0wn3d:
Can we get, "NO THE FACE UNLOCK DOES NOT WORK, YOU DONT EVEN HAVE A FFC FFS! " as a gigantic bold banner on the top of the OP? Maybe then people will stop asking about it after every 10 or so posts.

Herp derp Captivate XDA Premium.
[Captivate Android Development] skynet11:
Unlike any other phone, even the new dual-core beasts, the Captivate can sense your presence through the Force :D

Has anyone seen John Connor?
[Captivate Android Development] atinm:
Modify your build.prop, disable the asserts in cwm or come from an actual Captivate build. The issue is not this ROM, but the others that are using GT-I9000 for Captivate builds and I don't feel like changing this on our side because ours would be incorrect then, and it keeps the riff-raff away anyway.
[Captivate Android Development] froli13:
Long press home then swipe an app right or left to kill it.
[Captivate Android Development] skynet11:
Muchas Gracias

Has anyone seen John Connor?
[Captivate Android Development] MikeyMike01:
Apparently you can face unlock with the rear camera. Haven't tried it myself.

Sent from my SGH-I897
[Captivate Android Development] skynet11:
Great job with this, guys! I haven't posted in the Captivate forum for months since I was on CM7/MIUI the whole time after being on, like, Phoenix 1.x, and just went to the MIUI.US site to post/flash. When I saw this, though, I had to try it, and it's much more feature-complete and stable than most other ICS builds out there.

Even if I had a ffc, my favorite lockscreen is the CM7 rings one. I noticed how similar the ICS lockscreen is to rings, and I was wondering if there will be more unlock shortcuts (like unlocking to Twitter, or another app or two of the user's choice) in a future release. I'm sorry if this has been asked already (but, judging from my thread search, it hasn't). Thanks again for an elite ROM.

Has anyone seen John Connor?
[Captivate Android Development] MikeyMike01:
There's no good reason to have it. Caused me all sorts of problems when it was the only file on my phone and it couldn't boot or mount USB from recovery.

Sent from my SGH-I897
[Captivate Android Development] topiratiko:
What quadrants r you guys pullin?
[Captivate Android Development] nbell13:
1300ish... not a fan of quadrant though
[Captivate Android Development] pandakh:
Did that all 3 times, once the at&t logo is out. I know i have to remove the power button, and I do. After that, it simply boots again, and again. I'll give the phone a full wipe and try again. Thanks for your help.
[Captivate Android Development] AtoZ0to9:
Could be with timing, so i let go of the power as soon as i see white from att logo, i dont wait any longer...
[Captivate Android Development] poolemit:
has anyone figured out how to have the BLN on after a missed call?

works for SMS, emails, voicemails even (i think), just not missed calls
[Captivate Android Development] nyciz:
Curios but how do you get a voicemail without a missed call? (not trying to be a wiseguy but actually curious):confused:

I'm speaking about Build 15 but in the Settings>> Display>> Pulse notification Light is all we have on this build.

I know a few pages back, one of the DEVs said that we will have the ability to config which apps use BLN someday just dont know if Build 16 is that day...lol

************Edit**********

-Had a missed call and not BLN.

-left myself a voicemail and I got BLN (vib. pulsed and the softkeys are lit)
[Captivate Android Development] joedon3:
VM forwarding, or less than stellar AT&T coverage. ;-)
[Captivate Android Development] Razzman:
You should not see a difference, obviously keeping the latest build would be the smarter move, as I did. Having two does have an impact as both will notify of calendar events even if only entered in one.
[Captivate Android Development] nyciz:
LOL....nah the deathstar has bad coverage....lol
[Captivate Android Development] abuthemagician:
Weird issue. I hook my phone up to my car via the headset jack to an audio in on the car radio. When playing music everything is perfect. If I get a call while listening to music however, I have to crank the radio up 20db just to barely hear the caller talking. The volume on the phone itself is up as high as it will go during the call. Any ideas?
[Captivate Android Development] tsuda:
Seems to be better than b16 on stock battery with wifi+3g always on, google sync on...
[Captivate Android Development] sblees:
I always let go of all buttons as soon as the att splash screen appears.
[Captivate Android Development] Raul77:
so guys as promised i am reporting back ! after 4 days of use i thought i do a complete cycle, this is with everything ON, (exchange, gmail, whatsapp bla bla...)

2 Days 4 hours and 56 min. best 20$ i ever spent !
[Captivate Android Development] iphone=closedsystem:
Hey I was wondering if any logcats of the current build from my device would be helpful? (I have never sent / used logcat for anything minus my own personal debugging on apps I have worked on in the past.)

any suggestions?

---------- Post added at 09:27 AM ---------- Previous post was at 09:23 AM ----------

also, I rarely have questions to ask but I have been going into this build indepth;

1. Can you save the ,"background process limits," to save-on-boot?

2. is 203-233Mb's RAM usage at idle? (start up , and with no other apps open / set-open at boot.)

3. How can I donate if I'm broke? (testing, help, shamless promotion?)

---------- Post added at 09:31 AM ---------- Previous post was at 09:27 AM ----------

flashing nightly / sleep deth / AT&T service / AT&T towers / solar flares causing AT&T to lose service?
[Captivate Android Development] shadvich:
Does the BLN stay on forever? I got an email before I went to sleep and when I woke up the softkeys were still lit. Hopefully they aren't too huge of a battery drain, I like the features. I have the BLN control app, but it isn't supported by glitch.
[Captivate Android Development] SkitchBeatz:
LEDs use like NO battery. I wouldn't worry about drain from them as its negligible.
[Captivate Android Development] whipps:
I have been using build 15 for a little over 2 weeks and it is now my daily driver.

I came from build 13 and before that Dlev 5.0 Rom(2.3.4). I have been one of the lucky ones that hasn't had any issues.

Now I found the gapps-ics zip, but I'm not sure what the difference will be if I flash it over the 7.1 I have now. Any ideas or suggestions on if I should flash this or not?

P.S. Thank you Atinm, everyone with Teamhacksung, and everyone with CyanogenMod team. This port is so great it stops me from getting the Galaxy SII T989 from T-Mobile.:D
[Captivate Android Development] popodopolus:
I have a question that I am not sure if this has it at this point or if it will but in cm7 you could set up so a long press of the back button would kill the foreground app.. Does this have anything like that.. I am running build 16 with glitch v14 b3. Sorry if this was already asked and thanks for your reply.
[Captivate Android Development] shane87:
Settings > developer options > kill app back button is what you are looking for.
[Captivate Android Development] pqee:
I love this option since too many apps require you to jump through hoops to exit them.

My only problem with this is multi tapping the back button sometimes triggers this. It also kills my launcher sometimes (Apex). Wouldn't think the default launcher could be killed this way.
[Captivate Android Development] eachitandi:
i know the whole "battery charging issue" as well as "battery % display" has been beaten to death, but i have some screen shots and a bit of info that seems unique to the issue so take it for what its worth. I'm NOT complaining or suggesting anything, just giving the info to those that know what to do with it...

my phone doesn't seem to charge to full 100% (until recently), and it usually is shut off in the morning when i get off after being on the charger. (i know, this is old news). But what is unique is one of these screen shots in particular. I am uploading 2 pics, one is where i rebooted the phone manually because it seemed sluggish. you will see when the phone was done rebooting the battery level was near what it was when i rebooted it. The other screen shot is when i had removed the phone from the charger in the morning and booted the phone up (it had shut off). You will see that the phone is just a little of 90% charged. about half an hour later the phone crashed and rebooted on its own while it was in my hand and being used, But you will see this time after the reboot there is a significant difference in battery level before and after the reboot.
[Captivate Android Development] maizein:
Is this what you guys get too on build 16?
[Captivate Android Development] DaNaRkI:
Don't get what your trying to show... If it's the drop in % after a crash, then I can say from experience that the info gets messed up on any crash. I've had my phone show bigger drops crashing while testing GB ROMs for TC. Funny thing is, if you let it run till the phone dies the overall usage time will be normal. You'll just get it showing a % for a long time between 10%~5%. I've had it stay flatline'd at 6% while playing GunBros for over an hour.

If you can't get it to show above 95% when unplugging about 30min after it first says it's fully charged, then do part of the "calibrate battery" steps: let it run till the phone dies, charge it up while off, let it run till <5%. Since the folks at google decided to tell us that the "battery stats" get reset on every full recharge there is no reason to wipe them, but the displayed % can get a lil out of sync to the actual battery life; especially after an unexpected reboot.
[Captivate Android Development] anjosautomotive:
I don't know if this has been reported as a bug but check my screenshot.

I get this once in a while. Clears up after a few seconds.
[Captivate Android Development] kangi26:
I would say, if it ain't broke, don't fix it"
[Captivate Android Development] sNoxious:
I don't know where to post this but I figure out this would be the best thread, how would you know that it's time to install a "fresh" CM9 on your device? I mean, like returning to stock using Odin, rooting, installing ClockworkMod and whatnot before installing the latest CM9? Cos like me, I've been using CM9 since Build 13 and I'm just flashing on top of it the latest Build every now and then. Is there like a problem with that or would it cost any problem?
[Captivate Android Development] tiuk:
I've been running CM on my captivate for a year, since the first GB alphas. I've never once had to flash to stock. Wiping data and reflashing should fix just about anything. Even that, i think I've only had to do twice.
[Captivate Android Development] RootTheMachine:
Some people claim it's necessary to completely wipe your device in order to eliminate problems. But really it's a waste of time and effort
[Captivate Android Development] sNoxious:
So it's okay to just Wipe Data or do a Factory Reset then flash away?
[Captivate Android Development] popodopolus:
Thanks man I thought I had looked everywhere.. Thanks button clicked
[Captivate Android Development] topiratiko:
The "other" ics rom

Sent from my Galaxy S Captivate on ICSSGS 4.2 w/IcyGlitch v14b3
[Captivate Android Development] Gromlakh:
Or, you could just flash, which is the whole point of having a no wipe installer. There is no point in wiping data unless you're having some specific problem that isn't going away otherwise. All you should have to do is wipe caches and flash away.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] sNoxious:
Yea, that's what I do. Just wondering about the whole returning to stock thing. Oh well, thanks guys for answering. Appreciate it. :)

Sent from my Captivate
[Captivate Android Development] Jesterdtm:
yes, that is about the same as i get. it's about 400-600 less than CM7
[Captivate Android Development] thangphysk48:
I got problem when screen lock. After press power key, screen seem to be not responding. I have to press power key several time.

I'm using glitch kernel b3. Do you think that cause by kernel problem?
[Captivate Android Development] nakedninja42:
Yes, known issue in that thread.
[Captivate Android Development] thangphysk48:
Thankyou. I'll back to older version.
[Captivate Android Development] Fear of Oneself:
They spoke about this issue in the other thread, I found a somewhat gypsy magic way to avoid that. Setting the min CPU frequency to 200Mhz seems to have solved the issue for me, as well as keeping the CPU governor at GlitchOndemand and the I/O scheduler at fiops.

Seems to remain much more responsive for me, however the issue occasionally appears.
[Captivate Android Development] cbasse:
So, I'm beginning to think the low disk space error is not really indicative of the disk space. I have no real evidence of this other than the fact that I was getting the error on early builds of ICS (maybe pre-build 12 or so), then I went through several builds where I never got the error, now on build 16 I am getting it again. Thing is, I really have not added any apps to the phone during this time, even uninstalled several, and I am much more vigilant about clearing app cache on a regular basis. I also just did a complete revert to stock/master clear/reflash build 16 (I did this to hopefully get rid of my phone reboot during a call issue, which I hope to test today), but I immediately got the low disk space error upon booting the phone.

Can anyone else back up this observation? Better yet, can this be investigated by the dev team to see if there's something more to this than meets the eye? Just a suggestion...as I said, I have nothing more than my own experience with this error to go by, and I am far from understanding the stuff "under the hood"...

No matter, thanks for this fantastic ROM! I jumped ship briefly to CM7 and then to the CNA build, but I keep coming back to the THS builds!
[Captivate Android Development] Holmes108:
Yeah, I hadn't had the low space notification since maybe build 12 or so... suddenly I just got it the other day when I installed a single app (and at the time I had less apps overall on my phone than normal)... and a few minutes later it went away all on it's own, without me doing anything.

Since then I've installed numerous apps in addition to that one but haven't seen the message since.
[Captivate Android Development] omriasta:
It's definitely a space issue as you can check the space available on your datadata partition and it is full.

Try this: http://xdaforums.com/showpost.php?p=22183016&postcount=5161

I was weary but it doesn't affect preformance as badly as previous datafixes

and I have installed TONS of apps and all is good!