Can't connect to Gadgetbridge after Firmware 1.14 update. about infinitime

[SteveAmor]

I always end up having to pair again, after upgrades. So I remove the device from GB and Android and start afresh.

[z3t0]

I was able to get it to work by disabling and enabling bluetooth on the watch, and then disconnect and reconnect on the gadgetbridge. Hope it helps

[FreeJulianAssange]

I always end up having to pair again, after upgrades. So I remove the device from GB and Android and start afresh.

I had some time just now to play around with the watch again, removing the device & re-pairing solved the connection issue but I've stumbled upon a new issue.

When I Validate the Firmware, the watch resets itself and returns back to Firmware v1.13.

EDIT

I re-installed the bootloader (reloader-mcuboot.zip), then installed Firmware 1.14 and validated again.
The watch resets immediately but this time 1.14 firmware remained, though the Validation screen still appears like it hasn't been validated.

Compared to my other Pinetime (after validation).

[b02860de585071a2]

I always end up having to pair again, after upgrades. So I remove the device from GB and Android and start afresh.

What has worked for me on 1.13 and 1.14 is:

0. (if previously connected) Delete/forget watch in GB/Android settings
1. Connect to GB first without any bonding
2. Toggle watch BT off
3. Open pairing menu in Android settings
4. Toggle watch BT back on
5. Pair as normal through Android flow
6. Tap on watch in GB to reconnect

Pairing in Android first, attempting to bond in GB when adding the watch, or any other combination of things all seem to fail.

I'd guess there's some conflict between how GB and the OS handle device pairing, but that's beyond my expertise.

[JF002]

I also noticed that I sometimes have to remove my watch from the Android settings before being able to connect with Gadgetbridge after an update. I haven't had the opportunity to figure that out yet, unfortunately.

I'll close this issue since it appears to be resolved/worked around.

@FreeJulianAssange Feel free to open another post related to the validation issue you experienced.