yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] nyciz:
One thing that I do no matter what ROM I'm flashing (ICS/GB/Froyo based) is install a app called 'GPS Test' by Chartcross. Once installed after a ROM flash, run it, goto Setting by hitting the physical Menu key, at the top there are 2 buttons.

"Clear aGPS" and "Update aGPS", I do a "Clear aGPS" this clears the aGPS aiding data from the phone. You should do this id your GOS takes a long time to lock to a sat.

"Update aGPS", this the aGPS aiding data (sat info over head basically) can become outdated, this jsut request the latest.

My personal results on THS Build14 &15 have been better than on any other rom, avg right after a reboot the gps locks signal in 8-15 secs of launching Navigation. Most times I have sat lock before Navigation completes fectching the route.

On another note, most roms Devs, have set the proper server in the roms but remember the best server is based where you are located so if in EU I wouldnt use "north-america.pool.ntp.org"

Check this post for more specific settings for GPS if you live in the US. This isnt a fix, its more of trying to get a cappy's gps to get sat lock and work.

---------- Post added at 04:07 PM ---------- Previous post was at 03:36 PM ----------

Hi nkrick, could you post a link to KK4 but more importantly the issue that was being resolved?

Thanks in advance.
[Captivate Android Development] shaker2k:
Can you post a link for the kh1 modem please. Don't have a computer (on the road right now)and searching through the XDA app is kinda iffy

thanks
[Captivate Android Development] radicaleggnog:
Try this: https://market.android.com/details?id=com.simplyapplied.sign

If I recall it should be able to do what you listed.
[Captivate Android Development] shane87:
Just had my first sleep death. I sent an mms message, locked my phone and put it in my pocket. About 10 minutes later, I pulled it out to wake it, and got no response on pressing the power key. I tried a few more times, as some times my power key is finicky with my otterbox. After I confirmed that the phone was dead, I held power + vol up + vol down for a few seconds and got a vibe, so I let go of the keys, assuming the phone had shutdown and was rebooting. However, nothing happened. So I hit the three-key combo again, and held till I got a double vibe, then the att splash, followed by cm splash, followed by clockwork recovery. I hit reboot system now, and the phone booted successfully. After boot, I had lost about 8-10% battery. The battery was between 68-70% when I put it in my pocket (don't remember exact number), but after boot it was at 60%.

My setup:

1101 build captivate

Kk4 gb bootloaders

Ths ics build 15

Build 15 stock kernel

Tljl3 modem

I wasn't running logcat when it died, so I have no log dump to share.
[Captivate Android Development] nkrick:
The original post about a fix in the bootloaders was from Kaik541. When I found the post today I noticed that it doesn't specifically say the fix is in KK4, so it could have been in an earlier GB bootloader too. At the time I originally read the post, I assumed the fix was in KK4 because he says that is what he is running. See post below (keep in mind that the post was before they stopped supporting i9000 bootloaders on the Captivate):

---------- Post added at 04:07 PM ---------- Previous post was at 03:54 PM ----------

I sounds like your phone may not have been dead, rather you may have been in a state where the screen would not come on. A couple of people have posted information about what initially appeared to them to be sleep deaths, but they were able to tell that the phone was actually still powered on (got a sound, or a vibe, or were able to adb to their phone, or something else that indicated that it was not actually dead).

I have have never had a sleep or charge death, but one time on build 13, my screen would not turn on. I would have thought it was a sleep death had I not been talking on the phone when it happened, so I knew it wasn't dead. I think some of the reported sleep deaths may be similar occurances where the phone is not dead, but for some reason the power button won't turn the screen back on. I have not had a reoccurance of the issue, so I have not gotten a logcat for the devs. For anyone else, next time you have what appears to be a sleep death, if your computer is handy, plug in and see if you can adb to it and get a logcat.
[Captivate Android Development] iphone=closedsystem:
Just wanted to say thanks for all the hard work on the build, really enjoy the speed of Dev and how clean everything has gone.

Side Notes: Is there any way to get the, "Turn off boot-animation," to work or is that sitll a work in progress? (will re-edit post after reading thread again.)

Still having issues with the AT&T logo flashing twice upon reboot, no issues functionally just wondering if this is a issue specific to my device alone.
[Captivate Android Development] remroux:
Hi,

I just had my first major bug. Actually I still don't know what happened. I was running build 15, and didn't have the GB bootloaders.

I was just checking my data consumption when the phone rebooted, the ICS boot screen was very dark. After a few minutes the phone was still stuck on that screen. I decided to do a battery pull, and reboot it again.

This time it managed to boot but I got an "encryption failed" screen, telling me that I had to factory reset my phone. I restarted a few times just to be sure, but I always got the same message. I decided to do what the message said, factory reseted the phone.... And still got the same message.

I went into recovery to try to wipe the things from there but it didn't help. I also noticed that I couldn't wipe my dalvik cache, I tried to reflash ICS but my sdcard wasn't accessible.

I decided to go back to stock via Odin, flashed back to 2.1, and there the phone wouldn't boot. I had the AT&T screen, but after a few seconds it would stop booting and give me the battery charging screen. I decided to flash stock Rogers 2.2, and same problem, the phone wouldn't boot, I could go past the Rogers screen, but thats it. I flashed Speedmod kernel to see if it would change andything, and I manage to boot the phone, but my sdcard is still innacessible and a get a lot of FC. When going into recovery I'm still not able to access /mnt/sdcard.

I don't know what's happening, any help ?

Thanks!
[Captivate Android Development] J0ESK0:
Check this out for help:

http://xdaforums.com/showthread.php?t=1447303

Hopefully this will get you back to where you need to be..moral of the story is to NEVER click the "Reset phone" when the message appears.. but how were you supposed to know that? Sorry man.. hope you get it straightened out.
[Captivate Android Development] remroux:
Thanks for the link, I'll try the micro sd card method...
[Captivate Android Development] TonyStark R.I.P.:
A little help if someone might. I searched for external sd card and found many, MANY hits. So let me frase the question as such

Has anybody figured out how to use Root EX (on release 15). When I get to external_sd, there are no files to view?
[Captivate Android Development] Fear of Oneself:
notification suggestion

I've noticed that the notification drop down is set up slightly different than every other version of android I've used (eclaire, froyo and gingerbread). On older versions, on going applications would be default at the top of the list, (ie. music player, juice defender, msn etc.) and notifications (ie. texts, emails etc.) would be neatly tucted underneath

With ICS, it seems as if the most recent of anything will jump to the top of the list in real time, regardless of type. (notification or ongoing) I find this presents an issue for me because I have juice defender running, and list to music for hours everyday. So when I unlock my phone to answer a text, data turns on and I have to wait for a bit while the notifications organize themselves so I don't end up advancing songs when I want to open up messages...or shut off data when I want to change songs.

...This is just something I've noticed, isn't a big deal, is that an ICS thing? Can it be disabled to have the notifications lie in the traditional manner? Thanks

That's scary how it can mess up your phone so hard. I was reading though that thread, and I had one question, incase you knew. If you end up getting that error in build 15 (I'm curious, because I use this rom as my daily driver). What are you supposed to do?

Perhaps battery pull and odin 1-click at the first possible oppurtunity?
[Captivate Android Development] singlebeam:
I think what you are looking for is located under emmc. Hope this helps.
[Captivate Android Development] TonyStark R.I.P.:
Thanks mate, I owe you a thanks.... So is there an explanation as to why?
[Captivate Android Development] GRACO:
Im using this KP1

http://soggycashew.weebly.com/uploads/8/3/8/2/8382536/radio-cm7-ics-captivate-znkp1-signed.zip

And I have this as "back up" JL3, just to get back is something happends.

http://soggycashew.weebly.com/uploads/8/3/8/2/8382536/radio-cm7-ics-captivate-tljl3-signed.zip

regards!
[Captivate Android Development] J0ESK0:
Honestly.. I don't really know, because thankfully this has never happened to me. However, looking at the guide.. it recommends "Don't press it!(Reset phone) and then Try rebooting a few times with your external sdcard out first."

I'm guessing that resets the sdcard and /data partitions somehow. I would ask the OP in that thread for more info. ;)
[Captivate Android Development] TonyStark R.I.P.:
Does anybody have info regarding inversion of color on contact list and mms app? I remember when I was on my sgs2 there were apk's to change these.
[Captivate Android Development] J0ESK0:
Check this out:

