Bluetooth: hci0: last event is not cmd complete (0x0f) with LG TV

Bluetooth: hci0: last event is not cmd complete (0x0f) with LG TV

[Paul Menzel]

Dear Linux folks,


When trying to pair a Dell Latitude E7250 running Debian Sid/unstable 
with Linux 4.20 and GNOME 3.30 with an LG TV, after starting the pairing 
process the TV is listed. in Bluetooth dialog of GNOME setting.

The TV displays the instructions below.

> Complete the next three steps on your mobile device:
> 1. Turn ON Bluetooth.
> 2. Select the TV name from the list of available devices.
>    • TV Name : 679
> 3. Confirm the connection request.

Selecting the TV in the GNOME dialog, a dialog is shown on my system 
with a PIN consisting of six numbers. With the dialog, Linux logs the 
message below.

      Bluetooth: hci0: last event is not cmd complete (0x0f)

But, the TV does not show any PIN. Confirming it anyway, nothing is 
happening further.

Is that supposed to work? It’d be great if you helped me to set this up.


Kind regards,

Paul

Re: Bluetooth: hci0: last event is not cmd complete (0x0f) with LG TV

[Paul Menzel]

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

Dear Linux folks,


On 01.02.19 22:34, Paul Menzel wrote:
> [attaching Linux messages, lspci and lsusb output]
> 
> On 01.02.19 22:20, Paul Menzel wrote:

>> When trying to pair a Dell Latitude E7250 running Debian Sid/unstable 
>> with Linux 4.20 and GNOME 3.30 with an LG TV, after starting the 
>> pairing process the TV is listed. in Bluetooth dialog of GNOME setting.
>>
>> The TV displays the instructions below.
>>
>>> Complete the next three steps on your mobile device:
>>> 1. Turn ON Bluetooth.
>>> 2. Select the TV name from the list of available devices.
>>>    • TV Name : 679
>>> 3. Confirm the connection request.
>>
>> Selecting the TV in the GNOME dialog, a dialog is shown on my system 
>> with a PIN consisting of six numbers. With the dialog, Linux logs the 
>> message below.
>>
>>       Bluetooth: hci0: last event is not cmd complete (0x0f)
>>
>> But, the TV does not show any PIN. Confirming it anyway, nothing is 
>> happening further.
>>
>> Is that supposed to work? It’d be great if you helped me to set this up.

Please find a trace attached. This time Linux 4.19.16 was running.

     sudo tcpdump -i bluetooth0 -w bluetooth0_capture.pcap


Kind regards,

Paul

[-- Attachment #2: bluetooth0_capture.pcap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 33808 bytes --]