[CMGS]

The redroid 16 image now takes scrcpy-rfb from the immutable master-827baf531 release instead of the moving master release.

Why

build-os-images run 39908133499 (on 991ec16) failed only in ubuntu/22.04-redroid-16.0-gms-h264. The Dockerfile's own pin check stopped it:

scrcpy-rfb master is at 827baf531715d6b86482c7ac6c63fd31030c58aa, not the pinned 9bdf6ed2b50953589ef153c18f087bcaafc429d9

The master release is overwritten on every scrcpy-rfb master build, so the pin breaks as soon as master moves. scrcpy-rfb#11 added immutable master-<sha> releases. Pinning the tag and the commit together makes the build reproducible again.

What the bump brings in, from 9bdf6ed2 to 827baf53:

• scrcpy-rfb: clipboard both ways, meta state on keys, right button as Back scrcpy-rfb#9 (f15355898): clipboard in both directions, meta state on keys, and the right mouse button as Back.
• ci: add PR CI, SHA256SUMS and immutable tag releases scrcpy-rfb#11 (827baf531): PR CI, SHA256SUMS and the immutable tag releases.

remoteview.Dockerfile carries the same pins and gets the same bump; the README says both must move together. The README sentence now describes the tag pin.

Checks

• master-827baf531 build-info.json: "commit": "827baf531715d6b86482c7ac6c63fd31030c58aa".
• Each asset the Dockerfile fetches (scrcpy-rfb-linux-{amd64,arm64}, scrcpy-server-secure.jar, su1000-linux-{amd64,arm64}) is in the release. Each passes sha256sum -c against its .sha256 file and matches its line in SHA256SUMS.
• A local docker build --platform linux/arm64 -f remoteview.Dockerfile runs the same fetch block, passes the pin check and all three sha256sum -c checks, and installs the expected digests.
• Acceptance after merge: an Android box smoke on the published image (stream, tap, text, Back), since fix: support aarch64 by disabling io_uring and auto-decompressing gzip kernel #9 changes input handling.