ADB will not connect to my TV
· 2 min read
adb connect fails more often than it should, and almost always for one of
these eight reasons, in order of how often they actually occur.
1. Different networks
Computer and television have to be on the same local network. It is not enough
that both "have internet". Check the first three numbers of the IP match: if the
television is 192.168.1.45 and your laptop is 192.168.0.12, they will not
see each other.
Especially common: laptop on the guest network, television on the main one.
2. Debugging switched itself off
Many televisions turn network debugging off on reboot. It is the first thing to re-check in Developer options.
3. The IP changed
The router hands out addresses by DHCP and does not always give the same one. If it worked yesterday and not today, start here. Reserving a fixed address in the router settles it for good.
4. You did not accept the dialogue
If adb devices says unauthorized, there is a dialogue waiting on the
television screen. Go back to the home screen — you cannot see it from inside a
full-screen app — and accept it.
5. The ADB server is stuck
adb kill-server
adb start-server
adb connect 192.168.1.45:5555
Fixes more cases than seems reasonable.
6. Firewall
On Windows, Defender Firewall blocks ADB frequently. Check it has permission on private networks.
7. A different port
The standard is 5555, but some models use another and show it on screen when you enable debugging. Use it exactly as displayed.
8. It is not an Android TV
If nothing works, check that it actually is one. A Samsung on Tizen or an LG on webOS will never answer, whatever you do. We cover it in this article.
Status offline
If adb devices says offline, the connection was made but the device is not
answering:
adb disconnect
adb connect 192.168.1.45:5555
And if it persists, reboot the television.