[Bug 220564] New: Wrong indentification of Bluetooth in Lenovo Legion Pro 5 and 0489:e111 Foxconn / Hon Hai Wireless_Device

[Bug 220564] New: Wrong indentification of Bluetooth in Lenovo Legion Pro 5 and 0489:e111 Foxconn / Hon Hai Wireless_Device

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=220564

            Bug ID: 220564
           Summary: Wrong indentification of Bluetooth in Lenovo Legion
                    Pro 5 and 0489:e111 Foxconn / Hon Hai Wireless_Device
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: jcubic@onet.pl
        Regression: No

I commented on https://bugzilla.kernel.org/show_bug.cgi?id=80791

But I think that this is something unrelated, since the error message:

hci0: ACL packet for unknown connection handle 3837

in my case it may be an error in the driver, I have a flood of errors in logs.
I have a new laptop from 2025 (Lenovo Legion Pro 5 16IAX10 Ultra 7 255HX) and
the system I have (fedora 42 xfce) with kernel 6.16.5-200.fc42.x86_64 detects
something as MTP Wireless Device. There is an icon on the desktop. I think that
this is because of wrong detected Bluetooth device in the Bluetooth driver. The
laptop don't have any MTP device.

gio mount -l shows:

Volume(0): Wireless Device
  Type: GProxyVolume (GProxyVolumeMonitorMTP)


mtp-detect returns:

libmtp version: 1.1.19
Listing raw device(s)
Device 0 (VID=0489 and PID=e111) is a Vizio (for Lenovo) LIFETAB S9714.
   Found 1 device(s):
   Vizio (for Lenovo): LIFETAB S9714 (0489:e111) @ bus 3, dev 6
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB
interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

lsusb:
Bus 003 Device 006: ID 0489:e111 Foxconn / Hon Hai Wireless_Device


I've enabled debugging with /sys/kernel/debug/dynamic_debug/control

This is part of the logs from btmon:

> ACL Data RX: Handle 3837 flags 0x02 dlen 143         #26475 [hci0] 238.821952
      Channel: 259 len 139 [PSM 0 mode Basic (0x00)] {chan 65535}
        32 00 9f d2 95 00 01 00 e6 0a 03 00 00 00 00 00  2...............
        00 dd 9a 00 00 00 00 00 00 08 0a 00 00 00 00 00  ................
        00 d7 04 00 00 71 cc 00 00 e9 11 00 00 00 00 00  .....q..........
        00 fe 0e 01 00 00 00 00 00 9e d2 95 00 6a d2 95  .............j..
        00 07 d6 50 00 fc 07 00 00 00 00 c0 df ff 3f 00  ...P..........?.
        00 02 00 20 00 02 00 00 00 02 00 20 00 02 00 00  ... ....... ....
        00 02 00 20 00 02 00 00 00 02 00 20 00 02 00 09  ... ....... ....
        00 5c 01 00 00 02 00 09 00 00 00 00 00 02 00 20  .\............. 
        00 02 00 00 00 02 00 20 00 02 00                 ....... ...     
> HCI Event: Number of Completed Pack.. (0x13) plen 5  #26476 [hci0] 238.854712
        Num handles: 1
        Handle: 50
        Count: 1
bluetoothd[1539]: < ACL Data TX.. flags 0x02 dlen 850  #26477 [hci0] 238.854861
      Channel: 3778 len 846 [PSM 0 mode Basic (0x00)] {chan 65535}

This is output of journalctl -k

wrz 11 00:38:50 jcubic kernel: hdev 0000000021bf8090 len 147
wrz 11 00:38:50 jcubic kernel: hci0 ACL data packet
wrz 11 00:38:50 jcubic kernel: hci0: len 143 handle 0x0efd flags 0x0002
wrz 11 00:38:50 jcubic kernel: Bluetooth: hci0: ACL packet for unknown
connection handle 3837
wrz 11 00:38:50 jcubic kernel: hci0 Event packet
wrz 11 00:38:50 jcubic kernel: hci0: event 0x13
wrz 11 00:38:50 jcubic kernel: hci0: num 1

I listen to music almost non-stop with Bluetooth speakers, and the error happen
during short music interruption. I think that it started to happen after I've
upgraded to testing kernel in Fedora.

This is a related bug in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=2392938

I hope that the provided info is enough, I used Grok (LLM) to help with
debugging.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

[Bug 220564] Wrong indentification of Bluetooth in Lenovo Legion Pro 5 16IAX10 and 0489:e111 Foxconn / Hon Hai Wireless_Device

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=220564

Jakub Jankiewicz (jcubic@onet.pl) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Wrong indentification of    |Wrong indentification of
                   |Bluetooth in Lenovo Legion  |Bluetooth in Lenovo Legion
                   |Pro 5 and 0489:e111 Foxconn |Pro 5 16IAX10 and 0489:e111
                   |/ Hon Hai Wireless_Device   |Foxconn / Hon Hai
                   |                            |Wireless_Device

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

[Bug 220564] Wrong indentification of Bluetooth in Lenovo Legion Pro 5 16IAX10 and 0489:e111 Foxconn / Hon Hai Wireless_Device

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=220564

--- Comment #1 from Jakub Jankiewicz (jcubic@onet.pl) ---
The issue is solved in 6.16.7-200.fc42.x86_64 package.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

[Bug 220564] Wrong indentification of Bluetooth in Lenovo Legion Pro 5 16IAX10 and 0489:e111 Foxconn / Hon Hai Wireless_Device

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=220564

--- Comment #2 from Jakub Jankiewicz (jcubic@onet.pl) ---
I was mistaken it's still happening but less often. The logs are not flooded
anymore.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

[Bug 220564] Wrong indentification of Bluetooth in Lenovo Legion Pro 5 16IAX10 and 0489:e111 Foxconn / Hon Hai Wireless_Device

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=220564

jeremy (jeremy53561@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeremy53561@gmail.com

--- Comment #3 from jeremy (jeremy53561@gmail.com) ---
https://github.com/LuanAdemi/mediatek7925e-bluetooth-fix/tree/main?tab=readme-ov-file#quick-install
See if that fixes this issue

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

[Bug 220564] Wrong indentification of Bluetooth in Lenovo Legion Pro 5 16IAX10 and 0489:e111 Foxconn / Hon Hai Wireless_Device

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=220564

--- Comment #4 from Jakub Jankiewicz (jcubic@onet.pl) ---
Running:

udevadm info --query=all --name=/dev/bus/usb/*/$(lsusb | grep 0489:e111 | awk
'{print $4}' | sed 's/://') 2>/dev/null | grep -E "GPHOTO2|MTP|MEDIA_PLAYER"

gives no output in my case. But will test the udev config anyway. Even that I
already tested different things with udev. I've created this report after I've
found about udev system and was asking Grok how to disable the MTP device.

I also tried to edit:

/usr/lib/udev/rules.d/69-libmtp.rules

file, to ignore my device, with no effect.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

[Bug 220564] Wrong indentification of Bluetooth in Lenovo Legion Pro 5 16IAX10 and 0489:e111 Foxconn / Hon Hai Wireless_Device

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=220564

--- Comment #5 from Jakub Jankiewicz (jcubic@onet.pl) ---
The fix solved the issue with MTP device, but there are still interruption
during playing music over Bluetooth. And this still shows up in logs:

Bluetooth: hci0: ACL packet for unknown connection handle 3837

It seems that interruption was not related to MTP device.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.