What we're fixing, building, and turning down.

Three things, in order. Keep the phone and the TV on the same Wi-Fi network — a 2.4 GHz guest network and a 5 GHz main network count as different. Turn off VPN or Private Relay while pairing. And wake the TV, because some models stop answering discovery in standby. If the network hides broadcast traffic entirely, use Enter IP manually at the bottom of the TV list.

No. TV Remotly talks to the television over your Wi-Fi, so it works on any phone. The trade-off is that a TV with no network connection cannot be controlled at all — that is a limitation of the approach, not a bug.

Discovery. Finding TVs means sending a broadcast on your own network and listening for replies. Nothing is uploaded, there is no account, and the app has no server to send anything to.

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 is confirmed per platform; if a button fails on something marked fully supported, that is worth a ticket.

Mirroring depends on what the TV supports, 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 account, and nothing to sign up for. Download it and it works.

The developer account is in review. The iOS build follows the same feature set; the App Store button turns on the day it is approved.