Bug 318637 - bluetooth headset output/soundcard not shown in phonon settings in KDE - unable to play sound via bluetooth device
Summary: bluetooth headset output/soundcard not shown in phonon settings in KDE - unab...
Status: RESOLVED FIXED
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.6.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 4.6.1
Assignee: Harald Sitter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-20 14:24 UTC by Daniel Duris
Modified: 2022-12-31 11:03 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Duris 2013-04-20 14:24:12 UTC
I am unable to set up a bluetooth audio device (speaker) as output for KDE sound system.

Bluetooth connects without a problem, device indicates it is connected as well.

Option to route sound via Bluetooth is not shown in System Settings->Multimedia->phonon-audio hardware setup.

Reproducible: Always

Steps to Reproduce:
1. Pair bluetooth sound output device (headet and audio sink) to KDE
2. try to change sound routing
3. option is not shown
Actual Results:  
Not able to route sound via bluetooth

Expected Results:  
SOund routing via bluetooth

[    5.699986] Bluetooth: Core ver 2.16
[    5.700000] NET: Registered protocol family 31
[    5.700002] Bluetooth: HCI device and connection manager initialized
[    5.700003] Bluetooth: HCI socket layer initialized
[    5.700004] Bluetooth: L2CAP socket layer initialized
[    5.700008] Bluetooth: SCO socket layer initialized
[    5.701098] Bluetooth: Generic Bluetooth USB driver ver 0.6
[    5.701333] usbcore: registered new interface driver btusb
[    5.808812] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.808815] Bluetooth: BNEP filters: protocol multicast
[    5.822919] Bluetooth: RFCOMM TTY layer initialized
[    5.822924] Bluetooth: RFCOMM socket layer initialized
[    5.822925] Bluetooth: RFCOMM ver 1.11

Bus 003 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth

$ lsmod |grep blue
bluetooth             180153  28 hidp,rfcomm,bnep,btusb
toshiba_bluetooth      12807  0
Comment 1 Jean-Baptiste Kempf 2013-05-25 21:00:56 UTC
You should use PulseAudio.
Comment 2 Daniel Duris 2013-05-26 20:58:23 UTC
pulseaudio is used, this still happens.
Comment 3 Martin Sandsmark 2013-05-27 08:17:14 UTC
adding our PulseAudio expert.
Comment 4 Harald Sitter 2013-07-03 19:38:45 UTC
Unless I am mistaken you should see the device in the first tab not the hardware setup tab. Also that's where you'd need to change the routing.
Comment 5 Daniel Duris 2013-07-03 20:42:27 UTC
Anyway, device does not get displayed there either.
Comment 6 Harald Sitter 2013-07-03 21:03:38 UTC
output of 

> pacmd list-sinks

please
Comment 7 Daniel Duris 2013-07-05 12:20:28 UTC
this is with bluetooth showing audio device connected (!)

>>> 1 sink(s) available.
  * index: 0
        name: <alsa_output.pci-0000_00_1b.0.analog-stereo>
        driver: <module-alsa-card.c>
        flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
        state: RUNNING
        suspend cause: 
        priority: 9959
        volume: 0:  84% 1:  84%
                0: -4.57 dB 1: -4.57 dB
                balance 0.00
        base volume: 100%
                     0.00 dB
        volume steps: 65537
        muted: no
        current latency: 61.06 ms
        max request: 15 KiB
        max rewind: 64 KiB
        monitor source: 0
        sample spec: s16le 2ch 44100Hz
        channel map: front-left,front-right
                     Stereo
        used by: 1
        linked by: 1
        configured latency: 90.00 ms; range is 2.00 .. 371.52 ms
        card: 0 <alsa_card.pci-0000_00_1b.0>
        module: 4
        properties:
                alsa.resolution_bits = "16"
                device.api = "alsa"
                device.class = "sound"
                alsa.class = "generic"
                alsa.subclass = "generic-mix"
                alsa.name = "ALC269VB Analog"
                alsa.id = "ALC269VB Analog"
                alsa.subdevice = "0"
                alsa.subdevice_name = "subdevice #0"
                alsa.device = "0"
                alsa.card = "0"
                alsa.card_name = "HDA Intel PCH"
                alsa.long_card_name = "HDA Intel PCH at 0xc4820000 irq 52"
                alsa.driver_name = "snd_hda_intel"
                device.bus_path = "pci-0000:00:1b.0"
                sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"
                device.bus = "pci"
                device.vendor.id = "8086"
                device.vendor.name = "Intel Corporation"
                device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller"
                device.form_factor = "internal"
                device.string = "front:0"
                device.buffering.buffer_size = "65536"
                device.buffering.fragment_size = "32768"
                device.access_mode = "mmap+timer"
                device.profile.name = "analog-stereo"
                device.profile.description = "Analog Stereo"
                device.description = "Built-in Audio Analog Stereo"
                alsa.mixer_name = "Intel CougarPoint HDMI"
                alsa.components = "HDA:10ec0269,1179062e,00100100 HDA:80862805,11790001,00100000"
                module-udev-detect.discovered = "1"
                device.icon_name = "audio-card-pci"
        ports:
                analog-output-speaker: Speakers (priority 10000, available: no)
                        properties:

                analog-output-headphones: Headphones (priority 9000, available: yes)
                        properties:

        active port: <analog-output-headphones>
Comment 8 Andrew Crouthamel 2018-11-10 03:12:10 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Andrew Crouthamel 2018-11-20 04:02:34 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Justin Zobel 2022-12-31 00:24:16 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 11 Daniel Duris 2022-12-31 11:03:29 UTC
It has been working for years now.