public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sainty <david.sainty@dtsp.co.nz>
To: Stuart Pook <kernel6org@pook.es>
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 12:26:18 +1300	[thread overview]
Message-ID: <48E2B59A.7020600@dtsp.co.nz> (raw)
In-Reply-To: <48E29416.3030402@pook.es>

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! (*)

(* with the minor flaw that if I walk away out of range of my kneetop, 
even when paused, the audio connection is irretrievably broken and I 
need to restart the player)



  reply	other threads:[~2008-09-30 23:26 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 [this message]
2008-10-01 17:30   ` Stuart Pook
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=48E2B59A.7020600@dtsp.co.nz \
    --to=david.sainty@dtsp.co.nz \
    --cc=kernel6org@pook.es \
    --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