Re: Please help ... How can I connect to a bluetooth headset without pin_helper?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I finally found a solution, so - answering my own question:

Apparently you can't get this to work with the rpm-files only. You need to download the source code (e.g. bluez-utils-3.9.tar.gz), inside this archive find the "daemon" directory, and compile the program "passkey-agent". Please note that this program is *not* installed if you do "configure" and "make install" in the base directory only.

This is supposed to run as a daemon (in the background) and can provide the pin code, when the headset asks for it. So I have made this small script to get things properly working:

#!/bin/sh
/sbin/modprobe snd_bt_sco
/usr/sbin/hcid
passkey-agent --default "0000" &    # "0000" is the pin code for the headset
btsco 00:00:00:00:00:00 &    # Bluetooth address of headset

snd_bt_sco and btsco are from Bluetooth alsa (http://sourceforge.net/project/showfiles.php?group_id=116589)

/Jesper


Jesper Holck wrote:
I have been working on this far too many hours without luck ...

I want to connect my FC6 installation (KDE) with my bluetooth headset,
using a bluetooth dongle. The dongle works nicely, I can scan for and
find the headset, but I can't pair with or connect to it.

Older versions of /etc/bluetooth/hcid.conf had a line, specifying the
pin_helper to use, but apparently this is not allowed with the present
version. If I try this, I get an "Unknown option 'pin_helper' line 27"
error message.

When I try to connect with the headset using
  hciconfig cc 00:11:22:33:44:55
I get a line in /var/log/messages saying something like
  pin_code_request (sba=55:44:33:22:11:00, dba=00:11:22:33:44:55)
but nothing comes up, asking for the pin code...

I have tried specifying
  passkey "0000";
in the options-part of /etc/bluetooth/hcid.conf, but with no success.

With the commander script kbtsco
(http://www.kde-apps.org/content/show.php?content=45427), my experience
has been even more frustrating. I have in fact succeeded to establish a
connection two times (out of something like 50 attempts), but I have no
clue as to when it works and when it fails.

I use bluez-utils-3.7-1, bluez-libs-3.7-2, and bluez-gnome-0.6-1.fc6

Any help will be much appreciated!

Jesper, Denmark



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux