No sounds for ongoing call in both sides when connecting a BT speaker

Bug #1519594 reported by TarotChen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
In Progress
Undecided
Simon Fels
bluez (Ubuntu)
Invalid
High
Simon Fels
pulseaudio (Ubuntu)
Won't Fix
High
Simon Fels

Bug Description

Test Env:
current build number: 185
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-11-23 03:35:34
version version: 185
version ubuntu: 20151120.1
version device: 20151028-869191d
version custom: 20151111

BT speaker:
Philips BT25

Steps:
1.Connect a BT speaker
2.Play a music file
>Music plays from speaker
3.Make a call to DUT
>Ringtone sounds from the phone
4.Answer the call, then listen and talk

Actual:
No sounds for the call in both sides

Expected:
The calling should sound from the phone

Revision history for this message
Simon Fels (morphis) wrote :

This is quite confusing. Does

> 3.Make a call to DUT
> >Ringtone sounds from the phone

mean you heard the ringtone on the phone or is just your expectation?

> No sounds for the call in both sides

You mean you didn't heard a ringtone on both phones you used to setup the call? Or you didn't heard any voice on both sides?

Also always attach additional debug information by following https://wiki.ubuntu.com/DebuggingBluetooth

Changed in bluez (Ubuntu):
status: New → Incomplete
tags: added: bluez5
Revision history for this message
TarotChen (tarotchen) wrote :

Here are the info and logs:

[Philips BT25]# info FC:58:FA:11:D0:67
Device FC:58:FA:11:D0:67
 Name: Philips BT25
 Alias: Philips BT25
 Class: 0x260404
 Icon: audio-card
 Paired: yes
 Trusted: yes
 Blocked: no
 Connected: yes
 ConnectedProfiles:
   None
 LegacyPairing: no
 UUIDs:
   Serial Port (00001101-0000-1000-8000-00805f9b34fb)
   Headset (00001108-0000-1000-8000-00805f9b34fb)
   Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
   A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
   Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
   A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
   Handsfree (0000111e-0000-1000-8000-00805f9b34fb)

Revision history for this message
TarotChen (tarotchen) wrote :
Revision history for this message
TarotChen (tarotchen) wrote :
Revision history for this message
TarotChen (tarotchen) wrote :
Revision history for this message
TarotChen (tarotchen) wrote :

Answers for #1:

Yes, I can hear the ringtone sounds on the phone and answer the call, but when the call is established I cannot hear any voice from the call on both caller and receiver.

Revision history for this message
Simon Fels (morphis) wrote :

Can you reproduce this bug with following https://wiki.ubuntu.com/DebuggingBluetooth? The logs attached doesn't contain any debug information which would be really helpful.

Revision history for this message
TarotChen (tarotchen) wrote :

I did follow the WIKI page to pull out the log files. How about these?

Revision history for this message
TarotChen (tarotchen) wrote :
Revision history for this message
TarotChen (tarotchen) wrote :
Simon Fels (morphis)
tags: added: bluetooth-ota9
Revision history for this message
TarotChen (tarotchen) wrote :

Also, when re-testing, I aware that after call is established, the call is routed to bluetooth device by default and no voice. Tap speaker icon on live calling page to switch audio resource to ubuntu phone and I can hear the voice on phone.

Hope this can help.

Revision history for this message
Simon Fels (morphis) wrote :

Did you reboot after following the wiki page? The new syslog still doesn't seem to have the debug switches enabled.

Revision history for this message
TarotChen (tarotchen) wrote :

No, I did that before enabling the debug info. :(
How about the new one?

Revision history for this message
TarotChen (tarotchen) wrote :
Revision history for this message
TarotChen (tarotchen) wrote :
Revision history for this message
Simon Fels (morphis) wrote :

Still the same in syslog. Can you verify all steps in https://wiki.ubuntu.com/DebuggingBluetooth manually?

Revision history for this message
TarotChen (tarotchen) wrote :

Use another device to pull out the syslog with following steps:

1.Enable debug info
phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /
phablet@ubuntu-phablet:~$ sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf
phablet@ubuntu-phablet:~$ sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf
Add '-d' to the exec line in /etc/init/ofono.override
2.Reproduce the issue
3.Pull out syslog

If still doesn't work, please let know what is missing.

Simon Fels (morphis)
Changed in bluez (Ubuntu):
status: Incomplete → In Progress
Simon Fels (morphis)
Changed in bluez (Ubuntu):
assignee: nobody → Simon Fels (morphis)
status: In Progress → Invalid
Changed in pulseaudio (Ubuntu):
status: New → Fix Committed
assignee: nobody → Simon Fels (morphis)
Changed in bluez (Ubuntu):
importance: Undecided → High
Changed in pulseaudio (Ubuntu):
importance: Undecided → High
Changed in canonical-devices-system-image:
assignee: nobody → Simon Fels (morphis)
status: New → Confirmed
status: Confirmed → In Progress
tags: added: bluez-touch pulse-touch
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Ubuntu Touch is no longer supported.

Changed in pulseaudio (Ubuntu):
status: Fix Committed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.