Minecraft Bedrock handheld port 2.0.0-rc.14

Robustness, from a week on real hardware. No gameplay change from rc.13 — if rc.13 works for you, nothing here changes how the game runs. What changes is what the port believes about the machine it is on, and how much has to be working for it to launch.

NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED BY OR ASSOCIATED WITH MOJANG OR MICROSOFT. No game files are included — you supply your own legally owned Bedrock APK.

What changed

A card node with no driver behind it no longer counts as DRM. PortMaster's westonwrap.sh runs mknod /dev/dri/card0 c 226 0 on firmwares that have no DRM at all, and the node survives until reboot. So after one use of the on-device downloader, a muOS handheld reported MCPE_HAS_DRM=1 while /sys/class/drm was empty — into every boot report and support bundle. The capability probe now requires the kernel to list the card too. Measured both ways the same day: a muOS device answers 0 with the synthetic node present, and an RG DS on ROCKNIX with a real card0 and two connected DSI connectors still answers 1. No backend changed on any device — but a firmware without Mali could have been pushed onto the wrong one by a node left behind.

The launch path no longer needs a working regex engine. Memory size, panel geometry and the frontend-ancestry walk all went through awk '/re/', and Weston cleanup through pkill -f. On the muOS reference device every busybox regex path began failing with SIGILL partway through a day, and the visible result was a boot report reading memory_kb=0 with memory_tier=unknown, plus Weston and the client left running after the game exited. The game still launched — but on a device that reported nothing about its own memory. All four lookups now read the file in the shell and spawn nothing that can fail, and the Weston kill tries name-matching killall before the regex-matching pkill. Verified on that device with its awk still crashing: memory read 2027140 kB where it had read 0.

A written record of muOS. docs/CODING-FOR-MUOS.md is ten rules for changing this port against that firmware, each backed by a measurement rather than by recollection — the PortMaster stub redirect, the console that renders nothing, the frontend supervisor that becomes your own ancestor mid-launch, the Mali-only graphics stack, PipeWire without a Pulse socket, the muOS-Keys gamepad and its measured button order, the missing 64-bit libcom_err.so.2, and what busybox cannot do. tools/capture-muos.sh regenerates the whole set on any muOS device. Both live in the repository, not in the install archives.

Which file do I download?

Download	Who needs it
minecraftbedrock-standard-v2.0.0-rc.14.zip	Normal single-screen PortMaster devices; aarch64 and armhf
minecraftbedrock-rgds-v2.0.0-rc.14.zip	Anbernic RG DS on ROCKNIX/Sway; arm64 only
mcbedrock-get-windows-v2.0.0-rc.14.zip	Fetch your Google Play purchase from a Windows PC
mcbedrock-get-linux-x86_64-v2.0.0-rc.14.AppImage	The same helper for x86_64 Linux

Already running rc.12 or rc.13? Update port in the launcher installs this over it and keeps your worlds, versions and settings. Otherwise extract one port archive at the root of the storage holding your ROM folders. Do not use GitHub's generated Source code archives. SHA256SUMS.txt verifies every file here.

New here? rc.12 is where muOS became a firmware this port actually runs on — sign-in, download, install and play, entirely on the handheld. See the rc.12 notes for what that took.

What was verified, and what was not

Verified: the archives were built twice and compared byte for byte, scanned for anything that must not ship, and every published file is checksummed. The RG DS on ROCKNIX passes its self test with 17 ok, 0 warnings, 0 failures.

Verified on muOS hardware (added 2026-08-26). This release originally shipped without ever being installed on muOS, because the reference RG34XX-SP's SD card failed during the work — intermittent SIGILL and segfaults from binaries on it, a kernel oops through the filesystem layer, and it would not stay online in a card reader afterwards. That gap is now closed: on a fresh muOS 2601.0 card, this release's published minecraftbedrock-standard archive was installed, launched, signed in to Google on the device, downloaded and installed 1.21.51.01, and played. Its self test reports 15 ok, 0 failures.

Known rough edge. On muOS, downloading 1.21.51.01 took 20–30 minutes, while 1.16.221.01 on the same device and 1.21.51.01 on Knulli are both quick. The cause is not yet known — it is being investigated rather than guessed at — and the download does complete. If you hit it, let it run.

Still pending, unchanged: the final R36S and revised RGDS physical acceptance rows. Nothing here is promoted to stable or newly labelled Validated.

The most useful thing anyone could contribute remains a volunteer on dArkOS running Self test from the launcher menu, and pasting the report into an issue.