All of lore.kernel.org
 help / color / mirror / Atom feed
From: administrator tootai <admin@tootai.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: Connection issue with headset
Date: Thu, 03 Feb 2005 22:39:55 +0100	[thread overview]
Message-ID: <42029A2B.6020905@tootai.net> (raw)
In-Reply-To: <cttbgv$knk$1@sea.gmane.org>

Sebastian Roth a =E9crit :

> Hi Daniel,

Hi Sebastian

>
>
>>> are the other things build into the kernel or loaded? (bluetooth,
>>> hci_usb, l2cap, rfcomm, sco)
>>
>>
>> all in modules
>
> Have you really loaded all of them?
>
> Your posted output of dmesg:
> Bluetooth: L2CAP ver 2.6
> Bluetooth: L2CAP socket layer initialized
> Bluetooth: RFCOMM ver 1.3
> Bluetooth: RFCOMM socket layer initialized
> Bluetooth: RFCOMM TTY layer initialized
> # where is SCO?
> snd-bt-sco revision 1.4 $
> snd-bt-sco: snd-bt-scod thread starting
>
> My output:
> Bluetooth: L2CAP ver 2.7
> Bluetooth: L2CAP socket layer initialized
> Bluetooth: RFCOMM ver 1.5
> Bluetooth: RFCOMM socket layer initialized
> Bluetooth: RFCOMM TTY layer initialized
> Bluetooth: SCO (Voice Link) ver 0.4
> Bluetooth: SCO socket layer initialized
> snd-bt-sco revision 1.4 $
> snd-bt-sco: snd-bt-scod thread starting
>
>
> Btw. what kernel version do you use? Please update the kernel to
> 2.6.10-mh3 and the libs/utils to 2.15!!

2.6.10 (debian) + patch swsusp2 & bluez-utils 2.10-5 (debian sid)

>
>
>
> # sdptool search --bdaddr <bdaddr> 0x1108
> Class 0x1108
> Searching for 0x1108 on <bdaddr> ...
> Service Name: Headset
> Service RecHandle: 0x10000
> Service Class ID List:
>   "Headset" (0x1108)
>   "Generic Audio" (0x1203)
> Protocol Descriptor List:
>   "L2CAP" (0x0100)
>   "RFCOMM" (0x0003)
>     Channel: 1
> Profile Descriptor List:
>   "Headset" (0x1108)
>     Version: 0x0100
>
> What does this command show to you? Is the Channel the same when
> connecting with btsco?

#sdptool search --bdaddr 00:0b:2e:06:01:2e 0x1108
Class 0x1108
Searching for 0x1108 on 00:0B:2E:06:01:2E ...
Service Name: Headset
Service RecHandle: 0x20000
Service Class ID List:
  "Headset" (0x1108)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 6
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100

nomade:/etc/waproamd/keys# btsco 00:0b:2e:06:01:2e
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 6 connected
speaker volume: 10 mic volume: 10

Many thanks for you help


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-02-03 21:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28  9:32 [Bluez-users] Connection issue with headset administrator tootai
2005-01-28 15:53 ` [Bluez-users] " Sebastian Roth
2005-01-29 16:39   ` daniel huhardeaux
2005-01-29 16:43   ` administrator tootai
2005-01-29 17:29   ` Stefan Bellon
2005-01-30  3:13     ` Brad Midgley
2005-01-30 19:01   ` administrator tootai
2005-01-31 14:57   ` administrator tootai
2005-01-31 14:58     ` Marcel Holtmann
2005-01-31 15:30       ` administrator tootai
2005-01-31 15:55         ` Marcel Holtmann
2005-01-31 18:20           ` administrator tootai
2005-02-01 16:37     ` Sebastian Roth
2005-02-02 13:20       ` administrator tootai
2005-02-02 16:21         ` Sebastian Roth
2005-02-02 16:55           ` administrator tootai
2005-02-03 14:13             ` Sebastian Roth
2005-02-03 21:39               ` administrator tootai [this message]
2005-02-04  7:38                 ` Sebastian Roth
2005-02-04 12:25                   ` administrator tootai
2005-02-03 17:06           ` administrator tootai

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=42029A2B.6020905@tootai.net \
    --to=admin@tootai.net \
    --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.