From: attaboyu <attaboyu@163.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluetooth Headset (hstest, rfcomm and sco connected but no sound)
Date: Mon, 4 Aug 2008 15:55:04 +0800 (CST) [thread overview]
Message-ID: <33494690.546031217836504913.JavaMail.coremail@bj163app19.163.com> (raw)
In-Reply-To: <16515303.641251217832066401.JavaMail.coremail@bj163app113.163.com>
[-- Attachment #1.1: Type: text/plain, Size: 1919 bytes --]
and SCO route below:
[root@root bin]$../sbin/hciconfig hci0 revision
go...
hci0: Type: UART
BD Address: 00:06:6E:05:05:05 ACL MTU: 310:10 SCO MTU: 64:8
Unified 21e
Chip version: BlueCore4-ROM
Max key size: 128 bit
SCO mapping: PCM
--
Best Regards
------------
Tony
在2008-08-04,attaboyu <attaboyu@163.com> 写道:
hi everyone
I'm experimenting with the i-tech BlueBAND headset with bluez, this headset support HS,HF,A2DP and AVRCP profile, But for me, I only want to test the MONO for telephoning. it doesnt work well now.
toolchain: kernel 2.6.10, bluez-libs/utils-3.12, CSR BC4 UART interface
(the version of the toolchain is old, but I must work on that)
I will definitely test HeadSet profile, so btsco/snd-bt-sco are not included. and I use the hstest in bluez-utils. hcid,hciattach,sdpd are always work well.
when send audio to headset:
[root@root bin]$hstest play 1.wav 00:0D:3C:E8:1A:AC 2 &
Voice setting: 0x0060
RFCOMM channel connected
SCO audio channel connected (handle 45, mtu 64)
AT+VGS=11
AT+CKPD=200
AT+CKPD=200
AT+CKPD=200
AT+VGS=12
AT+VGS=11
AT+VGS=10
AT+VGS=11
AT+VGS=12
AT+CKPD=200
Here the headset beeps (it does that everytime a connection is initiated) and I can hear only some noise through it. By pressing one of the buttons on the headset I even see the AT-comands which are submitteted via the rfcomm channel. But no audio. A hcidump during the connection procedure shows just a normal looking bunch of hci and acl commands and events, but no sco packets whatsoever.
here the SCO is connected
[root@root bin]$hcitool con
Connections:
< SCO 00:0D:3C:E8:1A:AC handle 45 state 1 lm SLAVE
< ACL 00:0D:3C:E8:1A:AC handle 43 state 1 lm MASTER ENCRYPT
Am I doing something wrong or missing a step?
Thanks for your help and best regards
Tony
[-- Attachment #1.2: Type: text/html, Size: 2695 bytes --]
[-- Attachment #2: Type: text/plain, Size: 363 bytes --]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-08-04 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 6:41 [Bluez-users] Bluetooth Headset (Only for MONO test) attaboyu
2008-08-04 7:55 ` attaboyu [this message]
2008-08-04 9:30 ` [Bluez-users] Bluetooth Headset (hstest, rfcomm and sco connected but no sound) attaboyu
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=33494690.546031217836504913.JavaMail.coremail@bj163app19.163.com \
--to=attaboyu@163.com \
--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