Linux bluetooth development
 help / color / mirror / Atom feed
From: Ross Burton <ross@burtonini.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] bluetooth-alsa not working with Cellink headset
Date: Mon, 11 Apr 2005 09:53:36 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050411T115017-79@post.gmane.org> (raw)

Hi,

I've just purchased a cheap BT headset (a Cellink BTHS-6023F), and tried to use
it with the bluetooth-alsa userspace/kernel stuff.  However, it's not working:

$ ./btsco 00:0A:94:8C:CC:67
[enter PIN for pairing]
Error: The voice setting must be 0x060

For your information this is the output from hcitool:

$ hcitool info 00:0A:94:8C:CC:67
Requesting information ...
        BD Address:  00:0A:94:8C:CC:67
        Device Name: BT Headset-F
        LMP Version: 1.1 (0x1) LMP Subversion: 0x434
        Manufacturer: Cambridge Silicon Radio (10)
        Features: 0xfc 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
                <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>

Any ideas?

Thanks,
Ross



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2005-04-11  9:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11  9:53 Ross Burton [this message]
2005-04-11 15:20 ` [Bluez-devel] bluetooth-alsa not working with Cellink headset Brad Midgley

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=loom.20050411T115017-79@post.gmane.org \
    --to=ross@burtonini.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