From: Jelle de Jong <jelledejong@powercraft.nl>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Nokia BH-801 why??
Date: Sun, 18 May 2008 11:18:41 +0200 [thread overview]
Message-ID: <482FF471.6070708@powercraft.nl> (raw)
In-Reply-To: <alpine.LNX.1.00.0805180455510.25212@nge2.ngu.pk>
jayjwa wrote:
>
> On Thu, 15 May 2008, Jelle de Jong wrote:
>
> -> So got an other new headset with the hope it would work...
> ->
> -> The nokia website sad it was bluetooth 2.0 instead of the 1.0 headset i first
> -> tried. But I does not work... Can somebody please enlight me why?
>
> sudo hcitool info 00:53:53:FB:7E:9C
> Requesting information ...
> BD Address: 00:53:53:FB:7E:9C
> Device Name: Nokia BH-801
> LMP Version: 2.0 (0x3) LMP Subversion: 0x212b
> Manufacturer: Broadcom Corporation (15)
> Features: 0xbc 0xfe 0x8f 0x7e 0x18 0x18 0x00 0x80
> <encryption> <slot offset> <timing accuracy> <role switch>
> <sniff mode> <RSSI> <channel quality> <SCO link> <HV2 packets>
>
> Still looks like a plain SCO ^^^^^^^
>
> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
> <power control> <transparent SCO> <broadcast encrypt>
> <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan>
> <interlaced iscan> <interlaced pscan> <inquiry with RSSI>
> <AFH cap. slave> <AFH class. slave> <AFH cap. master>
> <AFH class. master> <extended features>
>
>
>
> May 15 13:39:57 debian-eeepc hcid[8991]: Badly formated or unrecognized
> command: AT+CCWA=1
> May 15 13:39:57 debian-eeepc hcid[8991]: Badly formated or unrecognized
> command: AT+COPS=3,0
> May 15 13:39:57 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet for
> unknown connection
> handle 1
> May 15 13:39:57 debian-eeepc last message repeated 2 times
> May 15 13:39:57 debian-eeepc hcid[8991]: Badly formated or unrecognized
> command: AT+CMEE=1
> May 15 13:39:57 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet for
> unknown connection
> handle 1
> May 15 13:40:28 debian-eeepc last message repeated 10190 times
>
>
>
> The error messages also look like those when eSCO gets sent to a SCO only
> device. Maybe it's possible for bluetooth 2.0 devices to still be SCO-only? I
> don't know the qualifications ...
Yes, it seem so but does this feature <EDR ACL 3 Mbps> not indicate that
its a 2.0 device?
Thanks in advance,
Jelle
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-05-18 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 11:49 [Bluez-users] Nokia BH-801 why?? Jelle de Jong
2008-05-18 9:05 ` jayjwa
2008-05-18 9:18 ` Jelle de Jong [this message]
2008-05-20 2:02 ` jayjwa
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=482FF471.6070708@powercraft.nl \
--to=jelledejong@powercraft.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.