From: Stuart Pook <kernel6org@pook.es>
To: David Sainty <david.sainty@dtsp.co.nz>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez-4.9 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect: Operation not permitted
Date: Wed, 01 Oct 2008 19:30:39 +0200 [thread overview]
Message-ID: <48E3B3BF.6070205@pook.es> (raw)
In-Reply-To: <48E2B59A.7020600@dtsp.co.nz>
On 01/10/08 01:26, David Sainty wrote:
> Stuart Pook wrote:
>> Er, what headsets do work? Please let me know. The Jabra JX10 "features
>> Bluetooth 2.0 and e-SCO for improved audio quality and MultiPoint
>> capability for connecting to 2 devices at once". Could that be
>> what is causing the problem?
> I use a Sony DR-BT20NX stereo headset, with both my kneetop and my phone
> attached (they don't play at once, but the phone can interrupt the audio
> playback). It works great! (*)
I'd like to use my headset to do VoIP via my PC. Do you do that or is
the communication just from your PC to the headset?
I wonder if my problems are due to my old dongle. I have an old
Bluetooth 1.2 Linksys USBBT100 USB dongle. Perhaps it has problems
talking to my Bluetooth 2.0 headset.
I would like a class I Bluetooth 2.x USB dongle. Does anyone have any
suggestions? I could buy a Belkin F8T012fr1 (class I & v2.0) or a Belkin
F8T017ng (class I & v2.1). http://www.bluez.org/ mentions the F8T016 and
its required quirks. I suppose that the F8T017ng is just the class I
version. Would it require the same quirks I wonder?
Stuart
next prev parent reply other threads:[~2008-10-01 17:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 21:03 bluez-4.9 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect: Operation not permitted Stuart Pook
2008-09-30 23:26 ` David Sainty
2008-10-01 17:30 ` Stuart Pook [this message]
2008-10-04 3:47 ` Luiz Augusto von Dentz
2008-10-04 11:25 ` Stuart Pook
2008-10-04 11:51 ` Marcel Holtmann
2008-10-04 23:24 ` bluez-4.11 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect(): Connection timed out (110) Stuart Pook
2008-10-05 17:50 ` Johan Hedberg
2008-10-05 19:17 ` Stuart Pook
2008-10-05 20:07 ` bluez-4.11 + 2.6.27-rc8 + SCO headset -> Invalid read of size 4 Stuart Pook
2008-10-06 8:47 ` Johan Hedberg
2008-10-06 10:52 ` Johan Hedberg
2008-10-06 18:38 ` Stuart Pook
2008-10-06 19:56 ` Stuart Pook
2008-10-06 20:31 ` Johan Hedberg
2008-10-06 20:56 ` bluez/git + 2.6.27-rc8 + SCO headset -> SIGSEGV Stuart Pook
2008-10-06 21:03 ` Marcel Holtmann
2008-10-06 21:10 ` Stuart Pook
2008-10-06 21:21 ` Marcel Holtmann
2008-10-06 22:40 ` bluez/git + 2.6.27-rc8 + bluetoothd " Stuart Pook
2008-10-07 5:34 ` Johan Hedberg
2008-12-06 12:15 ` bluez-4.22 + twinkle -> Unable to lock headset Stuart Pook
2008-12-08 18:42 ` Luiz Augusto von Dentz
2008-12-09 12:23 ` sreevani medhahal
2008-10-06 20:39 ` bluez/git + 2.6.27-rc8 + Belkin F8T017 -> Can't read class of adapter Stuart Pook
2008-10-06 20:45 ` Marcel Holtmann
2008-10-06 21:55 ` Stuart Pook
2008-10-06 22:38 ` Marcel Holtmann
2008-10-06 23:17 ` bluez/git + 2.6.27-rc8 + Belkin F8T017 -> works with reset=1 Stuart Pook
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=48E3B3BF.6070205@pook.es \
--to=kernel6org@pook.es \
--cc=david.sainty@dtsp.co.nz \
--cc=linux-bluetooth@vger.kernel.org \
/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