PS4 Duoshock controller does not connect using bluetooth

Boertie · 2024-01-30 19:44:25

Hi,

First time poster here, long time lurker. Normally I would refrain asking this question (I really do not like to ask questions) but alas I don't seem to fix a problem.
When the Duoshock controller is connected using USB it works fine. Well fine, the cable/port is rotten so I kinda have to use bluetooth.

First some system info:
uname -r

6.7.2-arch1-1

pacman -Q linux

linux 6.7.2.arch1-1

output rfkill

ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked

I've installed bluez, bluez-plugins, and bluez-utils packages.
Basically I've did everything listed https://wiki.archlinux.org/title/Gamepa … luetooth_3

Output dmesg -Hw when I use the Duoshock using USB:

[  +0.000439] playstation 0003:054C:09CC.000B: Registered DualShock4 controller hw_version=0x0000b400 fw_version=0x0000a00a
[Jan30 20:14] usb 1-9.1: USB disconnect, device number 21
[Jan30 20:16] usb 1-9.1: new full-speed USB device number 22 using xhci_hcd
[  +0.101798] usb 1-9.1: New USB device found, idVendor=054c, idProduct=09cc, bcdDevice= 1.00
[  +0.000010] usb 1-9.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  +0.000003] usb 1-9.1: Product: Wireless Controller
[  +0.000003] usb 1-9.1: Manufacturer: Sony Interactive Entertainment
[  +0.016933] playstation 0003:054C:09CC.000C: hidraw8: USB HID v1.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-0000:00:14.0-9.1/input3
[  +0.058468] input: Sony Interactive Entertainment Wireless Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.1/1-9.1:1.3/0003:054C:09CC.000C/input/input30
[  +0.000153] input: Sony Interactive Entertainment Wireless Controller Motion Sensors as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.1/1-9.1:1.3/0003:054C:09CC.000C/input/input31
[  +0.000078] input: Sony Interactive Entertainment Wireless Controller Touchpad as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.1/1-9.1:1.3/0003:054C:09CC.000C/input/input32
[  +0.000276] playstation 0003:054C:09CC.000C: Registered DualShock4 controller hw_version=0x0000b400 fw_version=0x0000a00a

When I try bluetootctl, using the commands, agent on, default agent, power on, discoverable on, pairable on, scan on,
I get the following:

Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent 
[bluetooth]# Default agent request successful
[bluetooth]# power on
[bluetooth]# Changing power on succeeded
[bluetooth]# discoverable on
[bluetooth]# hci0 new_settings: powered connectable bondable ssp br/edr le secure-conn cis-central cis-peripheral 
[bluetooth]# hci0 new_settings: powered connectable discoverable bondable ssp br/edr le secure-conn cis-central cis-peripheral 
[bluetooth]# Changing discoverable on succeeded
[bluetooth]# [CHG] Controller 14:AC:60:D2:FE:B8 Discoverable: yes
[bluetooth]# pairable on
[bluetooth]# Changing pairable on succeeded
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller 14:AC:60:D2:FE:B8 Discovering: yes
[bluetooth]# exit

Somehow the duoshock does not show up.
In my mind there can be two things happening.
1.) The bluetooth is dead inside the Duoshock or It is working.
2.) I am doing something wrong.

I really hope it is 2. But how do I know it is not 1.? It seems I am doing something wrong but what.

Kind regards and thank you for entertaining my question,
Boertie

Last edited by Boertie (2024-01-31 08:05:30)

d.ALT · 2024-01-31 07:36:36

Boertie wrote:

Well fine, the cable/port is rotten so I kinda have to use bluetooth

Boertie wrote:

1.) The bluetooth is dead inside the Duoshock or

Mmm... Some overvoltage due to short circuit by a bad USB port?

Did you try resetting the DualShock4?

PARTIAL UP\DOWNGRADES ARE NOT SUPPORTED!!

Can you check if it will work by downgrading bluetooth stack?
See here: https://bbs.archlinux.org/viewtopic.php?id=288824
Do NOT proceed if Pacman wants to downgrade other packages than bluetooth ones

PARTIAL UP\DOWNGRADES ARE NOT SUPPORTED!!

Boertie · 2024-01-31 07:53:21

Hi,

Thank you for your response. The port is rotten because my kids loved to play around with the cable.
Micro-usb is one of the worst and least asshole proof designed hardware ever made. And it is being used for playing.. That being said.

