public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Mahtab Hossain <mahtab_hossain2002@yahoo.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ and Headset
Date: Sat, 5 Apr 2008 06:28:26 -0700 (PDT)	[thread overview]
Message-ID: <5442.28036.qm@web50505.mail.re2.yahoo.com> (raw)
In-Reply-To: <878714.13630.qm@web50507.mail.re2.yahoo.com>


[-- Attachment #1.1: Type: text/plain, Size: 3433 bytes --]

I finally could make Nokia HDW-3 work with Fedora 8 by applying the patch listed in this mailing list.

At least everything is fine at the moment though I get the following error while playing (it still plays fine) -

[AO_ALSA] alsa-lib: pcm_bluetooth.c:417:(bluetooth_hsp_hw_params) Protocol not available (92)


Thanks
Mahtab

Mahtab Hossain <mahtab_hossain2002@yahoo.com> wrote: Hi,

I have a Nokia HDW-3 which has been used with btsco successfully before in Fedora 4. Now, it seems I can't somehow pair it.

Here is my hcid.conf file look like:
options {
        # Automatically initialize new devices
        autoinit yes;

        security user;

        pairing multi;

        # Default PIN code for incoming connections
        passkey "BlueZ";
}

hcitool scan or inq can find the headset. And I also have successfully paired with my Motorola Mobile Phone (entering PIN at both Phone and Laptop side) - so I think pairing can be done with the current state of my bluez stack.

The hcidump -X -V always gives me the following results whenever I try to connect with my headset or run some command  like, hcitool info <bt-addr of headset> or send direct command like CreateBonding through dbus or even when I switch-on my headset (I wonder why my dongle wants to connect with the headset since I have not saved any information of my headset in the Laptop).

HCI sniffer - Bluetooth packet analyzer ver 1.40
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Connect Request (0x04) plen 10
    bdaddr 00:03:89:B0:58:91 class 0x200404 type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 00:03:89:B0:58:91 role 0x01
    Role: Slave
> HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
    bdaddr 00:03:89:B0:58:91
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
    bdaddr  00:03:89:B0:58:91
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 00:03:89:B0:58:91
> HCI Event: Connect Complete (0x03) plen 11
    status 0x06 handle 42 bdaddr 00:03:89:B0:58:91 type ACL encrypt 0x00
    Error: PIN or Key Missing

These are my current bluetooth packages:

rpm -qa | grep bluez*

bluez-utils-3.20-6.fc8
gnome-bluetooth-0.10.0-1.fc8
bluez-libs-3.20-1.fc8
bluez-hcidump-1.40-1.fc8
bluez-utils-cups-3.20-6.fc8
bluez-gnome-0.14-8.fc8
bluez-gnome-analyzer-0.14-8.fc8
pybluez-0.9.2-1.fc7
bluez-utils-alsa-3.20-6.fc8
gnome-bluetooth-libs-0.10.0-1.fc8
bluez-libs-devel-3.20-1.fc8

It would be really helpful if somebody can point me somewhere why the pairing isn't happening.

Thanks
Mahtab
           

---------------------------------
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users


       
---------------------------------
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.

[-- Attachment #1.2: Type: text/html, Size: 4382 bytes --]

[-- Attachment #2: Type: text/plain, Size: 325 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2008-04-05 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04  7:47 [Bluez-users] BlueZ and Headset Mahtab Hossain
2008-04-04 12:08 ` Mahtab Hossain
2008-04-05 13:28 ` Mahtab Hossain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-15 13:53 [Bluez-users] Bluez and headset Daniele Primon
2004-02-02 19:18 [Bluez-users] BlueZ " Michal Semler (volny.cz)
2004-02-02 21:15 ` Marcel Holtmann
2004-02-02 21:42   ` Michal Semler (volny.cz)
2004-02-02 22:57     ` 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=5442.28036.qm@web50505.mail.re2.yahoo.com \
    --to=mahtab_hossain2002@yahoo.com \
    --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