View topic - Bluetooth phone no longer works with 3.12 kernel series :: aptosid.com :: aptosid

Bluetooth phone no longer works with 3.12 kernel series

aptosid.com Forum Index » Support Forums » Hardware

Author

Message

alexk

Post subject: Bluetooth phone no longer works with 3.12 kernel series

Posted: 24.12.2013, 06:14

Joined: 2010-10-01
Posts: 288

Status: Offline

A Panasonic KX-TG76 Bluetooth phone works well as a headset with the 3.11 and previous slh kernels (e.g. 3.11-4.slh.4-aptosid-amd64, 3.11-1.slh.3-aptosid-amd64 and earlier) but not with any 3.12 kernel, including the current 3.12-5.slh.2-aptosid-amd64. I can connect to it, e.g. with "bt-audio -c KX-TG76", but can't turn it on. E.g. in Bluetooth Manager GUI, if I try to change the audio profile of the Headset Service from "Off" to "Telephony Duplex HSP/HFP", it always fails with the message "Failed to change profile to hsp". I similarly can't turn the device on in KDE's System Settings/Multimedia, though it appears there as a Sound Card, the Profile always reverts to "Off". With the same 3.12.5.slh.2 kernel, an Air-Fi AF32 bluetooth headset works fine with both Headset Service and Audio Sink modes.

Code:

bt-device -l
Added devices:
AF32 (02:00:01:00:02:00)
KX-TG76 (00:80:F0:D8:1F:2F)
ASUS Transformer Pad TF700T (60:A4:4C:92:9D:A6)

bt-device -s KX-TG76
Discovering services...

[RECORD:65536]
SrvClassIDList: "Headset AG", "Audio"
ProtocolDescList:
"L2CAP"
"RFCOMM", Channel: 1
BTProfileDescList:
"Headset", 0x102
SrvName: "Voice Gateway"

[RECORD:65593]
SrvClassIDList: "Handsfree", "Audio"
ProtocolDescList:
"L2CAP"
"RFCOMM", Channel: 3
BTProfileDescList:
"Handsfree", 0x105
SrvName: "Hands-Free unit"

[RECORD:65594]
SrvClassIDList: "Handsfree", "Audio"
ProtocolDescList:
"L2CAP"
"RFCOMM", Channel: 2
BTProfileDescList:
"Handsfree", 0x105
SrvName: "Hands-Free unit"

[RECORD:65540]
SrvClassIDList: "OBEXObjPush"
ProtocolDescList:
"L2CAP"
"RFCOMM", Channel: 4
"OBEX"
BTProfileDescList:
"OBEXObjPush", 0x100
SrvName: "OBEX Object Push"

Done

bt-audio -c KX-TG76
Connecting to an audio service
Audio service is connected

tail daemon.log
Dec 24 00:39:50 MSAK1 acpid: input device has been disconnected, fd 18
Dec 24 00:40:02 MSAK1 bluetoothd[4714]: Protocol not supported (93)
Dec 24 00:40:12 MSAK1 bluetoothd[4714]: Protocol not supported (93)
Dec 24 00:41:01 MSAK1 bluetoothd[4714]: Protocol not supported (93)
Dec 24 00:41:18 MSAK1 bluetoothd[4714]: Disconnected from 00:80:F0:D8:1F:2F, /org/bluez/4714/hci0/dev_00_80_F0_D8_1F_2F
Dec 24 00:42:27 MSAK1 bluetoothd[4714]: Protocol not supported (93)
Dec 24 00:42:40 MSAK1 bluetoothd[4714]: Protocol not supported (93)
Dec 24 00:44:12 MSAK1 bluetoothd[4714]: Protocol not supported (93)
Dec 24 00:44:33 MSAK1 bluetoothd[4714]: Protocol not supported (93)

dmesg | tail
[ 1729.171797] Bluetooth: re-auth of legacy device is not possible.
[ 3539.658993] Bluetooth: re-auth of legacy device is not possible.
[ 3713.466399] sdd: detected capacity change from 30005821440 to 0
[ 3720.246077] usb 4-1.4: USB disconnect, device number 3
[ 4361.876880] input: 02:00:01:00:02:00 as /devices/virtual/input/input16
[ 6147.610237] Bluetooth: re-auth of legacy device is not possible.
[ 8513.165004] input: 02:00:01:00:02:00 as /devices/virtual/input/input17
[ 8560.998383] input: 02:00:01:00:02:00 as /devices/virtual/input/input18
[ 8614.289760] input: 02:00:01:00:02:00 as /devices/virtual/input/input19

lsusb | grep -i blue
Bus 003 Device 007: ID 0a5c:2198 Broadcom Corp. Bluetooth 3.0 Device

infobash -v3
Host/Kernel/OS "MSAK1" running Linux 3.12-5.slh.2-aptosid-amd64 x86_64 [ sidux 2009-02 Αιθήρ - kde-full - (200907141427) ]
CPU Info 4x Intel Core i5-2500K @ 6144 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 3538.218 MHz ]
Videocard Intel 2nd Generation Core Processor Family Integrated Graphics Controller X.Org 1.14.5 [ 1280x1024@60.0hz ]
Network cards Intel 82579V Gigabit
ATHEROS USB2.0 WLAN
Processes 211 | Uptime 2:52 | Memory 1795.0/7899.1MB | HDD WDC WD3200AAKS-0 Size 320GB (48%used) | Client Shell | Infobash v3.46

ls /boot/vmlinuz*
/boot/vmlinuz-3.11-1.slh.3-aptosid-amd64 /boot/vmlinuz-3.11-4.slh.4-aptosid-amd64 /boot/vmlinuz-3.12-5.slh.2-aptosid-amd64

alexk

Post subject: RE: Bluetooth phone no longer works with 3.12 kernel series

Posted: 24.12.2013, 16:49

Joined: 2010-10-01
Posts: 288

Status: Offline

Code:

grep -i blue messages | tail -14

Dec 24 07:03:47 MSAK1 kernel: [  118.929959] Bluetooth: re-auth of legacy device is not possible.

Dec 24 10:56:37 MSAK1 kernel: [ 4235.245462] Bluetooth: re-auth of legacy device is not possible.

Dec 24 11:03:52 MSAK1 kernel: [    2.504438] usb 3-1.6: Product: Broadcom Bluetooth 3.0 Device

Dec 24 11:03:52 MSAK1 kernel: [    5.363512] Bluetooth: Core ver 2.16

Dec 24 11:03:52 MSAK1 kernel: [    5.363525] Bluetooth: HCI device and connection manager initialized

Dec 24 11:03:52 MSAK1 kernel: [    5.363532] Bluetooth: HCI socket layer initialized

Dec 24 11:03:52 MSAK1 kernel: [    5.363534] Bluetooth: L2CAP socket layer initialized

Dec 24 11:03:52 MSAK1 kernel: [    5.363538] Bluetooth: SCO socket layer initialized

Dec 24 11:04:00 MSAK1 kernel: [   61.737269] Bluetooth: RFCOMM TTY layer initialized

Dec 24 11:04:00 MSAK1 kernel: [   61.737292] Bluetooth: RFCOMM socket layer initialized

Dec 24 11:04:00 MSAK1 kernel: [   61.737294] Bluetooth: RFCOMM ver 1.11

Dec 24 11:04:01 MSAK1 kernel: [   62.529950] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Dec 24 11:04:01 MSAK1 kernel: [   62.529954] Bluetooth: BNEP filters: protocol multicast

Dec 24 11:04:01 MSAK1 kernel: [   62.529963] Bluetooth: BNEP socket layer initialized

As mentioned above, connecting to the same KX-TG76 bluetooth phone works in 3.11 and previous kernels, e.g:

Code:

uname -r

3.11-4.slh.4-aptosid-amd64

tail daemon.log

Dec 24 11:27:15 MSAK1 bluetoothd[3368]: Endpoint registered: sender=:1.65 path=/MediaEndpoint/HFPAG

Dec 24 11:27:15 MSAK1 bluetoothd[3368]: Endpoint registered: sender=:1.65 path=/MediaEndpoint/HFPHS

Dec 24 11:27:15 MSAK1 bluetoothd[3368]: Endpoint registered: sender=:1.65 path=/MediaEndpoint/A2DPSource

Dec 24 11:27:30 MSAK1 bluetoothd[3368]: /org/bluez/3368/hci0/dev_00_80_F0_D8_1F_2F/fd1: fd(25) ready

This phone has been handy to use with VoIP services such as Googletalk, it connects via bluetooth to a computer and allows to roam beyond bluetooth range.

slh

Post subject: RE: Bluetooth phone no longer works with 3.12 kernel series

Posted: 24.12.2013, 20:39

Joined: 2010-08-25
Posts: 962

Status: Offline

Does it help if you "/etc/init.d/bluetooth restart" as root?

alexk

Post subject: RE: Bluetooth phone no longer works with 3.12 kernel series

Posted: 25.12.2013, 02:39

Joined: 2010-10-01
Posts: 288

Status: Offline

Unfortunately, not. Everything looks good on the cli but the device isn't available anywhere to use.

Code:

$ uname -r

3.12-5.slh.2-aptosid-amd64

alex@MSAK1:/var/log$ sudo /etc/init.d/bluetooth restart

[ ok ] Stopping bluetooth: rfcomm /usr/sbin/bluetoothd.

[ ok ] Starting bluetooth: bluetoothd rfcomm.

alex@MSAK1:/var/log$ bt-device -i KX-TG76

[00:80:F0:D8:1F:2F]

  Name: KX-TG76

  Alias: KX-TG76 [rw]

  Address: 00:80:F0:D8:1F:2F

  Icon: phone

  Class: 0x300208

  Paired: 1

  Trusted: 1 [rw]

  Blocked: 0 [rw]

  Connected: 0

  UUIDs: [OBEXObjectPush, HeadsetAudioGateway, Handsfree]

alex@MSAK1:/var/log$ bt-audio -c KX-TG76

Connecting to an audio service

Audio service is connected

alex@MSAK1:/var/log$ bt-device -i KX-TG76

[00:80:F0:D8:1F:2F]

  Name: KX-TG76

  Alias: KX-TG76 [rw]                                                                                                              

  Address: 00:80:F0:D8:1F:2F                                                                                                       

  Icon: phone                                                                                                                      

  Class: 0x300208                                                                                                                  

  Paired: 1                                                                                                                        

  Trusted: 1 [rw]

  Blocked: 0 [rw]

  Connected: 1

  UUIDs: [OBEXObjectPush, HeadsetAudioGateway, Handsfree]

bt-monitor shows:

Code:

[Device: KX-TG76 (00:80:F0:D8:1F:2F)] Audio property changed: State -> connecting

[Device: KX-TG76 (00:80:F0:D8:1F:2F)] Property changed: Connected -> 1

[Device: KX-TG76 (00:80:F0:D8:1F:2F)] Audio property changed: State -> connected

alexk

Post subject: RE: Bluetooth phone no longer works with 3.12 kernel series

Posted: 26.12.2013, 04:12

Joined: 2010-10-01
Posts: 288

Status: Offline

Same issue with the new 3.12-6.slh.1-aptosid-amd64 kernel as with all the 3.12 series that I've tried:

Code:

Dec 25 23:05:47 MSAK1 bluetoothd[2840]: Protocol not supported (93)

Dec 25 23:05:47 MSAK1 pulseaudio[4813]: [pulseaudio] module-bluetooth-device.c: Failed to acquire transport /org/bluez/2840/hci0/dev_00_80_F0_D8_1F_2F/fd0

I've been using Pulseaudio because I hadn't been able to get bluetooth devices working with ESD.

alexk

Post subject: RE: Bluetooth phone no longer works with 3.12 kernel series

Posted: 12.01.2014, 19:48

Joined: 2010-10-01
Posts: 288

Status: Offline

This issue persists with kernel 3.12-6.slh.4-aptosid-amd64. In addition, the issue is the same with both Enlightenment and KDE. It's only my Panasonic KX-TG76 Bluetooth cordless phone that no longer works in 3.12 kernels, other bluetooth devices still work, including an ISB33 bluetooth wireless speaker that I just tested.

alexk

Post subject:

Posted: 17.02.2014, 18:30

Joined: 2010-10-01
Posts: 288

Status: Offline

No change with kernel 3.13-2.slh.5-aptosid-amd64. I can connect to this KX-TG76 Bluetooth cordless phone, but cannot change the active profile to HSP, it always reverts to off. A bluetooth AF32 headset functions fine with HSP profile.

Code:

$ pactl list short cards

0       alsa_card.usb-046d_09a1_301C6850-02-U0x46d0x9a1 module-alsa-card.c

1       alsa_card.pci-0000_00_1b.0      module-alsa-card.c

2       bluez_card.00_80_F0_D8_1F_2F    module-bluetooth-device.c

$ pactl list cards

[...]

Card #2

        Name: bluez_card.00_80_F0_D8_1F_2F

        Driver: module-bluetooth-device.c

        Owner Module: 25

        Properties:

                device.description = "KX-TG76"

                device.string = "00:80:F0:D8:1F:2F"

                device.api = "bluez"

                device.class = "sound"

                device.bus = "bluetooth"

                device.form_factor = "phone"

                bluez.path = "/org/bluez/9707/hci0/dev_00_80_F0_D8_1F_2F"

                bluez.class = "0x300208"

                bluez.name = "KX-TG76"

                device.icon_name = "audio-card-bluetooth"

        Profiles:

                hsp: Telephony Duplex (HSP/HFP) (sinks: 1, sources: 1, priority. 20)

                off: Off (sinks: 0, sources: 0, priority. 0)

        Active Profile: off

        Ports:

                phone-output: Phone (priority: 0, latency offset: 0 usec)

                        Part of profile(s): hsp

                phone-input: Phone (priority: 0, latency offset: 0 usec)

                        Part of profile(s): hsp

