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
can these issues be connected?
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)
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
Yes it has always been on since Pixiel. Maybe something was changed since Canada Goose that caused the chip to be off. 
Hereās the behavior I observed:
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.
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
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.
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?
Make sure you install from the file with the .muxupd extension
Please tell me what is the name of your bluetooth device
Yes, thatās the one I used- thanks.
Iām using the 8bitdo SN30 Pro. thnx
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.
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ā¦
I had the same issue. Try to delete it from history and connect again.
Lmao. I just tried it and got the same thing, but after some tinkering it worked fine again.
Here are the steps I took:
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/<bdaddr>/ 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.
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!!!
Donāt worry about it, take your time and make sure everything works.
