Maciek Tomczyński

Issue still here, basically vanilla installation of Solus 4.0, Gnome 3.32.1

My case is a bit peculiar. I've got two devices on BT 4.2. They've got two modes, first is public undirected advertising for connection with an unknown central. Second is...

More info the issue. Actual event of scanning is corrupting future connections to bonded devices. After bonding I can connect freely to multiple devices, given that I turned off scanning...

I'm not an expert in low level BLE communication but I haven't seen anything out of ordinary in HCI logs. If you're interested in the topic I'd be more than...

Here are logs and thank you! HCI logs are a bit crowded with events, please use logcat highlights to get timestamps for easier navigation. Here are steps from the issue:...

I've prepared similar log package from Android 9 where this problem doesn't occur. Differences I found after comparision: 1. For some reason OnePlus with Android 9 doesn't seem to be...

You're right, the device won't always pop up in the scans, maybe it's scanned with true random address and is interpreted by something up in the stack. But still after...

Was doing some tests with single bonded device and managed to recreate the issue only on one device, which is new for my case. Checked the logs after connecting without...

@dariuszseweryn problem has been fixed from the bluetooth device perspective. I think it's really interesting case. Straight after bonding device didn't update it's address type immidiately to correct type (random...