-
Notifications
You must be signed in to change notification settings - Fork 100
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
Disconnects when exiting the grip order screen #39
Comments
Unfortunately, the issue you're experiencing is likely due to frequency problems I still haven't entirely solved yet. The Switch (as of SwitchOS v12 and onward) is far more sensitive to controller frequency when exiting the "Change Grip/Order" menu. NXBT attempts to keep a consistent frequency like a real controller, however, it can still vary a bit depending on external factors (OS scheduling, hardware, etc). At the moment, there are mitigations in place that work on some but not all hardware configurations. Firstly, would you be able to list the specifications of the system you're using NXBT on? Eg: OS/version, CPU, etc. Second, can you run |
Hey thanks for the help and sorry for the late reply. I just installed and tested on the latest version and its not working sadly. I'm currently running Ubuntu 21.10 x86_64 with an AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx (4) @ 2.500GHz. Here is the full neofetch
The output is
Although interestingly it didn't kill itself, and I manually had to ctrl + c it. |
Would you be able to explain what happened on the Switch while the |
Yep. The controller connected and and exited the grip menu, and then disconnected. |
It pairs successfully but the second I exit the grip order screen it instantly stops working. Using the pip version.
Here is the logs from the last check in bluetoothctl
Ubuntu 21.10
A not had to tell bluetoothctl to remove the switch for it to connect again.
Videos showing the issue
https://youtu.be/VUe2xvHM-So
https://youtu.be/P_nEkdsSc7w
Thanks
The text was updated successfully, but these errors were encountered: