yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] skynet11:
Thanks! Sorry for the superderp... Had a senior moment when I forgot where it was in settings...

Has anyone seen John Connor?
[Captivate Android Development] spacecase-25:
Que me-feel-like-an-idiot moment
[Captivate Android Development] nightshack0:
Who told you that?

It's not false, it DOES kill it.

Proof:

And actually it even disappears from the running/cached services.
[Captivate Android Development] 105437:
Now that's what I wanted to hear... I'm ALL IN! Flashing this bad boy tomorrow.
[Captivate Android Development] Lollipop_Lawlipop:
It could be that by going back to the launcher, you're forcing the app out of memory.
[Captivate Android Development] gstern:
Just had a drive, and in-call audio did not route to the hands free bt in my car on build 3. When I stopped I played with it a bit, tried to delete paired device, pair again, play with the in-call menu to route audio to speaker and again to Bluetooth, nothing. In-call audio always plays through ear speaker. Worked fine on build 2.

So- media audio routes through Bluetooth, in-call audio does not.
[Captivate Android Development] Koizuma:
Decided to hop back on here and give it more run down and so far i must say awesome work, having no issues other then what was already mentioned in the OP
[Captivate Android Development] DarkisFever:
Minor Error Report:

When opening App Drawer, went into another app from app drawer and back to the drawer had drawer went blank and until I opened another app from main screen the apps did not show back in the drawer. Only happened once just after flashing Build 16.

Phone:I896

Build: 16

Kernal: Stock

GApps: 7.1 Installed
[Captivate Android Development] airtower:
Are the stock THS wallpapers available anywhere? Not sure what happened, but I seem to only have the AOSP wallpapers now.
[Captivate Android Development] capefearless:
Call going straight to Voice Mail

I just experienced my first instance of a call going Straight to voice mail. No missed call notification, just a Google Voice notification.

Build 16

Test Kernel #2

JK9 Modem

Anyone figure out a fix for this?

Other than that no issues to report. I did have one instance of phone rebooting during a call but that has not happened again since switching to Test Kernel #2 as was recommended.

Thanks!
[Captivate Android Development] nkrick:
The KP1 modem is from the GT-i9088 which is a Chinese Galaxy S phone. People say it is a closer cousin to the i897 than the i9000 is, but I don't know why. The i9088 does not have an Audience chip, which is why the modem works well with i9000 kernels and THS/CM kernels. http://pdadb.net/index.php?m=specs&id=2586&c=samsung_gt-i9088_galaxy_s

Edit: it turns out that the i9088 looks like the captivate, similar to how the i9010 (Armani) looks like the Captivate. It is likely that the i9010 and i9088 are close cousins and both are essentially i897's without the audience chip. This means that orientation and button mapping is probably the same on the i897, i896, i9010 & i9088.
[Captivate Android Development] johnhazelwood:
Could the calls going directly to voicemail be a Google voice issue? Seems odd Google voice sees the missed call, but the phone doesn't. A new Google voice just came out a few weeks back. I might try reverting to older version and see if it still happens, though it was very intermittent for me anyways.
[Captivate Android Development] malbolgias:
Test kernel 2

Battery life much improved, I am getting over 50% more than standard kernel.

Voice calls OK. Still getting charge deaths though.
[Captivate Android Development] sblees:
I originally thought that Google voice was the problem so i disabled Google voice and routed everything back to default settings. this was a couple of weeks ago and calls still go straight to voicemail about 20-30 percent of the time.

Shawn
[Captivate Android Development] Chahk:
I'm having the exact same issue. I always thought this was because AT&T service sucks at my work location, but now I'm thinking maybe it's the ROM/kernel/modem at fault.
[Captivate Android Development] MechaGen:
I started having this issue with CM9. My wife's cappy is still on CM7 and she never has any missed calls, especially straight to voice mail. I have two coworkers with stock cappy's that have also say they never get calls straight to voice mail.

I think there is a real issue here, but I'm not giving up on this ROM, it's benefits far out way it's few announces!

Build 16

Stock Kernel

Google voice mail

KG3 modem

Sent from Tapatalk, NOOK Color CM9 Nightly's!
[Captivate Android Development] capefearless:
Thanks for this input as I was wondering myself if Google Voice might be the culprit. I now have had 2 additional calls go straight to voice mail for a total of 3 calls today.

The calls do not appear as missed calls on my phone or on Google Voice. In GV they appear as Voice Mail Messages (not as missed calls) so I have no idea if I am missing calls from people who hang up rather than leave voice mail.

Have others who are experiencing this tried switching modems? Kernels? Any idea if this issue is on showing up on other ICS roms?

I will happily help with some experimentation as well and report back but am wondering what others have already tried before I start randomly changing my set up.

While this could be a fairly significant issue it is thus far merely an inconvenience for me on an otherwise very stable and lovely ROM so I hope we can figure something out.
[Captivate Android Development] jswclw:
Regarding the calls going straight to GB -	I gave seem the phone light up as a call comes in, but make no noise. I think that sometimes it just doesn't ring.
[Captivate Android Development] pintek:
Haven't had app compatibility issues on THS though I be leave the compatibility issue with your ainol novo7 is the MIPS based cpu instead of the normal ARM.

I've been using this as a dayly driver in a pizza delivery job (phone is life for this job) an it hasn't let me down once at all awsome work devs :D
[Captivate Android Development] mbonus:
I have this same issue about 20 - 30 % of calls. No missed calls, just straight to (google) voice mail. Build 14 - stock kernel / gapps 7.1 / ugkg3 base
[Captivate Android Development] Monfro:
Since it became CM9 there is no more that wonderful TeamHacksung wallpaper.. i would like to have it again too
[Captivate Android Development] capefearless:
I did a quick search on the other ICS ROM threads and saw no mention of the issue. Seems like it is affecting folks with different kernels, modems and build numbers of this ROM. Interesting.

Please keep the reports coming, maybe together we can figure out a common enough thread. It might be a tough nut to crack since it is an intermittent problem but hopefully with more data one of the devs or resident geniuses might figure something out.

I hope it doesn't seem like I'm whining too much about this. I really love this ROM but an perplexed by this.
[Captivate Android Development] darvo:
Just for the record, I always had issue with CM7/9 with people calling and telling me I wouldn't answer without having missed call notification. I thought it could be related to modem or carrier but at the end I just got used to it. Also, I noticed that sometimes when my phone rings, it takes a while before I can see caller ID. Sometimes, it only rings once or twice even tough the person calling me says it ringed several times. Like the phone has problem getting out of sleep. This only happened with CM9. Sorry I don't have log. BTW, I don't have voice mail.
[Captivate Android Development] zuN!:
Google Voice is the problem. It could solely be the app or in combination with your location/provider. Nonetheless, it shouldn't have anything to do with this ROM. Why?

Canadians don't have access to Google Voice, thus we usually opt in for our carriers voicemail option. I've never had a problem with missed calls going straight to voicemail or any of that nonsense. I have not come across a complaint from a Canadian that has any of these issues when using CM ROMs. This logically leads to one result - it's either Google Voice or a combination of the app and your provider/area.

Both CM7 and CM9 have been flawless for me in every common phone functionality aspect.

Sent from my SGH-I896 on Pre-CM9
[Captivate Android Development] RockRatt:
+1 here in So Cal have not had this issue on my cappy.with cm9 , my daughters cappy with cm7, my sgs2 with cm7. I do not use google voice but have always used my att's voicemail. I do use google voice for a phone number on my Galaxy Tab with google voice associated with my cell number but did not set up a google voicemail account. So the google voice app is not activated on any of the phones.

EDIT TO ADD ON TO ABOVE AND CLARIFY: It could be multiple things here, the ONLY time I have seen this happen to me is when i happened to actually see it turn on the phone without ringing, this usually happened after flashing a new update. I would find that my ringtone was set to silent and I had to rechoose a ringtone and then i havent had another issue after that. Or it can be a combination of that and google voice as I said above. I usually find out if I missed a call without hearing it as it is usually my wife that calls so she sends a text, then i notice that i had a missed call in my notification bar so i did actually MISS hearing the call but phone showed i missed it, or i turn my phlne kn and see i missed a call. Again I am not using google voice for voicemail but only for a google voice phone number associated with my cell number, then I have my tab set up with google voice on it (without voicemail use) and use groove ip to make/get calls on my tab and make get mms/text.

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] nkrick:
If the issue was Google Voice, then other (non teamhacksung) CM9 builds would likely have the same issue.

The reason why Google Voice is linked to this is that it will show a "missed call" if someone calls, you do not answer, and they do not leave a voicemail. Since in the reported problem the phone never rings, there would be no way to know if your phone is affected without Google Voice, or someone telling you that last time they called you it went straight to voice mail.

In other words, the fact that you don't know that you are missing calls does not mean that you are not missing calls. That would be a bit like saying, "I have never seen a Canadian, so they must not exist." (BTW, I have known several Canadians, that was just an example.) Rogers' users could have the same problem and not know it since Google Voice is not there to let you know that someone called but did not leave a message.

I can say that I sometimes miss a call without hearing or feeling my phone ring (my phone is always set to vibrate, whether my ring tone is active or not). Since it does not happen often, I have assumed that the call came while I was in a dead zone, AT&T did not get my call through even if i was not in a dead zone, or my phone did indeed ring & vibrate, but I was driving my car and didn't notice. I don't have any definitive evidence that I have missed a call that was not due to AT&T/signal or not noticing the incoming call.

Edit: Also, since my wife's Captivate (running stock Samsung/AT&T GB) also rings straight to voicemail sometimes when I try to call her, I am inclined to blame AT&T or possibly the Captivate hardware before I blame the THS ICS ROM.
[Captivate Android Development] malbolgias:
Actually it's not something difficult to test, just time consuming. Who ever is experiencing the problem can conduct a controled test. Using the same hand set first on ICS place 50 calls and see how many go straight to voicemail. Then flash to Samsung gingerbread and repeat the same noting the number of calls. Compare data and you have a valuable hypothesis.
[Captivate Android Development] nkrick:
Make sure you allow your phone to go into deep sleep between each call though. I think there is relative agreement in most of the posts about this problem that a call was missed while the phone was in deep sleep.
[Captivate Android Development] capefearless:
Status Bar missing

Out of curiosity, I decided to test drive the ICSSGS ROM briefly today. Didn't like it as well as this Rom and so came running back.

When I restored from my nandroid backup my status bar was missing. I wiped all Data and cache and restored again from nandroid but still no status bar.

I looked around in the settings but can't see anything that might have changed.

Any suggestions before I wipe everything again and start over with a new install?

TIA
[Captivate Android Development] RockRatt:
Just go and wipe dad's alvich cache and install the SAME nightly build yoj are using over the top. Yoj wont lose your apps or anything, you may have to reflash gapps also at the same time but if you do it before the reboot you shouldnt have to set anything back up.

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] ptesmoke:
lol i did the same. ths is too perfect had to come back. i faced the same issue with no status bar from a restore. i reflashed the build 16 and gapps and all was good. though i later wiped and started fresh just in case.
[Captivate Android Development] kangi26:
Thanks for the feedback......

Really diggin the auto correct ;)
[Captivate Android Development] capefearless:
Thanks for the advice, but too late. I got impatient and went ahead with a full wipe and restore from scratch. Not too bad though with tubu.

Thanks for playing!

---------- Post added at 10:09 PM ---------- Previous post was at 10:02 PM ----------

