@mitu said in Libretro and bluetooth problems:
Hm, I recall some reports about Xbox controllers taking long to initialize. Try using the xpadneo driver from - https://github.com/atar-axis/xpadneo, it might work better, but, given the age of your distro, I'm not sure how well it will behave with your kernel version.
These problems mainly occur w/ LibRetro games. When plying Mame (advmame) I sometimes have to manually kill joy2key.py so that a keypress on my controller does not result in Mame trying to load a game when pressing "up".
joy2key - should stop itself, it's only used by runcommand. Are you using it for other purposes ?
Thank you for pointing me to the xpadneo (bluetooth) driver for my Xbox One S controller. It solves some probs not related to RetroArch. In the Libretro SNES emu I still experience a lot of slowdown, but the LR-Atari 2600 emu runs fine.
Lr-picodrive (Megadrive & Sega Master Sytem) appears to work fine. But I have to re-start my controller (on/off). Same thing for Lr-SNES: I can wait for 5 minutes to let the Pi / Libretro "find" my bluetooth controller or I can use the on/off button. "Yoshi's Island" won't run fine no matter what controller I use, ha ha (YI is a very hard game to run because of the extra chip it had in the cartridge).
[off topic] Still have that nasty problem that joy2key.py won't get killed after starting a game. This results in, for instance, the F10 keyboard key getting pressed by my controller in Mame4all. The F10 key makes Mame throttle to "ridiculous speed", just like the spaceships in "Spaceballs The Movie".