I’m getting an odd recurring, occasional issue with KLWP - the elements on my wallpaper stop responding (as though it’s become a static background image). Clock stops updating; Color changes on shapes stops changing; Touch action on “buttons” stops responding.
I’m running Nova 8.0.18, and KLWP 3.77b435216 on a Pixel 7a with Android 15.
Can you check and make sure to remove KLWP from your device’s battery optimization or similar 3rd party apps? Also, go to KLWP’s app settings >> Advanced options >> Turn on “Use direct touch”.
KLWP is set to allow background use (under Battery settings).
I turned on Direct Touch, but it immediately stopped responding to touches. Turning that back off has re-enabled touches.
I’ve turned off Adaptive Battery (Android settings) and I’ve NOT been editing the wallpaper multiple times per day (which I was doing). Ive not had the original issue (“frozen” wallpaper) in the last couple of days.
Hi
It’s just done it again, for the first time in several weeks (first time since I last posted)
I’ve been editing a new wallpaper extensively for the last 2 days. Otherwise nothing much has changed - although I did recently get the latest months security update.
Are there any KLWP logs I can be extracting for analysis?
Can you try turning on “Disable Parallel Rendering” under advanced optios?
I’ll try that for a few days, but it hasn’t done it again since I reported it again.
I have a half-theory that it’s related to the Android “wallpaper and style” screen or settings. That appeared randomly (I may have long-pressed and opened it in Nova). I’m going to see if I can force the issue to appear that way.
Ok, so I can recreate the issue, I think.
Starting from Kustom set as my wallpaper, Nova as my Launcher.
Re-creation steps:
Long press on a blank area
Nova shortcut options opens
Tap “Wallpapers” option
Choose Live Wallpaper
Choose Kustom
Tap “Set wallpaper”
That results in the wallpaper (including layers that are set with Visible If Not Locked) appearing, but the touch-responsive elements not responding - presumably because it’s actually just a flat image of the designed screen, and not a Live Wallpaper itself?
Going back to Kustom, loading the preset, and pressing Save prompts with the Missing Requirements, set as wallpaper screen. Tapping “Fix” solves the issue.
The thing I’m not sure on is how I could have triggered all of the re-creation steps without noticing. Feels unlikely, but no way to know.