@akafox thanks so much!

Facing the same issue with "select" not working. Don't know what "drastic" is, so cannot comment on this.

There seems to be a "fix", but I am not sure whether this is part of 4.3 yet? Anyone has a more recent image and can try? Are their nightly or weekly builds for Retropie?

https://github.com/RetroPie/SDL-mirror/pull/4

I had no trouble to connect both x-Box one s controller via Bluetooth (pi 3b - disable ertm and updated retropie and the both controllers via my Xbox one). I conectet the first one and after it was done I connected the other one. But I have trouble to configure them in the retroarch GUI. Does the controllers work in retroarch gui for you?

The GamepadBlock provides a hardware interface for original Amiga, C64 and other home computer controllers. It would be a wired solution, though.

@mitu Ah. Right.
Four official DS4s; all first-generation versions of the white, black, red, and blue colors.
They map / work in ES just fine. RA does something, so that when any DS4 controller is connected, it isn't able to control the emulation, including the keyboard (Escape, Control-C, and the like do not work at this point). I am only able to shut down via unplug.
Again, other controllers like Xbox works out of the box. Only minor re-binding is necessary under RA when I choose between Bluetooth and wired (i.e. Guide button is #10 wired, #16 BT).

@jonceramic said in Disconnected bluetooth controller causes freezes on regular intervals:

I'm assuming possible that the controller needs to be on when the system is booted under this setup so it can be discovered immediately

That's not necessary, if the pairing is ok, you can turn your controller on/off anytime. You didn't give any details about your system/controller, so it's hard to say if it's the same problem or not.
FWIW I have a 8bitdo SN30 controller that doesn't have any problems. It was updated to the latest firmware version available and I didn't have to fiddle with any bluetooth settings on the PI, it even goes into stand-by then reconnects back on a button press.

@exonerated I have that the majority of the times I have my PS3 controller plugged in via USB. It stays stuck in a never ending black screen restart loop - both at startup and on exit.

If it's the same thing, I find that unplugging it usually helps.

For anyone who thinks they have an “official” controller and it doesnt work you probably have a bootleg controller. Black is the only color i personally have seen the bootlegs in but i have seen hundreds of them.

yes, I've posted to DFRobot Bluno Bee forum. Hopefully, there'll be a reply soon.

There's a suspicion on the Raspberry PI forum that BLE devices are not supported in Raspbian. Interesting ...

Anyway, if anyone has a BLE device or gamepad working in RetroPI, that'll help a lot!

cytan

@mitu 1) thank you for responding. 2) I typed in the commands and ran the test. Pressed every button, and all categories said "off" for each button. Not sure what to do next I rebooted. Ran the bluetooth again, configured wii u pro again, and the buttons seem to all work. Going to try adding roms next to make sure.

I have no clue why this just worked all of a sudden, but thanks for the education about the jesse test.

@salvaliebana install joystick selection. Go into retropie menu. If you see joystick selection then it is already installed and go to paragraph 2. If it is not read paragraph 1.

In the retropie menu, go into runcommand. In there install joystick selection. Exit. Restart your pi.

Go into retropie menu, then into joystick selection. In option number 1 you can select which joystick is each player.

Hi there,

I just bought 2 of them.And.........
they are working great, after changeing the driver in the options.

Thanks it was just a bug all is OK thanks again.

@ckswenson Third Party images with custom configs and pre-loaded ROMs are not supported here. Go ask Mr .Death for tech support.

Replying to this old topic with the solution that worked for me, after finding this question via google with no reply.

It's likely your left/right triggers were configured incorrectly. If they're configured for minus axis, retroarch believes they are held down when the game launches and everything acts weird. It's likely the retroarch menus are un-navigable as well.

To fix the problem, go to "configure input" again and make sure left trigger is "Axis 5+" and right trigger is "Axis 4+". If they're negative the emulator thinks they're held down and that's causing the problems.

Hope this helps anyone else coming across this problem via google.