- ​**Client Device:** Motorola Edge 30 Fusion (Native resolution: 2400x1080)
- ​**Client OS:** Android 13
- ​**Steam Link App Version:** Latest available
- ​**Host OS:** Windows 11 24H2 (Also reproduced on a Linux host)


When connecting to the host PC, the bottom edge of the video stream is severely blurred/smudged, which visually looks like a texture edge clamping issue.

Worse than the visual artifact itself is that the Steam Link app applies a forced downscale to the entire video stream to fit the image into the screen area _excluding_ this blurred bar.

​This is strictly a video stream rendering issue. The Steam Link UI itself (menus, overlay buttons before and during the connection) renders perfectly without any blur or scaling issues.


1. ​**Device Isolation:** Tested Steam Link with the same hosts on a different phone — the issue does not occur. The problem is isolated to the Motorola Edge 30 Fusion.
2. ​**OS/UI Settings:** Disabled system cutouts (camera) and removed the navigation bar. Toggled between gesture navigation and on-screen buttons. The issue persists. No other apps on this phone have this rendering problem.
3. ​**Steam Link Settings:** Toggled Hardware/Software Encoding and Decoding, NVFBC, HEVC, and various latency modes.
4. ​**Resolution Tweaks:** Added the phone's native resolution (2400x1080) to the host PC. This didn't fix it. Changing the streaming resolution only alters the size of the blurred bar (and sometimes adds a second blurred bar on the right side), but the terrible global downscaling is always applied. In full-screen game mode, the problem persists.

The video stream should fill the screen at 1:1 pixel mapping (or scale cleanly) without blurred edges or forced downscaling.

If the root cause of this rendering/clamping bug cannot be easily fixed for this specific device, please consider adding a setting to simply **crop** the affected edge area instead of downscaling the entire frame. The global downscaling degrades the image quality significantly, and a slightly cropped screen would be vastly preferable.

https://files.catbox.moe/nlyng9.png