Related
I just had a scare. I updated my GN 8013 to JB 4.12 several days ago and haven't had any real issues. I let my Note go into hibernate to take a break and do some chores in between trying to finish an ebook checked out from my local library. The battery was at 68 per cent and I planned to be back to reading within 10 minutes. When I did get back to read and picked up my Note it wouldn't turn on. This is the first time this has happened. Jumping onto Google, it appears this has happened to other Samsung tablets in the past, usually after a software update. Here's a link I used and following the steps outlined in I then was able to reboot (keep finger on screen while holding down power button then reboot once battery icon appears on screen). http://mojocode.com/content/samsung-galaxy-tablet-101s-wont-boot My battery is still at 68 percent, but I'm leaving it plugged in while I do some other chores. I hope this isn't a new problem brought about by the update. If anyone else has this issue, I'd suggest we keep track so we can report to Samsung.
Yeah I think they call it the sleep of death. Happened to my recently updated wifi (8013)note also.
IF it is happening then only 8013 devices as none from other devices have reported so far. If two devices then it is a cause of worry
samir_a said:
IF it is happening then only 8013 devices as none from other devices have reported so far. If two devices then it is a cause of worry
Click to expand...
Click to collapse
I started the thread so we can see if it's happening to multiple units and what models and firmare seem to be affected. If more report the same issue, maybe this thread can be stickied. From what I read when looking for solutions, it seems to occur after firmware updates and has occurred on many of Samsung's tablets.
I have a N8000 and it's happened to mine three or four times since August; once on ICS. It would infrequently happen to my GT-P7500 on HC also. You can be in the middle of something and the screen goes black. No warnings or pop-ups, it just goes black. Nothing happens when you hit the power button normally like you would to wake it up. You have to hold the power button down for a looong time (maybe more than once) and the tablet boots. The first time it happens it's stroke inducing because you think your tablet's dead. After that it's just an annoyance. I have no idea what causes it but it does no harm (other than potentially losing unsaved work) when it happens. Between my OG G-Tab and the Note it's probably happened half a dozen times in eighteen months.
BarryH_GEG said:
I have a N8000 and it's happened to mine three or four times since August; once on ICS. It would infrequently happen to my GT-P7500 on HC also. You can be in the middle of something and the screen goes black. No warnings or pop-ups, it just goes black. Nothing happens when you hit the power button normally like you would to wake it up. You have to hold the power button down for a looong time (maybe more than once) and the tablet boots. The first time it happens it's stroke inducing because you think your tablet's dead. After that it's just an annoyance. I have no idea what causes it but it does no harm (other than potentially losing unsaved work) when it happens. Between my OG G-Tab and the Note it's probably happened half a dozen times in eighteen months.
Click to expand...
Click to collapse
On my GN 8013, I had to keep a finger on my screen while holding down the power button; that brought up the battery icon screen and from there I could reboot. Holding down the power button alone did not reboot and triggered my panic that drove me to a Google search and a solution to enable rebooting. This seems to be a long standing issue across versions of Android and manufacturers and seems to be a result of manufacturer code tweaking having unexpected consequences.
mke1973 said:
This seems to be a long standing issue across versions of Android and manufacturers and seems to be a result of manufacturer code tweaking having unexpected consequences.
Click to expand...
Click to collapse
I kind of look at it as the equivalent of the "blue screen of death" in Windows. My desktop PC throws a shoe every once in a while and it's usually tied to either graphics or memory conflicts based on the dump message. I'm guessing what we're experiencing is the Android version. As a pure guess I'd say it's something to do with memory reads/writes/buffers caused by either a management issue with the OS or an app (or combination of apps) doing something it shouldn't at an inappropriate time. And after playing with the power button I've gotten what you did (the giant battery icon showing up) and other times the Samsung boot logo. And I've had it happen twice in a week and other times once in six months; all without changing anything with the OS or apps. It's just one of life's little mysteries.
P.S. - My N2's done it but it behaves differently. It shows up a spontaneous reboot.
I had same issue frequently since last upgrade to 4.1.2 . I thought the problem is from Mobile VOIP. So I un installed it.
But today, another freeze happened. Ok, today just once. But, what's the problem?
N.b I recover it just by holding power button for 8 seconds.
Sent from my GT-I9100 using Tapatalk 2
mohammedsarhan said:
I had same issue frequently since last upgrade to 4.1.2
Click to expand...
Click to collapse
If it's happening frequently it may be something other than the random event some of us are talking about. A lot of you that upgraded from ICS to JB with all your apps intact could be having compatibility issues as not all apps have been updated/optimized yet. Older apps that are a little less mainstream and/or popular would be a good place to start to troubleshoot. Unless there's something specific to U.S. JB a lot of us have been on it since October and there haven't been any reports of frequent freezes or reboots. That is outside the random one discussed above that's not specific to JB.
mke1973 said:
I just had a scare. I updated my GN 8013 to JB 4.12 several days ago and haven't had any real issues. I let my Note go into hibernate to take a break and do some chores in between trying to finish an ebook checked out from my local library. The battery was at 68 per cent and I planned to be back to reading within 10 minutes. When I did get back to read and picked up my Note it wouldn't turn on. This is the first time this has happened. Jumping onto Google, it appears this has happened to other Samsung tablets in the past, usually after a software update. Here's a link I used and following the steps outlined in I then was able to reboot (keep finger on screen while holding down power button then reboot once battery icon appears on screen). http://mojocode.com/content/samsung-galaxy-tablet-101s-wont-boot My battery is still at 68 percent, but I'm leaving it plugged in while I do some other chores. I hope this isn't a new problem brought about by the update. If anyone else has this issue, I'd suggest we keep track so we can report to Samsung.
Click to expand...
Click to collapse
Pretty much exact same thing happened to me last night, for the first time ever. Took me about 30 seconds to get any response, by holding down the power button for a LONG time. Rebooted, saw the battery was below 20%, which was also odd since I had charged it overnight and had consistently been getting 2-3 days on a charge.
If it happens again, I'll go with Barry's suggestion and try a clean install, then adding apps one by one. Little disappointing though, as I've had no real problems at all with the GNote until this JB update.
Thanks,
JC
Sleep of Death...
I have the 16gb wifi GT8013 model and I am having the sleep issue too. Mine isn't "deathly" that requires the finger on the screen while powering up, or standing on your head and spinning three times while chanting "sleep of death" or any craziness like that, but every once and a while, for no rhyme or reason, I have to start it from a cold boot when I attempt to wake it with the power button. I press and hold the power button for 3-4 seconds and here comes the Samsung boot logo. Once it gets booted and connects to the wifi, I am good to go.
This happens so intermittently, with it not doing it for a couple days, or it might be within the next hour. I think I have narrowed it down to the wifi radio. Reason being...I have done a factory reset and tried running it naked and it still happened. But I have noticed the issue seems to happen when I have left the house and it drops the home wifi and then negotiates a new connection with my SIII hotspot, which I turn on before leaving the house for work, or anything that I will need connectivity for the tablet while away from the house. I don't know if it is due to roaming outside the home wife and dropping the connection, or if it is the combination of dropping the home wifi and then locking into the phone hotspot. I am so busy that I haven't been able to get that far in my troubleshooting. However, I am leaning to just the fact of it leaving a wifi signal and, I guess, it doesn't want to and gets jumbled and kills itself all together. I say that because it has happened when I have forgotten to turn on the hotspot until I got to work and then I open the tablet and its dead.
This has been happening from day one, when I bought the tablet towards the end of January. Unfortunately the Samsung warranty absolutely sucks, due to them wanting me to ship it in and do without it for 3wks and then to boil my blood even more, they want to give me a refurb unit if they can't fix this one. To make matters worse, its been almost a week now and they can't even get the shipping arrangements made yet! Needless to say, with this thing only being barely two months old, I am a little on edge with Samsung and I would love to figure it out and fix it myself. If it were something I knew, without a doubt, would be fixed with rooting and dropping CM on there, then I would. But I see there are still stability issues with most custom ROMs and I really would like to keep the functionality of the S-pen.
I have attempted to pull a log file with aLogCat and they are blank. It appears that the log files disappear when rebooted, which does me no good in figuring out what shut it down, if I can't recall the log from pre-shutdown. I have also tried aLogrec in hopes of accomplishing this, however, something isn't right because I left it recording for hours and days and the log file was only 1kb. Although, it doesn't much matter since the log recorder running in the background keeps it from sleeping to the point of shutdown, so I am assuming it is a sleep issue, due to that discovery.
If anyone has any thoughts that might help me, I am definitely all ears! This tablet is for work and school so it is next to impossible for me to do without it for 3wks...provided Samsung can get their crap in gear enough to even arrange the shipping for the service request. And I sure as hell don't want a refurb!!
Later,
Roger
I had periodic issues with the sleep-of-death once I updated to JB. It turned out that a VOIP program that worked fine on ICS (Sipdroid) crashed JB. I installed a different VOIP program that users said worked with JB (C-SipSimple) and my tablet stabilized. If you have non-stock apps that you use a lot, I would begin doing Google searches on them, starting with those that you use most frequently to see if anyone is reporting issues with JB (I wouldn't only rely on comments in playstore since users are more likely to engage in a discussin in a forum like this one). Good luck.
mke1973 said:
I had periodic issues with the sleep-of-death once I updated to JB. It turned out that a VOIP program that worked fine on ICS (Sipdroid) crashed JB. I installed a different VOIP program that users said worked with JB (C-SipSimple) and my tablet stabilized. If you have non-stock apps that you use a lot, I would begin doing Google searches on them, starting with those that you use most frequently to see if anyone is reporting issues with JB (I wouldn't only rely on comments in playstore since users are more likely to engage in a discussin in a forum like this one). Good luck.
Click to expand...
Click to collapse
Unfortunately, I have come to the conclusion it isn't an app issue. I have never used any VOIP service, of any kind, and I have done a factory reset and it happened before I installed any apps. Unless, of course, it is an app or service that is included in the Touchwiz junk and/or bloatware that comes with it. It happened on ICS, which is what came on it, and it happens after being update to JB. However, I only had it on ICS for a couple days and I would like to go back to it for further troubleshooting, but since it has been updated to JB, that isn't possible without rooting and I haven't decided if I want to do that yet.
--Roger
After further observation, it appears my sleep-of-death issues arise when I leave the comforts of my home Wifi. When doing so, apparently losing the Wifi signal causes the tablet to shut down completely... When asleep. If I have LogCatRec running, that keeps the tablet from falling into hibernate and the issue never happens, thus resulting in nothing interesting being logged, aside from the typical tablet activity.
Now the question arises, is it my home Wifi, or just leaving a Wifi range in general? I cannot get it to recreate the issue by simply turning off the Wifi signal it is currently connected to. However, I am now on a new Netgear router, due to the Belkin shooting craps on me, and it happened then, on the Belkin, and it happens now, on the Netgear. So, my presumption is that it has to drop a Wifi connection due to signal degredation, versus simply cutting a decent signal off at the source.
Has anyone else gotten this far with their sleep of death issue? Or is there another thread, that I've missed that I am just repeating? I am curious to see what's out there, before I send this thing off and its gone for three weeks!
-Roger
Sent from my GT-N8013 using xda app-developers app
I have no issues any longer after finding the offending app on my note and uninstalling it. I don't think there's one cause for this issue. Most often, Android OS updates seem to create program instability in some apps that then trigger the sleep of death. It gets hard to track down issues for individuals experiencing the sleep of death on their devices because we all have different apps installed. You might look at apps on your note that require WIFI to sync and are allowed to sync periodically since one of those may be the culprit. Check comments on Google Play to see if any are known to be buggy under JB. Good luck.
Mke1973, with all due respect, I dont think you are reading my post thoroughly.
As I have already said, this is not an app issue. I have done a reset and the issue still happens when I run it without any apps downloaded and installed. Unless it is an issue with a Samsung app that is preloaded, in which case the fix is still out of my hands, since the owner of the tablet can't uninstall crapware at their will, without rooting it.
Sent from my GT-N8013 using xda app-developers app
Actually, I wasn't ignoring your facts it's just that there are 3rd party apps installed by default that, if you decide to use them, require sync. Specifically I'm thinking of Evernote. Once device makers began pushing out upgrades to JB, some Android users began reporting incidents of the sleep of death when using or after closing Evernote in various Android forums. It wasn't a majority of people, but more than a smattering, but that is standard with the sleep of death. Again good luck on your hunt.
Ok guys. I don't post often since I can usually find my answers by lurking the forums....but I'm at my wits end here. My 2012 Wi-Fi nexus 7 all of a sudden started acting funny one day. It would freeze u randomly, then reboot, then get stuck in a boot loop for about 10-15 minutes, then boot up, then freeze after about 1-2 minutes of use and repeat the whole process. This was on stock 4.4.2. I've since tried using the toolkit to reflash stock, fix bootloop, unlock and root...all of which I was able to do. None of which helped my issue. Although flashing AOKP DID seem to fix it for about an hour.
Anyway, I gave up on it for about a week and came back to it this morning. Although it wasn't even going to te google boot animation, just stuck on the google logo. So I reflashed stock 4.4.2 again. Now I'm back to square 1. So it boots and will function for maybe about a minute or 2 (or less) before freezing and rebooting.
Is this device shot? I'm out of Google AND ASUS warranty now
I posted something in the big help thread yesterday (probably a mistake). Mine is doing exactly what you describe in terms of working for about 2 minutes before freezing, then rebooting. Mine is 100% stock 4.4.2. Never rooted, unlocked, etc. I have the adb stuff, but I haven't even attempted anything, because it seems so unstable. I don't want a partial flash to screw it up even worse. I feel slightly better knowing that someone else is dealing with exactly the same thing in a similar time frame, so maybe it is a software thing, not a totally dead unit.
Well I may have made some progress. Since the warrenty is up anyway, I decided to crack it open. I noticed the GPU was getting extremely hot for just sitting at the home screen. So I enabled developer options and turned on some monitoring options (the fact that it stayed on long enough to do this is a miracle in itself).
Right now I have some overlay monitoring on including cpu usage and gpu rendering (on screen as lines). I also checked the "stay awake" while charging option. It's been on about 2 minutes so far, although graphics performance is horrible atm. Almost like project butter is disabled and it's running at half power....that could just be the monitoring overlay though. We'll see what happens...
*Update*
It made it 21 minutes, but it did reboot again. On restart, the OS smoothness is back to normal, and it does seem like it goes longer stretches without restarting now, however the issue is obviously still there. I should add that the back cover is currently off. which is starting to make me think this has to do with cooling
9629464420
Okay....I just admitted defeat with this issue. Just ordered a replacement board for $30 because the resets are still happening. Upon reset, I can actually hear a part of the main board buzzing for about 5 seconds (not the speakers). Not to mention that prior to this issue, I was having a lot of wifi connectivity issues anyway. Hopefully the board arrives before my long bus ride to new york...
Dear community,
I own the phone since 1 1/2 years and so far I haven't had any problem, but since two days I have an issue with my N-900. My phone turns itself off several times per day. This happens when I don't use it for a while, or when I turn the screen off. Once it shut itself down, I can't even turn it on again. It behaves like a brick, it doesn't respond to any actions. Taking out the battery and put it in again, doesn't help. When I am lucky, it works after a while again, this can take between 5 minutes or half an hour. I already bought a new battery for the Note 3 and replaced the old one, it seemed like the most obvious reason, why I have this issue. Since I changed the battery yesterday the phone didn't make any issues, but this morning the problem occured again. So it can't be the battery. Currently I am doing a factory reset and reinstall android. My phone had been rooted. But smehow I think, it can't be a software related issue, otherwise it would be at least possible to turn the phone on all the time, wouldn't it?
Has anyone here exerpienced an issue like this before? Is it a hardware defect? If somebody had that issue before, what costs can I expect to fix it?
Thanks a lot guys!
Today I picked up my phone up to send a text and it was no longer powered up. It had randomly shut down.
When I switched it on again I noticed it has lost its battery stats so looks like they were reset or lost. There were no user apps installed on the phone either.
Have you had a similar experience?
You could try to reset it or take it back. Could be defective!!!
Was it somewhere it was hot? Maybe the phone got too warm and hit the shutdown temp?
Honestly hard (read impossible) to tell you what happened. Have any more info / logs?
I haven't had any issues with heat or shutdowns at all. I get 6+ hours SoT every single day at 75% brightness. 100% stock and unrooted. I use my N5 for all the modding aspects like V4A, Xposed, etc. I want this one for Android pay.
Anyways my uptime has been running since I unboxed it on 11/9/15. No issues.
I actually had it reboot in my pocket yesterday on the first day i had it but I already installed a custom ROM so no testing it out now.
RoyJ said:
Was it somewhere it was hot? Maybe the phone got too warm and hit the shutdown temp?
Honestly hard (read impossible) to tell you what happened. Have any more info / logs?
I haven't had any issues with heat or shutdowns at all. I get 6+ hours SoT every single day at 75% brightness. 100% stock and unrooted. I use my N5 for all the modding aspects like V4A, Xposed, etc. I want this one for Android pay.
Anyways my uptime has been running since I unboxed it on 11/9/15. No issues.
Click to expand...
Click to collapse
It was only room temperature. Here in England at 18cc so not too hot, but good point.
I read about the same thing happening with a N5 and it turned out to be a defective mother board.
Guess I should return today then... Bummer
If you just got it, might want to see if it happens again. I had one random reboot the first day and its been fine since.
My phone has started doing the same thing. Twice in 3 hours.
Same here...... 3 times reboot..... And now 2 times shutdowns.
I started having random reboots after I installed greenify. I tried several settings but had the same problem. It rebooted 5 or 6 times a day. I uninstalled it and haven't had any more problems.
I had my phone shut off yesterday and wouldn't boot until I plugged it in (it was at 80% battery). I then noticed that once it booted, it had deleted all of my paired Bluetooth devices.
Sent from my Nexus 6P using Tapatalk
murphyjasonc said:
I started having random reboots after I installed greenify. I tried several settings but had the same problem. It rebooted 5 or 6 times a day. I uninstalled it and haven't had any more problems.
Click to expand...
Click to collapse
Was just having the same problem but it was happening every 30 seconds to a few minutes. Deactivated greenify's device admin ability and now it's gone. Hopefully it stays that way, though if it comes to uninstalling it, that's fine since there don't seem to be as many background apps running on the 6P compared to my verizon LG G4.
Nevermind had to uninstall it.
Shut down, and a little warm
My nexus 6p shut down nearly every day, I just picked it up and it was shut down, I looked under battery and I could see it has been shut down for hours.. hope somebody knows anything about this problem.. I don't think a hard reset will help, because when I got the phone I installed all the update to Android 6.01 (MMB29M) and then I did a hard reset to make sure the phone was as good as it could be..
But maybe I'll try one more hard reset, just to be 110% sure
..
Lars
Danmark.
I'm having this problem too. It happens a couple times a day, and I think it always happens right after I pull it out of my pocket and try to unlock it. I'll feel the vibration from the Nexus Imprint fingerprint sensor, but then the screen doesn't turn on. So I try the power button, and nothing happens because the device is suddenly off. So then I hold down the power button to turn it on, and it boots normally.
Someone mentioned this happening with stock software, which makes me think it's a hardware problem, so we'll need replacement devices. However, I do have Xposed and GravityBox installed, so I need to rule those out first by removing them for a while.
I've had the phone for two weeks now and so far this happened twice.
The only two things that come to mind:
- enabling SRGB in the dev settings
- using a bluetooth headset
Has anybody pinpointed whether this is a HW or SW issue!?
How common is this ... I've seen ppl complaining in this thread and in Reddit also on random reboots as well
Thx
Still happening...
I am having the same issue. Did the reset to factory with no help. Phone was not hot, was sitting on my desk with 81% charged battery. This is the 3rd or 4th time in a week it just shuts itself off for no reason. Has anyone found anything??
I'm having this problem too, now on DVP 3 it's even worse. But I notice today that alarm clock works, but the screen won't. So I think is a SW related, the screen won't wake up, and after a while if you press the buttons the phone reboots. Anyone have e ideas how to fix this?
Enviado de meu Nexus 6P usando Tapatalk
facing this problem since may security update, on purenexus , dirty unicorn and rr rom. dont know if it hw or sw or simply power button getting pressed accidently.
I think I need to reopen this post, coz' I've been facing thif problems for so many times this week so I google around and come to this post.
Has anyone come to a workaround or point out if it is software or hardware related yet...? If it's hardware then I think I'm gonna go for a replacement then!!!
If you haven't done so already, go vote in the "early shutdown" poll
Hello guys,
I'm having two big problems since I bought the device (around 2 months ago).
1. My power button doesn't vibrate when I press it and I feel like it's "stuck". In the mayority of cases I can't even turn off my device and I have to use some app to do that.
2. I get random reboots during the day. It doesn't happen during a specific part of the day, but suddenly, when I'm playing or using social network, my device reboots and I can use it again after at least 15 minutes because it gets in bootloop for a very long time.
Can you help me?
Thank you!
Edit. My device is completely stock, no root and no custom rom ever installed.
That sounds like a possible hardware issue, especially if totally stock and you didn't change anything. For something like that I'd call support, it may need replacement which should be fine still being under warranty.
Just give a look at this post:
https://forum.xda-developers.com/g5-plus/help/solution-cell-mobile-standby-battery-t3612479
Are you sure you didn't turn experimental night mode on?