Welcome screen: no gamepads detected

[rockaddicted]

Roms on USB ?

[pmroyo]

The roms are in the micro SD

[Substring]

Bluetooth is started after ES, so if it's your only pad, and it's not paired, you'll get the message from ES. And it's totally normal

[pmroyo]

@substring Yeah I know, but before updating to 4.1, I could start ES without a gamepad connected and after that, connect a usb gamepad, pair a bluetooth one....now, If I don´t have a paired bluetooth device, it doesn´t start. Is there anyway to avoid this screen appearing?
Thank you

[Substring]

@pmroyo have you ever removed some files that are not roms ? I think you're missing the inouts config file

[pmroyo]

@substring I don´t think so, but maybe i did it accidentally. How can I check this file?
Just a clarification, when I get the above screen, I connect the bluetooth device and get paired automatically, but of course I have to remap again all the buttons.

[MarcDK]

@pmroyo I have had the same problem with the XBOX 360 Pads. This is not related to bluetooth only. And yes, I had to reconfigure the controller again everytime I started recalbox.

[rockaddicted]

@marcdk I'm using x360 wireless controllers, I'm flashing about 10x by week recalbox on each board, and I never had this kind of problem.
I can't reproduce it

[pmroyo]

@rockaddicted have you tried switching on your raspberry PI without switching on your gamepad? or do you switch on the gamepad before starting emulation station?

[Substring]

@pmroyo can you SSH ls -l ~/.emulationstation/es_input.cfg and tell me if there is an output and eventually give it ?

[pmroyo]

@substring Please find the attached screenshot, I executed the command you told me in winscp:

And I have also checked the file and is full of controls, including the one that I have:

But if I connect the gamepad after ES has started, I have to map it again

[Substring]

@pmroyo fine it does exist
what about ls -l /dev/input ?

[pmroyo]

@substring Currently I don´t have any gamepad connected:

[Substring]

@pmroyo now that's some unexpected behaviour ...

[rockaddicted]

@pmroyo please do ls -l /dev/input with gamepad connected.

[pmroyo]

This is a screenshot with the gamepad already connected:

[pmroyo]

@rockaddicted any other thing I can check?

[poulain26100]

@pmroyo

Hello have the same problem.
Have you find a reponse?
Thanks

[paradadf]

@poulain26100 i had that problem once and resolved it just by doing a new clean installation.

[pmroyo]

@poulain26100 It was solved automatically in one of the last updates. Now I can switch on recalbox and then connect the bluetooth gamepad without any problem