04-19-2018, 11:55 AM
(04-19-2018, 11:05 AM)Tim Curtis Wrote:(04-19-2018, 08:37 AM)Hillsidebeer Wrote: Thanks for the suggestions. It didn't seem to work quite that way for me. I have BT turned on the the System settings, but I can't use the BT configuration commands until I've selected BT as the output on the SEL page. I can then go to the BLU page and Initialise Controller, Scan, Pair and Connect, reporting apparent success each time. However, the Anker speaker never shows a connection and if I list connections in BLU, none exists.
The speakers links up to my phone with no problem, so the issue seems to be with my Moode settings.
Andy
Hi Andy,
The process for making outbound Bluetooth connections in 4.1 is not very well implemented. Its been completely redesigned for 4.2 update so just hang tight for a while. One of the challenges is that many Bluetooth Speakers auto-connect after they are powered up. This is an inbound connection to moOde, as if a Phone has just connected, and so the the UI reacts accordingly until MPD audio output is set to Bluetooth.
-Tim
I consider Autoconnect an invasive feature. If I have BT enabled on my phone, I can tell when my SO pulls into the driveway because her Suburu's Entertainment System autoconnects and takes over my phone as if I were the driver. After all, I've paired with it in the past so obviously this must be what I want to have happen. It's a pain to have to "forget" BT devices explicitly only to go through the whole pairing/connect scenario the next time you want to use them.
Besides the usual assortment of phones and tablets, the only BT-enabled devices I can test with are a small JBL Flip 2 speaker which works fine with moOde, an Amazon Echo which doesn't, and I think for different reasons than autoconnection.
