Captivate random shuts down

Maroon Mushroom

Senior Member
Jul 15, 2010
1,172
444
0
Portland, Oregon
I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.

Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.
I had this same issue. The second I disabled the superuser permissions of SetCPU it fixed itself.

Hope this helps if you have that app installed.
 

DesertZero

New member
Jul 25, 2010
2
0
0
Ohio
I think I've found a solution, one that works for me anyway. YMMV. I have found that if I disable the display power saving mode (Settings->Sound and display->Power saving mode), then the problem does not occur. With that setting disabled (unchecked), I can leave my phone sitting idle on my desk for over an hour without it automatically shutting down. I was not able to do this yesterday before I found this setting. I'd be curious to know if this also works for anyone else besides myself.

(This was also cross-posted on the AT&T forums).
My mileage is, in fact, different...my phone just shut itself down again and I checked what you suggested. I must have already turned it off when I got the phone as this option was already unchecked.

This is getting quite annoying.
 

ice3186

Senior Member
Feb 26, 2008
223
93
0
Possible answer

Okay so here is the skinny on how my Captivate is set up.

I am running not only ATK, but AutoMemManager AND Setcpu.

According to this thread I am doing everything wrong.

I have read the whole string and taken into account a few things. And i am running stable now.

1.) If you are using setcpu make sure your not running any profile or setting that is "on demand"

2.) Never set any of your profiles to anything less than 400MHz

3.) If your having problems with your alarm clock or what not shutting down, go into either AutoMemory or ATK and set that program to "ignore" or "white list"

4.) some programs to consider whitlisting: Live wallpapers if your using them, Android System, Clock, your email programs for push, Swype, your MemManager, things like that

5.) I have my kill intervals on both programs set to as often as possible and in ATK i am on the safe setting.

Okay I think that is the skinny.

Things to note:
I am running the method 1 speed fix (just search the forum)
I am getting quadrant scores up to 950, always above 900( i was getting about 850-860 previously)

hope this helps and just post back if your having problems!
 

zorphnog

Member
Jul 26, 2010
24
0
0
Just saw this thread as I had previously posted the same topic in the General Captivate subforum. I have the same issue and I went as far as reinstalling the stock ROM and have no Apps installed at all, and the issue still exists.

The only thing I have done since reflashing the stock ROM is sync my google account and my work exchange account. I saw a previous post in here about calendar events causing the issue. Maybe an exchange account issue with the email client?
 

eatkabab

Senior Member
Jan 4, 2007
366
16
0
I have a whole new dimension of whats going on. My phone NEVER did this until I did a factory reset. Now I get good-ish batt, but it seems to restart at roughly the same time each night.

I don't have any CPU clocker or task killer but I do have launcher pro and I did before my reset as well.

This is terrible, I cant rely on my phone as an alarm anymore. this MUST be fixed. It turned off twice in 2 hrs last night.
 

checkers2884

Member
Jul 28, 2010
14
0
0
Call Samsung Galaxy S Support

I called Galaxy S Support which is a special tier that you will be forwarded to when you tell the customer service tech that you have a Galaxy S phone. The guy I talked to said that he was unaware of any issue like the one we are experiencing. PLEASE make sure you are calling Galaxy S tech support because if they do not get enough calls about this, they will just dismiss it as a defective device which I really don't think it is.

There have been issues in the past with other Android phones having the same problem. This is something they should really be handling on their end I believe and not something that we should be returning phones for.

As far as my phone's setup is concerned, I have NO apps at all for memory or CPU management. My previous post can describe the exact series of events that causes the issue every time for me. I don't mean to sound like a jerk here but seriously try to take the time to bug Samsung about this issue because this is their flagship phone line and they will definitely fix the issue if they know it's spread out wide enough. Make sure you call them. If you just email them the email response you get will be worthless.
 

Ricparr

Member
Jul 26, 2010
33
1
0
Same issue here. I don't use setcpu and it is not rooted yet, nor do I use an alternative launcher/home. I do have ATK and that's about it. I hope someone comes up with a solution for this, I would hate to see my phone go back or even the entire galaxy s line for that matter, over a bug!
 

checkers2884

Member
Jul 28, 2010
14
0
0
Hey guys, I was having this problem as well. I called the Samsung Galaxy S premier support line and the tech suggested a factory reset by typing in the following on the dial pad:

*2767 *3855 #

Since doing this a week ago I haven't had my phone shutdown on it's own. FYI, it WILL RESET EVERYTHING so please remove your sim and SD card before doing so and backup anything you have stored on the internal flash memory. ALSO, I highly suggest doing this with a fully charged battery just in case.

Let me know if this helps anyone else.
 

eatkabab

Senior Member
Jan 4, 2007
366
16
0
I called Galaxy S Support which is a special tier that you will be forwarded to when you tell the customer service tech that you have a Galaxy S phone. The guy I talked to said that he was unaware of any issue like the one we are experiencing. PLEASE make sure you are calling Galaxy S tech support because if they do not get enough calls about this, they will just dismiss it as a defective device which I really don't think it is.

There have been issues in the past with other Android phones having the same problem. This is something they should really be handling on their end I believe and not something that we should be returning phones for.

Whats the number? I'll call every single damn day. I'm so annoyed that every time I go to use my phone its frikin OFF!
 

checkers2884

Member
Jul 28, 2010
14
0
0
Whats the number? I'll call every single damn day. I'm so annoyed that every time I go to use my phone its frikin OFF!
Unfortunately, there is no direct number. You will just have to call Samsung tech support and tell them that you have a Galaxy S phone and would like to speak with the Galaxy S Premier tech support. As soon as I told the girl my model number she just transferred me and said she wasn't properly trained to troubleshoot that line of phone.

Like I mentioned in my previous post, try the factory reset.
 

yinNout

New member
Aug 9, 2010
4
0
0
PLEASE make sure you are calling Galaxy S tech support because if they do not get enough calls about this, they will just dismiss it as a defective device which I really don't think it is.
It may actually just be a defective device. I experienced the same issue and wound up exchanging the phone for a new one. While the old one would shut down while charging each night, the new one has not, despite having all the same apps and stuff.

FWIW, I haven't rooted the phone yet -- old or new.

It could just be bad RAM that causes the device to crash and shut down when reading corrupted memory -- much like what PCs do when equipped with faulty RAM chips.

If it starts happening again, I'll eat my words and update you guys.
 
Last edited:

checkers2884

Member
Jul 28, 2010
14
0
0
It may actually just be a defective device. I experienced the same issue and wound up exchanging the phone for a new one. While the old one would shut down while charging each night, the new one has not, despite having all the same apps and stuff.

FWIW, I haven't rooted the phone yet -- old or new.

It could just be bad RAM that causes the device to crash and shut down when hitting reading corrupted memory -- much like what PCs do when equipped with faulty RAM chips.

If it starts happening again, I'll eat my words and update you guys.
You make valid points. How long has it been since you got the new phone? I'm thinking of exchanging mine just to be safe.
 

ieee1394

Member
Mar 8, 2007
38
0
0
Mine hasn't done this again since the very first time. The only thing I've changed in the meantime is to change WiFi settings so that radio never turns off while its within range of a known AP. Just as an FYI, doing that will also wildly increase your battery standby time: with WiFi at the office and at home, I can get over 24 hrs of standby time. 3G really kills the battery, especially if you're in a marginal area as I am.

Now, taking that statement into consideration, perhaps its some process that calls out to the Internet and hangs badly when it can't connect? I know the first motivation is to start installing apps on these things when you get them, and some of those apps can be configured to update automatically...the only app I have running that updates automatically is ActiveSync. I haven't turned any other autoupdates on.

From observation, I'd say that these devices don't handle network outages particularly well. Which is a shame. I've even seen certain sites crash the browser.
 

zorphnog

Member
Jul 26, 2010
24
0
0
It may actually just be a defective device. I experienced the same issue and wound up exchanging the phone for a new one. While the old one would shut down while charging each night, the new one has not, despite having all the same apps and stuff.

FWIW, I haven't rooted the phone yet -- old or new.

It could just be bad RAM that causes the device to crash and shut down when hitting reading corrupted memory -- much like what PCs do when equipped with faulty RAM chips.

If it starts happening again, I'll eat my words and update you guys.
I exchanged mine exactly one week ago for this exact issue and I haven't seen it happen once. Mine was shutting off 1-3 times a day on average before I exchanged for the new one. I definitely think there is a hardware issue with certain batches of the phone. Perhaps bad RAM as you suggested.
 

astrocrep

Senior Member
Oct 17, 2007
363
21
0
Central Jersey
Mine hasn't done this again since the very first time. The only thing I've changed in the meantime is to change WiFi settings so that radio never turns off while its within range of a known AP. Just as an FYI, doing that will also wildly increase your battery standby time: with WiFi at the office and at home, I can get over 24 hrs of standby time. 3G really kills the battery, especially if you're in a marginal area as I am.

Now, taking that statement into consideration, perhaps its some process that calls out to the Internet and hangs badly when it can't connect? I know the first motivation is to start installing apps on these things when you get them, and some of those apps can be configured to update automatically...the only app I have running that updates automatically is ActiveSync. I haven't turned any other autoupdates on.

From observation, I'd say that these devices don't handle network outages particularly well. Which is a shame. I've even seen certain sites crash the browser.

Can you explain a bit more about this wifi settings.

Thanks,
Richard P.
 

ieee1394

Member
Mar 8, 2007
38
0
0
If you go into your Settings->Wireless and network->Wi-Fi->Menu->Advanced.

The default behavior is to turn the radio off whenever the screen goes off. That forces your device to switch back to cell service. WiFi uses much less power. I don't want to hijack this topic so that's all I'll say about it here....but perhaps loss of a data signal is a contributing factor to these shutdown problems.
 

eatkabab

Senior Member
Jan 4, 2007
366
16
0
Unfortunately, there is no direct number. You will just have to call Samsung tech support and tell them that you have a Galaxy S phone and would like to speak with the Galaxy S Premier tech support. As soon as I told the girl my model number she just transferred me and said she wasn't properly trained to troubleshoot that line of phone.

Like I mentioned in my previous post, try the factory reset.
It only started happening after I did a factory reset to fix the batt issue. well it did fix the batt issue...
 

Jack45

Senior Member
Jul 2, 2010
632
168
0
Happened to me a short while ago for the first time. I read all of the pages in this thread and there does not appear to be a common link to this problem. From where I stand, this is a very serious issue. I will not reset, I will not exchange. If there's no guaranteed solution discovered in the next few days it's over for me. And as I wrote on another forum, I've been a supporter of the device after getting it on day one.