I've reset the duoshock no fix there.

It seems that bluetooth is working on the Arch Linux as well.
I just can't seem to connect the duoshock controller.

[bluetooth]# Agent registered
[bluetooth]# [CHG] Controller 14:AC:60:D2:FE:B8 Pairable: yes
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller 14:AC:60:D2:FE:B8 Discovering: yes
[bluetooth]# [NEW] Device 64:E7:6F:3C:53:8E 64-E7-6F-3C-53-8E                                               <===== some Low emitting bluetooth device
[bluetooth]# [NEW] Device 75:26:13:37:04:C8 75-26-13-37-04-C8                                              <===== some Low emitting bluetooth device
[bluetooth]# [NEW] Device A0:9E:1A:A3:B9:1D Polar Vantage M2 A3B91D21                          <===== not mine
[bluetooth]# [CHG] Device 64:E7:6F:3C:53:8E RSSI: 0xffffff93 (-109)
[bluetooth]# [CHG] Device 64:E7:6F:3C:53:8E ManufacturerData.Key: 0x004c (76)
[bluetooth]# [CHG] Device 64:E7:6F:3C:53:8E ManufacturerData.Value:
[bluetooth]#   10 06 20 1e 57 e6 d5 f1                          .. .W...        
[bluetooth]# [CHG] Device 64:E7:6F:3C:53:8E RSSI: 0xffffffa4 (-92)
[bluetooth]# [CHG] Device 75:26:13:37:04:C8 RSSI: 0xffffff94 (-108)
[bluetooth]# [CHG] Device 64:E7:6F:3C:53:8E RSSI: 0xffffff9a (-102)
[bluetooth]# [CHG] Device 64:E7:6F:3C:53:8E RSSI: 0xffffff91 (-111)
[bluetooth]# [CHG] Device 64:E7:6F:3C:53:8E RSSI: 0xffffff9b (-101)
[bluetooth]# [CHG] Device 75:26:13:37:04:C8 RSSI: 0xffffff9c (-100)
[bluetooth]# devices

The Polar Vantage m2 is not mine (probably it is from the neighbor). So it seems like the bluetooth is working on Arch as well.
I tried connecting the duoshock on my Iphone and it is discoverable there and it is connected.

It just seems that Arch and my Duoshock do not like to pair.

Last edited by Boertie (2024-01-31 07:58:58)

Boertie · 2024-02-01 20:40:20

Can you check if it will work by downgrading bluetooth stack?
See here: https://bbs.archlinux.org/viewtopic.php?id=288824
Do NOT proceed if Pacman wants to downgrade other packages than bluetooth ones
PARTIAL UP\DOWNGRADES ARE NOT SUPPORTED!!

The duoshock never showed up in the list. I've tried downgrading the packages but no fix here.
Thank you for your suggestions.

I did notice something else, I think it is not related but it seems like the WiFi device failed to load.
According to the specs of the motherboard it is the same board.

[    5.148121] ath12k_pci 0000:06:00.0: failed to get 16 MSI vectors, only -28 available
[    5.148311] ath12k_pci 0000:06:00.0: failed to alloc msi: -28
[    5.148507] ath12k_pci: probe of 0000:06:00.0 failed with error -28

Might that be an issue why the duoshock is not showing up in the list. But than I wonder, why do others show up?

Last edited by Boertie (2024-02-01 20:46:45)

d.ALT · 2024-02-02 07:49:19

Please show us you hardware:

# lspci -vnn

# lsusb

Boertie · 2024-02-02 08:56:54

Hi d.Alt,

Thank you for your time. The following output:

lspci -vnn

00:00.0 Host bridge [0600]: Intel Corporation Device [8086:a700] (rev 01)
	DeviceName: Onboard - Other
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000]
	Flags: bus master, fast devsel, latency 0

