What's new in Kiosk Satellite 2026.9.48
Kiosk Satellite now has a dedicated home at kiosksatellite.com, featuring a streamlined download page and a fully searchable documentation hub at kiosksatellite.com/docs. This release officially transitions all in-app, Remote Admin, and README links away from raw GitHub Markdown to the newly rendered guides, while squashing a few memory crashes and service timeouts on older hardware.
Changes & Enhancements
-
Centralized Web Hub: Project overviews, downloads, and documentation are now hosted on the new site. Guides are still written in the repository but publish directly to the web with each release.
-
Updated App Links: The About page (on-device and in Remote Admin), Analytics, Updates, and Fleet management pages now route you directly to the cleanly rendered web guides.
Bug Fixes
-
Android 7 Screenshot Memory Crash: Background apps and Android 7 devices rely on WebView for page captures. A bug was applying screen density twice, causing 1080p pages to scale up 3x and crash devices like the Galaxy A5 by allocating 100MB+ for the image. Width is now converted correctly and never exceeds the physical screen.
-
Foreground Service Kills on Slow Tablets: Previously, every resume asked Android to start a foreground service, which triggers a strict 10-second deadline for a notification. If a slow tablet stalled the main thread past this window, Android mercilessly killed the app. Since a resumed app is already in the foreground, the service now starts plainly and skips the trigger if it is already running.
-
Wake Word Self-Heal Interruptions: The app's microphone failsafe timer previously started counting from the wake word itself, prematurely cutting off voice turns to Home Assistant if your "Resume timeout" was too short. The self-heal now smartly waits while the turn's audio stream is open and only resets once it closes.
-
Transparent Screensaver Logs: If a screensaver fails to start because a dashboard interaction is still running, a voice turn is open, or a camera view is active, it no longer fails silently. The screensaver log now explicitly names the exact reason and blocking interaction.