Random controller disconnects about xow HOT 14 CLOSED

I'm currently trying to make xow behave as similar to the Windows driver as possible, while keeping the amount of configuration options low. Ideally, I'd like to expose the LEDs, the battery status and various other stuff via a D-Bus interface. That would allow you to write simple Python scripts to control xow's behavior.

from xow.

I also see a lot of disconnects and connects, and sometimes it ends with no controller are able to connect without a reboot of the PI4, maybe some services could be restart to make it work again, but for me it seems like the issue is only when having two controllers connected and playing at the same time. i couldn't reproduce it with both controller turned on and only using player 1

Both controllers are fully upgraded from PC, one is last gen Xbox One Elite, and the second is Xbox One S new model with BT support. but still i only use dongle as it was easier then BT

from xow.

@nkoester I'm not sure if I'll be able to help you, as these edge cases (and especially connectivity issues) are always hard for me to diagnose. The debug logs will be a good start, but a full USB packet capture might provide additional insights. I don't want to rule out the possibility of a connection to issue #57 either.

from xow.

yesterday i tried playing for 4 hours, and when only using one controller there is no issue. I started playing with two controllers, and after 10 min the first controller disconnected/reconnected, after that it worked fine for an hour. I also tried two different dongles. i will next try out some different controllers.

also i might look into doing a debug version, as i got some good information from issue #35 of other stuff to try out.

But see this Issue #35 looks very interesting and could be very similar to what i experience

from xow.

I have tested with the newest build. And could see it had a newer version then the previous. It seems good now. For many hours no disconnect. Will keep you posted

from xow.

I have tested with the newest build. And could see it had a newer version then the previous. It seems good now. For many hours no disconnect. Will keep you posted

Awesome! I made some changes to the wireless channels in the latest build to make it behave like the original Microsoft driver.

from xow.

@mooock Any news?
@nkoester Did you give the latest build a try?

from xow.

i have not had any disconnects after last time, it seems the thing you did with wifi channels fixed the problem.

from xow.

@mooock I've just pushed a change that should read the power values for the wireless channels from the dongle's internal memory (they are actually different for every dongle out there). I'd like to make sure that everything still works correctly without any disconnects, so I'd really appreciate if you could give this another try 😃.

from xow.

I also experimented with the latest version and can happily report that all scenarios I tested (1 - 4 controllers on a single stick) work flawlessly. No disconnects, no problems. Thanks so much!

PS. in some tests the controllers were simply out of battery, which I notice only after way too long. Maybe some form of indication could be implemented showing that the battery is empty? A LED flashing pattern every 5 minutes or so?

from xow.

I am happy that you had the time to look into this issue, most other forums has not been as helpful as you, and mostly you only see people ask questions then help out or do their own findings for troubleshooting.

I will say this version is on par with the windows experience.

from xow.

Thanks for the kind words, I'm very glad that it's working fine 😃.

Maybe some form of indication could be implemented showing that the battery is empty?

Yeah, I really want to implement a standardized solution for battery reporting rather than LED patterns, but the progress on that issue has unfortunately come to a halt.

from xow.

For me i have never cared about battery level, i have a good idea of when to change battery, and if they die on me, in the middle of action. i get a quick workout of running after new batteries.

from xow.

Unfortunately, my controllers do not seem to run out of battery at once but rather (for several days) miss inputs or do not hold a button when pressed continuously before finally turning off completely. I feel like missing inputs is really bad and any feedback to the users could avoid the issue of "did i miss to press the button? is the controller broken?"

I saw your efforts for a standardized solution and also the upstream problems.

One argument for an additional (infrequent) LED pattern would be a system setup not using the standard tools. A minimal setup without centralized power management would really benefit from any notification beyond OSD hints. I would not mind enabling this feature via a command line argument ;)

from xow.