From: Carl K <carl@personnelware.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] PM325 by LG cell phone - pairing failed
Date: Fri, 09 Jun 2006 03:27:37 -0500 [thread overview]
Message-ID: <448930F9.2080306@personnelware.com> (raw)
In-Reply-To: <1149840442.6618.16.camel@localhost>
Marcel Holtmann wrote:
> So since you are not emulating a headset or handsfree unit, this is not
> the way to go.
>
>
arg - I was going to ask if it mattered which direction the pairing was
done for a given profile. I guess it does. Now to try the other direction.
Here is my cut/paste bug report about the "security policies" error:
https://launchpad.net/distros/ubuntu/+source/bluez-utils/+bug/49105
Carl K
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-06-09 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 6:32 [Bluez-users] PM325 by LG cell phone - pairing failed Carl K
2006-06-09 7:08 ` Marcel Holtmann
2006-06-09 8:02 ` Carl K
2006-06-09 8:07 ` Marcel Holtmann
2006-06-09 8:27 ` Carl K [this message]
2006-06-09 8:40 ` Marcel Holtmann
2006-06-09 9:38 ` Carl K
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=448930F9.2080306@personnelware.com \
--to=carl@personnelware.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;
as well as URLs for NNTP newsgroup(s).