-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
Fix reporting of "share" button (KEY_RECORD) #17
Conversation
Hmmmm... please hold the merge. I tried to do the same change on |
Tested on a 8BitPro Pro 2 Wired Controller for Xbox. The driver was not reporting button presses of the "share" button (below the big Xbox button). After confirming that the controller is detected as "Series XS" and analyzing packet dumps, I noticed that this controller reports the button in a different offset than this driver expects. Since the controller works in Windows with the stock, official Microsoft driver I am assuming that both offsets are being used in the wild to report the state of this button. Signed-off-by: Leonardo Brondani Schenkel <leonardo@schenkel.net>
a48e72d
to
84c8144
Compare
Fixed patch. I'm assuming that the previous offset is valid and used by the official controllers, and I'm adding the new offset used by the 8BitDo controller. I don't have an official controller to test; we should verify what official controllers send in that different offset (if it's always zero, or consistent with the other offset, then we're good). |
Hi. Any feedback on this? |
I can confirm that the official Microsoft controller I have reports the Share button in byte 22 (counting GIP_CMD_INPUT as byte 0) and the Hori Fighting Commander Octa reports the Share button in byte 18. |
Hi again. Is there anything else I could do to get this merged? |
Hi, sorry for the delay. I've investigated the share button handling of the Windows drive a while ago and it looks like the button byte is always at a constant offset from the end of the packet. Handling the share button in this way ensures that we don't have to fix the offset for every new device. I've made the required changes to the packet handling in the |
I compiled and tested the |
Closing this PR since the maintainer implemented a better approach. |
@medusalix : any plans for that branch to be merged? |
Yes, I'll probably merge it later today. |
Tested on a 8BitPro Pro 2 Wired Controller for Xbox. The driver was not
reporting button presses of the "share" button (below the big Xbox
button). After confirming that the controller is detected as "Series XS"
and analyzing packet dumps, I noticed that this controller reports the
button in a different offset than this driver expects.
Since the controller works in Windows with the stock, official Microsoft
driver I am assuming that both offsets are being used in the wild to
report the state of this button.
Signed-off-by:
Leonardo Brondani Schenkel <leonardo@schenkel.net>