oh snap Nvidia shield support for Pyrowave

The three dots button on the Steam Controller (2026) does not work on this Steam Link Beta while connected/streaming.

Tested on a Redmi Note 12 Pro 5G (phone) and a Redmi Pad (tablet) connecting to a Steam Deck and a PC running Steam Big Picture Mode with the Steam Controller (2026) connected to the phone/tablet via Bluetooth (separately, ofc).

Test Controller screen on the Steam Link app correctly identifies and shows the button when pressed but not on the host system (Steam Deck/PC) through Steam Link.

Was working in the previous version (1.4.2).

Originally posted by Commentator Kris:

The three dots button on the Steam Controller (2026) does not work on this Steam Link Beta while connected/streaming.

Thanks for the heads-up; fixed for next beta.

Don't know if this is the right place to bring up bugs, but there's one long-standing issue that has been bothering me. If you go to the Streaming Settings inside the app, some settings have these white text boxes where you can manually input the numerical values to what you want (e.g. resolution or framerate). Except, tapping the boxes does not bring up an on-screen keyboard. So you need a physical keyboard to change them in practice.

Originally posted by slouken:

The next version of Steam Link for Android is now available as a beta build.

You can download it from Google Play by opting into the beta here:
https://play.google.com/apps/testing/com.valvesoftware.steamlink

Or downloading directly from Valve here:
https://media.steampowered.com/steamlink/android/latest/steamlink-android.apk

That's the same URL as in the link labeled "Android users without access to Google Play" on this page: https://store.steampowered.com/remoteplay

I was wondering how to get the beta without Google Play earlier, while browsing the Pyrowave thread...

Getting a black screen and this error in streaming_log.txt when trying pyrowave on my Google TV Streamer 4k
CLIENT: CPyrowaveVulkanAccel: pyrowave_decoder_create() failed: -2
I'd be happy to provide more information on it if I knew where to look.

Originally posted by LateParrot:

Getting a black screen and this error in streaming_log.txt when trying pyrowave on my Google TV Streamer 4k
CLIENT: CPyrowaveVulkanAccel: pyrowave_decoder_create() failed: -2
I'd be happy to provide more information on it if I knew where to look.

The Google TV Streamer doesn't actually support the features we need for Pyrowave. It won't show as available in the next build. Thanks!

Originally posted by raggar:

Don't know if this is the right place to bring up bugs, but there's one long-standing issue that has been bothering me. If you go to the Streaming Settings inside the app, some settings have these white text boxes where you can manually input the numerical values to what you want (e.g. resolution or framerate). Except, tapping the boxes does not bring up an on-screen keyboard. So you need a physical keyboard to change them in practice.

This is also fixed for the next build, thanks!

Is there a way to make the phones gyroscope be attributed to the connected controller rather than the Touch Controller? The gyro being on the separate touch controller makes Steam Input bindnings that activate the gyroscope not work since a connected controller cannot interact with the layers of the touch controller.

I also wonder, in regards to the latency options in the audio, is the "Unspecified" option defaulting to 20ms like the Automatic option or is it simply removing any buffring delay?

Originally posted by slouken:

Originally posted by LateParrot:

Getting a black screen and this error in streaming_log.txt when trying pyrowave on my Google TV Streamer 4k
CLIENT: CPyrowaveVulkanAccel: pyrowave_decoder_create() failed: -2
I'd be happy to provide more information on it if I knew where to look.

The Google TV Streamer doesn't actually support the features we need for Pyrowave. It won't show as available in the next build. Thanks!

Ah that stinks, but thanks!

guess Aspect Ratio(LetterBox) option seems only work on Pyrowave setting from client.
when it using HEVC, still client pick the wrong resolution, does these tested from AV1 and Pyrowave only?
unless forcing value from Host Steam Client everytime for each client devices, it pick the wrong resolution.
interesting that when using Pyrowave(even Old AP that broken on support range to decode Pyrowave and shows broken green frames) setting, it show proper 1920x1080 letterbox in 1920x1200 client screen. (and 1440x900 when HEVC)

these issue wasn't exist quite a months ago(not sure but not happen when fairly early in this year) so.. guess cause of differency on hw/sw processing? or picking wrong value from drivers? or just Pyrowave not depends on hw that exact working like headless mode? dunno why..

hope to know why it's maximum resolution to 'dynamic only', not just deliver 'steam can decide dynamic but fix in this aspect ratio' or 'possible to fix manual resolution value but only dynamic in bitrate' kind of design of options..

because, not like old game in old days, game nowdays just get stutter or overhead from from hw encode(lack of VRAM).
usually not from the 'lack of performence' to trigger resolution down in real time.

even if game has performence issue to trigger 'drop the overload to less affect in streaming' flag, game go to DLSS/FSR manual performence profile/auto profile flag to adjust them, not much from adjust entire game resolutions like old games style.

also those 'sw keyboard not triggered in setting menu' are exist from the first place, glad that recorgnize it finally even in it's reported many times in this forum..

Originally posted by 1337bignose:

guess Aspect Ratio(LetterBox) option seems only work on Pyrowave setting from client.
when it using HEVC, still client pick the wrong resolution, does these tested from AV1 and Pyrowave only?

I test using HEVC in every test run, so it certainly should be working. . Can you provide a little more information? Is the host PC using an ultrawide monitor, what OS, etc. (Alternatively, you can submit a system report in Steam, which will bundle up the necessary logs.)

Edit: I just tried with HEVC on a Samsung Galaxy Z Fold 8 Ultra -- Letterbox, Zoom, and Stretch all do what I would expect. Can you provide any other information?

Originally posted by junjun:

Is there a way to make the phones gyroscope be attributed to the connected controller rather than the Touch Controller? The gyro being on the separate touch controller makes Steam Input bindnings that activate the gyroscope not work since a connected controller cannot interact with the layers of the touch controller.

I also wonder, in regards to the latency options in the audio, is the "Unspecified" option defaulting to 20ms like the Automatic option or is it simply removing any buffring delay?

I'm waiting for the gyro thing for about 2-3 years now. Sunshine emulates a ps4 controller but their gyro implementation is so ♥♥♥♥♥♥♥ bad for me :( I'll be happy if steam will manage to do something about this someday.

Originally posted by Packetdancer:

Originally posted by 1337bignose:

guess Aspect Ratio(LetterBox) option seems only work on Pyrowave setting from client.
when it using HEVC, still client pick the wrong resolution, does these tested from AV1 and Pyrowave only?

I test using HEVC in every test run, so it certainly should be working. . Can you provide a little more information? Is the host PC using an ultrawide monitor, what OS, etc. (Alternatively, you can submit a system report in Steam, which will bundle up the necessary logs.)

Edit: I just tried with HEVC on a Samsung Galaxy Z Fold 8 Ultra -- Letterbox, Zoom, and Stretch all do what I would expect. Can you provide any other information?

1. maybe cause of my main Tablet device for Steam Link is Old model that Stucked in Android 13 with OneUI 5.1.1

Galaxy Tab Active 3 that samsung push B2C firmware on B2B model cause of COVID-19 days
(same reason as Galaxy A52S)
i'm not sure but i bet that model might be not in the they're remote test app.
https://developer.samsung.com/remote-test-lab
basicly 1920x1200 60hz with stylus samsung stock device.


2. i just got short test from S24Ultra (SM-S928N) but stupid steam client erase all my comment in this webpage.

so anyway, seems Steam Link app only referencing resolution info from android system resolution, not the actual device screen's physical pixel resolution.
(guess cause of avoid risk of out of range)

in my S24U, steam link's auto suggestion 1560x720 base on system resolution and aspect ratio, when i set this limit from client as 1920x1080 and use Pyrowave, then remote session start with 1600x900 resolution instead of 1920x1080 as proper side/topdown letter box like other apps(youtube as example)

same thing happen on tablet, steam link app auto suggest 1440x900 base on calculate android system side resolution,
(actually this tablet never push 1440x900 kind of resolution, so fairly steam link side issue, or read wrong value from hosts?)
not the actual display resolution of device 1920x1200
(usual behavior of android phone/tablets. set one~two step lower value then display resolution for power saving from lower the system render resolution)

not sure the dates but steam link in late 2025~early 2026 was reading this value percisely.
still was had aspect ratio issue but at least read it properly.

other apps in android(not from google, just a 3rd party open source remote solutions) doesn't had this kind of issues in reading resolutions so..

any way to send my device app log to here without install or activate some risky android dev things?
android only send logs to google play system from crash only so.. honeslty it's scum to send logs without break some credentials on personal devices.

of course Steam Link Android app and Steam Windows Client are all up-to-date beta branch.

guess fundamental issue is, steam link's client setting only suggest 'maximum limit' that purpose on 'simple effective' design turn in to much complicate results to users.
either ultra ultra wide host or either square square clients, steam's host-client behaivor in consider aspect ratio and 'where the f i should add black bar in side or topdown' letterbox, read and apply resolution in dynamic all completely wrong and garbage in latest enviorments of typical gaming users.

feels still this one stucked in mid 2016~2019 somewhere.
just like many customers frustrate that when only dev support improved and customer side support of steam store still stucked at 2011rish until valve change up since 2018~2020 days.