Compatibility is an identity check
Same name.
Different ring.
Colmi model names span multiple firmware and silicon lineages. “R02” is a starting point for discovery—not enough information to choose an image.
Read what the device reports.
Capture the Device Information firmware revision and hardware revision before doing anything with firmware. Match them to a documented baseline and its exact image hash.
DIS strings are firmware-controlled, not an immutable chip ID. A matching string is a necessary compatibility check, not proof of the physical silicon or an unmodified image.
Read-only identity inspection
ring info --name desk-ring --jsonA missing discovery result is not an unsupported-firmware verdict. Check device advertising, existing connections, identifier freshness and host Bluetooth authorization separately.
What has actually been established?
Hardware identities below are drawn from the repository’s catalogue. Evidence labels are curated from the research records: a catalogue UI label such as “recommended” is not itself proof of a hardware test.
| Marketed as | DIS hardware family | Evidence | What that means |
|---|---|---|---|
| Newer R02 | RT02R_V3.1RT02R12_V3.1 | Community result | About 50 Hz reported on compatible RT02R/RT02CR hardware. Exact identity still matters. |
| R02 charging-case variant | RT02CR_V3.1RT02R12_V3.1 | Community result | Compatible low-latency image; an exact RT02CR stock restore is not yet in this catalogue. |
| R06 | R06_V1.0 | Hardware canary | Adopted, accel-only, approximately 15 Hz on one tested ring. Not a fleet-wide stability guarantee. |
| Newer R10 | RT03CR_V1.0 | Hardware canary | Version-distinguishable modified image adopted. Exact vendor stock is retained for recovery. |
| Older R10 / R03 family | RY03CR_V1.0 | Review only | Mapped raw producer, packet suppression and queues. Hardware acceptance remains pending. |
| R09 | RT09_V3.1 | Review only | Exact stock and a deterministic low-latency candidate. Not yet hardware-validated. |
| R12 | RT11CR_V1.0 | Active research | Old de-load edits hit the wrong path. One physical C0 LUT read passed; BF/display control and the raw24 candidate are not hardware-validated. |
The table does not grant flash permission. Results apply to the stated family and test scope; rates are approximate where reported.
Older paths & unknown lineages
Older BlueX R02
The older R02_V3.0 family uses the standard image container. Modified accel-only streaming reached roughly 40 Hz in short captures, but long-link stability was not established. Do not transplant those images to a newer R02.
R03 / RY02
Historical transfer-then-rollback observations remain useful. The old signing-key/SWD-only explanation is not a settled conclusion after the nested-Realtek activation discovery. New acceptance needs its own exact-device evidence.
RT12COL
RT12COL_V1.0, seen on a ring sold as R02, is not in the existing compatibility allowlists. It has no reviewed stock/candidate pair in this catalogue. Its similar prefix is not permission to treat it as RT11CR or RT02CR.
Unknown family means stop. Do not add a new hardware string to an old image’s allowlist just to make a flash button available.
Recovery is part of compatibility.
A stock image for a neighbouring family is not your recovery image. For example, RT02R stock and recovery images exist, but that does not make them exact stock restores for RT02CR. A promising low-latency result does not erase this gap.
Before any device-specific canary: preserve exact stock, confirm identity and battery/readiness, make the candidate version-distinguishable, and decide how to measure adoption and behaviour. A completed progress bar proves transfer—not that the new image booted.