00:01.0 PCI bridge [0604]: Intel Corporation Device [8086:a70d] (rev 01) (prog-if 00 [Normal decode])
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000]
	Flags: bus master, fast devsel, latency 0, IRQ 120
	Bus: primary=00, secondary=01, subordinate=03, sec-latency=0
	I/O behind bridge: 3000-3fff [size=4K] [16-bit]
	Memory behind bridge: 50d00000-50ffffff [size=3M] [32-bit]
	Prefetchable memory behind bridge: 40000000-501fffff [size=258M] [32-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:01.1 PCI bridge [0604]: Intel Corporation Device [8086:a72d] (rev 01) (prog-if 00 [Normal decode])
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000]
	Flags: bus master, fast devsel, latency 0, IRQ 121
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: [disabled] [16-bit]
	Memory behind bridge: 51000000-510fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:14.0 USB controller [0c03]: Intel Corporation Device [8086:7a60] (rev 11) (prog-if 30 [XHCI])
	DeviceName: Onboard - Other
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007]
	Flags: bus master, medium devsel, latency 0, IRQ 126
	Memory at 51100000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: mei_me, xhci_pci

00:14.2 RAM memory [0500]: Intel Corporation Device [8086:7a27] (rev 11)
	DeviceName: Onboard - Other
	Flags: fast devsel
	Memory at 51114000 (64-bit, non-prefetchable) [disabled] [size=16K]
	Memory at 51124000 (64-bit, non-prefetchable) [disabled] [size=4K]
	Capabilities: <access denied>

00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:7a4c] (rev 11)
	DeviceName: Onboard - Other
	Flags: bus master, fast devsel, latency 0, IRQ 27
	Memory at 50200000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:15.1 Serial bus controller [0c80]: Intel Corporation Device [8086:7a4d] (rev 11)
	DeviceName: Onboard - Other
	Flags: bus master, fast devsel, latency 0, IRQ 40
	Memory at 50201000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:15.2 Serial bus controller [0c80]: Intel Corporation Device [8086:7a4e] (rev 11)
	DeviceName: Onboard - Other
	Flags: bus master, fast devsel, latency 0, IRQ 29
	Memory at 50202000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:15.3 Serial bus controller [0c80]: Intel Corporation Device [8086:7a4f] (rev 11)
	DeviceName: Onboard - Other
	Flags: bus master, fast devsel, latency 0, IRQ 43
	Memory at 50203000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:16.0 Communication controller [0780]: Intel Corporation Device [8086:7a68] (rev 11)
	DeviceName: Onboard - Other
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:1c3a]
	Flags: bus master, fast devsel, latency 0, IRQ 160
	Memory at 5111f000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation Device [8086:7a62] (rev 11) (prog-if 01 [AHCI 1.0])
	DeviceName: Onboard - SATA
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:b005]
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 125
	Memory at 51118000 (32-bit, non-prefetchable) [size=8K]
	Memory at 5111e000 (32-bit, non-prefetchable) [size=256]
	I/O ports at 4050 [size=8]
	I/O ports at 4040 [size=4]
	I/O ports at 4020 [size=32]
	Memory at 5111d000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	Kernel driver in use: ahci

00:19.0 Serial bus controller [0c80]: Intel Corporation Device [8086:7a7c] (rev 11)
	DeviceName: Onboard - Other
	Flags: bus master, fast devsel, latency 0, IRQ 31
	Memory at 5111c000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:19.1 Serial bus controller [0c80]: Intel Corporation Device [8086:7a7d] (rev 11)
	DeviceName: Onboard - Other
	Flags: bus master, fast devsel, latency 0, IRQ 32
	Memory at 5111b000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:7a38] (rev 11) (prog-if 00 [Normal decode])
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
	Flags: bus master, fast devsel, latency 0, IRQ 122
	Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
	I/O behind bridge: [disabled] [16-bit]
	Memory behind bridge: 50400000-508fffff [size=5M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1c.3 PCI bridge [0604]: Intel Corporation Device [8086:7a3b] (rev 11) (prog-if 00 [Normal decode])
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
	Flags: bus master, fast devsel, latency 0, IRQ 123
	Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
	I/O behind bridge: [disabled] [16-bit]
	Memory behind bridge: 50a00000-50bfffff [size=2M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:7a04] (rev 11)
	DeviceName: Onboard - Other
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
	Flags: bus master, fast devsel, latency 0

00:1f.3 Audio device [0403]: Intel Corporation Device [8086:7a50] (rev 11)
	DeviceName: Onboard - Sound
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:a0d5]
	Flags: bus master, fast devsel, latency 32, IRQ 171
	Memory at 51110000 (64-bit, non-prefetchable) [size=16K]
	Memory at 50c00000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:7a23] (rev 11)
	DeviceName: Onboard - Other
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
	Flags: medium devsel, IRQ 18
	Memory at 5111a000 (64-bit, non-prefetchable) [size=256]
	I/O ports at efa0 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:7a24] (rev 11)
	DeviceName: Onboard - Other
	Flags: fast devsel
	Memory at 50204000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: intel-spi
	Kernel modules: spi_intel_pci

01:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch [1002:1478] (rev 10) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at 50f00000 (32-bit, non-prefetchable) [size=16K]
	Bus: primary=01, secondary=02, subordinate=03, sec-latency=0
	I/O behind bridge: 3000-3fff [size=4K] [16-bit]
	Memory behind bridge: 50d00000-50efffff [size=2M] [32-bit]
	Prefetchable memory behind bridge: 40000000-501fffff [size=258M] [32-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch [1002:1479] (rev 10) (prog-if 00 [Normal decode])
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch [1002:1479]
	Flags: bus master, fast devsel, latency 0, IRQ 124
	Bus: primary=02, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 3000-3fff [size=4K] [16-bit]
	Memory behind bridge: 50d00000-50efffff [size=2M] [32-bit]
	Prefetchable memory behind bridge: 40000000-501fffff [size=258M] [32-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900 XTX] [1002:744c] (rev c8) (prog-if 00 [VGA controller])
	Subsystem: Sapphire Technology Limited NITRO+ RX 7900 XTX Vapor-X [1da2:e471]
	Flags: bus master, fast devsel, latency 0, IRQ 173
	Memory at 40000000 (64-bit, prefetchable) [size=256M]
	Memory at 50000000 (64-bit, prefetchable) [size=2M]
	I/O ports at 3000 [size=256]
	Memory at 50d00000 (32-bit, non-prefetchable) [size=1M]
	Expansion ROM at 50e00000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 HDMI/DP Audio [1002:ab30]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 HDMI/DP Audio [1002:ab30]
	Flags: bus master, fast devsel, latency 0, IRQ 172
	Memory at 50e20000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

04:00.0 Non-Volatile memory controller [0108]: Sandisk Corp WD Black SN850X NVMe SSD [15b7:5030] (rev 01) (prog-if 02 [NVM Express])
	Subsystem: Sandisk Corp WD Black SN850X NVMe SSD [15b7:5030]
	Flags: bus master, fast devsel, latency 0, IRQ 17
	Memory at 51000000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: nvme
	Kernel modules: nvme

05:00.0 Ethernet controller [0200]: Aquantia Corp. AQC113C NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:14c0] (rev 03)
	Subsystem: Gigabyte Technology Co., Ltd AQC113C NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1458:e000]
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at 50800000 (64-bit, non-prefetchable) [size=512K]
	Memory at 508a0000 (64-bit, non-prefetchable) [size=4K]
	Memory at 50400000 (64-bit, non-prefetchable) [size=4M]
	Expansion ROM at 50880000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: atlantic
	Kernel modules: atlantic

06:00.0 Network controller [0280]: Qualcomm Technologies, Inc Device [17cb:1107] (rev 01)
	Subsystem: Foxconn International, Inc. Device [105b:e0fb]
	Flags: fast devsel
	Memory at 50a00000 (64-bit, non-prefetchable) [size=2M]
	Capabilities: <access denied>
	Kernel modules: ath12k

lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0bda:5420 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
Bus 001 Device 003: ID 0bda:5420 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
Bus 001 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 005: ID 046d:c223 Logitech, Inc. G11/G15 Keyboard / USB Hub
Bus 001 Device 006: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 007: ID 048d:5702 Integrated Technology Express, Inc. RGB LED Controller
Bus 001 Device 008: ID 046d:c221 Logitech, Inc. G11/G15 Keyboard / Keyboard
Bus 001 Device 009: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 010: ID 1532:000c Razer USA, Ltd Lachesis
Bus 001 Device 011: ID 046d:c222 Logitech, Inc. G15 Keyboard / LCD
Bus 001 Device 012: ID 048d:5702 Integrated Technology Express, Inc. RGB LED Controller
Bus 001 Device 013: ID 1e71:300c NZXT NZXT Kraken Elite
Bus 001 Device 014: ID 0489:e10d Foxconn / Hon Hai 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0bda:0420 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 002 Device 003: ID 0bda:0420 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 002 Device 004: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 002 Device 005: ID 0bda:0411 Realtek Semiconductor Corp. Hub

My bluetooth controller is onboard.

d.ALT · 2024-02-02 10:15:41

Can you please try the whole DualShock 3 - 3.12.2 Pairing via Bluetooth paragraph?

Last edited by d.ALT (2024-02-02 10:16:10)

Boertie · 2024-02-02 13:17:31

Can you please try the whole DualShock 3 - 3.12.2 Pairing via Bluetooth paragraph?

I've (re)installed bluez bluez-utils bluez-plugins.

Started the Bluetooth#Pairing according to this page: https://wiki.archlinux.org/title/Bluetooth#Pairing

Then I turned on the controller by pressing the middle 'PS' button, the white LED was flashing, during that flashing I plugged in the USB cable.
The LED-color turned to red and after a few seconds it turned to blue again. However, there was no prompt in bluetoothctl.

To connect your PS3 controller to your computer using Bluetooth, you first need to install bluez and bluez-plugins then connect your controller via USB. A pop-up should appear asking for pairing.

Whenever I connect the controller with USB, it works but I never see a pop-up appearing to ask for pairing.

I've changed the

 /etc/bluetooth/input.conf

with:

ClassicBondedOnly=false

and restarted the service and made sure it was started.

 sudo vi /etc/bluetooth/input.conf
 sudo systemctl stop bluetooth.service 
 sudo systemctl start bluetooth.service 
sudo systemctl status bluetooth.service

I've read somewhere I could add the following as well the input.conf file

UserspaceHID=true

No idea, what it does, but it didn't help.

As a hail marry I've also installed the ds4drv AUR packages (and corresponding packages like bluez-utils-compat) but to no avail.
Somehow I think the bluetooth is not playing nicely because the WiFi card is also not loaded (it fails to load). I do seem to find some devices, but also not the Iphone.
However I do not see any errors regarding the bluetoothservice.

Last edited by Boertie (2024-02-02 13:59:31)

d.ALT · 2024-02-02 13:54:27

Boertie wrote:

Then I turned on the controller by pressing the middle 'PS' button

DualShock4 controllers need to be first-time paired by starting the pair operation via the SHARE+PS buttons combo (keep 'em pressed until the back LED-bar starts rapidly flashing).

Boertie wrote:

The LED-color turned to red and after a few seconds it turned to blue again

Orange or red? Usually, the red LED indicates that the device has acknowledged being connected as the second DualShock4 controller. Are you having some other(s) "parent(s)" around which could claim the DualShock4 bluetooth connection??

Boertie wrote:

As a hail marry I've also installed the ds4drv AUR packages (and corresponding packages like bluez-utils-compat) but to no avail.

Nope, I confirm there's no need for it at all.

Boertie · 2024-02-02 14:42:10

DualShock4 controllers need to be first-time paired by starting the pair operation via the SHARE+PS buttons combo (keep 'em pressed until the back LED-bar starts rapidly flashing).

When I press the PS and Share button at the same time, it does show up on my iphone not on my Arch in bluetoothctl or blueman.

Are you having some other(s) "parent(s)" around which could claim the DualShock4 bluetooth connection??

No, after the pairing-sequence (as it won't find any connection) the Duoshock turns off after a while. It might connect as red because it probably made a second profile on my Arch when connected again through USB?

Arch Linux

#1 2024-01-30 19:44:25

PS4 Duoshock controller does not connect using bluetooth

#2 2024-01-31 07:36:36

Re: PS4 Duoshock controller does not connect using bluetooth

#3 2024-01-31 07:53:21

Re: PS4 Duoshock controller does not connect using bluetooth

#4 2024-02-01 20:40:20

Re: PS4 Duoshock controller does not connect using bluetooth

#5 2024-02-02 07:49:19

Re: PS4 Duoshock controller does not connect using bluetooth

#6 2024-02-02 08:56:54

Re: PS4 Duoshock controller does not connect using bluetooth

#7 2024-02-02 10:15:41

Re: PS4 Duoshock controller does not connect using bluetooth

#8 2024-02-02 13:17:31

Re: PS4 Duoshock controller does not connect using bluetooth

#9 2024-02-02 13:54:27

Re: PS4 Duoshock controller does not connect using bluetooth

#10 2024-02-02 14:42:10

Re: PS4 Duoshock controller does not connect using bluetooth

Board footer