Questions About KLCK

Issues
1

There is no tag for KLCK here. So I hope that this post is OK…

I want some lockscreen shortcuts on my new Moto XT2214 with Android 12. This page suggests I can do this. But the it doesn’t work on my model at all. For some reason, there is one and only one - and it is hard-coded and deals with Google Home stuff - which I don’t want. Amazingly, the only way to even remove that single one is to have a PIN (or other secured) lockscreen in use. When you do, there is an option to disable that shortcut. But if you return to a simple, swipe lockscreen, it comes back! I have tried manipulating the phone’s secure settings (since I am rooted) to add some shortcuts as described here. But that doesn’t work at all on this phone.

So I finally come to KLCK as a user of KLWP…

I recognize that this app is new and still experimental. And I feel there is alot to like so far. But I notice a couple things (the 1st 2 are shown here):

20240721_090623
20240721_0906231365×2662 251 KB

  1. When KLCK is showing, KLWP does NOT realize the screen is locked - ie, $si(locked)$ does not equal 1. As such, parts of my KLWP show through at the top of the lock screen overlay even though their visibility is checking for locked and removes those items if true.

  2. Perhaps related to the issue in #1 is that the lockscreen overlay is not tall enough. This is likely due to the in-display camera or notch at the top. Or the area being reserved for the status bar. Not sure what, if anything, can be done about that. Either way though, it is a bit odd looking.

  3. This is really important! And maybe I am missing something… A normal lockscreen will allow the display to power off (or at least return to Always-On Display) after a period of time. Often, it fades away during this period. It is my experience that this NEVER happens with KLCK. It just stays on and that clearly seems a problem. I was thinking to create a top-level flow that is triggered on preset load, then waits a given amount of time, and then triggers a Kustom action to turn off the display. But I am not seeing anything like that. I could trigger a Tasker task to turn off the display. But it really seems like there should be a way to do this inside of KLCK since it is a rather basic requirement of lock screens.

Thanks for any suggestions/hints!

2

BTW - I have tried the following without success:

  1. In Android settings, enabled KLCK to be full-screen. Not sure but there MAY be the need for a permission request for this from the app itself. Perhaps this is a topic to be considered…

  2. Added a top-level rectangle shape to my lockscreen preset and changed its dimensions to be larger than the actual screen dimensions.

All of this is moot unless/until the app performs some form of display off after a timeout. That alone is a deal-breaker. Too bad…

3

I found out that the screen does turn off, but since the phone sees KLCK as a running app, it will turn off after the amount of time you’ve set in the time-out screen option. I’ve just shortened that time to my liking and now it works.

4

I guess it makes sense that you would get this result. My normal screen timeout is 2 minutes. I really do not think that I want to change this just to help KLCK. Seems to me that any normal app screen timeout would still be way too long for a lock screen timeout. If something like Tasker can turn off the display, I see no reason why KLCK cannot and should not. I hope that Frank can address this and the other issues I have raised. Best

5

I have the same problem with KLCK not showing a full screen as your example. I am on Android 15 and have tried EVERYTHING I can think of and cannot resolve it. Other applications show in complete full screen, but KLCK does not for me.

6

Problem solved! In order to have FULL screen with KLCK my phone(s) require that the phone be locked. So when you swipe across, you encounter a password (PIN) screen. So after a year of so trying every setting on multiple phones the issue was simply to “lock” the phone.

7

Well, congrats. Perhaps that actually makes some sense. But I don’t want/need a pin or pattern, etc.

I finally managed to get something akin to what I wanted using Tasker - which is another truely great and amazing app!