Solved Ipega doen'ts recognize as controller, it detects no controller

[A Former User]

@paradadf yeah, i did, now it shows just the mac, not "ipega bluetooth controller", but still does not detect in gamepad mode.

[paradadf]

please, pair the controller and unplug/unpair any other device if possible and follow the instructions given here:
https://github.com/recalbox/recalbox-os/wiki/Recalbox-support-(EN)
Share your support files here.
Pair it in the controller mode and don't bother with any other one.
Use 4.1 for this.

[A Former User]

@paradadf here's the file:
http://www.mediafire.com/file/8ocv6wxuyxsydxd/recalbox-support-20170422182254.tar.gz

[Substring]

how can we help if you don't even mention your recalbox version ?

[A Former User]

@leotrix14 said in Ipega doen'ts recognize as controller, it detects no controller:

@paradadf I already searched on the forum and that didn't helped me, then i opened the topic.
And now i already flashed recalbox 4.1, and when i enter to search a bluetooth controller it keeps saying "No controllers found" With, and without the bluetooth adapter usb.

@Substring said in Ipega doen'ts recognize as controller, it detects no controller:

@leotrix14 how can we help if you don't even mention your recalbox version ?

I mencioned up there that i was using the last stable, then i flashed the 4.1 version because paradadf said it was going to work right out the box. The exactly version is the Build 11603325

[paradadf]

somehow everytime a user says he/she has an ipega 9025, the internal controller name is different... Try this:

Execute the following three commands (one after another):

mount -o remount, rw /
echo 'SUBSYSTEM=="input", ATTRS{name}=="ipega media gamepad controller", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"' >> /etc/udev/rules.d/99-joysticks-exotics.rules
reboot && logout

Just for the record, it is needed to edit recalbox.conf so it reads (change auto for sdl2

## Set retroarch input driver (auto, udev, sdl2)
## If you don't have issues with your controllers, let auto
global.inputdriver=sdl2

reboot and try again.

If this rule works, comment it here so we can add it by default. Again... this only works on 4.1 upwards.

Don't do this part yet: I'm not sure anymore, but if your controller (assuming you really paired it in the right "controller" mode) is detected as a keyboard, you might need to add the following rule to the usbhid.conf:

# IPEGA
options usbhid quirks=0x1949:0x402:0x040

[Substring]

the pad doesn't even get listed in /dev/input ... so there is sthg wrong on the OS side. BT or kernel

[A Former User]

@paradadf D**n, that made it work!!!!! just followed these commands straight on recalbox F4 console and then the magic happened, after pairing it started recognize as a gamepad controller! hope this topic help someone else too!

And a simple question, you guys call 4.1 as "Instable", whats the problem with it? tried with a few games and its looks normald and fluid to me.
And thanks again!
Regards from Brazil!

[Neil_Hines]

It is a really great topic and you guys give the great suggestion. I will try what you guys say hope it will also work for me.

[Substring]

you see what is working, i see that there are many bugs left It will be marked stable when it does run as expected AND the upgrading process from 4.0.x to 4.1 is safe, we can't miss that.