Sometimes during games that have significant downtime (lobby waits, briefings, etc) I leave the 360 controller alone for long enough that it disconnects. If I attempt to immediately reconnect by turning the controller back on with the center (Guide?) button, the controller's lights indicate that it has reconnected, but the computer won't register any inputs from it.
Is there a recommended way to reconnect after the idle timeout?
Things I've tried already:
Disconnecting and reconnecting the receiver from the computer allows the controller to connect, though it often reconnects as player 2, then 3, then 4...then 1 again, and that seems to matter for how the computer enumerates it. Once it's back to player 1, all my software except for Teamspeak will recognize it as the same controller. The push-to-talk in Teamspeak has to be rebound.
Waiting for "a long time" (i.e. putting the controller down after a play session and then using it the next session) allows it to reconnect normally (i.e. I don't need to rebind anything, and it reconnects as player 1) so it seems like there's a second idle timer in play, but I don't know how long it is.