From: "Nicholas A. Preyss" <nalp@gmx.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Problems connecting to Nokia 6310I phone.
Date: Mon, 31 May 2004 13:54:24 +0200 [thread overview]
Message-ID: <20040531115424.GA24449@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0405311108560.10172@sebagqbbe.gwsvfure.pb.hx>
On 0, Toby Fisher <toby@tjfisher.co.uk> wrote:
> On Mon, 31 May 2004, Timothy Murphy wrote:
> > Do you have
> > # CONFIG_BT_HCIUSB_SCO is not set
> > in .config (or /proc/config.gz) ?
> > On my machine (a Sony C1VFK Picturebook)
> > I had more or less your problems when this was set.
>
> The problem here is that I have a usb bluetooth device, so according to
> the kernel help I need this option, so yes, I do have it.
You need the HCI_USB SCO option for audio transfer, only. For example if
you use the Headset or Handsfree profile. For data transfer there is no
need for SCO support. You are using RFCOMM which uses ACL links.
And >= 2.6.6-mh1 there shouldn't be any problems with the SCO
support activated.
Maybe you can run hcidump while your problem appears and provide here
the log.
nicholas
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-05-31 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 21:25 [Bluez-users] Problems connecting to Nokia 6310I phone Toby Fisher
2004-05-31 1:13 ` Timothy Murphy
2004-05-31 4:11 ` Andreas Gaufer
2004-05-31 10:09 ` Toby Fisher
2004-05-31 11:54 ` Nicholas A. Preyss [this message]
2004-05-31 13:24 ` Toby Fisher
2004-05-31 14:10 ` Nicholas A. Preyss
2004-06-01 1:05 ` Toby Fisher
2004-06-01 12:13 ` Nicholas A. Preyss
2004-05-31 13:53 ` Timothy Murphy
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=20040531115424.GA24449@gmx.net \
--to=nalp@gmx.net \
--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