Bangle.js 2 Firmware Update v2.18->v2.19 Is 'Programmable' set to Off?

After updating my Bangle.js 2 firmware to v2.19 I cannot connect with the Bangle.js Gadgetbridge App Manager on my phone anymore: Device connection failed. Is 'Programmable' set to 'Off'?

However Programmable is enabled in Settings and I can connect to the App Manager with my computer. Is this an issue for the Bangle.js Gadgetbridge app? To me it seems like something changed with the v2.19 firmware as this issue started immediately after updating the firmware using my phone.

Data transfer with phone seems broken after the firmware update: Weather report is not received by Bangle.js 2 and activity data and battery percentage is not received by the Gadgetbridge app.

I decided to try to go back to firmware v2.18, however somehow then my Bangle.js 2 came stuck in an infinite 'BOOTING...' loop like in https://forum.espruino.com/conversations­/385921/

With the special firmware updater I managed to install v2.18 again and everything is working now, think I will not touch the firmware again...

That's an odd one - were all your apps up to date? I think most people are using 2v19 now without issues.

And Gadgetbridge repeatedly complained that it couldn't connect? Or did you only try it once? Did you have any other bluetooth options set like a Pin code? I know we did add some code (in 2v19 I think) to ensure that if the pin pairing was requested, you couldn't communicate with the watch without the watch having been properly paired and I guess you might have hit that (but unpairing/repairing should have fixed it).

however somehow then my Bangle.js 2 came stuck in an infinite 'BOOTING...' loop

Sorry to hear that - was that when updating using https://banglejs.com/apps/?id=fwupdate ?

It can happen when using the DFU updater (especially from iOS) but it's rare it happens with the fwupdate app - at least (as you found) when it gets in that state you can update it with a DFU app

were all your apps up to date?

All but 4 apps were up to date

And Gadgetbridge repeatedly complained that it couldn't connect?

Yes

Did you have any other bluetooth options set like a Pin code?

Yes I have a pincode

I guess you might have hit that (but unpairing/repairing should have fixed it).

Probably, I haven't tried repairing indeed.

was that when updating using https://banglejs.com/apps/?id=fwupdate ?

Yes

I tried updating to v2.19 again (all apps up-to-date), same issue, infinite 'BOOTING...' loop again... :-(
Then I tried it again after removing the pincode and that worked.

I'm now wondering whether the pincode functionality works at all?

Interesting about the pin code. If it makes you feel any better you might have cancelled the Pin pairing process, so the phone was using the Bangle without the fully end to end encrypted connection - 2v19 fixed that, which is why you then had issues - and repairing should have fixed it.

I'm not sure I understand about the BOOTING boot loop. Initially you mentioned you got it when downgrading to 2v18, but now you're saying that you get is when going to 2v19? When it's got that BOOTING... loop did it display anything else after BOOTING... (like the Bangle.js logo or part of the watch screen?)

Do you have any other bluetooth settings enabled like Whitelist?

I'm now wondering whether the pincode functionality works at all?

Yes, it definitely does. I've just tried it again here and it works great on a watch with 2v19, even after reboot.

but now you're saying that you get is when going to 2v19?

Yes

did it display anything else after BOOTING... (like the Bangle.js logo or part of the watch screen?)

No, BOOTING... was the last line

Do you have any other bluetooth settings enabled like Whitelist?

No, Whitelist seems not to work as it always says: 'Connect device to add to whitelist' also when phone is connected.

Yes, it definitely does. I've just tried it again here and it works great on a watch with 2v19, even after reboot.

Yes it works.

Thanks for the answers.