OrbitTv/docs/VERIFICATION-0.108.2.md

0.108.2: Dragon Ball GT's picture, built on the installed 0.108.1

Paul's report (4 November 2026, 21:58): Dragon Ball GT on Vortex "won't play on this device".

What the box showed:

• S1 E4 (item 228430) failed with noVideoDecoder=video/x-unknown.
• A 3-minute test of S1 E5 (228431) played sound and English subtitles with no video track (video=none).
• Emby reports every GT episode as H.264 640x480 in MKV with Vorbis audio. The library has only one copy, 64 episodes.
• The cause: the files carry their H.264 in the old Video for Windows wrapper (Matroska CodecID V_MS/VFW/FOURCC). Media3's Matroska reader recognises that wrapper only for DivX/Xvid, H.263 and VC-1, and labels anything else video/x-unknown.
• Paul doesn't own the Emby server, so remuxing the files there isn't an option. He asked for the fix in the app.

The fix:

• tv/orbit/classic/mkv/ is a copy of Media3 1.8.0's Matroska reader (Apache 2.0). It's unchanged apart from its package and one addition: parseFourCcPrivate also maps H.264 FourCCs (H264, X264, AVC1, DAVC, VSSH, either case) to video/avc. The stream is passed as it is, with its parameter sets in band, which the decoder reads.
• OrbitExtractorsFactory is Media3's DefaultExtractorsFactory with only the Matroska reader swapped. The programme, picture and ident players use it.
• Every other format and subtitle path is Media3's own.
• It's built on 0.108.1, the version on the box, so Advent and The Naughty List aren't in it. The same change is on main for later releases.

Checks

• 482 unit tests run, 0 failures. OrbitMatroskaTest adds 3: the H.264 FourCCs map, other FourCCs stay Media3's, and only the Matroska reader is swapped. Lint shows the same warnings as before and no errors.
• Not provable off the box: that GT now shows its picture. After the install, a 3-minute test of S1 E5 must show video=video/avc with a first frame.
• Episode 4: item 228430 stays on the failed list from 21:56. It can be cleared, so it's booked again, once the picture is confirmed.

APK: outputs/revision-0.108.2, signed, versionCode 162. Not installed.

Installed on the box (4 November 2026, 22:29)

Paul said "install and test".

• Snapshot first: copied to Codex/install-0.108.2-20261104-222924, and on the box to no_backup/schedule-rollback-0.108.1.
• Install: versionCode 162. No plan changed, and the tickets are identical.

The test of S1 E5 (228431): the tracks are video=video/avc 640x480 audio=audio/vorbis en 2ch subtitles=en selected. The video track is now found; before the fix it was video=none. Ready in 24.7 s, and the first subtitle cue arrived at 4.9 s.

Then the connection dropped: at about 22:31 the box stopped accepting adb connections (connection refused), though it still answers ping. The test's final result line, with the first frame, couldn't be read. Paul was asked what the TV showed.

Confirmed on the TV: Paul, 22:31: "works now". Dragon Ball GT plays with its picture.

Episode 4 back in rotation (22:40, with Paul's OK to fix GT): item 228430 was taken off failed-0.json. A copy of the previous file is on the box as failed-0.json.before-gt. The other entry, 4503351, stays.

The test's final line, read once adb was back: playtest result ready=true firstFrame=true video=video/avc 640x480 audio=audio/vorbis en 2ch ... errors=0 ended=time. The full 3 minutes played with a picture and no errors.