Linux bluetooth development
 help / color / mirror / Atom feed
From: andreas knuth <andreas.knuth@daimlerchrysler.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: BlueZ, Linux and Windows
Date: Tue, 28 Jun 2005 16:08:29 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050628T180644-282@post.gmane.org> (raw)
In-Reply-To: 20050627080102.85B8E1EA336@mrelay1.st2.lyceu.net


> 
> Hi Andreas
> 
> I have review all information in Bluez home page and the one provided by
> you. Most of it is outdated... I haven't managed to get it into work. I
> think I'm missing some basic step... Let me explain you what I have done...
> - Install Fedora 4 (gnome-bluetooth, gnome-bluetooth-libs, bluez-hcidump,
> bluez-pin, bluez-utils, bluez-libs included)
> - hciconfig hci0 up
> - hciconfig (shows the device up and running)
> - hitool scan
> - mknod /dev/rfcomm0 c 216 0
> - sdptool browse <addr>
> - modify /etc/Bluetooth/rfcomm.conf
> 	Rfcomm0 { 	bind yes;
> 			device <addr>;
> 			channel 1;
> 			comment "FC4-BT";
> 		  }
> - Create file: /etc/bluetooth/mypin;
> 	#!bin /bash
> 	echo "PIN:1111"
> - In /etc/Bluetooth/hcid.conf
> 	pin_helper /etc/Bluetooth/my-pin
> 
> - hcid -f /etc/Bluetooth/hcid.conf (to reload file)
> - rfcomm connect /dev/rfcomm0 <addr> 1

Hi Esther 

anyhow you should play a little bit with "hcidump -X" for for getting in touch 
with the bluetooth stack communication.

When you would like to connect to another device then you normally would like 
to use (connect to) a service (on that device). For reaching this try to read 
out the service database of the other device (e.g. sdptool search ...). with 
this information you could select the service you would like to connect (on the 
other device). <= e.g. take the corresponding channel on the other device and 
connect to them.

Which address did you used? What is behind the channel 1? Did you checked the 
sdp database on the other device??
Does your hcidump trace shows a successful PIN delivering to the BT-chip (on 
the linux pc)?


When you try to connect your phone (e.g. in the context of sending vcards)to a 
clean bluetooth linux-pc then this will fail beause of missing "active" sdp-
records (eg. OPUSH, HF) with the specific channel number Y, a listening rfcommX 
socket on channel Y and some kind of server functionality (which takes the 
vcard) which will be called from rfcommX.  


Regards Andreas






-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-06-28 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20 15:20 [Bluez-users] BlueZ, Linux and Windows Esther Lopez
2005-06-24 15:03 ` [Bluez-users] " andreas knuth
2005-06-27  8:01   ` Esther Lopez
2005-06-28 16:08     ` andreas knuth [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20050628T180644-282@post.gmane.org \
    --to=andreas.knuth@daimlerchrysler.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox