Update tv.md: Add new "Use a Smart-TV Remote to Escape RetroArch" section

[davidhedlund]

No description provided.

[fpscan]

Thank you but this doesn't feel like it's need to be in the documents.

[davidhedlund]

Thank you but this doesn't feel like it's need to be in the documents.

I spent quite a bit of time putting this guide together, so if anything seems unclear, I'd really appreciate it if you could ask questions before closing this out. If you haven't used RetroArch on a streaming device, the frustration of getting stuck might not be immediately obvious. To provide some context: this workaround is essential because you often need to return to the Android TV home screen just to re-pair a disconnected Bluetooth controller via the TV remote so you can get back to gaming.

[fpscan]

Thank you for all of your additions, I'm truly appreciate the effort and changes, sometimes the changes might be not fit yet they are general knowledge. I'm looking forward to see more PR!

[davidhedlund]

Thank you for all of your additions, I'm truly appreciate the effort and changes, sometimes the changes might be not fit yet they are general knowledge. I'm looking forward to see more PR!

Thank you for taking the time to communicate so thoroughly on this, I really appreciate the extra effort. I know this particular section handles a bit of a niche scenario, but it definitely doesn't hurt to include it for the users who do run into this exact issue. I started the section in a new revision by explaining that autoconfigs are not designed for TV or digital media player remotes, which provides the necessary context for why this workaround is needed in the first place. So please review this revision:

Use a Smart-TV Remote to Escape RetroArch on Digital Media Players

Note: This section is for Digital Media Players only. TV remotes cannot operate on PCs at all; even basic navigation commands will not function, as standard computer graphics cards do not support HDMI-CEC communication.

Because RetroArch is designed for gamepads and not for TV or digital streaming remotes, it lacks built-in autoconfig profiles for them, meaning they will not function inside the app by default. Sometimes you need to exit RetroArch but find yourself stranded without a gamepad—for example, if the Bluetooth disconnects. In this situation, you specifically need to return to the OS HOME screen (for example, Android TV's HOME screen) to reach Settings just to re-pair that disconnected Bluetooth controller via the TV remote so you can get back to gaming.

Normally, you could just grab your digital media player remote and hit the HOME button. But what if you can't find it, you're traveling and forgot it at home, or you just want to keep things simple and stick to the TV remote? Without a way to exit RetroArch, you'd usually be forced to hard-restart the digital media player just to access the HOME screen every single time this happens. Thankfully, there is a better workaround.

Essentially every modern Smart TV has HDMI-CEC hardware built into it. While HDMI-CEC Remote Control Pass-Through is designed to pass basic commands—strictly only arrow or select keys—from your TV remote directly to your media player, the HOME button is trickier. TV manufacturers almost always hardcode it to open the TV's own built-in OS.

Fortunately, you can configure many smart TVs to override this behavior and map specific buttons on your remote—such as the "..." button found on certain brands, which opens an on-screen menu where extra functions like HOME are located—to send physical HOME button presses straight through to your connected device. Once enabled, you can easily switch to the HOME screen so you aren't locked in RetroArch, using nothing but your standard TV remote—saving you the hassle of a forced reboot.