OTA update performed despite disabled in settings

[Andersama]

Verification

• [x] I searched for similar bug reports (including closed issues) and found none was relevant.

What happened?

Firmware update started after reboot, although disabled via settings.

What should happen instead?

Honestly, not sure if this is a bug or feature. Seemingly was reliable, except for the unexpected firmware update scare. Nothing broke.

Reproduction steps

I cancelled a firmware update because nothing appeared to be happening, could not seem to reinitiate a firmware update. Confused I force reboot the watch. Then it seemingly reconnected via bluetooth, completed the firmware upload, although the phone didn't appear to indicate such a thing was happening. Then it failed the firmware install due to the new OTA settings. So no apparent harm done.

More details?

No response

Version

1.15.0

Companion app

Gadgetbridge 0.87.1

[mark9064]

Could you clarify which version you started with and which version you flashed? 1.15 has no way to disable DFU

[Andersama]

Huh, well the side menu after what I assumed was the failed update had a menu for "Over-the-air"...so now I'm not sure what happened. I went from the 1.15 dfu provided in the releases and tried to OTA update to a build using the latest commits.

I redid the firmware update and now definitely am on the one with the latest commits because I now have the background heart rate menu. It might just succeeded flashing initially but presented an error because of the new menu? I specifically rebuilt updating the version where I could so now my watch thinks I'm on a 1.15.1, which of course doesn't exist yet. I didn't quite get it right though I've clearly lost the shake / positioning sensor, but I don't mind I was more focused on the heart rate tracker.