Bluetooth Gamepad is not working on android-native and windows

[RafaelOliveira]

I tested a bluetooth gamepad with html5, android-native and windows, and it's only working on html5. I found a issue with html5, the directional pad is showing strange values (analogs are ok). First, the d-pad is showing the same axis for horizontal and vertical (9). And second, the values are these for horizontal (similar to vertical):
left: 0.7142857313156128
middle: 1.2857143878936768
right: -0.4285714030265808

should be negative on left, near zero on middle, and positive on right.

[RobDangerous]

Is you gamepad working correctly at http://www.html5rocks.com/en/tutorials/doodles/gamepad/gamepad-tester/tester.html ?

[RafaelOliveira]

The values are the same on the d-pad, and the d-pad is acting as a extra axis. From the article they should act as buttons. Maybe a problem with the gamepad or Google Chrome isn't detecting correctly.

the api is implemented on android-native and windows?

[RafaelOliveira]

just for the record:
Windows - yes, but only XInput, no DirectInput yet. Android not yet.

[RobDangerous]

Implemented some Android gamepad code, can you test that?

[RafaelOliveira]

My computer is on repair, I will try when I have time.

[RafaelOliveira]

I updated the code to the latest Kha, and now I receiving this message in the logcat (in android-native) when using the axis:
mouse locked
Probably related to the latest changes in mouse locking.

About the buttons, 3 buttons are being identified as button 0, and the left bottom shoulder and right bottom sholder aren't being identified.

[jamiltron]

I have the same issue with mouse locking on OSX 10.11.2 with last night's version of Kha.