M. Holtmann:
'this is from an odd Debian installation.'
What is? I use Slackware 12 and bluez 3.25.
'Kill all these processes and simply log into the GNOME or KDE
desktop and use their Bluetooth applet.'
These require X, which I don't use except under duress. I
just want to listen to files on my wireless headset.
russell bell
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
> -> 'Kill all these processes and simply log into the GNOME or KDE
> -> desktop and use their Bluetooth applet.'
> -> These require X, which I don't use except under duress. I
> -> just want to listen to files on my wireless headset.
>
> Same here, X isn't mandatory, only if you use a graphical bluetooth tool in
> GNOME or KDE, which I don't. The bluez-utils command line tools work fine for
> me. There's two which I use for my headset. I posted a full description of it
> a few issues back, but the pass/PIN part consists of starting
>
> passkey-agent --default <PIN> <bt address of remote device> &
> auth-agent &
I was of the impression that passkey-agent and auth-agent were
unsupported/sample programs. Am I correct?
As far as I can tell, they are undocumented, neither in the tarball, nor in
the wiki (aside from a few brief mentions)
I don't have a full build system up right now, but judging from the various
Makefile.in files in the tarball, it appears they are not built by default.
Debian does not distribute them-- does any distribution?
When I set up my bluetooth headphones back in December, the only way I could
figure out to do it was to switch window managers to something compatible with
the gnome bluetooth-applet. I'd be very happy to hear that there is now a
supported command-line app for this.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
> the other side, computer to device. I believe that's 'hcitool cc <address>'
> then 'hcitool auth <address>' but my headset doesn't seem to like to operate
> this way and wants to disconnect quickly due to not being used for sound.
>
If I'm not wrong it's not your headset the one that closes the
connection, but rather the kernel.
Solution:
ADDR=<SOMETHING> hcitootl cc $ADDR; hcitool auth $ADDR
Still not the preferred way but it works.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
On Fri, 8 Feb 2008, Russell A. Bell wrote:
-> M. Holtmann:
-> 'this is from an odd Debian installation.'
-> What is? I use Slackware 12 and bluez 3.25.
You didn't quote the output he was likely refering to:
>> 20945 tty6 S 0:00 /usr/local/lib/bluetooth/add-passkey 00:13:17:DD:D0:86
>>
>> is in the process list. Does this mean that add-passkey isn't
>> working?
> this is from an odd Debian installation.
"add-passkey" isn't a tool in bluez-utils 3.25. Where ever it came from, I
think he meant not to use it. Years ago I used Slackware, and it never
installed stuff in /usr/local. Unless it underwent a fundimental change (and
that's hard to image if you know how Patrick is) that looks like a 3rd-party
or user add-on.
> Using that is a bad thing. Kill all these processes and simply log into the
> GNOME or KDE desktop and use their Bluetooth applet.
-> 'Kill all these processes and simply log into the GNOME or KDE
-> desktop and use their Bluetooth applet.'
-> These require X, which I don't use except under duress. I
-> just want to listen to files on my wireless headset.
Same here, X isn't mandatory, only if you use a graphical bluetooth tool in
GNOME or KDE, which I don't. The bluez-utils command line tools work fine for
me. There's two which I use for my headset. I posted a full description of it
a few issues back, but the pass/PIN part consists of starting
passkey-agent --default <PIN> <bt address of remote device> &
auth-agent &
after sdpd & hcid are up, but before you try and use the headset. After that,
turn on the headset. Many look for a audio service to pair with. Mine does. On
the Jabra I use, there is a button on the side. Pressing it causes it to try
to pair with the computer. At that time, passkey-agent and auth-agent answer,
and output to the console that they did get a request. After a few seconds,
you should see the headset with 'hcitool con '. If you don't send sound, it
may disconnect after some time. If it does, pressing again re-starts the
process. If yours doesn't have such a button/setup, you could try to pair from
the other side, computer to device. I believe that's 'hcitool cc <address>'
then 'hcitool auth <address>' but my headset doesn't seem to like to operate
this way and wants to disconnect quickly due to not being used for sound.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users