So I'm using Stock Android 5.0.1 Nexus 5.
The problem is my lockscreen never turns itself off.
So the phone goes to sleep from any normal screen after 1 min (as per settings).
This turns the display off and everything is fine.
But if I manually get the lockscreen up by pressing the power button or by plugging in a charger the lockscreen will stay on forever. I think its supposed to turn off after 10 - 15 sec or so but it doesnt do that anymore.
So every time I plug in a charger I have to make sure I turn the display off again.
I'm not sure when it started. I have dev options enabled on the phone but I never found any setting to fix this anywhere.
Edit: Reboot fixed it for now but I'm pretty sure its recurring. Well with luck its not.
Reboot
Related
I noticed that if i leave the screen on (with gravitybox) for a mid-long period, e.g. 30/60 min, the display will start flickering (or jumping) and the oscillation will increase with time. The only solution is to turn off the phone and let it rest for some time then power it on. Do you know why?
Arathon said:
I noticed that if i leave the screen on (with gravitybox) for a mid-long period, e.g. 30/60 min, the display will start flickering (or jumping) and the oscillation will increase with time. The only solution is to turn off the phone and let it rest for some time then power it on. Do you know why?
Click to expand...
Click to collapse
I am not sure if mine is related, but today my Nexus 5's screen flickered then went black. I can feel the phone vibrate when holding the power button down. But still nothing, tried plugging into computer and after unplugging I hear the low power chime. So I know that it is working aside from the screen staying black.
The phone is running 4.4.3 stock that I flashed via twrp, with faux123 18u kernel, exposed installer, gravity box. This could all be coincidence, and I could just have a bad screen. But does anyone have any suggestions?
Lately my Nexus 5 (running CM11) will occasionally turn allow me to turn the screen on, and the notification LED will start slowly flashing a whitish-blue color.
It even seems to resist me trying to reset it, as I'll hold the power button down for 30 seconds at a time and it won't reboot. After doing this 5 or 6 times eventually it'll reboot and then act fine.
Does anyone have any experience with this type of behavior or know something to try? It's been happening for a few weeks now so I'm not sure if it started with the latest M-build or is unrelated.
Thanks,
Bish
Hello,
I flashed the latest LRX22C image on my nexus 5 today.Had flashed it clean,wiping data,cache and system etc except the Internal Storage.Then I flashed the SUPERSU 2.37 ZIP .Everything was fine for about 4 hours.Then suddenly when I pressed the power button to turn the screen off,it was not turning off and the "Switch off" mode was popping up instead .Then, when I got a call,it switched off.The phone won't turn on again.It starts,the Google Boot Splash appears and the bootanimation starts for like 2 seconds and it switches off.Same thing for bootloader mode.
Please Help me!
EDIT: Now its turning on by itself and switches off in 2 seconds!
Sounds like a bad power switch to me, but of course that is just my opinion. :good:
sounds like a mech issue.
legit isue
I have the same problem on mine now... Basically my phone powered down around 45%. Battery. At the time i thought it was dead... But it wasnt. When i would plug into external power, either usb or through wireless charging it would power cycle continuously at the android splash screen.... (1 to 2 second intervals - even if i booted into fastboot) Interestingly it would never go to the battery charging mode. But automatically boot on charge... It did this for about 6 hours then i gave up and left it unplugged for a day. I plugged it back in and it started power cycling again, however this time on its third boot it came back to life . thats when i discovered i still had 40% battery... I dont know what exactly made it boot but it did. Oddly also on boot, it started optimising apps and finishing install again. I checked the md5 before I installed the update so no issue there. Since it powered up i have powered the phone off using the power button long push and let the phone power down. After doing this when i plug the phone in to usb charge it goes to the charge screen. No issue. That said, if i try to power up while tethered and charging it will not allow it. It just stays at the charge screen. As soon as i unplug the usb the power button allows the phone to power up and work... When booted up it charges as normal when plugged in. Im convinced there is an issue with the power management drivers or drivers for the button controls. My phone worked fine until the 5.0.1 update was installed. On my nexus 5. Anyone else or just us two? Ive had a hard time finding people posting on this issue.
I've had the U11 for several months and everything is and has been great with it. Today, however, several things just stopped working. I first noticed the fingerprint scanner not working, then I noticed that the power button doesn't turn the screen off. The power button works, I can hold it down and the power menu appears.
I adjusted the screen timeout to 15 seconds and rather than the screen shutting off, it merely dims as though I've turned the brightness all the way down.
The phone is completely stock, but I did unlock OEM Bootloader in developer options.
I went into recovery and wiped the cache to no change. The screen won't shut off and the fingerprint scanner does not register anything. Everything else on the phone appears to work fine. Has anyone else had this issue?
The same night, I ran the battery all the way down and let it sit depleted all night. Charged it to 100% and everything started working again.
Hi there
I've got a problem with this device.
If it is charged to 100% everything works well, the power connector is working also.
When i need to charge it, the device flips on and stays on after 5 seconds when i set it on standby, it wont go 'to sleep' after that, it's always on
I've restored to factory settings, but with the same result.
I really dont know what could be a fix??