Talk:Mobile Phone/Bluetooth

From Gentoo Linux Wiki

[edit] Dependencies of gnome-bluetooth

The How-To doesn't work for me anymore since updating baselayout and sysinitv. And now gnome-bluetooth doesn't have bluez-utils, which results in a missing bluetooth-init-script and missing hci-tools. Maybe you should include those in the emerge-process.

[edit] Include KDE Setup

The KDE setup if very similar and works fine here. Do you mind me updating a little to include that information?
Tom 11:30, 28 Aug 2004 (GMT)

[edit] Splitting off core Bluetooth setup

I'm building a tutorial on using Bluetooth with Palms or PocketPCs. It makes little sense to recreate the sections on installing and configuring Bluetooth. What do you think about splitting off setup of Bluetooth itself into a seperate document? (I'll start work on one and edit this comment to match.)

--Srobertson 19:28, 14 Sep 2004 (GMT)

[edit] Troubles with pairing

Sorry for my english.I can't pair devices.When i'm try

#rfcomm connect 0 00:0E:07:42:ED:B2

phone show me enter dialog,i'm entering pin..and see that in console

#rfcomm connect 0 00:0E:07:42:ED:B2
Can't connect RFCOMM socket: Connection refused

Here is my /etc/bluetooth/pin

#!/bin/bash
echo "PIN:1234"

What's wrong?

in your case /etc/bluetooth/pin has to be simply

1234

and of course /etc/bluetooth/rfcomm.conf has to be configured properly

I have had the same problem with my T610. Then I deleted the entry of my computer in the mobile. The next step was searching for my computer and telling the phone the pin. And that's all. It works again.

I hope I could help.

[edit] gnome-bluetooth not working w/ >=gnome-2.10?

I was wondering if anyone had any luck getting gnome-bluetooth working with gnome-2.10? I can get gnome-bluetooth-manager to scan and find my phone, but I can't do anything after that (clicking the phone and going to properties does nothing at all). Also, when I start gnome-obex-server I get:

** (gnome-obex-server:14193): WARNING **: OBEX server register error: -94

** (gnome-obex-server:14193): WARNING **: Unable to initialize OBEX source

** (gnome-obex-server:14193): WARNING **: Couldn't initialise OBEX listener

Also, the bluetooth:/// uri scheme in nautilus doesn't seem to work either. Does anyone else have this problem? Is it working for anyone else in gnome-2.10?

I see a similar thing, but my OBEX server register error is -1.

[Update by jcb on Aug, 8th 2005]: "bluetooth:///" is not a valid location (my nautilus says) and my gnome-bluetooth-manager fails to startup due to "gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed" followed by the corresponding python traceback.

[Updated by hm on Aug, 12th 2005]: "bluetooth:///" is not a valid location (my nautilus says) and my gnome-bluetooth-manager fails to startup (output follows):

Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/gnomebt/manager.py", line 275, in ?
    BTManager ().main ()
  File "/usr/lib/python2.3/site-packages/gnomebt/manager.py", line 78, in __init__
    self.setup_gui ()
  File "/usr/lib/python2.3/site-packages/gnomebt/manager.py", line 143, in setup_gui
    gnome.ui.PREFERENCES_NEVER)
TypeError: gtk.HBox.__init__() takes at most 2 arguments (3 given)

Is it a conflict between pygtk and gnome-bluetooth versions?

Fixed in 0.5.1-r2

My 0.01euro trick for gnome 2.10:

1. Start the "Bluetooth File Sharing" utility
2. add a launcher in your panel and put "gnome-obex-send %s" in the "command" field
3. drag'n'drop your file in the freshly made icon on your panel
4. enjoy ;)

Update: The command is "gnome-obex-send %f" for gnome 2.18.

Fix: For this to work, the gnome-vfs-obexftp package needs to be installed. As of 6 Oct 2007 this is not yet in Portage, but an ebuild is available attached to bug #159920.

[edit] Addition regarding > udev-056

The line for /etc/udev/rules.d/10-local.rules did not work for me; in fact i couldnt even connect as root with it. The solution (on my system) was to remove the 'bluetooth/' from the NAME= directive, like this:

KERNEL="rfcomm[0-9]*", NAME="%k", GROUP="dialout", MODE="0660"

perhaps this is because i dont have a /dev/bluetooth directory. just guessing. hope this is helpful.

[edit] L2PING

I googled all over the net, and while I see lots and lots of different guides telling me how to get bluetooth working, and a lot of them refer to gentoo (it's working already, that's not what I wanted to do, grr) none of them ever focus on one tiny bit.

This example shows how to set up rfcomm devices in udev, however, l2cap protocol is not rfcomm, or at least, doesn't seem to be. :) I want to be able to l2ping a phone while not being root, by beloging to a bluetooth group.

Yes, I can probably do this with sudo.

However, that's hardly the right solution, is it?

[edit] PIN helper

I noticed with the default installation these messages in syslog:

hcid[21819]: pin_code_request (sba=00:10:60:D0:38:A0, dba=00:16:4E:0C:F6:60)
hcid[21880]: PIN helper exited abnormally with code 11

It appears that the default pin helper crashed shortly after being started. I solved it by enabling KDE's PIN helper application:

        # PIN helper
        # JPH: pin helper replaced because the bluez pinhelper crashes.
        # pin_helper /usr/bin/bluepin;
        pin_helper /usr/lib/kdebluetooth/kbluepin;