Lenovo keyboard

Lenovo keyboard

[chris]

Dear list,

I've been consistently using a lenovo bluetooth keyboard since Bluez4.
Since a recent (a month ago or so) upgrade (debian/stretch) it doesn't
connect anymore.
Neither does a Jabra Stealth earpiece which was doing fine a month ago.

$ bluetoothctl --version
5.36

Here is my attempt to pair the keyboard (as root):

# bluetoothctl -a
[NEW] Controller 9C:2A:70:82:50:FB pluto [default]
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 9C:2A:70:82:50:FB Discovering: yes
[NEW] Device 90:7F:61:11:2C:A7 ThinkPad Compact Bluetooth Keyboard
with TrackPoint
[CHG] Device 90:7F:61:11:2C:A7 Connected: no
[DEL] Device 90:7F:61:11:2C:A7 ThinkPad Compact Bluetooth Keyboard
with TrackPoint
[NEW] Device 90:7F:61:11:2C:A7 ThinkPad Compact Bluetooth Keyboard
with TrackPoint
[bluetooth]# pair 90:7F:61:11:2C:A7
Attempting to pair with 90:7F:61:11:2C:A7
[CHG] Device 90:7F:61:11:2C:A7 Connected: yes
[agent] Passkey: 136021
[agent] Passkey: 136021
[agent] Passkey: 136021
[agent] Passkey: 136021
[agent] Passkey: 136021
[agent] Passkey: 136021
[agent] Passkey: 136021
[CHG] Device 90:7F:61:11:2C:A7 RSSI: -53
[CHG] Device 90:7F:61:11:2C:A7 Paired: yes
Pairing successful
[CHG] Device 90:7F:61:11:2C:A7 Connected: no
[bluetooth]# trust 90:7F:61:11:2C:A7
[CHG] Device 90:7F:61:11:2C:A7 Trusted: yes
Changing 90:7F:61:11:2C:A7 trust succeeded
[bluetooth]# connect 90:7F:61:11:2C:A7
Attempting to connect to 90:7F:61:11:2C:A7
[CHG] Device 90:7F:61:11:2C:A7 Connected: yes
[CHG] Device 90:7F:61:11:2C:A7 RSSI: -68
Failed to connect: org.bluez.Error.Failed
[CHG] Device 90:7F:61:11:2C:A7 Connected: no
[CHG] Device 90:7F:61:11:2C:A7 RSSI: -57
[bluetooth]# quit

During the passkey thing, the color of the digits indicates that the
input from the bluetooth keyboard is taken into account.

Even when it says conneced: yes, it isn't actually connected:
the led of the keyboard indicates it isn't connected and there is no input.

# cat /var/lib/bluetooth/9C\:2A\:70\:82\:50\:FB/90\:7F\:61\:11\:2C\:A7/info
[General]
Name=ThinkPad Compact Bluetooth Keyboard with TrackPoint
Class=0x002540
SupportedTechnologies=BR/EDR;
Trusted=true
Blocked=false

[LinkKey]
Key=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Type=5
PINLength=0

I've got no knowledge about how bluetooth stack is working, I'm a
complete end-user there.
But if you can point me out something I've done wrong, or suggest
something else to do,
or if I can provide additional information...

Chris

Re: Lenovo keyboard

[Berend De Schouwer]

On Sat, 2015-12-12 at 17:06 +0100, chris wrote:
> Dear list,
> 
> I've been consistently using a lenovo bluetooth keyboard since
> Bluez4.
> Since a recent (a month ago or so) upgrade (debian/stretch) it
> doesn't
> connect anymore.
> Neither does a Jabra Stealth earpiece which was doing fine a month
> ago.
> 
> Even when it says conneced: yes, it isn't actually connected:
> the led of the keyboard indicates it isn't connected and there is no
> input.

I've got similar symptoms with 4 different bluetooth keyboards.  One
Logitech, one Apple, one Kanex and one Astrum.

Pairing works, input fails.

At the same time, the kernel loops:
[ 1449.370904] Bluetooth: hci0 ACL packet for unknown connection handle
2
[ 1455.734779] Bluetooth: hci0 ACL packet for unknown connection handle
3
[ 1461.731976] Bluetooth: hci0 ACL packet for unknown connection handle
4
[ 1468.037014] Bluetooth: hci0 ACL packet for unknown connection handle
5
[ 1474.005517] Bluetooth: hci0 ACL packet for unknown connection handle
6
[ 1479.972716] Bluetooth: hci0 ACL packet for unknown connection handle
7
[ 1491.066637] Bluetooth: hci0 ACL packet for unknown connection handle
8


Eventually a working handle is found.

The Logitech is ancient, but the others are relatively new.

Re: Lenovo keyboard

[chris]

On Sun, Dec 13, 2015 at 8:20 AM, Berend De Schouwer
<berend.de.schouwer@gmail.com> wrote:
> On Sat, 2015-12-12 at 17:06 +0100, chris wrote:
>> Dear list,
>>
>> I've been consistently using a lenovo bluetooth keyboard since
>> Bluez4.
>> Since a recent (a month ago or so) upgrade (debian/stretch) it
>> doesn't
>> connect anymore.
>> Neither does a Jabra Stealth earpiece which was doing fine a month
>> ago.
>>
>> Even when it says conneced: yes, it isn't actually connected:
>> the led of the keyboard indicates it isn't connected and there is no
>> input.
>
> I've got similar symptoms with 4 different bluetooth keyboards.  One
> Logitech, one Apple, one Kanex and one Astrum.
>
> Pairing works, input fails.
>
> At the same time, the kernel loops:
> [ 1449.370904] Bluetooth: hci0 ACL packet for unknown connection handle
> 2
> [ 1455.734779] Bluetooth: hci0 ACL packet for unknown connection handle
> 3
> [ 1461.731976] Bluetooth: hci0 ACL packet for unknown connection handle
> 4
> [ 1468.037014] Bluetooth: hci0 ACL packet for unknown connection handle
> 5
> [ 1474.005517] Bluetooth: hci0 ACL packet for unknown connection handle
> 6
> [ 1479.972716] Bluetooth: hci0 ACL packet for unknown connection handle
> 7
> [ 1491.066637] Bluetooth: hci0 ACL packet for unknown connection handle
> 8
>
>
> Eventually a working handle is found.
>
> The Logitech is ancient, but the others are relatively new.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Thanks for the answer,

I also have the same sort of error when I do "dmesg". However I don't
know whether they are relevant or not.

Also the problem is not limited to keyboard only; here is a session
with a "Jabra STEALTH" earpiece:
# bluetoothctl -a
[NEW] Controller 9C:2A:70:82:50:FB pluto [default]
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 9C:2A:70:82:50:FB Discovering: yes
[NEW] Device 50:C9:71:B5:42:2F Jabra STEALTH a1.15.0
[CHG] Device 50:C9:71:B5:42:2F RSSI: -71
[bluetooth]# pair 50:C9:71:B5:42:2F
Attempting to pair with 50:C9:71:B5:42:2F
[CHG] Device 50:C9:71:B5:42:2F Connected: yes
[CHG] Device 50:C9:71:B5:42:2F Paired: yes
Pairing successful
[CHG] Device 50:C9:71:B5:42:2F Connected: no
[CHG] Device 50:C9:71:B5:42:2F Connected: yes
[CHG] Device 50:C9:71:B5:42:2F Connected: no
[bluetooth]# trust 50:C9:71:B5:42:2F
[CHG] Device 50:C9:71:B5:42:2F Trusted: yes
Changing 50:C9:71:B5:42:2F trust succeeded
[bluetooth]# connect 50:C9:71:B5:42:2F
Attempting to connect to 50:C9:71:B5:42:2F
[CHG] Device 50:C9:71:B5:42:2F Connected: yes
[CHG] Device 50:C9:71:B5:42:2F Connected: no
[CHG] Device 50:C9:71:B5:42:2F Connected: yes
[Jabra STEALTH a1.15.0]# quit
Agent unregistered
[DEL] Controller 9C:2A:70:82:50:FB pluto [default]

Even though the earpiece "looks" connected, somehow, from the computer
side, sometime; when pressing the appropriate button on the earpiece,
it definitely says "you device is not connected".

Last point, as I already mentioned in the first mail, the computer did
somehow take the input from the keyboard at one moment; in the
following bit of the pairing session with the keyboard:
[agent] Passkey: 136021
[agent] Passkey: 136021
[agent] Passkey: 136021
[agent] Passkey: 136021
[agent] Passkey: 136021
[agent] Passkey: 136021
[agent] Passkey: 136021
Each line correspond to a keystroke from the (lenovo) bluetooth keyboard.

Hence, the controller is very much "aware" of the keyboard.

(here the "info" file created during the pairing attempt of the earpiece:
# cat /var/lib/bluetooth/9C\:2A\:70\:
82\:50\:FB/50\:C9\:71\:B5\:42\:2F/info
[General]
Name=Jabra STEALTH a1.15.0
Class=0x240404
SupportedTechnologies=BR/EDR;
Trusted=true
Blocked=false

[LinkKey]
Key=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Type=4
PINLength=0
)

Chris