Advanced use and troubleshooting
Yearn on a TV: check picture and delay with iPhone screen mirroring
Use Apple’s system screen mirroring to show Yearn on a compatible TV, then check connection, orientation, audio and input delay separately.
On this page
To put Yearn's game display on a TV, start with the iPhone or iPad's system screen mirroring. It displays the current device screen on a compatible receiver and lets you assess the larger image and controller use. Smooth results depend on local performance, the wireless network and TV display settings together.
Prepare a device that supports screen mirroring
Confirm that the TV, Apple TV or other receiver supports Apple's screen mirroring, and enable it according to that device's instructions. Connect the iPhone or iPad and receiver to the same wireless network where they can discover one another. Hotel or public networks may isolate devices, so an identical network name does not guarantee that they can connect.
For the first setup, place phone and TV fairly close so that weak coverage and compatibility are not tested simultaneously. Prepare a game you already own that runs normally on the phone. Play briefly to confirm picture, sound and button response before connecting, giving you a clear local reference for any later problem.
Establish the system connection in Control Center
Open Control Center on the iPhone or iPad, choose Screen Mirroring, then select the TV or receiver. If a code appears on the TV, enter it on the phone as prompted. Apple provides these system controls; their appearance may vary with the system version.
After connecting, stay on the Home Screen or an ordinary page and confirm that the TV shows the same content. Then open Yearn and the test game. Establishing system mirroring first separates two problems: the TV is not connected, or the game is connected but displayed unsuitably.
Understand whole-screen mirroring first
System screen mirroring follows the device's current screen. Opening Control Center, switching apps or showing a system prompt may also appear on the receiver. Arrange notifications and screen orientation before playing for a more consistent TV picture. To finish, return to Screen Mirroring and choose Stop Mirroring.
Mirroring the whole screen differs from sending only game video to an external display. For this process, first check whether the TV shows the complete phone screen. If borders remain, compare the phone's aspect ratio and orientation, then check the TV for additional scaling or overscan settings.
Adjust orientation and keep the edges visible
Observe portrait orientation first, then rotate to landscape and confirm that system orientation lock does not prevent rotation. TVs usually suit landscape better, but games have their own aspect ratios. Use text in all four corners of a game menu to check whether the TV crops top or bottom information.
If the phone shows everything but the TV crops the edges, the TV's display-area setting is a more likely cause. Look for the receiver's original-aspect or fit-picture options and change one at a time. Do not begin by greatly shrinking Yearn's picture to offset TV cropping, or you will need to restore it when playing on the phone alone.
Observe input delay in three stages
Before mirroring, press a physical or virtual button and watch the phone's response. Enable mirroring and compare phone and TV together. If the phone responds promptly but the TV updates later, most delay lies in transmission or the receiving display. If both are slow, check local game performance and controller connection first.
Choose repeatable actions, such as moving a menu cursor or walking a short distance. Do not rely only on an unpredictable battle. If the TV offers a game display mode, try it according to its official instructions and compare the same action again. Network improvements and display-mode changes require observed results; a switch's name alone cannot establish that delay is solved.
Troubleshoot missing picture or sound one layer at a time
If the receiver is absent from the list, check that it is powered on, mirroring is enabled, and both devices are on a network that permits communication. If it appears but connection fails, look for a confirmation prompt on the TV, then end the connection and select it again. Apple's official troubleshooting also includes updating software and restarting the relevant devices.
If there is picture but no sound, confirm that the phone itself can produce sound, then check TV volume, mute and the selected output device. If the picture disconnects while the game continues on the phone, pause before restoring the connection. Save important progress in advance using the save guides, rather than blindly pressing Back or Exit while the TV picture is missing.
Questions and real-use checks
If the game appears on TV, is it suitable for action games? You also need to check the response from a button press to the displayed action. Delay feels different in turn-based or slower games, so judge your own use case. Compare briefly before deciding to use the TV as the main display.
Can I turn the phone screen off and keep displaying the game on TV? This guide uses system mirroring of the entire screen. Lock-screen and background behavior depend on the system and app state. Test while the device shows normal gameplay rather than treating continued output with the screen off as a guaranteed feature.
Finish by checking three things: complete edges on the TV, sound from the intended device, and input delay within your acceptable range. Stop mirroring when finished and confirm normal phone display. Record the receiver model and network environment so future connection issues have a direct comparison rather than requiring you to guess through the entire process again.
Related tutorials and sources
Connect a physical controller first, Picture-scaling checks.
For system connection steps, see Apple's screen mirroring instructions and Troubleshoot the mirroring connection.
Information checked on October 23, 2026. Public release information comes from the Yearn store page and Apple’s lookup API, is 1.0.2, requiring iOS / iPadOS 17 or later. Follow the version actually shown on the device.