[Q]Screen doesn't turn off when locking - Xperia Z3 Q&A, Help & Troubleshooting

Hello everyone.
I have a couple of problem with my xperia Z3. The problem is that when i press the side button to lock the phone, the phone get locked but the screen seems to be still on(and then turn completely off after a few seconds) . I mean that even if the phone is locked it's like i am seeing a completely black image. This doesn't always happens with Android KitKat but with the Lollipop upgrade i made yesterday flashing a generic Baltic firmware, the problem got worse! When it happens the screen stays on even after few seconds and it doesn't turn off and i'm forced to restart the phone to "solve" the problem. If it helps, when the phone locks fine the screen turns off immediatly but when the phone has this problem when i press the lock button i can see for a moment the screen locked, with the clock, the padlock icon, the fast dial icon and the fast camera icon ecc and then the screen turn black(but still on) like "something is slowing/blocking the phone from getting locked"
The second problem that i have is that sometimes when i make a call or recieve one when i put the phone to my ear the screen doesn't turn off and the tousch screen still works making me end the call unintentionally touching the screen with my ear for example. I haven't had this problem yet with Lollipop, but I used to have it with KitKat. Anyway this is the less important problem that i'd like to solve because even if the phone should work proprely by itself i can always accept the call and then lock the screen with the side button "solving" the problem of unintentionally ended calls. But the first problem really bothers me a lot and i'd really like to know how to solve it.
Does anyone have at least one of this two problems and knows how to solve them? Thank you !
I'm sorry for my english and i hope i've explained myself well. I've just restarted the phone so the problem at the moment doesn't persist but the next time it will happend i will make a short video to make you see exactly what happens or if you think that this two problem could be caused by an app just tell me and I will write you a list off the app that i've installed.
**Edit: I'm really sorry, i haven't read that this was the wrong section for questions, could someone move it to the right one? Thanks.

screen doesnt turn off after locked
Hi
After the upgrade, my screen also remains on, still lit after screen is locked. Pls help

I had the same problem. And got it fixed by disable and enable "adaptive brightness" .

elli said:
I had the same problem. And got it fixed by disable and enable "adaptive brightness" .
Click to expand...
Click to collapse
It worked! Thank you so much.

Related

[Q] screen wierds out

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?

Black screen & no recovery!!!!

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!!

Screen is constantly locking for no reason, is my light sensor busted?

Hi all,
When I'm using my month old Nexus 5 it will just randomly kick me back to the lock screen, sometimes I can just unlock it and keep on trucking but sometimes it will just immediately lock again or it will work for a couple of seconds and then re-lock. Once its in this state even a reboot doesn't always help and about the only thing I can do is get into recovery mode and re-flash it again. I used the Sensor Box app and have noticed that the light sensor is always reading zero, and I'm not sure if this is part of the issue?
This was happening on the PA Alpha, Stock 5.0.1 and since I was still having the issue I flashed back to 4.4.
The weird thing is that my phone had been fine for the 3 weeks or so I had it before hand. I flashed lollipop on it less than an hour after I took it out of the box and it had been running smoothly up until yesterday.
So a few questions:
Is there anything I can try to fix ir?
Can I use debugging to see what is causing the screen to lock?
Is this likely to be a hardware issue?
If it is, is there anything I will need to do to make sure I keep my warranty?
Any help is very much appreciated.
Bump with some other information:
I don't think its the light sensor, I tried using the phone in a pitch black room last night and the same thing was constantly happening, there was something else odd happening though.
From the restore of 4.4 I was on the "Select language" screen, whilst I could swipe and roll the various language options up and down the moment I presses "Next" the phone locked, if I left the phone on this screen eventually the screen would automatically lock and then it would keep locking itself constantly again.
Also, just for total clarification by "lock" I meaning "return to lock screen" not freeze up and become unresponsive.

Help - My new SM-G930W8 S7 hangs on wake

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!

Problem of waking the screen

When I make a call and hold the device to my ear, the screen goes off. And that's fine. But when I remove the device from my ear, the screen is still black. I say goodbye to the caller, and to interrupt the conversation I have to press the power button or double tapp screen to wake the screen. Is there any option to wake the screen more actively?
The same problem here....
I hope they will fix this in future updates. My friend dont have this problem. On other forum some guy told me that i need move phone and i will get phone wake up. On my other phone (s9+) i dont have this problem. This problem have many s10 series phone. I read that the problem is because proximity sensor position. And AOD dont turn off when is phone in a pocket or screen down wich use more battery.
I tried old good wipe cache in recovery and...it's good, problem is gone.
Try it too!
I try. It didn't help
Same problem as well, it doesn't happen always but often enough to annoy me...
yeah, same problem here man
same problem.. if you turn your phone upside down it will get the movement and show the screen but don't think this is actually a good workaround! does anyone know if there is something to do for it?

Categories

Resources