Controls and Key Remapping - Keyboard, TV Remote and Gamepad, Your Way

Open Settings, General, and tap Controls & Keybindings to reach the key-binding screen for navigation and playback. Every command - grouped as Playback, Navigation, Browser Actions, View & Zoom, Audio & Subtitles, Sorting Actions, System UI and more - can be reassigned to a D-pad button, a gamepad button, a keyboard key or a mouse button. The Browser Actions group is remapped on its own, separate from the player's transport buttons, because the app reads which surface is active before deciding what a button does - the same physical button can browse a file list in one place and skip a track in another. Reset one group at a time from its own menu, or use the reset-all action to put every binding back to its factory defaults.

Hold a direction on the D-pad, remote or keyboard past a short repeat threshold in any large grid, and it jumps a whole page at a time instead of one cell. A gamepad's left stick works the same way, with its own dead zone and hold-to-accelerate; the right stick scrolls the active list, and the shoulder buttons page-jump too - the player keeps its own separate button mapping, so none of this changes how it behaves. If focus ever lands on an empty or bare scrollable area - after data loads late, for instance - the next directional key press moves it straight to the first real control instead of leaving it stuck nowhere.

Under a remote, keyboard or gamepad, a single highlighted frame - or, on some controls, an accent outline drawn on the control itself - travels with focus across every screen, form and dialog, so you can always see where you are; it only appears under non-touch control, never while you're using your finger. Opening any screen puts focus on a real control straight away, so the first key press does something instead of just waking focus up. In the player, the outline steps aside: arrow keys move focus between the on-screen transport controls instead, and the video or artwork surface itself is never outlined.

On a build with a VR runtime, the same Controls & Keybindings screen carries a VR Only group for headset gestures. Its rows show a readable name - Swipe Left, Double Pinch and the rest of the named gestures - or a clean "VR N" for a code with no name yet, instead of the raw "VR[15]" form the codes arrive as. A build without a VR runtime never shows this group at all.

The Permissions screen and its settings sub-fragments take D-pad focus correctly, so the remote always has something to move onto. An overlay fragment - permissions, extensions, licenses - keeps focus inside itself instead of letting a directional key slip through to the settings screen hidden underneath it. An empty file browser list handles arrow keys and next/previous-file commands without a problem. And the custom views that draw their own UI - the player, the mini-game, the launcher desktop and the gesture settings screen - all answer to the D-pad and the keyboard, and their colors follow the app's theme instead of staying fixed regardless of it.