• DarkRoom 0.22.1
    Benchmarks / CPU and I/O (per commit) (push) Successful in 8m35s
    Benchmarks / Frame budget (on demand) (push) Skipped
    Traceability / Requirement traces (push) Successful in 1m22s
    Build and test / Android (aarch64) (push) Successful in 46m43s
    Build and test / android-image (push) Successful in 2s
    🐳 Android image / Build and push (push) Successful in 2s
    Build and test / Desktop (Linux) (push) Successful in 1h4m43s
    Build and test / windows-image (push) Successful in 2s
    🐳 Windows image / Build and push (push) Successful in 2s
    Build and test / Layer separation (push) Successful in 34s
    Build and test / Windows (x86_64, cross) (push) Successful in 29m53s
    Build and test / Publish the release (push) Successful in 1m24s
    Stable

    dtourolle released this 2026-10-05 00:41:07 +00:00 | 21 commits to master since this release

    The tablet's NPU, for real this time: the app could never reach it, so every model ran on the processor, and AI denoise took half a minute or more a photograph.

    The tablet runs its models on the NPU. The app never declared the system library that carries its requests to the NPU, and recent Android versions refuse such a library to an app that does not ask for it by name. The NPU could not start, and the models meant for it — AI denoise, face detection, face landmarks, segmentation, scene recognition, keypoints and the panorama border fill — ran their NPU forms on the processor instead, in every release that claimed otherwise. The app now declares it. On the tablet AI denoise with Best takes about 10 s a 20-megapixel photograph instead of 30 s to two minutes, and the other models move to the NPU with it.

    A failed NPU no longer sticks. At launch the app checks which hardware runs its models fastest. When the NPU could not start, that check timed the processor standing in for it, judged the NPU slower, and kept the verdict for good. The check now fails cleanly when the NPU cannot take a model, and a verdict that fell back to the processor is checked again on the next few launches before it is kept. A tablet left on the processor by 0.22.0 checks again once this version is installed; nothing needs clearing.

    Faster release builds. The interface crate compiles on sixteen threads instead of one, which cuts about ten minutes from a release build. Nothing changes in the app.

    The APK, the desktop binary, the Windows installer and SHA256SUMS are built by CI from this tag's commit.

    Downloads