Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bluez integration ? #3

Closed
Roughtrade opened this issue May 11, 2016 · 7 comments
Closed

bluez integration ? #3

Roughtrade opened this issue May 11, 2016 · 7 comments

Comments

@Roughtrade
Copy link

I would try to connect a Bluetooth gamepad ( FC30 Pro from 8bitdo )
Do you have any Idea ? I have installed your great Extension to my Openelec. It is possible to pair the controller with openelec. But if i start a snes game with advanced launcher i can not controll the game.

Regards Peter

@bite-your-idols
Copy link
Owner

I can't tell you for sure because I don't have that gamepad. Over bluetooth I can pair a sixaxis controller in openelec and when I start an emulator it works flawlesly...
Please check if in openelec it is paired right, then when starting emulator a yellow text must display in botton left corner with the name of the controller.

Also, can be that controller plugged with a USB cable? just to check if the controller is compatible with retroarch or it is a bluetooth issue.

@Roughtrade
Copy link
Author

Roughtrade commented May 11, 2016

i have paired the controller in openelec. There is a blue indicator led on the controller and the light is permanent when it is paired. i can see it also wenn i go to tv guide it schows the Controller as a mouse.

Wenn i connect the controller via USB it works perfect with retroarch and the yellow text shows the controller with the right name.

Connected over bluetooth the controller is not recodniced

in /dev/input/ i see also js0

for testing i have installed retropie native on a other PI2 and testet the controller with this howto

https://www.youtube.com/watch?v=EiDJFdWXweI here it works

@bite-your-idols
Copy link
Owner

OK. I think it is related with name assigned by default by retroarch to your gamepad. For example sixaxis is called "PLAYSTATION(R)3 Controller" when connected over bluetooth, but when connected with USB it calls it "Sony PLAYSTATION(R)3 Controller".

The exact name is how it must be named the config file, located in /storage/emulators/retroarch/configs/joypads.

When starting retroarch with gamepad connected over bluetooth also some yellow text must display in bottom left corner, saying that a not-configured-gampad is connected in port 0, doesn't it?

One tricky method I did once was to start emulator with another gamepad connecetd (or maybe with 8bitdo's with USB), then enter retroarch menu, go to input configurations for player 2, connect the bluetooth gamepad and save a custom config file. After then, open that file and try to edit default config file (the one in /storage/emulators/retroarch/configs/joypads/name_of_your_gamepad.cfg) with correct values for input_driver, input_device, input_vendor_id, and input_product_id.

Tell me if you discover something new.

@Roughtrade
Copy link
Author

Sorry there is no yellow text when the Controller is paired over openelec :(

@bite-your-idols
Copy link
Owner

I am sorry, I can be something related with OE's bluetooth driver for your device...

Maybe looking for some issue like this in lakka (it uses OE in background)...
Try to update joyconfigs as they say in this issue: https://github.com/libretro/Lakka/issues/260

@Roughtrade
Copy link
Author

Roughtrade commented May 12, 2016

Sorry for my late response, but i had install a vm with windows to update the firmware of the controller. with the latest firmware it works very well.

your clue to rename the config file is the solution !!!

Thank you for your support.

Regards Peter

@bite-your-idols
Copy link
Owner

I am glad to hear that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants