Release Kaleido 0.1.10 with native Original playback and PCM compatibility
All checks were successful
Validate and publish Kaleido / android (push) Successful in 2m45s
All checks were successful
Validate and publish Kaleido / android (push) Successful in 2m45s
This commit is contained in:
parent
784921dba9
commit
2a83fe0db5
23 changed files with 721 additions and 43 deletions
|
|
@ -1,5 +1,7 @@
|
|||
# Device regression review - 2026-10-23
|
||||
|
||||
For the 2026-10-26 codec/HDR sweep and its native-versus-converted playback findings, see [Dedicated playback validation](playback-validation-2026-10-26.md). It includes confirmed Dolby Vision/HDR10/HLG signaling, audio output limits, the TCL HDMI capture limitation, and the restored HDR settings.
|
||||
|
||||
Target: the authorized onn at `192.168.50.195:5555`, package `tv.kaleido.app`. Other applications and the launcher were not modified. Screenshots, traces, UI dumps and server-specific logs stay in ignored `evidence/private/`.
|
||||
|
||||
## Browsing
|
||||
|
|
@ -144,3 +146,18 @@ Performance was measured with the signed release and confirmed ART `speed-profil
|
|||
The macOS checkout was reattached to the existing repository history without replacing its source files. Builds reused an existing JDK 17 with Gradle 8.13 and an isolated SDK 36, and used the original private signing key. `assembleRelease testDebugUnitTest lintDebug` passed (five unit tests); the signed debug build passed all 21 Android integration tests against the existing encrypted session. An outdated integration-test transcode argument was updated to `StreamQuality.Original`. Scripts accept `KALEIDO_ADB` for the local ADB executable and retain the authorized serial selection. Private keys, toolchains and raw device evidence remain ignored.
|
||||
|
||||
On the TCL (`192.168.50.200:5555`), 0.1.9 installed in place and ART confirmed `speed-profile` after a lost compilation reply. Rapid tab/Down, scrolled catalog re-entry and the horizontal round-trip passed. A longer transition run lost its ADB transport; `device.py` now reconnects when the serial disappears as well as on closed/offline errors. A shorter, complete Movies sample (`profile_transitions.py --skip-home`) measured tab → Discover p95 22.7 ms, Discover → row 23.2 ms and row → row 46.1 ms (baseline 74.8 ms). Entering Movies measured p95 94.2 ms / maximum 106.4 ms, versus baseline 106.8 / 150.1 ms. These are individual samples; the weaker TV still misses frames on section composition, and the interrupted run is not counted as a complete pass. Both comparisons retained the existing session and settings.
|
||||
|
||||
|
||||
## Native playback and release performance — 2026-10-26 (0.1.10)
|
||||
|
||||
Original quality now opens the actual file first. On the ONN, the default path retained 3840×2160 HEVC/AAC 5.1 and 3840×1608 Dolby Vision/EAC3 7.1 instead of the baseline's 1080p/stereo conversion. Plex-selected audio is applied to native tracks, Subtitles Off disables native text tracks, and unsupported selected tracks retain server fallback. A nonempty audio-only track list for a declared video now triggers fallback: the VC-1 sample automatically reached rendered 1080p HEVC through Plex. Stream preparation is serialized, and fallback checks its session generation before replacing a newer stream. Movie controls identify server conversions.
|
||||
|
||||
The failing mono WAV contained a center-only PCM speaker mask. The audio sink normalizes one-channel PCM to Android's standard mono output, preserving rate, channel count, timeline and channel mapping. The 24-bit/96 kHz source played at 96 kHz through the existing 16-bit PCM sink; standard 16-bit/48 kHz stereo also passed. Multichannel PCM and encoded bitstreams retain their layout. This is a playback compatibility fix, not a new claim of bit-perfect 24-bit output.
|
||||
|
||||
Debug functional checks passed native Dolby Vision profiles 5/8/10, EAC3 7.1, AV1/TrueHD 7.1, Opus 7.1, DTS-HD input with DTS-core output, FLAC, selected AC3, and backward seeking. The AV1/TrueHD steady run covered 61.8 seconds with 1,483 rendered frames, one dropped frame and no later buffering samples. All seven remote player checks passed, including switching a conversion to Original quality. The Android runner reported OK for 24 tests (the capability inventory is opt-in); five host unit tests and release/debug builds plus lint passed. Native next-episode validation was not completed after the testing interruption and is not counted as a pass.
|
||||
|
||||
The user reported severe lag while the devices still had temporary debug APKs installed. Both were confirmed `DEBUGGABLE`, version code 11, with ART `run-from-apk`. They were restored to the exact published 0.1.9 release, without clearing data, and profile compiled. A subsequent controlled ONN comparison used only non-debuggable production-signed APKs with ART `speed-profile`. Three cold starts measured activity startup median 431 ms for 0.1.9 versus 423 ms for 0.1.10. Home readiness, including UI-dump polling overhead, was 6.720 versus 6.773 seconds. A full Home/Movies transition cycle recorded 26 versus 23 skipped vsyncs overall; Movies entry p95 was 79.7 versus 75.6 ms, with 11 skipped vsyncs in each. Individual transitions varied by a few milliseconds. The release comparison showed no material navigation/startup regression; it does not promise zero stutter. The TCL repeat was skipped at the user's request.
|
||||
|
||||
The signed 0.1.10 APK uses the existing production certificate, version code 11. APK checks found neither private session data nor debug playback intent strings. Raw comparison records remain in ignored `evidence/private/release-comparison/`. The new benchmark scripts reject debuggable APKs and require `speed-profile`, so functional debug results cannot be mistaken for release performance evidence. The user explicitly authorized leaving Dolby Vision/HDR10 enabled; cleanup must not restore the earlier disabled list.
|
||||
|
||||
The actual non-debuggable release was also opened through Search and title details and played the 4K HEVC fixture from the beginning. Playback reached PLAYING/READY in 2.565 seconds; the recorded 30-second steady sample had zero BUFFERING transitions and one READY event. A preceding one-minute session also completed without a second READY event, but its harness incorrectly expected Home instead of the originating details page, so it is not counted as a fully completed benchmark. The corrected run returned normally and restored the exact previous resume point with the watched count unchanged. This checks real release playback, rather than ignored debug test intents.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue