I searched the forums with several different keywords to try to find similar threads about random shutdowns on Galaxy S phones, but I didn't find any, so I'm starting my own. I've noticed over the past couple weeks since I bought my Captivate that it will randomly shut down. Most often, it happens during the night, usually while it's charging or just after it reaches a full charge. This morning I noticed it had a pull charge so I unplugged the wall charger and went to take a shower. By the time I got out 15-20 minutes later, my phone had shut itself down. A few hours later at work this morning, it shut itself down again. It's been doing this for several days.
Has anyone else experienced this issue? Like I said, I didn't see the issue reporting here on the AC forums, but I found several other threads at AndroidForums (Phone Shutting off Randomly?), at the XDA-Developer forums (Captivate Random Shuts Down), and at AT&T's own forum (Captivate Random Shut Downs). It seems that most people are mentioning the same circumstances where the phone shuts down soon after charging.
I am running Advanced Task Manager Free, but I'm not using any Autokill features. I'm not running SetCPU, as some others in those linked threads mention. Some said they had success with the issue by running SetCPU and increasing the minimum CPU frequency during sleep, but just as many others said that didn't help. It also seems that the random shutdowns are happening even to users with fresh new phones with very few apps installed and no task killers, so it doesn't seem to be entirely related to task killers.
How many of you are seeing this issue? My intention was not to duplicate other threads, but just to spread the word and see if the AC community had any ideas or solutions. Hopefully, maybe the AC news crew will pick up this topic and do some investigation with their contacts. I've tried to investigate Samsung's response to the issue, but so far, they haven't mentioned anything. All their replies seem to mention something off-topic about battery usage instead of addressing the shutdown issue.
If you are seeing this issue, could you share the circumstances and whether or not you're running task killers or SetCPU, and how new/old your phone is? I've heard this issue may extend to the Vibrant as well, so it's possible that it affects all Galaxy S phones. If we can accumulate details and investigate the issue, maybe we can keep Samsung accountable and get an OTA update or something to fix it. Thanks for the help!
Has anyone else experienced this issue? Like I said, I didn't see the issue reporting here on the AC forums, but I found several other threads at AndroidForums (Phone Shutting off Randomly?), at the XDA-Developer forums (Captivate Random Shuts Down), and at AT&T's own forum (Captivate Random Shut Downs). It seems that most people are mentioning the same circumstances where the phone shuts down soon after charging.
I am running Advanced Task Manager Free, but I'm not using any Autokill features. I'm not running SetCPU, as some others in those linked threads mention. Some said they had success with the issue by running SetCPU and increasing the minimum CPU frequency during sleep, but just as many others said that didn't help. It also seems that the random shutdowns are happening even to users with fresh new phones with very few apps installed and no task killers, so it doesn't seem to be entirely related to task killers.
How many of you are seeing this issue? My intention was not to duplicate other threads, but just to spread the word and see if the AC community had any ideas or solutions. Hopefully, maybe the AC news crew will pick up this topic and do some investigation with their contacts. I've tried to investigate Samsung's response to the issue, but so far, they haven't mentioned anything. All their replies seem to mention something off-topic about battery usage instead of addressing the shutdown issue.
If you are seeing this issue, could you share the circumstances and whether or not you're running task killers or SetCPU, and how new/old your phone is? I've heard this issue may extend to the Vibrant as well, so it's possible that it affects all Galaxy S phones. If we can accumulate details and investigate the issue, maybe we can keep Samsung accountable and get an OTA update or something to fix it. Thanks for the help!
Facebook
Twitter
Instagram