Okay, I've added it in a temporary 32-bit build. Can you try it out there and see how it works for you?
https://www.libsdl.org/tmp/android-steamlink-release.apk

Update: Tested the new 32-bit (armeabi-v7a) build on Sony Bravia 7 (Mali-G57)

Summary: PyroWave now enables, but has a rendering issue and crashes after ~2 minutes.

Links:

1. https://pastebin.com/3BDFg3Ns (
   logcat -d -s DEBUG:V Granite:V libc:V SDL/APP:V > full_crash_backtrace.txt
   )
2. https://pastebin.com/dE71nkke (
   logcat -d | grep -i -a -E "pyrowave|vulkan|remoteplay|sdl|steamlink|mali|buffer|surface|swapchain" > pyrowave_bug_log.txt
   )
3. https://imgur.com/a/BboMyQC

Thank you for pushing the 32-bit build so quickly! The PyroWave toggle is now available and selectable on my Sony Bravia 7 (BRAVIA 4K AE2, MediaTek Pentonic 1000 / Mali-G57, Android 14 32-bit armeabi-v7a, Vulkan 1.3.247). However, when streaming at 1920x1080 with PyroWave enabled, two issues occur:

1. Corrupted Video Output (Top 50% Black, Bottom 50% Vertically Squished):
As shown in the attached photo, the top half of the screen is completely black and the video output is vertically compressed into the bottom half of the screen. Here are the relevant initialization lines from logcat when the stream starts:

2. Crash after ~2 Minutes of Streaming (std::bad_alloc / Out of Memory):
After streaming for about 2 minutes (with the target framerate fluctuating between 29.95 FPS and 59.90 FPS), the Steam Link app crashes with SIGABRT (std::bad_alloc) right after malloc(3110400) fails:

I have attached the photo of the screen along with the full logcat logs from the TV for reference. Please let me know if there are any other logs or tests I can run to help!

Okay, I think I know what’s going on here, thanks!

Okay, try this:
https://www.libsdl.org/tmp/steamlink-1.4.2-androidtv-pyrowave.apk

Just to set expectations, Android TVs are designed for media playback, not heavy GPU performance, so it's very likely that HEVC will be a better option for you.

Thanks for the experimental build! I can confirm that the changes you made completely resolved the display output issues with Pyrowave.

Screenshot of Stream [imgur.com]

I spent a good amount of time testing the Steam Link app on my TV today, and overall the experience was quite playable. I noticed some minor packet loss here and there (around 0.1%–0.5%), though that’s most likely just variance on my local network.

As you mentioned earlier, the main bottleneck right now is definitely the TV's hardware. As shown in the overlay stats in the attached photo, the display time sits around ~61 ms (compared to <1 ms input latency and ~2.4 ms ping), which seems to be the limit of what this TV's SoC/GPU can handle.

A couple of quick questions:

1. Do you have a rough timeline for when the Pyrowave fixes from this experimental build might make their way into the official public Android release?
   
2. While testing, I attempted to set the client resolution to 4K, but the stream remained at 1080p (Capture 1920x1080). Is this expected behavior because my host monitor only natively outputs up to 1080p, or should the client override be able to request a higher render target regardless of the host display?

Thanks again for looking into this and pushing the fix!

Originally posted by Yuma3015:

As you mentioned earlier, the main bottleneck right now is definitely the TV's hardware. As shown in the overlay stats in the attached photo, the display time sits around ~61 ms (compared to <1 ms input latency and ~2.4 ms ping), which seems to be the limit of what this TV's SoC/GPU can handle.

Yep, and notice you're losing about 14% of frames, just because your TV isn't fast enough to decode and display them all.

Originally posted by Yuma3015:

Do you have a rough timeline for when the Pyrowave fixes from this experimental build might make their way into the official public Android release?

No, but we have some Android mouse fixes coming, so I don't imagine it'll be too long.

Originally posted by Yuma3015:

While testing, I attempted to set the client resolution to 4K, but the stream remained at 1080p (Capture 1920x1080). Is this expected behavior because my host monitor only natively outputs up to 1080p, or should the client override be able to request a higher render target regardless of the host display?

Did you click on the enhanced 4K preset or go into the streaming settings and unlock higher resolutions?

Originally posted by Yuma3015:

Thanks again for looking into this and pushing the fix!

You're welcome! :)