So what do yo say to the user below who was experiencing the issue both with and without using Google Voice? My first inclination was to suspect GV but this seems to shoot a fairly sizable hole through you "it is Google Voice" theory.
[Captivate Android Development] galakanokis:
I am on a Rogers captivate (Rogers BL's) and I am getting the calls straight to voice mail.

No indication of the call unless they leave a message. I've had it happen from land lines and cell phones. Even people that call frequently. No rhyme or reason to it that I can figure.

Sent from I896 running ICS
[Captivate Android Development] sblees:
Eventually i will install a different ics ROM to see if the forwarding issue goes away. I would have done it a week or so ago but have been too busy. If someone else has done this and the problem went away, please report it so we can determine if it is ROM related or not. I'm currently running stock build 16. I haven't changed the kernel and i think I'm on froyo boot loader.

I need to do something soon though or else my wife is going to kill me for "messing" with my phone. Lol

Shawn
[Captivate Android Development] zuN!:
So if users who use Google Voice are not the only ones with the problem, then it can be a combination of many things:

-Provider

-Area

-Modem

-ROM

-Kernel

-Scripts

-Background Apps

-GB Rogers or AT&T Bootloader, Froyo Bootloader

-Method of flashing (I don't think this is viable as a reason but just throwing it out there)

Point being, there's a lot of factors to consider in trying to find the issue for this. Maybe it's the ROM, could be the stock/test kernel. If so, then why is this not an issue for the entire user base of THS's ICS ROM? If it was the entire user base then there would be a larger outcry and it would be more obvious to the devs. They would likely address the issue to give a confirmation that they recognize the issue as a universal problem for the ROM's user base.

If you're going to point fingers and state that the problem only exists in THS's ROM, then please try the other ROMs out extensively rather than briefly, as you have stated here:

Besides trying out different ROMs, try different kernels/modems/factors listed above and see if there's a change in the missed call/voicemail issue. If it's only an issue for a certain handful of people then it's hard on the devs to find the issue, unless they made some sort of mistake somewhere; I doubt that's the case or else everyone using this ROM would have this issue - everyone including myself.
[Captivate Android Development] lowlymarine:
Is there possibly something going on with the mirrors? I downloaded B16 from the haxer.org mirror and flashed it after a Cache wipe over B15 + Glitch 14 B3, but got stuck in a boot loop with the little Android guy and some really quickly scrolling text that would dump me back to recovery. Tried re-downloading it a couple times, wiping everything imaginable, multiple installs, etc, same result every time. The eriador.org mirror wouldn't even finish downloading, always erroring out right near the end. I re-downloaded B15 from the Mediafire link and rolled back, and it booted right up first try with nary but a Cache wipe before installing.

Also, I wasn't able to wrangle the search into finding me an answer to the chicken-and-egg problem of:

"Google Apps: Download from ROM Manager."

"You need to update ROM Manager to the latest version. *Crash as it tries to load a market link*"

I just installed the GAPPS 7.1 .zip I still had. Is that how it's supposed to be done?

Edit: Today I re-downloaded from the eriador.org mirror successfully and was able to reflash B16 and Glitch 14 B5 without incident after only a cache wipe.
[Captivate Android Development] mcnutty:
Personally, I haven't had a charge death in a really long time, but i tried the nexus s radio a couple of days ago and have had three charge deaths since. Changed back to the previous Ugkg3 and going to see how things go tonight.
[Captivate Android Development] Monfro:
Maybe someone needs this.

Sent from my Captivate
[Captivate Android Development] capefearless:
I never said it was the fault of the ROM. In fact I asked earlier for users to post their configurations so that we might see if there is a common thread other than the ROM. So far configurations have been all over the map and so it is inconclusive at best. And as I also mentioned myself, it might be difficult to narrow down for the devs.

Insofar as your theory that since it doesn't affect all users goes that it must not be the ROM... That simply doesn't hold water, there are plenty off issues that are intermittent or that only affect some users (in call reboot for instance).

Finally, one of the main points of this thread and alpha/beta testing is so that users can bring potential issues to the devs attention.

So relax. I love this ROM despite whether or not it turns out to be the root cause of this minor issue.
[Captivate Android Development] lothos:
I always cringe when people say they had a "bad download". At the most basic layer, IP networks have checksumming to prevent corruption on noisy, lossy data links (which most people don't have). If the file size matches the one you tried to download, the chances of it being randomly corrupted are tiny. If the size doesn't match and your web browser doesn't alert you to an incomplete download, shame on your browser. If you didn't flush all cached writes to your phone's memory card before unplugging it, shame on you.

Get a free checksum generator, run it on the file from your HD and the file on your phone and compare the hashes with the hash value posted in the first post of the thread. On top of that, zip files themselves are checksummed, so it shouldn't even work if it is corrupt, and you can run winzip or something and test for corrupt files. If winzip says nothing is corrupt and the md5 checksum doesn't match, then you are obviously the target of a government conspiracy.

If you do this, you will *know* whether or not the file was corrupted or something went wrong during the process of unzipping and copying files on your phone's internal memory.
[Captivate Android Development] ThreeofNine:
Here's the one from post # 5456 http://dl.dropbox.com/u/26095738/gap...207-signed.zip
[Captivate Android Development] ale3alfaro:
i want back to stock or downgrade from CM9 to CM7.1 can anybody Help me plzzzzz.
[Captivate Android Development] speedy_11:
Flashing Mods could also fall under your list too. In a since that people maybe flashing mods meant for older builds and other possibilities like mod breaks something on error

Read the op, under installing section it says how to downgrade
[Captivate Android Development] nyciz:
XDA's Swype Beta article....

Are you using Swype as ur keyboard? I've been since I first flashed ICS B14. Yesterday XDA dropped this arcticle

Does this mean that Swype was not supported on ICS? And no I'm not running the beta version from the article currently I got ver 3.26.92.37604

Curious if others are running it.

TIA

***Edit#1 2/22/12***

-signed up for the ICS Swype Beta

***Edit#2 2/22/12***

-uninstalled prev swype & installer,

-requested email invitation to get new installer for beta

-now on ver 3.26.92.38303
[Captivate Android Development] theyurtingyeti:
Next steps for rom

Note: I'm not asking for an ETA :)

But I've seen the posts about new servers for nightlies again, and I was curious if there was a planned build 17+ or if the next step was to move from build 16 to nightlies again?

Thanks for all the hard work. I'm still running build 15 and going strong!

Please disregard. I'll post this question in the Q&A.
[Captivate Android Development] Gromlakh:
There's a difference between "supported" and "runs just fine." I've been running Swype on this phone since Build 13 and haven't had a single issue with it.
[Captivate Android Development] theyurtingyeti:
I've been using the beta version on ICS and LOVE IT!
[Captivate Android Development] Holmes108:
Yeah, I've run it since the very first builds even, with no problem. Apparently there was a problem with the Nexus... but it was apparently more about the screen resolution than ICS itself. But since the Nexus was virtually the only ICS handset, it's been considered that Swype wasn't compatible with ICS.

As far as I've known it has run just fine for everyone running ICS on other devices, including the Nexus S official ICS... it was only the new Nexus that had problems.
[Captivate Android Development] kangi26:
I've also run swype from the very first ICS builds from both THS and Demonwav. the only time I've had any issues with Swype,was when I tried the soft button mods. Otherwise, it's run flawlessly
[Captivate Android Development] nkrick:
There have been plenty of reports stating that the missed calls issues occur across many different modems. I think we can safely eliminate testing different modems.
[Captivate Android Development] ale3alfaro:
Ok i read but i dont understand how to flash twice plzz help me! :confused:
[Captivate Android Development] Gromlakh:
Flashing twice is generally a fairly complex process. These steps may be difficult to follow, but hopefully you'll somehow trudge through it:

STEP 1: Flash the installer.

STEP 2: Flash the installer a second time.

If, by some miracle, you've survived those two incredibly difficult and confusing steps, then congratulations, you've successfully downgraded. Treat yourself to a beer or something.
[Captivate Android Development] know50:
Don't know if this will help but I was having some missed call issues at first with the i897 modems. I switched to the i9000 modem jjjv5 and haven't had the issue anymore (knock on wood). Anyway I just wanted to throw that in there. Maybe try some i9000 modems but yeah it may not be a modem issue at all and I just got lucky. In any case good luck
[Captivate Android Development] Saint Wacko:
Heh, just found a bit of bugginess in the thing that keeps the last used item at the top of the status dropdown. I have build 16 downloading, and some of my apps are updating themselves, and they all keep shuffling around, trying to stay at the top, so the whole dropdown is constantly changing. :)
[Captivate Android Development] Phoenix-Lead:
That's completely normal. It is a feature, or so they thought to make it a feature of ICS.
[Captivate Android Development] Saint Wacko:
Right, it's just odd that there's nothing to stabilize it and keep it from constantly changing. I would expect it to stop changing after a second or so.
[Captivate Android Development] nyciz:
LOL...I hate to say it but thanks for the laughs. I hate to say cuz its at some1's expense and we were all noobs at sometime....esp me!:D