In the few weeks since I got the marshmallow update, I've only seen this twice, and I just wonder if it is another marshmallow bug that others might have seen?
The screen will be turned on, looking perfectly normal, but nothing will respond to touch.
I'll hit the power button to turn it off then back on, and I immediately get a dialog popup telling me the app isn't responding and asking if it should be killed. If I say kill it, everything goes back to normal. If I say "wait" everything stays frozen (but the dialog box at least responded to me saying "wait" because it goes away).
This seems to be related to waking up. It happened once when a 3rd party alarm clock app sounded an alarm to wake the phone (which usually doesn't work at all on marshmallow, but that's another bug). It happened a second time when I turned off the screen then immediately thought "Wait. I want to check something" so I turned it back on nearly instantly.
It is like sometimes it wakes up and forgets to connect the touch events to the app.
Related
I just started having this "bug" yesterday. Basically, what happens (randomly) is that when I press the power button, remove the stylus, or slide the phone open to wake it up I'll be met with a black/blank screen. The backlighting will be on, and the phone is responsive (can receive messages, make calls, sounds/notifications work), but I won't be able to use the screen. If I use the power button to turn the screen back off and wait a few seconds, the screen might start working again. This is completely random and I cannot duplicate it with any guaranteed process, but it seems to be when the phone is waking up from standby. After a soft reset, probably half of the time I'll be met with this same delima, which leads me to believe it's hardware and not completely software.
At the same time the phone is also struggling to re-paint the screen from the change of Landscape-to-Portrait and visa versa. Also opening and closing windows to get back to the today screen also cause a problem. I've disabled TF3D to see if that makes a difference, it doesn't. I have a blank today screen with no plugins to free up the system resources, and am still having this issue.
I'm using JD's Rom (probably around 1.3, it's been running fine with no issues up to this point).
I'm also using S2U2 1.35 (if that makes any difference, haven't had any problems until recently)
The phone has never been dropped, it's in InvisibleShield, and normally sits on my desk charging all day.
This started happening last night for no apparent reason and it's really starting to irratate me.
Any advice is appreciated. Thanks.
Re the black screen:
Sounds like its software related. For example, I sometimes have this if I leave PocketTwit in the foreground and turn off phone. What software did you install yesterday? Also, do you try to press the home key and see if that clears the screen?
After more testing..
After some more fiddling around with the phone I'm about 90% certain it's a hardware issue. I noticed that when I slide the keyboard out if the slide portion is past the number line then the screen will stay on, but not update. I don't know how well I can explain it. If I'm typing and hold the screen to keep it from opening all the way then I can see the letters/words appear (in txt msg/email), but if I let the screen goes and it slides all the way open then the screen will stay on and only show what has already happened, any more typed characters will not appear, but if I move the screen back to the number row then the screen will re-draw and update what has happened.
Is this something that Sprint should fix no questions asked?
lulugirl896 said:
Re the black screen:
Sounds like its software related. For example, I sometimes have this if I leave PocketTwit in the foreground and turn off phone. What software did you install yesterday? Also, do you try to press the home key and see if that clears the screen?
Click to expand...
Click to collapse
The last piece of software I installed was Gyrator 2 on Friday-ish. Thinking that it was the problem, I removed it using MemMaid. I'm going to give the phone a flash tonight and see if it is software related (hoping for the easy fix) but as the post above says, I'm almost certain it's a hardware issue. I just wish I knew how it happened. . . So much for that time putting those InvShld on.
Final Update (this can be closed)
I took it into a Sprint store and they replaced the "flip" on the top for free (I have insurance).
Point of the story/thread, this can be closed, it was a hardware issue, and now it's fixed.
I've had an odd problem with my 820 almost since getting. I'm hoping one of you geniuses have some advice.
When I turn it on it works perfectly, sometimes for hours. Then the screen goes blank, and then random pixels begin to appear, starting at the top of the screen. Outdoors rather than random pixels the screen goes almost totally green. Strangely, if part of the screen is obscured the green only covers rhe exposed area.
Pressing the on button repeatedly usually brings back the lock screen and reset (on+down) fixes the problem for another few hours.
By the way, eventhough I can't see the screen the touch sensor works. For instance I can hold theon button and then swipe downwards to turn off the phone. I can also answer and hang up using earphones.
My daughter who purchased the phone said it worked fine until the amber update. I had hoped the black update would fix the problem but no change. I found some posts from people with the same problem who sent the phone in to be fixed and got it back in the same condition. I really don't want to go through the hassle unless I expect to get it back fixed. I'd rather try fixing it myself.
My question is whether this is a firmware problem an whether it is likely that re-installing the stock black rom would do any more than the ota install that occurred automatically did (or didn't do).
Any ideas?
Nobody?
By the way it seems to happen only, or mostly when in standby.
I installed an app that displays a clock and doesn't allow the phone to go into standby mode,
and the problem doesn't appear to occur (unless I forget to leave the app on top).
I would set the phone to standby = "never" but the option isn't available on my phone, though
I understand that there are those with the standby = "never" option.
Any idea if I can set standby = "never" with keyboard commands, perhaps?
Is anybody else getting the split window feature just turning on randomly when doing something else. I can't figure out what is making it turn on, if I'm hitting the recent button accidentally or what but it tries to turn on split window randomly at times and I cannot figure out what is making it do it or how to turn it off.
Macguyver said:
Is anybody else getting the split window feature just turning on randomly when doing something else. I can't figure out what is making it turn on, if I'm hitting the recent button accidentally or what but it tries to turn on split window randomly at times and I cannot figure out what is making it do it or how to turn it off.
Click to expand...
Click to collapse
Pressing and holding the Recent button brings up the split screen option.
Maybe you are accidentally hitting the recent button with your palm while using it in your left hand.
Little update, I took it to Best Buy and the Samsung guy watched it happen, as well as the camera came on and shut off on its own. I got the phone swapped out and this one seems fine.
Also happening to me. I have the GS7 from TMobile. There is an app that some people has recomended to deactivate the split acreen feature; it works, but is not a permanent solution. Hope Samsung fix it in a software update... I hope is not a hardware issue. I don't have a cover nor a screent protector.
I went to the T-Mobile store to try to exchange it for another one. Since the issue is hard to prove (it doesn't happen every time), casually, the person that helped me at the store was the manager (who was greeting the customers that came in). After describing the problem to her, she told me that T-Mobile had received an alert in their systems about this issue and that it appears to be a hardware problem. They exchange mine for free even when I had exceeded the 14 day window.
Now this doesn't happen all the time every time, but usually around a notification and the screen is off, I go to hit a button to turn on the phone and it doesn't respond but the touch-keys are backlit. If Always-on Display is on, the screen is black regardless, not even showing the time or notifications. The only fix is waiting ~10 seconds for the phone to respond, which in some cases can be the difference between a missed call.
Now, seeing Always On Display off like that while it should be on made me think back to when I saw some sort of Nougat optimization setting that allowed me to select Always On Display, and as far as I remember, I did. That makes me think this process is killing AoD and it is taking that long to start back up, where the phone won't unlock until AoD (is back on and) can confirm that it's trying to wake up out of that state.
However, I don't believe this is the issue. I have turned off AoD and the issue still happened directly afterward, after a Messenger notification. This is stock firmware, however it is not factory firmware. I believe I downloaded it from Sam-Mobile, and they had the 7.0 Nougat upgrade that I would have gotten OTA with the factory firmware anyway.
Somehow I don't think it's the flashed firmware that is the problem, however please let me know if that's a possibility.
While the phone (or whatever) is hanging, I can still hold down the power button and I will feel haptic feedback as if the power menu has opened, and when the phone responds the power menu will be open, so the phone does still receive input. It just doesn't seem to act upon it or wake the screen properly. Is this perhaps merely a known Nougat bug or is it a glitch with my flashed stock firmware?
I'm sorry I don't have much more information. I do have Greenify, but I don't think that can or is set to disrupt anything that would affect the phone waking, or that would hang the OS, homescreen or whatever it is.
I haven't done other troubleshooting because I don't know what direction to attack this from, and that is why I have come here.
Help please!
Thanks in advance. :good:
UPDATE: It seems to happen directly after my screen shuts off from being on. So, if a notification wakes my phone but I don't interact with it in time and the screen goes off, when I press the power button it won't respond for ~10-15s. That's all I've really noticed... Anyone else have this problem??
BUMP.
Also, the same thing happens if I press the power button on my phone (by accident) and then go to turn it back on almost immediately - it won't respond for a while.
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
*Detection* said:
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
Click to expand...
Click to collapse
Won't be factory resetting unless I plan to root or something. I'll fiddle with the keep screen off setting that I do have on, and I highly doubt gestures would affect it but regardless I haven't enabled or used any. Thanks for the reply.
So the "Keep screen off" setting didn't affect anything. I turned Always On Display back on and I see the same issues. However, now sometimes I notice when I lock my screen or it shuts off, sometimes the AOD will appear and then quickly disappear, and stay in this hanging state for 10-15s. Then, if I haven't touched it during that time, the AOD will reappear. Any ideas? :/
So nobody else has this issue? This is still a problem, even if I press the power button and sometimes I'll want to turn it back on again as I just remember something to do before putting the phone away, it hangs on black for too long to be useful in that moment. The only potential solution is a factory reset?
Even if I lock the screen... If I try to turn it back on too soon, and I think it's specific timing... I have to wait 10-20 seconds. Sounds and vibrations still work.
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Kilva said:
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Click to expand...
Click to collapse
This happens for me also as a point of interest.
I am hoping that O solves it, since the monthly updates have never helped.
I haven't had this happen since upgrading to Oreo a week ago, so far so good!
Hi guys,
this morning i have a strange issue on my oneplus 7. The screen turned off, then it won't turn on again, the only thing on the screen was a little "pixel" flashing at the top center of the screen. I keept the power button pressed to turn off the phone, and after a bunch of seconds the screen turned back on (the phone was still on).
After that, i frequently see a flashing window that looks like a crash notification for some app, but it is so fast that i can not read what is related on... This window keeps popping out every few minutes (or seconds) but the phone seems working as alwatys. I've tried rebooting with no luck. There's no way to see some kind of log to check what app is crashing? The phone is consuming a lot of battery now (30% in the last 2h) and looks like Google Play Services has used almost 25% of battery.