Wireshark with nRF BLE Sniffer often does not display the data packets when establishing a BLE connection

[Tim83]

I am using Wireshark 4.4.0 and Nordic nRF Sniffer for Bluetooth LE 4.1.1 (nRF52840-Dongle PCA10059). In Wireshark I see a device, a peripheral, sending advertising packets, and when I connect to the peripheral with my phone using the nRF app, the packets related to the connection often do not appear in Wireshark. Sometimes they do, sometimes they don’t. see the attached Image as an Example where everything works fine.

It seems as if Wireshark sometimes fails to switch from the advertising channels 37, 38, 39 to the connection channels.

Does anyone know how to make Wireshark more reliable?

I have already reinstalled Wireshark. I have also tried removing all filters, which results in a lot of traffic, but you should still be able to see the connection packets if they were there. So that didn’t help either.
And i also tried to reinstall nrfutils and reflash the Dongle with hardware flowcontrol.

[Tim83]

Hello,
I think I have figured out how to improve it.
I instructed the Atmosic chip to use only Channel 37 and also set Wireshark to scan only Channel 37.
(You just need to make sure to set Channel 37 in Wireshark first and then the device address, otherwise it always crashes for me.)
It seems that by separately scanning Channels 37, 38, and 39, the important packet is occasionally missed, so the nrf-Dongle does not see the connection.

However, it is strange how it works with other devices. I am fortunate to be able to instruct the Atmosic chip to advertise only on Channel 37.
How do you handle Peripherals that do not allow this?
Why does no one else encounter this problem?

Best regards
Tim