Skip to content

v0.4.0: instance rename, live RAM lowering, second install validated end to end

Choose a tag to compare

@fogelmanjg fogelmanjg released this 31 Oct 01:21
· 77 commits to main since this release

A second real install (jgustavo46, AMD Polaris) was brought up from scratch and exercised end to end against this release line -- not just the project's own dev host any more. Every fix below was found live on that second machine, several only because it exists: a hardcoded personal path, a missing per-host env var, a rename-then-restart sequence nobody had tried yet.

Added

  • Instance rename (pencil icon next to the name, PUT /api/instances/:id/name): renames the instance and, cosmetically, the underlying Docker container's own --name too. Validates and uniqueness-checks the new name; id, data volume and running state are untouched. Names are normalized automatically (lowercased, spaces/underscores to hyphens, disallowed characters stripped) instead of being rejected outright -- applies at creation too.
  • RAM can now actually be lowered on a running instance: stops it, applies the lower cap, restarts it, with a confirmation prompt first. Previously blocked outright. Raising RAM live is unchanged.
  • Doctor warns when hwenc is encoding all-intra (REDROID_FORGE_ENCODE_IDR_PERIOD unset, AMD for now) instead of using P-frames.

Fixed

  • Renaming an instance could permanently break its ability to ever restart -- meminfoFix's bind-mounted file was keyed by the renamable name, but a container's HostConfig.Binds is a path string frozen at creation time. Re-keyed everything off the immutable volumeName instead.
  • An instance that gained the gapps module after creation never had hasGapps recomputed on recreate, hiding the Android-ID registration flow.
  • Auto-refresh closed the inline rename editor mid-type.
  • A washed-out/low-quality scrcpy picture on the second install was live-misdiagnosed as an H.264 colour-matrix bug (two different VUI/matrix attempts changed nothing) before the real cause -- P-frames never enabled on that host -- was found. Confirmed live at both 8Mbps and 1Mbps once set.
  • REDROID_HWENC_ARTIFACTS_DIR silently fell back to this project's own author's personal AOSP build path when unset.
  • VA-API daemon's native build (Makefile) was missing -lm, a link failure on at least one host's toolchain.
  • Doctor/README pointed at a custom image build instead of the public Docker Hub default.
  • README now flags AMD Polaris as not recommended for hardware decode at the same time as hwenc.

Full diff: v0.3.1...v0.4.0