-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Power button should unlock the screen, not turn it off #97
Comments
That makes sense. Sadly, there's no way to detect pressing power button on a non-rooted device. I check what we can do. |
I'm on a rooted device. Also, AcDisplay already has Xposed hooks, so using root isn't really setting a precedent. Also, I'm not sure what technical capabilities Xposed provides. Would this functionality be something that should go into the Xposed module or be separate? |
Also, TIL Snapchat doesn't detect screenshots by detecting pressing the power key. |
I see that the power key is now disabled when the lock screen is on. Is that related to this issue? |
Registering a broadcast receiver Screen On/Off can help with this issue? If AcDisplay is not setted as Lockscreen, and the Active Mode is on and Turn Screen automatically on new notification then, use a wakelock, turn on again the device and close the Activity that handles the lockscreen, that'll be a workaround. |
No, you can not use the SCREEN_ON/OFF event cause it has no distinction between "user turned the screen off" and "the screen turned off by itself". Also, I don't like the idea of such workarounds where screen gets turned off and then pops on again. |
I think there should at least be an option that pressing the power button when AcDisplay active should cause AcDisplay to unlock, instead of turning the screen off. In other words, AcDisplay should be equivalent to the "screen off" state.
I think this feature would be not only nice to have just because, but also because I think it's really important from an interaction perspective. The rest of this issue explains why—
The advantage of AcDisplay is that it can provide me additional information, if I want it, without breaking my current workflow. However, the way I have AcDisplay current set up, it breaks my workflow.
First, my setup is as follows:
System: passcode lockscreen, locks after 10-minute delay unless kept unlocked by smart lock
AcDisplay: yes wake on notification, yes active mode, no use as lockscreen
Here are some scenarios where AcDisplay causes more interaction than if I did not use AcDisplay. These are not just theoretical – I encounter each of these a few times a day.
None of these scenarios would exist if pressing the power button turned the phone on instead of off.
With that said, I think that AcDisplay (even despite this) is incredible app. If someone can give me pointers on where in the code base I can start looking to address this issue, that would be appreciated too.
The text was updated successfully, but these errors were encountered: