Repository navigation
Android TV parity: subtitle state, overscan safe area, and audio passthrough #45
Description
Three customer-reported defects in the shipped Android TV app that have never been tracked. Filing here rather than against apps/tv-native because that app is being replaced by this one — these are parity requirements for the Compose shell, alongside #9 and #11.
Subtitles stay rendered after being turned off
Google TV, 2023-04-08. The viewer disables subtitles and they keep displaying. Reported together with the overscan issue below by the same customer.
The app overscans
Google TV, 2023-04-08. UI is cut off at the screen edges.
The workspace TV product spec defines the safe area — 2% vertical, 4% horizontal — and @putdotio/design carries it as tv.overscan.x / tv.overscan.y (0.04 / 0.02). So the contract exists; the app does not honour it.
No Dolby Digital Plus passthrough
Fire TV, 2024-01-24. Customer reports DD+ is not offered. The TV product spec promises HDMI audio passthrough, and Fire TV hardware supports it.
This is worth confirming against what the file actually contains before treating it as a bug — a source without a DD+ track cannot offer one.
Why these are worth carrying forward
All three reached customers and none produced an issue. The pattern that matters: a regression caught by a customer is a missing test. Subtitle state and safe-area layout are both cheap to assert and currently unasserted.
Scope
- Subtitle enable/disable state is authoritative and survives track changes and seeks (feat(tv): add Language, Subtitles and Speed pickers to the player #221, fix(playback): keep subtitles off until account settings load #231, fix(playback): pick the server's default subtitle and hide subtitles entirely with hide_subtitles #261)
- The Compose TV shell honours the overscan safe area from the design tokens rather than a hardcoded margin (fix(tv): pad the shell by the generated overscan safe area #207)
- Confirm the audio passthrough capability and expose it where the hardware and the source both support it (needs Physical device proof set: Android TV, Fire TV, phone, tablet inventory #51 hardware)
- Cover subtitle state and safe-area layout so none of the three can regress silently
Raised from the consolidating TV epic, putdotio/putio-web#954.
Activity
altaywtf commentedon Aug 8, 2026
Filed from the TV consolidation sweep in putio-web#954, which swept Intercom for TV problems tracked nowhere.
Belongs under #14 as parity requirements for the Compose TV shell, alongside #9 and #11. All three reached customers on the shipped app and none had an issue.
altaywtf commentedon Aug 8, 2026
Folded into the rewrite epic #14 (W4 checklist). Mapping onto the parity slices so nothing here needs its own workstream:
tv.overscan.x/ytokens (via the token adapter Generate the Compose design-token adapter from @putdotio/design with a drift gate #20), never hardcoded marginsThis issue stays open as the verification checklist — it closes when all three defects have assertions proving they can't silently regress in the Compose shell.
feat(tv): add Language, Subtitles and Speed pickers to the player (#221)
fix(tv): pad the shell by the generated overscan safe area (#207)