InfiniTimeOrg / InfiniTimeOrg/InfiniTime
OTA update performed despite disabled in settings
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Verification
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report provides no source file, test, or firmware entry point. Start by reproducing the cancelled update followed by a forced reboot on version 1.15.0, then trace how the OTA-disabled setting is checked during reboot and installation; done means a disabled OTA cannot proceed after reboot and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100