Handfree Profile doesn't work on most boots/attempts
Description
Following messages in journalctl are related to handsfree in ofono not working (i.e. not showing an connected/powered state):
.... bluetoothd[280]: RFCOMM server failed for Hands-Free unit: rfcomm_bind: Address already in use (98) ... bluetoothd[248]: Unable to connect hfp_hf: connect: Device or resource busy (16) bluetoothd[248]: Connecting hfp_hf failed: Input/output error ...
Important note is that seems happen at least 75% of the time which blocks making a phone call via HFP, and could be a simple race condition but also as likely an issue with 4A + ofono/bluez conflicting.
Environment
None
Activity
Matt Ranostay
January 18, 2019 at 9:14 AM
Works on master. Noted it won't be fixed on flounder
Thierry Bultel
January 17, 2019 at 2:40 PM
Hi Matt,
would you mind specifying the affected version ? Typically, HFP will not work on flounder, and will fail with the log you point, and it will not be fixed.
But on master, this must work.
Thanks !
Thierry
Jan-Simon Moeller
January 16, 2019 at 10:14 AM
: any advice?
Matt Ranostay
January 16, 2019 at 9:13 AM
How to confirm if is a 4A conflict with HFP profile?
Following messages in journalctl are related to handsfree in ofono not working (i.e. not showing an connected/powered state):
....
bluetoothd[280]: RFCOMM server failed for Hands-Free unit: rfcomm_bind: Address already in use (98)
...
bluetoothd[248]: Unable to connect hfp_hf: connect: Device or resource busy (16)
bluetoothd[248]: Connecting hfp_hf failed: Input/output error
...
Important note is that seems happen at least 75% of the time which blocks making a phone call via HFP, and could be a simple race condition but also as likely an issue with 4A + ofono/bluez conflicting.