This is a diagnostic build, not a fix. Intended only for users investigating a Fire TV Stick 4K (2nd gen) / Fire OS 8 focus bug where D-pad navigation into Home/Library/Authors content is only possible while holding the down button during the connect phase.
If you are not actively helping diagnose this specific issue, use Android TV v1.0.8 instead.
Update 2026-04-24 — logs screen UX fix
The previous build in this tag had a usability problem: every D-pad keypress appended a new focus-debug log entry to the Settings → Logs screen, and the screen auto-scrolled to the bottom on each new entry, fighting users trying to D-pad up to the Copy/Share buttons.
This build reverses the display order on the Logs screen — newest entries appear at the top, right next to the Copy and Share buttons. New entries no longer yank the scroll position. Underlying log storage is unchanged, so the shared .txt file is still oldest-first as before. This is a temporary UX tweak scoped to this diagnostic branch only; the general-release Logs screen stays chronological.
Re-sideload this APK over the previous -firetv-focus-debug install to pick up the fix.
What this build does
Adds extra logging to the TV navigation plugin so that every focus attempt and every D-pad keypress is recorded to the in-app log viewer (Settings → Logs). Behaviour is otherwise identical to v1.0.7.
For the reporter
- Sideload this APK over your current v1.0.7 install.
- Open the app and navigate to Settings → Logs → ⋮ menu → Clear Logs, then close the app.
- Reproduce the failing case: open the app, don't touch the remote, wait until fully loaded, then press down once and try to navigate.
- Close the app and reproduce the working case: open the app and hold down during connect.
- Open Settings → Logs — newest entries are at the top alongside the Copy and Share buttons. Tap Share and send the log file to your email / cloud / etc.
- Attach the log to the GitHub issue so we can diagnose.
For developers
Branch: fire-tv-focus-handling. See docs/FIRE_TV_FOCUS_DEBUG.md on that branch for the full instrumentation layout and signal interpretation guide.
The actual fix will be a separate PR once the reporter's logs tell us whether we need a post-connect focus pulse (Option 1) or a synthetic user-interaction event (Option 2). Do not merge this instrumentation to master as-is.