From: nirav rabara <niravrabara@gmail.com>
To: Iain Hibbert <plunky@rya-online.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Question regarding HS Connection
Date: Wed, 7 Apr 2010 15:02:21 +0530 [thread overview]
Message-ID: <t2g912bb79a1004070232tf3fdfdbdx40bec76239ca0c6e@mail.gmail.com> (raw)
In-Reply-To: <1270577491.816321.874.nullmailer@galant.ukfsn.org>
hi Lain,
Thanks for your suggestion,
> you will probably find that because the HS device is very limited in
> resources, it does not keep records of more than one paired device. So, if
> you pair with another device it forgets about the first and you will not
> be able to connect except that you pair it again.
>
Does it mean that once paired device information stored in our
cellphones, if remote device(HS) doesn't have paired information, out
cellphone will take care of re-pairing.
So ultimately am I need to do pairing again??
--
With Regards,
Nirav Rabara
prev parent reply other threads:[~2010-04-07 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 12:53 Question regarding HS Connection nirav rabara
2010-04-06 18:11 ` Iain Hibbert
2010-04-07 9:32 ` nirav rabara [this message]
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=t2g912bb79a1004070232tf3fdfdbdx40bec76239ca0c6e@mail.gmail.com \
--to=niravrabara@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=plunky@rya-online.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;
as well as URLs for NNTP newsgroup(s).