PS Remote Play 2026: 1080p in 12 Steps, 30 Min

There is a specific ritual that plays out in living rooms worldwide. Someone buys a $199.99 PlayStation Portal — or installs the free PS Remote Play app on a laptop — taps Connect, watches a grey rectangle stare back for ninety seconds, and then declares the whole thing broken. It is not broken. Remote Play is one of the most quietly competent things Sony ships. The technology is fine. Your network is the problem, and almost nobody configures a network correctly, because Sony's own guidance stops at “make sure you have a good connection” and then wanders off to sell you a subscription.

This tutorial fixes that. By the end you will have a console that wakes on command, a client that connects in under five seconds, and a stream running at a genuine 1080p60 with input latency low enough to finish a Souls boss without throwing the handset. We will do it in twelve numbered steps, then go deeper: the exact ports, the Wi-Fi bands that actually matter, the open-source client that runs Remote Play on a Steam Deck, and a troubleshooting table for when it all goes sideways anyway. Budget thirty minutes. Most of that is waiting for a console to finish an update.

One promise up front: nothing here requires a PlayStation Plus subscription. Remote Play is free. Sony would prefer you did not know that, which is exactly why we are going to say it several more times.

Remote Play vs Cloud Streaming — the Distinction That Is the Whole Article

Ninety percent of the confusion around this feature comes from conflating two things Sony deliberately markets as if they were one. If you understand the split, every setup decision downstream becomes obvious. If you don't, you will spend an afternoon wondering why your console has to be switched on.

Remote Play: your console does the rendering

Remote Play means your PS5, PS5 Pro, or PS4 renders the game locally, encodes each frame into an H.264 or HEVC video stream, and squirts it across your network to a receiving device — a Portal, a phone, a laptop, a Steam Deck. The console is doing all the work. That has one non-negotiable consequence: the console must be powered on or in rest mode. There is no cloud, no server farm, no monthly fee. The image quality is a function of your network and the console's encoder, not a data-center GPU you are renting by the hour. Because your own hardware is in the loop, Remote Play will happily stream your entire PS4 back catalogue and any PS5 title installed on the drive, including the ones no cloud service will ever touch.

Cloud Streaming: Sony's data center does the rendering

Cloud Streaming is the other thing, and it is the source of fact-sheet lines like “you can play with the console switched off.” That is true — of Cloud Streaming, which runs on Sony's servers and requires a PlayStation Plus Premium membership. The catalogue is curated: titles carry a “streaming supported” icon, and the PlayStation Portal gained Cloud Streaming access in 2024 so you can launch things like Marvel's Spider-Man 2, Spider-Man Remastered, and Miles Morales without your own PS5 running at all. Useful. Also completely different from Remote Play. When a reviewer says the Portal “lets you power the PS5 off,” they are describing Cloud Streaming. When this tutorial says “rest mode,” we are describing Remote Play. Keep the two filed separately and you will never be confused by a support article again.

A short, sardonic history of the feature

Remote Play is old. Per Wikipedia's Remote Play entry, the concept debuted in the PSP era around 2006–2007, letting a PlayStation Portable wirelessly reach into a PS3 and play a limited slice of its software. Sony then spent fifteen years slowly widening the gate. Remote Play reached Windows PCs and macOS in 2016. It opened to all Android and iOS devices in 2019, retiring the earlier rule that locked mobile Remote Play to a handful of Sony Xperia phones. In early November 2020, just ahead of the PS5's November 12 launch, the mobile app gained the ability to stream PS5 titles for the first time. And on November 15, 2023, Sony shipped dedicated hardware — the PlayStation Portal Remote Player, $199.99, an 8-inch 1080p panel bolted between two halves of a DualSense. The feature had finally earned its own box. If you want the retro angle on the console that feeds it, our breakdown of the PS5 Pro versus the base PS5 covers why the Pro's frames are worth streaming in the first place.

Prerequisites and Requirements

Do not skip this. Every failed Remote Play session I have ever diagnosed traces back to a prerequisite someone assumed they met. Read the three lists, confirm each line, and the twelve steps that follow will actually work.

Hardware you need

On the sending side: a PS5, PS5 Pro, or PS4/PS4 Pro. On the receiving side, pick one — a PlayStation Portal; an Android 7.0+ phone or tablet; an iPhone or iPad on iOS 13+; a Windows 10/11 PC; a Mac on macOS 11 (Big Sur) or later; or, via the open-source route below, a Steam Deck, a Linux box, or an Android retro handheld. A physical controller helps: a DualSense or DualShock 4 over USB or Bluetooth turns a phone into a real gaming device. If you are eyeing an Android handheld specifically for this, our Retroid Pocket 6 comparison is a sane place to start, because the SoC that decodes your video stream matters more than the marketing suggests.

Software versions

The console must be on the latest system software — leave auto-update on and let it settle before you begin. The official client apps are versioned per platform and self-update; grab them from the canonical source, Sony's PS Remote Play download page, which serves the iOS, Android, Windows, and macOS builds. Two software milestones are worth knowing because they define what “good” looks like today: an early-2024 Portal system update introduced the 1080p High Quality mode for Remote Play and Cloud Streaming (documented in this NeoGAF thread), and the subsequent 7.0 update tightened latency and stability to the point reviewers argued it beats cloud streaming outright. If your client predates 1080p HQ, update before you touch anything else.

The network baseline

Sony's stated floor is 5 Mbps down and up; the recommended figure is 15 Mbps. Those numbers are honest but incomplete. For same-house Remote Play, raw speed barely matters — latency and jitter do. For Remote Play away from home, the number that governs your experience is the upload speed at the console's location, because that is the pipe pushing video to you. Measure it, at the console end, before you blame the app:

$ speedtest-cli --simple
Ping:     11.482 ms
Download: 187.44 Mbit/s
Upload:   23.11 Mbit/s

# For EXTERNAL Remote Play, the upload figure is the one that
# matters - it is the console pushing frames out to you.
# 5 Mbps is the floor. 15 Mbps up gives honest 1080p headroom.
# Ping/jitter to your ISP predicts input feel better than raw
# bandwidth ever will.

If that upload number is under 5 Mbps, stop. No amount of tuning fixes a starved pipe. Everything below assumes you cleared the floor.

Enable Remote Play on the Console

Three toggles on the console decide whether any of this works. Get them right once and you never revisit them. Get them wrong and you will chase phantom connection errors for hours.

The three toggles that matter

First, Remote Play itself. Second, the two rest-mode network features that let a sleeping console stay reachable and wake on a remote command — without these, “connect while the PS5 naps” simply does not happen. Third, console sharing, which activates the machine for your account so the app trusts it. Here is the full map on a PS5; PS4 paths are near-identical under Settings > Remote Play Connection Settings.

Settings > System > Remote Play
  - Enable Remote Play ........................ [ON]

Settings > System > Power Saving
  - Features Available in Rest Mode
      - Stay Connected to the Internet ........ [ON]
      - Enable Turning On PS5 from Network .... [ON]

Settings > Users and Accounts > Other
  - Console Sharing and Offline Play .......... [ENABLED]

Why rest mode is the secret ingredient

“Stay Connected to the Internet” keeps the network stack alive while the console sleeps; “Enable Turning On PS5 from Network” lets a wake packet from the app boot it into a session. Skip either and you get the single most common failure mode on Earth: the app finds the console, tries to connect, and times out because the machine is a brick with the lights off. These two toggles cost roughly a watt of standby draw. Pay the watt.

Activate the console as primary

“Console Sharing and Offline Play” — historically called activating your primary PS5 — ties the hardware to your PSN account so the Remote Play handshake is authorized. If you sign into the app with one account and the console is primary for another, you will loop on sign-in errors that look like a bug and are actually a mismatch. One account, one primary console, and the whole class of authentication failures disappears.

The 12-Step Setup

This is the spine of the tutorial. Twelve steps, each with the reasoning behind it, because a step you understand is a step you can debug. Do them in order; the later ones assume the earlier ones held.

What the twelve steps accomplish

Steps 1–4 prepare the console. Steps 5–8 install and pair the client. Steps 9–12 make the first connection and tune it. Skipping around is how people end up on the troubleshooting table.

1. Update the console fully. Settings > System > System Software > Update. Why: Remote Play's encoder, the 1080p HQ path, and the handshake all live in system software. An out-of-date console negotiates a worse session or refuses newer clients outright.
2. Enable Remote Play on the console. Flip the toggle from the previous section. Why: nothing listens for a Remote Play connection until this is on. This is the literal on switch.
3. Turn on both rest-mode network features. Stay Connected to the Internet, and Enable Turning On PS5 from Network. Why: so you can wake and reach the console without walking to it. Without these, remote wake is impossible and rest-mode sessions fail.
4. Set the console as your primary / enable Console Sharing. Why: it authorizes your PSN account against the hardware, killing the sign-in-loop failure class before it can start.
5. Wire the console to the router, or move it to 5 GHz. Settings > Network > Set Up Internet Connection. Why: the console's uplink is the bottleneck for every session. A $10 Ethernet cable removes more latency and jitter than any in-app setting.
6. Give the console a static IP (DHCP reservation). Do it on the router by MAC address. Why: port forwarding and manual client pairing both need the console to keep the same address. A roaming IP breaks external play the next time the lease renews.
7. Download the official app from Sony's URL. Use remoteplay.dl.playstation.net for iOS, Android, Windows, or macOS. Why: third-party mirrors are how you install malware wearing a PlayStation logo. Go to the source.
8. Sign into the app with the same PSN account as the console. Why: account parity is what makes the handshake trust the device. Different accounts, guaranteed failure.
9. Pair the device. On the console, go to Settings > System > Remote Play > Link Device (labelled Pair Device on some builds) to reveal an 8-digit code, and enter it in the app if auto-discovery does not find the console. Sony's PC and Mac support page documents the same flow. Why: the code cryptographically binds this client to this console for future sessions. You do it once.
10. Make the first connection on the same Wi-Fi. Both devices on the same local network, console awake. Why: a local test isolates variables. If it fails on your own LAN, the problem is configuration, not the internet, and the troubleshooting table applies.
11. Set video to 1080p and 60 fps in the app. Settings > Video Quality for Remote Play > Resolution: 1080p (High), Frame Rate: High/60. Why: the app defaults conservatively. On a wired console and a clean 5 GHz link you have the headroom, and 1080p HQ is the entire reason to be on modern software.
12. Test it away from home, then tune. Move the client to cellular or another network and reconnect. Why: external play is the real test of your ports and upload. If local works but remote does not, jump to Network Tuning — you have a NAT or bandwidth issue, not a broken app.

Expected result after step 12

On a healthy local network, the app should connect in two to five seconds and the on-screen latency should feel indistinguishable from playing on the TV — call it 8–25 ms glass-to-glass. Over a clean internet connection, expect 30–60 ms, which is fine for everything short of frame-perfect fighting games. If you are seeing seconds of lag or constant macroblocking, you have a network problem the next sections exist to solve.

If a step fails

Do not restart from step 1. Identify which step broke — sign-in (step 8), pairing (step 9), local connect (step 10), or remote connect (step 12) — and match the symptom in the troubleshooting table. Each failure class has a distinct fix, and re-running the whole sequence usually just reproduces the same wall.

Network Tuning and Ports

Remote Play is a UDP application pretending to be a real-time protocol, which means it is exquisitely sensitive to the two things home networks handle worst: NAT traversal and latency under load. Fix both here.

The ports Remote Play actually uses

For same-LAN play you need to forward nothing — discovery and connection happen locally. For external Remote Play, forward these to the console's static IP. UPnP usually handles it automatically, but hostile routers and double-NAT setups need it done by hand:

# PS Remote Play / Chiaki port map
# Forward these to the console's static IP for EXTERNAL play.
# Not required on the same LAN.

Discovery      UDP   9302
Control        TCP   9295
Session/Stream UDP   9296   9297

# Some routers also want UDP 9303 open for older PS4 sessions.
# If UPnP is on and healthy, these open themselves - verify in
# the router's UPnP/port-forwarding status page, do not assume.

The discovery port is how a client finds the console; the control port sets up the session; the session ports carry the actual video and input. Block any of them and you get the classic “works at home, dead everywhere else” pattern.

Wi-Fi bands, and why the console should not use Wi-Fi at all

Put the client on 5 GHz or 6 GHz — never 2.4 GHz, which is a swamp of microwaves, neighbours, and Bluetooth. Put the console on Ethernet if there is any way to run a cable, because the console's uplink jitter propagates into every frame you receive. If the console truly must be wireless, force it onto a clean 5 GHz channel and accept that you have chosen convenience over the single biggest quality lever available. This is also the fix for the most common “random stutter” complaint: the stutter is 2.4 GHz interference, not the app.

Bufferbloat is the silent killer

Bufferbloat is when a saturated link buffers packets instead of dropping them, spiking latency from single-digit milliseconds to hundreds. It is invisible on a speed test and lethal to Remote Play. Diagnose it by pinging the console while something else saturates the link:

$ ping -c 5 192.168.1.42
64 bytes from 192.168.1.42: icmp_seq=1 ttl=64 time=1.12 ms
64 bytes from 192.168.1.42: icmp_seq=2 ttl=64 time=1.30 ms
64 bytes from 192.168.1.42: icmp_seq=3 ttl=64 time=1.19 ms
rtt min/avg/max/mdev = 1.081/1.204/1.301/0.079 ms

# Now run the SAME ping while a large download saturates the
# link. If avg jumps from ~1 ms to 80+ ms, that is bufferbloat,
# and it is exactly why your inputs feel like syrup mid-session.

The fix is Smart Queue Management — SQM or fq_codel — on the router. Any router running OpenWrt has it; many stock firmwares now call it “Smart Queues” or “QoS.” Turn it on, cap it slightly below your real line speed, and watch the loaded latency collapse. This one setting rescues more Remote Play sessions than every other tweak combined.

Optimize Video: 1080p and Bitrate

With the network sound, the last variable is the encode. This is where you trade sharpness against latency against reliability, and where the modern software updates finally pay off.

Turning on 1080p High Quality

Before the early-2024 update, the Portal and app topped out at 720p for Remote Play, and it showed. The 1080p High Quality mode changed the ceiling: a genuinely crisp panel-native image on the Portal's 1080p screen, and a sharp full-screen picture on a laptop. In the app, set Resolution to 1080p (High) and Frame Rate to High/60. If 1080p is greyed out, your client or console firmware is stale, or you are on a network the app has quietly decided cannot sustain it — fix the network first, then the option reappears.

Resolution vs frame rate vs bitrate

These three fight over the same bandwidth budget. Resolution buys sharpness on still images; frame rate buys smoothness in motion; bitrate buys freedom from compression mush. On a wired console and clean 5 GHz client, 1080p60 at roughly 15 Mbps is the sweet spot and matches Sony's own recommended figure. If you are bandwidth-limited, drop resolution to 720p before you drop frame rate — a smooth 720p60 feels far better to play than a sharp, stuttering 1080p30. Leave bitrate on auto unless you are chasing a specific problem; the encoder's adaptive logic is better than your guesses.

PS5 Pro, ray tracing, and PSSR over the wire

Here is the subtle part people get wrong. As of 2025, a PS5 Pro streams its enhanced output — ray tracing, and frames reconstructed by PSSR (PlayStation Spectral Super-Resolution) — over Remote Play, because Remote Play simply relays whatever the console renders. But the Portal does not run PSSR; it receives the Pro's already-upscaled frame, which is then re-encoded at up to 1080p for the stream. So the Pro's advantage reaches you as a cleaner source image feeding the encoder, not as native reconstruction on the handheld. It is a real, visible improvement, and it is also not magic. If you are weighing whether that source-quality bump justifies the hardware, our PS5 Pro cost breakdown does the math.

Chiaki-ng on Steam Deck

The official app is fine. But if you own a Steam Deck, a Linux handheld, a Raspberry Pi, or an Android retro device, the interesting route is Chiaki-ng — an open-source, reverse-engineered Remote Play client that does everything Sony's app does and several things it refuses to.

What Chiaki-ng is, and why it is legal

The original Chiaki project on GitHub reverse-engineered the Remote Play protocol cleanly — observing the wire format, not decompiling Sony's binaries — which is the same clean-room principle that has kept emulator authors out of court for decades. The actively maintained fork, chiaki-ng (formerly chiaki4deck), adds Steam Deck integration, better codecs, and a saner UI. Its documentation is genuinely good, which is more than can be said for most of this ecosystem. You are not pirating anything; you are talking to your own console with a client you are allowed to write. This is why Remote Play is a favourite on portable Linux — and if you are deciding between a Deck and the alternatives for exactly this kind of use, our Switch 2 versus Steam Deck comparison is the relevant read.

Registering a console from the command line

Chiaki-ng ships a GUI, but the CLI shows exactly what is happening, which is what you want when debugging. Registration needs two things: your PSN Account ID in base64 (chiaki-ng has a built-in PSN login button that fetches it for you), and an 8-digit PIN from the console at Settings > System > Remote Play > Link Device.

$ chiaki discover -h 192.168.1.42
host:                 192.168.1.42
state:                ready          # or standby, when in rest mode
host-type:            PS5
host-name:            CUSTOM-PS5
host-id:              0011AABBCCDD

# Grab the 8-digit PIN on the console:
#   Settings > System > Remote Play > Link Device

$ chiaki register --host 192.168.1.42 --psn-account-id AbCdEfGhIjK= --pin 12345678
register success

The base64 account ID is the single most common Chiaki failure — people paste their online ID (the display name) instead of the numeric account ID encoded to base64, and registration silently refuses. Use the built-in login flow and this never happens.

The config file and performance flags

Chiaki-ng stores settings in a plain config file you can version, copy between devices, or tune by hand. The keys below are illustrative — the canonical list lives in the docs — but they show the levers that matter on a handheld: codec, hardware decoder, and bitrate.

# ~/.config/Chiaki/Chiaki.conf  (chiaki-ng, Linux / Steam Deck)
[settings]
resolution=1080p
fps=60
bitrate=15000            # kbps; 0 = let the console decide
codec=h265               # HEVC decodes cheaper on modern SoCs
hardware_decoder=vaapi   # vaapi on Deck/AMD; videotoolbox on macOS
audio_buffer_size=9600   # raise if audio crackles; adds a little lag

[registered_hosts]
size=1
host_1=192.168.1.42
mac_1=0011AABBCCDD
# rp_key and nickname are written by the GUI on successful register

On a Steam Deck, set hardware_decoder=vaapi and codec=h265 and the APU sips power decoding the stream, buying you battery. Force software decoding and you will cook the handset for no reason. HEVC also survives lossy links better at a given bitrate, so it is the right default on anything made in the last five years.

Five Common Pitfalls

These are the traps that eat afternoons. Each one is common, each one has a clean fix, and every one of them is a configuration mistake rather than a hardware fault.

Network pitfalls

Pitfall 1 — the console on 2.4 GHz Wi-Fi (or Wi-Fi at all). Symptom: intermittent stutter and macroblocking that comes and goes with the time of day. Fix: wire the console with Ethernet, or at minimum force it to a clean 5 GHz channel. This is the highest-value change on the list.

Pitfall 2 — no QoS, so bufferbloat destroys latency under load. Symptom: play is fine until someone streams Netflix, then inputs turn to syrup. Fix: enable SQM/fq_codel on the router and cap it just below your real line rate.

Pitfall 3 — your ISP uses CGNAT. Symptom: local Remote Play is perfect, external Remote Play never connects no matter how many ports you forward. Fix: you have no public IPv4 to forward to — request one from the ISP, use a relay/VPN as covered in Advanced Tips, or accept LAN-only play.

Account and console pitfalls

Pitfall 4 — the console is not set as primary, or the app is signed into a different account. Symptom: endless sign-in errors that masquerade as bugs. Fix: enable Console Sharing and Offline Play on the console, and sign the app into the exact same PSN account. If your PS5 is misbehaving more broadly, a cache rebuild via our safe-mode cache-clear walkthrough clears a surprising amount of connection weirdness.

Client and expectation pitfalls

Pitfall 5 — expecting Cloud Streaming behaviour from Remote Play. Symptom: you switched the console fully off and now nothing connects, and you conclude the feature is broken. Fix: Remote Play requires the console on or in rest mode — full stop. Playing with the console off is Cloud Streaming, a separate PS Plus Premium feature. A bonus sixth trap: a VPN or aggressive firewall on the client silently eating UDP 9296/9297. If a VPN is running, allow those ports or drop the VPN for the session.

Troubleshooting Table

When a session misbehaves, read the error and match the symptom — do not guess. The table below covers the failures that account for the overwhelming majority of Remote Play support threads.

Match the symptom, apply the fix

When to reboot vs re-pair

Reboot the console (a full power cycle, not rest mode) when a previously working setup suddenly fails — it clears a wedged network stack. Re-pair only when the client no longer recognizes the console or you have changed accounts; re-pairing needlessly discards a working registration and solves nothing that a reboot wouldn't. Nine times out of ten, the fix is a network change from the sections above, not a re-pair.

Advanced Tips

Once the basics hold, these are the moves that separate a working setup from a genuinely good one.

External play without a public IP

If your ISP runs CGNAT, port forwarding is a dead end — there is no public address to forward. The clean workaround is a personal overlay network (Tailscale, WireGuard, or similar) that puts the client and the console's LAN on the same virtual subnet, so Remote Play behaves as if you were home. On Windows, if you are self-hosting a relay endpoint, open the session ports explicitly rather than trusting the default profile:

# Windows (admin PowerShell): allow the Remote Play UDP session ports
New-NetFirewallRule -DisplayName "PS Remote Play" -Direction Inbound -Protocol UDP -LocalPort 9296,9297 -Action Allow

Overlay networking also sidesteps double-NAT and hostile hotel Wi-Fi, and it keeps the traffic encrypted end to end — a strictly better answer than punching holes in a public-facing router.

Controllers, back buttons, and touchpads

The DualSense's touchpad and adaptive triggers map cleanly in the official app; on a phone, pair the controller over Bluetooth rather than leaning on touch controls, which are fine for menus and miserable for anything twitchy. Chiaki-ng lets you remap buttons and even emulate the touchpad from a keyboard region, which matters for games that treat the touchpad as a real input. On a Steam Deck, bind the rear paddles to touchpad clicks and the handful of PS games that demand a swipe stop being unplayable.

Encoder and decoder choices

Prefer HEVC (h265) over H.264 wherever your client can decode it in hardware — it holds up better at a given bitrate over a lossy link, which is most home Wi-Fi. Match the hardware decoder to the platform: VideoToolbox on macOS, VA-API on Linux and the Steam Deck, the native path on Windows. Getting the decoder right is the difference between the APU idling cool and the fans screaming while your battery evaporates. If you are also capturing this footage for anything, note that Remote Play is a lossy stream — for real recording, use the console's HDMI out and a capture card, which our PS5 capture-card guide covers properly.

Complete Working Configuration

Here is everything in one place — the known-good configuration this tutorial builds toward. Copy it, apply it line by line, and you have a Remote Play setup that connects fast and holds a clean 1080p60.

Console, router, and app in one block

========================================
 KNOWN-GOOD PS REMOTE PLAY CONFIGURATION
========================================

[ Console: PS5 / PS5 Pro / PS4 ]
  System software ................ latest (auto-update ON)
  Enable Remote Play ............. ON
  Rest Mode: Stay Connected ...... ON
  Rest Mode: Turn On from Network  ON
  Console Sharing / Primary ...... ENABLED
  Wired Ethernet ................. STRONGLY preferred

[ Router ]
  Console IP ..................... DHCP reservation (static)
  UDP 9296, 9297 ................. forwarded to console IP
  UDP 9302 (discovery) ........... forwarded (external only)
  TCP 9295 (control) ............. forwarded (external only)
  Smart Queue / QoS (fq_codel) ... ON (kills bufferbloat)
  Client Wi-Fi ................... 5 GHz or 6 GHz only

[ App / Client video ]
  Resolution ..................... 1080p (High Quality)
  Frame rate ..................... 60 fps
  Bitrate ........................ 15000 kbps (or auto)
  Codec .......................... HEVC / h265 where supported

[ Expected latency ]
  Same-LAN ....................... 8-25 ms glass-to-glass
  Clean internet ................. 30-60 ms

Chiaki-ng known-good config

For the open-source client on a Deck, Linux box, or handheld, this is the matching profile:

# ~/.config/Chiaki/Chiaki.conf
[settings]
resolution=1080p
fps=60
bitrate=15000
codec=h265
hardware_decoder=vaapi        # videotoolbox on macOS
audio_buffer_size=9600

[registered_hosts]
size=1
host_1=192.168.1.42
mac_1=0011AABBCCDD

Verify it end to end

Confirm the console is reachable, launch, and watch the client's log settle. This is what a healthy session looks like — if you see it, you are done:

$ chiaki discover -h 192.168.1.42
state: ready
host-type: PS5

# On launch, the log should settle into roughly:
[I] Setting up receiver
[I] Video profile 1920x1080 @ 60 fps
[I] Using codec h265
[I] Streaming session established

That is the entire game. Remote Play is not fragile; it is fussy, and fussy is fixable. Get the console wired, the rest-mode toggles on, the ports forwarded, and bufferbloat under control, and Sony's most underrated feature will quietly outperform the cloud service it competes with — for free, on hardware you already own, from a handheld small enough to forget in a jacket pocket. The Machine approves. Now go finish that boss.