http://xdaforums.com/showthread.php?t=1425183

Scroll down for the Inverted contacts and MMS. Also some slick battery mods :D

*these will work on the captivate
[Captivate Android Development] TonyStark R.I.P.:
You have used these? They work on I897?
[Captivate Android Development] Smasher816:
I will try.

Although the i9000 and i897 roms are practically identical, the main difference is just the kernel.

So i would assume it would work. Whats the worst that could happen, reflash cm9 in recovery?
[Captivate Android Development] TonyStark R.I.P.:
Tried it, works great:)
[Captivate Android Development] J0ESK0:
I've used the battery mods on my captivate and they work without a problem.. can't say about the inverted apps but I wouldn't see why they wouldn't. Just make a nandroid back-up before flashing just in case.
[Captivate Android Development] richsale:
I use the battery mod and the boot animations. No problem. On I897
[Captivate Android Development] diabolik711:
Mine was doing the samething when I had froyo bootloaders. Try updating to kk4 gb att bootloaders.
[Captivate Android Development] shaker2k:
Thank you very much!
[Captivate Android Development] J0ESK0:
Can also confirm flashing a stock Gingerbread ROM will remove the double ATT screen. I used KJ3 with bootloaders from this thread:

http://xdaforums.com/showthread.php?t=1300843
[Captivate Android Development] sinichi21:
For those who want perkamod statubar and quickpanel style here is a flashable zip i know perka would be busy so I tried to port it on build 15 here it is its a newborn3 battery mod and center date (I have only tried this on CM9 build 15)
[Captivate Android Development] kangi26:
As I understand, Google Android source uses emmc as the standard location for the external SD. Why that was not the case with the 2.1, 2.2, 2.3 ROM's; I have no clue

Also, (if I'm not mistaken) it's the same with Linux as well
[Captivate Android Development] b-eock:
It wasn't the same in 2.1, 2.2, or 2.3 because Samsung modified the kernel(which is how the mounting point is changed). And they will probably do it again for their first true ICS phone...
[Captivate Android Development] ptesmoke:
thanks for this! the bootscreen and inverted mms is genius! wish there was an inverted email mod...;-)
[Captivate Android Development] apbthe3:
http://soggycashew.weebly.com/cm7miui--ics-modems.html
[Captivate Android Development] rustyshakelford2:
My power button has been very unreliable since build 14. I have to press it many times to make the screen come on, and then when I turn the screen off it flickers. Updating to build 15 and clearing the dalvik cache didn't help. Any suggestions on how I could fix this?
[Captivate Android Development] Kaik541:
I don't know why you're convinced it's the kernel and why you keep repeating this, because it's totally not. It's all in the vold binary, framework support, and vold.fstab... has absolutely zero to do with the kernel.
[Captivate Android Development] kangi26:
NVM.....................
[Captivate Android Development] Slayer_b:
error 403 occurs in market when i'm trying to install paid app. Any solution?

P.S. build 15 + Glitch b2
[Captivate Android Development] k2ham:
emmc Usage Question

I've searched the thread but haven't found an answer for this (probably stupid) question...

Is it "normal" for the emmc folder (my external sd card, correct?) to basically be empty? Per Root Explorer, the only thing in it is a LOST.DIR folder, which is empty. Permissions on the emmc folder are 777.

I would like to use the 16GB card for storage of photos, apps, etc. but haven't figured out how to yet with this ROM. Perhaps I just don't understand the whole phone and card storage concept. Prior to ICS I was using the "emmc" card.

Before installing ICS I followed the recommendations in the OP including master clearing, flashing back to stock, etc. and also deleted everything on my "emmc" card in an attempt to have everything nice and fresh for ICS.

Do I need to go back and change something, format or partition the card? What do I need to do to utilize it?

Thanks as always for the help!

---------- Post added at 07:10 AM ---------- Previous post was at 06:59 AM ----------

On several occasions I've now experienced multiple overnight sleep deaths. The first night it happened I was running stock B15. I had been using it for a day or two with no problems, including no overnight sleep deaths. Then the next (2nd or 3rd) night, the phone had multiple sleep deaths over night. At least 4 or 5 times I woke up that night the phone appeared to be off... when I tried to turn it on I was presented with the ATT boot screen and it booted back up. As I mentioned I was running stock B15 and kernel but I had also increased the min voltage to 200 as I had had sporadic sleep deaths before.

After the multiple overnight sleep deaths I decided to install the latest icy glitch (B2) kernel to see if that would help. That night (the night before last) the phone was fine... no sleep deaths. Yesterday the phone worked fine also.

Yet last night the phone once again had multiple sleep deaths... running the icy glitch B2 kernel with a min voltage of 200.

So for my phone, at least for now, it doesn't appear to make much difference whether I'm running the stock kernel or glitch... I'm having multiple sleep deaths which appear to start the 2nd or 3rd night after making kernel changes.

Also, my phone is a 1007 and I don't recall having anything other than very sporadic/infrequent sleep deaths until build 14 & 15.

Don't know if this info will help the devs or not but wanted to put it out there in case it might.

Overall, though, thanks for the great ROM!
[Captivate Android Development] ScottyNuttz:
have you cleared data for the market app? That's always the first thing to try. If that doesn't fix it you might have to reflash the Google apps pack/app fixer.
[Captivate Android Development] nyciz:
+1

Seems to me (and I cant provide proof yet via a log...adb issues) If the battery is over ~65%-70% you can take /make a call and no reboot.

Yesterday evening, I left the phone off the charger, went to dinner and back called the Mrs with a 46% batttery and about 8 mins into the call reboot.

When it finished rebooting, the battery indicated 7%.

I thought the 7% was BS so for S&G's, I called her back after increasing the screen timeout 10mins. Spoke for about 20 mins, when I hung up the phone the battery showed 8%.

I know in other roms as well as when ppl OC/UV themselves, there are sometimes issues with the kernel dynamically setting the stepped OC and UV based on battery level to a level a point to low for background process to work efficently (SOD / COD). Or if you set the OC/UV higher/lowwer than what the individual device can handle (get a shutdown).

This is just a sneaking suspicion, I'm not accusing or laying blame on anyone or anything, just expressing thought/sentiment. Its super bowl weekend so I wont be able to fix my adb issue with my laptop but hopefully sometime during the week I will.
[Captivate Android Development] nakedninja42:
I want to report a problem/bug. I've been reading all the other posts and been wondering whats wrong with my phone. I have NOT had a single reboot in calls since installing build 15. I have NOT had a single charge/sleep death from build 3 - 15. I want to know why I don't experience any of these issues?!? I came from KK4 (using kies mini)to ICS, full wipe between each build, I don't have any mods or anything installed outside of what the ROM installs... no possible rouge third-party app that effects system apps. I don't get it. I spent 2 hours on the phone yesterday between 3 calls and did not have a single reboot, last call was initiated with less than 30% battery.

Now for the serious part. For all of you that has been having reboots and whatnot. Do any of you have a app installed that could effect your system apps like contacts, phone dialer? I am wondering this since most people who are reporting they have issues (compared to us who do not post because we do not have a single issue) if they have anything installed that is possibly not compatible with ICS that they were using on previous OS (GB,froyo, eclair).
[Captivate Android Development] morehush:
I also wanted to report that I have not had any reboots in calls or sleep or charge deaths. The only feature I really miss is GPS exif data in pictures, but that's not a big deal at all.

HUGE thanks to the devs for all their hard work.
[Captivate Android Development] Lhernandez0105:
PS Glitch b2 = post in Glitch thread
[Captivate Android Development] zeezz:
This is hardware problem I believe. I had to take apart my phone, blow dust and cleaner into the button switch to fix. There are a few other threads on XDA about this.
[Captivate Android Development] Holmes108:
Small issue I've actually had on all builds that I never bothered reporting.

I notice that fairly often, when I unlock the phone and touch the screen, the notification bar comes down. It doesn't matter how I touch the screen, or where (I can be nowhere near the notification bar). It only seems to be the first touch after unlocking.

It doesn't happen 100% of the time, but I'd say it's very often (close to half the time). Don't know if anyone else has noticed this, but I don't think I've seen it mentioned.
[Captivate Android Development] shaker2k:
Great point. People have to remember this is an alpha build. Should try to keep it as vanilla as possible.
[Captivate Android Development] nakedninja42:
Not only that, but people need to be careful restoring data. I had an issue with the launcher where the apps kept disappearing on my home screen as well as the app drawer. Turned out the issue was fixed in previous builds from nebkat and because I was restoring data using TiBu after it was fixed, I kept creating the problem so it was my fault :o.
[Captivate Android Development] bardroid:
Sleep Death Report

1006 Captivate Build

GB Bootloaders

ICS Build 15

Stock kernel & modem

No mods

No restores

Only apps added are Voodoo Control, and CalWidget.

Was listening to music app on shuffle for about 30 minutes and screen was off. Music app choked and output last note continuously like the app crashed. Power button unresponsive. Suddenly phone rebooted and all was back to normal. After reboot noticed battery was down to 44%. Didn't know where the battery was before I started music. I was listening to the audio pretty loud (on ear buds), maybe I triggered a power problem?
[Captivate Android Development] rsx19:
My wifi goes in and out once a minute, is this a problem and how do i fix it?
[Captivate Android Development] lurkingdevil:
I cannot do voice chat in gtalk, the app crashes. Is this a known issue?

I'm on Build 14.

Also, how can I set a custom tone for the alarm app?
[Captivate Android Development] picklesnickles:
For some reason I can't connect my phone to my macbook for USB storage. I want to drop some music on my external SD card and I have USB debugging selected.

Anyone help to be had?

Thanks a lot
[Captivate Android Development] alphahere:
Partial solution to charge of death.

Anyway I always get charge of death since build 10 and charge of death is 100% here.

I connected the captivate to the usb port of the computer with logcat running and no charge of death. I guess the usb debugging with logcat running keeps the phone awake.

Clean install of build 15 with KK4 GB bootloader and build 1010.

Downside the computer has to be on. :rolleyes:
[Captivate Android Development] Thnikk:
I've was using Captivate Keep Alive from the market [here] and it worked fine, you just need to close the app when you stop charging otherwise your battery will be drained in 2 hours.
[Captivate Android Development] alphahere:
Actually I tried that app (captivate keep alive) my phone still went to sleep.

I guess I have a sleepy phone :D It eats ice cream sandwich and goes to sleep! :rolleyes:

Thanks for the tip.
[Captivate Android Development] caleb4992:
I've tried. Can't get it to work either.
[Captivate Android Development] nkrick:
As previously discussed here and the Q&A thread, sleep death and charge death are two separate and unrelated issues. Search the threads for more information.
[Captivate Android Development] Chuckd610:
That happened to me on a couple of other ROMs. I never did find out why. Hopefully someone will have an answer.
[Captivate Android Development] nyciz:
yeah ok...

Congratz for not having an issue, wish I could say the same....

****edit**** removed****snarky****remarks****

oOn another note, I really do appreciate the hardwork on this ROM as my GPS has never ever worked as well and overall the B15 is more fluid that any other rom that ive loaded.

I got adb working again, {damn usb drivers}, is there a way to connect the usb w/o it charging the phone?

---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------

Before you(me/we) get asked, did you restore apps using TiBu?
[Captivate Android Development] simple man:
LOL.... I enjoyed that line... great sense of humor... . :-D
[Captivate Android Development] ScottyNuttz:
Another thing to consider if you're a charge death sufferer: are you using a stock USB charger?
[Captivate Android Development] ptesmoke:
on that note i have no charge deaths and use a htc 1A max output wall charger...i also use the stock charger as well but not as often..
[Captivate Android Development] alphahere:
Actually my phone has charge death problem. I have read this thread in detail and I am well aware of the difference between charge death and sleep death. I was joking around with the phone going to sleep (of course some folks took it seriously and some folks did not that is normal). I have posted before all the details of phone and this has occurred since build 10 without fail. I have never had sleep death expect with the glitch kernel which I tried once and removed quickly. I use the stock Samsung charger and stock battery. Interesting no charge death when connected to computer with usb. Probably the usb connection is keeping it alive.

Thanks to all the great developers ics is great! I can deal with the charge death problem, more of a minor headache than a game changer. What is strange - leaving the phone on the charger overnight of course causes charge death but the battery is down to 50% to 70% in the morning. So I remove the phone from the charger at night.

One thing I have noted with build 15 my battery life is phenomenal.