0.12.0 Build 0-kmb.9

Handles MediaTek DuraSpeed blocking the WebView renderer.

DuraSpeed suppresses the sandboxed process the WebView needs for a renderer, leaving the app alive and focused on a permanently blank page. On this panel it reproduced every time after an adb shell am force-stop; a force-stop from Settings never triggered it (5/5 clean), so this mostly affects developers.

What changed

• The app clears setting.duraspeed.enabled on startup when it holds WRITE_SECURE_SETTINGS (granted over adb; most installs will not have it, and the app never crashes without it). Measured on device: this cures an in-flight suppression, not just prevents future ones.
• Settings > About reports whether the device ships DuraSpeed.
• A blocked browser process is now explained, with the adb fix offered to copy, instead of a blank screen.

Post-install step

adb shell pm grant xyz.wallpanel.app.kmb android.permission.WRITE_SECURE_SETTINGS

The grant survives install -r and reboots; only an uninstall drops it.

Signed arm64-v8a split. See README, section "MediaTek DuraSpeed".