linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Проклов Александр Валерьевич" <ProklovAV@mail.zabtrans.ru>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Problem with StopDiscovery() via dbus-send
Date: Tue, 28 Aug 2018 10:41:39 +0800	[thread overview]
Message-ID: <5B84B663.2010906@mail.zabtrans.ru> (raw)
In-Reply-To: <CABBYNZKeotBdqAzsKkw-jN4tmcpBdYPC34C-71S4gzCkcdDM3g@mail.gmail.com>

27.08.2018 15:24, Luiz Augusto von Dentz пишет:
> Afaik that only works for legacy pairing, normally devices without any
> input/output should rely on just works pairing which is what you would
> usually see in headset, etc, though that are not always pairable so
> you have to switch it on with a button or something like it.

Now my pair process with non-android phone:
#bluetoothctl
[bluetooth] pair 11:22:33:44:55:66

I intering pin code in command shell: 1234
Phone shows a window for entering the code.
I intering pin code on phone. Device pair.

Step with the input of the code in the terminal can be skipped if the 
code is given in main.conf

the reverse process, when the code transmits the phone to the computer, 
I have not considered so far. I think this through the script will be 
difficult to implement.

  reply	other threads:[~2018-08-28  2:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24  1:58 Problem with StopDiscovery() via dbus-send Проклов Александр Валерьевич
2018-08-24  8:19 ` Luiz Augusto von Dentz
2018-08-24 14:36   ` Luiz Augusto von Dentz
2018-08-26 23:58   ` Проклов Александр Валерьевич
2018-08-27  7:24     ` Luiz Augusto von Dentz
2018-08-28  2:41       ` Проклов Александр Валерьевич [this message]
2018-09-06  0:43   ` Проклов Александр Валерьевич
2018-10-29  5:47   ` Non intheractive request pin-code Проклов Александр Валерьевич
2018-11-01  3:44   ` Serial communication over BT using the DBus API Проклов Александр Валерьевич
  -- strict thread matches above, loose matches on Subject: below --
2017-09-15  3:25 Problem with StopDiscovery() via dbus-send Проклов Александр Валерьевич
2017-09-15  6:27 ` Luiz Augusto von Dentz
2017-09-15  8:35   ` Проклов Александр Валерьевич
2017-09-15  8:46     ` Luiz Augusto von Dentz
2017-09-18  2:50       ` Проклов Александр Валерьевич
2017-09-18  6:53         ` Luiz Augusto von Dentz
2017-09-18  8:59           ` Проклов Александр Валерьевич
2017-09-19 23:58           ` Проклов Александр Валерьевич
2017-09-25  1:26           ` Проклов Александр Валерьевич
2017-07-25 23:51 Проклов Александр Валерьевич
2017-07-26  8:05 ` Luiz Augusto von Dentz
2017-07-27  0:50   ` Проклов Александр Валерьевич
2017-07-27 11:33     ` Luiz Augusto von Dentz

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=5B84B663.2010906@mail.zabtrans.ru \
    --to=proklovav@mail.zabtrans.ru \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).