$ pactl set-card-profile bluez_card.00_80_F0_D8_1F_2F hsp

Failure: Input/Output error

$ pulseaudio --log-level=4

I: [pulseaudio] client.c: Created 10 "Native client (UNIX socket client)"

D: [pulseaudio] protocol-dbus.c: Interface org.PulseAudio.Core1.Client added for object /org/pulseaudio/core1/client10

D: [pulseaudio] protocol-native.c: Protocol version: remote 28, local 28

I: [pulseaudio] protocol-native.c: Got credentials: uid=1000 gid=1000 success=1

D: [pulseaudio] protocol-native.c: SHM possible: yes

D: [pulseaudio] protocol-native.c: Negotiated SHM: yes

D: [pulseaudio] module-augment-properties.c: Looking for .desktop file for pactl

D: [pulseaudio] module-bluetooth-device.c: Acquiring transport /org/bluez/9707/hci0/dev_00_80_F0_D8_1F_2F/fd1

E: [pulseaudio] module-bluetooth-device.c: Failed to acquire transport /org/bluez/9707/hci0/dev_00_80_F0_D8_1F_2F/fd1

I: [pulseaudio] client.c: Freed 10 "pactl"

I: [pulseaudio] protocol-native.c: Connection died.

D: [pulseaudio] protocol-dbus.c: Interface org.PulseAudio.Core1.Client removed from object /org/pulseaudio/core1/client10

$ hcitool con

Connections:

        < ACL 00:80:F0:D8:1F:2F handle 11 state 1 lm SLAVE AUTH ENCRYPT

$ hcitool info 00:80:F0:D8:1F:2F

Requesting information ...

        BD Address:  00:80:F0:D8:1F:2F

        Device Name: KX-TG76

        LMP Version: 2.0 (0x3) LMP Subversion: 0x10b7

        Manufacturer: Cambridge Silicon Radio (10)

        Features: 0xff 0xff 0x8f 0xf8 0x1b 0x18 0x00 0x80

                [3-slot packets] [5-slot packets] [encryption] [slot offset] 

                [timing accuracy] [role switch] [hold mode] [sniff mode] 

                [park state] [RSSI] [channel quality] [SCO link] [HV2 packets] 

                [HV3 packets] [u-law log] [A-law log] [CVSD] [paging scheme] 

                [power control] [transparent SCO] [broadcast encrypt] 

                [enhanced iscan] [interlaced iscan] [interlaced pscan] 

                [inquiry with RSSI] [extended SCO] [EV4 packets] [EV5 packets] 

                [AFH cap. slave] [AFH class. slave] [AFH cap. master] 

                [AFH class. master] [extended features]

Since this bluetooth phone works fine with kernels before 3.12, I wonder if it's the bluetooth module?

Code:

$ diff -y bluetooth_module1 bluetooth_module2

filename:       /lib/modules/3.13-2.slh.5-aptosid-amd64/kerne | filename:       /lib/modules/3.11-4.slh.4-aptosid-amd64/kerne

alias:          net-pf-31                                       alias:          net-pf-31                             

license:        GPL                                             license:        GPL                                   

version:        2.17                                          | version:        2.16                                  

description:    Bluetooth Core ver 2.17                       | description:    Bluetooth Core ver 2.16               

author:         Marcel Holtmann <marcel>           author:         Marcel Holtmann <marcel> 

srcversion:     9F632F858697C2A938BC21E                       | srcversion:     96A133D4306E627B0D0547E               

depends:        rfkill,crc16                                    depends:        rfkill,crc16                          

intree:         Y                                               intree:         Y                                     

vermagic:       3.13-2.slh.5-aptosid-amd64 SMP preempt mod_un | vermagic:       3.11-4.slh.4-aptosid-amd64 SMP preempt mod_un

parm:           disable_esco:Disable eSCO connection creation   parm:           disable_esco:Disable eSCO connection creation

parm:           disable_ertm:Disable enhanced retransmission    parm:           disable_ertm:Disable enhanced retransmission 

                                                              > parm:           enable_hs:Enable High Speed support (bool)

Maybe try another bluetooth adapter?

All times are GMT - 12 Hours

aptosid.com Forum Index » Support Forums » Hardware

Menu

Rootserver Sponsor

Donations

News

Blog