[Q] bug black screen - ONE Q&A, Help & Troubleshooting

Hi,
I have android 4.4.4 with cyanogenmod 11.0 (multirom) installed on my oneplus one:
Regularly, I have the bug that my screen goes 'down' = black screen.
If I push on the power button, it appears again for 1 second, but then it goes away again.
Sometimes, I have to repeat this 10 times and then it is OK again for an hour and then again the same problems.
Very annoying !
Same when trying to unlock, I got my unlocked screen, but then it turns black again,
got to press on power button, I have the unlocked screen for 1 second and goes black again.
I guessed it had something to do with my security locking interval, but after setting it to 10 minutes, I still got the same issues?
Anyone the same problem?

same here
Hi miss.artemis,
I'm also experiencing the same problem. Neither the locking interval setting nor the sleep mode interval setting are doing any good.
This doesn't happen all the time, but is very annoying when it does. I couldn't watch an episode of TV show for more than 10 minutes before the bug occurred.
Have you by any chance found solution since you reported the problem? Could anyone else help us?
Thanks,
Alldorin

I had the same isssue after trying CM12 nightly. Reseting my device sto stock solved that issue

Wafflez_SE said:
I had the same isssue after trying CM12 nightly. Reseting my device sto stock solved that issue
Click to expand...
Click to collapse
That should do ! Thanks =)

Related

[Q] Problem: Screen keeps lighting up when in standby, happens on different ROMs

Hi all,
I have a problem: when in standy, my TF101's screen keeps always lighting up for about 1 second and goes off again. When it is off again and I then press the power button, the screen doensn't light immediately. (delay of 1-2 seconds or nothing at all)
It happens on different ROMs.
Doesn't matter if in plane mode (perhaps an application connected via the internet is doing it) or not.
Anyone has/had the same problem or a solution? Perhaps some stupig app is causing this? It's slowly draining my battery when in standby and I would like to get rid of it.
Thanks in advance!
Try flashing guevor's kernel latest version if you havn't already, fixes many issues with sleep. http://forum.xda-developers.com/showthread.php?t=1565519&page=151
This started happening AFTER receiving a damaged unit back from ASUS. Then the random reboots started soon after that.

[Q] Trouble with screen

Hello, I've been running MOAR 6.1 for few days and since yesturday when i tried to shut the screen to off mode the screen won't close and the power off reboot screen appears, it also turns on and off few times on it's own and it interrups with the popup of power off reboot screen continously, i thought maybe it was the rom so i changed to different rom but it wasn't the rom. i'm kinda puzzled and i just can't get this problem solved. anyone with similar issues or someone who knows what this issue is please help.. it's driving me crazy everytime i try to use the phone.

[Q] Note 10.1 Wake up bug

Hello everybody , from time to time my moms Note 10.1 (N8000) refuses to wake up from sleep , it doesn't happen too frequently , but it does require a forced reboot , is it a known bug or is there any fix ?
BTW , its running completely stock 4.1.2 .
iamezio said:
Hello everybody , from time to time my moms Note 10.1 (N8000) refuses to wake up from sleep , it doesn't happen too frequently , but it does require a forced reboot , is it a known bug or is there any fix ?
BTW , its running completely stock 4.1.2 .
Click to expand...
Click to collapse
Look up android sleep of death. I had on previous devices but not the note 13
I actually think it does wake up just not turning on the screen , i can hear the volume changing , and the device going to mute mode , but screen is off .
or maybe i am wrong and its normal to change the volume with the screen is off on samsung devices?
iamezio said:
I actually think it does wake up just not turning on the screen , i can hear the volume changing , and the device going to mute mode , but screen is off .
or maybe i am wrong and its normal to change the volume with the screen is off on samsung devices?
Click to expand...
Click to collapse
It isn't normal no, the only button that should work with the screen off is the screen on button. I'd start by looking into what shaun suggested above and if you find no fix, maybe just try a factory format? (back your data up first).
I get a slightly similar issue on mine but I got the bug when I flashed Hyperdrive Rom, my screen occasionally "goes off" but it's not really off, I can see the back light still. I just have to screen off/screen on and I'm fixed. Your issue sounds different though because you need forced reboot.
Hope you get it fixed, Good luck!
stickfinger said:
It isn't normal no, the only button that should work with the screen off is the screen on button. I'd start by looking into what shaun suggested above and if you find no fix, maybe just try a factory format? (back your data up first).
I get a slightly similar issue on mine but I got the bug when I flashed Hyperdrive Rom, my screen occasionally "goes off" but it's not really off, I can see the back light still. I just have to screen off/screen on and I'm fixed. Your issue sounds different though because you need forced reboot.
Hope you get it fixed, Good luck!
Click to expand...
Click to collapse
did OP ever get this resolved? I am having the exact same problem with the 10.1 2014. Screen goes to sleep, but when pressing power, or opening the book cover, the backlight does not turn back on. You can see the image on the LCD in the light and hear screen presses, or volume adjustments.
Tried factory reset, and Odin'd a fresh rom.. No go
Serinety said:
did OP ever get this resolved? I am having the exact same problem with the 10.1 2014. Screen goes to sleep, but when pressing power, or opening the book cover, the backlight does not turn back on. You can see the image on the LCD in the light and hear screen presses, or volume adjustments.
Tried factory reset, and Odin'd a fresh rom.. No go
Click to expand...
Click to collapse
I got rid of my bug by turning off airview in the pen settings, ive been stable since then. Wouldnt harm trying it?
Serinety said:
did OP ever get this resolved? I am having the exact same problem with the 10.1 2014. Screen goes to sleep, but when pressing power, or opening the book cover, the backlight does not turn back on. You can see the image on the LCD in the light and hear screen presses, or volume adjustments.
Tried factory reset, and Odin'd a fresh rom.. No go
Click to expand...
Click to collapse
I am on stock rom and never rooted. Mine started doing the exact same thing. You can see it on in the light. Factory reset didn't fix.
Hi,
I have a quite similar problem. It started with a charging problem so I thought changing the cable would solve the problem but no. My charging is kow ok, but each morning after a long charging night, my note n8010 with stock android gets SSSSSSLLLLOOOOOWWWW . Black screen, then slowly wakes up, but need 10sec to unlock screen and unusable... I have to force reboot too.
It seems like it doesnt want to wake up, like extreme energy saving mode... ?! No solution actually found for me
The only fix for me is flashing Boefla kernel

Random screen crashes, freezes, glitches

Hello! I have a stock Android Lollipop 5.0.1 Nexus 5 and for the past week or so I have been experiencing a weird issue.
The device randomly crashes. By "crashes" I mean the screen goes black, but the backlight is still on (it's a lighted black). I can push the power button and it will turn completely black (locked) and if I push it once more it turns lighted black again.
To get the device back into usable state I have to keep the power button pressed until the phone resets. Sometimes I keep it pushed for a full minute and nothing happens, sometimes 10 seconds are enough. Sometimes it will go through the "Google" logo and then stay in the lighted black state until I finally manage to reboot it again. Sometimes it crashes again right after it boots up.
It's weird because a lot of the times it's ok throughout the day and then when I go out in the evening, I take it out of the pocket and I see it crashed. Sometimes it crashes while I actually use it.
Last night it started doing something else: instead of lighted black, the screen is filled with static noise. It doesn't move or anything, it's a still image. Today, when a crash like that occurred, the screen glitched first (random lines on the screen, some parts got moved, really weird). I will get some photos if it happens again.
The problem is that I can't identify what's causing it. There is no particular app or action that I do / use that triggers this. It also doesn't seem to be movement-based, as it sometimes happens while it's sitting still on a table.
I updated to 5.0.1 about a day before this started happening, but I'm still not sure if it's software or hardware-based.
I tried a factory reset and booting into safe mode, none of these helped. I will only consider flashing a custom ROM as a final resort, because I'm not sure if it voids the warranty.
PS: the device is still under warranty, but I'm away for the holidays and will be until the beginning of the next year. And I'd like to have a usable device, especially while I'll be on the road.
Smith_S9 said:
Hello! I have a stock Android Lollipop 5.0.1 Nexus 5 and for the past week or so I have been experiencing a weird issue.
The device randomly crashes. By "crashes" I mean the screen goes black, but the backlight is still on (it's a lighted black). I can push the power button and it will turn completely black (locked) and if I push it once more it turns lighted black again.
To get the device back into usable state I have to keep the power button pressed until the phone resets. Sometimes I keep it pushed for a full minute and nothing happens, sometimes 10 seconds are enough. Sometimes it will go through the "Google" logo and then stay in the lighted black state until I finally manage to reboot it again. Sometimes it crashes again right after it boots up.
It's weird because a lot of the times it's ok throughout the day and then when I go out in the evening, I take it out of the pocket and I see it crashed. Sometimes it crashes while I actually use it.
Last night it started doing something else: instead of lighted black, the screen is filled with static noise. It doesn't move or anything, it's a still image. Today, when a crash like that occurred, the screen glitched first (random lines on the screen, some parts got moved, really weird). I will get some photos if it happens again.
The problem is that I can't identify what's causing it. There is no particular app or action that I do / use that triggers this. It also doesn't seem to be movement-based, as it sometimes happens while it's sitting still on a table.
I updated to 5.0.1 about a day before this started happening, but I'm still not sure if it's software or hardware-based.
I tried a factory reset and booting into safe mode, none of these helped. I will only consider flashing a custom ROM as a final resort, because I'm not sure if it voids the warranty.
PS: the device is still under warranty, but I'm away for the holidays and will be until the beginning of the next year. And I'd like to have a usable device, especially while I'll be on the road.
Click to expand...
Click to collapse
I have none of your issues, try booting the device in safe mode and see if the problems still occure. It must be a or multiple downloaded apps that are causing your issues. Or try a data factory reset and restore/download your apps one by one amd try to identify the culpritt.
gee2012 said:
I have none of your issues, try booting the device in safe mode and see if the problems still occure. It must be a or multiple downloaded apps that are causing your issues. Or try a data factory reset and restore/download your apps one by one amd try to identify the culpritt.
Click to expand...
Click to collapse
I said in the post that I tried both of those things. The crash occurred seconds after booting in safe mode and factory reset did not help either.
Smith_S9 said:
I said in the post that I tried both of those things. The crash occurred seconds after booting in safe mode and factory reset did not help either.
Click to expand...
Click to collapse
Flashing the 5.0.1 factory image in fastboot should fix your issues. Or try flashing system.img first, maybe thats enough.
Same issues with my Nexus 5
gee2012 said:
Flashing the 5.0.1 factory image in fastboot should fix your issues. Or try flashing system.img first, maybe thats enough.
Click to expand...
Click to collapse
I am experiencing SAME exactly issues in my N5 with 5.01 and 5.1 . EXACTLY... you are not alone
Seems a software problem (third party app ?) , started in 5.01 and now is in 5.1 , of course system and boot images where flashed with fastboot, so no solution using
Stock, Rooted, using Nova Launcher - Smartwatch 2 - Google Cardboard - Chromecast and many apps.
But started ..if memory helps .. after installing Cardboard 3D apps.
reimer1 said:
I am experiencing SAME exactly issues in my N5 with 5.01 and 5.1 . EXACTLY... you are not alone
Seems a software problem (third party app ?) , started in 5.01 and now is in 5.1 , of course system and boot images where flashed with fastboot, so no solution using
Stock, Rooted, using Nova Launcher - Smartwatch 2 - Google Cardboard - Chromecast and many apps.
But started ..if memory helps .. after installing Cardboard 3D apps.
Click to expand...
Click to collapse
My phone had an issue with the screen. I went to the LG service and they replaced the screen entirely, so that's that.
again and again...
i'm in the same case... I don't have any clues or solutions, i'm just wainting like a dumb... I don't know what to do, i always have to make the thing with the power button and the lower sound button to make it show the boot screen, but it glitch after few seconds... PLS HALP

[Q] n5 turns off after screen goes off second time

This is a weird one. The phone works fine with one caveat. The second time the screen turns off and goes to black, the phone turns off. Pressing the button turns the phone on. It is very frustrating. Yes the os is the latest release.
Just an FYI for anyone who cares or has the same issue. I tried installing a new OS (CM12) and a new kernel (a couple of them). The issue persists, the problem is not solved. Any advice would be welcome.
its happenning to me too

Categories

Resources