BLE name issue

[mritunjai-capgemini]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

BLE should always display the actual provided bluetooth name even after disconnect/connect.

Actual behavior (suspected bug)

On every connection BLE should display the actual provided bluetooth name but BLE name is coming correctly only on first connection, after it disconnect and then connect, it displays ble name as 'N/A'. We are using binc driver code on our board with Bluez version 5.65.

Error logs or terminal output

No response

Steps to reproduce the behavior

1. Bluetooth service starts
2. BleGattserver with Binc starts
3. Device advertises with name
4. Connect
5. Disconnect
6. Device adverises with N/A
7. Even if we kill and restart BleGattServer, advertisement would be N/A
8. If we kill both BleGattServer & Bluetooth and redo from step#1, then every step above repeats i.e. name would be advertise until 1st connect and disconnect.

Project release version

v1.0.3

System architecture

ARM 64-bit (Apple M1/M2, Raspberry Pi 4/5)

Operating system

Linux

Operating system version

Linux

Shell

Bash

Additional context

No response

[mantriyogesh]

hello @mritunjai-capgemini ,

I’m having difficulty understanding how this could be an ESP-Hosted issue, given that ESP-Hosted's role is primarily to relay messages between the BlueZ stack and the BLE controller. Could you please help clarify?

Further, I suspect that this may be BlueZ stack issue or BlueZ stack with specific Kernel version issue.

Some related links:

1. Cannot start advertising or re-register an advertisement after disconnecting BLE device bluez/bluez#644 (Check with BlueZ)
2. Failed to register advertisement: org.bluez.Error.Failed #453