I am on Sprint and an running the latest update plus root. I have noticed that my S3 occasionally looks up while asleep and will not want up. It will not even reboot itself on its own. My power button is totally unresponsive.
I have no other problems with my phone at all.
Should I try to return the phone or should I just wait for a big fix?
EDIT: it looks like it happened again in two hours.
Related
so heres the story:
when i lock the phone, the screen turns off as normal. but when i hit the power/home button to wake it and unlock it, nothing happens. literally, nothing happens. its as if the phone has turned itself off.
So whats happened is, I left the phone on the charger last night. it woke perfectly this morning when the alarm went off. no issues there.
I put the phone into my pocket and headed into work. i went to check my phone when i got on the bus and this was the first tme that I noticed that the phone wasnt waking. i eventually pulled the battery to get the phone to restart. i tried it again and the same thing happened.
later I made a phone call. the same thing happened again when i took the phone away from my head (the screen didnt restart, and I couldnt hit the End Call button cause there was none.)
since then, i've figured that to make sure the phone doesnt go to permanent sleep i have to do one of 2 things,
1) keep the phone music player running constantly, or
2) keep the phone connected to the usb charger.
clearly this isnt exactly practical for a mobile.
im not running any other Rom, its still the stock rom, android v 2.3.5, not rooted or anything else?
is this somethign anyone else has seen?
its called 'sleep of death' or SoD. some people has experienced this and some are able to fix it. it depends on what is causing it.
some blame it to the battery and the battery's contact point..
sometimes it fix itself after few reboots..
cheers for the info. Ill look into it and see if its worth trying to fix or just sending back.
no problem, i have this problem and cant do anything about it. i used load monitor to keep the phone awake, u/v a bit so it wont drain so much battery. but battery drainage still noticeable like 1% every 5 min..
just wondering, does it feels hot/warm near the camera lens when it happens? bcause mine does.
not particularly.
i finally got through to my provider and will be able to get it fixed/replaced soon. they just dont half drag their feet
A couple weeks ago, I finally figured out that Cyanogenmod wasn't auto-updating past CM 10.2 on my Evo 4G LTE because I needed to update TWRP to 2.7.1.2 and also get S-OFF and update HBOOT to version 2.10.0000. Although I had a couple stressful moments in updating all of that where I thought I might have accidentally bricked my phone (I'm still pretty new at flashing custom ROMs), I managed to get it all figured out and I updated Cyanogenmod to CM11. I can't remember whether I updated directly to Snapshot M11 or if I updated first to M10 and then M11, but at any rate everything worked out fine and I had no problems with my phone. Then I updated to snapshot M12 through the auto-updater when it came out a week or so after doing all the above, and again everything was working fine with no problems (though I did start having some lag sometimes when I was using the Kii keyboard app I had installed, or sometimes the keyboard would drop my swipe halfway through a word and type two words instead of the one that I wanted, which was happening at an increasing frequency in the days before my phone crashed). At any rate, a few days ago I was reading the news on a news app, then the screen froze, the operating system crashed (the screen just went black and the phone turned off), and ever since then I haven't been able to use the phone at all. It doesn't turn on now.
I have tried booting into recovery a number of times using the power + down volume combo, but I haven't been able to get it to work -- though I'm not sure if there's some trick that I don't know about how long to press down. The phone does not boot up into Cyanogenmod, either. The screen just stays black no matter what I do. Sometimes when I mess around with pressing the power button or holding it for different periods of time and/or pressing and holding the down volume, the phone has made some responses. Sometimes the capacitative buttons will light up for a couple seconds before going black again, and sometimes the phone will vibrate for a half second. (Also, when I have it plugged in, sometimes I can get the battery charging light to turn off or on.) But after that, the screen always just stays black. It seems like I bricked my phone, but I wanted to ask before throwing in the towel. The thing is, sometimes when I was flashing new ROMs, my phone would get into a similar state (I was never quite sure what was going on) and I'd be able to get it into recovery or get it to boot regularly (though I was never quite sure what exactly I did to make it work again -- I always kept trying different combinations and pressing-lengths of the power and volume down buttons like I've been doing recently), so it seems like maybe there's still a possibility I could do something similar now.
Any idea what I should try? Any idea what might have happened to lead to a crash like this, so that I can avoid making the same mistakes or having the same problems in the future? I would appreciate your help so much; I'm overseas right now and was depending on having my phone to stay in touch with people. Thank you!
Hey guys,
have u ever heard of my problem? Please help if you did!
First of all, I think one of my batteries is broken, cause it's lasting ways to short.
If my battery goes down to 15, display starts flickering but I dont care.
Now I realized another, hard issue!
If my phone got to nearly 5% it's powered off and reboots. But it dont just reboots, it seems it is off for 30 seconds, then it reboots. Btw, without "powering down", just off. Screen off, no sound, sometimes LED glowing blue.
After that reboot i realized all of my Apps are gone, including GAPPS!! Just one of my games is still there. I didnt do any wipe!
My phone is back on non-rooted stock Android 4.3 UGNG3 DBT version.
I do not understand how this loss works!?
best regards
sp3d00
So about 3 weeks ago, I dropped my HTC so now I have a large crack running down the middle of the screen. However I haven't had any other problems up until last night. The ringtone volume turns itself up without me even touching the phone every now and then and once it does that, the power button stops working. But it does work again once the screen is switched off, meaning I can turn in on but not off. The power button functions fine until the volume button acts up the first time after restart.
I factory reset my phone thinking it may have had something to do with the software but the problem came back within the hour when all the updates started rolling in. Once it did, i booted it into safemode and the problem seemed to stop but I don't know what's causing it. Could it be an actual bug in an update or is the damage to the screen simply too much for the phone itself? Has anyone ever dealt with a problem like this? Any help will be appreciated as I know it's expensive to fix these things and I don't want to go to the shop to get it fixed only for the problem to come back as it's software related.
Hi,
Just few minutes ago my brand new phone just broke on me. I was holding it in my hand, locked screen, like minute later I tried to unlock it to no avail, screen just stayed black. There was a sound when I touched it by the fingerprint sensor, but no light up from behind the screen. I tried holding down power, then power+volume up, phone only vibrated, no reaction on the screen. I've connected it to the charger, and now it seems to be in bootloop - screen is turned off, and every few seconds phone vibrates. I've managed to somehow turn it back on once, phone booted to system, everytthing worked just fine, then I locked screen and it just stayed black, now I can't reproduce that, can't even turn it off, it's just vibrating every so often. Did it really brick in my hand? Software of Hardware? Everything worked just fine, maybe battery was draining a little bit too much for my taste, (15-20%/hour with screen on+lte/wifi) but 120Hz refresh rate+bright setting and AOD turned on 9am-9pm could do that. Do you guys have any suggestions, or I'm expecting trip to the service?
Sorry, but i cannot guess any reason. I am stumped as this bootlooping shouldn't beb happening... Very strange. May be its better to show it to service center guys.
Btw, i had tried this on my previous android phone to shut it down, like a hard shutdown. I had pressed power + volume down + volume up keys together to shut it down completely. Basically by pressing all the 3 keys. If you want to try, you can try it. I have not tried it on my GT, but had used it on Oneplue 2 and Honor View 10.
Hope your issue gets resolved asap...
Okay, I've contacted support via livechat, they told me it's definetly just software glitch, and to resolve this I have to wipe dialer cache (?) and all system settings - I did it, everything worked just fine, but today, again, same thing happened. First time phone just died in my hand, second time it was while listening to music via Pulsar, today I was just sharing wifi as a hotspot, phone randomly broke connection and would not unlock, but still I could tell it was on, because of vibrations and sounds. Not a software glitch after all? If I manage to unlock it I'll just recover it to factory settings, we'll see if that helps, but I don't like the sound of that.
What apps are -you- installing?
Launchers and power management apps are prime suspects...
Otherwise, mobo failure. It may be firmware but how far do you want to take it?
It should run fine out of the box.
Last time I played with launchers was with good old SGS about 5 years ago, only app out of ordinary was AccuBattery to check that SoT drain, but could it make such a damage without root privilages?
d4m4in said:
Last time I played with launchers was with good old SGS about 5 years ago, only app out of ordinary was AccuBattery to check that SoT drain, but could it make such a damage without root privilages?
Click to expand...
Click to collapse
Accubattery isn't the culprit...