Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Notify users when connecting an Xbox One controller with outdated firmware and possibly provide firmware upgrade function #1777

Closed
bitrot-alpha opened this issue Jan 15, 2025 · 1 comment

Comments

@bitrot-alpha
Copy link

Your system information

  • Steam client version: 1733265492
  • SteamOS version: 3.6.20
  • Opted into Steam client beta?: No
  • Opted into SteamOS beta?: No
  • Have you checked for updates in Settings > System?: Yes

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen.

This is a feature request related to issue #1776. Atrempting to connect two Xbox One controllers with outdated firmware results in only one functioning in SteamOS.

It would be nice for SteamOS to at a bare minimum notify the user when they connect an Xbox One controller with extremely outdated firmware to update the firmware. Above and beyond would be to provide a firmware upgrade via the Steam Deck itself, as a user may not own an Xbox console or a Windows system capable of running the Xbox Accessories application.

I am unsure that Proton would be capable of running the Xbox Accessories application as Xbox Accessories is a Unified Windows Platform (UWP) application.

Steps for reproducing this issue:

  1. Connect via Bluetooth multiple Xbox One controllers with outdated firmware
  2. Observe that only one of them functions properly
@kisak-valve
Copy link
Member

Hello @bitrot-alpha, there isn't a realistic way to implement this request without there already being some common Linux firmware update framework that's been wired up and is ready to use with the specific controllers you're interested in. Running a firmware updater through a compatibility layer like Proton is asking for a bad time with bricked hardware unless extreme care is taken in advance.

@kisak-valve kisak-valve closed this as not planned Won't fix, can't repro, duplicate, stale Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants