#8BITDO M30 RETROARCH BLUETOOTH#
Not only the startup gets slower, but loading thumbnail images (inside playlists) also gets slower/delayed while my 8BitDo Bluetooth controller is connected in X-input mode (turn on the controller by holding X+Start). And that path takes about 10 seconds to return any data, which means at least 40 extra seconds waiting for retroarch to load. Using strace -f -o strace.log retroarch, I can see retroarch opening that path about four times during startup. I'm using Raspberry Pi 4 running Gentoo arm64. Openat(AT_FDCWD, "/run/udev/data/+power_supply:hid-e4:17:d8:d8:f9:80-battery", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) I'm not having much luck rebuilding to stop accessing that, but I'm getting very good at making retroarch segfault when I change something I shouldn't have.Īccess("/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:045E:02E0.001F/power_supply/hid-e4:17:d8:d8:f9:80-battery/uevent", F_OK) = 0 That'd account for double the time on the freeze in retroarch.ĮDIT2: I've verified during the hang, even with battery display disabled, it's opening /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:045E:02E0.001A/power_supply/hid-e4:17:d8:58:86:7f-battery/uevent and hanging on reading that. I'm going to downgrade mine later.ĮDIT: Seems both status and capacity are being checked, and both return no data for me.
#8BITDO M30 RETROARCH UPDATE#
As for the autoconfig, I just learned the hard way that the m30 in particular screws up the button layout if you update from 1.10 to 1.13 or 1.14. I'll see if I can replace the check with a spoof file and rebuild to verify. The reason it's taking so long is because it -doesn't- error. The error means it stopped waiting for a "no data" response. The errors going away isn't actually a good sign. Yeah, it's still running the check in the background.
0 kommentar(er)
