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.
Hi all,
Its very weird for me, my phones vibration suddenly stopped working, completely. I tried all restart the phone, pull the battery out and start after 5mins but nothing helped.
If it’s a hardware issue then I’m worried as I didn’t expect this from a so expensive phone.
I will try factory reset later as I’ve to take all backups but if there any other suggestion please advice. As doing all restore will take time. thanks
soumen.sam said:
Hi all,
Its very weird for me, my phones vibration suddenly stopped working, completely. I tried all restart the phone, pull the battery out and start after 5mins but nothing helped.
If it’s a hardware issue then I’m worried as I didn’t expect this from a so expensive phone.
I will try factory reset later as I’ve to take all backups but if there any other suggestion please advice. As doing all restore will take time. thanks
Click to expand...
Click to collapse
Try flashing stock, or close to stock like Alexndr's ROMs. If they work on that, then it's a problem with your ROM..
I just checked with the *#7353# -- Self Test Mode (2nd Hidden Menu) code. it nothing happens for the vibration test, just the option going blue. Can any one try this and post what it does in other devices as i dont have any more note 3 here.
I think the vibration motor is gone.
nicholaschum said:
Try flashing stock, or close to stock like Alexndr's ROMs. If they work on that, then it's a problem with your ROM..
Click to expand...
Click to collapse
No other feedback in it. As the self test didn’t turn the vib on so I doubt it’s was hardware problem not a software issue, I googled and check the vib motor location in the phone and give some moderated tap/knock by my finger at the back of the phone and amazingly it started working again.
This is what didn’t expect from a $700 phone. Anyway the issue has been fixed temporarily don’t know what will happen in future.
I need an advice, if any one of you help. Now the thing is, when the vibration stopped, by tapping from behind it started working but after a day it again goes off and never turned on by any thing, I did the same thing many time but this doesn’t help.
After few days I put it on vib mode while listening song and chatting on hangout, I put it in vib mode as new message wont pause the song. But suddenly the vib started again. It worked for that day but next morning it gone again, and then I put it on vib mode and started sending fake msg over hangout many time and it started again after few attempt.
So here I wanted to know it’s a hardware issue or software end issue? as I'm really confused. Thanks
soumen.sam said:
by tapping from behind it started working
Click to expand...
Click to collapse
If it's software, no matter what, nothing can detect a tap from behind.
So it has to be hardware.
I think this could be a software end issue too, as now if its not working its not starting but hitting from behind, but if I restart its working again. it was off for a day then while I was listening song on vib mode it suddenly started by itself. since then its going off anyway and coming after restart. and it started after the last small OTA update.
soumen.sam said:
I think this could be a software end issue too, as now if its not working its not starting but hitting from behind, but if I restart its working again. it was off for a day then while I was listening song on vib mode it suddenly started by itself. since then its going off anyway and coming after restart. and it started after the last small OTA update.
Click to expand...
Click to collapse
Please use the reply button so I know you actually replied to the thread.
No matter what you do, hitting from behind as a fix means it's hardware. The fact that when you reboot is because it repowers the chip on the board, and when it does it probably allows for some grace working time.
nicholaschum said:
Please use the reply button so I know you actually replied to the thread.
No matter what you do, hitting from behind as a fix means it's hardware. The fact that when you reboot is because it repowers the chip on the board, and when it does it probably allows for some grace working time.
Click to expand...
Click to collapse
My Bad, I usually do so but somehow missed that.
Yes I doubt it’s a hardware issue but before repairing or replacing the vibration parts I wanted to try fix it by software end if this is a software issue. I still have the warranty period left for 6month or so but the thing is here in India Samsung doesn’t replace the complete faulty device like they or apple does in US. The always repair or replace the faulty parts. And I’m not comfortable to use a repaired phone.
What I was trying to do is I wanted to reinstall the stock latest firmware by Kies 3. I really don’t want to use any custom rom, neither rooting as Stock is quite good for me and fulfill my all requirement what I need for my work. But the thing is with Kies 3 1stly it always showing “N-900 Device not supported” when I was trying “firmware upgrade and initialization” but somehow I manage to let it work but at the end it showing “you are already have latest firmware” and it stopped.
I googled it as saw all those have this same issue, factory reset didn’t solve this, neither hard reset. I wanted to know is there any way to reinstall the same stock official updated firmware easily by Kies 3? I don’t wanted to do it by odin and a downloaded pack from sammobile, I am looking for a fast and easy official way. the reason I don’t want to use by odin is it will require lots of learning to learn the whole thing to avoid messing up with it, and I really don’t have time for this.
Also another question is: when I went to download mode for the 1st time I see its says “Knox warranty 0x” what does that mean? Warranty void or its still under it. I saw people have 0x0 or 0x1 but didn’t see any one having 0x only. Please advice, thanks
Edit: also now the vibration coming and going off by itself, like yesterday night it was not working but when I wakeup it was working, and no restart meanwhile. BUT I observed most of the time its turning off when I’m charging the phone or at the end of charging or before pulling the charging cable off. When charging starts it was vibrating and during charging it working same, but after I pull the cable, it stopped.
So I've looked at all the other threads on this topic already, and most of them were CM14.1 or CM14 issues... I'm running RR (as can be seen in my signature) on 3 of my S5's. 2 of them have been fine for almost a year with it. One of them isn't so happy
You turn it on... don't do hardly anything (i literally use it as a phone, imagine that?!?), no overclock/underclock or any root tools... just my standard MoodSMS app and the other standard minimal GAPPS
Could be 1 minute, could be 15 minutes, could be 3 hours, could be instant. I turn the device on, it works fine... Once I turn the screen off or it goes into sleep mode due to screen on time out, it never turns back on without battery pull. Also, sometimes it just randomly reboots and gets CRAZY hot
I'm chalking this up as a hardware issue, but I still wanted to ask others about it to see if maybe I'm just being stupid about something. This also is a Release Day Galaxy S5... so it is over 3 years old
Any experience with this kind of issue? if so, what did you do to try to fix it, or did you just get a new phone (i did personally, but I want to go back to my S5. Got a Nexus 6 and a 5C... ones too big, the others too small. S5 is perfect)
Post some logcats and dmsg logs?
Hello guys, right now, i am totaly pissed of on this piece of **** equipment.
This has been issue a long time ago but recently it happens very often.
First of all, when i turn car on, it goes to full reset mode. Or when i turn key on, HU turns on, but when i turn on ignitition - it resets. But right now i had 2nd full factrory reset in like 10 days, i really dont know why.
I am on 6.0.1 i updated it from version 5 long time ago and had no issues during the proces or after it.
Did anyone know what the hell is going? Is there hope for this trash to work normaly, at least for music and youtube? Turning on immediately when i turn car on without resetin, thats all i am looking for...
maricmilan said:
Hello guys, right now, i am totaly pissed of on this piece of **** equipment.
This has been issue a long time ago but recently it happens very often.
First of all, when i turn car on, it goes to full reset mode. Or when i turn key on, HU turns on, but when i turn on ignitition - it resets. But right now i had 2nd full factrory reset in like 10 days, i really dont know why.
I am on 6.0.1 i updated it from version 5 long time ago and had no issues during the proces or after it.
Did anyone know what the hell is going? Is there hope for this trash to work normaly, at least for music and youtube? Turning on immediately when i turn car on without resetin, thats all i am looking for...
Click to expand...
Click to collapse
Check your car battery or have it checked. If you car battery is bad and doesn't deliver a high enough voltage, this behaviour also occurs.