public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Bedot <littletux@zarb.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] HT820, capture and  eSCO
Date: Sat, 26 Jan 2008 10:01:29 +0100	[thread overview]
Message-ID: <1201338089.22866.14.camel@littletux> (raw)
In-Reply-To: <1201336771.22866.7.camel@littletux>


On sam, 2008-01-26 at 09:39 +0100, Guillaume Bedot wrote:
> Hello,
> 
> I have issues using "voice"/HSP/HFP profiles with this headset and
> latest kernels/bluez cvs.
> 
> It seems it tries to use extended SCO when it shouldn't...
> 
> hcitool info xx:xx:xx:xx:xx:xx
> Requesting information ...
> 	BD Address:  xx:xx:xx:xx:xx:xx
> 	Device Name: Motorola HT820
> 	LMP Version: 2.0 (0x3) LMP Subversion: 0xa41
> 	Manufacturer: Cambridge Silicon Radio (10)
> 	Features: 0xff 0xff 0x8b 0x78 0x18 0x18 0x00 0x80
> 		<3-slot packets> <5-slot packets> <encryption> <slot offset> 
> 		<timing accuracy> <role switch> <hold mode> <sniff mode> 
> 		<park state> <RSSI> <channel quality> <SCO link> <HV2 packets> 
> 		<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme> 
> 		<transparent SCO> <broadcast encrypt> <enhanced iscan> 
> 		<interlaced iscan> <interlaced pscan> <inquiry with RSSI> 
> 		<AFH cap. slave> <AFH class. slave> <AFH cap. master> 
> 		<AFH class. master> <extended features> 

If it can help, I noticed there are a lot of these messages in syslog :

Jan 26 07:52:05 littletux kernel: hci_scodata_packet: hci0 SCO packet
for unknown connection handle 1

And with "hifi" profile, the headset playback works although it seems to
use eSCO too :

hcitool con
Connections:
	> ACL xx:xx:xx:xx:xx:xx handle 11 state 1 lm SLAVE AUTH ENCRYPT SECURE 
	< eSCO xx:xx:xx:xx:xx:xx handle 0 state 8 lm SLAVE 

I'm not sure what the problem is anymore...

Best regards,

Guillaume B.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-01-26  9:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26  8:39 [Bluez-devel] HT820, capture and eSCO Guillaume Bedot
2008-01-26  9:01 ` Guillaume Bedot [this message]
2008-01-26 10:04   ` Guillaume Bedot
2008-01-28  8:43     ` Guillaume Bedot
2008-01-28 14:52       ` [Bluez-devel] [PATCH] " Guillaume Bedot
2008-01-28 17:26         ` Guillaume Bedot

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=1201338089.22866.14.camel@littletux \
    --to=littletux@zarb.org \
    --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