You are not logged in.

#1 2017-11-27 15:37:01

reesewang
Member
Registered: 2017-11-27
Posts: 1

Duplicated endpoints causing bluetoothd error?

I recently configured my Bluetooth headset, but it isn't stable.

I noticed following lines in bluetoothd journal:

Nov 27 23:10:29 bluetoothd[2148]: Starting SDP server
Nov 27 23:10:29 bluetoothd[2148]: Bluetooth management interface 1.14 initialized
Nov 27 23:10:29 bluetoothd[2148]: Endpoint registered: sender=:1.67 path=/MediaEndpoint/A2DPSource
Nov 27 23:10:29 bluetoothd[2148]: Endpoint registered: sender=:1.67 path=/MediaEndpoint/A2DPSink
Nov 27 23:10:29 bluetoothd[2148]: Endpoint registered: sender=:1.39 path=/MediaEndpoint/A2DPSource
Nov 27 23:10:29 bluetoothd[2148]: Endpoint registered: sender=:1.39 path=/MediaEndpoint/A2DPSink
Nov 27 23:10:29 bluetoothd[2148]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Nov 27 23:10:29 bluetoothd[2148]: RFCOMM server failed for :1.39/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb: rfcomm_bind: Address already in use (98)

The last two lines are error messages. It seems that two pairs of endpoints with the different sender is registered and one endpoint (1.39) failed in rfcomm_bind because the address is already taken by another endpoint (1.67).

How to avoid these errors?

Last edited by reesewang (2017-11-27 15:37:45)

Offline

Board footer

Powered by FluxBB