Here's something that might help any of you who might be irritated by B4A-Bridge losing connection frequently. I started experiencing this a few months ago and tried everything to not make it disconnect, or to make it reconnect after it did. It was taking valuable time away from my app development. Looking here on the forum, it was clear that there were no B4A-Bridge bugs to speak of, and Erel always insisted disconnections were a user problem. The way I would usually get it to return to working OK for awhile was to exit B4A and then reenter, or to restart my Windows 11 laptop.
I just recently realized that the problems had seemed to start around the time I got my Google Pixel Watch 3, which I'm always wearing and is usually positioned close to may development device, to which it's paired. During a disconnect, I went into the Watch settings and disconnected Bluetooth, WiFi, and Mobile - and B4A-Bridge reconnected no problem (just doing Airplane Mode didn't work)! So this has been my solution lately - and it was also becoming a pain.
This morning, B4A-Bridge disconnected again. I took the Watch off my wrist and took it into the other room, without adjusting any of the settings, just to see if that would also do the trick. And it did! The connection has been stable for hours. So my conclusion is that somehow, the smartwatch connection interferes with B4A-Bridge when it's in close proximity to the target device. Maybe it's just a Google Pixel Watch 3 problem, but I kind of doubt it.
I just recently realized that the problems had seemed to start around the time I got my Google Pixel Watch 3, which I'm always wearing and is usually positioned close to may development device, to which it's paired. During a disconnect, I went into the Watch settings and disconnected Bluetooth, WiFi, and Mobile - and B4A-Bridge reconnected no problem (just doing Airplane Mode didn't work)! So this has been my solution lately - and it was also becoming a pain.
This morning, B4A-Bridge disconnected again. I took the Watch off my wrist and took it into the other room, without adjusting any of the settings, just to see if that would also do the trick. And it did! The connection has been stable for hours. So my conclusion is that somehow, the smartwatch connection interferes with B4A-Bridge when it's in close proximity to the target device. Maybe it's just a Google Pixel Watch 3 problem, but I kind of doubt it.