My phone used to work as a TV remote, but now it won’t connect to my smart TV. Both devices seem to be on the same Wi-Fi, and I’ve tried restarting the app and TV. I need help figuring out why my phone remote app isn’t pairing or controlling the TV.
The first thing to check is the boring one: make sure the phone and TV are actually on the same Wi-Fi. A lot of “the app can’t find my TV” problems come down to that.
Watch out for the usual gotchas:
- The phone is connected to 5GHz and the TV is on 2.4GHz. Depending on the router, those may act like separate networks. Try putting the phone on 2.4GHz too.
- One device is on a guest network.
- Your phone quietly switched to mobile data, or you have a VPN running. Turn those off for the test and confirm Wi-Fi is active.
- If you use a mesh router, make sure both devices are on the same SSID and not being isolated by the system.
After that, restart both devices. Don’t just turn the TV off with the remote. Unplug it for about 30 seconds, then plug it back in. Restart the phone too. It sounds too simple, but it clears a lot of weird network discovery issues.
Also check the TV settings. Some TVs don’t allow app control until you enable it manually.
- Samsung: Settings → General/Connection → look for “Remote/mobile control” or “Device Connection Manager” and make sure it’s enabled.
- LG: Check Mobile TV On and network standby settings.
- Roku: Settings → System → Advanced → “Control by mobile apps” should be Enabled or Permissive.
- Fire TV: Make sure it’s powered on and awake, not asleep in the background.
If everything looks right and the app still sees nothing, check the router. Settings like AP Isolation, Client Isolation, or AP/station isolation can block devices on the same Wi-Fi from talking to each other. If that’s enabled, the phone app won’t be able to detect the TV at all.
It’s also worth updating the basics: the remote app, the TV firmware, and the phone OS. A mismatched or outdated version can break pairing even when the network is fine.
If the TV showed up before but won’t connect now, remove it from the app and add it again. On the first pairing attempt, many TVs show a 4-digit code on the screen that you need to enter on the phone, so don’t skip that part.
One useful test is trying a different remote app. If the official app is being flaky, something like TVRem can help narrow it down. It supports Samsung, LG, Roku, Fire TV, Android/Google TV, and Apple TV. If one app connects and the other doesn’t, your network is probably fine and the issue is with the app itself.
One last reality check: the TV has to be a smart TV and it has to be connected to the network. If it’s an older non-smart TV, or it’s not on Wi-Fi/Ethernet, a phone app won’t find it. In that case you’ll need the original remote or a universal remote.
If you share the TV brand/model and what happens in the app, like whether it finds nothing, finds the TV but won’t pair, or connects and then drops, it should be easier to pin down.
25 Likes
Your phone OS matters here, because the app can be blocked before it ever reaches the TV.
The Wi-Fi checks mentioned above are valid, but if this suddenly stopped after a phone update or app reinstall, I’d look at permissions next. On iPhone, go to Settings, find the remote app, and make sure Local Network is turned on. If that permission is off, the app may act like your TV doesn’t exist even when both devices are on the same router. On Android, check the app permissions too, especially Nearby devices and sometimes Location, since some apps use that for device discovery.
I’d also clear the saved pairing on both ends if the TV has a list of allowed phones. Some TVs keep an old authorization token, so the app “sees” the TV but fails when connecting. Delete the TV from the phone app, remove the phone from the TV’s allowed devices list if that menu exists, then pair again while the TV screen is on and unlocked.
A quick workaround is to try casting from YouTube or another app to the TV. If casting works but the remote app doesn’t, the network is probably fine and the issue is more likely app permission, pairing, or that specific remote app being broken after an update. If casting fails too, then I’d go back to router isolation or guest Wi-Fi as the main suspect.
The downside of “instant on” and power-saving modes is that the TV can look connected in its network menu while the little service that accepts phone-remote commands is asleep or stuck.
That’s different from the TV being off Wi-Fi. The TV may still show an IP address, Netflix may still work, and the remote app may still fail. A lot of smart TVs have separate settings for network wake, mobile control, standby control, quick start, eco mode, and “wake on LAN” type behavior. If one of those changed after a firmware update, the phone app may only connect when the TV is fully awake, or not at all from standby.
I agree with the permission and pairing advice above, but I wouldn’t get too hung up on 2.4 GHz versus 5 GHz by itself. On a normal home router, those bands can still be the same network. The real problem is when the router treats them like separate client groups or blocks discovery traffic between them. Phone remote apps often depend on broadcast/multicast discovery, so they can fail even when both devices technically have internet.
A quick way to separate those problems:
- Turn the TV on with the physical remote.
- Open the remote app while the TV is already awake.
- If the app connects only while the TV is awake, check TV settings for quick start, mobile control, network standby, wake over Wi-Fi, eco mode, or deep sleep.
- If the app still cannot find it, look for a manual IP option in the app, if it has one.
- Compare the TV’s IP address and the phone’s IP address. They should usually start the same way, like 192.168.1.x and 192.168.1.y. If one is 192.168.0.x and the other is 192.168.50.x, they may not really be on the same local network.
Another boring but useful check: if the TV is wired by Ethernet and the phone is on Wi-Fi, don’t assume they can see each other. Some routers keep wired, wireless, guest, and mesh nodes separated depending on settings. Internet access will still work, which makes this confusing. The phone needs local access to the TV, not just internet access.
If your router has settings like IGMP snooping, multicast filtering, wireless isolation, guest isolation, “IoT network,” or “smart home protection,” those can break remote apps too. I would not start flipping every advanced setting blindly, but if this stopped after a router update or you recently moved the TV to an IoT/guest network, that is a strong suspect.
There’s a smaller edge case people miss: the TV may have a full list of paired phones or remembered controllers. If the app says something like “connecting” forever instead of “TV not found,” the TV might be rejecting the old pairing rather than failing discovery. In that case, removing the phone from the TV’s device list matters more than reinstalling the app. Reinstalling only clears the phone side.
For a fast workaround, try the TV maker’s official app and the platform app, not just a generic remote app. For example, a Roku TV may respond better to the Roku app than a universal app. A Google TV may work through Google Home or the Google TV app. Samsung and LG have their own apps. Universal apps are fine for testing, but they can fail when the TV brand changes its pairing method or permissions.
If you want the least annoying path, do this in order:
Unplug the TV from power for a full minute, not just standby. Restart the phone. Turn off VPN temporarily. Open the TV’s network status page and write down its IP address. Then open the remote app with the TV screen already on. If it appears, delete and re-pair it. If it does not appear, try entering the IP manually if the app supports that. If manual IP works, your Wi-Fi is probably fine and discovery is the problem. If manual IP does not work either, the TV is blocking app control or the devices are separated on the network.
The exact TV brand matters here because “phone can’t connect” can mean three different failures: the app can’t discover the TV, it discovers it but pairing fails, or it pairs but won’t wake/control it later. Those point to different fixes. If you post the brand and whether the TV appears in the app at all, people can give a much less generic answer.
Power-cycle the router/access point too, not just the TV and phone. A lot of these remote apps depend on local discovery, and the router can be the thing holding stale device info even though normal internet still works fine.
Do it in a clean order: close the remote app, unplug the TV from power, reboot the router, wait until Wi-Fi is fully back, plug the TV back in, then connect the phone to Wi-Fi and open the app while the TV is already on. Don’t use the TV’s standby button for this test. Give the TV a minute after it boots because some of them connect to Wi-Fi before the app-control service is actually ready.
If that fixes it and then it breaks again later, I’d look at DHCP/IP changes. Some remote apps seem to remember the TV by its old local address and get confused after the router hands out a new one. Setting a DHCP reservation for the TV in the router can make it more stable. I would try that before doing a full TV factory reset, because factory resets are annoying and usually don’t fix a flaky router discovery problem anyway.
Try entering your TV’s IP address manually if your remote app offers this option.
For a Roku TV, use your physical remote to open Settings > Network > About and note the IP address. On your phone, open the Roku app, tap Devices, then Get help?, then Connect manually. Enter the address and tap Connect.
Double-check teh numbers befor submitting. This gives you a different next step without repeating the restarts or changing router settings.