kernel-packages team mailing list archive

[TJ <ubuntu@xxxxxx>]

I've managed to connect the Asus Transformer T300Chi; this may work for
other tablets/hybrids/modern Bluetooth devices.

I am working from the 16.04 GUI installer in 'Try' mode. Touch-screen
and stylus input was working so I first went to System Settings >
Universal Access and enabled the on-screen keyboard.

Then I was able to join to the WiFi network by entering its details.
With that I opened a Terminal and installed the SSH server with:

$ sudo apt install openssh-server

I then set a default password for the 'ubuntu' user:

$ passwd

And then from another PC was able to ssh to the T300Chi:

$ ssh ubuntu@10.254.1.42

With shell access I then put the docking keyboard into pairing mode and
did:

ubuntu@ubuntu:~$ bluetoothctl
[NEW] Controller 34:02:86:FC:AD:59 ubuntu [default]
[NEW] Device 1C:B7:2C:04:C7:FE ASUS T300CHI DOCKING
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 34:02:86:FC:AD:59 Discovering: yes
[NEW] Device 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj
[CHG] Device 1C:B7:2C:04:C7:FE RSSI: -36

[bluetooth]# pair 1C:B7:2C:04:C7:FE                                                                                                                           
Attempting to pair with 1C:B7:2C:04:C7:FE
[CHG] Device 1C:B7:2C:04:C7:FE Connected: yes
[agent] PIN code: 117372

At this point I typed the PIN code on the docking keyboard followed by
Enter.

[CHG] Device 1C:B7:2C:04:C7:FE Modalias: usb:v0B05p8502d0001
[CHG] Device 1C:B7:2C:04:C7:FE UUIDs: 00001000-0000-1000-8000-00805f9b34fb
[CHG] Device 1C:B7:2C:04:C7:FE UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 1C:B7:2C:04:C7:FE UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 1C:B7:2C:04:C7:FE Paired: yes
Pairing successful

I then started pressing keys on the keyboard which caused lots of
messages

[CHG] Device 1C:B7:2C:04:C7:FE Connected: no
[CHG] Device 1C:B7:2C:04:C7:FE Class: 0x0005c0
[CHG] Device 1C:B7:2C:04:C7:FE Connected: yes
[CHG] Device 1C:B7:2C:04:C7:FE Icon is nil
Authorize service
[CHG] Device 1C:B7:2C:04:C7:FE Connected: no
[CHG] Device 1C:B7:2C:04:C7:FE Connected: yes
[CHG] Device 1C:B7:2C:04:C7:FE Connected: no
[CHG] Device 1C:B7:2C:04:C7:FE Class: 0x0025c0
[CHG] Device 1C:B7:2C:04:C7:FE Icon is nil
[CHG] Device 1C:B7:2C:04:C7:FE Class: 0x0005c0
[CHG] Device 1C:B7:2C:04:C7:FE Connected: yes
[CHG] Device 1C:B7:2C:04:C7:FE Icon is nil
[CHG] Device 1C:B7:2C:04:C7:FE Connected: no
[CHG] Device 1C:B7:2C:04:C7:FE Connected: yes
[CHG] Device 1C:B7:2C:04:C7:FE Connected: no
[CHG] Device 1C:B7:2C:04:C7:FE Connected: yes
[CHG] Device 1C:B7:2C:04:C7:FE Connected: no
[CHG] Device 1C:B7:2C:04:C7:FE Connected: yes
[CHG] Device 1C:B7:2C:04:C7:FE Connected: no
[CHG] Device 1C:B7:2C:04:C7:FE Class: 0x0025c0
[CHG] Device 1C:B7:2C:04:C7:FE Icon is nil
Request canceled
[CHG] Device 1C:B7:2C:04:C7:FE Class: 0x0005c0
[CHG] Device 1C:B7:2C:04:C7:FE Connected: yes
[CHG] Device 1C:B7:2C:04:C7:FE Icon is nil

Until I noticed the following message and prompt

Authorize service
[agent] Authorize service 00001124-0000-1000-8000-00805f9b34fb (yes/no): yes

At which point the docking keyboard and trackpad began working:

[ASUS T300CHI DOCKING]# paired-devices
Device 1C:B7:2C:04:C7:FE ASUS T300CHI DOCKING

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490347

Title:
  [Regresision] 15:10 - Cannot pair with devices using PIN codes

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+subscriptions