Bug#464501: marked as done (eSCO support breaks (SCO?) headsets)

[Moritz Muehlenhoff <jmm@inutil.org>]

reopen 464501
submitter 464501 fbriere@fbriere.net
thanks

On Thu, Dec 18, 2008 at 05:20:55PM -0500, Frédéric Brière wrote:
> On Thu, Dec 18, 2008 at 08:27:07PM +0000, Debian Bug Tracking System wrote:
> > There's not much point in leaving the bug open, then.
> 
> This bug report has evolved a lot since it was opened, as it accumulated
> lots of (possibly unrelated) "my headset does not work" reports.  (Good
> luck following up on those.)
> 
> Its current purpose is to track a specific regression, introduced with
> eSCO support in b6a0dc82.  Namely, the kernel will always attempt to
> establish an eSCO connection if the Bluetooth adapter supports it,
> regardless of any support from the device itself.  This is a problem for
> those of us who are using a cheap old headset with a not-so-old
> Bluetooth adapter.
> 
> (To answer your previous question, this is still present in 2.6.26.  I
> haven't had the time to try .27 yet.)
> 
> Ideally, the kernel would be smart enough to try eSCO only if the
> adapter and device support it.  Or, at the very least, fall back to SCO
> if eSCO doesn't work.
> 
> I'll let you determine whether you prefer to reopen this report, or
> clone it beforehand.  (In the latter case, feel free to use me as its
> submitter.)

Done.

If you find the time plesae check, whether this behaviour persists with
2.6.28 and if that should still be the case, please file a bug at
bugzilla.kernel.org

Cheers,
        Moritz