audio has been back since the last build and the new one is working as well. thank you!

Please, please, please, can I just have any of my Bluetooth controllers stay connected and then have the Steam Link not crash when trying to unpair/pair/connect after it disconnects?

Originally posted by megadrivers:

audio has been back since the last build and the new one is working as well. thank you!

Great!

Originally posted by fash:

Please, please, please, can I just have any of my Bluetooth controllers stay connected and then have the Steam Link not crash when trying to unpair/pair/connect after it disconnects?

Possibly, what kind of controllers do you have?

Originally posted by slouken:

Possibly, what kind of controllers do you have?

For example, I have a Google Stadia controller[support.google.com] here. Shows up in Bluetooth Setup as Device: "StadiaJVCX-[last 4 hex digits of device BD address]", Type: "gamepad", Connected: "paired".

I'm only able to get to the menu by using a keyboard. (How am I meant to do menu actions set to controller buttons like like "Reset" with a keyboard btw? No keys seem to do the Y-button or X-button actions.)

Then if I stay on that screen, the controller might disappear from the menu. It might come back later. All of this regardless of whether the controller is off, on (searching), or pairing.

Or the controller might change from "paired" to "connected", and then I can use it. But eventually.... it will disconnect. Maybe 1 minute later, maybe 20 minutes later during a game. The controller will kick back into an idle/searching state.

Then if I use a keyboard to get back to the menu and explicitly tell it to connect to the controller, the Steam Link might connect, or it might reboot.

Today I have gotten SSH going, I tail /mnt/scratch/log/S13blueooth.sh (and the .sh.1, and the .sh.2) and nothing logs when/while these various things happen.

I do, though, have a pretty constant flood of "Can't store name for private addressed device" warnings with a couple of repeating device BD addresses.

Is this another issue like unsupported BT 4.2 DLE? Because I think I get the same issue on an Xbox One controller which was designed before BT 4.2 even existed. (I would need to dig it up and re-test)



Now, at the moment, my controller is indicating that it's in pairing mode or some error state, while the Steam Link says "connected". If I use the keyboard to try to disconnect, I get "Bluetooth disconnection failed: Disconnection timed out".

Meanwhile, I have sound S99steam.sh and get a constant loop of

as well as a few

and from my disconnect attempts:

Originally posted by fash:

Originally posted by slouken:

Possibly, what kind of controllers do you have?

For example, I have a Google Stadia controller[support.google.com] here. Shows up in Bluetooth Setup as Device: "StadiaJVCX-[last 4 hex digits of device BD address]", Type: "gamepad", Connected: "paired".

I'm only able to get to the menu by using a keyboard. (How am I meant to do menu actions set to controller buttons like like "Reset" with a keyboard btw? No keys seem to do the Y-button or X-button actions.)

Then if I stay on that screen, the controller might disappear from the menu. It might come back later. All of this regardless of whether the controller is off, on (searching), or pairing.

Or the controller might change from "paired" to "connected", and then I can use it. But eventually.... it will disconnect. Maybe 1 minute later, maybe 20 minutes later during a game. The controller will kick back into an idle/searching state.

Then if I use a keyboard to get back to the menu and explicitly tell it to connect to the controller, the Steam Link might connect, or it might reboot.

Today I have gotten SSH going, I tail /mnt/scratch/log/S13blueooth.sh (and the .sh.1, and the .sh.2) and nothing logs when/while these various things happen.

I do, though, have a pretty constant flood of "Can't store name for private addressed device" warnings with a couple of repeating device BD addresses.

Is this another issue like unsupported BT 4.2 DLE? Because I think I get the same issue on an Xbox One controller which was designed before BT 4.2 even existed. (I would need to dig it up and re-test)



Now, at the moment, my controller is indicating that it's in pairing mode or some error state, while the Steam Link says "connected". If I use the keyboard to try to disconnect, I get "Bluetooth disconnection failed: Disconnection timed out".

Meanwhile, I have sound S99steam.sh and get a constant loop of

Bluetooth scan toggle failures: 1 bool CShellSystem::BEnableBluetoothScan(bool) Error stopping Bluetooth discovery: [ QDBusError::Other ] "No discovery started" bool CShellSystem::BEnableBluetoothScan(bool) Attempting to cycle Bluetooth discovery bool CShellSystem::BEnableBluetoothScan(bool) Bluetooth discovery cycled successfully Bluetooth scan toggle failures: 1 bool CShellSystem::BEnableBluetoothScan(bool) Error stopping Bluetooth discovery: [ QDBusError::Other ] "No discovery started" bool CShellSystem::BEnableBluetoothScan(bool) Attempting to cycle Bluetooth discovery bool CShellSystem::BEnableBluetoothScan(bool) Bluetooth discovery cycled successfully

as well as a few

QDialog::exec: Recursive call detected

and from my disconnect attempts:

