linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohan Sundaram <mohan.tux@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Headset problem
Date: Thu, 01 Nov 2007 08:18:37 +0530	[thread overview]
Message-ID: <47293E85.1050708@vsnl.com> (raw)

I have a Motorola headset and am trying to use it with my system. When I 
invoke the Bluetooth headset applet, the headset is discovered by does 
not register as the active handset. It looks like the connection is made 
but it still does not show up.

root@smohan-laptop:/home/smohan# hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.39
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Inquiry (0x01|0x0001) plen 5
 > HCI Event: Command Status (0x0f) plen 4
 > HCI Event: Inquiry Result with RSSI (0x22) plen 15
 > HCI Event: Inquiry Result with RSSI (0x22) plen 15
 > HCI Event: Inquiry Result with RSSI (0x22) plen 15
 > HCI Event: Inquiry Result with RSSI (0x22) plen 15
 > HCI Event: Inquiry Result with RSSI (0x22) plen 15
 > HCI Event: Inquiry Result with RSSI (0x22) plen 15
 > HCI Event: Inquiry Result with RSSI (0x22) plen 15
 > HCI Event: Inquiry Result with RSSI (0x22) plen 15
 > HCI Event: Inquiry Result with RSSI (0x22) plen 15
 > HCI Event: Inquiry Complete (0x01) plen 1
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
 > HCI Event: Command Status (0x0f) plen 4
 > HCI Event: Remote Name Req Complete (0x07) plen 255
< HCI Command: Create Connection (0x01|0x0005) plen 13
 > HCI Event: Command Status (0x0f) plen 4
 > HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
 > HCI Event: Command Complete (0x0e) plen 10
 > HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
 > HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Create Connection (0x01|0x0005) plen 13
 > HCI Event: Command Status (0x0f) plen 4
 > HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
 > HCI Event: Command Complete (0x0e) plen 10
 > HCI Event: Connect Complete (0x03) plen 11

after this, hcitool con does not show any connections.
Mohan

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2007-11-01  2:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01  2:48 Mohan Sundaram [this message]
2007-11-01  5:02 ` [Bluez-users] Headset problem Marcel Holtmann
2007-11-01  6:27   ` Mohan Sundaram
2007-11-01  6:32     ` Marcel Holtmann
2007-11-01  7:19       ` Mohan Sundaram
2007-11-01  7:26       ` Mohan Sundaram
  -- strict thread matches above, loose matches on Subject: below --
2007-11-01 13:31 Mohan Sundaram
2007-11-01 13:30 Mohan Sundaram
2007-03-19  9:53 [Bluez-users] headset problem Livio Tenze
2007-03-19 11:55 ` Wolfgang Wershofen

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=47293E85.1050708@vsnl.com \
    --to=mohan.tux@gmail.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=smohan@vsnl.com \
    /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).