Release 0.1.2 with navigation sounds and smoother Home scrolling
All checks were successful
Validate and publish Kaleido / android (push) Successful in 2m14s

This commit is contained in:
Elijah 2026-10-24 10:18:59 -07:00
parent 6269425b33
commit 430616330b
21 changed files with 232 additions and 18 deletions

View file

@ -52,3 +52,21 @@ The onn stayed on version 0.1.0 / code 1 until the actual in-app installation. N
For future live checks, start with an installed lower version signed by the same key, publish a genuinely higher version/code, navigate to Settings > Software updates with the D-pad, and follow the sequence above. Never clear app data to manufacture an update scenario. Android's source permission is a one-time, per-app step; the package installer still requires explicit confirmation for each update. Wait for the TV Settings source list to populate before selecting Kaleido.
Private evidence remains in ignored `evidence/private/`: `updater-results.json`, `published-release.json`, `updater-before.png`, `updater-fallback-discovery.png`, `updater-release-discovery.png`, `updater-source-allowed.png`, `updater-confirmation.png`, `updater-installed.png`, `updater-after.png` and `updater-final-home.png`. This verifies manual discovery, the manifest fallback and a real release download/install. It does not independently test the six-hour automatic-check interval, permission denial/retry, or rejection of deliberately corrupted/wrong-signed APKs.
## Navigation sounds and Home scroll performance - 2026-10-24
The specific hero-to-Continue Watching movement now has a dedicated check: `scripts/profile_home.py <label>`. It resets frame statistics for each Down transition, waits until it finishes, samples completed frames, then returns to the hero outside the measured interval. UI hierarchy dumps do not run during the measured animation. Its p95 limit is 33.34 ms; `--cold --cycles 1` skips the warm-up scroll and `--trace` records app layout/rendering spans. Use an optimized release with the baseline profile installed and `speed-profile` compilation, and never run another device test alongside it.
The original profiled release failed across five repeated transitions: 59 frames, median 17.5 ms, p95 50.3 ms, maximum 60.5 ms, and 28.8% above 33.34 ms. A separate trace showed main-thread measure/layout passes of 40–51 ms, repeatedly composing and remembering newly exposed image cards. Render-thread spans were substantially shorter. This isolated lazy-row preparation/disposal as the primary bottleneck in this scenario.
Home now uses a bounded one-viewport-ahead / one-viewport-behind lazy-layout cache window. It prepares adjacent rows and retains the hero/nearby cards on the return path. Artwork resolution, card geometry, the cinematic hero and Movies/TV presentation are unchanged. The fix does not cache the entire catalog or change focus/scroll destinations.
With navigation sounds enabled and its hot paths included in the baseline profile, the final APK measured 66 frames across five repeated Down transitions: median 17.2 ms, p95 28.6 ms, maximum 34.8 ms, and one frame above 33.34 ms (1.5%). Its first transition after a cold process launch measured 13 frames, p95 26.9 ms and maximum 30.1 ms. These are device samples, not a guarantee of every frame meeting a 60 Hz deadline. A preliminary run where the profile-install broadcast targeted the wrong receiver was excluded from the matched comparison; the final preparation returned profile-install result 1 and package compilation Success.
Navigation sounds default to On under Settings > Interface. Shared focus targets call Android's native UI sound only after an actual focus change; startup focus, unchanged targets and disabled sounds are silent. The TV's global sound-effects setting remains authoritative and was not changed. `verify_navigation_sounds.py` reproduced the missing control on the original installation, then passed both Off and On persistence checks across cold process launches on the final build. Two unit tests cover initial/duplicate focus suppression and muting/re-enabling behavior.
For a quiet device with system effects already enabled, run `python -c "import sys; sys.path.insert(0, 'scripts'); from verify_navigation_sounds import audio; audio()"` using the configured Python runtime. It compares identical D-pad focus movements with the app preference Off/On: the final test recorded zero native audio mixer writes while muted and 141 while enabled. This confirms output through Android's audio pipeline; physical speaker listening was not performed. It leaves the preference On and returns to Home.
Private evidence includes `home-baseline-results.json`, `home-trace-baseline-atrace.txt`, `home-complete-results.json`, `home-complete-cold-results.json`, `navigation-audio-results.json`, `navigation-audio-off-atrace.txt`, `navigation-audio-on-atrace.txt`, and the On/Off setting screenshots. `Build.ps1 -Release -Test` passed with three unit tests and zero lint errors. These measurements were taken on the local optimized test build before versioning the changes as 0.1.2. The installed test build retains the existing session and was left on Home with navigation sounds On.
All six `verify_ui.py browse` checks passed with the sound setting and cache window, including focus restoration, separate Movies/TV layouts, A–Z grids and PIN cancellation preserving the session. The broader `repro_runtime.py browse` check initially failed at p95 42 ms (48 ms with tracing), with further card composition/measurement during rapid movement. Including the new sound modifier/controller in the app's baseline profile brought the final profiled release to median 15 ms / p95 36 ms, GPU p95 7 ms, and stable horizontal Y coordinates at 182 px. Some stress-test frames still miss 60 Hz. `browse --trace` now records this exact regression loop to `browse-regression-atrace.txt` for future diagnosis.