InfiniTimeOrg / InfiniTimeOrg/InfiniTime

Flashing resources documentation/improvements

Open
#1,951 5 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
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
  • itd (https://gitea.elara.ws/Elara6331/itd) is currently not working too well due to this issue
  • GadgetBridge doesn't yet support uploading resources so without digging into another project and stack I'm unable to upload new resources to my sealed PineTime.
  • WatchMate does actually work for uploading resources, however it's not documented on the doc/gettingStarted/updating-software.md page. It's also somewhat unstable (I have to disconnect/reconnect/remove/etc to get a stable Bluetooth connection) and it's also not documented that Infinitime Resources.zip can't be flashed directly, it has to be unzipped into infinitime-resources-1.13.0.zip in order to work. This is distinct from InfiniTime DFU.zip which works just like pinetime-mcuboot-app-dfu-1.13.0.zip.
Preferred solution

It seems like all these things almost work, if someone could give these various items a nudge it'd help greatly.

Version

main

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

Start with doc/gettingStarted/updating-software.md and compare its existing flashing guidance with the WatchMate workflow described in the issue. Document how InfiniTime Resources.zip differs from InfiniTime DFU.zip, including the required resource archive name, and capture the relevant connection or stability caveats; done means the page covers these steps clearly.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.