What's new in Kiosk Satellite 2026.8.27

Bug Fixes

Motion detection asks the camera for its slowest frame rate so dark rooms get longer exposures instead of cranked-up gain. Some cameras cannot live with that request: the Galaxy Tab S6 Lite's front camera answers by hunting exposure forever, and that endless hunt is what kept a core pinned in the camera system, which is why the camera library rollback in v2026.8.20 was not enough on its own.
The motion analyzer already sees the hunt plainly, as an unbroken run of frames where the whole image brightens or darkens together with no local change, something no real scene sustains. After about ten seconds of it, the camera is restarted once with default exposure for the rest of the session. Expect at worst a few seconds of high CPU right after the screensaver starts, then normal camera cost.
Healthy cameras are untouched: the long-exposure request stays exactly as before wherever auto exposure settles, so dark-room motion detection loses nothing on devices that were already behaving.
If you were affected, the app log confirms the fallback with "auto exposure kept hunting under the slow fps range; restarting the camera with default exposure".

The Sendspin protocol announces nothing on connect about a queue that is not playing, so a Music Assistant queue paused before an app restart was invisible to the player: the gesture flipped its setting, but there was no card to reveal, even though the queue sat in Music Assistant ready to resume.
The gesture now asks Music Assistant directly when it has nothing to show: the player's active queue comes back as a paused card with the artwork, track and position it left off at, and play on that card resumes exactly where the queue stood. Players synced into a group find the group's queue.
Nothing changes when there is a real reason to show nothing: a queue already playing keeps its live card, and a server with no queue for this player still shows no card, by design.