Bluetooth dropped connection - not reconnecting on Samsung S23

[akapelrud]

On my Samsung S23, if RunnerUp looses connection to my Garmin HRM Dual it never reconnects. The audio queue of the lost connection is sounded once, but there doesn't seem to be any reconnects at all. I have to stop the activity to connect again.

The same setup was working flawless on my previous phone (Samsung S10) with the HRM Dual.

I have previously made some android BLE apps, and my experience is that the main android BLE API is quite buggy on many phones. I would recommend looking into using the blessed-android library for dealing with connections/reconnects. Blessed deals with all the known quirks of BLE on android and is actually quite nice to work with.

[gerhardol]

The BLE implementation should be refreshed to use the Android 5 APIs, now when Android 4.4 was dropped first
(I have got a quite annoying number of connect/disconnect messages with a cheap CooSpoo belt, so it can work...)

[akapelrud]

Bumping this.:
The front page says 'The current 2.x release support Android 4.0 and later.', but build.gradle has minSDK set to 21 (Android 5.0). I take it that the current master branch only works on android 5.0 and up.

• Would any effort I put down on rewriting the BLE backend to use blessed (android 5.0) be accepted by this project?

[gerhardol]

but build.gradle has minSDK set to 21 (Android 5.0).

Users had finally updated...

• Would any effort I put down on rewriting the BLE backend to use blessed (android 5.0) be accepted by this project?

Yes
There are changes by @roberi that I should merge soon, normally I am a little quicker. I have some changes myself too.

[Werkov]

I observe issues with the very same Garmin belt on Samsung A5 2017 (A520F). Once there's an BT connection interference (e.g. wrong contact of the belt, it stops transmitting transiently), it'll be lost till the end of the activity.

(Anecdotally, when I had Garmin Connect app installed, the belt connection seemed more stable. OTOH, I had to uninstall that app because it caused BT headphones disconnect when they're idle.)

All in all, @akapelrud be assured that there's at least one more user who'd bless fixing dropped connections.