
Why Can’t My TV Find My Phone for Screen Mirroring?
Why Can’t My TV Find My Phone for Screen Mirroring?
Why Can’t My TV Find My Phone for Screen Mirroring?
TV not finding your phone for screen mirroring? Check AirPlay, Google Cast, Smart View, and Miracast compatibility, settings, and connection issues.
TV not finding your phone for screen mirroring? Check AirPlay, Google Cast, Smart View, and Miracast compatibility, settings, and connection issues.
TV not finding your phone for screen mirroring? Check AirPlay, Google Cast, Smart View, and Miracast compatibility, settings, and connection issues.
In most built-in phone-to-TV mirroring workflows, you select the TV on your phone—not the phone on your TV. If the TV is missing from that list, check that both devices support the same mirroring method, that the TV is ready to receive, and that discovery is allowed for that connection.
Start with the list you’re using. AirPlay, Google Cast, Smart View, and third-party mirroring apps don’t all find the same receivers. A TV can support one method without supporting another.
This guide is for a device that doesn’t appear in the correct list. If you can already select the TV but the connection fails, or you connect and get a black screen or no sound, you’ve moved past discovery.
In most built-in phone-to-TV mirroring workflows, you select the TV on your phone—not the phone on your TV. If the TV is missing from that list, check that both devices support the same mirroring method, that the TV is ready to receive, and that discovery is allowed for that connection.
Start with the list you’re using. AirPlay, Google Cast, Smart View, and third-party mirroring apps don’t all find the same receivers. A TV can support one method without supporting another.
This guide is for a device that doesn’t appear in the correct list. If you can already select the TV but the connection fails, or you connect and get a black screen or no sound, you’ve moved past discovery.
In most built-in phone-to-TV mirroring workflows, you select the TV on your phone—not the phone on your TV. If the TV is missing from that list, check that both devices support the same mirroring method, that the TV is ready to receive, and that discovery is allowed for that connection.
Start with the list you’re using. AirPlay, Google Cast, Smart View, and third-party mirroring apps don’t all find the same receivers. A TV can support one method without supporting another.
This guide is for a device that doesn’t appear in the correct list. If you can already select the TV but the connection fails, or you connect and get a black screen or no sound, you’ve moved past discovery.
First, Make Sure You’re Looking in the Right Device List
First, Make Sure You’re Looking in the Right Device List
First, Make Sure You’re Looking in the Right Device List
Before changing settings, match your phone’s sending feature to the TV’s receiving capability. Check the TV’s exact model and regional specifications, not just whether it is a “smart TV.” If you use a streaming device plugged into the TV, check that device’s support too.
You’re using | Where to look | What the receiver needs |
iPhone Screen Mirroring | Control Center → Screen Mirroring on the iPhone | AirPlay support on the TV or attached receiver |
Cast button in a Google Cast-enabled app | That app’s Cast device list | Google Cast support |
Galaxy Smart View | The phone’s Smart View device list | A receiver compatible with that phone’s supported mirroring method |
Android phone with confirmed Miracast support | Your phone’s documented wireless-display list | Miracast receiving support |
A third-party mirroring app | The app’s documented device or pairing screen | The receiver setup required by that app |
If you use Android’s system-level Screen Cast, check your phone manufacturer’s documentation to identify the protocol and confirm full-screen casting support. Then match it to a Google Cast or Miracast receiver. The menu name alone isn’t enough.

App casting and whole-screen mirroring are also different tasks. Casting a YouTube video from an iPhone through Google Cast does not mean that receiver will appear in the iPhone’s Screen Mirroring list. That list uses AirPlay.
Wrong list? Switch to the appropriate sending feature.
Matching support on both ends? Continue below.
Confirmed mismatch? Skip to the final section; restarting the router won’t add a missing protocol.
Before changing settings, match your phone’s sending feature to the TV’s receiving capability. Check the TV’s exact model and regional specifications, not just whether it is a “smart TV.” If you use a streaming device plugged into the TV, check that device’s support too.
You’re using | Where to look | What the receiver needs |
iPhone Screen Mirroring | Control Center → Screen Mirroring on the iPhone | AirPlay support on the TV or attached receiver |
Cast button in a Google Cast-enabled app | That app’s Cast device list | Google Cast support |
Galaxy Smart View | The phone’s Smart View device list | A receiver compatible with that phone’s supported mirroring method |
Android phone with confirmed Miracast support | Your phone’s documented wireless-display list | Miracast receiving support |
A third-party mirroring app | The app’s documented device or pairing screen | The receiver setup required by that app |
If you use Android’s system-level Screen Cast, check your phone manufacturer’s documentation to identify the protocol and confirm full-screen casting support. Then match it to a Google Cast or Miracast receiver. The menu name alone isn’t enough.

App casting and whole-screen mirroring are also different tasks. Casting a YouTube video from an iPhone through Google Cast does not mean that receiver will appear in the iPhone’s Screen Mirroring list. That list uses AirPlay.
Wrong list? Switch to the appropriate sending feature.
Matching support on both ends? Continue below.
Confirmed mismatch? Skip to the final section; restarting the router won’t add a missing protocol.
Before changing settings, match your phone’s sending feature to the TV’s receiving capability. Check the TV’s exact model and regional specifications, not just whether it is a “smart TV.” If you use a streaming device plugged into the TV, check that device’s support too.
You’re using | Where to look | What the receiver needs |
iPhone Screen Mirroring | Control Center → Screen Mirroring on the iPhone | AirPlay support on the TV or attached receiver |
Cast button in a Google Cast-enabled app | That app’s Cast device list | Google Cast support |
Galaxy Smart View | The phone’s Smart View device list | A receiver compatible with that phone’s supported mirroring method |
Android phone with confirmed Miracast support | Your phone’s documented wireless-display list | Miracast receiving support |
A third-party mirroring app | The app’s documented device or pairing screen | The receiver setup required by that app |
If you use Android’s system-level Screen Cast, check your phone manufacturer’s documentation to identify the protocol and confirm full-screen casting support. Then match it to a Google Cast or Miracast receiver. The menu name alone isn’t enough.

App casting and whole-screen mirroring are also different tasks. Casting a YouTube video from an iPhone through Google Cast does not mean that receiver will appear in the iPhone’s Screen Mirroring list. That list uses AirPlay.
Wrong list? Switch to the appropriate sending feature.
Matching support on both ends? Continue below.
Confirmed mismatch? Skip to the final section; restarting the router won’t add a missing protocol.
Check That Your TV Is Ready to Appear in That List
Check That Your TV Is Ready to Appear in That List
Check That Your TV Is Ready to Appear in That List
Follow only the branch for your connection. You don’t need to try all four methods.
iPhone Screen Mirroring: Check the TV’s AirPlay Receiver
Wake the TV and make sure its AirPlay receiving feature is enabled. The setting’s location varies by model; use the TV manual rather than looking for a universal menu path.

For a typical home setup, make sure your iPhone and AirPlay receiver are on the same reachable home network. Apple recommends using the same Wi-Fi network. If the receiver uses Ethernet, check that it can communicate with your iPhone over the local network. If the receiver is managed through the Home app, check whether its Speakers & TV access settings restrict who can use AirPlay.
An external receiver must be powered, connected as required, and running its receiving service. Switch the TV to its HDMI input so you can see the receiver’s interface, code, or prompts. Choosing that input helps you see what’s happening; it isn’t, by itself, a general requirement for wireless discovery.
Reopen Screen Mirroring after the change. Once the receiver appears, select it and follow any on-screen code prompt. A code or connection rejection is a different issue from a missing device.
Google Cast: Check Receiver Setup and App Discovery Permission
Confirm that the TV or attached device supports Google Cast and has completed its required setup. Being connected to the internet doesn’t establish that its Cast receiver is ready.
For app-based casting, put the phone and receiver on the same Wi-Fi network, then open a Google Cast-enabled app. Google’s app-casting instructions describe this media-casting workflow; they don’t establish full-screen mirroring support for every Android phone.
On an iPhone or iPad, check the sending app’s local-network permission:
Settings → Privacy & Security → Local Network → enable the relevant app.

Google provides these steps in Troubleshoot missing devices on iPhone & iPad. Reopen the app and check its Cast list again. This is an app permission check, not a universal fix for native AirPlay discovery.
Smart View or Miracast: Check the Supported Sender and TV Receive Mode
For Galaxy Smart View, follow the requirements for your phone and TV. Samsung’s current screen-mirroring guidance calls for the same Wi-Fi network. If your TV requires a screen-mirroring receiving mode, open it before searching. Smart View isn’t available on every Android device.
For another confirmed Miracast setup, use the TV’s documented receiving mode. It may be labeled Screen Mirroring, Screen Share, or Wireless Display; the exact feature matters more than the wording. Keep the required wireless functions enabled.

Don’t apply Samsung’s network instructions to every Miracast implementation. The Wi-Fi Alliance’s Miracast overview confirms that Miracast can work without an existing Wi-Fi network. Follow your devices’ documented connection path rather than assuming a router change is necessary.
If the TV displays an Allow/Deny prompt, or you know the phone was previously blocked, check that model’s access or device-list settings. Keep manual approval enabled. There’s no reason to disable all connection notifications just to troubleshoot one phone.
Third-Party Mirroring Apps: Check the App’s Own Receiving Screen
Check which device the app expects to act as the receiver. If it requires a TV receiver app, open that app and leave it on its receiving screen. The TV’s native AirPlay or Miracast menu may not serve the app’s connection method.
Follow the app’s documented network and discovery-permission requirements. Use a QR code, pairing code, or manual address only if that product supports it. A code can identify a receiver without automatically making an otherwise unreachable network path work.
Follow only the branch for your connection. You don’t need to try all four methods.
iPhone Screen Mirroring: Check the TV’s AirPlay Receiver
Wake the TV and make sure its AirPlay receiving feature is enabled. The setting’s location varies by model; use the TV manual rather than looking for a universal menu path.

For a typical home setup, make sure your iPhone and AirPlay receiver are on the same reachable home network. Apple recommends using the same Wi-Fi network. If the receiver uses Ethernet, check that it can communicate with your iPhone over the local network. If the receiver is managed through the Home app, check whether its Speakers & TV access settings restrict who can use AirPlay.
An external receiver must be powered, connected as required, and running its receiving service. Switch the TV to its HDMI input so you can see the receiver’s interface, code, or prompts. Choosing that input helps you see what’s happening; it isn’t, by itself, a general requirement for wireless discovery.
Reopen Screen Mirroring after the change. Once the receiver appears, select it and follow any on-screen code prompt. A code or connection rejection is a different issue from a missing device.
Google Cast: Check Receiver Setup and App Discovery Permission
Confirm that the TV or attached device supports Google Cast and has completed its required setup. Being connected to the internet doesn’t establish that its Cast receiver is ready.
For app-based casting, put the phone and receiver on the same Wi-Fi network, then open a Google Cast-enabled app. Google’s app-casting instructions describe this media-casting workflow; they don’t establish full-screen mirroring support for every Android phone.
On an iPhone or iPad, check the sending app’s local-network permission:
Settings → Privacy & Security → Local Network → enable the relevant app.

Google provides these steps in Troubleshoot missing devices on iPhone & iPad. Reopen the app and check its Cast list again. This is an app permission check, not a universal fix for native AirPlay discovery.
Smart View or Miracast: Check the Supported Sender and TV Receive Mode
For Galaxy Smart View, follow the requirements for your phone and TV. Samsung’s current screen-mirroring guidance calls for the same Wi-Fi network. If your TV requires a screen-mirroring receiving mode, open it before searching. Smart View isn’t available on every Android device.
For another confirmed Miracast setup, use the TV’s documented receiving mode. It may be labeled Screen Mirroring, Screen Share, or Wireless Display; the exact feature matters more than the wording. Keep the required wireless functions enabled.

Don’t apply Samsung’s network instructions to every Miracast implementation. The Wi-Fi Alliance’s Miracast overview confirms that Miracast can work without an existing Wi-Fi network. Follow your devices’ documented connection path rather than assuming a router change is necessary.
If the TV displays an Allow/Deny prompt, or you know the phone was previously blocked, check that model’s access or device-list settings. Keep manual approval enabled. There’s no reason to disable all connection notifications just to troubleshoot one phone.
Third-Party Mirroring Apps: Check the App’s Own Receiving Screen
Check which device the app expects to act as the receiver. If it requires a TV receiver app, open that app and leave it on its receiving screen. The TV’s native AirPlay or Miracast menu may not serve the app’s connection method.
Follow the app’s documented network and discovery-permission requirements. Use a QR code, pairing code, or manual address only if that product supports it. A code can identify a receiver without automatically making an otherwise unreachable network path work.
Follow only the branch for your connection. You don’t need to try all four methods.
iPhone Screen Mirroring: Check the TV’s AirPlay Receiver
Wake the TV and make sure its AirPlay receiving feature is enabled. The setting’s location varies by model; use the TV manual rather than looking for a universal menu path.

For a typical home setup, make sure your iPhone and AirPlay receiver are on the same reachable home network. Apple recommends using the same Wi-Fi network. If the receiver uses Ethernet, check that it can communicate with your iPhone over the local network. If the receiver is managed through the Home app, check whether its Speakers & TV access settings restrict who can use AirPlay.
An external receiver must be powered, connected as required, and running its receiving service. Switch the TV to its HDMI input so you can see the receiver’s interface, code, or prompts. Choosing that input helps you see what’s happening; it isn’t, by itself, a general requirement for wireless discovery.
Reopen Screen Mirroring after the change. Once the receiver appears, select it and follow any on-screen code prompt. A code or connection rejection is a different issue from a missing device.
Google Cast: Check Receiver Setup and App Discovery Permission
Confirm that the TV or attached device supports Google Cast and has completed its required setup. Being connected to the internet doesn’t establish that its Cast receiver is ready.
For app-based casting, put the phone and receiver on the same Wi-Fi network, then open a Google Cast-enabled app. Google’s app-casting instructions describe this media-casting workflow; they don’t establish full-screen mirroring support for every Android phone.
On an iPhone or iPad, check the sending app’s local-network permission:
Settings → Privacy & Security → Local Network → enable the relevant app.

Google provides these steps in Troubleshoot missing devices on iPhone & iPad. Reopen the app and check its Cast list again. This is an app permission check, not a universal fix for native AirPlay discovery.
Smart View or Miracast: Check the Supported Sender and TV Receive Mode
For Galaxy Smart View, follow the requirements for your phone and TV. Samsung’s current screen-mirroring guidance calls for the same Wi-Fi network. If your TV requires a screen-mirroring receiving mode, open it before searching. Smart View isn’t available on every Android device.
For another confirmed Miracast setup, use the TV’s documented receiving mode. It may be labeled Screen Mirroring, Screen Share, or Wireless Display; the exact feature matters more than the wording. Keep the required wireless functions enabled.

Don’t apply Samsung’s network instructions to every Miracast implementation. The Wi-Fi Alliance’s Miracast overview confirms that Miracast can work without an existing Wi-Fi network. Follow your devices’ documented connection path rather than assuming a router change is necessary.
If the TV displays an Allow/Deny prompt, or you know the phone was previously blocked, check that model’s access or device-list settings. Keep manual approval enabled. There’s no reason to disable all connection notifications just to troubleshoot one phone.
Third-Party Mirroring Apps: Check the App’s Own Receiving Screen
Check which device the app expects to act as the receiver. If it requires a TV receiver app, open that app and leave it on its receiving screen. The TV’s native AirPlay or Miracast menu may not serve the app’s connection method.
Follow the app’s documented network and discovery-permission requirements. Use a QR code, pairing code, or manual address only if that product supports it. A code can identify a receiver without automatically making an otherwise unreachable network path work.
Still Missing? Use One Controlled Test to Narrow Down the Cause
Still Missing? Use One Controlled Test to Narrow Down the Cause
Still Missing? Use One Controlled Test to Narrow Down the Cause
For a connection that depends on the local network, first check whether a guest network or AP/client isolation prevents devices from communicating. Both devices can have internet access while remaining invisible to each other. Google documents this restriction in its Cast setup guidance.
Don’t assume both devices must use 2.4 GHz. The relevant question is whether the network allows communication for your connection method. If a VPN may be blocking local access, temporarily disconnect it on a trusted home network and retry. On a work, school, or hotel network, ask the administrator or use an authorized network that permits device communication; don’t bypass security restrictions.
If you have a spare device, choose one test you can perform: try another compatible phone with the same TV, or try your phone with another compatible receiver. Keep the protocol and task the same. Testing app-based media casting against full-screen mirroring would not be a like-for-like comparison.
The table shows possible results, not a sequence of tests to complete. The multiple-combination row is useful only if you have already observed that result—you don’t need to run extra tests to reach it.
Test result | What to investigate next |
Another compatible phone finds the same TV using the same method | Prioritize the original phone’s entry point, permissions, and device-specific support. |
Your phone finds another compatible receiver using the same method | Prioritize the original TV’s receiving state and model-specific settings. |
Several confirmed-compatible combinations already failed on the same LAN-dependent path | Investigate shared network restrictions or receiver setup. |
The target TV appears in the correct list | Stop discovery troubleshooting and proceed to connection. |
These results narrow the next check; they don’t prove a single cause. Differences in software, permissions, and receiver capabilities still matter. A LAN-based result also doesn’t diagnose a Miracast connection that bypasses that network.
No spare device? Skip the comparison. Restart the phone and receiver, check for manufacturer-recommended updates, and retry the original list.
Consider a factory reset only as a last resort. It can erase local data and settings and require setup again, without fixing a protocol mismatch. Check the manufacturer’s guidance and back up important data before deciding.
For a connection that depends on the local network, first check whether a guest network or AP/client isolation prevents devices from communicating. Both devices can have internet access while remaining invisible to each other. Google documents this restriction in its Cast setup guidance.
Don’t assume both devices must use 2.4 GHz. The relevant question is whether the network allows communication for your connection method. If a VPN may be blocking local access, temporarily disconnect it on a trusted home network and retry. On a work, school, or hotel network, ask the administrator or use an authorized network that permits device communication; don’t bypass security restrictions.
If you have a spare device, choose one test you can perform: try another compatible phone with the same TV, or try your phone with another compatible receiver. Keep the protocol and task the same. Testing app-based media casting against full-screen mirroring would not be a like-for-like comparison.
The table shows possible results, not a sequence of tests to complete. The multiple-combination row is useful only if you have already observed that result—you don’t need to run extra tests to reach it.
Test result | What to investigate next |
Another compatible phone finds the same TV using the same method | Prioritize the original phone’s entry point, permissions, and device-specific support. |
Your phone finds another compatible receiver using the same method | Prioritize the original TV’s receiving state and model-specific settings. |
Several confirmed-compatible combinations already failed on the same LAN-dependent path | Investigate shared network restrictions or receiver setup. |
The target TV appears in the correct list | Stop discovery troubleshooting and proceed to connection. |
These results narrow the next check; they don’t prove a single cause. Differences in software, permissions, and receiver capabilities still matter. A LAN-based result also doesn’t diagnose a Miracast connection that bypasses that network.
No spare device? Skip the comparison. Restart the phone and receiver, check for manufacturer-recommended updates, and retry the original list.
Consider a factory reset only as a last resort. It can erase local data and settings and require setup again, without fixing a protocol mismatch. Check the manufacturer’s guidance and back up important data before deciding.
For a connection that depends on the local network, first check whether a guest network or AP/client isolation prevents devices from communicating. Both devices can have internet access while remaining invisible to each other. Google documents this restriction in its Cast setup guidance.
Don’t assume both devices must use 2.4 GHz. The relevant question is whether the network allows communication for your connection method. If a VPN may be blocking local access, temporarily disconnect it on a trusted home network and retry. On a work, school, or hotel network, ask the administrator or use an authorized network that permits device communication; don’t bypass security restrictions.
If you have a spare device, choose one test you can perform: try another compatible phone with the same TV, or try your phone with another compatible receiver. Keep the protocol and task the same. Testing app-based media casting against full-screen mirroring would not be a like-for-like comparison.
The table shows possible results, not a sequence of tests to complete. The multiple-combination row is useful only if you have already observed that result—you don’t need to run extra tests to reach it.
Test result | What to investigate next |
Another compatible phone finds the same TV using the same method | Prioritize the original phone’s entry point, permissions, and device-specific support. |
Your phone finds another compatible receiver using the same method | Prioritize the original TV’s receiving state and model-specific settings. |
Several confirmed-compatible combinations already failed on the same LAN-dependent path | Investigate shared network restrictions or receiver setup. |
The target TV appears in the correct list | Stop discovery troubleshooting and proceed to connection. |
These results narrow the next check; they don’t prove a single cause. Differences in software, permissions, and receiver capabilities still matter. A LAN-based result also doesn’t diagnose a Miracast connection that bypasses that network.
No spare device? Skip the comparison. Restart the phone and receiver, check for manufacturer-recommended updates, and retry the original list.
Consider a factory reset only as a last resort. It can erase local data and settings and require setup again, without fixing a protocol mismatch. Check the manufacturer’s guidance and back up important data before deciding.
Know When to Stop Searching and Use a Different Path
Know When to Stop Searching and Use a Different Path
Know When to Stop Searching and Use a Different Path
The TV appears: discovery is working. Select it and follow the connection prompts. If it rejects the connection, switch to troubleshooting for that protocol and device combination rather than repeating discovery checks.
The devices don’t support the same method: choose a compatible path. That might be an external receiver supporting your phone’s protocol, a third-party solution that supports both devices, or a wired connection if your phone supports video output. Check the exact hardware requirements before buying; a USB-C or Lightning connector alone doesn’t establish HDMI-output compatibility.
Support is confirmed, but the TV stays missing: take the phone model, OS version, TV or receiver model, sending feature, and network details to the relevant protocol guide or manufacturer support. If you still need help identifying the failure stage, use the device-by-device troubleshooting guide.
Once your TV appears in the list, discovery is no longer the problem. If the connection fails or the picture doesn’t work correctly, follow troubleshooting for that specific symptom.
The TV appears: discovery is working. Select it and follow the connection prompts. If it rejects the connection, switch to troubleshooting for that protocol and device combination rather than repeating discovery checks.
The devices don’t support the same method: choose a compatible path. That might be an external receiver supporting your phone’s protocol, a third-party solution that supports both devices, or a wired connection if your phone supports video output. Check the exact hardware requirements before buying; a USB-C or Lightning connector alone doesn’t establish HDMI-output compatibility.
Support is confirmed, but the TV stays missing: take the phone model, OS version, TV or receiver model, sending feature, and network details to the relevant protocol guide or manufacturer support. If you still need help identifying the failure stage, use the device-by-device troubleshooting guide.
Once your TV appears in the list, discovery is no longer the problem. If the connection fails or the picture doesn’t work correctly, follow troubleshooting for that specific symptom.
The TV appears: discovery is working. Select it and follow the connection prompts. If it rejects the connection, switch to troubleshooting for that protocol and device combination rather than repeating discovery checks.
The devices don’t support the same method: choose a compatible path. That might be an external receiver supporting your phone’s protocol, a third-party solution that supports both devices, or a wired connection if your phone supports video output. Check the exact hardware requirements before buying; a USB-C or Lightning connector alone doesn’t establish HDMI-output compatibility.
Support is confirmed, but the TV stays missing: take the phone model, OS version, TV or receiver model, sending feature, and network details to the relevant protocol guide or manufacturer support. If you still need help identifying the failure stage, use the device-by-device troubleshooting guide.
Once your TV appears in the list, discovery is no longer the problem. If the connection fails or the picture doesn’t work correctly, follow troubleshooting for that specific symptom.
Table of content
Table of content

Still Need a Hand?
Still Need a Hand?
Still Need a Hand?
Explore more reviews, step-by-step guides, and troubleshooting tips—or contact us if you could not find the answer you needed.
Explore more reviews, step-by-step guides, and troubleshooting tips—or contact us if you could not find the answer you needed.
Explore more reviews, step-by-step guides, and troubleshooting tips—or contact us if you could not find the answer you needed.
