I turned off my tab (pressing the on off button) in a dark room to watch television, after a few seconds the display began to flicker every few seconds kept doing it until I turned it back on over 10 minutes. Has anyone seen this issue since the 3.2 upgrade, didn't have prior to it.
Related
How do I make WidgetLocker launch without waking the screen? Every time I press power, it turns the screen back on after about 3 seconds, then I can press it again and it stays off. Apparently this is because the Archos firmware (I have UrukDroid 1.0, same either way) turns screen on when _any_ app is launched in the background, unless it's a service.
Anyone else experiencing their 10.1 retail Tab having the screen come on randomly and stay on? Every so the screen comes on, but it's black. I can tell because of the backlighting being on. I have to reboot to make it stop.
spokenjeremy said:
Anyone else experiencing their 10.1 retail Tab having the screen come on randomly and stay on? Every so the screen comes on, but it's black. I can tell because of the backlighting being on. I have to reboot to make it stop.
Click to expand...
Click to collapse
That has something to do with background apps making it "wake" up
I think a more important problem is the Tab either turning off on its own or having the "sleep of death" even on Android 3.1. I just experienced both of these but the one that scares me more is the "sleep of death" because in order for you to turn it back on, you have to plug it into a power source, hit the power button once until the battery gauge appears then hit it again, and this time hold it down until the Galaxy Tab 10.1 logo appears. Then it boots into Android like it should. this is the first time its done it for me, and its only been two weeks since i got it.
Hopefully Samsung's upcoming TouchWiz UX update will include fixes for this and maybe a dash of Android 3.2
Yes. I have exactly the same symptoms. Every few days, my Galaxy Tab 10.1 (v3.1) will turn on the backlight (but with a black screen). Sometimes it is on battery, and other times it is being charged. Either way, I cannot wake the tablet and have to hold down the power button until it resets. Then, the first time it tries to reboot, it displays a DOS-like error message and I have to reset it again. Then typically it boots up fine. I really don't like these symptoms. Any help in fixing it would be very appreciated.
When I leave my galaxy player 5 (international) plugged during the night the screen wakes up at some point which forces me to leave it with the screen down (when I remember), I would guess that happens when the battery full notification comes up.
That anoys me specially because sometimes the screen doesn't seem to follow the screen timeout settings and stays always on. It used to happen in stock froyo and still happens in eryigit gingerbread rom.
Does that happen to anyone else? Any tips?
I have the US version and when it finishes charging the screen stays on for about 3 minutes before turning off (I actually waited to see what would happen). I think it's a bug because my default settings is a minute. Try using different timeouts to see if that solves anything.
Hello, I come from a Nokia 5800 and this behavior was common in CFWs, but I can't find anything similar on android yet.
What I mean is, android's behavior is something like this:
- 30 seconds go by and the screen dims.
- 5 seconds more and screen turns off.
- 2 seconds more and lockscreen kicks in.
- If you want to use the phone now, you must press power or home button.
In Nokia 5800, it was something like this, and what I'm looking on android:
- 30 seconds go by and screen dims.
- 5 seconds more and screen turns off.
- xx seconds more and lockscreen kicks in. Also (this is the important part!) if you tap the screen at this point while the screen is off, it turns on back again! Kinda like when its dim and you touch it and it lights up again. Same behavior but with screen off!
My question is, Is there some way to replicate this behavior on android?
Thanks.
I have a Xiaomi Redmi Note 9S which has the following behaviour: it works normally until the moment it goes under the sun, then (apparently only) the backlight of the screen is turned off and never turns on again until I restart the smartphone, where it works normally until the very moment it "detects" a bright light like under the sun, then the screen goes black. When this happens, sometimes you can still see the shape of what was on screen, but most times it only goes totally black.
When the screen is black, the telephone keeps working normally (music keeps being played, receives calls, vibration responses keep working, etc...(confirmed it using scrcpy and all is working normally)), only that the backlight is turned off and it keeps totally black. During the night, i.e. with artificial light, the telephone works normally (I was able to replicate the error using a strong flashlight above the telephone, the screen also went black the very moment I turned it on).
What I tried to resolve: restarted many times, disabled every auto brightness (also one that I think is a Xiaomi MIUI only, sunlight detector, something like this) settings that are in the configuration menu, restarted using vol up + power button. Factory reseted the smartphone. Disabled pocket mode before and after factory reset.
Any idea how to proceed? What is killing me is that it seem to be a software issue, like, why the screen don't turn on back after a while, but every time you restart it, or why the phone works all night long (i.e. there no strong light on it)?
How to capture the telephone log (logcat perhaps?) and be sure of what is the exact event that is disabling screen? Maybe I can manipulate it to prevent from happening, or to make screen goes back to normal after a while, as I work as a software developer.