# Bluetooth App
**URL:** https://community.muos.dev/t/bluetooth-app/163
**Category:** Release
**Tags:** pixie, banana
**Created:** [April 15, 2025, 8:53am UTC](https://community.muos.dev/t/bluetooth-app/163 "2025-04-15T08:53:41Z")
**Posts on this page:** 20
**Page:** 7
### Author:  [@iKuba](https://community.muos.dev/u/iKuba)
#### Post date: [September 25, 2025, 5:35am UTC](https://community.muos.dev/t/bluetooth-app/163/122 "2025-09-25T05:35:46Z")
but the currently BT works only if wi-fi connected, if I disconnect wi-fi BT starts failing to start
I make all the same steps as on original goose - installed, open and trying to start
I also created a topic [Canada Goose Wi-Fi](https://community.muos.dev/t/canada-goose-wi-fi/866)
can these issues be connected?
---
### Author:  [@nvcuong1312](https://community.muos.dev/u/nvcuong1312)
#### Post date: [September 25, 2025, 5:54am UTC](https://community.muos.dev/t/bluetooth-app/163/123 "2025-09-25T05:54:31Z")
Yes. Wifi and BT are in one chip. So if you turn off wifi, BT is also turned off. So make sure wifi is always on (not required to connect to any network)
---
### Author:  [@iKuba](https://community.muos.dev/u/iKuba)
#### Post date: [September 25, 2025, 6:02am UTC](https://community.muos.dev/t/bluetooth-app/163/124 "2025-09-25T06:02:22Z")
~~I’m not sure that I understand correctly.~~
~~how can I turn wi-fi chip off? I thought it always on?~~
~~I’m saying not about turing the chip on/off.~~
~~I mean I can use BT only when I connected to some wi-fi network (receiving IP from it, don’t not how to explain more clear)~~
~~And as I say on previous version of goose there was not such an issue - I could use BT without connection to wi-fi network.~~
upd.: made some tests:
looks like BT work depends not from actual connection to the network but on “start network on boot” toggle in wi-fi settings.
It seems like this toggle works as “turning on/off wi-fi chip on boot”
But it should work (and did work in goose) as “trying connect to saved network on boot”
so I suppose that is not BT app issue, but the issue from mentioned topic [Canada Goose Wi-Fi](https://community.muos.dev/t/canada-goose-wi-fi/866)
---
### Author:  [@nvcuong1312](https://community.muos.dev/u/nvcuong1312)
#### Post date: [September 25, 2025, 6:41am UTC](https://community.muos.dev/t/bluetooth-app/163/125 "2025-09-25T06:41:36Z")
Yes it has always been on since Pixiel. Maybe something was changed since Canada Goose that caused the chip to be off. :dogheh:
---
### Author:  [@greenleaf108](https://community.muos.dev/u/greenleaf108)
#### Post date: [September 25, 2025, 12:46pm UTC](https://community.muos.dev/t/bluetooth-app/163/126 "2025-09-25T12:46:37Z")
Here’s the behavior I observed:
- With a WiFi network configured but not “start at boot”, the bluetooth app is unable to start Bluetooth.
The only way I was able to get this app working was to blank out the SSID and password, _and_ enable start at boot.
If the previous behavior was that bluetooth and wifi could both be on at the same time, then something is definitely amiss in the Canada Goose release.
---
### Author:  [@iKuba](https://community.muos.dev/u/iKuba)
#### Post date: [September 25, 2025, 1:34pm UTC](https://community.muos.dev/t/bluetooth-app/163/127 "2025-09-25T13:34:41Z")
thats what i’ms talking about, but looks like its not a BT app issue, so you can bump my topic for increasing chances for help - [Canada Goose Wi-Fi](https://community.muos.dev/t/canada-goose-wi-fi/866)
---
### Author:  [@chungiiie](https://community.muos.dev/u/chungiiie)
#### Post date: [September 30, 2025, 12:24pm UTC](https://community.muos.dev/t/bluetooth-app/163/128 "2025-09-30T12:24:16Z")
Unable to connect. Everytime I try it gives me “Attempt to index a nil value” error. I’m trying on RG Cube XX. Please help.
---
### Author:  [@Doctorossi](https://community.muos.dev/u/Doctorossi)
#### Post date: [September 30, 2025, 3:40pm UTC](https://community.muos.dev/t/bluetooth-app/163/129 "2025-09-30T15:40:19Z")
I’m running Canada Goose on RG35XX H. I tried to install the app and the install process reported success but when I look in the Apps section, there’s nothing new there. Am I missing the app somewhere else? Or did the installation actually fail?
---
### Author:  [@nvcuong1312](https://community.muos.dev/u/nvcuong1312)
#### Post date: [October 1, 2025, 4:42pm UTC](https://community.muos.dev/t/bluetooth-app/163/130 "2025-10-01T16:42:38Z")
Make sure you install from the file with the .muxupd extension
---
### Author:  [@nvcuong1312](https://community.muos.dev/u/nvcuong1312)
#### Post date: [October 1, 2025, 4:43pm UTC](https://community.muos.dev/t/bluetooth-app/163/131 "2025-10-01T16:43:44Z")
Please tell me what is the name of your bluetooth device
---
### Author:  [@Doctorossi](https://community.muos.dev/u/Doctorossi)
#### Post date: [October 1, 2025, 4:59pm UTC](https://community.muos.dev/t/bluetooth-app/163/132 "2025-10-01T16:59:35Z")
Yes, that’s the one I used- thanks.
---
### Author:  [@chungiiie](https://community.muos.dev/u/chungiiie)
#### Post date: [October 2, 2025, 9:16am UTC](https://community.muos.dev/t/bluetooth-app/163/133 "2025-10-02T09:16:34Z")
I’m using the 8bitdo SN30 Pro. thnx
---
### Author:  [@nvcuong1312](https://community.muos.dev/u/nvcuong1312)
#### Post date: [October 3, 2025, 5:21pm UTC](https://community.muos.dev/t/bluetooth-app/163/134 "2025-10-03T17:21:51Z")
BT App is now available on Trimui Brick.
(It will probably work on the Trimui Smart Pro too, I’m just not sure if the buttons are mapped properly)
Also, I fixed the issue of not being able to turn on BT after deep sleep.
---
### Author:  [@Brenoit](https://community.muos.dev/u/Brenoit)
#### Post date: [October 3, 2025, 8:12pm UTC](https://community.muos.dev/t/bluetooth-app/163/135 "2025-10-03T20:12:25Z")
I own a 8bitdo SN30Pro with the last firmware installed.
The bluetooth app sees it, and can connect/pair to it (in D-input mode, set with start+B at controller boot). And then… Nothing. the MuOS menu does not respond to keys pushed on the controller and Retroarch does not see it. Trying to set the controls manually does not yield any result neither.
This happens on any device I installed muOS on (Canada Goose).
I did not have better results with an 8bitdo Micro either…
---
### Author:  [@bulkh](https://community.muos.dev/u/bulkh)
#### Post date: [October 3, 2025, 9:07pm UTC](https://community.muos.dev/t/bluetooth-app/163/136 "2025-10-03T21:07:46Z")
I had the same issue. Try to delete it from history and connect again.
---
### Author:  [@nvcuong1312](https://community.muos.dev/u/nvcuong1312)
#### Post date: [October 3, 2025, 11:49pm UTC](https://community.muos.dev/t/bluetooth-app/163/137 "2025-10-03T23:49:49Z")
Lmao. I just tried it and got the same thing, but after some tinkering it worked fine again.
Here are the steps I took:
1. Play any game
2. Open Quick Menu
3. Overrides
4. Unload Overrides
5. Main Menu - Configuration file - Save Current Configuration
6. Quit
7. Connect to the controller and open the game to configure the controller (now input is received)
---
### Author:  [@palotaiz87](https://community.muos.dev/u/palotaiz87)
#### Post date: [October 8, 2025, 7:36am UTC](https://community.muos.dev/t/bluetooth-app/163/138 "2025-10-08T07:36:43Z")
I’ve been using this App since I bought my first Anbernic handheld. It works like a breeze. Pairs my BT headphones and connects them in no time.
When I saw that it is also available on TrimUI devices I quickly checked it.
It worked on my Brick but unfortunately, the devices that I already connected disappeared after reboot.
I also checked the App on my Smart Pro and it didn’t work. No button presses were detected.
This frustrated me and I started to debug the issue. A little bit later I noticed that adding gptokeyb2 to the launcher script fixes the issue on TSP. The buttons started to work.
I also found that the firmware is the issue with the disappearing devices. The BT firmware assigns a new hw address to the Bluetooth interface every time the device starts up. This is not fortunate, as bluetoothd stores the information of the paired devices in the `/var/lib/bluetooth//` folder. I also tried to fix this issue. Unfortunately, I could not make the firmware use a static address, so I needed to find a workaround.
At the end, I created two pull requests in GitHub. Please check them. I tested them both on my Brick and my Smart Pro. The code with those modifications is working for me, but there might be issues I didn’t notice or something I forgot to update.
Thanks again for this great App. I love it.
---
### Author:  [@nvcuong1312](https://community.muos.dev/u/nvcuong1312)
#### Post date: [October 8, 2025, 12:20pm UTC](https://community.muos.dev/t/bluetooth-app/163/139 "2025-10-08T12:20:18Z")
Thank you very much. I merged them and the build automatically built here:
>
I haven’t tested it yet so I can’t release it yet.
Maybe I will release it tomorrow.
Again, thank you so much!!!
---
### Author:  [@palotaiz87](https://community.muos.dev/u/palotaiz87)
#### Post date: [October 8, 2025, 1:23pm UTC](https://community.muos.dev/t/bluetooth-app/163/140 "2025-10-08T13:23:07Z")
Don’t worry about it, take your time and make sure everything works.
---
### Author:  [@nvcuong1312](https://community.muos.dev/u/nvcuong1312)
#### Post date: [October 9, 2025, 11:11am UTC](https://community.muos.dev/t/bluetooth-app/163/141 "2025-10-09T11:11:49Z")
The new update for Trimui is available.
Thank you so much @palotaiz87
> **[Releases · nvcuong1312/bltMuos](https://github.com/nvcuong1312/bltMuos/releases)**
>
> Bluetooth Settings for MUOS. Contribute to nvcuong1312/bltMuos development by creating an account on GitHub.
[Previous page](https://community.muos.dev/t/bluetooth-app/163.md?page=6)
[Next page](https://community.muos.dev/t/bluetooth-app/163.md?page=8)