Hi,

I rarely use bluetooth, anyway,
in the past, I've used it, successfully,
via command-line.

How can I do the pairing, via command line,
on a Kubuntu Intrepid Ibex?

In the past I did the pairing with:
passkey-agent --default /etc/bluetooth/bluepin

Nowaday it is not possible to act in this way yet.


I read here:
https://help.ubuntu.com/community/BluetoothDialup

In this tutorial the new procedure seems to be the following:

sudo hcitool cc your-phone-mac-address

then:

sudo hcitool cc your-phone-mac-address

Unfortunately the first command seems to be successfull
(gives no output), but the second command told me the device is not connected


So how can I do the pairing, via command line,
on a Kubuntu Intrepid Ibex?


If I had more RAM I could use kbluetooth or some GUI,
but unfortunately I need to do the pairing via command line,
because of the low RAM machine I'm on.


Please help,


deadlinx

JUuuuuuuuuuuh,

is there anybody reading?

Don't say me there's nobody pairing bluetooth,
via command line in Intrepid Ibex,

so, please, help.


deadlinx

Don't say me everybody uses only GUI tools,
I can't belive it,

so please, give an idea and so on,


deadlinx

This forum is not like the Slackware forum. Over there you would have about a dozen answers in a given hour.

When you figure out the command line for Bluetooth, can you post it here. I have a headset and mouse that constantly need reconnecting

thanks

hcitool scan (to find out bt devices)

This command to do the pairing using a pre-edited file in /etc/bluetooth:

passkey-agent --default /etc/bluetooth/bluepin



Now consider that passkey-agent command does not exist in Intrepid anymore
and I've written something about what I've read online that, anyway, doesn't work.


In the past, after pairing, I've no problem of sort in transferring files and so on. I used obexftp etc but I think it has no importance 'cause the problem is "how to pair nowaday" and nothing more.


deadlinx

I wonder if that's why the right click on file Send to with bluettoth no longer works. I've found that right clickinging the bluetooth applet icon offers a send to that does work. I upgraded from 8.04 and all my pared buetooth devices were carried forward.

Uhm,
ok, I know GUI is cool,
but what about answering my question?

deadlinx

I gave some insite that might help you find an answer. Bluetooth is somehow different in 8.10. Nasty people don't get help.

Hi,


---Maybe something I've written is not so clear, so:---


-1- In the past I've used bluetooth successfully;

-2- I've used bluetooth, via command line, successfully.




---In the end the reason I'm writing here is the following:---


On Intrepid Ibex, the procedure I was used to use, (passkey-agent...)
seems to be *no more available* these leads us, obviuosly,
to the conclusion something have been changed.






----> @ Perry <--------------------------


Going back to the text of my first post:
I said, I've surfed the web looking for
answers and I've found people using:

sudo hcitool cc myPhoneMacAddress

to pair, now, their devices,
but when I use it there's *no output*,
so, everything seems to be succefull and,
I go forward with the command:

sudo hcitool auth myPhoneMacAddress


unfortunately this gives me the output:
"Device not connected"...so, probably,
the first command *was not* successfull.




-----> @ Fragos <-------------------


I knew Intrepid Ibex is different,
in BT usage,
than previous Ubuntu releases,
this is the reason of my first post,
the question is:"how about solution..?"





---The problem is:---

"How can I do the BT pairing,
via-CLI, successfully,
on Intrepid Ibex?"



---The problem is not:---

-1- how it works via GUI (I know, but low ram...)

-2- how it worked, in the past (I know, I've used it...)

-3- everything not mentioned in "The problem is" section






deadlinx




P.S.
If there's something to clear,
please ask me about it

Hi,


it seems to be
a known problem
with no solution
...uff...
too many bugs
in this release.

I've been trying to do the same thing via fedora 9, and now fedora 10. Same basic problems... the 'hcitool cc' is working, though, the connection just fails immediately. Try this and you'll see:

hcitool cc <bdaddr>; hcitool con

(wait 3 seconds)

hcitool con


It looks like the connection gets established, but then immediately dies. I've been playing with dbus-send and the bluetoothd dbus interface, but I haven't been able to work out a better solution.

Gnome's bluetooth-applet seems to work, which means they must be doing things differently than hcitool. Maybe if we can work out how bluetooth-applet does it, we can craft a CLI script that uses dbus-send to achieve the same result.

Hi,


before replying,
I'd like to thank you
for your competent post!








This induces me to suppose
it's a BlueZ bug.








I don't use, now, Gnome, anyway
I totally agree with you.

I tried kbtobexclient and
it seems to bypass the problem
binding rfcomm on channel 5,
so it works (without asking
for a pairing password!!).

Unfortunately if I try to,
manually, bind rfcomm on
channel 5, it asks for
a password, but it doesn't
use nor the default one, nor
the one in pin or bluepin
file in /etc/bluetooth,
so, in the end, it isn't
able to do the pairing.

:-(



deadlinx

kbtobexclient overrides
password requirement,
but I don't, exactely,
know how it does,
anyway I'm sure the
solution is
"behind the corner"

On further inspection, bluez-4.x is just *weird*... /etc/bluetooth/main.conf is a completely different configuration file, and if there's a place for a default pin, it doesn't seem to be documented.

In addition, gnome's bluetooth-applet *doesn't* work in f10. I jumped the gun on that one. So now, no bluetooth at all for me, even with the gui (and I agree with your approach - I would far prefer to stick with the command line).

I'll continue experimenting with it as time allows. If I discover anything, I'll post it here.