yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] krakerx:
I don't know if it may have something to do with the manufacturing date, but I got two phones and both have the same issue, first I thought i was some of the apps, and the root, so I restored it, and put the apps back one by one, still shut down.

The second phone, same thing, so i said f it, I restored my phone back to JF6 using Odin3, have yet to re-root, and put any apps on except SMS Backup & Restore. And sure as S*** the phone still shuts down.

With both phones it hasn't as drastic as having to take out the battery to get it to turn back on. Pressing the power button twice usually gets the phone back on for me.

But going back to the manufacturing date, I noticed that both phones were made around the same time in July [go to samsung's website to register your phone, when you put in your serial it will tell you when it was made]. So i'm wondering if it was a bad lot. So if some of you that are having this issue, could you post your build date to see if the phones in question were made around then.

My date was 7/12/10
[Captivate Q&A, Help & Troubleshooting] RexEscape:
I have registered my phone but didn't take note of the mfg date. I went back to Samsung's website and logged in under my account but couldn't find a way to retrieve the date. I figured it would have been manufactured at around that time since I bought this phone on July 30th.

I just got done chatting with AT&T's chat support. They claim there have been no known issues with this device powering down on its own.

EDIT: I returned my phone and got a new one. My new device, another Samsung Captivate was manufactured: 08/02/2010
[Captivate Q&A, Help & Troubleshooting] krakerx:
even vibrant users are noticing thier phones randomly shutting down... AT&T has to have some idea, do they not count the number of phones that they have being returned? or how many times a user reconnects to their network?
[Captivate Q&A, Help & Troubleshooting] RexEscape:
Apparently not. Or maybe the chat department is not connected with the returns dept. I don't know. I shouldn't make excuses for AT&T.

Anyway, I've read (on this thread) that by changing your wallpaper, it fixes the random power shutdown (skeptical, but I'll give it a chance). When I did my Factory Reset yesterday, it defaulted to the animated blue bubbles wallpaper. It was on that when it shut down on its own after the Factory Reset.

This morning, I changed the wallpaper to the non-animated green grass. No other apps have been installed (except for SMS Backup and Restore). It have the connect-the-dots to unlock set. I have my Yahoo! and Gmail setup using the Android Email client, set to check emails every 30min.

Let's see how it goes.
[Captivate Q&A, Help & Troubleshooting] jswclw:
Third day on perception beta8. No random shutdowns. Interesting.
[Captivate Q&A, Help & Troubleshooting] eatonjb:
yea.. same here.. tho no "real" testing yet.. but so far so good! <3
[Captivate Q&A, Help & Troubleshooting] jswclw:
It is tough to do a real test since the issue cannot be repeated with 100% reliability. However, I have had a high shutdown rate following a battery recalibrate - charge to 100% with phone, torn off, charge to 100%, repeat, and so on. Almost always, as the battery passes 90% on the way down after this recalibrate, the phone would shutdown. That didn't happen this time under Perception. So I am encouraged, but not convinced.
[Captivate Q&A, Help & Troubleshooting] xxgg:
are any rogers galaxy s captivates failing like Bell's galaxy i9000m with internal sdcard issue?
[Captivate Q&A, Help & Troubleshooting] SkateEmerica987:
I was getting these shutdowns multiple times per day. Then I downloaded captivate keep alive from the market and that worked pretty nicely. Recently I've gone to a custom rom which has pretty much taken care of the problems as well.
[Captivate Q&A, Help & Troubleshooting] volusia7:
I got my new (read refurbished) Captivate this weekend. I kept it stock 2.1 and charged it to 100% before bedtime, then left it off the charger in sleep mode and no shutdown last night. I even put it in the window that I know was 35-40 degrees. Today, I went ahead and loaded some apps (including text to speach) and I will do the normal test again tonight. Charge to 100%, then put in a cold place and let sleep all night. This was the most reliable test I could do with my original phone, as I tried to use it for an alarm clock. but the alarm no worky when it's turning itself off!

I keep you posted on my results.

oh and my new phone is a 10.08 Not sure what the "dot" is. My old one is 1007.
[Captivate Q&A, Help & Troubleshooting] eatonjb:
Just recived a new phone.. my old one was 1008 and the new one is 10.08.

the Lable looks different too.. no "Samsung" Logo, but this could be a referb sticker

there also is no 888-987-4357 phone number and all that power rateing stuff..

ohh well.. we will see.. hope this works.

I hate to say it, already been rooted and new rom installed.. but it was happening no matter what..
[Captivate Q&A, Help & Troubleshooting] StevenMP:
Sorry for the delay, but more time passed gives me more ammo. 12-14-2010 - I have not had random shutdowns since my last post. Loaded plenty of apps and using the phone with zest! Sometimes email and calendar take a poo, and then restart. I am using Hotmail, and Exchange on the stock phone client. I feel it is due to the battery getting conditioned through multiple charge/discharge cycles. It seems to struggle through its first cycles (in terms of reporting its condition to the phone) and then gets better? I also bought the 3000mAh Seidio battery to test. Out of the box, no issues and I can go 4 days before charging. Bought a cheap silicone case and make some relief cuts to allow the phat batt to get into its stretch pants. I also believe the battery issue could tied to temperature - cold weather short? I don't know if it is eclair not playing nice with the hardware, but thus far the phone is tolerable. I hope we get 2.2 soon and Gingerbread before end of Q1 2011. I continue to want to like this phone.
[Captivate Q&A, Help & Troubleshooting] cdwhit:
Possible solution

OK, This solved my random shut down problem so far. Keep in mind I'm not one of the uber hackers or techno whizzes that come up with most of the stuff here. This was just a lucky observation that apparently fixed the shut down problem for me. Reading the posts, I don't think this will fix them all, but maybe most?

In trying to reboot (AGAIN) I noticed my SD card was not seated all the way in. It was almost in, but not 100%. I removed and reinstalled the SD and haven't had a shut down in 2 days (I was up to 4-5 a day and increasing before that.)

This got me thinking. At least on my phone there isn't much pressure holding the SD card in place. Vibration or even the bumping as I was walking was causing enough movement to knock it loose, which turned the phone off!

From past experiences, SD cards are NOT identical. I have had several which would work in some SD card adapters, but not ones I received with other cards. I suspect that a flakey socket design on the Captivate may make it kind of picky about the SD card. Those that have had no trouble have a tighter socket or lucked into the card brand that fits best. Those of us that have had trouble have a looser socket or picked the wrong brand SD card. If your luck was REALLY bad, your card made bad enough contact that as soon as you put it in a new phone, it started shutting off. For most of us this would explain the working fine when you first get the phone and then developing problems later as the clip holding the SD card loosens up or the card works out a touch.

If you're phone shuts off often, try pulling the SD card completely out for a while and see if that helps. Post your results here and if I'm wrong, OH well, I tried. If I'm right though, maybe we can determine which card brands work best.

I'm waiting to see how long mine goes without a shut down, and if/when it shuts down again I'm going to try putting a bit of tape on the back of the SD card to hold it in the socket better.

Good luck.
[Captivate Q&A, Help & Troubleshooting] gibson3659:
A reset also helped mine tremendously. I was able to move Keepalive from 60-70% to 90+%. I keep inching it up and currently have it set to 97% with no shutdowns. I had wiped my battery stats one before.

I also have some suspicions that it could be a battery, charging, or conditioning issue. My wife and I got our Cappy's at the same time and from the same lot. I deep cycled mine once or twice, but she didn't. She has not complained, or even mentioned, a single shutdown.

Now she did accidentally get a deep cycle yesterday, so it will be interesting to see if the issue develops.
[Captivate Q&A, Help & Troubleshooting] cdwhit:
SD won't solve all?

The number of phones helped by the keep alive and charge limiting software is why I don't think all the shutdowns are from the same thing, BUT...

Even with the loose card mine NEVER shut down when in use. Maybe the bad contact for some reason would only shut off the phone when it was asleep? I can see how electrically this might be possible, but don't know the hardware or software enough to know if it's possible for this phone. If the Keep Alive software is keeping the phone in a state when the card won't power it down (the card is supposedly hot swappable after all) then that would explain why that helped. Also, charging most batteries generates heat, so the heat generated during a full charge could conceivably be making a marginal SD contact bad.

Just guessing on my part, but I still haven't had another shut down. (Knock on wood!)
[Captivate Q&A, Help & Troubleshooting] Nimocone:
Well, after 7 days of no random shutdowns using the new Seidio extended battery, ended on the 8th day. My shutdowns between 100-80% came back so I'm using the Keep Alive program again. I wonder what would make it suddenly go back when there were no new apps loaded. Does the battery's internals change to some degree after a weeks worth of using? Room temp doesn't play a role with my phone.
[Captivate Q&A, Help & Troubleshooting] socalledsin:
Just got a captivate myself, and am having this issue as well. Has anyone found a rom that does not have this issue, or know of a good setcpu setting to prevent this?
[Captivate Q&A, Help & Troubleshooting] BelvedereWRX:
After lurking this thread for weeks I've decided to post my findings. The only reason I didn't post earlier is because this issue seems so varied. So far, there definitely doesn't seem to be a single resolution for this issue and it varies from person to person.

I started having random shutdowns about 2 days after getting the device. I instantly rooted it then loaded Cognition. For the first 2 days, there were no random shutdowns, but after 2 days it would occur 5-6 times a day. It seemed to get worse.

Like everyone else, I basically tried everything I could. Without boring you with a long story, I'll just post what I did that DID NOT work.

Cleaning the battery terminals and phone terminals.

Going back to stock.

Factory flash/restore.

800 MHz band setting.

Set CPU frequency adjustments.

Captivate Keep Alive.

Different battery.

I noticed on any ROM, even stock, the app "Load Monitor" would significantly reduce my random shutdowns/locks though it would never fully resolve it as I would still get the occasional lock. The behavior would be that when trying to "wake" my phone after the screen had shut off, it would always delay and take a few seconds normally. Load Monitor has a "wake lock" feature that when enabled, significantly reduced this.

I recently loaded Perception 8 after hearing a few people claim that it helped with random shutdowns. This wasn't the case for me (wait for it) until I installed Load Monitor and enabled the wake lock setting. So far, it's been more than 100+ hours without a single shutdown/lock. I know since an app is involved that it's not the most ideal resolution, but my phone is at least in the realm of dependable now.

I know there are so many variables for this issue, but if it helped me I'm sure it may help someone else.
[Captivate Q&A, Help & Troubleshooting] socalledsin:
Thanks for the info, flashing perception 8 as soon as i type this. Did you install the oc/uv version or non? Also can you tell me what voltage settings you changed if any, and what settings you used in load monitor? Thanks a ton for the help. I love this phone, but I have to find a solution to this.
[Captivate Q&A, Help & Troubleshooting] Jeffu:
I've read most of the posts myself, and have been trying to pay attention to when I experienced the shut down. It seems to happen at work, but since I keep it in my pocket I can't tell if it's losing bars or anything else until it happens and I notice when I pull it out. Seems to be pretty random, as others have said.

For whatever reason it only happens 2-3 times in a day which I can live with; I haven't bothered with the Keep Alive app anymore as the battery drain isn't worth it.

I guess I should make time to read up on how to use roms!

Hm. I'm going to give that a try. Will post after a few days if it helped.
[Captivate Q&A, Help & Troubleshooting] cmeyer3:
I did some testing on my phone. I found a app that caused mine to shut down. Weather and Toggle widgets. After a full reset I had no shut downs,I installed Weather and toggle and had shut downs. I uninstalled it the shut downs stopped.

I am not saying for 100% that this app is what caused it but maybe a situation that is caused from the app (or those like it). There is a word that describes my exact thought I just can't think of it.
[Captivate Q&A, Help & Troubleshooting] BelvedereWRX:
Sorry for the delay, I installed the non OC version as it seems it's more stable.
[Captivate Q&A, Help & Troubleshooting] LBCaptivate:
what widgets were you using? I also use the weather widget that came with the phone. I have Fancy widget installed on mine and I get shut downs everycouple of days. My phone is stock.
[Captivate Q&A, Help & Troubleshooting] socalledsin:
I have tried several roms and saw no change in the issue, but this morning I flashed back to stock and have installed very few apps, so far no shut down. I doubt this is a solution as many have already posted they run stock, but if not it is definitely not as bad as it was on perception or cog roms.

As far as the weather toggle widgets I don't believe I had any installed, the only widgets that come to mind that I left out from this flash are the Curvefish 2g/3g swap, and the Musicmod widget.

I also would like to note that after returning to stock I have not installed any type of task killer, whereas before I was using the one included one from froyo.

I will post if there are any changes, would love if we could figure this out.
[Captivate Q&A, Help & Troubleshooting] cferby:
Phone case causing phone to power off

I have determined that my phone case causes my phone to power off. My case has a magnet that holds it shut. Apparently the magnets in the case make the phone power off after being in it. If I put the phone in the case with the back of the phone facing my side it doesn't power off. When the phone is in the case with the front facing my side it powers off regularly.
[Captivate Q&A, Help & Troubleshooting] cmeyer3:
I was using the weather clock that looks alot like the sense clock.
[Captivate Q&A, Help & Troubleshooting] socalledsin:
So much for the issue being gone =(
[Captivate Q&A, Help & Troubleshooting] eatonjb:
so far my 10.80 (ten POINT eighty) phone seems to have no issues

with the perception8 rom. this is a new referb phone.
[Captivate Q&A, Help & Troubleshooting] mindcandy30:
3 of them at work

Our company bought 5 Captivate's, and 3 of them experience this problem (1009 prefix serials). "Captivate Keep-Alive" didn't help, and for the most part, neither did AT&T. The standard warranty folks we talk to gave us the run-around (told us we had to replicate the problem while he was on the phone? .. wth?), but eventually a call to the AT&T account rep fixed that.

Despite the fact that these were *new* phones, they got swapped with respiff units, which (thus far) have been problem free.

Tip: if you call in, ask to speak to the warranty exchange folks. If you end up with an "Android Specialist" start over.
[Captivate Q&A, Help & Troubleshooting] XjCrazy09:
Well I have read through this thread and it seems like everyone is just repeating the same problems over and over and there doesn't seem to be a great solution to the problem. So I guess I'll just state my case and move on.

First Samsung Captivate purchased day after Thanksgiving, it wasn't for about 2.5 weeks before I experienced first random shut off. In that time I had rooted with a ROM that I had found off the Samsung Captivate forum. I had used ATK however, when I learned that this was a rumored problem I uninstalled the application. Got to the point where it was powering off multiple times a day. So I decided to return it within the 30 days, brand new phone, Did not root or even install any apps. Within 24 hours of exchanging to the new phone it had powered it self off. I thought about rooting to Froyo Leak to see if it would fix the problem. However, I feel I am better off waiting to see if the problem is resolved with a more logical solution.

Thanks for hearing me out. I was really getting used to Android too.
[Captivate Q&A, Help & Troubleshooting] rudous:
I found that StabilityTest crash after a few minutes. I don't have oc device. Currently using Perception 9. What about you? Couldn't this be the problem? Simply bad cpu or something.
[Captivate Q&A, Help & Troubleshooting] avgjoegeek:
I've had my phone since September - had a few random shutdowns and it seemed to go away for a bit.

Now - if I charge my phone to 100% (I've calibrated, and drained/recharged many times) the phone will start giving me the "sleeping death" and I'll have to cold boot it - sometimes it will stay up, most of the time I'll have to keep booting it up until its around 80% then will normally stay running. But... not all the time :D

I'd say its 100% hardware - as I have run just about every ROM you can think of - even went so far as to format the entire SD Card and wiped all the cache etc.. and kept it stock for a day (JH7 OTA) and still had the issue.

I'll be exchanging it when I get the chance - but I don't have high hopes that the issue won't start happening with the new device I get.
[Captivate Q&A, Help & Troubleshooting] bscode:
This is exactly what Captivate Keep Alive does but it allows you to tune when the wake-lock is on. If you want it on all the time just set the threshold to 0% - though it may burn through your battery a little faster.
[Captivate Q&A, Help & Troubleshooting] paulo.bartos:
Just to inform that in many days and many roms i just cross the barrier of 48hours without shutdowns using his recomendations.

Perception oc with loadrom wake feature and refresh interval set to 2 hours(i think, but is the bigger value).

Thanks for sharing.

I will comment if anything diferent happens.
[Captivate Q&A, Help & Troubleshooting] paulo.bartos:
Another info. My battery IS running faster. But as the phone was always shutting down the battery lasted for days, but the phone was unusable as nobody would reach me.

Thanks again.
[Captivate Q&A, Help & Troubleshooting] GSMinCT:
Very interesting. I think all of my problems started around the time I put the Weather Channel and rotation toggle widgets on. CKA works fine for me, I'm just getting sick of the battery drain of this phone, it rarely lasts though the day...
[Captivate Q&A, Help & Troubleshooting] socalledsin:
Load monitor seems to have done the trick for me as well. I am using it with stock rom as perception 8 seemed to drain my battery. So far so good. Phone lasted from 530am to 7pm with medium usage.
[Captivate Q&A, Help & Troubleshooting] qwertyaas:
Since my last restart, my phone has an uptime of 432h 47m...!
[Captivate Q&A, Help & Troubleshooting] socalledsin:
wth details please lol
[Captivate Q&A, Help & Troubleshooting] qwertyaas:
I don't mean on one charge ;)

Usually I get home from work with 50-55% charge with medium usage (unplugged the night before around 11pm). I use Edge network however, and minimal 'updating' widgets.
[Captivate Q&A, Help & Troubleshooting] socalledsin:
What did you do to fix it? (sorry if I missed that post lol)
[Captivate Q&A, Help & Troubleshooting] qwertyaas:
Right now I left my phone stock and really don't have all too much installed. I only had one shutdown since I 'factory reset' my phone last.

Guess that's not much help though :p
[Captivate Q&A, Help & Troubleshooting] mrx_rf:
I've solve the problem by using captivate keep alive. From my observation, the shutdown usually happen during high battery level so i finetune the captivate keep alive bar down to 65%. So far no more random shutdown. Make sure to refresh keep alive after full charge and never ever kill the apps when your battery level is above 65%.

I hope this help. Thank you.
[Captivate Q&A, Help & Troubleshooting] gibson3659:
That's exactly how mine was, around 65%. A factory reset has allowed me to slowly push Keepalive to 98%, so far. I may try disabling it all together soon to see if it still shuts down.
[Captivate Q&A, Help & Troubleshooting] dwmoss:
I'll go over my nightmare experience at the att store yesterday.

We have 2 captivates on our account, mine is 1007 and my step sons whose is 1008. Both purchased through amazon wireless, one beginning of sept. other middle of september.

Both have been getting random shutdowns, we've both been using captivate keep alive to help minimize it. I've been following this thread for a while and tried a number of the ideas discussed in this thread with out any luck. Factory reset seemed to help for a while but didn't solve the issue.

Finally had enough and wanted to setup the warranty exchanges to get newer models that hopefully won't have the issue. My wife had stopped by the att store earlier in the week and was told for us to stop by with the phones so they could help troubleshoot and help with the warranty exchange.

So we went down last night on our way to taking my step son to his fathers. Left about 45 minutes earlier then usual to leave plenty of time. Store was packed took about 5 minutes to get waited on, The manager claimed she had never heard of anyone having this issue, of course. But she quickly got on the phone for warranty exchange and proceeded to be on hold for ever. After checking the water indicators, software version, damage etc.. she had me talk with the warranty exchange contact. That guy claimed he had a captivate and never heard of anyone having this issue. I told him and the manager they needed to google "captivate random shutdowns" or even look at their own att forums.

He also needed me to explain to him how I did the factory reset before he could process any warranty exchange. I told him i did it according to the steps in the owners manual but I didn't have them memorized while standing at the att store on the phone with him. He explained to me that he has a captivate and never read the manual. (What does that have to do with me??) Anyway the store manager brought up a copy of the manual, a told her to turn to page ~115 and read to the warranty exchange guy what the manual said. Really?? I need to read to you a page from the manual on the phone while i'm standing at the att store?? Seriously??

Anyway have both captivates have warranty exchanges coming minus the battery and backplates in 5-7 days unless I wanted to pay them for faster turnaround. No thanks, I don't want to pay you more money for my faulty product.

Ended up being a 75 minute process standing at a counter in the att store. Never again, in the future I'll just call the warranty exchange department from home while I'm powning noobs on halo at the same time.

cliff notes: call warranty exchange at 8008011101 instead of going to an att store and be prepared to have your owners manual ready to read it to the warranty exchange rep.

Sorry to ramble but I'm still pissed off about the whole experience 13 hours later.

:mad:

dm