On 30.07.2015 10:48, Sebastien Bacher wrote:
Le 30/07/2015 10:30, Simon Busch a écrit :
From what it looks in the ubuntu-system-settings code we nowadays
don't support the DisplayPinCode call from BlueZ which is relevant for
Bluetooth devices not supporting SSP (those using Bluetooth < 2.1).
Will file a bug for this.
Indeed it's not, but the bluez documentation states
" void DisplayPinCode(object device, string pincode)
This method gets called when the service daemon
needs to display a pincode for an authentication.
An empty reply should be returned. When the pincode
needs no longer to be displayed, the Cancel method
of the agent will be called.
If this method is not implemented the RequestPinCode
method will be used instead."
So in practice RequestPinCode is used and you can pair those devices, we
should still support DisplayPinCode so please open a bug (unsure if
there is a visible user experience difference between those?)
The user experience is in so far different that the user has to enter
the PIN only on one device. It comes more along what the Bluetooth spec
specifies: Initiator displays, responder inputs. Will create the bug
report against the settings-app.
regars,
Simon
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
