Thank you for your donation!


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problem: Issue with Blutooth in 4.1
#11
(04-16-2018, 08:48 PM)Tim Curtis Wrote:
(04-16-2018, 08:09 PM)Tim Curtis Wrote: Hi Kent,

For reference, I just ran a clean-slate test using iPhone, iPad and an ANKER SoundCore speaker with release 4.1 on Pi-3B, 3B+ and a 0W. The only issue I ran into was that I had to turn Bluetooth OFF/ON on my iPhone in order for it to see the 0W, otherwise no issues with discovery, pairing, connecting and playing music.

Email me if you run into issues tonight :-)

-Tim

Hey Kent,

Bluetoothctl util can be used to see what Bluetooth profiles a particular paired device supports. The device needs to be paired but not connected.

Examples showing support for "Advanced Audio Distribu.." (A2DP) profile for both Anker SoundCore Speaker and iPhone.

Code:
pi@rp3:~ $ sudo bluetoothctl
Agent registered
[bluetooth]# info XX:XX:XX:XX:XX:XX
Device XX:XX:XX:XX:XX:XX (public)
        Name: Anker SoundCore
        Alias: Anker SoundCore
        Class: 0x00240404
        Icon: audio-card
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
[bluetooth]# 

[bluetooth]# info YY:YY:YY:YY:YY:YY
Device YY:YY:YY:YY:YY:YY (public)
        Name: Tim's iPhone
        Alias: Tim's iPhone
        Class: 0x007a020c
        Icon: phone
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacafe)
        UUID: Service Discovery Serve.. (00001000-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: NAP                       (00001116-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v004Cp6D00d0A30
[bluetooth]# 

-Tim

Thanks. I emailed you some test results before I saw this. Expect an addendum.
Reply
#12
I kinda have similar problems with BT....Can't connect to my (Chinese) phone:

Code:
pi@JST-moOde:~ $ systemctl status bluetooth
● bluetooth.service - Bluetooth service
  Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)                                                                                                
  Active: active (running) since Tue 2018-04-17 00:39:11 CEST; 5min ago
    Docs: man:bluetoothd(8)                                                                                                                                                                
Main PID: 830 (bluetoothd)                                                                                                                                                                
  Status: "Running"                                                                                                                                                                        
  CGroup: /system.slice/bluetooth.service                                                                                                                                                  
          └─830 /usr/sbin/bluetoothd --noplugin=sap                                                                                                                                        
                                                                                                                                                                                           
Apr 17 00:39:11 JST-moOde systemd[1]: Starting Bluetooth service...                                                                                                                        
Apr 17 00:39:11 JST-moOde bluetoothd[830]: Bluetooth daemon 5.49                                                                                                                            
Apr 17 00:39:11 JST-moOde systemd[1]: Started Bluetooth service.                                                                                                                            
Apr 17 00:39:11 JST-moOde bluetoothd[830]: Starting SDP server                                                                                                                              
Apr 17 00:39:11 JST-moOde bluetoothd[830]: Bluetooth management interface 1.14 initialized                                                                                                  
Apr 17 00:39:11 JST-moOde bluetoothd[830]: Endpoint registered: sender=:1.9 path=/A2DP/SBC/Source/1                                                                                        
Apr 17 00:41:01 JST-moOde bluetoothd[830]: a2dp-source profile connect failed for C0:EE:FB:4A:3C:D0: Protocol not available
Apr 17 00:42:51 JST-moOde bluetoothd[830]: a2dp-source profile connect failed for C0:EE:FB:4A:3C:D0: Protocol not available
pi@JST-moOde:~ $
And the thing is, it says "protocol not available", which is weird, cuz I use this a2dp protocol to connect my phone to my car....
Johan
I swear your honor, I have no idea where that knife came from....
Reply
#13
(04-16-2018, 05:57 PM)TheOldPresbyope Wrote:
(04-16-2018, 04:54 PM)dbrgn Wrote: I also just tried it with the Nexus 10 Android tablet - same result.

...

@dbrgn

Running the app "Bluetooth Profiles Scanner" on my Nexus 9 tablet (Android 7.1.1), I see the two moOde r41 players I currently have running are advertising both the Advanced Audio Distribution Audio Profile (A2DP) and the Audio/Video Remote Control Profile (AVRCP). In the Bluetooth devices screen on the tablet, I see (under the gear icons) the paired players can be used for media audio.

Having said this, using the same Bluetooth source and settings, my installation of the released version of r41 doesn't seem to be playing the Bluetooth stream while an earlier r41beta version does, so I think you may be on to something.

...

Regards,
Kent

@dbrgn

So I went through several cycles of clearing and configuring moOde r4.1 and my Nexus 6P phone (Android 8.1.1) while generating test data to send to Tim. 

At some point, I discovered moOde was now playing the music being streamed over Bluetooth. However, I don't seem to be able to do this repeatedly and I broke it again trying several different Android devices (a Nexus 9 tablet running Android 7.1.1 and a Nexus 7 tablet running Android 6.0.1 over a third-party rom).

I believe the basic Bluetooth audio stack is working properly (e.g., A2DP is working as it should) but the pairing-connecting mechanism is brittle.

Regards,
Kent
Reply
#14
(04-17-2018, 01:52 AM)TheOldPresbyope Wrote:
(04-16-2018, 05:57 PM)TheOldPresbyope Wrote:
(04-16-2018, 04:54 PM)dbrgn Wrote: I also just tried it with the Nexus 10 Android tablet - same result.

...

@dbrgn

Running the app "Bluetooth Profiles Scanner" on my Nexus 9 tablet (Android 7.1.1), I see the two moOde r41 players I currently have running are advertising both the Advanced Audio Distribution Audio Profile (A2DP) and the Audio/Video Remote Control Profile (AVRCP). In the Bluetooth devices screen on the tablet, I see (under the gear icons) the paired players can be used for media audio.

Having said this, using the same Bluetooth source and settings, my installation of the released version of r41 doesn't seem to be playing the Bluetooth stream while an earlier r41beta version does, so I think you may be on to something.

...

Regards,
Kent

@dbrgn

So I went through several cycles of clearing and configuring moOde r4.1 and my Nexus 6P phone (Android 8.1.1) while generating test data to send to Tim. 

At some point, I discovered moOde was now playing the music being streamed over Bluetooth. However, I don't seem to be able to do this repeatedly and I broke it again trying several different Android devices (a Nexus 9 tablet running Android 7.1.1 and a Nexus 7 tablet running Android 6.0.1 over a third-party rom).

I believe the basic Bluetooth audio stack is working properly (e.g., A2DP is working as it should) but the pairing-connecting mechanism is brittle.

Regards,
Kent

Just to add a coda to my story.

I've now got all three Android devices connected to my moOde r41 player via BT. I can play music from any of them, and two of them, or even all three of them at the same time.

The magic seemed to be to go through the pairing and connecting process with one Android device. Then turn off the BT on that device and turn it on again, followed by reconnecting it to moOde (it's already paired at this point). After that, I could play music from it. Even better, I could now go on to pair and connect more devices and play from them immediately (e.g., without having to cycle their BT off/on).

I'll have to start again with a fresh install to see if this off/on cycling of the BT connection is reproducible. Meanwhile, all my Android devices are working fine with this moOde player.

Regards,
Kent
Reply


Forum Jump: