public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Majola <charles@ubuntu.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] pairing problem - please help
Date: Mon, 15 Aug 2005 11:05:31 +0200	[thread overview]
Message-ID: <43005ADB.9040400@ubuntu.com> (raw)
In-Reply-To: <396736060508141923370a6662@mail.gmail.com>

Robert Brewer wrote:

>I'm not sure I ever had an /etc/bluetooth/link_key file.  
>I've got an email into Logitech support to find out more
>about it pairing abilities and any reset capability... but
>my guess is the best I can do is remove the battery.  I'm
>not certain that will clear its memory though.
>
>If I tried to find the PIN and hostname used on the Windows
>side would that help?
>
>Thanks for the tips.
>
>-Rob
>
>On 8/14/05, Brad Midgley <bmidgley@xmission.com> wrote:
>  
>
>>Robert,
>>
>>    
>>
>>>A few weeks ago I successfully paired my headset with my broadcom dongle
>>>under bluez.  I was able to l2ping the headset, and btsco was able to make
>>>the headset ring.  I couldn't get audio data through, but now I know that
>>>is because bluez doesn't support SCO for broadcom.
>>>
>>>Now I can't get the headset paired.  The past week I've been pairing the headset
>>>with the same dongle under WinXP.  Any thoughts on what is going wrong?
>>>      
>>>
>>Several people have had similar issues. Sometimes, removing
>>/etc/bluetooth/link_key works since it resets the pairing. Sometimes it
>>doesn't help at all.
>>
>>Is it true that the failed attempts are all on dualboot machines that
>>have used windows to pair to the headset? Maybe the headset remembers
>>the bdaddr but gets confused by the fact that the stored credentials
>>under linux don't match the last pairing in windows. That's about the
>>only idea I've had on it and I don't see much discussion here about
>>what's going on...
>>
>>Some headsets remember multiple pairings. Does yours have a reset,
>>something more drastic than just putting it in pairing mode? My iTech
>>set has a reset but I've come to believe they put that in there because
>>the headset completely locks up and becomes unresponsive on occasion :(
>>
>>Brad
>>
>>
>>    
>>
>
>  
>
TOP POSTING ? *sigh*

Actually I think his probem is that fact that /etc/bluetooth/pin reads
"1234" and it actually should read "PIN:1234". I noticed that from the
sources after my fone stopped pairng with my laptop. Removing the
link_key file and fixing the above should work.

--
chmj

www.sourcecode.za.net
www.ubuntulinux.org



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-08-15  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14  3:31 [Bluez-users] pairing problem - please help Robert Brewer
2005-08-14  6:03 ` Brad Midgley
2005-08-15  2:23   ` Robert Brewer
2005-08-15  9:05     ` Charles Majola [this message]
2005-08-22  3:54       ` Robert Brewer

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=43005ADB.9040400@ubuntu.com \
    --to=charles@ubuntu.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