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.
Hi,
Does anyone else have the same problem I have?
If I leave the phone running on battery for a couple of hours it is sometime impossible to wake it up by pressing the power button. Also the LED flashes white (not red). In order to get it working again I have to hold the power button a couple of seconds causing it to reset.
This happens on stock 4.2.1 and also in CM (4.2.1 and 4.2.2).
Seems like a HW problem? Should I send it in for repair?
BR/Svanteson
I've had this issue as well. It may be an issue with one of your downloaded apps. I have gone back to stock without any 3rd party apps and I haven't had the issue yet. Going to test a couple days and see what happens.
Edit: Maybe if you post some of your 3rd party apps you downloaded we can see if we have some in common.
Sure, here are some of my 3rd party apps
Moxier Mail
Eniro
Hitta
Wifi Analyzer
CPU Spy
Subnet calculator
Quadrant
Dropbox
Facebook
Whatsapp
Viber
Spotify
Shazam
MX Player
Truecaller
Llama
Android Lost
Out of those, Facebook and Android Lost are the only ones we had in common. I'll report back on this thread if this issue returns on my freshly flashed stock device without any 3rd party apps.
Similar problem here...
beand1p said:
Out of those, Facebook and Android Lost are the only ones we had in common. I'll report back on this thread if this issue returns on my freshly flashed stock device without any 3rd party apps.
Click to expand...
Click to collapse
Similarly, on two occasions now, I've gone to bed with the N4 on the charger, only to find it completely shutdown in the morning, and the battery unchanged from where it was when I plugged it into the charger. It required holding the power button down for quite awhile before I got a response and the unit rebooted. The first time, I didn't bother doing anything at all, but this morning, when it happened again, I called N4 support. I was advised to do a factory reset, and monitor it. If it did it again, they'll do an RMA. It seemed they would have sent another one right then if that's what I wanted them to do, but I told them I'd try the factory reset. They also sent an email with a direct contact link to the agent I spoke with in the event I need to return it.
My Device:
Nexus 4 16GB
Android 4.2.1
Kernel 3.4.0-perf-ge039dcb
Not rooted
I'll also post if the factory reset works. I've also read online, that holding the Volume Down and Power Button both for about 10 seconds, disregarding anything that appears on your screen, will shut your device down. Restart and, at least for several posters, the problem disappeared. Just an FYI. I'll try it if the reset doesn't provide the cure.
No joy....
Phubai said:
Similarly, on two occasions now, I've gone to bed with the N4 on the charger, only to find it completely shutdown in the morning, and the battery unchanged from where it was when I plugged it into the charger. It required holding the power button down for quite awhile before I got a response and the unit rebooted. The first time, I didn't bother doing anything at all, but this morning, when it happened again, I called N4 support. I was advised to do a factory reset, and monitor it. If it did it again, they'll do an RMA. It seemed they would have sent another one right then if that's what I wanted them to do, but I told them I'd try the factory reset. They also sent an email with a direct contact link to the agent I spoke with in the event I need to return it.
My Device:
Nexus 4 16GB
Android 4.2.1
Kernel 3.4.0-perf-ge039dcb
Not rooted
I'll also post if the factory reset works. I've also read online, that holding the Volume Down and Power Button both for about 10 seconds, disregarding anything that appears on your screen, will shut your device down. Restart and, at least for several posters, the problem disappeared. Just an FYI. I'll try it if the reset doesn't provide the cure.
Click to expand...
Click to collapse
Following up on my post yesterday, a hard reset did not help anything. Neither did an update to 4.2.2 for that matter. I also tried holding the Volume Down and Power Button until it shut down, and while the problem hasn't re-occurred, I really haven't provided enough time to tell yet. So Google is sending me another one and issuing an RMA. In the interim, while I'm waiting for the new one to arrive, I'll follow up if the VolDown and Power button has done anything.
I'm having the same issue. I just woke up, phone had a flashing white LED and would not boot. A reboot was neccessary. Is this a hardware failure?
The last couple of days I have not had WLAN activated. So far it is running fine.
I will activate WLAN today to see if the problem reappears.
svanteson said:
The last couple of days I have not had WLAN activated. So far it is running fine.
I will activate WLAN today to see if the problem reappears.
Click to expand...
Click to collapse
Why would you think there's a correlation between the two? I do have problems with wireless-notifications; for example, messages on whatsapp are often delayed, where I get a notification at say 11PM when the message was sent 10:45PM. Do you also experience this?
No problem noted this morning...
Phubai said:
Following up on my post yesterday, a hard reset did not help anything. Neither did an update to 4.2.2 for that matter. I also tried holding the Volume Down and Power Button until it shut down, and while the problem hasn't re-occurred, I really haven't provided enough time to tell yet. So Google is sending me another one and issuing an RMA. In the interim, while I'm waiting for the new one to arrive, I'll follow up if the VolDown and Power button has done anything.
Click to expand...
Click to collapse
I don't know whether holding the Vol Down and Power Button resolved the issue, but at least it didn't happen last night whereas it has been failing nightly when on the charger. Unfortunately, I was just notified that my replacement has already shipped, or I would tell them to hold off a day or two. For those of you experiencing this, you might try holding the Vol Down and Power Button at the same time until the device shuts down ignoring anything on the screen. Then simply restarting. I'm not saying that mine is fixed, only that it had a good night and that was the only thing I've done.
I will post again up until I have sent this device back. I have 21 days in which to return it or my credit card will be charged for real.
Phubai said:
I don't know whether holding the Vol Down and Power Button resolved the issue, but at least it didn't happen last night whereas it has been failing nightly when on the charger. Unfortunately, I was just notified that my replacement has already shipped, or I would tell them to hold off a day or two. For those of you experiencing this, you might try holding the Vol Down and Power Button at the same time until the device shuts down ignoring anything on the screen. Then simply restarting. I'm not saying that mine is fixed, only that it had a good night and that was the only thing I've done.
I will post again up until I have sent this device back. I have 21 days in which to return it or my credit card will be charged for real.
Click to expand...
Click to collapse
Mine also failed while on the charger a few times, but it also happened when not charging, so.... I'll try your solution. Why not!
This just happened again this morning. My alarm failed to go off, but the phone LED was flashing white. I could not turn the screen on. I did install some 3rd party apps yesterday:
Facebook
Tasks Free
reddit sync
Ally
IMDb
Pandora
Twitter
I tried the Vol Down + Power and that didn't work for me. I think I am going to RMA the device.
Yea...I have a few apps on my device, but not the ones mentioned here. So I don't think that can cause it. Hoping for more responses! I subscribed to this thread now.
Does anyone know if there is a bug report for this issue?
Not sure, don't think so as I've googled this quite alot. I just saw my telephone, which was idle next to me for about an hour, reboot itself. I saw the google and then the nexus logo without me even touching it. No white flashing LED this time, allthough that also has happened to me. This is getting very annoying now...
Google Support's reply on this
I have seen this happen to my phone more than a few times. I can't make it happen consistently though. I contacted the support hoping for a RMA, and today I received this response from them.
"Thank you for contacting us about your Nexus 4 and providing those details for clarification. This issue could be possibly not be a problem, it is a feature as with any Jellybean OS device; and goes in to the sleep state after some hours of inactivity - such as the details your describe when left overnight. It can go in to a deep sleep, where holding the power button for 30 seconds or more is what wakes the device up."
So this is a *feature*? It seems puzzling to me. I don't know if receiving a call would wake it up (if not, it would definitely be a problem).
I also tried different roms, PA and Xylon, and stock 4.22 with different kernels ranging from Franco to Motley. It would still happen. Rarely but it's still there. Also I am trying to see if changning the minimum clock speed to 1024 would change anything. I will report back once I have more info.
Still working so far...
I've not had a problem with mine since the Vol Down and Power Button shutdown. It may not even be related and may have just "healed" itself, or the problem has simply become intermittent and hasn't repeated itself yet...dunno unfortunately. Since my replacement will be arriving today, I may never know since I'll be shipping this one back to them. I may wait until Monday to ship it though, and see if it acts up again and repost if it does or doesn't.
Hopefully the replacement won't have this problem at all!
locked up
I don't think the flashing white-LED is a signifier of a problem. I think it is a different status message, like email or facebook, or something. I haven't found that documented anywhere, but I've noticed it is blue sometimes and white other times. Without being locked up.
My phone will lock up while charging overnight. I have turned off Dream State and the LED notifier thinking it was related to these. It did seem to be somewhat better after that, but the last two nights have seen the phone locked up.
Also, holding down the power button for 30 seconds will hard power it off at 10 seconds, it seems to me. That is typically how I deal with this lock up! Hold down the power button 10 seconds, release, press it again and wait for it to boot.
This is frustrating. I was thinking of rooting the phone so I can use a logwatcher, but I'm not sure I will see anything in the logs after booting the fracking thing.
But.. while I consider that I will start by uninstalling Facebook, Dropbox, and Twitter apps, based on seeing them on other people's lists.
I'm going to RMA the phone. Just a question, what charger do you guys use? I've been using a samsung charger (from my Galaxy S2), perhaps that's related? As it does happen while charging mostly, allthough I saw the phone reboot itself out of nowhere without it being plugged in yesterday too.
I've only used the Nexus 4 charger on mine. No others. I'm on my new device now but haven't sent the other one back yet. Probably tomorrow.
Sent from my Nexus 4 using Tapatalk 2
Hi all,
I know there a two threads open about random freezing and rebooting but I just wanted to find out if there are users in UK like myself who have had their S7 or S7 Edge freeze out of nowhere then shut down. Mine has done it twice since I got it on the 8th but it doesn't reboot just turns off and requires me to press volume down and power for around 7 secs, mine has come back on both times using this method luckily.
Do we think this is a software issue or hardware? Not sure whether to even go to Samsung as I think I'm just going to get the same old response, then swapping it and still having the issue with new one. Would like to know if many other UK users have had this happen, US users seem to have random freezing and reboots will using certain apps but mine both happened while using the multi tasking button . .going back into others apps etc
Cheers guys!
Mine did it a couple of times on the 8th. After that it hasn't done it since.
Hi
I have my sgs7e from Virgin, black version. Very first hour it froze once but that could be the fact the apps didnt optimaze fully. That was a one off and the phone is flying fast since.
Btw. Using smart manager by Samsung very often to kill running tasks and free up ram. Phone is a beast, very happy
Sounds maybe app problems more than a full hardware issue . . Hoping a update fixes but it isnt doing it to me on a daily basis
Got the UK version direct from Samsung and had no freezes or unwanted restarts since launch.
My wife has the EE brandad model. Her's has restarted on it's own once since she got it on the 8th.
I have had no such issues with my unbrandad model (purchased from CPW)
Mine has frozen 3 times. I've had to manually shut it down with volume down + power to get it unfrozen
I have an S7 edge black and it froze for the second time last night using the night clock at 00:02. I wasn't even using the phone so have no idea why this would happen!!!
ive had it happen 3 times but i think its got something to do with the sd card because when it eventually restarts it doesnt see the card until i restart it again
done it once while in aida64 totally froze and needed me to force reboot
not done it since
mine was from EE
Mine has frozen 3 times too. I've had to manually shut it down with volume down + power to get it unfrozen
Mine has frozen at least 5 times since 8th March when I got the phone from EE. The first 3 times it happened when the phone was not in use but had the always on clock turned on. I thought it was the always on screen causing it and turned it off, but in last few days it has happened again when I was simply using the phone. I had to reboot it by holding the power button with volume down. Really frustrating especially when you have spect so much money on pre ordering an expensive phone and contract.
I wasn't expecting it from S7 edge which is Samsung's flagship phone. Very disappointed with the stupid Touch-Wiz interface. I wish they sell 2 versions (one with Touch-Wiz and one without) and let users to choose. It eats so many resources and is completely pointless. Samsung better release an update to fix this issue.
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Sounds like your battery is on its way out. Have you tried a new battery?
Already mentioned in post above
tiguy99 said:
Sounds like your battery is on its way out. Have you tried a new battery?
Click to expand...
Click to collapse
QCube said:
I've tried everything, bought a replacement (genuine) battery and not fixed it.
Click to expand...
Click to collapse
Earlier in the week I had an error I've not seen before. Phone restarted and went to black screen sort of looking at a recovery screen with android logo and in the centre of the screen was the message
"Kernal Panic" with some information on the top. This only has happened the one time and hasn't happened since. Took the battery out and restarted again...
Try hardreset or flash via odin
Krprem said:
Try hardreset or flash via odin
Click to expand...
Click to collapse
How do I go about doing either of these....
Still happening and it's driving me insane, It won't last me until the end of my contract (January)
Its rebooting 80-90 times in ONE day? Good god! Have the phone turned off then. Unnecessary pressure is being put on the phone mate!
Factory Reset isn't going to solve it anyway, its for tiny problems. Your system is somehow messed up badly.
Do what the above member said. Flash a stock ROM via Odin. But before that you need to completely wipe the phone. To completely wipe you need a custom recovery like TWRP. So flash it now, root the phone, then reboot into TWRP and use the Advanced Wipe section to wipe everything (external SD not needed), then reboot the phone in Download mode, and flash the latest stock ROM via Odin.
You are now part of a large group of us having the same issues. Several things have been tried. One thought is that the motherboard is faulty. Replacing it would be expensive. Download the app "wake lock" and set it to partial_wake_lock. Don't ask me why it works, but it does. Apparently the phone goes nuts when the screen tries to go off, the partial lock keeps it from crashing. That makes the phone usable, hopefully a permanent solution will become available. ;( The only time it goes nutty again is if the battery runs down and when I restart, the app is not running. Going back to the back and setting it to partial has allowed me to play games, etc for extended periods of time and no problems. It shouldn't be that way, and I really suspect the marshmallow update and then security update screwed it up, it was fine before that.
QCube said:
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Click to expand...
Click to collapse
Which version is your note 4? verizon? att? tmobile? sprint? etc united states variant? other country? This helps find out if others that are having the same problem are on the same setup as you and more importantly tells me if I'm likely to have a problem with mine getting ready to come. :laugh:
ithehappy said:
Its rebooting 80-90 times in ONE day? Good god! Have the phone turned off then. Unnecessary pressure is being put on the phone mate!
Factory Reset isn't going to solve it anyway, its for tiny problems. Your system is somehow messed up badly.
Do what the above member said. Flash a stock ROM via Odin. But before that you need to completely wipe the phone. To completely wipe you need a custom recovery like TWRP. So flash it now, root the phone, then reboot into TWRP and use the Advanced Wipe section to wipe everything (external SD not needed), then reboot the phone in Download mode, and flash the latest stock ROM via Odin.
Click to expand...
Click to collapse
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
phonepie said:
Which version is your note 4? verizon? att? tmobile? sprint? etc united states variant? other country? This helps find out if others that are having the same problem are on the same setup as you and more importantly tells me if I'm likely to have a problem with mine getting ready to come. :laugh:
Click to expand...
Click to collapse
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
grizzylemon said:
You are now part of a large group of us having the same issues. Several things have been tried. One thought is that the motherboard is faulty. Replacing it would be expensive. Download the app "wake lock" and set it to partial_wake_lock. Don't ask me why it works, but it does. Apparently the phone goes nuts when the screen tries to go off, the partial lock keeps it from crashing. That makes the phone usable, hopefully a permanent solution will become available. ;( The only time it goes nutty again is if the battery runs down and when I restart, the app is not running. Going back to the back and setting it to partial has allowed me to play games, etc for extended periods of time and no problems. It shouldn't be that way, and I really suspect the marshmallow update and then security update screwed it up, it was fine before that.
Click to expand...
Click to collapse
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
While upgrading a phone, especially for major upgrades like from LP to MM, OTA method should always be avoided. You MUST do a clean flash of the ROM, otherwise you are bound to have problems. 80% of time people complain because they didn't flash the ROM cleanly, so whatever you want to do now, do it, but if it doesn't solve it (very likely it won't), then kindly flash the ROM via Odin after a full wipe. And if even that doesn't solve it then its hardware.
QCube said:
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
Click to expand...
Click to collapse
Thanks for letting me know your version. Hopefully it wont affect mine since mine is US Verizon. But out of curiosity have you checked for even the slightest sticky button? I've had phones where a button started to get tacky and would cause it to keep the screen on or go on and off like what you're saying. May not even feel like a sticky button. Do they all click very responsive? or do any feel like they have a dull thud experience?
phonepie said:
Thanks for letting me know your version. Hopefully it wont affect mine since mine is US Verizon. But out of curiosity have you checked for even the slightest sticky button? I've had phones where a button started to get tacky and would cause it to keep the screen on or go on and off like what you're saying. May not even feel like a sticky button. Do they all click very responsive? or do any feel like they have a dull thud experience?
Click to expand...
Click to collapse
The volume rocker and power button feel really loose but this isn't really something new. Something I have noticed is when I take the cover off the back, the battery barely stays in itself. If holding screen upwards and battery cover off then It doesn't hold the battery which made me possibly think that perhaps the battery does not situate properly and doesn't deliver enough power (or too much) but this was just one of my theories into why the hell my phone is acting this way.
Edit:
Forgot to add I'm running the security patch 01/08/2016
QCube said:
The volume rocker and power button feel really loose but this isn't really something new. Something I have noticed is when I take the cover off the back, the battery barely stays in itself. If holding screen upwards and battery cover off then It doesn't hold the battery which made me possibly think that perhaps the battery does not situate properly and doesn't deliver enough power (or too much) but this was just one of my theories into why the hell my phone is acting this way.
Edit:
Forgot to add I'm running the security patch 01/08/2016
Click to expand...
Click to collapse
Are you able to wedge a folded small piece of paper between the bottom edge of the battery and the phone to make the battery fit tighter? I mean it's not good to have a loose battery. But I can't see how that would cause the screen to stay on. If anything I would think it would cause the phone to shut off or reboot.
QCube said:
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
Click to expand...
Click to collapse
Let me know how it goes. There are other threads about same issue. Most of us have tried reflashing, wiping everything, custom roms, going back to stock, trying to downgrade, taking out the sim card, taking out the sd card, not having both in at same time, brand new battery, I think even putting the battery in the freezer momentarily, etc. etc. Nobody seems to have had any real luck with it, except those who were under warranty and got a new phone, or are capable and wiling to exchange some hardware. I just find it odd that it happened all of a sudden after updates and recently to many people.. Still, I keep coming here hoping someone will have great news. Mine started with marshmallow, but definitely got worse with the security update.
grizzylemon said:
Let me know how it goes. There are other threads about same issue. Most of us have tried reflashing, wiping everything, custom roms, going back to stock, trying to downgrade, taking out the sim card, taking out the sd card, not having both in at same time, brand new battery, I think even putting the battery in the freezer momentarily, etc. etc. Nobody seems to have had any real luck with it, except those who were under warranty and got a new phone, or are capable and wiling to exchange some hardware. I just find it odd that it happened all of a sudden after updates and recently to many people.. Still, I keep coming here hoping someone will have great news. Mine started with marshmallow, but definitely got worse with the security update.
Click to expand...
Click to collapse
why don't you reflash you device with supported PIT file and stock F.W ?
QCube said:
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Click to expand...
Click to collapse
Aside from the previously proposed wake lock solution, members in the T-Mobile Note 4 threads have experienced limited success with a downgrade to LP from MM.
From my reading, these issues seem to be common across all Snapdragon models, not to say it Exynos is excluded (I don't frequent Exynos threads).
himuslg123 said:
why don't you reflash you device with supported PIT file and stock F.W ?
Click to expand...
Click to collapse
I tried that and it didn't work for me. The only surefire solution is a replacement device, but even then there's no guarantee the device won't start acting up in the future.
pls help stuck in download mode
this is the issue I'm getting...I did a complete data wipe using twrp...now stuck on this screen...cant even push files...device not recognized in adb or fastboot mode....
what to do...??
imgur(dot)com/a/gKPaL
Well a new motherboard was the only thing that fixed it for me, replaced under the 2 year warranty but I had to wait a while for parts. What is interesting is that the phone is much faster, the battery life much better than when it was new. Also it now barely gets warm using google maps - before it got quite hot. It would be very interesting to find out what percentage of Note 4's have been going down with is problem - mine was a fairly early one - was Samsung rushing to beat Apple two years ago and a bad batch of parts used? I don't know -we need some answers on what is the problem to be sure.
Just a personal experience and thus advice, please don't keep flashing bunch of stuffs every other day. The more your eMMC gets used more chance of your phone getting messed up. This is how my Note 3 died, kept flashing this and that, and did the same on Note 4 too, but have now stopped. I don't know whether there's an endurance rating on these eMMCs used or not but this is what I think, I could be wrong, please quote me in that case.
hathertonwood said:
Well a new motherboard was the only thing that fixed it for me, replaced under the 2 year warranty but I had to wait a while for parts. What is interesting is that the phone is much faster, the battery life much better than when it was new. Also it now barely gets warm using google maps - before it got quite hot. It would be very interesting to find out what percentage of Note 4's have been going down with is problem - mine was a fairly early one - was Samsung rushing to beat Apple two years ago and a bad batch of parts used? I don't know -we need some answers on what is the problem to be sure.
Click to expand...
Click to collapse
Wow, that sounds promising. I'm sending mine for replacement, and although I'm not getting a new MB installed, hopefully the incoming unit will be similar in performance to yours.
ithehappy said:
Just a personal experience and thus advice, please don't keep flashing bunch of stuffs every other day. The more your eMMC gets used more chance of your phone getting messed up. This is how my Note 3 died, kept flashing this and that, and did the same on Note 4 too, but have now stopped. I don't know whether there's an endurance rating on these eMMCs used or not but this is what I think, I could be wrong, please quote me in that case.
Click to expand...
Click to collapse
Your reasoning sounds plausible, but my phone suffered similar issues and I only flashed my unit 2-3 times in the 14 months I had it.
hello,
my note 4 has been working pretty good up until maybe a week ago, and then it started to randomly turn off and sometimes it would re-boot. other times pushing the home button it wouldnt awake, even thou the blue led lights was flashing like i had a message or notification, pushing any button would not awaken it, pushing and holding the power button would not turn it off, prompting me to pull the battery out. put the battery back in, push and hold the power button had no effect, having to volume down, home button, and push power button, and then volume down when prompted would boot the phone.
many times the phone would freeze, and pop up window would say X app has stopped working do you want to shut it down?, play store, samsung ui, various apps.
so, i googled my symptons, several suggestions suggested remove google play updates and then reinstall and update everything, that was last night. it casually freezed more and then it seemed to sort of work better last night and this morning. and just a few minutes ago, i had a new pop up screen "Runtime Error bad argument#1 to 'abs' (number expected, got nil)" as google is one of my loyal and usually helpful friends i asked it, to my surprise i found basically zilch. putting "Runtime Error bad argument#1 to 'abs'" inside quotation marks was limiting results, it didnt look like other phone users had had similar troubles.
i did see this hit "http://geco.mines.edu/guide/Run-Time_Error_Messages.html" lightly scanning over it made me think i was not looking in the correct place. as the word "intel" was mentioned a few times.
i found another page "https://github.com/layeh/gopher-luar/issues/1" as the title is similar to my issue "bad argument #1 to <function name> (userdata expected, got string)"
those with far more of an understanding of android and code, please assist...
thank you
View attachment 4419367
More and unusual pop ups
nothing?
seems my phone has signed me out of google play
and has unrooted itself
many times the "Samsung UI has stopped working" pops up
i was hoping those with much more knowledge would have offered some suggestions.
i will back up all my data (in several different ways)
root my phone (again)
do a system re-format
and then re-install my apps and crap
crossing my fingers that that is all it needs... cause frankly i have no idea what, how, or why it recently crapped out. i suspect it was one of my apps, as the phone was working very well for several years, and within the last few days its all freezes and hangs, and occasionally crashes and reboots..
This morning I woke to find my phone looking like this