InfiniTimeOrg / InfiniTimeOrg/InfiniTime

Firmware not Updated through bangle.js Gadgetbridge app

Open
#2,410 0 comments 0 reactions 0 assignees View on GitHub

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 issues (including closed issues) and found none was relevant.
Introduce the issue

I have Bangle.js Gadgetbridge app in android

I have pinetime 1.15.0 binary into hardware

I connected pinetime watch with gadgetbridge app and started pinetime 1.16.0 firmware update through app it successfully but it reboots with same version 1.15.0 that previously flashed before firmware update

When i see docs of pinetime that say you need to validate firmware after updating but when try to validate the firmware version it says i already validate firmware 1.15.0 that was previously loaded into pinetime through jlink

Help me how can i validate the firmware version ?

Preferred solution

No response

Version

Pinetime 1.15.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source files, tests, or entry points. Start by reproducing the update from Pinetime firmware 1.15.0 to 1.16.0 through the Gadgetbridge Android app, then trace the firmware update and validation flow. Done means identifying why the watch reboots into 1.15.0 and documenting or fixing the validation result.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp
Domain
embedded-iot, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.