Skip to content
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

Xiaomi gamepad stop working after a few minutes #11

Closed
FFrelay opened this issue Mar 31, 2019 · 6 comments
Closed

Xiaomi gamepad stop working after a few minutes #11

FFrelay opened this issue Mar 31, 2019 · 6 comments

Comments

@FFrelay
Copy link

FFrelay commented Mar 31, 2019

Not sure it's a Windows 10 (1809) or USB dongle issue (I changed to a Intel 9260) or gamepad itself. The problem is the gamepad works fine at first, but after a few minutes it stop working. The mi button led on the gamepad is still on, the gamepad was not disconnected from the PC, all I need to do is go to Windows Setting > Bluetooth and other devices then magically it works again, then keep stop working a few minutes after that. I must keep switching from game window to "Bluetooth and other devices" window in order to "refesh" it. Please advise, thanks!

@FFrelay
Copy link
Author

FFrelay commented Mar 31, 2019

Found similar issue has been discussed here: irungentoo/Xiaomi_gamepad#47

@sfOoca
Copy link

sfOoca commented Apr 12, 2019

Same issue systematicaly after a cinematic on assassin's Creed 3 for example

@dancol90
Copy link
Owner

Hi! This seems a Windows 10 issue, maybe related to bluetooth stack. Unfortunately, I've never experienced it yet.

Have you tried with the compatibility mode as suggested in the linked issue?

@FFrelay
Copy link
Author

FFrelay commented Apr 20, 2019

Hi, thank for your reply, I did try that suggestion but it did not work.

@sfOoca
Copy link

sfOoca commented Apr 20, 2019

I try too, but it doesn't change anything.
It's ok with others apps (but a lot more complicated)

@FFrelay
Copy link
Author

FFrelay commented Jun 17, 2019

Windows 1903 build 18362.175 seems to fix this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants