Public support board
Fixes, open reports, and answers.
Browse historical fixes and current reports. Historical fixes are written by the maintainer; new reports appear after review.
- 0
- Open tickets
- 26
- Fixed in code
- Public
- Every answer, on the board
Start here
Eight situations cover most reports. Open one before you write a ticket.
Three things, in order. Keep the phone and TV on the same local network; a guest network may isolate them even when both use Wi-Fi. Turn off VPN or Private Relay while pairing. Wake the TV, because some models stop answering discovery in standby. If automatic discovery still fails, use Enter IP manually at the bottom of the TV list.
No. TV Remotely talks to the television over your home Wi-Fi using the TV's own protocol, so no IR blaster is required. The TV must already be reachable on the network; a phone app cannot replace the physical remote needed for initial setup or authorization.
Discovery. Finding TVs means sending a broadcast on your own network and listening for replies. Your TV commands go straight from the phone to the TV and are never uploaded, and there is no account. The app does send anonymous usage statistics, which you can switch off in Settings.
Each platform exposes a different set of commands. A TV may accept power and volume but refuse source switching or text entry. The Supported TVs table shows what works on each platform; if a button fails on something marked fully supported, that is worth a ticket.
Mirroring is your phone's own feature, not ours: the Cast tab opens the system picker (AirPlay on iPhone, Cast or Smart View on Android) and your phone takes it from there. So if it will not start, the TV or the network is the limit — and it is the first thing to fail on a congested 2.4 GHz network. Try casting a single video, photo or track first: if that works, the connection is fine and the problem is mirroring specifically. Fire TV sticks have a known issue on the board.
No, and deliberately. Commands go straight from your phone to the TV on your own network. Remote access would need a relay server in the middle, which is why that request was turned down on the board.
No. There is no subscription, no ads and no account, and there is nothing to sign up for. Install it and it works.
Both. The iPhone and Android apps share the same feature set. The store buttons on this site link straight to each listing as soon as it is public.
Need a step-by-step answer? Read the TV discovery guide or check supported TV platforms.
The board
Filter by status, then open a ticket for the full history.
26 tickets shown
- 00 votesFloating tablet keyboards could still cover fieldsClosedAn undocked keyboard could report no useful bottom inset, leaving the focused field hidden.TVR-134BugAndroid and iPad tabletsUpdated 26 Sept 2026
- 00 votesSony TVs could be missed by discoveryClosedSome BRAVIA devices did not expose the identity the app expected through its first discovery route.TVR-133BugSony BRAVIAUpdated 26 Sept 2026
- 00 votesAndroid TV pairing could fail with a TLS alert on some boxesClosedThe client key format was incompatible with TLS 1.3 behavior seen on a Xiaomi box.TVR-132BugAndroid TV / Google TVUpdated 26 Sept 2026
- 00 votesLarge files cast from iPhone could arrive truncatedClosedThe iOS media server closed its file handle after the first chunk of a file over 64 KB.TVR-131BugCast / iOSUpdated 26 Sept 2026
- 00 votesSaved TVs could reconnect late or show duplicate sightingsClosedDiscovery results were not used promptly and some sightings or cast descriptions remained separate.TVR-130BugDiscovery / multiple TV platformsUpdated 25 Sept 2026
- 00 votesBoth sides of the volume rocker could raise the volumeClosedTouch coordinates were interpreted relative to the wrong view.TVR-129BugRemote controls / all TVsUpdated 21 Sept 2026
- 00 votesSome Apple devices appeared in the TV listClosedMacs, iPhones, and HomePods advertise a Continuity service that was mistaken for Apple TV.TVR-128BugApple TV discoveryUpdated 21 Sept 2026
- 00 votesOlder Android TV devices could be sent to the wrong pairing protocolClosedThe legacy remote service and modern Android TV service were previously treated alike.TVR-127BugLegacy Android TVUpdated 20 Sept 2026
- 00 votesThe on-screen keyboard could cover pairing and text fieldsClosedSeveral sheets did not move their fields into view when a keyboard opened.TVR-126BugAndroid and iOSUpdated 20 Sept 2026
- 00 votesA cast could stop when the phone screen timed outClosedThe phone sleeping could interrupt the local stream that the TV was reading.TVR-125BugCast / Android and iOSUpdated 19 Sept 2026
- 00 votesAndroid TV pairing could reject the correct codeClosedThe pairing digest included extra separator bytes that real TVs did not expect.TVR-124BugAndroid TV / Google TVUpdated 19 Sept 2026
- 00 votesThe Fire TV Apps list could fail to filter on iPhoneClosediOS lacked the native package-list method used by the Apps screen.TVR-123BugAmazon Fire TV / iOSUpdated 18 Sept 2026
- 00 votesFire TV could report success when an app failed to openClosedThe ADB launch command could acknowledge a request even when the package was absent.TVR-122BugAmazon Fire TVUpdated 18 Sept 2026
- 00 votesHulu and Max shortcuts could do nothing on Android TVClosedTwo hardcoded deep links were not reliable launch routes.TVR-121BugAndroid TV / Google TVUpdated 18 Sept 2026
- 00 votesSony app shortcuts did not launch TV appsClosedApp tiles lacked the TV-specific application URI needed by BRAVIA.TVR-120BugSony BRAVIAUpdated 18 Sept 2026
- 00 votesSony could show connected while asking to pair again on each keyClosedA missing authorization cookie could be mistaken for a completed connection.TVR-119BugSony BRAVIAUpdated 18 Sept 2026
- 00 votesLG pairing could be approved but leave every key unresponsiveClosedwebOS could show Allow, then reject registration or silently ignore navigation keys.TVR-118BugLG webOSUpdated 18 Sept 2026
- 00 votesOne saved TV could appear twice in discoveryClosedA saved record and a live sighting could fail to match, especially after its network address changed.TVR-117BugDiscovery / multiple TV platformsUpdated 16 Sept 2026
- 00 votesAndroid TV showed a keyboard control it could not useClosedThe provider advertised a keyboard capability without a command channel behind it.TVR-116BugAndroid TV / Google TVUpdated 31 Aug 2026
- 00 votesThe SOURCE button did not open input choicesClosedThe remote screen failed to pass the SOURCE action to its input sheet.TVR-115BugSamsung Tizen / Sony BRAVIA / other TVsUpdated 31 Aug 2026
- 00 votesAn uninstalled TV app looked like a remote failureClosedLaunching an app absent from the TV showed a red failure notice with an unhelpful technical message.TVR-114BugApps / multiple TV platformsUpdated 31 Aug 2026
- 00 votesThe app could ignore an online saved TV at launchClosedAutomatic connection considered only the last TV and could give up after one short scan.TVR-113BugDiscovery / multiple TV platformsUpdated 31 Aug 2026
- 00 votesA TV connection could stop responding after idle or backgroundingClosedControl sockets were not recovered after an unexpected drop or after returning to the app.TVR-112BugMultiple TV platformsUpdated 31 Aug 2026
- 00 votesA cast could fail after opening the phone’s file pickerClosedOpening the picker backgrounded the app and stopped its local media server; the TV then requested a file URL that no longer existed.TVR-111BugCast / Android and iOSUpdated 31 Aug 2026
- 00 votesScreen mirroring opened a picker that could not show Samsung TVsClosedThe handoff opened Google Cast settings, which does not list Miracast-only Samsung TVs.TVR-110BugAndroid / Samsung TizenUpdated 31 Aug 2026
- 00 votesSamsung photo casting could say the TV cannot accept filesClosedA Samsung could be found for app launching while its media renderer was missed, so photo casting stopped before the picker opened.TVR-109BugSamsung TizenUpdated 31 Aug 2026