Open WilsontheWolf opened 2 years ago
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 sudo nxbt test
and post the output here?
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
.-/+oossssoo+/-. shorty@shorty-laptop
`:+ssssssssssssssssss+:` --------------------
-+ssssssssssssssssssyyssss+- OS: Ubuntu 21.10 x86_64
.ossssssssssssssssssdMMMNysssso. Host: HP Laptop
/ssssssssssshdmmNNmmyNMMMMhssssss/ Kernel: 5.13.0-21-generic
+ssssssssshmydMMMMMMMNddddyssssssss+ Uptime: 1 day, 22 hours, 11 mins
/sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Packages: 3497 (dpkg), 21 (snap)
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Shell: zsh 5.8
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ Resolution: 1366x768
ossyNMMMNyMMhsssssssssssssshmmmhssssssso DE: GNOME
ossyNMMMNyMMhsssssssssssssshmmmhssssssso WM: Mutter
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ WM Theme: Adwaita
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Theme: Yaru-dark [GTK2/3]
/sssssssshNMMMyhhyyyyhdNMMMNhssssssss/ Icons: Yaru [GTK2/3]
+sssssssssdmydMMMMMMMMddddyssssssss+ Terminal: tilix
/ssssssssssshdmNNNNmyNMMMMhssssss/ CPU: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx (4) @ 2.500GHz
.ossssssssssssssssssdMMMNysssso. GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series
-+sssssssssssssssssyyyssss+- Memory: 5793MiB / 6848MiB
`:+ssssssssssssssssss+:` Disk (/): 410G / 435G (99%)
.-/+oossssoo+/-. Battery1: 100% [Full]
Local IP: 10.0.0.54
The output is
[1] Attempting to initialize NXBT...
Successfully initialized NXBT.
[2] Checking for Bluetooth adapter availability...
1 Bluetooth adapter(s) available.
Adapters: ['/org/bluez/hci0']
[3] Please turn on your Switch and navigate to the 'Change Grip/Order menu.'
Press Enter to continue...
Creating a controller with the first Bluetooth adapter...
Successfully created a controller.
[4] Waiting for controller to connect with the Switch...
Connection timeout is 120 seconds for this test script.
Successfully connected.
[5] Attempting to exit the 'Change Grip/Order Menu'...
Controller disconnected after leaving the menu.
Exiting...
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 test
command was running? Did the emulated controller connect and was the "Change Grip/Order" menu exited successfully?
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