Kustom KLWP Beta – Shader System & UI Bugs (Current Build)
Shaders are an awesome and much‑needed addition to KUSTOM, huge thanks to Frank for bringing them in. I very much appreciate the film grain one as that mitigates color banding (due to androids bit depth restrictions), but I’m afraid still has its shortcomings. That said, after testing the current beta, there are several issues that seem consistent and reproducible. Listing them here so they can be tracked and addressed.
- Shaders not working on root background layers
Applying a shader to the root background has no visible effect. It looks like the root layer is bypassing the shader pass entirely, so global effects (noise, distortions, colour shifts, etc.) can’t be applied. I can understand because blurred background acts the same it’s just very frustrating with how you set up a project as a whole considering no blur can be made with separate overlay groups.
- Shader parameters not labelled correctly
All shader parameters show up as “Parameter 1”, “Parameter 2”, etc.
They don’t inherit the actual parameter names defined in the shader, which makes tuning them guesswork. Not within FX on in the animation tab.
- Shaders cannot stack in animation layers
When adding multiple shaders in the animation tab, the topmost shader always overrides the previous one.
They don’t composite or chain, only the highest layer is applied.
- Shader animation loops are not continuous (visible jitter)
Any looping shader animation shows a stutter or jump at the loop point.
Even with smooth parameters (e.g., Amount), the animation loses frames or resets abruptly.
- Animation layer reordering still bugged
Using the up/down arrows to reorder animation layers still requires multiple presses before the order actually updates.
This has been an issue for years and still persists in the current beta.
- Left‑side hierarchy view not updating correctly
The layer hierarchy on the left panel doesn’t reliably show the correct nesting level.
It often fails to highlight or reflect the current position in the structure.
This has been broken for several months.
Summary
Shaders are a fantastic addition, but the current beta has several functional and UI issues that make them difficult to use in real projects. Happy to provide logs, examples, or further testing if needed. This addition has great potential as some one who creates shaders themselves, even within the phone and applied via another app through live wallpaper, it’d be a great addition if custom shaders could be pipelined into kustom aswell. I love this major step, but we still have a way to go.