Related
Hi,
I've had my phone about a month now. I rooted it the day I got it. It seems like whenever I wake it up from long sleep or get a text message sometimes and try to wake it up, it freezes during the swipe and then randomly reboots. Sometimes it'll just make it to the att symbol and lock up again making me hold power down and then turn it back on. Then it works fine for a good period of time before the issue happens again.
tried- returning phone to stock. Didn't fix. Tried uninstalling att bloatware, not as frequent now but still happens. I have tried underclocking using rom manager. Didn't change anything. Next step maybe to try a custom rom and see if maybe there's a problem with my factory rom? Right now im in safe mode to see if its a third party app.
Is anyone else having this problem or should I consider warranty issue?
Not a third party app
It just did this in safe mode, so it must not be a third party app issue. I'm thinking about trying to install wicked rom following directions on galaxys4root.com. If it still freezes I think it may be a hardware issue.. Anyone have any thoughts?
alt keyboard?
My phone was/is doing the same thing. It seems to me like the phone is working now and I haven't had it freeze up since last night. Every time I install Swiftkey it starts freezing up and I have to pull the battery to reboot.
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
Hi guys
I recently bought an OnePlus 2. With the original firmware, I experienced a very strange and very annoying issue: My screen randomly turned off (e.g. during a chat in WhatsApp). The screen turns off and I have to turn it on again by pressing the power button. Then I enter my PIN to access my phone again and it locks AGAIN. This happens like 10 times in a row, then I have to reboot the phone and it was OK again. I seriously don't know what triggered this issue.
However, recently I got pissed of because I tried to call one of my customers and as soon as I entered my PIN and tried to open the phone app, the screen locked again and I almost threw away my phone. Damned troll.
So I decided to try another ROM as I thought it was an OS-related issue. Now I'm running Exodus Android 6.0.1. I did a clean install and guess what: The issue came back on this ROM...
In my opinion there's only something both installations (my previous 5.1.1 stock ROM and my current 6.0.1 ROM) have in common: I've been using XPosed with Amplify, Greenify and XPrivacy. Other than that, I have no idea what it might be.
Have you encountered the same or a similar issue? If so, were you able to solve it? How did you solve it?
I just uninstalled Amplify, as I think it stops somehow the Gyroscope service, that's why it locks randomly. I'll check if the issue appears again...
I think I have good news for you guys: I guess I was able to locate the issue.
I noticed it always happened when I was holding the phone in the hand I had a ring on my finger. Then I found out the phone has magnetic sensors (for flip covers).
I downloaded the Xposed module "Magnet Sensor Control", the bug hasn't appeared so far!
I hope I was able to help you guys with my findings. This thread may be closed now.
6P - Rooted, Stock, Xposed w/Amplify, Greenify, & Gravity Box.
Android v. 6.0.1 w/ 8/5/16 Security Patch.
Build number MTC20F.
Kernel version 3.10.7.-g909746b.
I'm getting 2 or 3 Sleep of Death (SOD) occurrences a day. Fingerprint scanner, nor power button press wakes it. I have to do a hard reset to turn it back on. I did a factory wipe about two weeks ago when it was getting to be that every time it slept it wouldn't wake up and it was better for a short while, but it's popping up again.
My research has shown that apps can cause it, but I have no way of narrowing down what's causing it at all. It's getting super frustrating at this point.
So my questions are:
1) Is there a way to figure out what's causing the SOD? I can't seem to find a pattern or figure out what's triggering it, so it's not like I can turn a logger on to figure it out before it happens.
2) Once I figure it out, what can I do about it? Or is there something I can do to prevent it without figuring out what directly is causing it?
Hopefully there's a solution that's obvious that I'm missing here. I'd rather not go through the factory reset process again, as it happened again after I reset the last time.
Help is sorely needed.
I use gravity box but not greenify. I use Recently instead of greenify with no problems. Not sure what Amplify is but I use the XML hack to raise headphone volume. Hope this helps.
RRuszczyk said:
6P - Rooted, Stock, Xposed w/Amplify, Greenify, & Gravity Box.
Android v. 6.0.1 w/ 8/5/16 Security Patch.
Build number MTC20F.
Kernel version 3.10.7.-g909746b.
I'm getting 2 or 3 Sleep of Death (SOD) occurrences a day. Fingerprint scanner, nor power button press wakes it. I have to do a hard reset to turn it back on. I did a factory wipe about two weeks ago when it was getting to be that every time it slept it wouldn't wake up and it was better for a short while, but it's popping up again.
My research has shown that apps can cause it, but I have no way of narrowing down what's causing it at all. It's getting super frustrating at this point.
So my questions are:
1) Is there a way to figure out what's causing the SOD? I can't seem to find a pattern or figure out what's triggering it, so it's not like I can turn a logger on to figure it out before it happens.
2) Once I figure it out, what can I do about it? Or is there something I can do to prevent it without figuring out what directly is causing it?
Hopefully there's a solution that's obvious that I'm missing here. I'd rather not go through the factory reset process again, as it happened again after I reset the last time.
Help is sorely needed.
Click to expand...
Click to collapse
I think the best way to diagnose and pinpoint the issue would be by obtaining logs. Haven't used xposed in a while though I think it has a log mechanism you can refer to. If you check the logs for keywords such as "error", "reboot", or "restart, etc. that may narrow down the processes causing the issue.
blitzkriegger said:
I think the best way to diagnose and pinpoint the issue would be by obtaining logs. Haven't used xposed in a while though I think it has a log mechanism you can refer to. If you check the logs for keywords such as "error", "reboot", or "restart, etc. that may narrow down the processes causing the issue.
Click to expand...
Click to collapse
Just checked. The logs are automatically cleared when the phone reboots or resets, so no way I can tell to get the logs before the SOD occurs.
RRuszczyk said:
Just checked. The logs are automatically cleared when the phone reboots or resets, so no way I can tell to get the logs before the SOD occurs.
Click to expand...
Click to collapse
Then try to capture a system-wide log instead. This article may help. Do the logcat after you have experienced the bug. I'm sure it will point out what's causing the issue.
Other than taking the logcat approach you can try eliminating possible culprits. If you suspect it may either be amplify or gb then temporarily disable each module within xposed then observe if the problem persists.
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.