Linux bluetooth development
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: Re: Plantronics M2500 recording problem
Date: Thu, 02 Jun 2005 14:37:35 -0600	[thread overview]
Message-ID: <429F6E0F.3080805@xmission.com> (raw)
In-Reply-To: <429E3429.6000108@ex.ac.uk>

Guys,

I created a bug report for this one ([ 1213784 ] noisy sco recordings).

It would be good to know what kernel version and bluez-libs versions you 
guys are having the problem with and if it's persisting between 
versions. Email me and I'll keep the bug report up to date.

Brad

George Norton wrote:
> Thanks for the quick reply:
> 
> george@G0on:~$ hciconfig -a
> hci0:   Type: USB
>        BD Address: 00:E0:98:D1:B0:5F ACL MTU: 192:8  SCO MTU: 64:8
>        UP RUNNING PSCAN ISCAN
>        RX bytes:101956 acl:25 sco:1980 events:62 errors:0
>        TX bytes:72654 acl:23 sco:1403 commands:29 errors:0
>        Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>        Link policy: RSWITCH HOLD SNIFF PARK
>        Link mode: SLAVE ACCEPT
>        Name: 'G0on-0'
>        Class: 0x000100
>        Service Classes: Unspecified
>        Device Class: Computer, Uncategorized
>        HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 
> 0x20d
>        Manufacturer: Cambridge Silicon Radio (10)
> 
> george@G0on:~$ hciconfig hci0 revision
> hci0:   Type: USB
>        BD Address: 00:E0:98:D1:B0:5F ACL MTU: 192:8  SCO MTU: 64:8
>        HCI 16.4
>        Chip version: BlueCore02
>        Max key size: 56 bit
>        SCO mapping:  HCI
> 
> george@G0on:~$ hcitool info 00:03:89:B6:0D:F8
> Requesting information ...
>        BD Address:  00:03:89:B6:0D:F8
>        Device Name: M2500 by Plantronics
>        LMP Version: 1.2 (0x2) LMP Subversion: 0x615
>        Manufacturer: Cambridge Silicon Radio (10)
>        Features: 0xbc 0xe8 0x01 0x00 0x08 0x08 0x00 0x00
>                <encryption> <slot offset> <timing accuracy> <role switch>
>                <sniff mode> <SCO link> <HV3 packets> <u-law log> <A-law 
> log>
>                <CVSD> <AFH cap. slave> <AFH cap. master>
> 
> 
> // While recording in audacity, first recording is normal:
> george@G0on:~$ hcidump -X
> HCIDump - HCI packet analyzer ver 1.12
> device: hci0 snap_len: 1028 filter: 0xffffffff
> 
>> HCI Event: Command Status (0x0f) plen 4
> 
>  0000: 00 01 07 04                                       ....
> 
>> HCI Event: Connect Complete (0x03) plen 11
> 
>  0000: 00 2c 00 f8 0d b6 89 03  00 00 01                 .,.........
> 
>> HCI Event: Command Status (0x0f) plen 4
> 
>  0000: 00 01 06 04                                       ....
> 
>> HCI Event: Disconn Complete (0x05) plen 4
> 
>  0000: 00 2c 00 16                                       .,..
> 
>> HCI Event: Command Status (0x0f) plen 4
> 
>  0000: 00 01 07 04                                       ....
> 
>> HCI Event: Connect Complete (0x03) plen 11
> 
>  0000: 00 30 00 f8 0d b6 89 03  00 00 01                 .0.........
> 
>> HCI Event: Command Status (0x0f) plen 4
> 
>  0000: 00 01 06 04                                       ....
> 
>> HCI Event: Disconn Complete (0x05) plen 4
> 
>  0000: 00 30 00 16                                       .0..
> 
> // A second recording which is corrupted:
> 
>> HCI Event: Command Status (0x0f) plen 4
> 
>  0000: 00 01 07 04                                       ....
> 
>> HCI Event: Connect Complete (0x03) plen 11
> 
>  0000: 00 2c 00 f8 0d b6 89 03  00 00 01                 .,.........
> 
>> HCI Event: Command Status (0x0f) plen 4
> 
>  0000: 00 01 06 04                                       ....
> 
>> HCI Event: Disconn Complete (0x05) plen 4
> 
>  0000: 00 2c 00 16                                       .,..
> 
> // I attempted to record and got a corrupted recording:
> george@G0on:~$ btsco -v 00:03:89:B6:0D:F8
> btsco v0.4c
> Device is 1:0
> Voice setting: 0x0060
> RFCOMM channel 1 connected
> speaker volume: 7 mic volume: 15
> i/o needed: connecting sco...
> connected SCO channel
> Done setting sco fd
> recieved AT+VGS=07
> Sending up speaker change 7
> speaker volume: 7 mic volume: 15
> driver is not in use
> disconnected SCO channel
> 
> Kernel Version: 2.6.11.11
> Distribution: Ubuntu 5.04 (Hoary)
> 
> -George
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2005-06-02 20:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 22:18 [Bluez-users] Re: Re: Plantronics M2500 recording problem George Norton
2005-06-01 22:28 ` Brad Midgley
2005-06-02 10:22   ` Florian Echtler
2005-06-02 20:37 ` Brad Midgley [this message]
2005-06-03 11:41   ` Florian Echtler

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=429F6E0F.3080805@xmission.com \
    --to=bmidgley@xmission.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