First of all about BT App, this is free work, it serves my needs and I feel like sharing it with those who have the same needs as me.
As you know, the app has problems connecting to Xbox controllers.
Unfortunately, I don’t have one for this.
For those who want to contribute, you can absolutely:
Hey, probably a bit of a dump question, but when I go to change the audio output on my RG35XX SP I see that there are two Built-In Stereo options, what are the differences between the two?
Compiled this locally and can confirm it’s working. Great job!! It seems like it can’t find devices if the app hasn’t been launched during that session though, idk why. Could it be that bluetooth isn’t on by default? Maybe a custom user init script could somehow “force it” on when booting muOS?
Edit: Just adding the standard bluetooth.sh to MUOS/init does the trick, now it auto-connects after booting the device without needing to go into the Bluetooth app!
However, after auto-connecting, the connected controller doesn’t seem to react until a button on the actual device is pressed. Is there a way to bypass this issue?
So, what my fork is doing under the hood is updating the MUOS/init/bluetooth.sh script, so if that does not exist yet then it won’t do anything. I wasn’t sure how the app was handling that as a package, so for the moment I had left it to the merge to make sure all the files were in the right place, which might explain your hiccup!
And that’s an interesting question for your controller – I’m not sure, but if I have time I could definitely look into it.
If you cannot connect using Expect, please restart your Bluetooth device and try using None Expect.
Additionally, I’ve also updated the scripts to be compatible with muOS Goose.
I added this because my newly purchased headphones couldn’t connect using Expect.
The None Expect method worked for me. I think this will work with Xbox controllers.
If you still have issues with Xbox controllers, please consider contributing to the source code or donating so I can buy one for testing. (https://ko-fi.com/alcavic)
I bought an iine retro pocket game controller and when I connect it via bluetooth to my device and open a game it doesn’t work. When I open the Retroarch menu it keeps going up and up and I can’t do anything else. Does anyone know what it could be or how to fix it? Other controllers work normally.
Hi guys. I’m on MuOS Pixie on RG35xx Plus, I installed the bluetooth app via archive manager. I have tried connecting a 8Bitdo Pro 2, as well as a third party controller (which i use for ps4). They both connect fine in the BT app (the TP controller shows as a Switch Pro Controller). The 8Bitdo does not show up in RetroArch, but the ‘switch’ one does. However the device does not pick up input from either controller (in the BT App, the main menu, or retroarch). TL:DR Connects in BT app, but no input anywhere. Can anyone help?
There’s an (unintended?) behavior, not sure if it’s a muOS issue or something to do with the app. When a paired Bluetooth controller automatically connects after turning on, it won’t register any input until I use the controls on the device first, then the controller starts registering inputs normally.
