Steam Link

Steam Link

Backbone one input
After updating to 1.3.28 the steam link connect prompt would double up the recognized controller duplicating it in the connected controllers settings.

This broke any controller functionally for the backbone one.

Reverting to 1.3.23 restored functionality.
Running Android 16 on a pixel 8 pro
< >
Showing 1-9 of 9 comments
I'm running 1.3.29 on a Google Pixel 6a with Android 16 and I only see one controller in the connected controller settings, and I'm not getting doubled inputs.

However, I also don't have the Backbone app installed. Are you using that?
I updated to 1.3.29 hoping it would fix the issue but the issue persists. I do not use the backbone app, I only use it as a controller in steam link. Does steam link prompt you to connect the backbone controller on the steam link app if you
Launch Steam Link -> Connect backbone controller

"Allow Steam Link to access Backbone One Playstation? Edition?"
"Cancel" "Ok"

pressing outside the modal or pressing cancel still allows the backbone to connect but the "second virtual controller" does not connect allowing regular functionality.

Pressing Ok shows the 2 controllers and then does not work while streaming.

Note that outside of the steam link app the controller navigates around the phone as expected.
Here is a quick screen recording of the 2 behaviors note that I press Ok on the first pass and cancel the second.

Each run I launch Steam link with the backbone disconnected and then plug it in once the app is open

https://imgur.com/a/llA2PnU
Ahh, that makes sense. I'm not using the PlayStation Edition, so Steam Link isn't trying to open it as a USB PlayStation controller.
Can you send a link to the Steam logs\streaming_log.txt after streaming in the duplicate controller state?
streaming_log [gist.github.com]

remote_connections [gist.github.com]
It appears to be a conflict happening. note the duplicate hardware
[2026-05-19 18:09:30][9472.886006] CLIENT: Got control packet k_EStreamControlControllerConfigMsg [2026-05-19 18:09:30][9472.890722] CLIENT: Sending HID device 358a/0304/-1 Labs, Inc. Backbone One PlayStation? Edition at sdl://48 [2026-05-19 18:09:30][9472.890741] CLIENT: Sending HID device 358a/0304/-1 Labs, Inc. Backbone One PlayStation? Edition at sdl://49 [2026-05-19 18:09:30][9472.890752] CLIENT: Targeting 59.88 FPS
vs just a singular device
[2026-05-19 15:50:18][1121.095844] CLIENT: SDL Mapping for 358a/304: 050040778a35000004030000ffff3f00,*,a:b0,b:b1,x:b2,y:b3,back:b4,guide:b5,start:b6,leftstick:b7,rightstick:b8,leftshoulder:b9,rightshoulder:b10,dpup:b11,dpdown:b12,dpleft:b13,dpright:b14,leftx:a0,lefty:a1,rightx:a2,righty:a3,lefttrigger:a4,righttrigger:a5,crc:7740,platform:Android, [2026-05-19 15:50:18][1121.146829] Setting target framerate: 119.75 [timing: game 0.00, capture 0.15, convert 0.27, encode 2.97, network 3.55, decode 11.07, display 0.00] [2026-05-19 15:50:18][1121.197914] CLIENT: Sending HID device 358a/0304/-1 Labs, Inc. Backbone One PlayStation® Edition at sdl://46 [2026-05-19 15:50:18][1121.197936] CLIENT: Targeting 59.88 FPS
Fixed in 1.3.30 thanks for the quick patch!
You're welcome!
< >
Showing 1-9 of 9 comments
Per page: 1530 50