Here is the senario:
This issue has rendered my phone nearly unusable, but it seems to be a software issue. Has anybody run into this one before? I haven't had 5.1.1 pushed to my handset yet, nor am I sure I want to update when I do. If it will fix this though, I'll give it a go.
Basically, to avoid losing data, I have to keep my phone awake until I finish what I'm working on. That eats the battery though (because "Note 4"). I will not be able to answer a call when this happens either, it won't even ring or show a missed call. It's like the call ust didn't happen.
I haven't figured out how to reproduce the issue consistently, it only happens when an app is open that accepts input, and something has been typed (to my recollection).
- Sompe app is open that accepts input (most readily happens when Facebook is open, but not limitied to that at all).
- Phone goes to sleep (locks screen).
- I attempt to unlock it (with my fringerprint).
- It neither unlocks, nor does it give me an error (as it typically does whenthe fingerprint is misread, etc).
- The screen goes black (regardless of what buttons are pressed, etc).
- I attempt to reacitvate the screen (with the home or the power button).
- For just a second, the screen will flash the unlocked display (usually with a crash message abut the Google App, but sometimes a message about the other app I was using).
- The lock screen displays again after < 1 second, and the loop continues.
- The only way to escape the loop at this point is to reset the device.
[*]That only works when you hit the "OK" button during the split second that it displays.
This issue has rendered my phone nearly unusable, but it seems to be a software issue. Has anybody run into this one before? I haven't had 5.1.1 pushed to my handset yet, nor am I sure I want to update when I do. If it will fix this though, I'll give it a go.
Basically, to avoid losing data, I have to keep my phone awake until I finish what I'm working on. That eats the battery though (because "Note 4"). I will not be able to answer a call when this happens either, it won't even ring or show a missed call. It's like the call ust didn't happen.
I haven't figured out how to reproduce the issue consistently, it only happens when an app is open that accepts input, and something has been typed (to my recollection).