On Wed, Nov 11, 2015 at 1:54 PM, CJ <[email protected]> wrote: > At one point the 360 controller seemed to randomly connect to the dongle. > Input would appear in /dev/input/js0 and with games. Now, however, the only > way to ensure communication between the dongle and the controller is to > reboot with the dongle plugged into the USB and then power on the > controller. This seems to work every time. Without this procedure, the > controller's LED blinks a few and then powers off. > > Also, even when connected properly the controller will disconnect and > reconnect within a few seconds. This happens not very often and in what > seems a random way. > > My hope is that there is some obvious, simple processes which I'm oblivious > to but an experienced user can inform me about so that I do not need to > reboot to use the controller.
That doesn't sound like an obvious error. You can check the output of `dmesg` for errors, sometimes a USB device can be a little dodgy and that should show up in there. Loose connection with the battery or empty batteries would be another guess. But generally speaking the driver isn't really concerned with syncing the controller to the dongle, that is all happening in hardware and should "just work". There is a known issue where a controller might shutdown and stop sending events, which can be fixed by unplugging the battery. But that issue should be limited to long periods of inactivity and never happen while the controller is actually in use. Does the controller work in Windows or when using the default xpad kernel driver? -- Blog: http://grumbel.blogspot.com/ JabberID: xmpp:[email protected] ICQ: 59461927 -- You received this message because you are subscribed to the Google Groups "xboxdrv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/xboxdrv. For more options, visit https://groups.google.com/d/optout.
