06-06-2020, 02:52 PM
Hi, Jorgen.
I'm not able to reproduce your issue using a Google Pixel3a phone and moOde 6.5.2 on an RPi3B+ (my RP3A+ isn't hooked up at the moment). Bluetooth renderer and pairing agent features both enabled. I'm playing a radio station on the phone and piping output via Bluetooth to my moOde player as I type this.
The error messages you reported concerning plugins are unrelated to Bluetooth connectivity. So, I believe, is the th-cmd error message (this is triggerhappy and I see nothing in its configuration file to suggest a possible interaction).
More to the point, I see them too. OTOH I do not see the bluetoothd error messages you reported.
Not sure what to suggest you do. Maybe try reverting to the manual scanning/pairing/connecting process in the Bluetooth Config screen?
Bluetooth is a messy specification and vendors arrive at their own interpretations of it. My Pixel is "pure" Android so has the Android team's interpretation. I don't know how much spin the Moto team give it.
Regards,
Kent
I'm not able to reproduce your issue using a Google Pixel3a phone and moOde 6.5.2 on an RPi3B+ (my RP3A+ isn't hooked up at the moment). Bluetooth renderer and pairing agent features both enabled. I'm playing a radio station on the phone and piping output via Bluetooth to my moOde player as I type this.
The error messages you reported concerning plugins are unrelated to Bluetooth connectivity. So, I believe, is the th-cmd error message (this is triggerhappy and I see nothing in its configuration file to suggest a possible interaction).
More to the point, I see them too. OTOH I do not see the bluetoothd error messages you reported.
Not sure what to suggest you do. Maybe try reverting to the manual scanning/pairing/connecting process in the Bluetooth Config screen?
Bluetooth is a messy specification and vendors arrive at their own interpretations of it. My Pixel is "pure" Android so has the Android team's interpretation. I don't know how much spin the Moto team give it.
Regards,
Kent