Device "/org/bluez/hci0/dev_E5_BD_0F_78_ED_E6" manual reconnect is false DisconnectBluetoothDevice "/org/bluez/hci0/dev_E5_BD_0F_78_ED_E6"

So I have a Stadia controller here, and I had to reset Bluetooth on my Steam Link (Y button on the Bluetooth settings) in order to connect it, but once I did it connected fine. It did disconnect after a while, but I'm pretty sure that was just low battery.

I'm going to charge it for a few hours and try again. Can I suggest you reset Bluetooth and charge your controller battery for a few hours so we're in the same state for testing?

Greets slouken, thanks for looking after us still.

My steam link keeps crashing back to menu/loses connection to my PC a few minutes after I boot up a game. This only started after the most recent update and happens at multiple games. Is this a known issue?

Originally posted by Hermke:

My steam link keeps crashing back to menu/loses connection to my PC a few minutes after I boot up a game. This only started after the most recent update and happens at multiple games. Is this a known issue?

Nope, can you go to the system menu and click "Save debug logs" and then start streaming to upload them.?

Originally posted by slouken:

I'm going to charge it for a few hours and try again. Can I suggest you reset Bluetooth and charge your controller battery for a few hours so we're in the same state for testing?

Sure, I've done quite a few Bluetooth resets in the course of testing. After a disconnect, the Stadia controller stays turned on, flashing white, then flashing orange, for at least an hour, so it's not a battery issue. I've seen a few threads around issues with the Stadia controller disconnecting (1 2), maybe they're not all relevant anymore but they sound just like my problem.

Anyway I set about debugging interactively w/ Opus 5.5 and after hours of kernel/firmware analysis & test cycles and $39 of tokens, I have a report. Can I send that to you?

Short summary: the SD8897's Bluetooth function stops answering even at -50 dBm (no interference) and emits no Disconnect Complete, leaving a phantom connection handle that makes every recovery path I found trip the 4-second watchdog into a reboot. I have btmon traces, dmesg, and an unattended capture harness that reproduces it.

(testing used Ethernet & a separate USB controller to rule out radio chip contention)

Originally posted by fash:

For example, I have a Google Stadia controller[support.google.com] here. Shows up in Bluetooth Setup as Device: "StadiaJVCX-[last 4 hex digits of device BD address]", Type: "gamepad", Connected: "paired".

Welp. While all the controllers we usually test with (various Xbox, PlayStation, 8BitDo, etc. ones) work fine with build 930, the Stadia controller slouken grabbed is definitely causing indigestion. I'll take a look at it more in-depth in the next couple of days.

(The offer of the report is appreciated, but since I can reproduce the problem here it's probably not needed this time.)

Originally posted by Packetdancer:

While all the controllers we usually test with (various Xbox, PlayStation, 8BitDo, etc. ones) work fine with build 930, the Stadia controller slouken grabbed is definitely causing indigestion.

Thanks for the followup, I'll switch to other BLE controllers and make a new thread if they have any issues. It's been a couple years, maybe those are all good now.

Originally posted by fash:

Thanks for the followup, I'll switch to other BLE controllers and make a new thread if they have any issues. It's been a couple years, maybe those are all good now.

In general, stock Xbox and Playstation controllers are both pretty safe bets if you have any Bluetooth ones around.

a recent latest patch sets the output volume to 75% instead of 100%
and everything was quieter

can you add the volumes to the link main audio menu, please?

the only way to change them is to begin streaming after you enable the link controller overlay, then hold the overlay keybind and adjust them
then stop stream to disable the overlay, and start stream again, if you dont use/like it enabled

Thanks for keeping the Steam Link updated! Just wanted to share a feature request and a Bluetooth audio bug I've been running into.

1. Separate Input & Output Audio Devices
If I plug in my Blue Yeti USB mic, Steam Link forces all audio output through the mic's built-in aux port. Since I use a Bluetooth headset for listening, I can't split the two. It’d be great if we could choose Input (Mic) and Output (Audio) separately in the audio settings.

Right now, my workaround is connecting the headset directly to my host PC via Bluetooth since it's close enough. But that's not ideal, as using the mic over PC Bluetooth tanks the audio quality pretty hard.

2. Bluetooth Reconnect Bug After Sudden Drops
Turning off the headset normally or powering down the Steam Link works totally fine—it reconnects without issues.

The problem only happens when the connection randomly drops while in use. Once an unexpected disconnect occurs, the two devices just refuse to talk to each other again:

A Steam Link factory reset alone doesn't fix it.

A headset reset alone doesn't fix it either.

The only way to get it working again is resetting BOTH the Steam Link and the headset so neither has any leftover pairing memory/keys of the other, and then pairing from scratch.

For context, this has happened on my Jabra Evolve 65, Jabra Evolve 75, and Sennheiser Momentum 3.

Hope this helps track down what's happening with the BT handshake :)