Related
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
Has anyone had their screen stop timing out? I've had my phone for 11 months, noticed this problem periodically but now my screen won't time out at all. My phone has been rooted for 6 months, never any big problem with the screen. About 3 weeks ago it stopped timing out completely. I have adjusted the settings from 2-1-.5 minutes, and it would work for the first while then it stops. I haven't installed anything on my phone that I can say triggered this. Resetting and taking the battery has no effect. I believe I have froyo on here.
Thanks for your help
this is on my incredible
Bad day today. This morning started out with a very difficult time getting the screen to work. Everything took 2-3 touches. Some things I had to give up on. This lasted all day. A short while ago I was reading some pages and it got so bad I just pulled out my tablet. 10 minutes latter I grabbed the phone and it would not activate...just a black screen. Battery pull required. I recalled reading about black screens of death.
Is this part of a normal pattern of quality decline I'm seeing? Ill keep an eye on it for a few days, I have a 30 day remorse period.
Thoughts, suggestions, words of wisdom? Just don't say root..won't root in the remorse period.
alodar1 said:
Bad day today. This morning started out with a very difficult time getting the screen to work. Everything took 2-3 touches. Some things I had to give up on. This lasted all day. A short while ago I was reading some pages and it got so bad I just pulled out my tablet. 10 minutes latter I grabbed the phone and it would not activate...just a black screen. Battery pull required. I recalled reading about black screens of death.
Is this part of a normal pattern of quality decline I'm seeing? Ill keep an eye on it for a few days, I have a 30 day remorse period.
Thoughts, suggestions, words of wisdom? Just don't say root..won't root in the remorse period.
Click to expand...
Click to collapse
Ummm.....
Rom?
Kernel?
Uv?
Profiles?
Oops didnt finish reading post. Root!
G2X
Sotty to say this mine does this.
Are you using auto brightness?
That's when my phone acts funny and don't want to wake up.
Sent from my LG-P999 using XDA Premium App
KRAZYADROIDMASTER said:
Sotty to say this mine does this.
Are you using auto brightness?
That's when my phone acts funny and don't want to wake up.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Everything is stock out of the box. If auto bright is selected by default then yes.
What timing for this to occur. My sensation just arrived in Seattle for delivery tomorrow. Was hoping for an honest comparison.
when i first bought the phone, the screen felt insensitive too, also 2-3 touch, especially that "touch android" in the beginning to set it up. It was ridiculous for first impression
But hey, i rooted it and flashed it with a rom & kernel so everythings all good
If it helps the first g2x I got 420 I didn't root and it wouldn't turn of after a week .. rooted replacement with faux and now its been good
Sent from my LG-P999 using XDA App
Sounds like after awhile the phone starts to misbehave on stock everything. I have seen other ppl complain having same issues while on stock.
I had a my phone getting hot and it rebooted after that and then apn would not stick. I'm glad I had apn backed up so it wasn't much of a problem.
Sent from my LG-P999 using XDA App
Well my sensation arrived this morning at 1113. Its now 137 and its still not running. Apparently are still downloading. On the G2x, same apparently 20 minutes tops.
First thoughts after that, sensation is only a few fractions wider. Side by side no wifi, g2x pulls 2 bars 4g. Sensation 2bars 2g.
Screen comparison ...toss up..both look good...better? ?? They are different...
Scrolling is different. G2x is smooth uni page, a continuous page action. Sensation is page by page.
So far I'm leaning strongly towards g2x...except for that touch screen worry. That plays very heavy here. With no fix in sight, g2x would go back. But I've got 30 days
Sent from my LG-P999 using XDA Premium App
Just perform a factory reset or reflash your rom and kernel to fix the black screen issue. Mine started doing it and that fixed it. Everytime I tried to unlock the screen it went black but was still on technically cuz I could unlock and open apps. I had to hit the unlock button and have mg finger on the screen already to keep it from going off, then I could unlock it.
JHaste said:
Just perform a factory reset or reflash your rom and kernel to fix the black screen issue. Mine started doing it and that fixed it. Everytime I tried to unlock the screen it went black but was still on technically cuz I could unlock and open apps. I had to hit the unlock button and have mg finger on the screen already to keep it from going off, then I could unlock it.
Click to expand...
Click to collapse
hes all stock but yea he could do a factory reset of stock rom i dont really see it doing anything unless there is a corrupt app and the way to fix that is factory reset then when it says restore backup data you uncheck it, this way it doesnt restore anything or any app that was corrupt and then start fresh one app at a time, and keep it on for a few days then if its good add another app. thats the real way to find out, it is tedious and time consuming but it u will find out what it is. but... after the remorse period he could add throw on another rom and kernel that solved my issue with sleep of death issues on stock
With stock there is a bug where it is always in engineering mode or something like that. There is a patch available in the development section, but don't remember if root is needed to apply it. How long since you last shut the phone off? If I remember right, that bug would cause everything to slow down really bad after a couple days. Try rebooting once a day and see if this issue comes back. If that works, you may be able to get by until you are willing to root.
jsapp said:
With stock there is a bug where it is always in engineering mode or something like that. There is a patch available in the development section, but don't remember if root is needed to apply it. How long since you last shut the phone off? If I remember right, that bug would cause everything to slow down really bad after a couple days. Try rebooting once a day and see if this issue comes back. If that works, you may be able to get by until you are willing to root.
Click to expand...
Click to collapse
Yes root is required because it requires ClockWorkMod to flash it.
This is why the phone boots up so quick out of the box because it doesn't preload anything but this causes it to become overloaded and run out of memory after some use and locks up.
The LG O2x had the same issues.
Stock REQUIRES the patch to function properly. Or just flash CM7 and enjoy the wealth of great features.
player911 said:
Yes root is required because it requires ClockWorkMod to flash it.
This is why the phone boots up so quick out of the box because it doesn't preload anything but this causes it to become overloaded and run out of memory after some use and locks up.
The LG O2x had the same issues.
Stock REQUIRES the patch to function properly. Or just flash CM7 and enjoy the wealth of great features.
Click to expand...
Click to collapse
My thinking...and pardon the train of thought....if something out of the box is broke...like this....then...rooting it still leaves me with a device that had to be fixed...by me. I had 10 days of no issues with the G2x. I ordered and received the Sensation only because my son has one...and its nice. I have 30 days to try them out. I wanted to test them side by side....for basic comparison, the way I use a phone. Once I decide which one to keep, then root will most likely follow. But rooting to be able to compare side by side....misses the point of the comparison.
3 hrs after starting the setup on the Sensation...the battery is charged and everything is setup to test. One of the first, less obvious things I noticed on the Sensation is the multi tasking....running things like restore and browsing at the same time...is way slower than the G2x. It took 90 minutes to download the apps from backup....on the Sensation....the G2x is maybe 20 minutes. That couldn't be right and I tried it again. Still a long time. Finally I tried it again..and just let the phone sit...didn't do anything else....it downloaded just like the G2x.
When considering which phone, do I think about that slowness...in comparison to say....the Touch problems, Black screen problems....and reported rebooting....sure...thats why I'm testing them side by side.
alodar1 said:
My thinking...and pardon the train of thought....if something out of the box is broke...like this....then...rooting it still leaves me with a device that had to be fixed...by me. I had 10 days of no issues with the G2x. I ordered and received the Sensation only because my son has one...and its nice. I have 30 days to try them out. I wanted to test them side by side....for basic comparison, the way I use a phone. Once I decide which one to keep, then root will most likely follow. But rooting to be able to compare side by side....misses the point of the comparison.
3 hrs after starting the setup on the Sensation...the battery is charged and everything is setup to test. One of the first, less obvious things I noticed on the Sensation is the multi tasking....running things like restore and browsing at the same time...is way slower than the G2x. It took 90 minutes to download the apps from backup....on the Sensation....the G2x is maybe 20 minutes. That couldn't be right and I tried it again. Still a long time. Finally I tried it again..and just let the phone sit...didn't do anything else....it downloaded just like the G2x.
When considering which phone, do I think about that slowness...in comparison to say....the Touch problems, Black screen problems....and reported rebooting....sure...thats why I'm testing them side by side.
Click to expand...
Click to collapse
And, as I'm sitting here....the G2x just did its first reboot. this kind of tells me...well... lets wait a week....and see.
Do all the nexus s 4g's have the back button issue? or just some? should i exchange?
Issue is that the back button becomes unresponsive periodically for about 15 seconds. Workaround is to wait or turn off the screen and then turn it back on.
It happens a few times every day.
My back button works just fine.
No problems here. Don't even really know what the back button issue is...
What is the issue you have? Doesn't work?
Sent from my Nexus S 4G using XDA Premium App
Back button becomes unresponsive periodically for about 15 seconds. Workaround is to wait or turn off the screen and then turn it back on.
Mine is fine.
Sent from my Nexus S 4G using Tapatalk
I've never heard of that.
If it's such a bother, you might as well just exchange it.
I had the same exact problem with the menu button. I found out about it two days into owning it, returned it for a new one and haven't had the problem since.
Sent from my Nexus S 4G using XDA App
Mine had the back button issue. it's currently at Samsung for repair. Turnaround time is about 10 days for repairs. If you bought it recently, I'd recommend exchanging it. The problem will not go away and cannot be fixed with a software update. My wife has the Nexus 4g as well and she's never had the issue. Mine would freeze 5 or more times a day. Talk about frustrating. It is a very common problem which has been posted on over 500 times at google's forum and it effects the home button more commonly.
Strangely, Samsung says they never heard of the problem, Yeah right. But it's definitely a crappy hardware issue.
A friend of mine just got a Nexus S and has the same issue. He's been asking me if that's normal. I know my Epic doesn't do that. I assumed maybe it was a software issue but now that I've seen several other people have returned theirs, I'll suggest he do the same.
I believe it to be a bug in Samsung touch panel driver. But we can't know for sure because they don't release the source code.
Mine does it on back and home buttons. Some do it on search button which is even worse. Basically this bug causes a tap on a button to register as a long press for about ten seconds. Turning screen off and on makes it stop. Otherwise the button stays dark and you see long press behavior (if there is any for your current context) for about ten seconds. Very annoying.
Sent from my Nexus S using XDA App
My first two did the same thing.
Sent from my Nexus S 4G
My device Nexus 5 16 gb with android 4.4.2kitkat all stock.The problem is that the phone itself is locked in any application such as now when I write a message has to press several times to unlock. Please do a full reset. And it worked fine but when put a couple of programs namely program premium widgets then the phone started again blocked.Than you in advance!
Easy96 said:
My device Nexus 5 16 gb with android 4.4.2kitkat all stock.The problem is that the phone itself is locked in any application such as now when I write a message has to press several times to unlock. Please do a full reset. And it worked fine but when put a couple of programs namely program premium widgets then the phone started again blocked.Than you in advance!
Click to expand...
Click to collapse
You could try disabling lock screen for a while in settings/security.
Are you using a case that covers/touches the power button?
GUGUITOMTG4 said:
I could try disabling lock screen for a while in settings/security.
Are you using a case that covers/touches the power button?
Click to expand...
Click to collapse
tried
Easy96 said:
tried?
Click to expand...
Click to collapse
Lol I meant You should disable screen lock. So, if it happens again, it might be due to a weird app causing it.
Also, if screen randomly turns off by it self after disabling screen lock, then the problem cold be around the power button.
That's why I asked if you are using a case.
Hi,
I'm having a similar problem from the past week on my nexus 5. it's getting worse as more days go by.
I'm not using any case for the phone. I have tried factory resetting the phone which has not helped.
the phone keeps locking and timing out every 10 seconds or so. I have disabled the lock screen too, but it makes no difference.
I've uploaded a small video of this happening on Youtube. It is actually much worse than seen in the video.
I cannot post the link as I'm a new user.the video is titled "Nexus 5 lock screen loop". It's a 30 second video.
Hope you guys have a solution. Thanks in advance.
Same issue here on now two of my nexuss. You'll either notice the top right portion of the screen is raised up ever so slightly or the battery is warm to the touch. With both I could press the screen back in and it would move or have a little crackle. Seems the power button is effected by this, it's a design fault apparently. Wonder how many times I'll get it and how may times they'll replace my device.