public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: attaboyu <attaboyu@163.com>
To: bluez-users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] noisey while run hstest
Date: Thu, 28 Aug 2008 17:08:54 +0800 (CST)	[thread overview]
Message-ID: <31384302.881251219914534417.JavaMail.coremail@bj163app113.163.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1917 bytes --]

 hi all

hstest is not working right, please let me break it down.

My platform: ARM, kernel-2.6.18, bluez-utils/libs-3.30

#hstest play angel44k8b.wav 00:0D:3C:E8:1A:AC 2     
Voice setting: 0x0060
RFCOMM channel connected
SCO audio channel connected (handle 45, mtu 64)
AT+VGS=12

Though the rfcomm and SCO are really connected. their is no sound but noise output from headset. here are some useful information list below.

#hcitool conn
Connections:
        < SCO 00:0D:3C:E8:1A:AC handle 46 state 1 lm SLAVE 
        < ACL 00:0D:3C:E8:1A:AC handle 43 state 1 lm MASTER ENCRYPT 

#hciconfig hci0 revision
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:  HCI

# hcitool info 00:0D:3C:E8:1A:AC
Requesting information ...
        BD Address:  00:0D:3C:E8:1A:AC
        Device Name: i.Tech BlueBAND R
        LMP Version: 2.0 (0x3) LMP Subversion: 0xd55
        Manufacturer: Cambridge Silicon Radio (10)
        Features: 0xff 0xff 0x8f 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> 
                <power control> <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> 

 
above all, I still can see some SCO packet through hcidump, but i cant here the right sound.

 
what's the problem of this and how to solve it?
Thanks in advance!

 

--

 Best Regards
 ------------
 Tony

[-- Attachment #1.2: Type: text/html, Size: 3447 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

             reply	other threads:[~2008-08-28  9:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  9:08 attaboyu [this message]
2008-08-30  9:09 ` [Bluez-users] noisey while run hstest Marcel Holtmann

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=31384302.881251219914534417.JavaMail.coremail@bj163app113.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