riking/joycon

Not working on latest clone

Opened this issue · 12 comments

s5bug commented

Followed instructions in readme and joycon does not connect as an input device or controller (tested via http://html5gamepad.com/)

The lights keep going back and forth and not setting on a player number.

s5bug commented
s5bug commented

Switching to the develop branch also does not seem to work. I run sync, hold the sync button on my JoyCon, and nothing happens.

Is jcdriver running? Are you actually connecting to them via your system's Bluetooth settings? And are you pressing L + R on your JoyCons after jcdriver confirms your JoyCons have connected?

s5bug commented

jcdriver doesn't (as far as i'm aware) automatically connect your joycons to your computer. You need to manually enter your system's bluetooth settings, look for the joycons there while holding the sync button, and connect them to your system. You'll know jcdriver has detected your joycons if they start flashing a single light, instead of having the lights go up and down.

Yeah, the auto connection is the feature I was working on, it was broken, so the changes I made were to disable it on master.

Also confirm that you're running on Linux? I haven't written an OS X kernel driver yet, so it can't add a device on Mac.

s5bug commented
s5bug commented

I hold the sync button, pair through blueman-manager, and nothing happens in the console or with my joycon's player lights (even when pressing L+R). The joycon disconnects after a time.

s5bug commented

So, connecting it via the HID service connects it to the driver. I'll try connecting a second joycon.

Edit: Attempting to connect a second joycon via bluetooth results in dmesg spewing out
image

I am able to connect a single joycon at a time without issue however trying to connect a second errors. Both joycons work properly via the driver (as a single joycon).

Blueman spits out
image

@sorenbug that's probably a bug with your bluetooth card / driver then :( You'll probably need to buy a different BT radio.

s5bug commented

Which is weird, because using mfosse's driver for windows works fine. I think it's a bug with linux bluez that nobody has bothered to resolve/look into yet.