8bitdo sn30 Pro cannot connect after upgrade to Batocera v40

olind commented 2 months ago

Batocera build version

40 2024/08/03 05:52

Your architecture

Raspberry_Pi_3_Model_B_Plus_Rev_1_3

Your Graphic Processor Unit(s) (GPU)

built in

Issue description

I have been using Batocera 38 and 39 with one 8bitdo SN30 Pro and one 8bitdo Lite 2 with Bluetooth without issues. After upgrading to v40 I cannot get any of them to connect.

I removed all BT devices in batocera and tried both methods in the GUI. Without succes. I then tried to remove my /system/userdata folder, rebooted and no success. Also tried to manually connect it with the commands in the terminal as described here: https://wiki.batocera.org/bluetooth_controllers_-_manual_setup

I also made sure both had latest 8bitdo firmware.

I starting the controllers with x+start and then set them to pairing mode.

bluetoothctl

agent on
default-agent
power on
scan on

pair E4:17:D8:B6:F4:79 and connect E4:17:D8:B6:F4:79 gives I suspect it might have something to do with [8Bitdo SN30 Pro]# Failed to connect: org.bluez.Error.NotAvailable br-connection-profile-unavailable but I couldn't find anything?

output from bluetoothctl:

[bluetooth]# [NEW] Device E4:17:D8:B6:F4:79 8Bitdo SN30 Pro
[bluetooth]# hci0 type 7 discovering off

[bluetooth]# hci0 device_flags_changed: E4:17:D8:B6:F4:79 (BR/EDR)
[bluetooth]#      supp: 0x00000001  curr: 0x00000000
[bluetooth]# hci0 type 7 discovering off
[bluetooth]# hci0 E4:17:D8:B6:F4:79 type BR/EDR connected eir_len 22
[CHG] Device E4:17:D8:B6:F4:79 Connected: yes
[8Bitdo SN30 Pro]# hci0 new_link_key E4:17:D8:B6:F4:79 type 0x04 pin_len 0 store_hint 1
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:B6:F4:79 Bonded: yes
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:B6:F4:79 Modalias: usb:v045Ep02E0d0903
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:B6:F4:79 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:B6:F4:79 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:B6:F4:79 ServicesResolved: yes
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:B6:F4:79 Paired: yes
[8Bitdo SN30 Pro]# Pairing successful
[8Bitdo SN30 Pro]# hci0 E4:17:D8:B6:F4:79 type BR/EDR disconnected with reason 2
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:B6:F4:79 ServicesResolved: no
[CHG] Device E4:17:D8:B6:F4:79 Connected: no

[bluetooth]# connect E4:17:D8:B6:F4:79 
Attempting to connect to E4:17:D8:B6:F4:79
[bluetooth]# hci0 E4:17:D8:B6:F4:79 type BR/EDR connected eir_len 22
[CHG] Device E4:17:D8:B6:F4:79 Connected: yes
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:B6:F4:79 ServicesResolved: yes
[8Bitdo SN30 Pro]# Failed to connect: org.bluez.Error.NotAvailable br-connection-profile-unavailable
[8Bitdo SN30 Pro]# hci0 type 7 discovering on
[8Bitdo SN30 Pro]# [CHG] Device 7F:3A:32:32:04:73 ManufacturerData.Key: 0x004c (76)
[8Bitdo SN30 Pro]# [CHG] Device 7F:3A:32:32:04:73 ManufacturerData.Value:

Detailed reproduction steps

Described it in the issue description

Details of any attempts to fix this yourself

No response

Details of any modifications you have made to Batocera.

No

Logs and data

No response

Jarthianur commented 2 months ago

Second that, exact same behavior for me. Failed to connect: org.bluez.Error.NotAvailable br-connection-profile-unavailable

I've tried Nintendo Pro and PS4 controller. Bluetooth is given by Asus BT500 dongle (have also tested with another older dongle, which I don't know the name of). Both dongles verified to be working on various linux systems. All other peripherals disconnected, in case it's a power issue. There are similar issues from 2021/22 on various forums regarding bluez to be not working, unless some pulseaudio-bluetooth package is installed, or service started, or switch to pipewire. I don't know if that is related anyway.

Model: Hardkernel_ODROID_XU4 System: Linux 6.6.27 Architecture: armv7l Board: odroidxu4 CPU Model: ARMv7 Processor rev 3 (v7l) CPU Cores: 4 / CPU Threads: 8 CPU Frequency: 1400/2000 MHz Temperature: 42°C Available Memory: 1611/1979 MB Display Resolution: 1920x1080 Display Refresh Rate: 60.000Hz Data Partition Format: ext4 Data Partition Available Space: 55G OS version: 40 2024/08/02 08:03

olind commented 2 months ago

Please tell if you find any workarounds - does it for example solve the problem to do a fresh install?

anonymouz commented 2 months ago

Can you try:

In the menu: Forget a Bluetooth device: Remove All
From the command line: bluetoothctl scan on
On the 8bitdo: X + start (two lights indicating x-input)
On the 8bitdo: sync button (scanning lights)
From the command line:
Output from scan: [NEW] Device E4:17:XX:XX:XX:XX 8Bitdo SN30 Pro trust E4:17:XX:XX:XX:XX (wait for "yes") pair E4:17:XX:XX:XX:XX (wait for "successful") connect E4:17:XX:XX:XX:XX (wait for "successful")

After a reboot; just press "start" on the 8bitdo and it should work... Well... it works on my machine...

Can you give some feedback!?

olind commented 2 months ago

Thanks for your reply. I tried but cannot get it to connect. I have removed it from the menu before I after running its back in the menu. It still seems to fail.

Log no 1 is the output from trust, pair, connect.

I then rebooted and started the controller with just the start button (2 flashing lights). watched the bluetooth output from scan and maybe there can be a clue on [8Bitdo SN30 Pro]# hci0 E4:17:D8:1C:F4:79 type BR/EDR disconnected with reason 2 ?

More suggestions or things to try?

Log no1

bluetooth]# hci0 type 7 discovering off
[bluetooth]# hci0 E4:17:D8:1C:F4:79 type BR/EDR connected eir_len 22
[CHG] Device E4:17:D8:1C:F4:79 Connected: yes
[8Bitdo SN30 Pro]# hci0 new_link_key E4:17:D8:1C:F4:79 type 0x04 pin_len 0 store_hint 1
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 Bonded: yes
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 Paired: yes
[8Bitdo SN30 Pro]# [DEL] Device 69:70:3E:92:26:7A 69-70-3E-92-26-7A
hci0 E4:17:D8:1C:F4:79 type BR/EDR disconnected with reason 2
[CHG] Device E4:17:D8:1C:F4:79 Connected: no
[bluetooth]# trust E4:17:D8:1C:F4:79
[bluetooth]# Changing E4:17:D8:1C:F4:79 trust succeeded
[bluetooth]# connect E4:17:D8:1C:F4:79
Attempting to connect to E4:17:D8:1C:F4:79
hci0 type 7 discovering on
[CHG] Device 40:9B:83:86:A6:0B ManufacturerData.Key: 0x004c (76)
[CHG] Device 40:9B:83:86:A6:0B ManufacturerData.Value:
  0c 0e 08 49 42 5d ea 9b 0f ae 0b 6d 42 88 87 ab  ...IB].....mB...
  10 06 42 1d 43 99 52 48                          ..B.C.RH
[CHG] Device 43:41:16:46:1E:EF ManufacturerData.Key: 0x004c (76)
[CHG] Device 43:41:16:46:1E:EF ManufacturerData.Value:
  0c 0e 08 49 42 5d ea 9b 0f ae 0b 6d 42 88 87 ab  ...IB].....mB...
  10 06 42 1d 43 99 52 48                          ..B.C.RH
[bluetooth]# pair E4:17:D8:1C:F4:79
Attempting to pair with E4:17:D8:1C:F4:79
[bluetooth]# Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# hci0 E4:17:D8:1C:F4:79 type BR/EDR connected eir_len 17
[CHG] Device E4:17:D8:1C:F4:79 Connected: yes
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 Modalias: usb:v045Ep02E0d0903
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 ServicesResolved: yes
[8Bitdo SN30 Pro]# Failed to connect: org.bluez.Error.NotAvailable br-connection-profile-unavailable
[8Bitdo SN30 Pro]# hci0 E4:17:D8:1C:F4:79 type BR/EDR disconnected with reason 2
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 ServicesResolved: no
[CHG] Device E4:17:D8:1C:F4:79 Connected: no
[bluetooth]# [CHG] Device E4:17:D8:1C:F4:79 RSSI: 0xffffffc7 (-57)
[bluetooth]# hci0 type 7 discovering off

Log no 2

[bluetooth]# [NEW] Device 61:49:5B:22:8C:EF 61-49-5B-22-8C-EF
[bluetooth]# hci0 E4:17:D8:1C:F4:79 type BR/EDR connected eir_len 22
[CHG] Device E4:17:D8:1C:F4:79 Connected: yes
[8Bitdo SN30 Pro]# hci0 type 7 discovering off
[8Bitdo SN30 Pro]# hci0 E4:17:D8:1C:F4:79 type BR/EDR disconnected with reason 2
[CHG] Device E4:17:D8:1C:F4:79 Connected: no
[bluetooth]# hci0 type 7 discovering on
[bluetooth]# [NEW] Device 58:83:0D:7D:B9:6E 58-83-0D-7D-B9-6E
[bluetooth]# [NEW] Device 65:63:D6:1C:25:38 65-63-D6-1C-25-38
[bluetooth]# [NEW] Device 7B:79:E2:E3:07:C7 7B-79-E2-E3-07-C7
[bluetooth]# [NEW] Device 69:40:A3:2C:60:A0 69-40-A3-2C-60-A0

olind commented 2 months ago

Is this the same / similar issue https://github.com/bluez/bluez/issues/605 ?

anonymouz commented 2 months ago

Thanks for your reply. I tried but cannot get it to connect. I have removed it from the menu before I after running its back in the menu. It still seems to fail.

Log no 1 is the output from trust, pair, connect. [snip]

I had similar problems... but I was too slow... Can you try again as fast as possible?

From what I read you probably did this, but to be sure: when removed from the menu; please reboot, sometimes in-memory state can cause problems with all the interacting pieces.

And, again to be sure, did you read this? https://wiki.batocera.org/bluetooth_controllers_-_manual_setup

Is this the same / similar issue https://github.com/bluez/bluez/issues/605 ?

Looks similar indeed. There seems to be a bluez update that breaks stuff in the chain. The batocera defaults are set to be backwards compatible (and look ok) but changed default settings in bluez could also be the culprit.

anonymouz commented 2 months ago

Also a tip for readers of this thread; do NOT pair Wii controllers in the Batocera menu; first start the Wii emulator (dolphin), then press the sync button on the controller and then dolphin pairs the controller. This is in the Batocera manual but I glanced over it the first time...

Jarthianur commented 1 month ago

So I haven't tested much more on the XU4 as of now, but on an x86-64 build. Using the same BT500 dongle connected via USB 2 port to an amd64 HTPC on latest batocera works flawlessly. The XU4 and RPi3 actually have only one thing in common, and that is a ARMv7 32bit architecture. Hence I would suggest it is some incompatibility on the bluez drivers side. I have an RPi5 (64bit ARMv8) at hand, where I can test in the next few days. Let's see how that works...

olind commented 1 month ago

I'll try to find another memory card - if so I could try a fresh install. I'm afraid of loosing my save states etc. if I reinstall.

I write back if i manage to find one.

olind commented 1 month ago

I just tested again (and quickly) with the same problem.

Removed all controllers in GUI
Rebooted

bluetoothctl
scan on

x+start
pair

trust E4:17:D8:1C:F4:79
pair E4:17:D8:1C:F4:79
connect E4:17:D8:1C:F4:79

Gives

[bluetooth]# [NEW] Device E4:17:D8:1C:F4:79 8Bitdo SN30 Pro
[bluetooth]# trust E4:17:D8:1C:F4:79
[bluetooth]# [CHG] Device E4:17:D8:1C:F4:79 Trusted: yes
[bluetooth]# Changing E4:17:D8:1C:F4:79 trust succeeded
[bluetooth]# hci0 type 7 discovering off
[bluetooth]# pair E4:17:D8:1C:F4:79
Attempting to pair with E4:17:D8:1C:F4:79
[bluetooth]# hci0 device_flags_changed: E4:17:D8:1C:F4:79 (BR/EDR)
[bluetooth]#      supp: 0x00000001  curr: 0x00000000
[bluetooth]# hci0 E4:17:D8:1C:F4:79 type BR/EDR connected eir_len 22
[CHG] Device E4:17:D8:1C:F4:79 Connected: yes
[8Bitdo SN30 Pro]# hci0 new_link_key E4:17:D8:1C:F4:79 type 0x04 pin_len 0 store_hint 1
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 Bonded: yes
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 Modalias: usb:v045Ep02E0d0903
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 ServicesResolved: yes
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 Paired: yes
[8Bitdo SN30 Pro]# Pairing successful
[8Bitdo SN30 Pro]# hci0 E4:17:D8:1C:F4:79 type BR/EDR disconnected with reason 2
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 ServicesResolved: no
[CHG] Device E4:17:D8:1C:F4:79 Connected: no
[bluetooth]# connect E4:17:D8:1C:F4:79
Attempting to connect to E4:17:D8:1C:F4:79
[bluetooth]# hci0 E4:17:D8:1C:F4:79 type BR/EDR connected eir_len 22
[CHG] Device E4:17:D8:1C:F4:79 Connected: yes
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 ServicesResolved: yes
[8Bitdo SN30 Pro]# Failed to connect: org.bluez.Error.NotAvailable br-connection-profile-unavailable
[8Bitdo SN30 Pro]# hci0 type 7 discovering on
[8Bitdo SN30 Pro]# [CHG] Device 41:6E:21:D1:99:57 RSSI: 0xffffffc0 (-64)
[8Bitdo SN30 Pro]# [CHG] Device 41:6E:21:D1:99:57 ManufacturerData.Key: 0x004c (76)
[8Bitdo SN30 Pro]# [CHG] Device 41:6E:21:D1:99:57 ManufacturerData.Value:
[8Bitdo SN30 Pro]#   0c 0e 08 cd 60 e4 95 5f 73 d4 03 a6 e0 33 5e b1  ....`.._s....3^.
[8Bitdo SN30 Pro]#   10 06 4c 1d cd e6 3a 48                          ..L...:H
[8Bitdo SN30 Pro]# [CHG] Device 7F:BB:FA:37:9E:AC RSSI: 0xffffffc2 (-62)
[8Bitdo SN30 Pro]# [CHG] Device 7F:BB:FA:37:9E:AC ManufacturerData.Key: 0x004c (76)
[8Bitdo SN30 Pro]# [CHG] Device 7F:BB:FA:37:9E:AC ManufacturerData.Value:
[8Bitdo SN30 Pro]#   0c 0e 08 cd 60 e4 95 5f 73 d4 03 a6 e0 33 5e b1  ....`.._s....3^.
[8Bitdo SN30 Pro]#   10 06 4c 1d cd e6 3a 48                          ..L...:H
[8Bitdo SN30 Pro]# [CHG] Device 6B:9D:3D:CA:DB:8D RSSI: 0xffffffb1 (-79)
[8Bitdo SN30 Pro]# hci0 E4:17:D8:1C:F4:79 type BR/EDR disconnected with reason 2
[8Bitdo SN30 Pro]# [CHG] Device E4:17:D8:1C:F4:79 ServicesResolved: no
[CHG] Device E4:17:D8:1C:F4:79 Connected: no

olind commented 1 month ago

Also, rebooted again and tried

bluetoothctl
scan on

start controller with just start

Gives

[bluetooth]# hci0 type 7 discovering off
[bluetooth]# hci0 E4:17:D8:1C:F4:79 type BR/EDR connected eir_len 22
[CHG] Device E4:17:D8:1C:F4:79 Connected: yes
[8Bitdo SN30 Pro]# hci0 E4:17:D8:1C:F4:79 type BR/EDR disconnected with reason 2
[CHG] Device E4:17:D8:1C:F4:79 Connected: no

olind commented 1 month ago

When I look in the GUI I can see the controller under Forget a bluetooth device (But it doesnt work).

anonymouz commented 1 month ago

[8Bitdo SN30 Pro]# hci0 E4:17:D8:1C:F4:79 type BR/EDR disconnected with reason 2

Everything up to the line above is what I see, but the "disconnected" after pairing is a problem.

When I look in the GUI I can see the controller under Forget a bluetooth device (But it doesnt work).

Weird, this works fine for me.

But I have a question; @Jarthianur mentioned a difference in behavior between a x86 and ARM platform. On his x86 platform the pairing works but on ARM the pairing fails. I agree with his suggestion that it could be a bluez+ARM compatibility problem.

So @olind; what platform are you using!?
And if it is ARM, is there a possibility to test it on x86?

@Jarthianur; I think you are on to something (bluez+ARM incompatibility); I'm on x86 and it also works for me.

olind commented 1 month ago

@anonymouz I'm using a Raspberry Pi 3b+ with the raspberry image from batocera. Does that answer your question?

Not really sure if I can try a X86 on that computer? Apart from that I only have a macbook air (m2).

anonymouz commented 1 month ago

@anonymouz I'm using a Raspberry Pi 3b+ with the raspberry image from batocera. Does that answer your question?

Not really sure if I can try a X86 on that computer? Apart from that I only have a macbook air (m2).

Yes, the observation of @Jarthianur seems to be correct. I also reported this on the bluez issue and there is someone who has also this problem on ARM and he will double check this on x86 and report back. I'll give feedback here if his check is done.

hugochinchilla commented 1 month ago

I'm having the same issue with ARM on a raspberri pi 3b

hugochinchilla commented 1 month ago

I have tested two controllers.

A PS5 DualSense controller that will shutdown as soon as it pairs, then if powered on it turns off again. A xbox one (first generation with bluettoth) never exits pairing mode even if batocera says it connected successfully.

I have tested both from the UI in auto mode, manual mode and manual mode from the cli.

Both controllers worked fine on the same hardware with latest release from recalbox and work fin in Arch linux on my main desktop.

Edited

I just tried disabling internal bluetooth adapter and using an external one over USB with the same results.

claudiomet commented 1 month ago

Same problem here in v40. Machine: Dell Optiplex 3060. Two different 8bitdo SN30 Pro+ controllers are impossible to detect and pair. Controllers with last firmware, and turned on in X-Input mode. To discard internal Bluetooth device problem, I boot the machine with a Linux Mint Live CD, Bluetooth works OK, and controllers are paired with no problems. Same controllers paired succesfully in Switch console and other Windows machines, both tested and working OK. Discarded Bluetooth Dell machine malfunction, discarded controllers problems. Next step was disabling internal Bluetooth in BIOS and use two different supported Bluetooth dongles, with same results.

Viewing Batocera dmesg output, the only curious messages are:

[    8.058272] pcieport 0000:00:1c.7: AER: Multiple Correctable error message received from 0000:00:1c.7
[    8.058303] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[    8.058306] pcieport 0000:00:1c.7:   device [8086:a33f] error status/mask=00000001/00002000
[    8.058309] pcieport 0000:00:1c.7:    [ 0] RxErr                  (First)

Making a "lspci -s 0000:00:1c.7", the output is: 00:1c.7 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #8 (rev f0) This device kernel support in Batocera would be the problem?

olind commented 1 month ago

Same problem here in v40. Machine: Dell Optiplex 3060. Two different 8bitdo SN30 Pro+ controllers are impossible to detect and pair. Controllers with last firmware, and turned on in X-Input mode. To discard internal Bluetooth device problem, I boot the machine with a Linux Mint Live CD, Bluetooth works OK, and controllers are paired with no problems. Same controllers paired succesfully in Switch console and other Windows machines, both tested and working OK. Discarded Bluetooth Dell machine malfunction, discarded controllers problems. Next step was disabling internal Bluetooth in BIOS and use two different supported Bluetooth dongles, with same results.

Viewing Batocera dmesg output, the only curious messages are:
[    8.058272] pcieport 0000:00:1c.7: AER: Multiple Correctable error message received from 0000:00:1c.7
[    8.058303] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[    8.058306] pcieport 0000:00:1c.7:   device [8086:a33f] error status/mask=00000001/00002000
[    8.058309] pcieport 0000:00:1c.7:    [ 0] RxErr                  (First)
Making a "lspci -s 0000:00:1c.7", the output is: 00:1c.7 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #8 (rev f0) This device kernel support in Batocera would be the problem?

Does it work for you with one controller? Or is the problem when you pair two?

If so - your issue might be more like this https://github.com/batocera-linux/batocera.linux/issues/11844 ?

anonymouz commented 1 month ago

@hugochinchilla

Both controllers worked fine on the same hardware with latest release from recalbox and work fin in Arch linux on my main desktop.

So it failed on ARM (pi 3b). Recalbox on the PI 3b worked. And on your x86 it worked. Correct?

Others also reported that Batocera 39 worked... So if your recallbox on PI uses older bluez driver (as in Batocera 39) then the new bluez drivers don't auto connect on all platforms and don't even manually connect on ARM. Correct?

anonymouz commented 1 month ago

@claudiomet

Same problem here in v40. Machine

Did you also try the manual connect or only from the GUI? See: https://wiki.batocera.org/bluetooth_controllers_-_manual_setup

hugochinchilla commented 1 month ago

on your x86 it worked. Correct?

Others also reported that Batocera 39 worked... So if your recallbox on PI uses older bluez driver (as in Batocera 39) then the new bluez drivers don't auto connect on all platforms and don't even manually connect on ARM.

That's correct

i5rael-lp commented 1 month ago

Hello! I have the same problem with RPi3 + Batocera v40 + 8bitdo NES 30 Pro (x2). Everything was fine at v39, then I upgraded to v40 and the pads didn't pair. Tried multiple ways to solve this, but nothing. I had to downgrade to v39 (batocera-upgrade https://mirrors.o2switch.fr/batocera/rpi3/stable/39/) and after the reboot, both controllers paired inmediatly, without doin' nothing. Also, all my saves and configs are there (@olind)

I hope this gets a patch or something, but for now, I'll stick with v39.

olind commented 1 month ago

I had to downgrade to v39 (batocera-upgrade https://mirrors.o2switch.fr/batocera/rpi3/stable/39/) and after the reboot, both controllers paired inmediatly,

Thanks! Did you just run the command @i5rael-lp

batocera-upgrade https://mirrors.o2switch.fr/batocera/rpi3/stable/39/

?

i5rael-lp commented 1 month ago

I had to downgrade to v39 (batocera-upgrade https://mirrors.o2switch.fr/batocera/rpi3/stable/39/) and after the reboot, both controllers paired inmediatly,

Thanks! Did you just run the command @i5rael-lp

batocera-upgrade https://mirrors.o2switch.fr/batocera/rpi3/stable/39/

?

Yes, that very one (i have a rp3, if you got something different, you should change the url). It took a couple of minutes, and after rebooting, all was perfect.

Here's the wiki https://wiki.batocera.org/upgrade_manually

olind commented 1 month ago

Thanks @i5rael-lp I have the 3b+ so I guess we can use the same URL?

i5rael-lp commented 1 month ago

Thanks @i5rael-lp I have the 3b+ so I guess we can use the same URL?

Yes! The wiki says: Raspberry Pi 3 and variants.

sanomi78 commented 1 month ago

I had exactly the same issue with Batocera 40, but with an 8bitdo Ultimate BT. The bluetooth wouldn't connect at all and the 2.4ghz would connect and disconnect a few times before it stopped working.

Downgrading to 39 solved the issues on BT. 2.4ghz still doesn't work (but it's not as important tbh).

I'm on a Rasperry Pi 3b+

olind commented 1 month ago

Even I have successfully downgraded and all my 3 (2 x sn30 pro + 1 x lite2) works fine again. I had to connect-trust-pair them via bluetoothctl but that's ok for now.

claudiomet commented 1 month ago

@claudiomet

Same problem here in v40. Machine

Did you also try the manual connect or only from the GUI? See: https://wiki.batocera.org/bluetooth_controllers_-_manual_setup

via command line, the gamepads are not displayed in detected devices (I can see speakers, phones, and other devices, but gamepads are not displayed)

claudiomet commented 1 month ago

Same problem here in v40. Machine: Dell Optiplex 3060. Two different 8bitdo SN30 Pro+ controllers are impossible to detect and pair. Controllers with last firmware, and turned on in X-Input mode. To discard internal Bluetooth device problem, I boot the machine with a Linux Mint Live CD, Bluetooth works OK, and controllers are paired with no problems. Same controllers paired succesfully in Switch console and other Windows machines, both tested and working OK. Discarded Bluetooth Dell machine malfunction, discarded controllers problems. Next step was disabling internal Bluetooth in BIOS and use two different supported Bluetooth dongles, with same results. Viewing Batocera dmesg output, the only curious messages are:
[    8.058272] pcieport 0000:00:1c.7: AER: Multiple Correctable error message received from 0000:00:1c.7
[    8.058303] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[    8.058306] pcieport 0000:00:1c.7:   device [8086:a33f] error status/mask=00000001/00002000
[    8.058309] pcieport 0000:00:1c.7:    [ 0] RxErr                  (First)
Making a "lspci -s 0000:00:1c.7", the output is: 00:1c.7 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #8 (rev f0) This device kernel support in Batocera would be the problem?
Does it work for you with one controller? Or is the problem when you pair two?

If so - your issue might be more like this #11844 ?

with both controllers, no matter which one I choose to pair.

protocultor commented 1 month ago

Wanted to mention that I had the exact same problem with a Nintendo Switch Pro Controller on a RPi3B+ with v40, tried all the mentioned tips, and the only solution was also to downgrade to v39. To add something that "might" be interesting, also have an Arch Linux ARM installation (thanks to PINN), and there bluez works just fine, pairing and connecting the Pro controller at first try. Current version is 5.78-1.

Whoops-all-chaingunners commented 3 weeks ago

Sn30 Pro using the 8 bit do Wireless Dongle connects but has frequent drops and disconnects on RPI 3b on v40 fresh install. This issue also occurs on my Odroid go Ultra v 40. Can only reproduce it with Batocera.

dmanlfc commented 2 weeks ago

please try v41 with the RPi3b - https://drive.google.com/drive/folders/1pGcMDtlpQfWQE1eZnz6xKrAHMOz-BUjg?usp=drive_link i have working bluetooth with all my controllers.

i5rael-lp commented 2 weeks ago

please try v41 with the RPi3b - https://drive.google.com/drive/folders/1pGcMDtlpQfWQE1eZnz6xKrAHMOz-BUjg?usp=drive_link i have working bluetooth with all my controllers.

While it works with 8bitdo, it doesn't recognize the reset/power buttons of my retroflag NESPi Case+. Had to downgrade again to v39. :(

olind commented 2 weeks ago

please try v41 with the RPi3b - https://drive.google.com/drive/folders/1pGcMDtlpQfWQE1eZnz6xKrAHMOz-BUjg?usp=drive_link i have working bluetooth with all my controllers.

Thanks!

I tried to make a copy of my SD-card with MacOS Diskutil and tried to restore it to a new SD-card. I couldnt get it to boot. Any idea for how I can try the upgrade on another disk?

dmanlfc commented 2 weeks ago

please try v41 with the RPi3b - https://drive.google.com/drive/folders/1pGcMDtlpQfWQE1eZnz6xKrAHMOz-BUjg?usp=drive_link i have working bluetooth with all my controllers.

While it works with 8bitdo, it doesn't recognize the reset/power buttons of my retroflag NESPi Case+. Had to downgrade again to v39. :(

No worries. GPIO scripts are on the to-do.

dmanlfc commented 2 weeks ago

please try v41 with the RPi3b - https://drive.google.com/drive/folders/1pGcMDtlpQfWQE1eZnz6xKrAHMOz-BUjg?usp=drive_link i have working bluetooth with all my controllers.

Thanks!

I tried to make a copy of my SD-card with MacOS Diskutil and tried to restore it to a new SD-card. I couldnt get it to boot. Any idea for how I can try the upgrade on another disk?

You will need the full image. I will post it when back home.

dmanlfc commented 2 weeks ago

@olind the full image is there now

olind commented 2 weeks ago

@olind the full image is there now

I flashed the full image but it crashes during boot. First step with installation seems fine but when it boots the screen gets black after the Batocera boot splash is shown. Then the Raspberry (pi 3b+) green led starts blinking.

Any idea what to try?

batocera-linux / batocera.linux