You have lost the remote, or the batteries are dead, and the manufacturer’s app on your phone refuses to find the television. The app is usually fine; what stops it is almost always something about how your network is arranged, and the app tells you nothing useful about which.
The short answer
The phone and the television must be on the same network segment. Guest networks, separate 2.4 and 5 GHz networks with client isolation, VPNs and mobile data are the four things that break this, and all four look identical from the app’s point of view. Get both devices onto the same main network with the phone on Wi-Fi rather than mobile data, and most failures resolve.
How these apps find your television
The app broadcasts a discovery message across the local network and listens for the television to answer. That message does not cross between network segments, does not travel over the internet, and is frequently blocked by isolation features. So anything that separates the phone from the television, even while both have working internet, stops discovery dead.
This is why the app works one day and not the next: the phone silently switched to mobile data, or joined the guest network, or a VPN came on.
Confirm the phone is on Wi-Fi, not mobile data
Turn mobile data off entirely while testing. A phone that has fallen back to mobile data cannot see anything on your home network, and the app will simply report that it found nothing.
Check both are on the same network
If your router broadcasts separate 2.4 and 5 GHz networks, the television is probably on 2.4 GHz and your phone on 5 GHz. On most routers these are the same segment and discovery works, but on some they are separated. Join the phone to the same network name as the television to rule it out.
Get off the guest network
Guest networks isolate devices by design. If either the phone or the television is on guest, discovery will never work. This is the single most common cause once mobile data is ruled out.
Turn off any VPN or private DNS
A VPN routes your phone’s traffic elsewhere and usually breaks local discovery entirely. Turn it fully off rather than pausing it, and turn off private DNS as well.
Enable the TV's remote control setting
Most televisions have a setting permitting control from mobile devices, sometimes called mobile app control, network remote, or similar. It is not always on by default, and a factory reset or software update can turn it off.
Grant the app local network permission
Both phone platforms now require explicit permission for apps to communicate on the local network. If it was declined at first launch, the app cannot discover anything and gives no clear explanation. Check it in the app’s permissions.
Check for AP isolation on your router
Some routers have client isolation enabled on the main network, not only on guest. Look for AP isolation, client isolation or similar in the wireless settings and turn it off.
Restart both, television first
Power cycle the television at the wall, let it fully reconnect, then restart the phone. Discovery services can get stuck on both ends.
If the app finds the television but pairing fails, look at the television screen. Many require you to confirm a code or accept a pairing prompt that appears on the TV, and if the television is on a different input you will never see it. Switch to the television’s home screen before pairing.
Alternatives while you sort it out
- HDMI-CEC. If you have a streaming box or console with a working remote, its remote may be able to control the television’s power and volume over CEC.
- The buttons on the television. Every set has physical controls, usually a single multi-function button underneath or behind the panel on the right-hand side. It is fiddly and it works.
- A universal remote. Inexpensive and, for an older television, often a better long-term answer than an app that depends on your network being arranged correctly.
- A phone with an infrared blaster. Rare now, but some phones have one, and it controls televisions directly without any network involvement.
Be wary of third-party universal remote apps that promise to control any television. Most rely on either infrared, which your phone probably lacks, or the same network discovery that is already failing. They will not succeed where the manufacturer’s own app does not.
Making it reliable
If you intend to rely on the app, a few things make it dependable rather than occasional: reserve a fixed IP address for the television in your router, so it does not move; keep the television on the main network rather than guest; and make sure your phone is not set to switch to mobile data whenever Wi-Fi is weak, which many phones do automatically and which silently breaks discovery.
Why can my phone not find my TV?
Almost always a network separation problem: mobile data, a guest network, a VPN, or client isolation on the router. All four look the same from the app, which just reports that nothing was found.
Does the app need internet to work?
No, it needs the phone and television on the same local network. It will work with the internet down entirely, provided both are connected to the router.
Why did it stop working after I changed routers?
The television is probably on a different network name, or the new router has client isolation on. Check both are on the same network and look for an isolation setting.
Can I control the TV from outside the house?
Generally not with these apps, which are designed for local control only. Some manufacturers offer limited remote features through a cloud account, but the remote itself is local.
What if I have lost the remote entirely?
Use the physical buttons on the television to get into the settings, enable network remote control, then pair the app. A replacement remote or a universal one is worth ordering as a backup.
The bottom line
Turn mobile data off, get the phone and the television onto the same main network, and turn off any VPN. Those three cover most failures. Then check the app has local network permission and that the television’s network remote setting is enabled, since both are easy to miss and neither gives a useful error.
