Connection upgrade failure on Lenovo Tab M10 leads to constant disconnection about nearby HOT 3 OPEN

Is it possible to provide bugreports from both sides (advertiser and discoverer)?

from nearby.

What do you mean by that? The logcat extract I provided in the original issue is on the advertiser side, that seems to cause the disconnection, so all that the discoverer gets is a disconnection from the advertiser and that's all. The question is to understand why the advertiser disconnects.

from nearby.

If you can grab bug reports from both devices, it'll help us better understand the cause of the disconnection. Beyond just the logcat snippet, bug reports include a system dump of the system and some other interesting logs. The other adb commands below will also enable some logging that's off by default.

# To increase log buffer
adb logcat -G 32M

# To enable WiFi verbose logging
adb shell cmd wifi set-verbose-logging enabled

# To enable BT HCI logs
adb shell setprop persist.bluetooth.btsnooplogmode full
adb shell device_config put bluetooth INIT_logging_debug_enabled_for_all true
adb shell svc bluetooth disable
adb shell svc bluetooth enable

# To take a bugreport
adb bugreport

From just a glance at what you've pasted, it looks like when it tries to host WiFi Direct on 2.4GHz (after 5GHz fails), it causes interference with the Bluetooth connection. But it's hard to tell if this is caused by a 3rd device failing to upgrade and accidentally taking the entire hotspot down with it, or if there's an ongoing WiFi or Bluetooth scan that may be causing interference, or if it's as you said there's a hardware defect with this device.

from nearby.