Bug 73231 - Bluetooth speaker immediately connects and disconnects
Summary: Bluetooth speaker immediately connects and disconnects
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-30 19:31 UTC by aldea.diaguita
Modified: 2018-06-29 06:56 UTC (History)
4 users (show)

See Also:
Kernel Version: 3.13.7
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Comment4 - blutoothd logs (66.40 KB, text/plain)
2018-06-28 12:21 UTC, charly
Details
Comment4 - btmon logs (459.60 KB, text/plain)
2018-06-28 12:22 UTC, charly
Details
Comment4 - pulseaudio logs (269.94 KB, text/plain)
2018-06-28 12:22 UTC, charly
Details

Description aldea.diaguita 2014-03-30 19:31:23 UTC
Got a bluetooth speaker paired and recognized as headset, but when i turn it on, get connected and disconnected in less than a second, just one time, and then nothing. Using bluez 5.16-1, pulseaudio 5.0-1, pulseaudio-alsa 2-2, alsa 1-0-27-2-1.

bluetoothctl -a shows this:

[NEW] Device FC:58:FA:F1:EF:51 FD-HR800
Agent registered
[CHG] Device FC:58:FA:F1:EF:51 Connected: yes
[CHG] Device FC:58:FA:F1:EF:51 Connected: no
Comment 1 takieszti91 2014-04-02 23:32:50 UTC
I have a similar problem with my usb dongle and my headset with the same versions of bluez, pulseaudio, pulseaudio-alsa and alsa.
Comment 2 Andrea 2014-04-03 18:48:45 UTC
(In reply to aldea.diaguita from comment #0)
> Got a bluetooth speaker paired and recognized as headset, but when i turn it
> on, get connected and disconnected in less than a second, just one time, and
> then nothing. Using bluez 5.16-1, pulseaudio 5.0-1, pulseaudio-alsa 2-2,
> alsa 1-0-27-2-1.
> 
> bluetoothctl -a shows this:
> 
> [NEW] Device FC:58:FA:F1:EF:51 FD-HR800
> Agent registered
> [CHG] Device FC:58:FA:F1:EF:51 Connected: yes
> [CHG] Device FC:58:FA:F1:EF:51 Connected: no

I have the same issue,
but according to the release notes this is a feature, not a bug.

http://www.bluez.org/release-of-bluez-5-0/

HFP and HSP have been dropped.

in bluetoothctl, do an info on the headset.

I get

Device 00:22:A6:16:E3:F0
        Name: Wireless Headset
        Alias: Wireless Headset
        Class: 0x200404
        Icon: audio-card
        Paired: yes
        Trusted: no
        Blocked: no
        Connected: no
        LegacyPairing: yes
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v12BAp0010d0140

which shows only Headset and Handsfree.
Comment 3 aldea.diaguita 2014-04-07 00:52:15 UTC
with info i get this

Name: FD-HR800
Alias: FD-HR800
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
Comment 4 charly 2018-06-28 12:20:20 UTC
I have a similar issue using the following versions:
bluez 5.50-3
pulseaudio-bluetooth 12.0-1
linux 4.17.2-1-ARCH

My device is an audio sink:
Device FE:5D:E8:35:F8:77 (public)
        Name: MY2608
        Alias: MY2608
        Class: 0x00240408
        Icon: audio-card
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Serial Port               (00001101-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)

My phone connects correctly, but on my laptop it disconnects after a few seconds.
blutoothd logs: https://pastebin.com/KCub12Ny
bluemon logs: https://pastebin.com/dytEqjew
pulseaudio logs: https://pastebin.com/wA1DdZSe

On this last logs, there is this line right before the disconnect:
I: [bluetooth] module-bluez5-device.c: FD error: POLLERR POLLHUP

Not sure how I can help diagnose this bug.
Comment 5 charly 2018-06-28 12:21:39 UTC
Created attachment 276965 [details]
Comment4 - blutoothd logs
Comment 6 charly 2018-06-28 12:22:18 UTC
Created attachment 276967 [details]
Comment4 - btmon logs
Comment 7 charly 2018-06-28 12:22:54 UTC
Created attachment 276969 [details]
Comment4 - pulseaudio logs
Comment 8 Luiz Von Dentz 2018-06-29 06:33:45 UTC
It looks like the adapter is rfkilled:

bluetoothd[6388]: src/rfkill.c:rfkill_event() RFKILL event idx 13 type 2 op 1 soft 0 hard 0
bluetoothd[6388]: src/adapter.c:index_removed() index 0
bluetoothd[6388]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0
bluetoothd[6388]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0
Comment 9 charly 2018-06-29 06:56:43 UTC
Any idea what is causing this?
I have the feeling that somehow the adapter gets reseted by use of
rfkill events:
2018-06-29 09:53:35,866334+03:00: idx 3 type 2 op 1 soft 0 hard 0
2018-06-29 09:53:36,268675+03:00: idx 4 type 2 op 0 soft 0 hard 0

On Fri, Jun 29, 2018 at 9:33 AM <bugzilla-daemon@bugzilla.kernel.org> wrote:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=73231
>
> Luiz Von Dentz (luiz.dentz@gmail.com) changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |luiz.dentz@gmail.com
>
> --- Comment #8 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
> It looks like the adapter is rfkilled:
>
> bluetoothd[6388]: src/rfkill.c:rfkill_event() RFKILL event idx 13 type 2 op 1
> soft 0 hard 0
> bluetoothd[6388]: src/adapter.c:index_removed() index 0
> bluetoothd[6388]: src/adapter.c:adapter_unregister() Unregister path:
> /org/bluez/hci0
> bluetoothd[6388]: src/adapter.c:adapter_remove() Removing adapter
> /org/bluez/hci0
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Note You need to log in before you can comment on or make changes to this bug.