I've been searching for awhile now...
I have disabled my lock screen. Now the problem I'm having is the phone wakes with any of my hard buttons. Does anybody know how to disable the phone waking with any button other than power?
Thanks!
Well what phone/OS are you using? I'm pretty sure cyanogen has options for that, but everything is slightly different on each different phone and OS.
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 have a evo which I had rooted and left everything stock on.Suddenly the down volume button wants to engage at any given time and for extended periods of time...in call,while on home screen,when the screens off...doesnt matter engages volume down and doesnt stop..
So I thought maybe unrevoked wasnt installed so clean,since this happened the first time soon after rooting.I hoped totally wiping the phone(caulkins) would fix this button issue,which is HELL in the bootloader....AFter a full wipe and stable cyanogen7 all seemed well! the problem was gone...So I figured cool,must been some software issue.Now its back a week later,I walkd in room to see screen on battery drained and phone just vibrating away.
So I switched to armons recovery,wiped dalviks and caches...no luck so I decided I would remap the key.I got a remapping app and it didnt have a way to DISABLE the key only remapp it to another function.Needless to say any such function being pushed 100 times a minute isnt much a fix.I tried a volume blocker app which just popped up every ten seconds asking if i confirm the volume change....
I am debating on opening the phone up and seeing if its a physically stuck key...However due to the fact that I can make it happen by turning screen off then on to me says its not an actual hardware button issue...
I have an evo I use for cellular service...which I dont much mess with,this one is wifi only and running cyanogen7 and latest godmode kernel...its weird how it worked great for a week never a problem and now Im stuck in a scrolling out of control bootloader...because when i powered off lol the down button engaged while turning back on....very frustrating...
Can I DISABLE this key?
I have the same exact problem. My phone boots to HBOOT but I can't push the volume buttons to select nor can I push the power button. Any help would be greatly appreciated!
Hello every1,
First of all im sry to be starting a new thread about this, but I cant seem to find anything related to it in google or in here, at least with a quick search. My phone is generally treated well enough, and I always keep it in a protector, but tonight it fell off my hands, and I THINK than since then, the "android" settings and return capasitive keys, right under the screen, cannot switch off. This means that if I lock the phone, or even turn it off, the backlight of these buttons does NOT switch off. I have to remove the battery. If I insert it again, and switch the phone back on, they still wont shut down. I now that they CAN be switched off, because I resetted the phone to its factory settings, at least the internal memory, and when it rebooted, the backlight of the keys turned off and back on again.
I am not interested in shipping the phone back to china to make use of its warranty, and im not sure whether letting that backlight on permanently will damage the phone. The screens function and backlighting seems to be OK. What can I do to disable or restore them to good functionality? I never rooted the phone, and I have searched for some apps that can disable those buttons backlight but they require rooting. What would you have me do? I do not mind rooting the phone, or tweaking it in anyway, as long as it remains functional. Thank you for any help!
any1?
Hey guys,
strange and frustrating problem. I was using my phone pretty extensively today (although nothing crazy), mostly thanks to Pokemon Go. Tonight after using my phone normally, I went to press the power button to turn the screen off and nothing happened. I was able to reboot (by changing one of the long-press actions to bring up the power menu via GravityBox) and then was unable to power on the phone. It seems like my hardware power button has suddenly become unresponsive. This leaves me unable to power on/off the phone, including booting into the bootloader. Also, I seem to be unable to wake my phone up by double tapping the screen or swiping up.
The phone otherwise functions fine. If I get a notification, the screen wakes up and I can use the phone. Otherwise, the only way I've been able to get into the phone is by connecting it to a computer and issuing ADB commands. The IR blaster functions fine which makes me think it's not the hardware button?
Has this happened to anyone else before? Can the power button just break like that without any water / physical damage? The fact that I also can't wake the screen makes me think it's a software issue. One other thing I suspect is that my phone abruptly died yesterday (battery died despite software thinking it still had juice left). In the past, with the modified kernel / rom, this has resulted in some nasty issues, including 4G not working and the Android system process basically exploding. I thought I lucked out when I powered it on after that, but maybe it just took a day for this issue to manifest itself.
I'm going to make a NANDROID backup and try flashing a few different things to see if I can fix it. I'll post my progress here.
Current build:
- Verizon M8, S-OFF
- TWRP
- Android GPE 6.0 (MRA58K.H13)
Edit: I haven't been able to find a fix. I'm a bit afraid to try a full RUU since I can't use the hardware keys to reboot into the bootloader should something go wrong. It may just be that my PWR hardware button is f'd which really sucks. I'm not sure I'm up to cracking open the phone to fix it. In the meantime I downloaded an app called Gravity Screen On/Off which uses the phone's proximity sensor to wake the screen up and it seems to work ok for now.
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!