Random Shutdowns and LauncherPro - Captivate General

I've been very careful not to point a finger at a particular app as a cause of random shutdowns (other than aggressive user settings within SetCPU). Before I continue, let me say that I believe there is more than one culprit responsible for shutdowns and that most are caused by non-app related issues.
I've had my third device for 2-1/2 months. No shutdowns whatsover...until I installed LauncherPro last week. Then they started. I removed LauncherPro and - back to normal. Another user on another forum experienced the same effect and caused me to start this thread. I hereby declare an official suspicion that LauncherPro is one of the causes of random shutdowns. Before you react, I understand that many use LauncherPro with no problems. Great. I'm not saying that the app itself is poorly coded, but rather that it may begin a chain reaction in some devices that causes random shutdowns. I have not taken this declaration lightly. I waited a long time before openly stating my theory. I hope it proves of interest.

Are you using Task Killer? I was having the same issue and thought it was Launcher Pro for a while but when I stopped using Task Killer my random shutdown problems stopped.
Captivate Cog 2.2 Beta 9

No task killers.

I've recently had some extended freezes and one force close with launcher pro, and one shutdown when I was launching Vlingo and/or starting bluetooth, can't recall which step. Might be something to do with the recent update.
Sent from my SAMSUNG-SGH-I897 using XDA App

I suppose I can test this out on mine. I'll let you know what I find.

I was using LauncherPro on my previous handset which experienced random shutdowns, but the shutdowns continued even after reflashing to factory with no add-ons or apps. Not saying that LP isn't causing problems of it's own, but power issues exist regardless.

I've been using LauncherPro (and upgraded to Plus when that came out) since release. No random shutdowns. Actually no random shutdowns at all. But I guess I'm lucky

pezx44 said:
I suppose I can test this out on mine. I'll let you know what I find.
Click to expand...
Click to collapse
Your device would have to be inherently susceptible to shutdowns caused by the action of LauncherPro for your test to work. If your internals are solid, nothing will happen.

pfroo40 said:
I was using LauncherPro on my previous handset which experienced random shutdowns, but the shutdowns continued even after reflashing to factory with no add-ons or apps. Not saying that LP isn't causing problems of it's own, but power issues exist regardless.
Click to expand...
Click to collapse
Agree. LP, IMHO, is simply offered as one possible culprit.

tysj said:
I've been using LauncherPro (and upgraded to Plus when that came out) since release. No random shutdowns. Actually no random shutdowns at all. But I guess I'm lucky
Click to expand...
Click to collapse
You are fortunate, as there are multiple scenarios under which shutdowns have occurred...e.g., during high charge percentages as experienced repeatedly by some. My LP experience is being offered as my phone has served as an otherwise stable environment.

Jack45 said:
Your device would have to be inherently susceptible to shutdowns caused by the action of LauncherPro for your test to work. If your internals are solid, nothing will happen.
Click to expand...
Click to collapse
Oh I'm quite susceptible. I get it regularly until my battery is down to about 82. I've used LP the whole time I had the phone. Currently I am using Captivate Keep Alive and it seems to work. I also started another thread where I found that running Grooveshark keeps the phone alive for me. I can guarantee that my phone will shut off within a couple of minutes of unplugging it without these things.
I'm charging now. I have already backed up and removed LP and CKA. When it is fully charged I will unplug it and leave it alone for a bit and report back. I agree with people who say "hardware issue - return it" but I can't do that and don't mind testing different workarounds. So far CKA has been working pretty well for me but I'm open to running less instead of more to solve it.

pezx44 said:
Oh I'm quite susceptible. I get it regularly until my battery is down to about 82. I've used LP the whole time I had the phone. Currently I am using Captivate Keep Alive and it seems to work. I also started another thread where I found that running Grooveshark keeps the phone alive for me. I can guarantee that my phone will shut off within a couple of minutes of unplugging it without these things.
I'm charging now. I have already backed up and removed LP and CKA. When it is fully charged I will unplug it and leave it alone for a bit and report back. I agree with people who say "hardware issue - return it" but I can't do that and don't mind testing different workarounds. So far CKA has been working pretty well for me but I'm open to running less instead of more to solve it.
Click to expand...
Click to collapse
Excellent. Two separate potential culprits - charge level and LP. I'm looking forward to your assessment.

I decided to reinstall LP to get a baseline. 6 minutes after unplugging it I tried to turn the screen back on and found that it had shut down. I recharged and repeated. Again I found it had shut down when I checked after 6 minutes.
I then recharged and removed LP. I waited 6 minutes and found that it was still on. I am recharging and will try again after a longer period of time but it looks promising. I will let you know when I have more info.

Well, no dice. I checked after a half hour and it was off. I'm open to any other experiments though.

pezx44 said:
Well, no dice. I checked after a half hour and it was off. I'm open to any other experiments though.
Click to expand...
Click to collapse
You have no complaints, my friend. A half hour of uptime is better than 6 minutes!
So, yours is a power-related issue and it looks like CKA is the answer. I wonder if Froyo will address this.

But it was only a half hour when I saw it was off. It could have been 6.5 minutes in.
I'm currently running Froyo (Cognition 8.1). This has been an issue for me since before that though. One thing I can't quite remember is if it happened before I unlocked my phone. Is yours unlocked? I needed to do this because I do not live in the US.

