WIP Documentation for using Xbox One/Series Controllers

[oblivioncth]

This is extremely overkill vs being able to post a one liner solution in an existing (now closed) thread in which the relevant question was asked, but here we are...

However, before going through all the effort to create this page, I wanted to make sure it wouldn't be rejected outright.

Assuming the quality is up to your standards, I'd like to create a page that covers the specifics of connecting Xbox One/Series controllers, the different ways you can connect them, the quirks of each (e.g. ensuring your controller has BT at all, using the right driver depending on wired vs wireless, ensuring the firmware is updated for BT, etc.), along with a note that explains how to utilize the Home button as a standard input when using xpadneo which doesn't let you by default. More-or-less I'd expect it to mirror the layout of the PS4 controller page.

Then, either in this same PR or a separate one (up to you) I'd add a small note on the 8bitDo page, giving the user a heads up that if they are using the xpadneo driver on their Pi and have their controller in XInput mode they won't be able to use the "8BitDo"/Home button by default, and then link them to the section in this page that explains how to change that.

[cmitu]

@oblivioncth thank you for the intention. I like simple and to the point info, so I'd leave aside any quirks information, especially if it depends on upstream (e.g. xpadneo) docs.

If you'd like, you can start with an outline of your intended page and specify which info you'd expand to - just to check before doing an deep dive into it.

What I found is that too much information can confuse the users and if the page is long, some users might just stop reading it altogether.

Then, either in this same PR or a separate one (up to you) I'd add a small note on the 8bitDo page, giving the user a heads up that if they are using the xpadneo driver on their Pi and have their controller in XInput mode they won't be able to use the "8BitDo"/Home button by default, and then link them to the section in this page that explains how to change that.

That behavior may change in a future update of our module so I'm not sure if it's worth mentioning, perhaps pointing at xpadeneo's documentation is better. So the changes I have in mind right now:

• xpadneo would be included by default. It isn't now, because on some old kernels xpadneo required some Bluetooth parameters set (etrm..) which had a negative impact for some other controller models.
• we should automatically disable the 'shift mode' and make the Home/Guide button enabled by default, hence not requiring any setup by the users. I intend to do this sooner than later and I was waiting for the xpadneo's v0.10 to be released to include the new build method (v0.9.8 was also release on Christmas last year and will be the version for Buster).

[oblivioncth]

we should automatically disable the 'shift mode' and make the Home/Guide button enabled by default, hence not requiring any setup by the users. I intend to do this sooner than later and I was waiting for the xpadneo's v0.10 to be released to include the new build method (v0.9.8 was also release on Christmas last year and will be the version for Buster).

Lmao, my original goal, thwarted again. Honestly though I think this is for the best and I'm glad that you intend to make this change, I doubt most users know or want to make use of the feature anyway, an those who do will of course know how to turn it back on. In this case there's not much of a need to mention it.

What I found is that too much information can confuse the users and if the page is long, some users might just stop reading it altogether.

Fair, and I'm still willing to add this page. I'll try to make it as short and sweet as possible. If I feel uncertain of how you'd like the detail that is there, I'll stop before I get to that point and you can check the general layout as you suggested.

On a good day where I have a couple hours of free time I can probably bang this out in 1 or 2 steps.