I've had recurring SoD issues with my 12.2" Tab Pro for a while now and have recently narrowed it down to the case. If I remove the tablet from the case and sleep/wake it using the buttons it works every time. In the case when it is woken by opening the case if it has been asleep for more than 5-10 minutes there's a high likelihood it will fail to wake and have to be hard restarted by holding the power button for 10-15 seconds. When the issue occurs the capacitive buttons light up but nothing shows up on the screen.
Is this a hardware issue or is it firmware/software/setting? The issue has followed me through a few versions of CM12 although seems to have gotten worse recently. I can't remember the issue on CM11 or stock but it may simply have not presented yet.
Thanks for your post, it helped me get my Tab Pro 8.4 powered on again. I picked it up yesterday and it was off, and I knew it had enough juice...go to power it on, nothing. I try all manner of start combinations, to no avail. The only thing that worked was removing it from my case (with magnetic front), held power for a bit, and voila, extreme relief. I've been running a CM11 nightly on it for several months (no other major tweaks like a different kernel, OCing, etc.) and it's been flawless. A few days before the the Sleep Of Death happened, however, I rebooted and it came back up with a completely different home screen...WTF. I power it down/up and then it was back to normal, heh. Not sure what the cause of all this is.
I just had a sleep of death on my GTab Pro 8.4 (SM-T320). I just held the power button down for 30 seconds, and it rebooted.
The odd thing was that when it completed booting, it thought the date was August 14. It has now corrected itself after wifi connected.
It happened to me once... But I held power button and it restarted normally, with all dates correctly,etc. And it never happened since.
Related
I did not have that problem for a long time, it only recently happened. In the morning the device 'froze' for the first time and did not react to any input without the screen turning on.
I took out the battery to restart and everything seemed fine. But later on it happened while I was using the device, certain pixels moved out of place (like a green pixel distortion) and the device froze. Screen turned off soon after. Taking out the battery was the only option.
Now, this is either battery or some other hardware flaw. After restart the battery had been hit with a 20% drop.
Might the device act up by some charging problems? When I am charging the device, I can feel the electric 'buzz' from the docking connectors (the three golden circles).
Also, when it is not charging, I cannot detect it myself, but if I take a strand of hair, the end of it 'sticks' lightly to the screen (and to the docking connector) if I put it close there. I fear like there's some manufacturing flaw there that broke loose.
The device has not dropped once, nor has had any other physical damage happen to it.
Has anyone else had the same symptoms happen?
Sounds like you've hit the same (or similar) issue to others (including me)
Sleep of Death
http://forum.xda-developers.com/showthread.php?t=1360880
I found this issue (or one very much like it) at code.google.com here:
http://code.google.com/p/android/issues/detail?id=22748
jss42 said:
Sounds like you've hit the same (or similar) issue to others (including me)
Sleep of Death
http://forum.xda-developers.com/showthread.php?t=1360880
Click to expand...
Click to collapse
Thank you. I thought it was different from Sleep of Death since the initial symptoms were different from weeks ago when I read that thread, but now reading it this seems correct. This thread can be merged or removed, I'll post in the other thread. Thanks again!
I've had that too, couple days ago using Facebook everything just froze. The keyboard went all buggy and green pixels everywhere. The back of the phone started to warm up phone wouldn't respond in any way.
Tried everything I could try, only option was to pull the battery, once that happened phone wouldn't turn back on!
I gave the phone 5 mins to rest before putting battery back in then it turned on.
My heart was pounding I thought my phone had died!
Thankfully it hasn't happened since
Sent from my Galaxy Nexus using xda premium
It's happened to me multiple times. Less since I turned off the EQ in the Music app, but it's still happening.
Once it happened with the device just sitting there with Tapatalk displaying a list of posts. I wasn't even interacting with it.
I think it's a OS or driver problem and will be fixed in an OTA.
happened to me once, although when it happened I was already pretty low on battery, about 20% left, maybe less.
I was in a settings menu for some app, I can't remember which. But I had the keyboard up, and the green pixels hit, froze, unfroze, green pixels again, froze, and then shut off.
it would not turn on via the power button, so I quickly pulled the batt and put it back after 30 secs or so and powered it up. Batt did not drop any lower than it was, and it worked fine. Plugged it in, recharged overnight, and has been fine ever since.
I'm running 4.0.1 and I don't have anything but apps made by Google on the phone at the moment.
never rooted or unlocked bootloader.
Hopefully 4.0.2 or 4.0.3 fixes this
i realize now that there's no support for 720P AC3 .MKV files on the Nexus yet, but every time i tried the phone would lock up and i'd have to do a battery pull. other then that, i notice if i have Google Music running and attempt to do something else(multi-task) the phone will also lock up.. but then it will reboot on it's own. i also get lag regularly switching views/menus or going from portait/landscape. additionally, the browser(regardless of which one i use) will occasionally just freeze & close by itself.. usually if i try to do a secure login on a site. i will also sometimes get FC's(have seen them for launcher pro & android keyboard)
About three weeks ago my launch Epic 4G Touch got its power button stuck on. In the weeks prior I had had occasional glitches where pressing the power button would turn on the flashlight (an AOKP feature where if you hold the power button from off, it turns on the light), or when pressing it to put it in sleep I'd get the power-off menu. And occasionally it would get worse, where pressing the power button would lead to the entire phone shutting off and restarting after a few seconds, as though I had held the power button down the whole time. Anyway, as I said, it finally reached the point where the button was apparently stuck sending the On signal the entire time. And it was clearly hardware-level, as if I'd pull the battery and put it back in it would INSTANTLY power itself back on.
I took it to the Sprint store, they reviewed it, couldn't fix it, and ordered me a replacement which arrived a few days later. I've had that replacement for about two weeks now without any hardware problems. I did switch to AOKP again, but I've had no issues whatsoever.
Until today, when it progressed through all the above-mentioned symptoms and all the way to stuck ON permanently, in the span of a few hours.
Has anyone else experienced this? Is there any logical reason to suspect this could be a fault of the sofware I've installed? I've never heard this symptom before, which makes me think it's extremely unlikely or others would have caused it, plus the power-on from battery implies to me this can't possibly be a software issue. But I want to be sure before I get it replaced yet AGAIN and cause it again, or have the store try to blame my custom ROM (they never said a word last time).
Help?
EDIT: Pretty confident I just confirmed it's a hardware problem. I booted into CWM to try to make a backup so I could flash to stock and confirm it wasn't software. The power button of course didn't work in CWM either. What I hadn't thought of is that I couldn't get back OUT of CWM without the power button. Even a battery pull would put me right back into it. I finally get desperate and yanked the battery and banged the phone on the desk against its power button a few times, then put the battery back in and the phone didn't power itself back on. I then hit the power button, booted to CWM, and managed to use the power button to reboot to system. So that confirms it's hardware to me. So I guess the question shifts to: two phones in a row with this problem, and I've never seen it mentioned before. Am I just incredibly unlucky, or have others experienced this? Second: anyone successfully manage to use a scenario like this to talk them into a different phone? I'm not loving this chain of events, and I'm not loving to hack my phone to get a good stock experience. I'd really love to switch to a Galaxy Nexus. Any tips?
I have the same problem just got it today....Really need to fix this
Sent from my SPH-D710 using xda app-developers app
Seen a couple different threads about power button. Someone took it in to be repaired/replaced only to have it go bad again later. I guess I have gotten lucky, there was a good while that my power button liked to stick and not function properly. It went away one time after I accidentally left my phone in a hot car. I suppose my issue could have been from something sticky being spilled on the phone though.
Sent from my SPH-D710 using XDA
Recently my Captivate glide has been having many issues. Originally it started when my phone would just randomly turn off for no reason, I attributed this to overheating and figured maybe it was a normal thing. Eventually it got to the point where the battery would hold no charge and I could not power on the phone. I replaced the battery after noticing that it was swollen and this seemingly fixed the issue. Though after a week or so I noticed there were still a few problems with it in regards to it going off randomly and coming back on but nothing major. Last week though I was at the gym and it dropped from my pocket I picked it up, put it back on but a few seconds later it turned off again. I just figured it needed to charge. I tried later to turn it back on that's when I noticed that the phone would keep randomly going on and off constantly and the lock button no longer worked when it was on so the only way to unlock it was to slide it out. I figured it was just a matter of replacing the button but it got worst and now the phone wont stay on, It comes on for a second, boots up then turns off, the battery has 0% at all times and even if it's on the charger and shows the charging icon, it won't stay on. For the few minutes that it is on for, the lock function spasms and the phone keeps locking and unlocking itself, eventually showing the lock button menu then finally going off and coming back on. I gave the phone to my friend to check out as he fixes a lot of phone, he took it apart but there was no damage to the button or anything holding it down that would cause the problem, he used a tester to test it and found that it was working fine. He thinks it might just be a software issue and suggested I reinstall the OS. Does anyone have any insight as to what might be the problem and a solution?
TL;DR Lock button on phone acts as if it's constantly being pressed and won't remain on for longer than a few minutes and even when it is on, just keeps locking and unlocking itself before shutting off.
While playing Lionheart Tactics on my TabPRO (while connected to the charger) it suddenly turned off, and won't be powered back on using the power button. It's not an issue of flat battery, as the battery was on close-to-100%.
I was wondering why this happened and what I may do to fix it. Please help.
Hold down on the pwr button .....keep holding it down
amityg said:
Hold down on the pwr button .....keep holding it down
Click to expand...
Click to collapse
Thanks a lot. That did the trick.
Why does this happen?
Sent from my beastly SM-T320
Not sure as to why. It has only happen once with mine. I had to hold the pwr button down for almost 30 sec.
@amityg how do you came up with that way of fixing it?
Sent from my beastly SM-T320
Had to try something...as it would not turn on. It work for me and when I saw the post that someone's else had the same problem , had to share!
amityg said:
Had to try something...as it would not turn on. It work for me and when I saw the post that someone's else had the same problem , had to share!
Click to expand...
Click to collapse
Thanks a bunch. This worked for me. Is this a recurring issue with many users, or am I just one of the lucky few?
turned off
loosefalcon said:
Thanks a bunch. This worked for me. Is this a recurring issue with many users, or am I just one of the lucky few?
Click to expand...
Click to collapse
i just had the same problem . It went off last night and wouldn't turn back on . i was reading here that he had to hold down the power for almost 30 seconds.it also worked for me thanks.
For me worked as well . At first actually recovery boot worked as well, but after a point not anymore. Thanks for the posts.
The still existing problem is that, the tablet (running on M12) turns off spontaneously couple of minutes after it switched to sleep mode (with display forced on, it does not happen).
Any similar issues?
I doubt the tablet is "powering off" its more like it's freezing up perhaps a hardware issue or overheating ...etc, holding the power button for 20 sec causes the tablet to force shutdown (like hitting breaker switch on a powerstip or holding down the power button on a computer), where if the tablet was already shutdown you would only need to hold it for 5 sec.
Anyways if its just a software freeze and not a hardlock you might be able to catch the problem in logcat or dmesg if you have adb access and root (since you mentioned CyanogenMod you probably do) , just monitor the logs as you are using the device and when it happens look at the messages for an explanation.
power off
sometimes I have to hold down the recovery buttons for 45 seconds for it to turn back on
To clarify something here, the tab pro's were made in february as premium line and in a couple of months later were the Tab S tablets been released.
That means that all the pro tablets has been reduced in price really fast.
Many people bought this tablets while thinking that they had premium tablets.
This tablets are unfortunately having multiple annoying and mostly unique issues.
I haven't experienced any of those issues on any other devices.
Issues like:
- Problems with slow recovery
- Annoying noise when doing high end tasks.
- Problems with official fully working cm releases.
- Several random issues.
I think i know why there has been released a new ( Tab S ) tablet serie so fast.
Maybe it was even based on economic tactics
Sent from my i9100 running gingerbread.
otyg said:
I doubt the tablet is "powering off" its more like it's freezing up perhaps a hardware issue or overheating ...etc, holding the power button for 20 sec causes the tablet to force shutdown (like hitting breaker switch on a powerstip or holding down the power button on a computer), where if the tablet was already shutdown you would only need to hold it for 5 sec.
Anyways if its just a software freeze and not a hardlock you might be able to catch the problem in logcat or dmesg if you have adb access and root (since you mentioned CyanogenMod you probably do) , just monitor the logs as you are using the device and when it happens look at the messages for an explanation.
Click to expand...
Click to collapse
Thanks for the tip. I started to use logcat couple of weeks ago. Then my tablet is turned off suddenly again as i described before. When i looked in the log-file, i saw high camera activity just before it turned off. My interpretation for that was "the Smart Stay + is the cause". I uninstallted it nearly two weeks ago, since then my tablet stays on as it has to . Thanks again for the tip .
Two days ago, my T-Mobile Samsung Galaxy S3 dropped out of my coat pocket as i was running for the bus. I picked it up and saw the screen was cracked along the top left and bottom left hand side. Everything was working for the past two days and i figured i'll just wait till Christmas to get a new phone. This morning i took my phone off the charger and turned it on. The Samsung logo flashed, and then the boot animation for Slimrom (the custom rom i'm currently running on) flashed for about a second but then the screen went black. I did a battery pull but the weird thing is whenever i put my battery back in, even without touching the power button, it boots up by itself but then the screen goes black again. I can access TWRP and download mode but they both go black after a few seconds as well. I was able to successfully turn on my phone and have it fully function for about 15 minutes after putting it back on the charger, but it quickly blacked out again. It also keeps randomly booting up by itself which is weird. Im guessing this is a problem with the screen itself, but could it be a software issue because the device keeps booting up by itself? If it is the screen, will i have to buy a new one or is it not worth it? I've also tried using a different battery and i have the same issue so it can't be that. Any help is appreciated!
Sounds like an issue with the power button, it probably got stuck somehow either when you dropped it, or after you dropped it. Do a simple search for power button and you will find ways to fix it!
Holy crap i didn't even think of that! It makes total sense since every time i even tap my power button, even for just a second, it turns on. I've read around that clearing the cache or a factory reset could work. Is this true?
Unlikely, unless it's a software issue but it's always a possibility. Slam the phone against something to try to get the power button back into place, or open it up and try to see if you can fix it yourself, or replace it
The problem seems to be gone. I haven't had any issues for two days now. All i did was press the power button really hard multiple times. Thanks for you help man!