From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bluetooth 1.2 - how do I know it's working?
Date: Wed, 13 Apr 2005 17:15:22 +0200 [thread overview]
Message-ID: <1113405322.9061.36.camel@pegasus> (raw)
In-Reply-To: <pan.2005.04.13.14.52.16.599459@wingnet.net>
Hi Jesse,
> I just bought a D-Link DBT 120 rev B3 from ebay and flashed
> it with the latest Apple dfu firmware using btdfu. (Thanks
> for the advice, Marcel!)
>
> Before the firmware upgrade, it talked to my Logitech Mobile
> Freedom headset fine (Logitech HS02-V07) using btsco, but
> the connection cracked and popped a lot. I run an 802.11b
> network, so I figured the BT 1.1 might be getting interference
> from the 802.11b net, thus causing the sound artifacts.
>
> After the successful upgrade, it sounds a little better, I
> think, but how do I make sure that the USB adapter AND the
> headset are using BT 1.2's AFH features?
>
> Here's my adapter:
>
> hci0: Type: USB
> BD Address: 00:0D:88:93:FC:3E ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:576034 acl:30 sco:11266 events:88 errors:0
> TX bytes:569989 acl:26 sco:11157 commands:40 errors:0
> Features: 0xff 0xff 0x8f 0x78 0x18 0x18 0x00 0x80
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ (0)'
> Class: 0xff0100
> Service Classes: Positioning, Networking, Rendering, Capturing, Object Transfer, Audio, Telephony, Information
> Device Class: Computer, Uncategorized
> HCI Ver: 1.2 (0x2) HCI Rev: 0x632 LMP Ver: 1.2 (0x2) LMP Subver: 0x632
> Manufacturer: Cambridge Silicon Radio (10)
>
> And here's my Mobile Freedom Headset:
>
> # hcitool info 00:0D:44:36:E6:F4
> Requesting information ...
> BD Address: 00:0D:44:36:E6:F4
> Device Name: Logitech HS02-V07
> LMP Version: 1.2 (0x2) LMP Subversion: 0x611
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xfc 0xfe 0x0f 0x00 0x08 0x08 0x00 0x00
> <encryption> <slot offset> <timing accuracy> <role switch>
> <hold mode> <sniff mode> <RSSI> <channel quality> <SCO link>
> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
> <paging scheme> <power control> <transparent SCO>
> <AFH cap. slave> <AFH cap. master>
>
> # hcitool afh 00:0D:44:36:E6:F4
> AFH map: 0xffffffffffffffffff7f
>
> Does this indicate that both devices are using AFH correctly?
monitor the "hcitool afh" call and if the value changes then AFH is
working.
Regards
Marcel
-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-04-13 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 14:52 [Bluez-users] bluetooth 1.2 - how do I know it's working? Jesse Guardiani
2005-04-13 15:15 ` Marcel Holtmann [this message]
2005-04-13 19:53 ` [Bluez-users] " Jesse Guardiani
2005-04-13 20:26 ` Marcel Holtmann
2005-04-14 16:59 ` [Bluez-users] " Jesse Guardiani
2005-04-14 17:07 ` Marcel Holtmann
2005-04-14 17:44 ` [Bluez-users] " Jesse Guardiani
2005-04-14 18:21 ` Marcel Holtmann
2005-04-15 13:18 ` [Bluez-users] " Jesse Guardiani
2005-04-15 13:44 ` 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=1113405322.9061.36.camel@pegasus \
--to=marcel@holtmann.org \
--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