This should only affect recent SWMO master, after the new locking mechanism and new button assignment has been implemented.
3x power can be triggered simply by holding the power button for a moment. I do not think that hold should trigger triple press at all in this case.
3x power is set to open an instance of foot. 2x power is used to unlock the screen. This seems to be a bad idea, especially because of 1. and on top of that it allows to open foot from locked or crust state. To replicate: go into crust and hold down power for a bit -> n instances of foot open up but the phone is still locked.
Sometimes the phone enters a lock screen state with screen on. I do not know how to trigger it on purpose and it should not happen at all since I have SXMO_LOCK_SCREEN_OFF=1.
When 3. happens the phone no longer automatically enters crust. I can still force crust via the menu. After doing that and waking it again it enters crust automatically once more.
- 3x power can be triggered simply by holding the power button for a moment. I do not think that hold should trigger triple press at all in this case.
For the moment, we cannot distinguish boths. That would be ideal ya ! We can prevent terminal trigger while not unlocked. I would love a patch for this :D
- 3x power is set to open an instance of foot. 2x power is used to unlock the screen. This seems to be a bad idea, especially because of 1. and on top of that it allows to open foot from locked or crust state. To replicate: go into crust and hold down power for a bit -> n instances of foot open up but the phone is still locked.
I agree that this is not the more logical or "intuitive" combination. Anyway this decision has been made to let keyboard on a one trigger button (voldown) and we dont really want to loose easy access to keyboard.
- Sometimes the phone enters a lock screen state with screen on. I do not know how to trigger it on purpose and it should not happen at all since I have SXMO_LOCK_SCREEN_OFF=1.
This env variable usage has been dropped. Now you can decide which state you target with one or two power trigger.
- When 3. happens the phone no longer automatically enters crust. I can still force crust via the menu. After doing that and waking it again it enters crust automatically once more.
There is a "is idle" check that can prevent the phone to go to sleep. Maybe a ssh session is active ? Maybe the proximity lock daemon is running ?
s/loose easy access to keyboard/loose easy access to terminal/
Your numbering got a bit messed up there, I'll just try to refer to the original numbering.
Not quite sure what you mean here. We can no longer distinguish hold from 3x press but it would be nice to have?
Yes, it's unintuitive and I to would like to keep quick access to the terminal. Not sure what the nicest solution would be for that. But this point was mostly about being able to launch the terminal while the phone is locked. How can we prevent this?
Good to know that this has been dropped. What do you mean by one or two power trigger? I know that I can get into the (blue LED) screen locked with screen on state for a few seconds when single pressing from locked/suspend state. Sometimes this also happens under some other conditions, which I think is a state bug and probably causes 4.
No SSH session, proximity lock is turned off. I think this is a state bug with the "blue LED" state. It only happens after the phone gets into this unintentional "blue LED" state. The problem is gone again after I put the phone to crust once via menu.
5, I just had the phone suspend during an active ssh session. Weird also is that it just needed 3x power to wake up. Right now it is in lock with screen off and doesn't wake up at all anymore.
yes point 5 is true. There is no way now in swmo to just turn off screen and listen to music being played in mpv. The idle timer kicks in to put the phone into crust mode.
Regarding 3, I figured I could enter a blue LED, screen locked but on, state by 2x power while the phone is unlocked. After 10s it turns the screen off, 10s longer and it goes to crust. Why have this at all? I can't think of a scenario where this is useful.
On Wed, Oct 27, 2021 at 10:56:32AM -0000, ~murks wrote:
Regarding 3, I figured I could enter a blue LED, screen locked but on, state by 2x power while the phone is unlocked. After 10s it turns the screen off, 10s longer and it goes to crust. Why have this at all? I can't think of a scenario where this is useful.
Do you mean a 'why is a locked plus screen on state useful'? It is useful if you get a notification: we can wake up from crust and go into a 'locked plus screen on' state to display the notification.
However, if you mean 'why do we first go into lock-but-screen-on and then into lock-and-screenoff and then finally into crust as opposed to lock-and-screenoff and then crust'? I agree! I think we should just go straight into lock-but-screenoff, or have this as a user-defined variable somewhere.
On a related note, I don't particularly find mapping powerbutton_two to lock_screen_action 2. Why not just click it once to wake up and then click it again to unlock? This frees up the double click for something else. (On my system, I have one click do lock_screen_action and two+ clicks do the keyboard.)
-- sic dicit magister P https://phartman.sites.luc.edu/ GPG keyID 0xE0DBD3D6 (CAE6 3A6F 755F 7BC3 36CA 330D B3E6 39C6 E0DB D3D6)