Still having an issue with Samsung Galaxy S9 Ultra crashing with DualSense controller connected. Cleared all data and uninstalled multiple times. Crashes immediately when a PS5 controller is connected. controller is on latest software. confirmed I am on 1.3.29

To check... is this a Samsung Galaxy Tab S9 Ultra, e.g. the Android tablet from 2023, or a Samsung Galaxy S9+ (which was sometimes called the S9 Ultra), e.g., the Android phone from 2018? I just want to make sure I know which we're dealing with here.

I can say that I cannot reproduce this on an Samsung Galaxy S21 Ultra phone or a Samsung Galaxy Tab A7, so long as I'm on 1.3.29. (I can absolutely reproduce it with 1.3.28 on those devices.)

I don't have a Tab S9 Ultra tablet or an S9+ phone here to test with, so I can't directly check those.

It's the tab S9 ultra. I'll continue to respond in the other chat where you and the valve employee responded as well

I joined the beta and updated the Steam Link app to 1.3.29.308. I had no issues for almost 40 minutes streaming from my PC with Fedora 43 (Wayland) to a Samsung Galaxy Tab S10+ paired with a Dualsense 5 via bluetooth. However, Steam did gave an error seconds after exiting the game while still being in Big Picture mode asking me to restart it on my host PC with the -pipewire parameter. I think this might be another issue altogether but I don't remind having it before updating to 1.3.28. Hope it helps somehow.

Originally posted by Rubiola:

However, Steam did gave an error seconds after exiting the game while still being in Big Picture mode asking me to restart it on my host PC with the -pipewire parameter. I think this might be another issue altogether but I don't remind having it before updating to 1.3.28. Hope it helps somehow.

That's unrelated, and probably a false positive -- are you running the Steam beta client (not Steam Link, the actual Steam client on the host) or the release one?

Originally posted by Packetdancer:

Originally posted by Rubiola:

However, Steam did gave an error seconds after exiting the game while still being in Big Picture mode asking me to restart it on my host PC with the -pipewire parameter. I think this might be another issue altogether but I don't remind having it before updating to 1.3.28. Hope it helps somehow.

That's unrelated, and probably a false positive -- are you running the Steam beta client (not Steam Link, the actual Steam client on the host) or the release one?

I think so too. The Steam client on the host is the stable version but installed as a flatpak from the Fedora's software store. The specific version is 1778281814 (taken from the Steam About window).

By the way, I played for another 2.5hrs without experiencing any freeze.

Originally posted by Rubiola:

I think so too. The Steam client on the host is the stable version but installed as a flatpak from the Fedora's software store. The specific version is 1778281814 (taken from the Steam About window).

I *think* the beta builds of the Steam client (or a future main release update) will fix that for you, then. That said, I wouldn't mind knowing what steps you took to get there just to double-check later, though; I *think* I got all the edge cases with detecting Wayland and Pipewire misbehaving, but it never hurts to double-check!

My issues seems to be solved with this version, thanks for the fix!

Originally posted by Packetdancer:

I *think* the beta builds of the Steam client (or a future main release update) will fix that for you, then. That said, I wouldn't mind knowing what steps you took to get there just to double-check later, though; I *think* I got all the edge cases with detecting Wayland and Pipewire misbehaving, but it never hurts to double-check!

The error message pops up whenever I spent some time (no more than a few second) in the Steam Big Picture mode UI on the client. There is some screen flickering too. Then, it either exits by itself or I close the it manually. On the host side, Steam keeps running normally.

The client is running Samsung's One UI 8 (Android 16), Kernel version 6.1.134-android14-11-abX820XXS7CZB5. The Steam Link app is now on the beta branch 1.3.29.308 but this issue in particular started with update on the stable branch 1.3.28 along with the other problem where the app just froze while playing.

The host is on Fedora 43 updated to the last version (I'm not able to use my PC right now to check). The Steam version is 1778281814.

Basically, both the Steam app on the host and the Steam Link app on the client worked fine before updating the later to 1.3.28.

If there is anything in particular you want to know, just let me know.

Originally posted by Rubiola:

Basically, both the Steam app on the host and the Steam Link app on the client worked fine before updating the later to 1.3.28.

I would not expect to have seen the pipewire notice false-positive before updating both because the code didn't exist prior to those updates. The Linux host side of detecting a capture failure didn't exist in older versions (you'd just get an endless empty loading spinner, or a totally black screen, depending on the failure state). And prior to 1.3.28, the client didn't know how to actually *act* on the new messages that capture had failed, so would just ignore them. :)

At any rate, the current beta build for Steam should be 1779155395 -- if you can try the beta build to see if the false positive detection of a no-capture scenario still occurs, that'd be a huge help.

(To opt in to the beta builds of Steam, just go Steam -> Settings, Interface, scroll down to "Client Beta Participation" and pick "Steam Client Beta.")

Originally posted by iamlegendinjapan:

Still having an issue with Samsung Galaxy S9 Ultra crashing with DualSense controller connected. Cleared all data and uninstalled multiple times. Crashes immediately when a PS5 controller is connected. controller is on latest software. confirmed I am on 1.3.29

I have exact same behaviour on Razer Edge Wifi with Steam Link 1.3.29. It used to work really good with Dual Sense controller before 1.3.28.

Originally posted by Cpt.Jones-1891:

I have exact same behaviour on Razer Edge Wifi with Steam Link 1.3.29

Well, I'm... slightly happy that it means we have a repro that *isn't* the S9 Ultra, but still puzzled since if you're seeing the same Concurrency exception in the crash logs... there's demonstrably no way that should be able to happen *internal to Steam Link*.

It makes me think something else on the S9 Ultra or Razer Edge may be accessing sensors and doing so on a separate thread.

Still, just for the sake of sanity, can you try the special APK that slouken linked in this thread?

Originally posted by Packetdancer:

At any rate, the current beta build for Steam should be 1779155395 -- if you can try the beta build to see if the false positive detection of a no-capture scenario still occurs, that'd be a huge help.

Sure. No problem.

I can confirm the "restart steam with the -pipewire command" popup still persists with the beta version of Steam on the host PC (1779155395).

The weird thing is that I can play with no problems as long as I don't hang around in the Steam Big Picture UI for more than a few seconds.