Second release. TMDB is now the default metadata provider, and a new chooser resolves ambiguous matches (remakes, same-named sequels) instead of guessing.
What's new
- TMDB is now the default metadata provider, using a key bundled with the app - no setup needed. TheTVDB is still available as an alternative from Settings, and you can enter your own personal TMDB key there too if you'd rather use that instead of the shared one.
- New: a "which one did you mean?" chooser for titles that match more than one thing exactly (e.g. a remake, or several movies sharing a name across different years) - shown as a floating tray over the recommendation, letting you pick the right one instead of TVRelay guessing the most recent. Can be turned off from Settings → "Ask when a match is ambiguous" if you'd rather it always pick automatically.
- Faster Nuvio launches: when TMDB resolves a title, TVRelay now opens it in Nuvio using TMDB's own id directly, skipping an extra lookup step.
- Fixed a real mismatch where a launcher card's title included a franchise prefix (e.g. "Star Wars: The Mandalorian and Grogu") that the metadata provider didn't have on file that way, occasionally resolving to an unrelated result.
Limitations
- Fire TV is not supported. Tested on a real Fire TV Stick; recommendation clicks never reach TVRelay's detection at all, most likely because Amazon's newly-redesigned Fire TV home screen doesn't expose standard Android accessibility events to third-party apps. TVRelay is Google TV only.
- WuPlay isn't supported as a player - it has no deep link for opening a specific title, only for switching profiles remotely.
- Some recommendation rows (personalized/algorithmic ones in particular) don't expose their title to accessibility tools at all.
- Voice search isn't detected. Speaking a title into the mic jumps straight to that title's page through the launcher's own voice assistant, without ever generating a click for TVRelay to see - there's nothing for it to intercept. Typing into the launcher's own search bar works fine and is detected normally.
- The metadata provider's search can still occasionally have no better candidate at all for a title (a data-coverage gap, not something the chooser above can fix on its own).
See the README for full installation instructions and troubleshooting.
Verifying the APK
Signing certificate SHA-256: 97:B2:E9:39:61:B5:13:85:8C:66:EE:34:22:E0:C2:E8:87:2E:73:E3:C0:7B:57:52:75:08:2B:59:79:7D:FF:DA