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.
Since day one I've had issues with random shutdowns (plenty of threads out there about it). Mine happen when the device is in use, usually when switching between applications.
In my case it disappeared after a reset but then returned after installing lollypop. I get a shutdown maybe once or twice a day. Each time the phone won't turn back on unless I remove the battery.
Just discovered that if it shuts down plugging in a power cable not only causes it to switch back on without a battery pull but it automatically starts again!
Anyone else noticed this? I'm still not sure about returning the device for a replacement! What do you think?
I've had this issue, it did stop for a few weeks without me doing anything to the device but the last couple of days it's returned. Hopefully just software related since so many people seem to have the same issue.
ben.cordy said:
Since day one I've had issues with random shutdowns (plenty of threads out there about it). Mine happen when the device is in use, usually when switching between applications.
In my case it disappeared after a reset but then returned after installing lollypop. I get a shutdown maybe once or twice a day. Each time the phone won't turn back on unless I remove the battery.
Just discovered that if it shuts down plugging in a power cable not only causes it to switch back on without a battery pull but it automatically starts again!
Anyone else noticed this? I'm still not sure about returning the device for a replacement! What do you think?
Click to expand...
Click to collapse
this is a well know issue and has been fixed via software updates, please make sure you are on the latest version firmware.
i had the problem when i first got the phone, solved problem after two updates.
weird_iris said:
this is a well know issue and has been fixed via software updates, please make sure you are on the latest version firmware.
i had the problem when i first got the phone, solved problem after two updates.
Click to expand...
Click to collapse
As mentioned in my original post I had the problem at first but a factory reset with the latest software corrected the issue. I've since upgrades via kdz to the latest lollipop rom (v20a) which brought the issue of random reboots back. As mentioned these seem different to the ones common to this device as they always happen during use of the phone and not whilst it's idle.
The only time i have random turning off is when i leave it on charge over night
Sent from my LG-D855 using XDA Free mobile app
I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
ks-man said:
I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
Click to expand...
Click to collapse
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late
jbkmin said:
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late
Click to expand...
Click to collapse
Did your issues first start after you upgraded to lollipop?
ks-man said:
Did your issues first start after you upgraded to lollipop?
Click to expand...
Click to collapse
Definitely after the upgrade.
While on KitKat, it never happened (1 month ownership). But after upgrading to lollipop, it has happened 4 times (6 nights since lollipop).
Have you figured anything out with your situation? Woke up this morning to my backup alarm and the Yellow Sprint screen on my phone.
I guess I'll have to try another factory reset and if it still happens try and get a replacement. It just doesn't seem widespread enough of an issue to be a software bug with 5.0.1.
Very frustrated. I did another factory reset but the issue still plagues my device. It still only occurs once or twice a week but when I hear my old clock radio alarm in the morning I know when I look over I'll see the yellow frozen Sprint Spark screen. I am completely out of ideas and guess I will need to have it replaced under warranty. I'm hoping Sprint won't give me a hard time as this will be very hard to demonstrate.
It definitely appears to be a software issue as it never happened before I upgraded to Lollipop but there must be more to it or others would be complaining.
If anybody has ideas please let me know. Thanks.
Response to Note 4 Freeezing while charging
I have found that after turning the quick charge feature off the problem is not happening. Hopefully this is fixed in 5.1
I'm having the same issue even after turning quick charge off..def a lollipop bug, never experienced this on kk.
I know its not the BEST option, but after taking the update to lollipop, sometimes left over kitkat files can make the system poop out. Sometimes a factory reset will take care of the leftovers. But of course, then you have to set your phone up again
If you've tried this or plan to to, let us know the results.
(When i first took the update, my heartrate monitor sensor was always on, so i did a factory reset and it fixed my problem).
Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.
same problem here
Ive tried turning off fast charging option on the powersaving mode
And also tried the option on developer mode, the "keep device awake while charging"
And even flashing dofferent firmwares from sammobile through ODIN and installed custom roms. These options doesnt resolve the issues on freezing while charging..
I think turnong off your device while charging is the only option..
Im using note4 N910C..
Clasimodo said:
Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.
Click to expand...
Click to collapse
Thanks a lot, Mate. I'm trying your workaround now. Will report later if it works on my phone. BTW, so, are you sure it is a just a system issue? Definitely, isn't a hardware problem? Did you fix it, after your post -a month ago-, installing, for example, lollipop 5.1.1 or Cyanogenmod 12.1? I'm on 5.0.1, SimpleRom V4. Of course, mi device, N910C, is rooted.
Thanks again.
With lollipop 5.1.1 the problem is solved for me, even without this workaround.
Sent from my SM-N910F using XDA Forums PRO
I'm having similar issues as you guys. I found out that my phone will only perform normally when I charge it with my laptop USB port which I think is around 0.5amps. Anything above that, even a 1amp charger would cause the phone to freeze, reboot and turn off and not turn back on. The phone has been in repair 4 times and the problem is still there. Now every night I'm forced to charge my phone with my laptop which takes an age instead of the fast charger that came out of the box.
Currently my phone is still freezing and rebooting when I'm out and about and the only way I can get it to perform normally is when I plug it into my laptop. This normal functioning would only last whilst the phone is plugged in.
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 XDA,
This is my very first community post so please don't judge if I do something wrong here
Let's cut to the chase. I am a happy owner of the OP6T 8/256gb phone and I am super happy with the device, however, I have been having an awkward issue. From time to time, couple of times a day, my phone would not recognize neither double tap nor the power button to wake the display up. Usually out of frustration I press the power button couple of more time, but nothing happens. Then after 3-4 seconds the display wakes up and even opens the camera (because I pressed the button couple of times, but not in a fast way...). Afterwards, the phone works without an issue until same thing happens hours later.
So my question is if anyone is experiencing anything similar and found the culprit of it?
If you need any additional info on my settings, please let me know!
It is not the worst thing that could be happening with a new phone, but you know, one expects the brand new phone to work 100% of the time
Looking forward to your replies and ideas!
Many thanks,
Donatas
It's happened to me only recently. I'm rooted with magisk 17.3 running a few modules such as dual speaker, Google dialer framework and viper. I was on stock kernel, but switched to Smurf kernel without any hiccups so far.
Well I am full stock, even with stock launcher... That's why it bothers me that it is happening:/ thanks for your reply
Donis.za said:
Hello XDA,
This is my very first community post so please don't judge if I do something wrong here
Let's cut to the chase. I am a happy owner of the OP6T 8/256gb phone and I am super happy with the device, however, I have been having an awkward issue. From time to time, couple of times a day, my phone would not recognize neither double tap nor the power button to wake the display up. Usually out of frustration I press the power button couple of more time, but nothing happens. Then after 3-4 seconds the display wakes up and even opens the camera (because I pressed the button couple of times, but not in a fast way...). Afterwards, the phone works without an issue until same thing happens hours later.
So my question is if anyone is experiencing anything similar and found the culprit of it?
If you need any additional info on my settings, please let me know!
It is not the worst thing that could be happening with a new phone, but you know, one expects the brand new phone to work 100% of the time
Looking forward to your replies and ideas!
Many thanks,
Donatas
Click to expand...
Click to collapse
Yes this has happened to me, glad to see I'm not alone.
It happeneds randomly, like few times a day, not too frequent to render the device unusable, but enough to be irritating - especially when it's a brand new device.
My setup;
*Rooted
*Magisk (viper & YouTube vanced module)
*Stock kernel
I'm at a loss as to what's the cause of this issue, it's very weird, it could just be an oxygen os bug that will be resolved by OnePlus. Who knows. Hopefully if more people comment about this here - we will eventually get to the bottom of it.
So far on 9.0.6 build the issue appears to have been fixed, I have not had any random temporary lock screen freeze.
Can anyone else confirm this?
krohme said:
So far on 9.0.6 build the issue appears to have been fixed, I have not had any random temporary lock screen freeze.
Can anyone else confirm this?
Click to expand...
Click to collapse
Glad to hear it is fixed for you!
Unfortunately, since the update, I already experienced it 4 times...
Even more so, sometimes now the phone would randomly stop playing music from Soundcloud (I dont know about other apps, i predominantly use Soundcloud).
I love the phone but it is a little shame that some of these features are failing
Hope 1+ will fix this and we all be happy!
Yeah, sometimes my device doesn't respond to double-tap. Usually I just have to double-tap again and it wakes up. I haven't noticed the issue with the power button, but I rarely use that to wake the device. I did have a situation recently where the device wouldn't wake from a screen tap no matter how many times I tried. I can't recall if using the power button woke it or if I had to force a reboot. But that's only happened that one time.
I just updated to 9.0.6 a day ago. I don't think I've experienced any non-wake issues since then. Really haven't been paying that close attention, I guess.
I believe I am having this issue. I just flashed 9.0.7 from TMO and I'm rooted with magisk v4a and vanced. I get random freezes where I can't tap anything on my screen. I have to turn it off and on with the power button.
I experience this as well. I thought it was just an isolated thing, and it's kinda annoying...
It's very irritating. I'm trying to pin point it and so far I notice it with Firefox and Spotify transitions.