i use an external bluetooth dongle, with 2 wii u pro controller.
Not a single issue, zero lag in the input.
My best controller so far 🙂

I think we are speaking about two different things. There is a problem with joystick/analog stick calibration/deadzone in general with recalbox.
At the moment I am able to drive 'assetto corsa' on PC with my xbox360 pad quite well (steering help etc. turned off of course).
In Recalbox I am not even able to play Mariokart 64 mit analog stick since the deadzone/calibration issue.

I solved used Sixasis Pairing tool from Windows, i forced my "problematic" Shanwan to connect to Raspberry BT address.
Now i have the problem that all 2 shanwan copies are detected as "Playstation 3 original" , but i selected Shanwan drivers from configuration and i read that supports "original and shanwan" , so at the moment i cannot see any issue with this.

Recalbox is free and support is not expected to be given quickly, i just ask if somebody can shed light about where BT pairing informations are stored, why Shanwan copies are detected as Ps3 original and so on.

In the FAQ, in the tutorial we can add Sixasis Pairing tool way for problematic controller, i can give my availability to improve the community experience.

I also had other issues with Ps3 ORIGINAL pad (that now i use only with Android phone), this device often pressed buttons, never really pressed! Led often stay OFF, but pad was working (with ghost pressing issue).
I thought was a problem with pad, but with Android works like a charm, maybe if reoccurs with Shanwan units i should open another thread.

@Substring worked for me too, thank !

@kollech87 I don't understand why you're now speaking about your Xbox controller. So what is your setup exactly ?

I have the same N64 issue with 17.12.02 using the Pi3 (no overclock) and the internal Bluetooth controller.

FYI, it took me a while to get my SZMY-POWER clone controllers to work.

I had the driver initially set to Official and they would pair, but no buttons would work. So reset the controllers and cleared the Bluetooth controllers from Recalbox. I then tried the Bluez driver and again they would pair, but no buttons world work. I then changed the driver back to Official, rebooted my Pi3, turned the controller on, it connected, but no buttons working again. I then connected the controller(s) via usb again, waited 20 seconds, disconnected (like I was pairing them again, but I had not reset them or cleared the Bluetooth controllers from Recalbox) and they are now working over Bluetooth (with a little bit of lag, but still playable ).

For piece of mind, I created a new SD Card with clean Recalbox 17.12.02, and went through the process again. Same issue. Official would not work initially, neither would any of the other drivers. I had to set to Bluez, pair via usb, change to official, pair again and everything works.

@neo-1986 cool now have fun 🙂 Thanks for your feed back!

@substring Well I took your advice and got a new SD card. I used Paragon to pull all the roms off the old sd. (because of linux I couldn't see the partitions with windows that held them) Did the flash of the newest recalbox and every controller works as mapped that I try. In the process of doing this I now know exactly how to build and work on my own. Thank you again for the help.

@substring IT WORKS!!! and for the 4 joys!! thanks you a lot man! you are the prince of the forum, metod of pair now is diferent, it was changed a little jejeje, im using the official drivers, bluez not work.

@substring problem solved 🙂 after a reboot I just had to hold down the "home + x" buttons. classical user error 🙂 but, thank you for your helpfulness 🙂

I used this tutorial : https://github.com/recalbox/recalbox-os/wiki/Test-your-joystick-with-jstest-(EN)

My gamepad seems to work properly with jstest.

@oyyodams yes indeed but the one I got came with the new switch support packaging and last firmware from factory, so it seems very recent, maybe there's a new BT chip or something new hardware wise that triggers that PIN code request, well anyway it's "fixed" but new owners may come across this issue too.

@steve1977 give a try to https://forum.recalbox.com/post/84335