pezx44 said:
Is yours unlocked? I needed to do this because I do not live in the US.
Click to expand...
Click to collapse
Unlocked, rooted, and stable (which is more than I can say for myself).
On a more serious note, when I first received my replacement I created the following settings to try to avoid the shutdowns until I was confident that the phone was o.k.
For your consideration:
1. Wi-Fi was always on and is set to never sleep. The "never sleep" settings can be accessed via the Wi-Fi settings page menu, Advanced tab at the bottom. Reason: I'm attempting to generate additional under-the-cover activity (plus I do use Wi-Fi). As I'm not a technician, this may be nonsense.
2. Power saving mode was not checked. Reason: "Don't do me any favors, Captivate. Your idea of power saving may get out of hand."
3. I never let the phone go into sleep mode on its own (that's still the case). Default is 30 minutes, but I always push the button to get it to sleep and get it to wake. Reason: Just in case the built-in sleep timer thinks that "sleep" and "coma" are synonymous.
You can try these three mods to see if they work for you. Remember to uninstall CKA for now to make the above a valid test.
Don't forget to write.

Jack45 said:
Unlocked, rooted, and stable (which is more than I can say for myself).
On a more serious note, when I first received my replacement I created the following settings to try to avoid the shutdowns until I was confident that the phone was o.k.
For your consideration:
1. Wi-Fi was always on and is set to never sleep. The "never sleep" settings can be accessed via the Wi-Fi settings page menu, Advanced tab at the bottom. Reason: I'm attempting to generate additional under-the-cover activity (plus I do use Wi-Fi). As I'm not a technician, this may be nonsense.
2. Power saving mode was not checked. Reason: "Don't do me any favors, Captivate. Your idea of power saving may get out of hand."
3. I never let the phone go into sleep mode on its own (that's still the case). Default is 30 minutes, but I always push the button to get it to sleep and get it to wake. Reason: Just in case the built-in sleep timer thinks that "sleep" and "coma" are synonymous.
You can try these three mods to see if they work for you. Remember to uninstall CKA for now to make the above a valid test.
Don't forget to write.
Click to expand...
Click to collapse
1. I have the same setting for wifi (I use my phone for SIP calls often).
2. I absolutely agree with you on this and it is also already my setting.
3. I always turn off my screen too, but I will set it to 30 minutes to see if that makes a difference and test again without LP/CKA. I can't see how it would be related but I certainly don't mind trying it if for no other reason than to rule it out.
I'll let you know how things go.
And just in case, by unlocked we are talking SIM unlocked right?

>>> I always turn off my screen too, but I will set it to 30 minutes to see if that makes a difference and test again without LP/CKA. I can't see how it would be related but I certainly don't mind trying it if for no other reason than to rule it out.
As the timeout for sleep mode is power-related, I wanted to take that out of the Captivate's hands. The on-off switch is OURS to deal with at will. Want the room light on? Turn it on. Etc. Basically, I wanted to generate persistent under-the-cover activity (WiFi) while eliminating decision making activity on the part of the device.
>>> And just in case, by unlocked we are talking SIM unlocked right?
I can place any non-AT&T SIM in the phone and it will work.

No LP issues here since I've owned the phone.
I've had LP on with full charge all the way down to 30% +/- and still ran like a champ.
Currently on Cognition beta 9 - still the same story.
I truly think you have a lemon phone. And I just flashed and haven't tweaked any of the default settings that are "out of the box" after a flash... so I assume they are all default.
The only FC/shutdown issues I've had recently were with Cognition beta 7 and advanced audio manager. I removed it and *poof* no more FC's. And since I was never that concerned with my sound settings (it's on vibrate 99% of the time anyways due to work environment and a lil' guy) I didn't care.
I'd look into getting a refurb - or flashing to Cognition's latest and greatest (hmm... well I would wait for 9.2 as he is having some "growing pains" with his new kernel) and see how it goes then. Can always Odin back to stock if needed.

Related

Random Shut Down Issue - Theory: Let's compare apps

Some of us are having problems with our Captivate randomly shutting down. AT&T technical support thinks it could be apps that we've installed. Could they be right? My replacement device didn't start shutting down again after 3-4 days of owning it. By that time, I have already installed some favorite apps. Here's my list. Let's compare and figure this out. It's just a theory. Can't hurt.
<<<< OMG! While typing this new thread to turn on my phone so I can see the list of apps I have installed, MY PHONE TURNED OFF ON ME! WHAT THE...!!! >>> Anyway...
Apps installed:
-SMS Back Up and Restore
-Yahoo! Mail for Android
-Adobe Reader
-XDA-Developers
-Market History Manager
-Speedtest.net
-Google Maps
Mine never did it until I set advanced tag killer to harsh every half hour. I watered down the harshness a little bit and it hasn't shut off since
Sent from my SAMSUNG-SGH-I897 using XDA App
Theres a thread in the vibrant section that's about the same problem and it happens after 3 days could try there
Sent from my Nexus One using XDA App
Thanks. I just posted on an existing thread over there. I will do a hardware master reset later and observe again the next 3-4 days. Samsung gave me the directions. (Hold the volume up and down plus the power button, all 3 buttons for 15 seconds, etc.)
most are saying that its bad RAM/memory and exchanging the handset fixed all the problems
andy2na said:
most are saying that its bad RAM/memory and exchanging the handset fixed all the problems
Click to expand...
Click to collapse
Is there a memtest type application for android? Bad memory would make sense, but so would a number of other theories.
Ur welcome hope it helps and u get it figured out
Sent from my Nexus One using XDA App
RexEscape said:
Thanks. I just posted on an existing thread over there. I will do a hardware master reset later and observe again the next 3-4 days. Samsung gave me the directions. (Hold the volume up and down plus the power button, all 3 buttons for 15 seconds, etc.)
Click to expand...
Click to collapse
Yeah, that's their answer for all problems, big and small. I'm sure in some cases it's valid, but the reset is used more as a "what the hell' reply rather than a knowledge-based solution.
Jack45 said:
Yeah, that's their answer for all problems, big and small. I'm sure in some cases it's valid, but the reset is used more as a "what the hell' reply rather than a knowledge-based solution.
Click to expand...
Click to collapse
...which I agree to some point. Some users just end up loading crap on devices which screws things up (some of the apps mentioned above might be crap, or not, not sure, it's only a theory. Of course, a perfect device is a unit that can withstand ANY apps you feed to it. But we don't have THE perfect device (yet, or ever).
I will do the hardware master reset in a few minutes and not load anything for 3-4 days (but I will enter my Gmail account and let it sync with my Contacts, Calendar, and Email, but that's it...for now).
RexEscape said:
...which I agree to some point. Some users just end up loading crap on devices which screws things up (some of the apps mentioned above might be crap, or not, not sure, it's only a theory. Of course, a perfect device is a unit that can withstand ANY apps you feed to it. But we don't have THE perfect device (yet, or ever).
I will do the hardware master reset in a few minutes and not load anything for 3-4 days (but I will enter my Gmail account and let it sync with my Contacts, Calendar, and Email, but that's it...for now).
Click to expand...
Click to collapse
What steers me away from the app theory is that there have been several posts indicating that the random shutdowns have occurred with a stock device. No apps downloaded / installed.
I don't have an answer except to say that the master reset can't hurt. Realistically, though, if you go a few days without a shutdown don't sit back and smile like the Cheshire Cat. Sometimes the shutdowns occur weeks into ownership. I'm not being negative, just realistic.
I wish you well.
Jack45 said:
What steers me away from the app theory is that there have been several posts indicating that the random shutdowns have occurred with a stock device. No apps downloaded / installed.
I don't have an answer except to say that the master reset can't hurt. Realistically, though, if you go a few days without a shutdown don't sit back and smile like the Cheshire Cat. Sometimes the shutdowns occur weeks into ownership. I'm not being negative, just realistic.
I wish you well.
Click to expand...
Click to collapse
Agreed. Like I said, this is my second device and the shutdowns didn't start until 3-4 days after ownership on both devices. The reality (for me) is that the Captivate isn't so great after all after two devices already (sorry to say) but I'm not going to give up just yet. I have until the 31st to decide whether I will continue this 30-day early upgrade trial or take it back and continue to use my HTC Fuze and just let my contract expire (in October). If I take it back, come October, I will decide whether I will stay with AT&T and take on another (hopefully bug-free) Captivate, or move to Verizon and check out their Android phones -- HTC and Motorola devices!
I just did a hardware master reset. It isn't exactly a hardware master reset like the tech guy described it. He gave me the directions to "delete user data". It deleted the apps that I have downloaded from the Market, and other things. I don't know what else. However, when it booted up again, I noticed my settings and widgets are still there. My homescreen was still customized the way I had it. So, it's not a total master reset. The software Factory Reset isn't also a total (software) reset. I did that and found some folders left in my internal memory (not my external MicroSD) from the previous working session. Hmm..
my captivate started to shutdown about five days ago. it's been doing it once a day, always in the morning. i wonder if it has something to do with the power management. the phone is always charged overnight and the shutdowns always seem to happen about an hour or so after i unplug it from the charger.
the one day it didn't shut down, i noticed that the lock screen was unresponsive (ie i couldn't unlock the phone) and i ended up having to power down the phone anyway.
vksf01 said:
my captivate started to shutdown about five days ago. it's been doing it once a day, always in the morning. i wonder if it has something to do with the power management. the phone is always charged overnight and the shutdowns always seem to happen about an hour or so after i unplug it from the charger.
the one day it didn't shut down, i noticed that the lock screen was unresponsive (ie i couldn't unlock the phone) and i ended up having to power down the phone anyway.
Click to expand...
Click to collapse
exactly how it happens on mine.
i'll see what happens over the rest of the week and then try the master reset. if it still happens, i'm going to return this for another one. unfortunately, i've had it for over 30 days.
vksf01 said:
i'll see what happens over the rest of the week and then try the master reset. if it still happens, i'm going to return this for another one. unfortunately, i've had it for over 30 days.
Click to expand...
Click to collapse
Even after 30 days, you will still be able to return it (maybe to Samsung) for repair or a replacement. Good luck.
vksf01 said:
my captivate started to shutdown about five days ago. it's been doing it once a day, always in the morning. i wonder if it has something to do with the power management. the phone is always charged overnight and the shutdowns always seem to happen about an hour or so after i unplug it from the charger.
the one day it didn't shut down, i noticed that the lock screen was unresponsive (ie i couldn't unlock the phone) and i ended up having to power down the phone anyway.
Click to expand...
Click to collapse
Mine has shut down twice, and I've only had it for 12 days. As you described, it happened both times in the morning, following a recharge.
I had to remove and replace the battery to get it to turn back on, is that the same thing that happened to you? I mean to say, did you have to remove and replace the battery to get it to work again?
The two Captivates I've owned (and returned due to a combination of GPS and Random Shut Downs) have shut down on me even in the middle of the day (not only in the morning after recharging for the night). It shut down on me while getting my afternoon coffee. I was showing the phone to the Barista, set the phone down on the counter to pay, picked it up, walked back to my office and just when I'm about to wake it up, it does the bootup. It also shut down on me at night while walking in the dark. I noticed my pocket lit up. I pulled out my phone and I saw the Shut Down screen as if you had pressed and held the power button (but nothing else was in my pocket that could have pressed the button!).
Random, I tell ya. Random.
pmpntl said:
exactly how it happens on mine.
Click to expand...
Click to collapse
Larry202br said:
Mine has shut down twice, and I've only had it for 12 days. As you described, it happened both times in the morning, following a recharge.
I had to remove and replace the battery to get it to turn back on, is that the same thing that happened to you? I mean to say, did you have to remove and replace the battery to get it to work again?
Click to expand...
Click to collapse
no, i just turned it back on using the power button.
I just wanted to chime in to say that I am having the same problem. Random shutdowns, not necessarily related to charging. Often they are in the morning however. For me it has been happening a few times a day. Likewise, it seems to have not happened at first, but began a few days ago (I have owned the phone about 2 weeks.)
Are you guys rooted? I have tried unrooting to see if that matters. I don't know why it would, but perhaps...

Random shutdown solution!

Random shut down solution! At least for me.
My phone shuts down pretty much 2-5 times a day since i got it. No matter what I do to it. But I tried the app, load monitor and enabled WAKE LOCK and my phone hasnt rebooted in 4 days!
Anyone else had similar experience.
Sent from my SAMSUNG-SGH-I897 using XDA App
Umm, not meant in an asshat way at all man, but your real solution is to take that sucker back. I wouldn't put up with that at all. Bad phone. Just my opinion.
From a phone on an app
I have to agree with the post above mine. I believe it's a hardware issue and that you should return it for another one. I have two captivates and neither I've of them have ever had the random shutdown issue.
Truth is, the phone is bad. Ask for a warranty replacement. I went through 2 phones until I got a good one with no issues. A perfectly good working phone should never randomly shut off as mine were doing before (4-10 times a day) Even setting Set-CPU to 1000mhz 100% of the time didn't fix the other phones I had. Hell, even leaving the screen on the entire time one of them still shut off once.
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Did you have set cpu installed? That's what happened to me after installing set cpu. Sometimes it would lock up after the screen went off & sometimes it would just reboot randomly. I got around this by setting the min clock speed to 200mhz. I think set cpu sometimes undervolts the cpu when scaling especially at 100mhz & at 1000mhz when the screen is off. If it did that stock then I would definitely return that pos! Wake lock will kill your battery life.
Sent from my SAMSUNG-SGH-I897 using XDA App
Well we will see. I was in the process of a rma and just got the phone last night.
I see if the new one has any issues. By the way this will be my 4 th phone(3 through the first month, this one through rma). So the get another phone idea kind of sucks.
Just a curser glance at the back of the rma phone and I can see its different. So maybe I'll get lucky on it.
Sent from my SAMSUNG-SGH-I897 using XDA App
. .
Same here, I'm in Australia, I bought the phone from the US, It used to shutdown 3 - 5 times a day, especially when it's fully charged. Wiped the phone (Internal and external) and now it's solid stable. no special apps or settings or whatsoever. It's a little bit weird though.
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
I leave mine plugged in all the time overnight and it has Never booted off
Sent from my SAMSUNG-SGH-I897 using Tapatalk
galaxyjeff said:
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I thought the same, but last night I forgot it on the charger with no problems at all, No shutdowns... Strange...
It happens to my Samsung S Vibrant and I *think* I can reliably reproduce the issue, at least on my phone.
Steps:
1. Go to a spot where you know it has failed, for me this is my office because it has bad reception and it seems to only shutdown for me when there is bad reception.
2. Make sure 3G is turned on and open an application that uses data.
3. Wait for the phone to sleep, do not hit the power button or anything to make it sleep (not sure if this step matters)
4. Wait ~30 mins without touching the phone (You can play music with it while this is happening if you want, the music will stop to let you know it's failed)
5. Try to wake up your phone, it is now dead.
I'm not sure this will work for everyone but last night I could reproduce 3 shutdowns in an hour and a half. And reproduced about 7 shutdowns yesterday when my phone only usually shuts down ~2 times a day.
I'm testing out all kinds of software permutations (disabling stuff, installing things like Captivate Keep Alive). Nothing has worked so far, my guess right now is that the problem lies in the Pattern Unlock feature so I have disabled it, I read that on a forum somewhere.
My guess is that if you have too much running in the background it might take up too much cpu or ram so that when the phone tries to come out of sleep it can't get enough CPU power to come out of sleep and therefore gets stuck in a kind of limbo. This theory could then be releated to the SetCPU problem when you set the CPU too low when it sleeps the issue occurs.
Moral of the storey is I have no idea what's going on, but please post if this works or doesn't work. Maybe it will shed some light on the issue, or you can tell me I'm wrong so I can give up. Let me know if you have Pattern Unlock enabled...
Luckily I'm not past the 30 day mark and I'm exchanging for a new Vibrant tonight. Wish me luck!
UPDATE: It's not the fault of Pattern Unlock, just reproduced the issue with it turned off.
UPDATE #2: Got my second Vibrant, just reproduced the issue within 30 mins of getting into work in the morning.
My Captivate used to shut off once every 2 weeks. Now it's doing it 4 times a day. However, I just found this app:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
Looks promising. I hope this works.
My wife's stock Captivate has been doing this for a week or two (our phones are about 6 weeks old). My rooted Captivate has -not- been doing it. We both have the same "plug it in all night" charging pattern. Hers will be going back shortly.
Jack45 said:
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Click to expand...
Click to collapse
Tha'ts not true.
My phone was working fine. Then I rooted it. Then I started sideloading bunch of apps. Randon shutdown started to happen. I started tracing back and deleted apps one by one. Didn't work. Replacing the phone was out of the question because I live in Canada and bought the AT&T phone cash off a seller.
SOLUTION:
if you have had SetCPU (or overclock app) and had it to anything to your phone, this is what you got to do.
Run the SetCPu again, and make sure that you do Max 200mhz and Min 200mhz.
Reboot the phone.
Then go into SetCPU, disable autodetect. Then uninstall app.
No more random shutdowns.
It is NOT a hardware issue.
I can confirm that the App stops my phone from shutting down.. unfortunately I have to set it to 65% charge for it to work (whereas others can leave it on default 80%).
Found my issue, it was happening when my phone was jumping between the 850 mhz band and the 1900 mhz band. It would freeze and only happen in areas of bad signal. Locked it on to the 850 mhz band and havent had a freeze since.
100 hours of uptime and counting
http://forum.xda-developers.com/showpost.php?p=8612667&postcount=386
I have also heard that some phones experience the issue when fully charged and that putting a wake lock on your phone with captivate keep alive will solve the problem. These are two independant issues.
i'm not really that knowledgeable about how the phone interacts with different bands, but i'm trying to fix this problem as well and i'll try anything. are there any side/adverse affects to locking it onto a single band?
Has anyone tried removing the sim? to see if it still turns off?
The problem im having is when its near full and goes to sleep i need to turn it back on (like it shuts off) but i tried removing the sim and has not had this problem

TRUE Solution! - Random Shut-Downs

Hey everyone!
My problem with random shut-downs on the captivate became unbearable, and I kept searching through threads for a solution, and I finally found this:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
This app doesn't let your CPU completely turn off when on standby.
I used it for a whole day and no shut-downs.
Usually, I'd get at LEAST 3 shutdowns a day.
I hope this helped you all.
What have you done to be getting random shutdowns? I've flashed multiple roms and used modded framework files and still I never get a random shutdown.
NeoXerO said:
Hey everyone!
My problem with random shut-downs on the captivate became unbearable, and I kept searching through threads for a solution, and I finally found this:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
This app doesn't let your CPU completely turn off when on standby.
I used it for a whole day and no shut-downs.
Usually, I'd get at LEAST 3 shutdowns a day.
I hope this helped you all.
Click to expand...
Click to collapse
Not bad. Wouldn't you want to have the convenience of NOT worrying about random shut downs (with or without) the app tho? I guess its just me, but those things would really irk me. lol
cappysw10 said:
What have you done to be getting random shutdowns? I've flashed multiple roms and used modded framework files and still I never get a random shutdown.
Click to expand...
Click to collapse
It's just pure luck. Some phones will randomly shutdown regardless what ROM you use. Some don't.
The only true solution so far is get a warranty replacement, or maybe couple replacements (the refurbs you get back may still suffer the same problem). Samsung itself has no clue what's the cause of it yet last time I checked.
NeoXerO said:
Hey everyone!
My problem with random shut-downs on the captivate became unbearable, and I kept searching through threads for a solution, and I finally found this:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
This app doesn't let your CPU completely turn off when on standby.
I used it for a whole day and no shut-downs.
Usually, I'd get at LEAST 3 shutdowns a day.
I hope this helped you all.
Click to expand...
Click to collapse
CKA is a possible solution for one of the anomalies that causes shutdowns. For additional information, use the forum's "Search" function and look for "Captivate Keep Alive."
i just starting to get shutdown once a day started 4 days ago. i trying to uninstall 1 app at a time to see what happen. just uninstall dolphin browser v4.0.
Jack45 said:
CKA is a possible solution for one of the anomalies that causes shutdowns. For additional information, use the forum's "Search" function and look for "Captivate Keep Alive."
Click to expand...
Click to collapse
Really? Well, this worked for me, and I had it pretty bad with those random shutdowns (even happened to me on stock 2.1 before flashing).
I think some people might be getting random shutdowns due to certain apps.
I 2nd that. I installed Keep Alive because my would shut down once a day after full charge but only if GPS is on. Mine doesn't shut down if GPS is off. Now it's been 3 days without any shut down and I leave GPS on continuously.
my phone shut down (1 time) daily, and i'm unable to reproduce the shutdown. maybe it' a memory leaks, it shuts down when it runs out of ram. going to reboot my phone (1 time) daily to see what happens...
NeoXerO said:
Really? Well, this worked for me, and I had it pretty bad with those random shutdowns (even happened to me on stock 2.1 before flashing).
I think some people might be getting random shutdowns due to certain apps.
Click to expand...
Click to collapse
I concur, I never had any shutdowns until I went to cog 7... And for the first week I didn't have any shutdowns, only after installing apps did this problem start. So I think you are correct that out has something to do with certain apps. Probably an app that is not fully compatable with android 2.2... I just wish I could figure out which app is causing this issue.
Sent from my SAMSUNG-SGH-I897 using XDA App
My phone keeps shutting off also. At first thought it was software, but even with a clean install of 2.1 with Odin and nothing added to it, it still did it. Then I thought it was the SD card, but still not it. I started noticing a pattern with it doing fine for 11-16 hours with a full charge depending on how much I used it, but it eventually shuts off. Every time I turned it back on, the battery is at <65%. I completely drained the battery last night and charged it back up and now it's doing it at 70%.
Anyone in this thread that has had at least 1 random shut down, or more, should look into a warranty replacement. A perfectly good working phone shouldn't shut down for the hell of it or because it "runs out of memory"
I went through this before and messed with the phone for a few days taking off apps, re-flashing etc... ultimately the problem went away when I simply just asked for a replacement unit.

Nice try LG, but, it's not quite ready for prime time!

I've been through 2 G2x's , both have had the same problems...
Random reboots
Random freezes
Random shutdowns
Crazy inconsistencies in battery life
I've also gone the route of rooting and trying CyanogenMod with the same results.
With the battery issues, I did the following test 3 nights in a row.
Phone wiped, 100% battery charge, signed into Google and let the apps download, rebooted phone, data connection turned off (airplane mode), unplugged the phone and set in the exact same spot in the same room 3 nights in a row at 11PM.
Come 8AM when I woke here's the results:
Day 1: 30% battery remaining
Day 2: 80% battery remaining
Day 3: 0% remaining - battery was stone cold dead - wouldn't boot until I plugged in.
Phone was fine when I started typing this post, but just now while typing this message I reached over to check my phone for text messages (I keep the alerts volume all the way down while at work) and it's locked up again...
Guess I'll be returning the phone for a refund and borrowing an old flip phone for a month until the Sensation comes out.
Sorry LG - when it works, it works AWESOME, but I need something a bit more reliable considering that work needs to contact me on the phone and I am on call 24/7 !
In the 2 weeks I've had it I've only had 2 random freezes and no other issues at all. This is my first android phone and the thing i see that's screwed up with android is it leaves applications open, there is no exit buttons on apps. I've been using juice defender and uninstalling any apps that keep popping back up after ending task on them.
Sorry to hear about your problems. You're doing the right thing by returning it and getting another phone. I don't understand why people have loyalties to corporations who could give 2 craps about you. Buy what works for you and makes you happy.
For me, the occassional reboot on the G2X is a pain but the promise of a stable CM release and an official gingerbread release on this hardware has me sticking it out. Can't wait
I haven't had any issues with my phone except battery life. Buy my battery life isn't as bad as yours. It used to be horrible but I got a new sim and that seemed to make it better.
Regarding the reboots, some apps are causing the phone to reboot. Either the apps aren't optimized for the phone or the other way around. I had one reboot and after I removed the offending app, never happened again.
Sent from my LG-P999 using XDA App
kangxi said:
I haven't had any issues with my phone except battery life. Buy my battery life isn't as bad as yours. It used to be horrible but I got a new sim and that seemed to make it better.
Regarding the reboots, some apps are causing the phone to reboot. Either the apps aren't optimized for the phone or the other way around. I had one reboot and after I removed the offending app, never happened again.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Actually, when I bought the phone I had them put a brand new SIM card as mine was getting to be a little long in the tooth - if getting a new one helps the situation I'd hate to see how it was with my old one :-D
Removing an offending app would prove to be a real problem for me though, as everything that I install has a legitimate work-related function.
im returning mine today for a newer batch one. its may 4 so i expect one that has the date of 4/24 and up as stated in other threads. mine reboots and freezes during random functions.
I ordered mine on the 20th so the day the phone was out in the store. I had to order mine online since i am a T-Mobile RSA. I have alittle screen bleed but not much. I will be doing exchanges until i get one with no bleed. Other wise i have had no problems at all. No reboots, lock ups, data problems, nothing the phone is rock solid. I love the phone. Every person that has come into my store with problems i have told them that T-Mobile is going to exchange this for you under the lifetime warranty if you have it for the life of you having the phone. So you have nothing to worry about. The phone is a great phone to have. Do the exchanges until you get a working one. I know i would do it until i did. Even if it meant doing it 100 times.
JWhipple said:
I've been through 2 G2x's , both have had the same problems...
Random reboots
Random freezes
Random shutdowns
Crazy inconsistencies in battery life
I've also gone the route of rooting and trying CyanogenMod with the same results.
With the battery issues, I did the following test 3 nights in a row.
Phone wiped, 100% battery charge, signed into Google and let the apps download, rebooted phone, data connection turned off (airplane mode), unplugged the phone and set in the exact same spot in the same room 3 nights in a row at 11PM.
Come 8AM when I woke here's the results:
Day 1: 30% battery remaining
Day 2: 80% battery remaining
Day 3: 0% remaining - battery was stone cold dead - wouldn't boot until I plugged in.
Phone was fine when I started typing this post, but just now while typing this message I reached over to check my phone for text messages (I keep the alerts volume all the way down while at work) and it's locked up again...
Guess I'll be returning the phone for a refund and borrowing an old flip phone for a month until the Sensation comes out.
Sorry LG - when it works, it works AWESOME, but I need something a bit more reliable considering that work needs to contact me on the phone and I am on call 24/7 !
Click to expand...
Click to collapse
A better test would have been to not install any apps. Then you could truly test your phone and not some rogue app, that you keep installing.
I'm about to do a complete wipe again and use a secondary Gmail account I have so to eliminate any apps from auto-installing and test throughout the day since I have my work PC handy.
or just skip the Gmail sign in process at first and add your Gmail account later from Settings. This will prevent it downloading your apps on first boot.
Also to the New Android User: Back closes apps, Home leaves them open. It isn't the OS's fault if you don't know how to use it.
To the OP: Have you rooted and flashed the Pre-Dexopt Patch from Paul?
http://forum.xda-developers.com/showthread.php?t=1051616
LG left the phone in Dev mode and doesn't dexopt the phone on initial bootup. This is why our phones boot so quickly. The downfall is after a few hours, it starts to lag out and lock up/reboot.
Sounds exactly like the problem you are having.
This patch is required for stock and EaglesBlood Roms excluding CM7. This should be fixed in the upcoming Gingerbread update. I also believe EaglesBlood and future roms will start coming with this patch included.
So do yourself a favor and patch it.
Basically, it's an awesome phone and many, if not all, of the issues should be resolved with software updates. Gingerbread is already in the works.
Sent from my LG-P999 using XDA App
player911 said:
or just skip the Gmail sign in process at first and add your Gmail account later from Settings. This will prevent it downloading your apps on first boot.
Also to the New Android User: Back closes apps, Home leaves them open. It isn't the OS's fault if you don't know how to use it.
To the OP: Have you rooted and flashed the Pre-Dexopt Patch from Paul?
http://forum.xda-developers.com/showthread.php?t=1051616
LG left the phone in Dev mode and doesn't dexopt the phone on initial bootup. This is why our phones boot so quickly. The downfall is after a few hours, it starts to lag out and lock up/reboot.
Sounds exactly like the problem you are having.
This patch is required for stock and EaglesBlood Roms excluding CM7. This should be fixed in the upcoming Gingerbread update. I also believe EaglesBlood and future roms will start coming with this patch included.
So do yourself a favor and patch it.
Click to expand...
Click to collapse
Yep, have tried without the patch initially and then with it.
I have signed in with the secondary Gmail account - only thing I imported from the original was my contacts, so, it's 100% stock with the exception of Paul's patch and recovery.
I'll be damned...
In an attempt to preemptively find out what I would need to return the accessories I ordered for the phone just in case I took the plunge and returned the phone, I was on hold with T-Mobile...
And while on hold, I grabbed my phone - and SURE ENOUGH - LOCKED UP HARD!
So, I guess this just made up my mind for me - I'll be returning this phone to point of purchase. Just need to use NAND to restore the stock backup , reflash stock recovery and unroot...
I am planing to return this phone too..
It seems the phone shut down completely for no reason, sometimes the screen doesn't wake up even tho phone is running in background.
So far i have tried to run completely stock with no apps installed no sync nothing and i was getting battery like 6-7 hrs.
I guess that was not acceptable for me.
I might have to wait till HTC Sensation comes out. What you think guys ?
Mine works fine, no problems at all, yes the screen bleeds a bit, but I can deal with that.
awesome phone, much better than my atrix
Sent from my LG-P999 using XDA Premium App
Slappy00 said:
Mine works fine, no problems at all, yes the screen bleeds a bit, but I can deal with that.
awesome phone, much better than my atrix
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
+1 Mine also works amazing... and a lotttt better than atrix....
ikm19 said:
I am planing to return this phone too..
It seems the phone shut down completely for no reason, sometimes the screen doesn't wake up even tho phone is running in background.
So far i have tried to run completely stock with no apps installed no sync nothing and i was getting battery like 6-7 hrs.
I guess that was not acceptable for me.
I might have to wait till HTC Sensation comes out. What you think guys ?
Click to expand...
Click to collapse
That's where my money is going...
my understanding is the sensation is locked down that's why cyan isn't going to get it. Which also means no dev support.
The MyTouch 4G and G2 were locked down too... Unless they are going to lock the bootloader?
ikm19 said:
I might have to wait till HTC Sensation comes out. What you think guys ?
Click to expand...
Click to collapse
HTC announced an update to the Sensation in Q3 that will include a NFC chip to match the features of the SGS2. I'm also guessing they'll increase the amount of RAM in the phone to make it more competitive. If the 2.3.3 update makes the G2X stable I may keep it until later in the year. If the Sensation comes out before they update the G2X I'll get Sensation. I need a phone that's consistently dependable and in that regard the G2X is a mess. I can't do custom ROMs because I travel globally and everyone I've ever used has always given me problems registering on foreign networks so CM7 is no silver bullet for me. It's a shame too because the G2X hardware (bleeding screen excepted) is pretty slick and it's really fast when the planets line up and everything works. Sigh.

[q] major bugs in samsung droid charge

Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
I haven't experienced any of the problems you bring up.
Sent from my Gummy Charged GBE 2.0 using xda premium
1. Are you sure that you are not pressing the power button while in the camera application. Doing so will toggle the screen lock and appear to freeze the phone.
Sent from my SCH-I510 using Tapatalk
I haven't experienced any of those issues either.
As for number 4, I think that was a conscious design decision. I don't really like it either, but you can use Tasker or Locale to detect when you're in a call and change your timeout to whatever you want.
nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
Click to expand...
Click to collapse
Have not experienced on my stock Charge nor on my rooted Charge. Just tried both to try to get this to happen.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
Click to expand...
Click to collapse
Never had this issue on either phone.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
Click to expand...
Click to collapse
When you have the auto brightness turned off you can push and hold the notification bar and slide your finger to the right or left to raise/lower brightness. Is it possible you are doing this?
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
Click to expand...
Click to collapse
The phone isn't supposed to be waken by shaking it. You can change the time-out timing through the settings. I've never hung up the phone via the power button so I can't even comment on that one.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
Out of curiosity, are you on EE04?
I have not experienced any of these on the 3 months with my phone. It locked up maybe once on the camera but never more than that.
I've had none of these issues and furthermore I second the above thoughts regarding locking three camera and the status bar brightness.
Sent from my SCH-I510 using xda premium
Count me in the camp that says I havent seen any of those issues. As far as the camera goes, the only issue is the substandard SD card that Sammy sends. You cannot record in HD because the card speed is too slow.
All the other issues you are seeing are unique.
Search these forums for them, if others have had the problem you will find someone asked about it.
If you do find them, I am sure that they will be very isolated.
I couldn't say about a totally stock phone as I flashed mine to gummy 1.9.1 on its very first boot, but I have never had a single problem with my phone.
I absolutely LOVE this thing, I have owned a TON of phones and IMHO this is hands down the best phone I've ever owned.
My boss bought a new Bionic last Friday and after playing with it for the day Friday I wouldn't swap my phone even for the Bionic (among other things, the screen SUCKS on the Bionic). My boss doesn't like it either, he is returning it tomorrow.
~John
Never experienced number 1,2 or 4. But I have experienced number 3. Only happens though every couple of weeks. Hardly ever basically. It is weird though. I have no idea why my brightness changes even with my auto brightness off. Still a great phone though.
Sent from my GummyCHARGED Charge using Tapatalk
kelmar13 said:
Have not experienced on my stock Charge nor on my rooted Charge. Just tried both to try to get this to happen.
Never had this issue on either phone.
When you have the auto brightness turned off you can push and hold the notification bar and slide your finger to the right or left to raise/lower brightness. Is it possible you are doing this?
The phone isn't supposed to be waken by shaking it. You can change the time-out timing through the settings. I've never hung up the phone via the power button so I can't even comment on that one.
Out of curiosity, are you on EE04?
Click to expand...
Click to collapse
Omg just read your post about the auto brightness. Never knew that. Thanks!
Sent from my GummyCHARGED Charge using Tapatalk
piizzadude said:
As far as the camera goes, the only issue is the substandard SD card that Sammy sends. You cannot record in HD because the card speed is too slow.
.
Click to expand...
Click to collapse
Mine must have come with a different card as I have had no problem recording in HD (I just tried it again to make sure)
ms0chez said:
Omg just read your post about the auto brightness. Never knew that. Thanks!
Sent from my GummyCHARGED Charge using Tapatalk
Click to expand...
Click to collapse
Lol, anytime!
It's a feature I don't think I could live without now.
I can honestly agree with ur first concern. My camera is wonky. I can take pics all day without flash enabled. But I turn on the flash and try to focus (tap to focus), and as soon as the pic is snapped, the screen goes black, causing me to do a battery pull. Happened to me on my former Charge, my current replacement Charge and my wife's Charge. Happened on stock unrooted, stock rooted, and with custom Roms on all firmware versions. And I can easily replicate it.
Sent from my SCH-I510 using XDA Premium App
Please use the Q&A Forum for questions Thanks
Moving to Q&A
nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.
jpolzner said:
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.
Click to expand...
Click to collapse
I think the fact that he is a journalist with some very pointed questions is the dead giveaway for his agenda. He's looking for a sensationalist angle to play for an article. Whether it's against Verizon or Samsung, I don't know, but it's pretty certain he came here with an agenda.
jpolzner said:
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.
Click to expand...
Click to collapse
Well put, I agree 100%
~John
never experienced those issues either..probably a android issue..
Sent from my Gummy Charged GBE 2.0 using XDA App
I've had my Charge for about three months. I ran bone stock EE4 for a few weeks and have been using the various iterations of Humble Roms ever since. I never encountered any of the 4 issues brought up by the OP.
As for HD recording, I recall posts mentioning that some phones shipped with class 2 and some with class 4 sd cards. I got a class 4 card in mine and I've never had an issue with recording HD. Likely the source of the recording issue.

Categories

Resources