Bluetooth dropping connection almost instant on every device connected.

[levi2m]

Describe the bug

When trying to connect, any device that is already paired (for example a couple of DualShock 4's i've), they instantly drop connection as you can see in the screenshot bellow:

Note that when this does happen, the controllers doesn't show a specific color as when they show when forced-connected or via USB. They just keep blinking white as waiting for the host to accept connection.

But, the controllers can connect and work with bluetooth if they got forced to connect through bluetoothctl or Steam's system > bluetooth > device > connect.

What did you expect to happen?

Power on machine with the PS button on the DS4's is a feature at this point, but would love to see it connecting and keeping that way when the system is full powered on and idle.

Output of rpm-ostree status

l2m@bazzy:~$ rpm-ostree status
State: idle
Deployments:
  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:f23de493b70d8900546a7f485a9110c75df9c8d7529626ce4580d557b7349587
                  Version: 40.20240826.0 (2024-08-27T06:59:55Z)
          LayeredPackages: ncdu

● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:f23de493b70d8900546a7f485a9110c75df9c8d7529626ce4580d557b7349587
                  Version: 40.20240826.0 (2024-08-27T06:59:55Z)
          LayeredPackages: ncdu

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:40-testing
                   Digest: sha256:6161ea5dfb03263283552b128f31b3d23f4c3ebaeb36a8b44ea5dee1d1dc4321
                  Version: testing-40.20240822.3 (2024-08-23T20:45:29Z)
          LayeredPackages: ncdu

Hardware

• MB - MS-TZZ H510ITX
• CPU - Intel i5-11400f
• GPU - AMD Radeon RX580 2048SP
• RAM - 16GB (8x2) Asgard Loki 3200mhz

neofetch:

Extra information or context

No response

[KyleGospo]

@YeGop0218 can you elaborate more on what this zip does?

This is malware, ignore it. Github is getting spammed.

[levi2m]

@KyleGospo is there any info i can provide that can help you dive deeper into it?

[dosubot[bot]]

Hi, @levi2m. I'm Dosu, and I'm helping the bazzite team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• DualShock 4 controllers disconnect shortly after pairing via Bluetooth.
• Successful connections occur through specific commands or applications.
• Controllers fail to maintain a connection when the system is idle.
• A zip file mentioned by another user is identified as malware and should be ignored.
• You are seeking further guidance on what information could assist in resolving the issue.

Next Steps:

• Please let me know if this issue is still relevant to the latest version of the bazzite repository by commenting here to keep the discussion open.
• If there is no further activity, this issue will be automatically closed in 14 days.

Thank you for your understanding and contribution!

[levi2m]

hey @dosubot

yes, definitely still happening

my way of using the DS4s even with this issue is every time I boot up the machine, I need to go into remote console and pair again the DS4 im currently using

I can't say how much this issue is bugging me, and also happens on another machine I have that is a ryzen laptop

[Celer21]

Hi, I have same issue with Xbox Wireless Controller. I have 3 xbox controllers and all of them are disconnecting or cannot be paired (firmware is up to date). So I have to connect usb cable to controllers.

My Wife approval factor of Bazzite is now quit low 1/10 😄

[noelmiller]

Are these issues still happening on Bazzite 42?

[dosubot[bot]]

To improve the reliability of your DualShock 4 controller connections, you can try disabling Bluetooth Enhanced Re-Transmission Mode (ERTM). This has been known to help with connection issues for certain Bluetooth devices, including game controllers. You can disable ERTM by executing the following command in your terminal:

echo 1 > /sys/module/bluetooth/parameters/disable_ertm

This should help maintain a stable connection with your controllers ^[1].

Additionally, a maintainer has already been looped in, so they might provide further assistance or insights into the issue.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[lmirel]

To improve the reliability of your DualShock 4 controller connections, you can try disabling Bluetooth Enhanced Re-Transmission Mode (ERTM). This has been known to help with connection issues for certain Bluetooth devices, including game controllers. You can disable ERTM by executing the following command in your terminal:

echo 1 > /sys/module/bluetooth/parameters/disable_ertm This should help maintain a stable connection with your controllers [1].

Additionally, a maintainer has already been looped in, so they might provide further assistance or insights into the issue.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

doesn't seem to change connect/disconnect behavior in any way

[levi2m]

this is still happening with the latest stable and testing branches updates anybody still having the same issue?

[StarSister]

I also have this problem I think. I have the Xbox Wireless controller but can't get it to work via Bluetooth. I can initially pair with it, but right after the settings report the controller as paired, the LED on the controller keeps flashing as if it wasn’t connected. When I wait for the controller to time out and turn off automatically (or turn it off manually), then turn it back on again, it keeps connecting/disconnecting continuously, very fast.

[StarSister]

I just solved my failing controller connection by updating the controller firmware via the Xbox Accessories app on Windows and now it does connect successfully. I still have to test it with gaming but at least the connection is stable and Steam does recognize and is able to interact with the controller. But if I encounter any issues I will add it here. Also I'm curious why updating the controller firmware did help in my case but not in other people's cases (at least not always).