changed my screen phone works fine after booting. but when waking up after screen timeout there are vertical lines all over the screen. if i turn phone off and reboot it works fine again. anyone have any ideas? thanks
Related
VZW TP with Mighty ROM 6.
Hey guys, I started experiencing this weird problem yesterday. Basically, when the phone is turned on from sleep mode, whether I pushed the button to turn it back on, I get a phone call or text message, whatever...it doesn't show an image on the screen. I can see the screen itself light up (backlight or whatnot), but nothing else. Just a blank, black screen. It happens randomly. I've found that if I hold down the enter key on the d-pad, and turn the phone on, it works fine again.
Any clues, suggestions, advice?
metaGlass said:
VZW TP with Mighty ROM 6.
Hey guys, I started experiencing this weird problem yesterday. Basically, when the phone is turned on from sleep mode, whether I pushed the button to turn it back on, I get a phone call or text message, whatever...it doesn't show an image on the screen. I can see the screen itself light up (backlight or whatnot), but nothing else. Just a blank, black screen. It happens randomly. I've found that if I hold down the enter key on the d-pad, and turn the phone on, it works fine again.
Any clues, suggestions, advice?
Click to expand...
Click to collapse
You may want to try a program such as S2U2 and see if your phone will wake correctly.
This is really weird, my NS just always lights up the screen after I lock the screen.
I locked screen, the screen went black, then after a few seconds the screen turned on just like I pressed the power button.
Why this kind of thing happens? I have reboot my phone, It still the same.
As the title says the phone's screen won't turn on after I ended a longer call, i have to press the power button to get the screen working.
Did it happen to you also?I have this phone for 2 months but it never happened in the beginning, this seems to be a recent issue.
Is it a hardware issue or a software bug?I've tested the proximity sensor and it works just fine as much i can tell, it switches the screen of and on, it never happened to wake the screen during a call and to activate random keys.
Another strange thing that i noticed during a call:If have the keypad up and i lay the phone horizontally the screen won't turn off if i hover my hand over the proximity sensor but if i put the phone vertically the screen goes off or if i hide the keypad the screen also goes instantly off.
I have a single issue when the phone goes to "sleep" mode it reboots.
so i set the lock screen time out to 30 minutes, sure enough phone is stable and useable, if i set the phone down for 30 mins as soon as the screen goes dark, it will reboot
same as if i turn it on, when its on the lock screen after booting, if i dont touch it for a few seconds as soon as the screen goes dark, it will reboot. this is now my ONLY issue
is this a known issue? i cant find anything for a fix for it. help is appreciated.
I have a sprint Nexus S 4g. It recently got wet and i let it dry out for a day. The screen is slightly cracked, but before getting wet, the screen still worked properly. Currently, my phone will turn on and i can confirm this through the use of droidscreen, which displays the screen. Using adb, i can still input taps but the screen remains black. Even though the screen is black, the screen still registers touches and i can still open apps, open the notification bar, etc. I let the battery die recently. When i started charging again, it displayed the charging animation when off. I turned it on, and it did not show the boot animation, but the screen turned on at the home screen (since i do not use a lockscreen, and i mostly use this device for a hotspot). The power was at 1%, so i let it charge. When i came back to it a few minutes later, the screen no longer worked again. I have been able to recreate this and i do not know why the screen only displays at around 1%, but still registers touch at any time. Could replacing the screen fix this issue or is this a result of water damage in the circuitry?
This device is rooted and is currently on CM.