Hi,
I've been trying to manually connect a PS3 headset using bluez 5.16 without success.
It does work using KDE Bluetooth tools (still based on bluez 4), but as I would like to use it on a
headless box, I need to do it via CLI.
Using bluez 5.16 (both in Fedora 19 and on Arch on a Pi) I can pair the device but when I try to
connect I get
[NEW] Controller 00:15:83:0C:BF:EB localhost.localdomain [default]
[NEW] Device 00:22:A6:16:E3:F0 Wireless Headset
[bluetooth]# list
Controller 00:15:83:0C:BF:EB localhost.localdomain [default]
[bluetooth]# connect 00:22:A6:16:E3:F0
Attempting to connect to 00:22:A6:16:E3:F0
[CHG] Device 00:22:A6:16:E3:F0 Connected: yes
[CHG] Device 00:22:A6:16:E3:F0 Modalias: usb:v12BAp0010d0140
[CHG] Device 00:22:A6:16:E3:F0 Modalias: usb:v12BAp0010d0140
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 00:22:A6:16:E3:F0 Connected: no
on the daemon I can see
bluetoothd[16241]: src/device.c:connect_profiles() /org/bluez/hci0/dev_00_22_A6_16_E3_F0 (all),
client :1.234
bluetoothd[16241]: src/device.c:connect_profiles() Resolving services for
/org/bluez/hci0/dev_00_22_A6_16_E3_F0
bluetoothd[16241]: src/adapter.c:connected_callback() hci0 device 00:22:A6:16:E3:F0 connected eir_len 18
bluetoothd[16241]: src/device.c:search_cb() 00:22:A6:16:E3:F0: No service update
bluetoothd[16241]: src/device.c:device_svc_resolved() /org/bluez/hci0/dev_00_22_A6_16_E3_F0 err 0
bluetoothd[16241]: src/device.c:connect_profiles() /org/bluez/hci0/dev_00_22_A6_16_E3_F0 (all),
client :1.234
bluetoothd[16241]: src/adapter.c:dev_disconnected() Device 00:22:A6:16:E3:F0 disconnected, reason 2
bluetoothd[16241]: src/adapter.c:adapter_remove_connection()
bluetoothd[16241]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr 00:22:A6:16:E3:F0 type 0
status 0xe
bluetoothd[16241]: src/device.c:device_bonding_complete() bonding (nil) status 0x0e
bluetoothd[16241]: src/device.c:device_bonding_failed() status 14
bluetoothd[16241]: src/adapter.c:resume_discovery()
anything else I should be doing to get a connection?
On 26 March 2014 21:14, Andrea <[email protected]> wrote:
> and we know that HSP and HFP have been dropped from Bluez 5
> Could this explain why connection fails?
Yes, this is it.
By the way:
1. Why were those profiles removed?
2. It seems that HSP is not supported :) (and never been?)
http://www.bluez.org/profiles/
--
Pozdrawiam / Best regards
-------------------------------------------------------------------------------------------------------------
Michał Łabędzki, Software Engineer
Tieto Corporation
Product Development Services
http://www.tieto.com / http://www.tieto.pl
---
ASCII: Michal Labedzki
location: Swobodna 1 Street, 50-088 Wrocław, Poland
room: 5.01 (desk next to 5.08)
---
Please note: The information contained in this message may be legally
privileged and confidential and protected from disclosure. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorised use, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to
the message and deleting it from your computer. Thank You.
---
Please consider the environment before printing this e-mail.
---
Tieto Poland spółka z ograniczoną odpowiedzialnością z siedzibą w
Szczecinie, ul. Malczewskiego 26. Zarejestrowana w Sądzie Rejonowym
Szczecin-Centrum w Szczecinie, XIII Wydział Gospodarczy Krajowego
Rejestru Sądowego pod numerem 0000124858. NIP: 8542085557. REGON:
812023656. Kapitał zakładowy: 4 271500 PLN
On 24/03/14 07:24, Michal Labedzki wrote:
> Hello,
>
> Wireshark is able to open both files. More interesting is "blue.log".
> It seems that you want to connect via HSP or HFP (only supported by
> headset). In "blue.log" headset asks (SDP) your bluez about "Handsfree
> Audio Gateway" or "Headset Audio Gateway", but bluez return empty
> records, so they must be disabled.
>
I seem to understand what happens
this is the device info
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
and we know that HSP and HFP have been dropped from Bluez 5
Could this explain why connection fails?
it seems I need to learn about oFono and Pulseaudio
On 24/03/14 07:24, Michal Labedzki wrote:
> Hello,
>
> Wireshark is able to open both files. More interesting is "blue.log".
> It seems that you want to connect via HSP or HFP (only supported by
> headset). In "blue.log" headset asks (SDP) your bluez about "Handsfree
> Audio Gateway" or "Headset Audio Gateway", but bluez return empty
> records, so they must be disabled.
>
sounds plausible, but as I have not touched anything,
they must be disabled by default.
cant find any configuration file that mentions anything similar.
on Arch there is /etc/bluetooth/main.conf but it does not seem to help.
In Fedora 20, not even that.
Do I need some extra package? kernel module? audio bluez plugin?
Something like snd-usb-audio for usb sound cards.
thanks for your help
Andrea
Hello,
Wireshark is able to open both files. More interesting is "blue.log".
It seems that you want to connect via HSP or HFP (only supported by
headset). In "blue.log" headset asks (SDP) your bluez about "Handsfree
Audio Gateway" or "Headset Audio Gateway", but bluez return empty
records, so they must be disabled.
--
Pozdrawiam / Best regards
-------------------------------------------------------------------------------------------------------------
Michał Łabędzki, Software Engineer
Tieto Corporation
Product Development Services
http://www.tieto.com / http://www.tieto.pl
---
ASCII: Michal Labedzki
location: Swobodna 1 Street, 50-088 Wrocław, Poland
room: 5.01 (desk next to 5.08)
---
Please note: The information contained in this message may be legally
privileged and confidential and protected from disclosure. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorised use, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to
the message and deleting it from your computer. Thank You.
---
Please consider the environment before printing this e-mail.
---
Tieto Poland spółka z ograniczoną odpowiedzialnością z siedzibą w
Szczecinie, ul. Malczewskiego 26. Zarejestrowana w Sądzie Rejonowym
Szczecin-Centrum w Szczecinie, XIII Wydział Gospodarczy Krajowego
Rejestru Sądowego pod numerem 0000124858. NIP: 8542085557. REGON:
812023656. Kapitał zakładowy: 4 271500 PLN
On 23/03/14 19:19, Andrea wrote:
> On 21/03/14 21:10, Andrea wrote:
>> Hi,
>>
>
> any sort of traffic log I could provide to help resolving the issue?
I've logged a failed attempt using hcidump and wireshark.
maybe it can be useful
http://utente.xoom.it/depo/scambio/blue.log
http://utente.xoom.it/depo/scambio/blue.pcapng
andrea
On 21/03/14 21:10, Andrea wrote:
> Hi,
>
> I've been trying to manually connect a PS3 headset using bluez 5.16 without success.
> It does work using KDE Bluetooth tools (still based on bluez 4), but as I would like to use it on a
> headless box, I need to do it via CLI.
>
> Using bluez 5.16 (both in Fedora 19 and on Arch on a Pi) I can pair the device but when I try to
> connect I get
>
I think it is a regression of 5.16 vs 4.xxx
I've just installed Fedora 20 (using bluez 5.16) and the KDE Gui bluetooth tools can't connect
either with a very similar log from bluetoothctl
this is the output while I was using the KDE Gui tools.
it pairs well, connects, but the disconnect immediately.
at the end I tried manually froom here, with no success
I don't think the kernel version matters, as it is 3.13.6 in all cases.
any sort of traffic log I could provide to help resolving the issue?
andrea@thinkpad:~$ sudo bluetoothctl
[NEW] Controller 00:15:83:0C:BF:EB thinkpad [default]
[bluetooth]# devices
[CHG] Controller 00:15:83:0C:BF:EB Discovering: yes
[NEW] Device 00:22:A6:16:E3:F0 00-22-A6-16-E3-F0
[CHG] Device 00:22:A6:16:E3:F0 LegacyPairing: no
[CHG] Device 00:22:A6:16:E3:F0 Name: Wireless Headset
[CHG] Device 00:22:A6:16:E3:F0 Alias: Wireless Headset
[CHG] Device 00:22:A6:16:E3:F0 LegacyPairing: yes
[CHG] Controller 00:15:83:0C:BF:EB Discovering: no
[CHG] Device 00:22:A6:16:E3:F0 Connected: yes
[CHG] Device 00:22:A6:16:E3:F0 Modalias: usb:v12BAp0010d0140
[CHG] Device 00:22:A6:16:E3:F0 Modalias: usb:v12BAp0010d0140
[CHG] Device 00:22:A6:16:E3:F0 UUIDs has unsupported type
[CHG] Device 00:22:A6:16:E3:F0 Paired: yes
[CHG] Device 00:22:A6:16:E3:F0 Trusted: yes
[CHG] Device 00:22:A6:16:E3:F0 Connected: no
[CHG] Device 00:22:A6:16:E3:F0 Connected: yes
[CHG] Device 00:22:A6:16:E3:F0 Modalias: usb:v12BAp0010d0140
[CHG] Device 00:22:A6:16:E3:F0 Modalias: usb:v12BAp0010d0140
[CHG] Device 00:22:A6:16:E3:F0 Connected: no
[bluetooth]# connect 00:22:A6:16:E3:F0
Attempting to connect to 00:22:A6:16:E3:F0
[CHG] Device 00:22:A6:16:E3:F0 Connected: yes
[CHG] Device 00:22:A6:16:E3:F0 Modalias: usb:v12BAp0010d0140
[CHG] Device 00:22:A6:16:E3:F0 Modalias: usb:v12BAp0010d0140
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 00:22:A6:16:E3:F0 Connected: no
[CHG] Device 00:22:A6:16:E3:F0 Alias: Wireless Headset
[CHG] Device 00:22:A6:16:E3:F0 Connected: yes
[CHG] Device 00:22:A6:16:E3:F0 Connected: no