Bug 91502

Summary:	Audio unstable using HFP profileon IMX6
Product:	PulseAudio	Reporter:	mallory.daries
Component:	modules	Assignee:	pulseaudio-bugs
Status:	RESOLVED MOVED	QA Contact:	pulseaudio-bugs
Severity:	major
Priority:	medium	CC:	lennart
Version:	unspecified
Hardware:	ARM
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	Pulseaudio log first time succes + 2nd time fail

Description mallory.daries 2015-07-29 16:43:12 UTC

Created attachment 117444 [details]
Pulseaudio log first time succes + 2nd time fail

Hi,
I'm currently integrating in Yocto pulseaudio 6.0 with bluez 5.28 and ofono 1.16 on a Nitrogen6x board (with dongle bluetooth Belkin).
My purpose is to use the board as handsfree gateway: 
with a smartphone connected via bluetooth redirect the sound of a voicecall from the smartphone to the board output (HFP profile).

I already got it work on my computer as I can hear the voicecall with the computer's speaker as output and use the integrated microphone as input.
I'm using Pulseaudio launched as a user-instance with the backend ofono.
I had strange behaviour testing it : 

After connecting my phone with bluetoothctl pulseaudio create an HF card and I got the same output as on my computer where HFP is working
D: [pulseaudio] bluez5-util.c: oFono is running: yes
D: [pulseaudio] backend-ofono.c: New HF card found: /card_4
D: [pulseaudio] backend-ofono.c: RemoteAddress: 40:A6:D9:6E:1B:73
D: [pulseaudio] backend-ofono.c: LocalAddress: 00:0A:3A:7A:3A:58
D: [pulseaudio] bluez5-util.c: Transport /card_4 state changed from disconnected to idle
D: [pulseaudio] module-bluez5-discover.c: Loading module-bluez5-device path=/org/bluez/hci0/dev_40_A6_D9_6E_1B_73
I: [pulseaudio] module-card-restore.c: Restoring port latency offsets for card bluez_card.40_A6_D9_6E_1B_73.
I: [pulseaudio] card.c: Created 1 "bluez_card.40_A6_D9_6E_1B_73"
D: [pulseaudio] module-bluez5-device.c: Acquiring transport /card_4
E: [pulseaudio] backend-ofono.c: Deferred setup failed on fd -1: Transport endpoint is not connected

I dial a number on my phone and it works well at the first try, the audio is routed to the output of the board.(see pulseaudio_log_success_HFP)
Then, I hangup the call and make a second try, and the problems are coming :

pulseaudio loops for few minutes :

I: [alsa-sink-HiFi sgtl5000-0] module-loopback.c: Could not peek into queue
D: [bluetooth] module-loopback.c: Requesting rewind due to end of underrun.

and I also have this kind of messages with dmesg :

Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 1536
Bluetooth: hci0 SCO packet for unknown connection handle 48
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 1536
Bluetooth: hci0 SCO packet for unknown connection handle 48
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 4864
Bluetooth: hci0 SCO packet for unknown connection handle 14
Bluetooth: hci0 SCO packet for unknown connection handle 61695
Bluetooth: hci0 SCO packet for unknown connection handle 65527
Bluetooth: hci0 SCO packet for unknown connection handle 0
Bluetooth: hci0 SCO packet for unknown connection handle 65520
Bluetooth: hci0 SCO packet for unknown connection handle 57392
Bluetooth: hci0 SCO packet for unknown connection handle 101
Bluetooth: hci0 SCO packet for unknown connection handle 63191
Bluetooth: hci0 SCO packet for unknown connection handle 641
Bluetooth: hci0 SCO packet for unknown connection handle 3566
Bluetooth: hci0 SCO packet for unknown connection handle 60418
Bluetooth: hci0 SCO packet for unknown connection handle 41479
Bluetooth: hci0 SCO packet for unknown connection handle 2516
Bluetooth: hci0 SCO packet for unknown connection handle 6178
Bluetooth: hci0 SCO packet for unknown connection handle 56309
Bluetooth: hci0 SCO packet for unknown connection handle 5636
Bluetooth: hci0 SCO packet for unknown connection handle 20508
Bluetooth: Unexpected continuation frame (len 0)
Bluetooth: Unexpected continuation frame (len 0)
Bluetooth: Unexpected continuation frame (len 0)

No sound can be heard in that case.

Ask me for any further information that could be useful.

Mallory

Comment 1 GitLab Migration User 2018-07-30 09:38:19 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/66.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.