From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] btsco and connection problems
Date: Sun, 11 Jun 2006 14:50:04 -0600 [thread overview]
Message-ID: <448C81FC.50509@xmission.com> (raw)
In-Reply-To: <85cea3460606111303r218e088ek21d50709fce3c6df@mail.gmail.com>
Sweta
> [root@lirr ~]# hcitool info 00:07:A4:26:8D:3F
> Requesting information ...
> Can't create connection: Connection timed out
> [root@lirr ~]# btsco 00:07:A4:26:8D:3F
> Error: Failed to connect to SDP server: Function not implemented
> Assuming channel 2
>
> Can't connect RFCOMM channel: Resource temporarily unavailable
something more fundamental is wrong with your setup if you can't get the
rfcomm channel connected or an sdp scan. is the headset in pairing mode
when you are trying this stuff?
make sure /etc/bluetooth/hcid.conf has not been customized, try
restarting the bluez utils, etc. that's the sort of thing I do, but
there are probably more systematic ways of narrowing down the problem.
brad
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-11 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 20:03 [Bluez-devel] btsco and connection problems Sweta Vasudevan
2006-06-11 20:50 ` Brad Midgley [this message]
2006-06-15 3:49 ` Sweta Vasudevan
2006-06-15 20:28 ` Brad Midgley
2006-06-16 17:11 ` David Greaves
2006-06-18 22:59 ` Sweta Vasudevan
2006-06-23 1:40 ` Sweta Vasudevan
-- strict thread matches above, loose matches on Subject: below --
2006-06-10 23:42 Sweta Vasudevan
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=448C81FC.50509@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).