Thank you for your donation!


RPI 3B+, MA4.3 - AS a speaker
#11
That's what I thought.

I may have expressed myself badly in my previous message (my English is not very good, sorry).

In fact, the device trust works well via BlueZ config screen.
These are the requests from Bluetooth clients that are problematic and do not trigger the trsut of client.

So the problem is related to bluetoothd.



I watched what happening via hcidump but I do not know much about it.
I will enquire about that and dig a little more Smile

EDIT : I saw the edit of your message after my tests.
I will search with the help of Btmon who is much more talkative and accurate than hcidump!

Quote:HCI sniffer - Bluetooth packet analyzer ver 5.43
device: hci0 snap_len: 1500 filter: 0xffffffff

> HCI Event: Connect Request (0x04) plen 10
    bdaddr 90:68:C3:E9:54:01 class 0x5a020c type ACL
> HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 90:68:C3:E9:54:01 type ACL encrypt 0x00
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1
> HCI Event: Read Remote Extended Features (0x23) plen 13
    status 0x00 handle 12 page 1 max 2
    Features: 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 90:68:C3:E9:54:01 name 'Moto G'
> HCI Event: Command Complete (0x0e) plen 10
    IO Capability Request Reply (0x01|0x002b) ncmd 1
    status 0x00 bdaddr 90:68:C3:E9:54:01
> HCI Event: Command Complete (0x0e) plen 10
    User Confirmation Request Reply (0x01|0x002c) ncmd 1
    status 0x00 bdaddr 90:68:C3:E9:54:01
> HCI Event: Encrypt Change (0x08) plen 4
    status 0x00 handle 12 encrypt 0x01
> HCI Event: Command Complete (0x0e) plen 7
    Read Encryption Key Size (0x05|0x0008) ncmd 1
> HCI Event: Command Status (0x0f) plen 4
    Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x16
    Reason: Connection Terminated by Local Host
Reply
#12
Maybe, but sometimes when you initiate the connection from the client it has to happen while the scan is being run from moOde, or as soon as the device appears in the scan results. My iPhone is very tolerant but my iPad mini often does not connect at first. Below is the help (#2).

Code:
1) Put your device in discovery mode and verify that it discovers Moode Bluetooth. You may have to turn Bluetooth off/on on your device to accomplish this. Next submit 'SCAN for devices' Action and verify that your device appears in the scan results. The scan runs for 20 seconds.

2) To send audio from your device to moOde:
Initiate the connection on your device. You may have to initiate the connection as soon as your device is discovered and appears in the scan results. After a successful connection the pairing is stored.

3) To send audio from moOde to your device:
Initiate the connection on moOde. Select your device from the scan results, PAIR it then select 'Bluetooth device' for MPD audio output, then CONNECT.

You could try running the btmon tracer and hope that there is an informative error message.

Otherwise it may simply be bugs in the bluetooth stack in moOde 4.3 that may have already been fixed in the latest version of Bluetooth. An upgrade to latest Bluetooth is on the moOde 4.4 TODO list.

-Tim
Reply
#13
You're right Tim, running the scan on MoOde side when initiating the client connection solves most of the problems.
Sorry I missed the instruction you just quoted Undecided

Only an Android device still have a problem. I will wait a Bluetooth update to see if the problem is solved Smile


Incidentally, do you know why some devices need that MoOde scans for bluetooth devices to initiate a connection correctly ?
Reply


Forum Jump: