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.
Related
My streak was working flawlessly until yesterday. Since yesterday all i did was to install 3 apps. Dialer One, ADWnotifier and AutoKiller Memory Optimizer.
Now every time my screen turns off to sleep after a minute i push the power button and it doesn't wake. Sometimes i press the power button and the phone reboots. I uninstalled all 3 apps but still the same.
Any suggestions? I'm freaking out here
My streak has 2.2 latest official with Steve's performance fix.
Thanks
I was experiencing this same issue and also had AutoKiller Memory Optimizer installed. I removed it and still the same thing. I suspected Tasker was the culprit so I disabled it and the problem stopped. I enabled Tasker after a day and only turned on one profile.....no issues. I am slowly reactivating the various profiles I have on it to see if I can ID the problem. I realize this may not help you but you should know you aren't the only one.
My suggestion is to remove/disable all third party apps and if the issue persists then perform a factory reset or install a fresh ROM.
It would be nice to know if there is some kind of logging that can be done to help diagnose the issue.
zyonuf79 said:
I was experiencing this same issue and also had AutoKiller Memory Optimizer installed. I removed it and still the same thing. I suspected Tasker was the culprit so I disabled it and the problem stopped. I enabled Tasker after a day and only turned on one profile.....no issues. I am slowly reactivating the various profiles I have on it to see if I can ID the problem. I realize this may not help you but you should know you aren't the only one.
My suggestion is to remove/disable all third party apps and if the issue persists then perform a factory reset or install a fresh ROM.
It would be nice to know if there is some kind of logging that can be done to help diagnose the issue.
Click to expand...
Click to collapse
is Tasker something that's installed by default? I can't find it anywhere.
Hey guys, I got my Nexus 4 about 2 weeks ago. Love the device, and haven't had any problems until recently. I set alarms to wake myself up in the morning. When it comes time for the alarm to go off, the device fails to ring, and when I attempt to turn it on, it fails to work. I have to hard reset it in order for it to turn back on. Do keep in mind, that I use multiple alarms, so the device's screen is always off when this happens. I also have installed JuiceDefender, and I think that might be a possible cause for this crash (I will have to do some trials). I did a search on the forums, and haven't quite found anything specifically related to this, just yet. I've read some things about wake locks, but I don't really know much about them.
Is anybody else experience this issue? I am on 4.2.1 stock everything. I have JuiceDefender Ultimate, and I believe it may be a source for the issue. But I will have to test further. Any ideas?
Thanks, in advance!
Today I've the problem again, the notification simply doesn't work, it looks like the sensor is failing or something because I took it out of the pocket, as usual, and it doesn't light on... having to use the power button again...
It happened other time, some weeks after I bought it... complaining with the technical support on Moto Care, without results, so I've factory reset and wipe everything, and it works...
So, my first guess is that the cache of Active Notification may have some guilty on that, but I can't find the app from it to clean and check if it works. Does anyone knows what app is it?
I'm not gonna to factory reset this time, it simply not useful as a solution.
Does anyone have/had this problem?
Regards,
It happened to be one time. I found the solution to be simply disabling Active Notifications and then re-enabling it.
Julianocas said:
It happened other time, some weeks after I bought it... complaining with the technical support on Moto Care, without results, so I've factory reset and wipe everything, and it works...
Click to expand...
Click to collapse
If a factory reset fixes it, it's probably not a sensor issue. It's possible that an app you've installed is interfering with it somehow - do you have any kind of root apps, or apps that play with system resources (like process managers/Greenify/etc.), or apps that control notifications?
I've noticed this on 4.4 a few times, as well as the lag on unlocking from AN a few times, too. Then again, I'm still on the leak, so that may have something to do with it.
Case maybe? Make sure the screen is clean. That proximity sensor is sensitive.
I think I found the problem.
The app management of what will show on active notification... don't active any of those that did not come checked after a reset. I did check some "Google's" for active notification.
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.
Anyone having any issues with their phone crashing/restarting quite a bit?
A few times my phone wouldn't wake from sleep, so I've had to hold down the power and volume keys. Lots of times when I go to unlock the phone, it says that can't use biometrics as it has restarted, probably in my pocket without me noticing. It's also crashed once whilst I was actually using it, opening YouTube app.
I did a full Smart Switch restore from my S7, so that might have something to do with it. What's the best way to debug this to try and work out whether it's an app causing me problems or whether there's something with the phone?
Your phone might be defective, is it lagdragon or exynos? My S8+ is exynos and I've had no such problems with it, and nobody else that i talked to that also have exynos.
Nick676 said:
Anyone having any issues with their phone crashing/restarting quite a bit?
A few times my phone wouldn't wake from sleep, so I've had to hold down the power and volume keys. Lots of times when I go to unlock the phone, it says that can't use biometrics as it has restarted, probably in my pocket without me noticing. It's also crashed once whilst I was actually using it, opening YouTube app.
I did a full Smart Switch restore from my S7, so that might have something to do with it. What's the best way to debug this to try and work out whether it's an app causing me problems or whether there's something with the phone?
Click to expand...
Click to collapse
You could try settings>apps>reset app preferences. It'll obviously wipe out some stuff but if it is related to smart switch then it might solve it. This is the sort of thing restoring backups from smart switch/helium/titanium can do, and it ends up damn hard to diagnose. If all else fails I would factory reset it and let google play download and restore as many of the apps as it can and then manually reinstall the others from play store. If it still keeps crashing after than then it is probably faulty.
I just had one random restart after i had connected to the pc to transfer some stuff over, unplugged it and next thing i hear is a beep as it was rebooting. That is only the second time i have seen a random reboot since I got it though and I am putting a certain number of reboots down to being new/having a few bugs but it shouldn't be doing it very often.
Thanks, might have to try resetting app prefences. The only thing I really care about keeping is my SMS history and my launcher setup, both of which are backed up anyways.