From: Niv <nivv@cs.bgu.ac.il>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] headset wont work <sdp?>
Date: Thu, 12 Jan 2006 20:14:59 +0200 [thread overview]
Message-ID: <43C69CA3.1060606@cs.bgu.ac.il> (raw)
In-Reply-To: <43C581DE.6030205@cs.bgu.ac.il>
More info:
# hcidump -X
HCI sniffer - Bluetooth packet analyzer ver 1.27
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Command Complete (0x0e) plen 6
0000: 01 25 0c 00 60 00 .%..
> I am running Gentoo 2005.1 with ck-sources kernel 2.6.14-ck8. I had
> bt_sco working for a while. here is my dongle:
> hci0: Type: USB
> BD Address: 00:10:60:A8:86:A3 ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:4112 acl:0 sco:0 events:392 errors:0
> TX bytes:4094 acl:0 sco:0 commands:214 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: 'blacky does BT device (0)'
> Class: 0x3e0100
> Service Classes: Networking, Rendering, Capturing
> Device Class: Computer, Uncategorized
> HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP
> Subver: 0x33c
> Manufacturer: Cambridge Silicon Radio (10)
>
> I am tring to use a logitech mobile freedom :
> # hcitool info 00:0D:44:33:E1:63
> Requesting information ...
> BD Address: 00:0D:44:33:E1:63
> Device Name: Logitech HS02-V07
>
> yet when I try to find the channel:
> # sdptool search --bdaddr 00:0D:44:33:E1:63 0x1108
> Class 0x1108
> Failed to connect to SDP server on 00:0D:44:33:E1:63: Permission denied
>
> my probelm is that I follow the guide at
> bluetooth-alsa.sourceforge.net and when I:
> # esdctl stop
> # hciconfig hci0 voice 0x0060
> # btsco2 -v 00:0D:44:33:E1:63
> Device is 2:0
> Voice setting: 0x0060
> Can't connect RFCOMM channelCan't connect RFCOMM channelCan't connect
> RFCOMM channelCan't connect RFCOMM channelCan't connect RFCOMM
> channelCan't connect RFCOMM channelCan't connect RFCOMM channelCan't
> connect RFCOMM channelCan't connect RFCOMM channelCan't connect RFCOMM
> channelCan't connect RFCOMM channelCan't connect RFCOMM channelCan't
> connect RFCOMM channet
>
> I also tried it with btsco and even with "1" as it uses channel 1.
> still same response.
> I tried restarting both alsa deamon and the bluetooth. same thing.
> I think I m using the current version - as I emerged it two days ago,
> how can I tell what version I use?
>
> Thanks a lot,
> Niv
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&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:[~2006-01-12 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 22:08 [Bluez-users] headset wont work <sdp?> Niv
2006-01-12 18:14 ` Niv [this message]
2006-01-12 22:43 ` Niv
2006-01-13 1:47 ` Niv
2006-01-13 3:20 ` Niv
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=43C69CA3.1060606@cs.bgu.ac.il \
--to=nivv@cs.bgu.ac.il \
--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;
as well as URLs for NNTP newsgroup(s).