Hope this helps someone. Problem seems to be in dual booting.
Since I am getting error message 111
$ sudo journalctl -n 20
...
Mar 10 16:11:20 solususb bluetoothd[716]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Mar 10 16:11:21 solususb bluetoothd[716]: connect error: Connection refused (111)
...
I think that following Arch Wiki entry for dual-booting applies:
Device connects, then disconnects after a few moments
If you see messages like the following in journalctl output, and your device fails to connect or disconnects shortly after connecting:
bluetoothd: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd: connect error: Connection refused (111)
This may be because you have already paired the device with another operating system using the same bluetooth adapter (e.g., dual-booting). Some devices cannot handle multiple pairings associated with the same MAC address (i.e., bluetooth adapter). You can fix this by re-pairing the device. Start by removing the device:
$ bluetoothctl
[bluetooth]# devices
Device XX:XX:XX:XX:XX:XX My Device
[bluetooth]# remove XX:XX:XX:XX:XX:XX
Then restart bluetooth.service, turn on your bluetooth adapter, make your device discoverable, re-scan for devices, and re-pair your device. Depending on your bluetooth manager, you may need to perform a full reboot in order to re-discover the device.
Device does not connect with an error in journal
If you see a message like the following in journalctl output while trying to connect to a device:
a2dp-source profile connect failed for 9C:64:40:22:E1:3F: Protocol not available
try installing pulseaudio-bluetooth and restarting PulseAudio. This error can manifest even while using only file transfer.
https://wiki.archlinux.org/index.php/Bluetooth#Device_connects.2C_then_disconnects_after_a_few_moments
I am going to buy another BT adapter just to test if this is the case, each system will use different adapters.