My Mi5 is facing a weird issue. Have jotted down all details below. Has anyone else faced this issue? What is the fix? Please help!
1. The phone works fine as long as the screen is on. It does not hang or face any issues.
2. After locking the phone, the screen does not come on (this happens sometimes not always). It always happens when I leave the phone un-touched for a while. The phone remains on (I can hear the lock sounds, phone ringing and also see the keypad lights) however the screen does not come on. I need to wait for a long time for it to work after multiple presses of the unlock button or I need to restart the phone.
3. I do not think it is a screen issue because it works when on. I think it is the 'sleep of death' issue.
4. I have reset the phone. I have re-loaded the global MiUI 8 ROM and also tried loading the developer rom. I have not rooted the phone so far. Happy to do it if needed.
5. The issue does not happen if I have the music player on and lock the screen. It tends to happen only when the phone goes totally to sleep with no applications using it in the background.
Please let me know what I can do to fix the issue.
Thanks.
Related
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.
Over this past week the back light for my Nexus S 4G appears to randomly shut off. Right now it has happened about 5 times and when I need to use it right then, preventing me from just stopping to investigate what may be causing this. The screen still comes on allowing me to quickly unlock using the pattern and then restart by holding down the power button. The one time I was able to investigate a little I was navigating into the settings menu when the screen just went blank. I pressed the power button a few times and could see the hardware buttons below lighting up as if the screen was on but that was it.
I'm currently running Slim Bean (Android 4.2.1) Beta and will be trying another rom but wanted to see if anyone else may have encountered this issue before I bring it up with that thread.
Yeah experienced this too in most 4.2 ROMs that I've tried. Some people say it's a bug with the auto- brightness settings but I don't buy it since I don't really use auto-brightness but still get the error. I'm back to 4.1.2
Glad to hear. I was becoming worried I had some hardware that was failing.
I will turn auto brightness off and see how it goes.
Thank you
So it has happened quite a bit since my last post. Even with auto-brightness turned off. I'm blaming this bug for my alarm not continuing after I snoozed it a few times. (I know they are unrelated but its just really annoying).
It happened again about ten minutes ago and I managed to output a bug report feature on 4.2.1. Not sure if it is of any use to anyone. Message me if you would like it.
The problem is like this:
SOMETIMES when I call someone, the screen turns off without approaching the phone to my ear. The screen is not turning off by pressing the power button or the volume buttons (I enabled using GravityBox to turn on the screen using the volume keys).
After I end up the call, after a couple of seconds, the phone comes back to normal.
Once again, this behavior appears just SOMETIMES! Usually I don't have this problem!
Any ideas to how so solve this problem?
peslap said:
The problem is like this:
SOMETIMES when I call someone, the screen turns off without approaching the phone to my ear. The screen is not turning off by pressing the power button or the volume buttons (I enabled using GravityBox to turn on the screen using the volume keys).
After I end up the call, after a couple of seconds, the phone comes back to normal.
Once again, this behavior appears just SOMETIMES! Usually I don't have this problem!
Any ideas to how so solve this problem?
Click to expand...
Click to collapse
I wouldn't worry too much about it, its just a glitch, it happens to me sometimes too , when i put it on speaker and i get close to the phone , the screen turns off and it comes back after a while. it doesn't bother me too much. It might be that the sensor is too sensitive. Have you tried a custom rom ?
This issue happens to my son's phone too.
Anyway, it shouldn't be random, please double check if it happens ALWAYS after a phone reboot, this is the behaviour of mine
I want the moderator to ban me.
display issue
Hello,
I have started to face the same issue mentioned above.
On googling I came across the motorola forum (google search: Moto G Proximity Sensor Software Issue)
It seems the issue is being discussed there and apparently they need more moto g users with this issue to help them out solve this.
On using z device i noticed the proximity sensor value stuck at 3 with no change covered/not covered (sensor) [Phone running without restart for 6+ hours]
After restarting the phone the sensor value in z device changes. 100 (uncovered) to 3 when covered.
I will keep checking this every few hours to see when does the proximity sensor stop working without restarting the phone. (uptime)
Can the DEV's here help us out? looks like Motorola may take some time in finding a solution to this issue.
This seems to have went away with 4.4.3 and the new Dialer app.
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.
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.