The screen of my OPO went blank, but I believe the phone is still working as it gets notifications, the torch comes on with the "V" from the standby screen, phone wakes from a double tap and the phone rings when called from another phone. But the screen is completely blank, so I cannot reset it because I do not know where to touch the screen.
I have entered a repair ticket with OPO support but they are advertising a wait of at least ten days before any response and I have tried, but cannot hold my breath quite that long. Any help would be greatly appreciated.
Same problem over here, have been using phone for few months without any problems, very carefull with my phone, no drops, moist or whatever, but suddenly this strange blank screen starts to occu. Backlight buttons come on and vibrate but screen stays blank.
I can however reboot my phone by holding the power button until it vibrates, phone will work ok ..... until it happens again.
Try clean flashing whatever ROM you're on and go from there
I think it's referred to as "SOD" which stands for "screen of death" maybe? Or darkness? Lol I dunno search for sod
Sent From Lollipopified Bacon Goodness!
look at my post one the oneplus forum, i'm pretty sure this must be some sort of a software issue
https://forums.oneplus.net/threads/bug-screen-not-turning-on.78141/page-4
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.
The other day, I hit the power button on my touch pro, and the screen didn't come on. I did a soft reset, and it started working again. Now today, the same thing is happening, but a soft reset isn't helping.
The screen's back light comes on, the LEDs on the buttons come on, and the phone seems to be working fine. I hear all the sounds, including the HTC sound while it is booting, and the new message sound, but the screen stays black. It still recognizes touches, it just doesn't show an image. I want to do a hard reset, and will if I can get it to come one one more time, but its been about a month since I backed up my contact list. Lesson learnt there. I'm afraid it might be a hardware problem since I don't see anything while its booting either.
Anyone know if this is a known hardware issue with the touch pro? The phone is less then 3 months old, and I've been real careful with it. I haven't dropped it from more then 2 feet, and even that was onto carpet. Its the Verizon version if that makes a difference, and I'm running one of the NFSFAN roms. Its not the newest one, but rather the one posted on October 19th. I doubt its the rom, though, as I've been using it for around 2 months with no issues.
EDIT: Ok, I went into the bootloader to see if it was hardware of software. I figured if it was hardware, the screen would be black, and if it was software, it would be the rainbow. Sure enough, the screen stayed black. Hit the reset button, and the screen actually came on! Go figure. Went to do a backup, and the screen literally crapped out on me while I was watching it. Definitely a hardware problem.
similar with Touch HD... kinda
I've been having a similar problem with my Touch HD. The problem is very intermittent though and is sometimes hard to reproduce. The screen and phone will be working fine then once in a while when I push the power button to lock the phone, I'll unlock it and the screen stays black. I know that the phone is still on and even unlocked because pushing the buttons at the bottom makes the phone vibrate. The only consistency in reproducing the problem happens after I do something major on the phone such as making a phone call, browsing the internet, sometimes charging the phone. Other than that, I can sit here and push the power button all day and it'll come on and off with no problems. When the screen does go black I've taken the battery out repeatedly as well as repeatedly rebooted the phone until it comes back on. I've tried doing hard and soft resets to no avail. I've tried deactivating "turn off backlight if device is not used for" and "turn off device if not used for" without any resolve. After this I've even left the screen on (disabled backlight off) to see if it flickers or shows any sign of being faulty and it seems to be fine. I'm currently on Dutty's HD WM 6.5 Leo R5 WWE rom, but this has happened with two other roms (NRG, LIA). Other info include:
OS: 5.2.23016
Manila: 2.519192828.0
Radio: 1.14.25.24
Protocol: 52.64.25.34H
I guess the only consistent software has been my radio. Please help! Any advice would be awesome. I've tried google search and xda search without much help. Thanks
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?
Hi all !!! Sorry for my English but I need your help
I commented what is happening with my phone N5 (which for good and evil is always stock without root or anything, with corresponding OTA updates.)
1- Yesterday afternoon at lunchtime while reading a book in playbooks, I notice that suddenly disappears one line and then appeared intermittently. I close the app and noticed the same thing happening on the screen menu. I shut down the cell and turn on again and I thought it must be an application be kidding. But still does.
2 Also yesterday I happened to change the security on the phone screen. After a while of normal operation, try to turn it on the screen with the button, nothing, the screen goes "black", with light and retrolight turned on but no picture no nothing .
Called the cell to see if it works or is turned off and the phone rings but the screen nothing. Try turning it off and on again by holding the on / off / lock button and the phone restarts, but the screen nothing. In one such attempt to do the above it is seen that managed to turn it off. And I get it on and do a normal boot, except that the picture of my screen is changed to the original. Change the lock screen which was previously using (slip). And it seemed that out or some conflict with the lock. In one of those again pressed the ON / OFF / lock as would normally and it starts all over again.
After I magically back to life, I want to make a full wipe as I think it should be an app that is doing some conflict or something. BUT ....
3I turn off the phone and then press the keys VOLUME UP / DOWN and ON / OFF is normally off, squeezed the first screen with the options but options RECOVERY / BOOTLOADER appears in red I choose RECOVERY give the ok with the key and .... andriod robot appears with the legend below that says something (I do not remember well) without or without controls options appears. So its seems thatI dont have recovery.
After that keep pressing the key ON / OFF and the phone turns off and / or reboot normally. All this I did it again to see if the error reappears and looks that I do not have recovery.
The failure of the screen is increasing. I dont know if they are separate problems or is it all the same problem.
Sorry if I was too long but I need the help of you.
UPDATE Now it seems that the screen died, since I do not achieve to turn it on as before, the light and the retrolight its ok. The phone receives calls and notifications but the screen stills black.
Thanks all.
Matias M 73
the android laying on its back IS the atock recovery.
simms22 said:
the android laying on its back IS the atock recovery.
Click to expand...
Click to collapse
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Matias M 73 said:
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Click to expand...
Click to collapse
sometimes things just "derp". itll happen more often if you dont reboot your phone often. also, your phone will be a little bit more responsive if it gets reboot once a day or two.
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
republicano said:
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
Click to expand...
Click to collapse
Thank you Republicano!!
I think too that its a hardware issue. I already see on you tube problems like mine.
Thanks again!!
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!