Kodi Community Forum

Hey Guys,
Since I've upgraded to kodi 17, my controllers arent detected as joysticks anymore but instead detected as keyboard or at least thas what I think.
When inspecting the debug logs i found the following entries

Some of my buttons have the same functionality for instance A Left stick and Right stick all act like Select
While both X and B act as back.
The shoulder buttons act as pageup and pagedown.

Is there a way i can restore the functionality as it was in Kodi 16 where is detected as a joystick and I can configure my keymaping via joystick ids with buttons and hat ids instead of a crippled keyboard (emulation?)?

Some discoveries made today.

I have several usb controller attached to my shield which all also get detected as keyboard.
Now what I have noticed is that when I turn of my shield controller and turn it back on it suddenly gets detected as a joystick and so do the other controllers.
When removing any of the usb controller a simular event happens Kodi detects changes to controller and the controllers still connected switch to joystick mode.

I am having this same issue. I didn't see @Jo__ posted workaround while I was at home, but I will test it after work.

@Montellese was the main guy behind Android joystick support. My contribution was in Oct. 2016 to force joysticks to show up as keyboard if the Joystick Support add-on isn't present.

If the add-on *is* present, then joysticks shouldn't show up as keyboards, so there's some Android black magic that's going on. I've added this bug to my List of controller bugs for my v17.1 target

Thanks @garbear I will also verify if @Jo__ workaround of turning off and back on the controller while KODI is running works for me as well, since that "might" provide some hints to where the problem could be.
I am curious though, in the 16.* all the buttons resisted different scan codes. Why would that have stopped?

I seem to be experiencing a similar issue on Windows 7, Steam OS, and the Nvidia Shield.

In Windows 7 and Steam OS I have found that if controller goes to sleep or powers off it will loose the OS mappings. Then start acting very strange in the case of the Steam controller or PS4 Controller. If I power off the controller, then power the controller back on, it will eventually go back to the OS mappings, and work properly. But it seems random how may attempts it needs.
My hypothesis was that a controller pass though would resolve this issue. I recall it was possible to disable controller support in Isengard and Jarvis.

I think this is a Kodi 17.0 Krypton issue, and not only on one platform.

My original post on the my issue: http://forum.kodi.tv/showthread.php?tid=...pid2514888

Off topic, but PS4 Dual Shock (DS4) controllers work with the Shields Bluetooth now since the big update. (no root or extra apps required).
Just put in pairing mode and add device via settings

So after testing, I can confirm that turning on the controller while KODI already running allows full function of the controller.

@garbear thanks for looking into it, if any testing is required Ill be glad to help. Looking forward to 17.1 .

@garbear Yeah thanks for looking into it indeed... because everyone with a Shield has problems now, as Kodi is it's main player, and the controller is the only way of controlling it. Poor Nvidia, they just released their new shield and now it won't work for most people (and it's usually not the tech savvy people either, so I wonder how many questions about this will end up at Nvidia support )

So... when is 17.1 coming out?

https://www.reddit.com/r/kodi/comments/5...use_again/
https://www.reddit.com/r/kodi/comments/5...ield_2015/
https://www.reddit.com/r/kodi/comments/5...ypton_for/

(2017-02-03, 14:21)DeltaBlast Wrote: [ -> ]So... when is 17.1 coming out?

We do nightlies for Krypton builds. Tomorrow will be the first nightly based on 17.1 RC1, and that will include the fix for "stuck" analog sticks and triggers.

I'm travelling in a week and a half, so I'll try to fix the Shield bug by then, if not then it'll be late february when I'm able to look at it.

(2017-02-03, 14:21)DeltaBlast Wrote: [ -> ]@garbear Yeah thanks for looking into it indeed... because everyone with a Shield has problems now

Umm I use a Nvidia Shield TV, and have no problems with it. Admitedly I use FLIRC with mine, but it is just plain not true that Everyone is having problems with it

(2017-01-03, 18:49)Jo__ Wrote: [ -> ]Some discoveries made today.

I have several usb controller attached to my shield which all also get detected as keyboard.
Now what I have noticed is that when I turn of my shield controller and turn it back on it suddenly gets detected as a joystick and so do the other controllers.
When removing any of the usb controller a simular event happens Kodi detects changes to controller and the controllers still connected switch to joystick mode.

Thanks for this post! My shield updated kodi and I was just about to downgrade until I found this fix! Thanks again!

(2017-02-03, 20:18)garbear Wrote: [ -> ]

(2017-02-03, 14:21)DeltaBlast Wrote: [ -> ]So... when is 17.1 coming out?

We do nightlies for Krypton builds. Tomorrow will be the first nightly based on 17.1 RC1, and that will include the fix for "stuck" analog sticks and triggers.

I'm travelling in a week and a half, so I'll try to fix the Shield bug by then, if not then it'll be late february when I'm able to look at it.

Cheers!

Has the nightly that fixes this issue been fixed yet? Also, what version would I use for the 2017 shield?