scrcpy lags over wifi when phone switches from 5GHz to 2.4GHz connection to router (Macbook Pro Sequoia to Samsung Galaxy S10+)

I used to use scrcpy from my Mac to my Galaxy S10+ with no issues over a 2.4G home network. 50Mbps up/down was more than sufficient.

I upgraded to a 1GB up/down plan with an eero 7 Pro mesh router pair that supports 5GHz and 6GHz frequencies.

scrcpy will work fine for a while and then suddenly get laggy. Screen loads get slow and I will get multiple repeated characters when typing into text fields.

When the eero app shows the phone connected via a 5GHz link, everything seems to work. When it switches to a 2.4GHz link, the lag seems to begin. I have a reserved IP for the phone with the mesh router but there is no control over the link frequency. The phone can be sitting 4 feet from the router and suddenly switch. The lag is well correlated but I can't assure causation.

The 120+Mbps I get on the 2.4GHz link should be plenty fast enough. I think something is going askew when the switch happens.

My normal invocation is:
scrcpy --video-codec=h265 --max-size=1920 --max-fps=30

I've tried lower resolution settings and the problem still occurs.

This is likely PEBCAK (hence the question vs. bug report) but I've read the docs, prior tickets, etc. and can't figure out a solution.

Help appreciated.

Edit: It occurred to me that dl/ul speeds shouldn't matter since the scrcpy link doesn't go over the internet. The local wifi connection should be plenty fast enough...

scrcpy 4.1 https://github.com/Genymobile/scrcpy

Dependencies (compiled / linked):

• SDL: 3.4.14 / 3.4.14
• libavcodec: 63.1.100 / 63.1.101
• libavformat: 63.1.100 / 63.1.101
• libavutil: 61.1.100 / 61.1.101
• libusb: - / 1.0

No source file or test is identified in the report. Start by reproducing the supplied scrcpy 4.1 invocation while the phone switches between 5GHz and 2.4GHz, then compare behavior with the documented troubleshooting and prior tickets the reporter mentions. Done means establishing whether the switch causes the lag and identifying a reproducible fix or a clearly documented limitation.