8000
pcooke9
changed the title
UHK80 crash when pairing TV
UHK80 crash when cancelling pairing request code entry prompt
May 30, 2025
UHK80 crash when cancelling pairing request code entry prompt #1235
Comments
|
A second pairing attempt was "successful"... •I was able to enter the pairing code and added the TV to Agent's connections list. The TV showed it was paired to "UHK 80 Right NUS", but no UHK output was sent to the TV. UART_Log_(2nd attempt)Of course, I don't really know what I'm talking about, but the following section from the "UART_Log_(2nd attempt)" seems weird to me. Shouldn't "Host22" be "Host3"? (bc:7e:8b:d1:ee:19 is the TV) I only have a few BLE devices and one dongle, definitely not 22 hosts: |
|
After using "Reset device configuration" in Agent, my phone tried to pair repeatedly, even when I hit cancel on the phone. It kept trying, so I also tapped "ESC" on the UHK80, and it crashed with another error message in Agent: I also had the UART adapter connected this time: UART_adapter_output |
<
8000
div class="pr-review-reactions ">
|
And another crash when tapping "ESC" to cancel the pairing code entry prompt. Similar situation as the last, but this time my phone tried sending pairing requests immediately after importing a config, instead of using "Reset device configuration". Agent crash log: UART_adapter_output |
|
This is similar to what I experience and described in #999 although in my case the crash happens automatically if I try to pair through the Pop_OS! Bluetooth UI without me actively cancelling the pairing. I don't even get to the pairing code entry. I can manually pair through commandline calls to bluetoothctl but it is weird and tedious and doesn't always work. |
|
Terribly sorry for so long wait time!
22 (BLE HID) and 23 (USB) are placeholders for when the device is not present in the UserConfig host connection list. This is expected for newly paired devices. Eventually, Agent should maintain a "new ble hid device" placeholder just the way it does for a usb connection (which is why you see Host 23 only very rarely - as a result of invalid user config usually). The I have added some more traces, so please @pcooke9 retest with this firmware: |
Ok, that makes sense. Speaking of long wait times; I'll have to test that tomorrow. It's just about bedtime for me now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
FW v14.0.0-e70a7ca [master]
Both USBs & bridge cable connected
Dongle plugged into PC, but not in use
Tried connecting to my TV via BLE. (Samsung Q80T)
•UHK80 showed the pairing code prompt, but the TV didn't offer a pairing code.
•Tapped "ESC" to close pairing code prompt, but UHK80 restarted with the following error appearing in Agent:
The text was updated successfully, but these errors were encountered: