gnome and bluetooth

[alienjon]

Having recently switched over to gnome, I figured that I would give the gnome bluetooth tools a shot. I followed the [ur=http://www.gentoo.org/doc/en/bluetooth-guide.xmll]bluetooth[/url] guide and everything is good until I get to the 'hcitool scan' command. The command runs fine (so long as my phone is allowing devices to search for it) other than one simple fact. The name that hcitool comes up with is the factory name for the phone, not the name that I set it too. This wouldn't be a problem, normally, but later on, when I tried the rfcomm commands, I can connect to the phone, but the I get an 'invalid pin' error and my phone and computer won't connect. I have tried changing the pin (to something simple, like 123456) and then restarting the bluetooth service (I also tried changing the phone name again) but I still get the same problems. The MAC address seems fine, and looks familiar (I did use to use this in both KDE (in which I never got it to work well) as well as in Windows (where it worked marginally better)).

Any suggestions?

[alienjon]

Cmon all, I imagine someone must have bluetooth working with gnome.

[johoe]

working here without any problems. Using bluetooth to connect to my motorola phone and to my TungstenT3. But I'm sorry, I've no idea how to solve your problems.
this is my hcid.conf:

Code: Select all

#
# HCI daemon configuration file.
#

# HCId options
options {
	# Automatically initialize new devices
	autoinit yes;

	# Security Manager mode
	#   none - Security manager disabled
	#   auto - Use local PIN for incoming connections
	#   user - Always ask user for a PIN
	#
	security auto;

	# Pairing mode
	#   none  - Pairing disabled
	#   multi - Allow pairing with already paired devices
	#   once  - Pair once and deny successive attempts
	pairing multi;

	# PIN helper
	pin_helper /etc/bluetooth/pin-helper;

	# D-Bus PIN helper
	#dbus_pin_helper;
}

# Default settings for HCI devices
device {
	# Local device name
	#   %d - device id
	#   %h - host name
	name "BlueZ (%d)";

	# Local device class
	class 0x3e0100;

	# Default packet type
	#pkt_type DH1,DM1,HV1;

	# Inquiry and Page scan
	iscan enable; pscan enable;

	# Default link mode
	#   none   - no specific policy 
	#   accept - always accept incoming connections
	#   master - become master on incoming connections,
	#            deny role switch on outgoing connections
	lm accept, master;

	# Default link policy
	#   none    - no specific policy
	#   rswitch - allow role switch
	#   hold    - allow hold mode
	#   sniff   - allow sniff mode
	#   park    - allow park mode
	lp rswitch,hold,sniff,park;

	# Authentication and Encryption (Security Mode 3)
	#auth enable;
	#encrypt enable;
}

my pin is only 4 characters long. maybe this ...?

regards,
johoe

[alienjon]

Thanks for posting your hcid.conf. There were only two minor differences between yours and mine (I also tried shortening my pin to just 4 characters) but nothing was working. I then tried changing the pin helper to /usr/bin/bluepin and it works. (The only downside is that I have to put the pin in my computer as I want to connect) If anyone knows how to get the other to work, or how to configure bluepin to work without that I would appreciate it. In the meantime I have a quick question. How should I do file transfers in gnome? I see (in 'Applications->System Tools') that there is a 'Bluetooth File Sharing' option, but it just has a little icon pop up in my system tray and clicking on it doesn't do anything.

[johoe]

Glad that it works for you now.
you can send file to your device with: gnome-obex-send (you need gnome-bluetooth installed)

johoe

[alienjon]

Hmm, I get a popup error:

Code: Select all

Unable to connect to remote device.

Here's the terminal output:

Code: Select all

Browsing 00:15:A8:37:34:2D ...
Service Name: OBEX Object Push
Service Description: OBEX Object Push
Service Provider: Cingular
Service RecHandle: 0x10008
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 8
  "OBEX" (0x0008)
Service Class ID List:
  "OBEX Object Push" (0x1105)
** Message: device 00:15:A8:37:34:2D (OBEX Object Push) port 8



** (gnome-obex-send:25696): CRITICAL **: btctl_obexclient_source_new: assertion `channel <= 0' failed

** (gnome-obex-send:25696): WARNING **: Unable to initialize OBEX client source

[Tutumark]

Humm...I've the same error here. No solution around?
Mark

[pytooli]

I used

Code: Select all

rfcomm bind /dev/rfcomm0 [device id] 8

but no results again

[Robu]

Code: Select all

** (gnome-obex-send:25696): CRITICAL **: btctl_obexclient_source_new: assertion `channel <= 0' failed

** (gnome-obex-send:25696): WARNING **: Unable to initialize OBEX client source

This is exactly the same error I get (profile amd64). No solution found by me up to now for gnome-obex send, but I found as a workaround, the following:

Code: Select all

 emerge ussp-push 

It use the RFCOMM channel and then sending from pc to the phone it works through terminal command. Something like:

Code: Select all

ussp-push PHONE_MAC-ADDRESS@PORT_NUMBER FileName MessageFileName

I added the command to a nautilus-script then I send the files to the phone from nautilus with success.
Hope it helps.