Installing an update fills the Install button with a progress bar,
driven by the ZIP's size against its Content-Length. When the install
finishes, a blue Restart button starts the new version. After the
restart, a card names the new and old versions. A failed install or a
missed restart shows a card with the reason.
A pending update marks the Settings button and the Settings header with
Steam's alert yellow (#FFC82C) and its exclamation mark, taken from the
SettingsAlert icon in Steam's UI on the Frame. The automatic check runs
daily instead of weekly, and retries after an hour when it fails.
run_program takes an optional cancel flag and stops its child within
about 50 ms when the flag is set. Downloads and the unpack use it and
throw Canceled, which leaves the install folder as it was. The file
swap after them is never canceled. The resident app sets the flag
whenever run() returns, so quitting SteamVR no longer waits up to 180 s
on a download.
The report server could hang Done: a phone that stopped reading a
download held its thread, and the destructor waited on it. A stalled
download took 29.9 s to give up with a send timeout alone. Sends and
receives now wait at most 200 ms at a time and check for shutdown, and
the server stops in about 0.1 s.
The ZIP and text downloads now carry the whole report. Only the page's
copy is shortened to fit a GitHub issue.
--report connects as a Background app, which never starts SteamVR.
Pressing Check for updates during the weekly check now shows that
check's result. A failed weekly check retries in a day, not a week.
With a recording, the phone page leads with Download the report file,
which gives knockthru-report.zip holding the report and the recording,
then Open GitHub, then one step to attach the file. A separate
recording link was easy to miss. Without a recording, the page keeps
the copy and paste flow.
Record knocks on the report card records 20 s of headset and controller
motion in the tests/data CSV format, gzips it to
~/knockthru-knocks.csv.gz, and adds the knocks and actions heard to the
report. The phone page then offers the recording as a download to
attach to the issue.
detector_test FILE replays any recording and prints every knock and
action, for triaging a report.
GitHub rejects issue bodies over 65,536 characters, and a full log can
reach about 93,000. The phone copy keeps the start and the newest log
lines and marks the cut. The saved file stays complete.
THIRD_PARTY_NOTICES.md now carries the qrcodegen MIT text, because the
release ZIP ships the notices file but not third_party/.
start_detached forks and closes inherited descriptors before exec, so
the restart after an in-app update does not hold the old app's SteamVR
connection open.
The report card's QR code now opens a page on the Frame, over the local
Wi-Fi, with the whole report. One button copies it and opens the
prefilled GitHub form, where it goes in the Report box. The page also
offers the report as a download. It needs a random token in the path and
stops when the card closes or after 15 minutes. SteamOS's firewall opens
TCP 1024 to 65535, and the kernel picks the port from that range.
Without a network, the QR code opens the GitHub form directly, as before.
The report card numbers the steps: open the phone camera, scan the code
through a lens, then sign in and press Create. Save report file is a
separate button that keeps the full report on the headset and says it
sends nothing. The issue link also carries the last error KnockThru
showed, in a new last-error field on the bug form.
Report in Settings opens a card with a QR code. A phone held up to a lens
scans it and opens the bug form in .github/ISSUE_TEMPLATE/bug.yml, with
the KnockThru version, SteamVR version, and passthrough status filled in.
The full report still goes to ~/knockthru-report.txt.
Vendors nayuki/QR-Code-generator (MIT) to encode the code.
--update installs the latest GitHub release over the running one and
restarts it. It reads the FrameDrop manifest, checks the ZIP's SHA-256,
and renames each new file over the old one. The resident app has the same
check and install behind CheckUpdate and InstallUpdate, for the panel.
--report writes ~/knockthru-report.txt with the KnockThru and SteamVR
versions, registration state, settings, and the end of both logs.
--uninstall --purge also deletes ~/.config/knockthru and SteamVR's
vrappconfig file for KnockThru.
A missing Room View button now throws DashboardChanged. The passthrough
tile then says a Steam update moved the button, and the log records the
SteamVR version once.
Robin Anderson