Bluetooth App

Applications Release
,
61

Hii,

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:

  1. Create a pull request to improve BT App here: GitHub - nvcuong1312/bltMuos: Bluetooth Settings for MUOS.
  2. Donate to me so I can buy some Xbox controllers (I plan to need 2: Xbox One and Xbox Series) here: https://ko-fi.com/alcavic

Thank you for reading and accompanying me during the past time.
:saluting_face:

1 Like
62

Hello, I’ve created a pull request adding autopair functionality. It’s not the prettiest yet, but from my testing it works correctly.

EDIT: Needs a bit more work to get it to switch audio device for those, but it’s a start.

EDIT2: Added that functionality as well.

2 Likes
63

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?

64

I tried it and concluded: one for HDMI, one for built-in speakers.
If HDMI is not plugged in, then it will be the built-in speakers

1 Like
65

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?

1 Like
66

Thanks for giving it a try!

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.

1 Like
67

Thanks for your contribution.
I have a deadline this week so it will be a little late.
I hope you understand.

1 Like
68

Hello,

I have released a new update for the BT App. Download
In this update, I’ve added two connection options: Expect and None Expect.

  • Expect – This is the old method that we have been using so far.
  • None Expect – This is a new method that connects without using Expect.

muOS_20250703_2348_0
muOS_20250703_2348_0640×480 18.9 KB

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)

image
image1237×235 17.4 KB

1 Like
69

I can try it out with my Xbox controller I use for PC. I’ll let you know if I run into any issues.

1 Like
70

Yeah. Thank Bluetooth!. :dogheh:

1 Like
71

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.

72
1 Like
73

Thanks a lot, this fix it. <3

1 Like
74

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?

75

Yeah. Try d-input mode. :dogheh:

76

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.

1 Like
77

Happens to me as well, hope it’s fixable! Maybe, as a workaround, simulating a fake button press upon connection could help?

78

Hi! Controller is work fine now except on PPSSPP. Os retroarch its all set but on PPSSPP it wont recogniza the D-pad and dont let me remap the other buttons. Even when the control is remapped it wont work properly.
Controller: iine retro pocket game controller (shows as IINE CONTROLER or XBOX CONTROLLER. If i try to connet choosing iine the app show one error log. )

79

Yeah.
I also tried but did not find a solution, maybe you need to use ppsspp core in retroarch, then you can configure the controller there.

80

yeah.
BT App is run via bluetoothctl, so there are some OS related things I haven’t mastered yet.
Maybe we need to wait for the next update of muOS then find a solution.