yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] twilightwolf90:
Just checking in. I've flashed the latest cognition build (2.2 oc/uv) to my phone and have experienced no (0) random shutdowns. It's fantastic, however I'm dealing with the charging death issue and random lock ups that seem to occur whenever OpenGL is being used. I.e. Rocket Bunnies or SNES emulator.

It's a step in the right direction. I'm not sure where to find the captivate's version number though to be more helpful. I'm attempting to overcharge my phone while adb logcat prints everything out.
[Captivate Q&A, Help & Troubleshooting] dwmoss:
Its on the lower left part of the white sticker on the phone under the battery.

dm
[Captivate Q&A, Help & Troubleshooting] cdwhit:
Ok, everyone seemed to ignore my previous post but I'll toss this out anyway if anyone is interested. Since previous post I had no shutdowns until yesterday. I wondered if it was a fluke or a return of the problem, so just turned it on and ignored it. Today it shut down again.

I opened the phone and once again the SD card was very slightly out. Guesstimate between 1/32 & 1/64 inch. If I hadn't been looking for it I wouldn't have noticed.

Obviously this isn't the problem if you have no external card installed, but I really think the card slot is picky and doesn't like some SD cards.

If I get a chance to shift data around I'll probably try a different brand card over Christmas and see what happens. Otherwise I'll try a bit of scotch tape to hold it in and see if that help. Even if I do moyhing,if I can get by with opening the phone once a week to reset the SD card I can live with that.
[Captivate Q&A, Help & Troubleshooting] caspio:
Finally received my replacement phone. Original phone was a 1009 - worked fine for two weeks and then started with random shutdowns 5-10 times a day. The replacement I received is a 1007. So far no shutdowns, but the GPS is completely non-functional. On the 1009 I could have a lock down to 15 foot accuracy in under 30 seconds. New handset won't lock at all most of the time, and when it does it's around 100 foot accuracy, and it drops the lock the second you move.

Anyway, time to contact warranty again

At least the store was willing to deal with you. When I tried to exchange mine in-store, they brought a phone out of the back, had everything ready to go. The second they heard that the phone had been purchased online, the shiny box on the other side of the counter from me went away. Refused to help in any capacity because the phone hadn't been purchased there.
[Captivate Q&A, Help & Troubleshooting] FiniteSM:
Thought i should check in here. Just got a replacement a month back, and this phone has never had this issue. Definitely, if you can, replacement will fix this issue.
[Captivate Q&A, Help & Troubleshooting] GSMinCT:
Was it a corporate store or an authorized retailer? Authorized retailers only deal with phones they sold, corporate stores are supposed to deal with any phone sold by AT&T, online, or an authorized retailer.
[Captivate Q&A, Help & Troubleshooting] caspio:
It was a corporate store. The guy stated that they can only help for phones purchased from another corporate store. He said online and authorized retailers they can't do anything for.

One important note is that I originally approached the question as a "within 30 days direct exchange" kind of thing. However, after that was turned down I did ask about the warranty services dept.
[Captivate Q&A, Help & Troubleshooting] codyrt:
Hi guys,

I am starting to have this issue of the phone being on, and out of nowhere the screen turns off. After that, the backlight on the buttons turns on and stays on. Leaving the phone alone for a while does nothing, the phone just keeps reloading itself, not going all the way to the boot-up animation, just looking like I had just powered it on repeatedly. No buttons work, removing the battery is the only thing that lets me restart the phone. But even after restarting, it does not work, it continues to do the same thing.

This issue has only happened on two days, it has been almost a month since th3e first time it acted up. I got a call from a local number, rejected the call, and they left a voicemail. After that, the phone started the problem I explained above.

NOTE: I am running the AT&T update with the voodoo lagfix. I have not flashed any custom ROMS, but I most likely will be doing so soon.

I decided to tinker around, trying ideas within this thread, nothing helped much. BUT one thing did (Sort Of). I removed my SIM card and the phone stays on and doesn't freeze or become unresponsive. Keep in mind my SIM card is years old, it has been through several phones. I will try and get a replacement SIM card to see if the issue is resolved, but it seems like it has something to do with the problem, at least in my case.

I have now booted the phone up with the SIM card back in the phone, and it has locked up yet again.

UPDATE: I checked my voicemail through my landline phone and deletet the messages, now the phone is back to normal. Software related, possibly android being buggy?

UPDATE2: The phone will not stay running properly for more than a minute if that with the SIM card in the phone, without, it works perfectly fine minus the features a cellphone needs.
[Captivate Q&A, Help & Troubleshooting] 40Love:
Just returned my first Captivate for random shutdowns. It was mfg. early October. My new phone (30-day exchange) showed batch 1012/.4 and the Samsung registration site showed a manufacturing date of 12/12/10. We will see how it goes.
[Captivate Q&A, Help & Troubleshooting] codyrt:
I think I have pinpointed my issue to my SIM card, it may not be the problem for everyone else though. I found out that once my phone showed I had voicemail that I had not checked, I used my landline, deleted them and the icon still showed on my phone.

I then put the SIM card into an old Go Phone, it showed the same voicemail icon even when there weren't any messages. So i called my own number, left a message, called my voicemail and deleted my new message. The icon went away, I put the SIM card back in the captivate, and now it works perfectly.(For now)
[Captivate Q&A, Help & Troubleshooting] tedtech:
I was having the same issues with the phone turning off...seems mine was fixed with turning off Power Saving Mode under "Sound and Display" and Stay Awake under "Applications/Development". After one of those was turned on it would shut down at some point. Hope this helps someone
[Captivate Q&A, Help & Troubleshooting] LBCaptivate:
I decided to got to the AT&T device support center in Austin TX to see if they know anything about the shut down issue. I was told that they were aware of the problem , but the Samsung has not come out with a fix yet. If I wanted to do a warranty exchange I could but there was no way to know if the next phone would have the same problem since it would be a refurbished phone. I did not do an exchange because I have a Zag screen protector and I want to get another one first (under warranty $4.95) to protect the next phone.

I then called Samsung when I got home and was told they were aware of the problem and it was a software fix and I could send the phone in so they could apply the update. Next I told her that I already had the update and it did not fix the phone. The update was the I897ucjh7. Next she changed her story and said it must be a hardware issue and I should get a repair request so I could send the phone in so they could fix it. It was supposed to be a 6 day turn around.. I then asked, "Am I supposed to go without a phone while they fix it?" Her answer to that was, " Go to an AT&T store and get a loaner phone." I seriously doubt that AT&T will give me a phone to use while I send mine in to get fixed. They were the one that sent me to there device support location.

Still no solution to the issue other than send it to Samsung and hope they are able to fix it.

What to do??

PS. Already got another battery from AT&T and did a master reset.
[Captivate Q&A, Help & Troubleshooting] liqn7:
This fixed it for me (so far ~an hr in). Previous to this I was getting shutdowns every time the screen was off for more than a few minutes.

Keep Captivate Alive also works but really kills the battery, so it only lasts half a day :(

Thanks for the heads up! Will let you know if there's a problem again.
[Captivate Q&A, Help & Troubleshooting] socalledsin:
Has Samsung even acknowledged this issue? Haven't had any shutdowns since installing Load Monitor, but it still pisses me off there is an app on the market "Captivate Keep Alive" yet Samsung plays dumb.
[Captivate Q&A, Help & Troubleshooting] p0l0g1rl:
My captivate has also been doing this as of day 3. None of the other methods tried have worked for me; i did not use the workaround programs, however.

I was wondering, for those that it worked for, how did you guys change your mobile network type from hsdpa to edge? I would like to try this and see if it will help.
[Captivate Q&A, Help & Troubleshooting] liqn7:
Opps guess I spoke to soon. It was working for an hour or so and it has now gone back to the shutdowns while sleeping.

Back to Captivate Keep Alive :(
[Captivate Q&A, Help & Troubleshooting] donrob:
I got the first batch of Captivates in Canada from Best Buy, new activation, 3 year term, and i had this issue on the stock rom, 2 cognition roms, and the new ginger rom. I am passed the 30 days to return to Best Buy. After speaking to a Rogers rep he asked me for my imei #, after i gave it to him he said he will send me a replacement unit. Samsung knows, Rogers knows, and i'm sure AT&T in the USA knows about this issue. I'm happy Rogers stepped up for me, he also said that updating the firmware does not void the warranty, as i was having this issue with their stock rom. Keep Captivate Alive is pure genious, but this bandaid solution is not acceptable for me, especially for a high end phone like this. If you have this issue I suggest not settling for Keep Alive, don't wait for a firmware upgrade, do what you can to replace the phone.

Just my suggestion...
[Captivate Q&A, Help & Troubleshooting] philoso:
shutdown log?

I have random shutdown problem like many other people.

I think I've read almost all the messages on this thread.

My basic conclusion is that no one knows what is going on.

What I've come to realize is that we have so no solid log of any kind.

Can everyone run

$ locat > /sdcard/logcat.txt

hmm would that just keep cpu alive so that shutdowns dont happen??

I dont know.

Or something to that effect.

Im sure some android dev can make background app that collects logs?

That would be my best approach to this problem.
[Captivate Q&A, Help & Troubleshooting] Jikx:
Interesting.. my phone use to shutdown on screen lock when on stock firmware, and Cognition b3 - now that I've updated to Cognition b8 it doesn't happen anymore!

There is definitely something funny going on with our phones... multiple reasons giving the same effect perhaps.
[Captivate Q&A, Help & Troubleshooting] volusia7:
Day 10 with my new (referb) phone, and not a single shutdown so far, and as far as I can tell, I have everything back to exactly the same configuration, same apps, same battery, same live background, email check freq, etc. I have performed the same tests, Full charge with wall charger then let sit for hours in sleep mode in cool/cold environment and so far (knock on wood), no problems.

AT&T warranty sent me a new (referb) phone and I had 10 days to get my orig phone shipped back in the pre-paid package. So I was never without a phone, nor did it cost me anything but a little setup time.

Since I kept my same sd card, sim card and battery, it rules out one or more of those being defective... but does not rule out the actual connection. Since a LOT of these phones start showing this behavior after a few months of use, it could be the connections start getting corroded or building up some type of resistance. OR, the actual phone itself has defective electronics that only show up after so many hours of use, or heat cycles (recharge cycles)? I am keeping a very sharp eye on the replacement tho, I will keep posting any change in behavior.

Oh, one thing to note: I had put Froyo 2.2 on my original phone, and the replacement came with Eclair UCJH7 2.1-update 1. Not sure if that makes any difference, but I am sticking to what works for now.
[Captivate Q&A, Help & Troubleshooting] ajm786:
Just to let everyone know, I've had my replacement phone for a month now. The phone is brand new, exchanged directly from an AT&T store. I have not had any shutdown issues whatsoever yet to speak of.
[Captivate Q&A, Help & Troubleshooting] Jeffu:
Rogers Captivate owner here.

I just gave them a call to see what they'd say about the shutdown problem. I asked him right away if he was familiar with it, and he said "I wouldn't say it's a non-issue; we're aware of it". He said it was definitely hardware when I asked him.

He said I should try at least one factory reset to see if it was an app thing, as things such as task killers modify the phone settings causing it to crash. I don't use it actively anymore, but I do have ATK on my phone.

Seeing as I'm past the 30 day mark it'll be a refurb if I want one, so I'll give the factory reset a try first...

edit: just did the factory reset. I'll run it stock for a while I guess, will update if it helped any.
[Captivate Q&A, Help & Troubleshooting] dwmoss:
Surprised this hasn't been posted in this thread yet....

At&t captivate shut down press release

dm

It will be interesting to see what the manu dates on the 2 refurbs coming my way from texas!
[Captivate Q&A, Help & Troubleshooting] Richy_T:
Just another data point:

Mine has just started doing this in the last week (I have had the phone since September). It appeared to start soon after I tried to connect the phone to my PC and got a "There was a problem with your hardware" type message from windows (it worked fine connecting to a different USB port after). I have tried it with the SMS card out and the wifi odd and it still occurs.

IMEI ends in 7009. (Edit: looks like it's the first 4 numbers that count which I think I may be in range of for the replacement)

I will wait until after Christmas then try a factory reboot and see if that helps. Also if the update comes (Yeah, right. I bought the phone expecting the update to be within the first 30 days) I'll see if that helps.
[Captivate Q&A, Help & Troubleshooting] Jeffu:
So far no shut downs from last night. GPS works due to the hard mod suggested in that new GPS thread, and I haven't had shut downs... my phone is perfect now far as I'm concerned.

But I'm afraid to just think it was software; does this issue end up reappearing for some people? I do remember reading that Launcher pro was a possible culprit, so I've not even bothered restoring it or ATK with TitaniumBackup.

fingers crossed~
[Captivate Q&A, Help & Troubleshooting] socalledsin:
Just curious on the change in battery life to those who got a replacement now that you dont have to run CKA or Load Monitor anymore. Wish I had called when my wife originally told me to a week ago!
[Captivate Q&A, Help & Troubleshooting] eatonjb:
hard mod? could you hit me up with that link?
[Captivate Q&A, Help & Troubleshooting] Jeffu:
http://xdaforums.com/showthread.php?t=876179

Not too fancy a mod, but I suppose you have to scratch a bit at it. :P
[Captivate Q&A, Help & Troubleshooting] gt50:
An update on my situation. I installed perception 9 around the 17th. My shutdowns were no better or worse than they had been. About 5 days ago, shutdowns became worse than ever. 4-5 times per day minimum. The phone seemed to shutdown initially if bluetooth was left on with wifi. It shutdown a couple of times while disabling BT while the headset was connected. Initially I thought overclock was doing it, but disabling oc did not change anything. The day after the shutdowns started, listen stopped working. None of my downloaded podcasts would play. I tried deleting them, and redownloading them. They still would not work. Alternate episodes would not work either. On this day the phone shutdown while charging overnight.

My phone has never done that. It shutdown the next night while charging also. Two days ago, it shutdown while I was talking on the phone. Another first. I turned it back on, and after booting up the email application that I use to access exchange FC'ed. Now I am puzzled, I think the filesystem is hosed. I reboot again. Everything seems fine. Later I click on the email application to check it, since my phone is not making noises when email shows up in outlook. All of my settings are gone.

I try downloading the latest cognition to reflash at work. It downloads to the phone. Clockwork is not able to install the rom, it seems bad. Phone won't boot. I try each of three backups that I have, all show bad MD5 checksum. Filesystem is definately bad. I don't know how to format the entire internal card. I decide to try master clear, since it erases everything, and hope it does so by reformatting the entire card. When I get home, I flash to stock, run master clear, factory reset, and install latest cognition. I copy a titanium backup that I happened to have from the week prior when I tried perception, and restore.

It has been running like a champ for 36 hours so far.
[Captivate Q&A, Help & Troubleshooting] ph00ny:
Odd

I've never had this issue with my captivate (stock or flashed with p8)

however, i'm having random reboot issue with my nookcolor rooted with supernooter
[Captivate Q&A, Help & Troubleshooting] eatonjb:
the Rom had an issue of corrupting the SD Card, and that could be your reason.. format the SD card and start over :/
[Captivate Q&A, Help & Troubleshooting] gt50:
Thanks. This supports my observation.

Phone is still running like a champ after master clear. I am at 2.5 days and no random shutdown. I am running stock launcher instead of adw, or launcher pro, but I don't think this has anything to do with my lack of shutdowns.
[Captivate Q&A, Help & Troubleshooting] dspsaab:
Captivate random shut down / shut off fix

Here is a semi-fix. This trick will prevent your phone from shutting down but will decrease battery life somewhat.

1. Download "Load Monitor" from the Android Market.

2. Once installed, open the Load Monitor app.

3. Click on the Menu Button and Select Preferences.

4. Check the following Items:

* Add Notification

* Auto Start

* Wake Lock

* Only screen on

5. Go to "Update interval" and select 5 Minutes.

6. Although the Auto-start assures the app runs everytime you reboot your phone, if it ever shuts off, start the app manually; though you should haven't to do this step too many times.

Load Monitor keeps your phone from shutting down by preventing suspend via wake lock setting and by actively monitoring your load, the phone is always doing something. The main reason these phones shut-off is due to the processor going into suspended mode whenever it is not being used much and then it shuts off once it hasn't been used long enough. This trick worked for me, can't gurantee everyone but very good chance it will work.

Please visit, "mysmartphonenews.blogspot.com" to support my blog.

Thanks!
[Captivate Q&A, Help & Troubleshooting] bscode:
That's essentially what Captivate Keep Alive does - though you can have CKA release the wake-lock below a certain battery %. That way if you only have problems when your battery is over, say, 75% you are only burning through battery fast for the first 25%.
[Captivate Q&A, Help & Troubleshooting] chasesavestheday:
i tried all of them a while back. CKA, and Load Monitor. Still received shutdowns. You need to return the device to the warranty center. my 1007 had shutdowns, replacement is a 1010 and havent had one.
[Captivate Q&A, Help & Troubleshooting] LBCaptivate:
I went into an AT&T store yesterday and told them I had tried a reset of the phone, new battery under warranty and that I went to a service center that said they were aware of the problem but that a refurbished phone may not fix the problem. I had even call Samsung and was told to send my phone in and get a loaner from AT&T. I told the AT&T rep at the store that I did not want a refurbished phone. He then went into the back of the store for about 10 minutes. He then came out with a brand new phone still in the sealed box. I was told that they usually do not do this. I opened the phone and it has a build date of 1012. Now it is a wait and see if they fixed the shut down issue. On my first phone it did not start until about 3 months after I got it.

I forgot to mention I also gave him a copy of the shut down press release, which he took to the back. WHen he came out he said the release was B.S, yet they gave me a new phone.
[Captivate Q&A, Help & Troubleshooting] samven582:
how did they give you a brand new phone?

Anyway here is my story. I went into an AT$T warranty center located in Islandia, New York. I told them that my Samsung Captivate was randomly shutting itself off and I want it replaced. Unfortunately they only offered my a replacement battery which I kindly refuse. I explain to them that the battery has noting to do with this problem but they refuse to believe me. Right there and then I called AT&T warranty support explain, my problem and they are sending me a replacement phone. They sad part of this story is AT$T has not acknowledge this problem. As soon I get my replacement phone its going on ebay and I am switching to T mobile for the G2. Enough is enough, I am done with of this Phone and AT$T.
[Captivate Q&A, Help & Troubleshooting] LBCaptivate:
I am not sure why they did it. I did tell them that I tried every possible solution including Captivate Kepp Alive. Maybe because they know I kenw what I was talking about. I am a used car salesman, so maybe they bought my B.S. lol!
[Captivate Q&A, Help & Troubleshooting] samven582:
The representatives that I talk to did not have a clue what I was talking :(.
[Captivate Q&A, Help & Troubleshooting] 3viction:
This man is a genius! You should make a thread and get it stickied or something
[Captivate Q&A, Help & Troubleshooting] BelvedereWRX:
254 hours and going on Perception with Load Monitor wake lock.

10 days!
[Captivate Q&A, Help & Troubleshooting] kegobeer:
Glad it works for you. It's not a real fix since there's a hardware issue, and I recommend you get a replacement if your IMEI falls in that range (or even if it doesn't, because I got my first replacements before this memo appeared).
[Captivate Q&A, Help & Troubleshooting] kegobeer:
This also isn't a fix that works long term (for most people). Quite a few people tried it and were believers, until their Captivates started shutting down again. If you have a phone in the IMEI range, I recommend you get it replaced.
[Captivate Q&A, Help & Troubleshooting] BelvedereWRX:
For the time being, it's the closest thing to a guaranteed resolution I'll seem to get. Especially since silly AT&T are sending out refurb units in the problematic range.
[Captivate Q&A, Help & Troubleshooting] genem1:
Can you restate what you know about this, or point me to it?

I didn't see this comment come through.

Thank you
[Captivate Q&A, Help & Troubleshooting] dwmoss:
Its another big thread here in general.

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

dm
[Captivate Q&A, Help & Troubleshooting] gibson3659:
A factory reset has fixed my problem to the point that I have un-installed CKA. I had also done a calibration and cleared the battery stats previously.
[Captivate Q&A, Help & Troubleshooting] Clienterror:
I cleaned off my battery contacts because there was almost no shine to them and I haven't had a random shutdown in a few days. Not using any apps to keep it up either. I got it on launch day so I'm 1006.
[Captivate Q&A, Help & Troubleshooting] realsjn:
1008

sadly it happens to me everytime i go to sleep.

in daytime also ramdom shuts down

i bought it last week:mad: