public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bearcat M. Sandor" <Linux@feline-soul.com>
To: Brad Midgley <bmidgley@xmission.com>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Logitech Traveler Headset. pin never seen and i am never asked.
Date: Thu, 24 Aug 2006 01:59:54 -0600	[thread overview]
Message-ID: <200608240159.54651.Linux@feline-soul.com> (raw)
In-Reply-To: <44ED589B.7080101@xmission.com>

On Thursday 24 August 2006 01:43 in an email titled "Re: [Bluez-users] 
Logitech Traveler Headset. pin never seen and i am never asked." Brad Midgley 
wrote:
>Bearcat
>
>most headsets go into pairing mode by holding down the power until the
>led flashes red/blue. check your manual if you can find one.
>
I misunderstood the statement. I put it in paring mode all the time by holding 
the power button down till it flashes red/blue.  However it has never been 
successfully paired that i know of.

>hmm. yeah this one has come up from time to time. the headset *should*
>respond to sdp even when not in pairing mode. sdp shouldn't require the
>pin code either. so it's going wrong even before you can start to pair
>with it. did you get the address in the first place with hcitool scan?
Yes, with hcitool scan.  And it is found. Kdebluetooth even pops up a dialog 
telling me about it.
I just can't get it to pair/operate.

If only i could get a "0000" to it i think it would work, but it doesn't want 
to send or give me the option to enter a pin.
>Brad

-- 
Bearcat M. Sandor
Bearcat@feline-soul.com
Jabber: bearcat@jabber.feline-soul.net
ICQ: 6628727
MSN: bearcatsandor@hotmail.com
Yahoo: bearcatsandor
AIM: bearcatmsandor



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-08-24  7:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23 22:25 [Bluez-users] Logitech Traveler Headset. Progress but not there yet. Advice wanted.] Bearcat M. Sandor
2006-08-24  4:05 ` [Bluez-users] Logitech Traveler Headset. pin never seen and i am never asked Bearcat M. Sandor
2006-08-24  4:34   ` Brad Midgley
2006-08-24  5:00     ` Bearcat M. Sandor
2006-08-24  7:43       ` Brad Midgley
2006-08-24  7:59         ` Bearcat M. Sandor [this message]
2006-08-24 12:18       ` John McDougald
2006-08-25 22:20         ` Bearcat M. Sandor
  -- strict thread matches above, loose matches on Subject: below --
2006-08-25 22:22 Bearcat M. Sandor

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=200608240159.54651.Linux@feline-soul.com \
    --to=linux@feline-soul.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=bmidgley@xmission.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