linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Winston <spwinston@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] btsco headset almost works
Date: Mon, 14 Nov 2005 04:34:58 -0600	[thread overview]
Message-ID: <1131964498.3323.77.camel@Linux.localdoman.com> (raw)

I'm trying to get btsco to work with my headset.  Thus far, I've managed
to solve my first problem of having to reinstall ALSA libs; got
everything to compile and run fine.  btsco even starts and looks to be
running correctly.  HCIDUMP shows it connects correctly.
When I go to play a sound file, the device makes a distinctive sound
(incoming call style sound (wav file being played I guess corresponds to
the same sound)) I can hear the speaker in the headset turn on.  When I
stop playing a sound, the speaker turns off.  However, no sound is
actually played.


Anyone have a suggestion for what to try next?  Thanks in advance for
any help.

I have a motorola HS820 and a CompUSA USB Bluetooth Adapter
hciconfig -a
hci0:   Type: USB
        BD Address: 00:10:60:AE:74:1E ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN
        RX bytes:14130 acl:314 sco:0 events:790 errors:0
        TX bytes:8555 acl:307 sco:0 commands:244 errors:0
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'CW Service'
        Class: 0x500204
        Service Classes:
        Device Class: Phone, Cellular
        HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver:
0x309
        Manufacturer: Broadcom Corporation (15)

hcitool info 00:07:A4:47:B0:1D
Requesting information ...
        BD Address:  00:07:A4:47:B0:1D
        Device Name: Motorola HS820
        LMP Version: 1.2 (0x2) LMP Subversion: 0x525
        Manufacturer: Cambridge Silicon Radio (10)
        Features: 0xff 0xff 0x0b 0x00 0x08 0x08 0x00 0x00
                <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> <AFH cap. slave> <AFH cap. master>
-- 
Steven Winston <spwinston@gmail.com>
spwinston@gmail.com



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2005-11-14 10:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 10:34 Steven Winston [this message]
2005-11-14 11:15 ` [Bluez-devel] btsco headset almost works manish Verma
2005-11-14 11:41 ` Maik Zumstrull

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=1131964498.3323.77.camel@Linux.localdoman.com \
    --to=spwinston@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).