Hi,
I encountered the same problem recently with ICS based roms: after I activate the Developer options / Stay awake option, the lockscreen just goes AWOL. No matter what I do afterwards (reboot, clearing the dalvik cache, unchecking this option), the lockscreen just does not come back. When I press the power button, the screen goes off but the phone is not locked. Any advice on this?
Is it everytime or just when you have recently locked it? Maybe u have got your android timeout function put too high or when you have Cm you put a tick at the Cm settings the part for tablets where you can switch your whole lockscreen off
If its every time then its possibly because the wakelock "keep awake" places may prevent lockscreen from activating as the screen isn't "turned off" as such.
Then turn off the things that prevent it from going to sleep mode
Related
Hi,
I'm using a Galaxy S running a froyo custom ROM.
I was wondering whether there is a way to disable the "auto lock" feature of the phone?
The display can still shutdown based on the selected screen time-out time, however, the phone should stay without getting auto locked, unless its explicitly locked.
Ideally, it should be like in the Nokia 5800, where the screen switches off after the given number of seconds, however the phone stays unlocked (unless its locked using the hardware button) and the display comes on when the screen is tapped/touched.....
Is there any way something similar could be done with Android?
Thanks in advance,
Look for an app in the market called No Lock. One click on the app toggles the auto-lock on/off and it's auto-loaded every time the phone boots up. Couldn't be easier simpler.
Thanks for the reply.
Actually, I'm using "no lock" at the moment.... What I'm ideally looking for is a way to bring the screen alive just by tapping on the screen. Even eith "no lock" still you need to press one of the hardware buttons to awaken the screen....
Maybe this is not possible in Android ?
I don't think it is...
But even if it was possible, why would you want it? It'd get triggered so often any time you brushed up against it, wasting battery and launching apps while in your pocket or something.
try Extended control
I also need an app or a tweak or something that let me set the screen timeout, withOUT autolocking, but also withOUT disabling the lockscreen, so when I press the side buttons the phone locks.
I've been searching for days with no luck. Any help, please?
I've recently picked up my new Infinity and I've noticed that after the screen times out (I've set it to 30 seconds), it won't turn back on after I press the power button. Sometimes I have to press it numerous times before it will show the lock screen; other times, I've had to press the outer button down to reboot it.
Is anyone else having this issue or know what the issue is?
I have "same" problem and is driving me crazy. Did a cold boot, did a factory reset (through cold boot and through OS) - didn't help.
When my pad is in a locked/sleep state for longer time, it doesn't wake up anymore. It is draining battery as a sponge, but doesn't receive e-mails etc...so it could be it freezes or the wifi is off.
This problem is usually reported with a fact that one has enabled to turn off wifi when in sleep state (prime forums)...
My case:
- i had set wifi to never sleep
- i fiddled with build.prop and i think only after that the problem emerged (i mention this because there is a setting about sleep/wifi thing)
- i have restored orginial build.prop
- i have tried to set wifi to turn off in sleep
- i switched back to never sleep
- i coold boot, factory reset
Nothing helps anymore.
It is better with the Power Fx widget i think.
It happens less regulary, but it still does and I also don't know what else to do.
Some are reporting there is a bug in 4.0.3 ICS - but i don't know.
I think this is not a HW issue, and i refuse to do so
Hopefully JB update will solve this, too.
BTW: as i mentioned in my other topic on this matter, i am pretty surprised that factory reset didn't change my bootanimation and some other stuff on the system folder. Because of this fact i think factory reset will not help with this problem as it seems it leaves some things intact, which could also mean that if there is something wrong with SW it just doesn't overwrite/change it and that's why the problem is still here (broken file, changed file, cache...i don't know).
If this problem persist for a week or so and if there is still no JB update i will probably just go and install the latest update manually, which i think should overwrite all files. But, not sure.
Please if anyone has any idea on what is going on....
I have this same issue. It usually occurs after long periods of being idle and I pick it up to use it, hit the power button to wake it up, and it just doesn't wake up.
I have to hold the power button + vol down button to restart it.
Sometimes it'll happen when I just put it to sleep too or after short idle periods.
It's somewhat embarrassing when in public using it and randomly have to reboot; it also did it once when I was in class taking notes, thankfully SuperNote saves as I go.
Any ideas what the cause is? I'm only rooted, no custom recoveries, ROMs, kernels, etc. I'm running the stock ROM .26
Hi everyone,
I have a problem with LRX21O on my Nexus 5 32 GB. I installed it on day one and everything went fine. I was able to press the power button to get to the lockscreen then either swipe right to phone, left to camera, or up to unlock, or just leave it alone to re-lock after checking my notifications.
I then turned on a PIN lock under security and played with it a bit to see if it could use my FitBit One as a Smart Unlock device (no dice because it doesn't do a bluetooth pairing, it just syncs). So... I turned the PIN back off.
I now have no lockscreen. Pressing 'power' just sends me straight to whatever was happening when the screen turned off. I've tried turning various screen lock methods on and off and goofing with it that way, but I can't get a password-free lockscreen to show up again! ARGH!
EDIT: NEVER MIND I'M AN IDIOT
I had been chosing 'none' instead of 'swipe' because I went to a list called security->screen lock and was figuring it was a "security" setting (swiping does not equal security). I somehow did not see Swipe even though I looked at the screen with Swipe on it like 47 times.
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!
Basically this, every 3 or 4 days or so my OnePlus screen will go dark. It isn't *crashing*, though - it's happened when I've had headphones in listening to music and the music still plays, responds to headset controls, etc., so I think it's just the screen. Normal reboot will not work (holding the power button), although this might be because that presents a reboot menu rather than just rebooting the device. I have to do power button + volume up to reboot the device, at which point it reboots and everything is back to normal. I'm happy to gather any addition logs/data needed to debug, but I can't find anything in my crash debugging app (because it's not a crash...). Other interesting pieces of info
- I get the "Intent Verification Service stopped responding" issue every reboot
- I originally installed by wiping OOS + Android 12 and trying to install 19.1 and 19.1 recovery; this failed (same problem as here: https://forum.xda-developers.com/t/denying-ota-because-it-is-a-spl-downgrade.4463975/), so I installed 18 instead, which failed, but then wiping and going back to 19 succeeded (because the update was newer and thus no longer a "downgrade", I presume. IDK what really happened there).
- Trying to do Android Beam hard crashes the whole device; I've disabled NFC for now
Other than that the build runs swimmingly. I can live with the other stuff but the screen shutting off randomly is worrying to me - anything I can do to fix this or help you guys help me fix it?
hyve9 said:
Basically this, every 3 or 4 days or so my OnePlus screen will go dark. It isn't *crashing*, though - it's happened when I've had headphones in listening to music and the music still plays, responds to headset controls, etc., so I think it's just the screen. Normal reboot will not work (holding the power button), although this might be because that presents a reboot menu rather than just rebooting the device. I have to do power button + volume up to reboot the device, at which point it reboots and everything is back to normal. I'm happy to gather any addition logs/data needed to debug, but I can't find anything in my crash debugging app (because it's not a crash...). Other interesting pieces of info
- I get the "Intent Verification Service stopped responding" issue every reboot
- I originally installed by wiping OOS + Android 12 and trying to install 19.1 and 19.1 recovery; this failed (same problem as here: https://forum.xda-developers.com/t/denying-ota-because-it-is-a-spl-downgrade.4463975/), so I installed 18 instead, which failed, but then wiping and going back to 19 succeeded (because the update was newer and thus no longer a "downgrade", I presume. IDK what really happened there).
- Trying to do Android Beam hard crashes the whole device; I've disabled NFC for now
Other than that the build runs swimmingly. I can live with the other stuff but the screen shutting off randomly is worrying to me - anything I can do to fix this or help you guys help me fix it?
Click to expand...
Click to collapse
Go into display settings at the bottom and turn off pocket mode.
mattie_49 said:
Go into display settings at the bottom and turn off pocket mode.
Click to expand...
Click to collapse
I don't see anything that says "pocket mode", here are my settings:
Brightness
Brightness level
Adaptive Brightness
Lock Display
Lock screen
Screen timeout
Appearance
Dark theme
Font
Font Size
Display size
Icon Shape
Color
Night Light
LiveDisplay
Colors
Other display controls
Rotation Settings
Display white balance
Smooth display
Full screen apps
Screen saver
Tap to wake
Prevent accidental wake-up
Tap to sleep
Wake on plug
All the "tap to <blank>" settings are on.
hyve9 said:
I don't see anything that says "pocket mode", here are my settings:
Brightness
Brightness level
Adaptive Brightness
Lock Display
Lock screen
Screen timeout
Appearance
Dark theme
Font
Font Size
Display size
Icon Shape
Color
Night Light
LiveDisplay
Colors
Other display controls
Rotation Settings
Display white balance
Smooth display
Full screen apps
Screen saver
Tap to wake
Prevent accidental wake-up
Tap to sleep
Wake on plug
All the "tap to <blank>" settings are on.
Click to expand...
Click to collapse
Prevent accidental wake-up
mattie_49 said:
Prevent accidental wake-up
Click to expand...
Click to collapse
This setting has been turned on, I'll keep my phone running for the next few days and see if it crops up again.
hyve9 said:
This setting has been turned on, I'll keep my phone running for the next few days and see if it crops up again.
Click to expand...
Click to collapse
Ok, it's been about a week and a half, I thought this was resolved but lately the issue has cropped up again, always at inconvenient times. Any logging I can enable or other settings I can tweak?
Had the same issue when I upgraded from C.61, which I now have learned breaks some sensors like light and proximity.
I'm currently back to stock until I have some time on the weekend to experiment again with downgrading to C.47 and then installing LineageOS.
Seems to be happening more frequently as of late. Friendly reminder for those of you experiencing this to not press the power button a bunch of times to try and resolve as (at least on my phone) this calls 911 and then you have to awkwardly explain to emergency services that there is no emergency :/
mattie_49 said:
Prevent accidental wake-up
Click to expand...
Click to collapse
I'm having the same issue continously, basically every time I put my phone into my pocket, it is unable to wake...
It is responsive but it's like the proximity sensor gets messed up.
I used on the proximity sensor tester apps to prove that it is still functioning properly, which I could turn it off at this point as it's certainly causing the issue based that it only happens when I put it into my pocket.
I've tried almost every combination of those settings at this point and it's not working. Might try doing a factory reset at this point..
Edit: I've used SD Maid to clear everything, it helped a bit.
Still having black screens. Going to just downgrade back to lineage os 18 till Twrp comes out for 12