Minecraft Bedrock handheld port 2.0.0-rc.11
Pre-releaseCross-firmware reliability work. Testing pre-release — see what was and was
not verified at the bottom before installing.
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.
New: Self test
The launcher menu has a Self test entry (or bash selftest.sh over SSH). It
checks firmware, panel, client, runtimes, audio, controls, storage and installed
versions without starting Minecraft or needing an APK, and prints a short
redacted report that is safe to paste into a bug report.
If the port does not work on your device, run this first — it will usually say
why, and it is the fastest way to get a fix.
If a launch freezes
Two things changed for the case where the game hangs and the handheld needs a
power cycle:
- A startup watchdog supervises every launch. If the client stops making
progress it writeslogs/hang-report.txt, terminates it, and restores the
frontend rather than leaving you stuck. It waits for a stall rather than
enforcing a deadline, so a slow first launch on a cold SD card is not killed. - Every launch records the stage it reached in
logs/stage.txt, overwritten in
place so it survives pulling the power. After a freeze, the next launch reports
where the previous one stopped.
Between them, a hang now leaves evidence instead of nothing.
If a launch fails to start
A failsafe ladder drops to a conservative launch profile (no CPU/GPU tuning,
no thread pinning, VSync on, 30 fps) and, if that also fails, to a minimal one
(X11 video, no Crusty context hand-off, sound off). Two clean launches climb back
to normal by themselves.
Anything above the normal profile is announced on screen with the reason and how
to overrule it. Pin it yourself with Safe mode in the menu. docs/FAILSAFES.md
lists every fallback and the evidence needed to remove it again.
Fixes
- The game exits before the character menu when Wi-Fi is on. Old Bedrock
builds crash if they think the network is up. The in-client guard only ever
covered one arm64 binary, and the compatibility registry claimed it for three
combinations where it cannot fire. The registry is corrected and the launcher
now covers the gap. Network / LAN in the menu overrides it if you would
rather keep LAN. - No sound on the 32-bit path. It selected no audio backend at all, so
OpenAL tried PipeWire first and failed twice on images that ship the PipeWire
libraries without a client config. Both launch paths now share one audio
selection. - Wrong client chosen on mixed-architecture systems. ABI selection asked
unameinstead of whether the loader the client needs actually exists. - Menu input dead on some firmwares. The input helper was pointed at a
process name that does not exist there. - Support bundles were deleting version numbers. Bedrock versions look like
IP addresses, so the privacy filter had been rewriting1.16.221.01to
REDACTED_IP— removing the most useful field from every bundle. Fixed, with
addresses, emails and credentials still removed.
Also
The port now resolves which firmware it is on in one place instead of four
drifting copies; ROCKNIX and the ArkOS family have an identity for the first
time. The bug report template asks for the self test and how far the launch got.
docs/CFW-CONTRACTS.md records what each firmware requires and marks every
clause as measured or assumed.
What was verified, and what was not
Verified on reference hardware:
- RG34XX-SP / Knulli and RG DS / ROCKNIX — launch and clean exit from the
on-device menu with controller input, correct firmware/profile/panel/audio
detection, watchdog disarming at the first frame, frontend restored with no
leftover processes, and the failsafe ladder staying at the normal profile.
Not verified:
- muOS and dArkOS/ArkOS have no reference device. Their support is derived
from user reports and code, not measurement. The self test exists to change
that — running it on those firmwares is the single most useful thing you can
contribute. - Text entry, immediate relaunch, and a full controls re-check on both devices.
- The RGDS LAN transition and companion-tab rows of the acceptance checklist
were not re-run against this build.
TESTING.md carries the full per-firmware acceptance checklist and the current
state of every row.
Checksums
1a472f9fceae06b7ed74a1d236fe3fa74628c4920629f1c59f53d56071337560 minecraftbedrock-standard-v2.0.0-rc.11.zip
f6a7d8539120151faf5b2dc0c320cd53c14f04c43ab84acd736bb91807c4a6ca minecraftbedrock-rgds-v2.0.0-rc.11.zip
f976fa480aa0d597c1ee31a2c13d48b0790c1b0ca856ae1f698b4ce83393f65a minecraftbedrock-source-v2.0.0-rc.11.zip
ce54f5ca4334a1e3755e56073c6be9dd0826c2646a3a0e65101200f58701c759 minecraftbedrock-standard-v2.0.0-rc.11.spdx.json
f101a8e5f5952996fa41e6b9b8e4642aff0be3528107aa20d730315ceb842b4f minecraftbedrock-rgds-v2.0.0-rc.11.spdx.json
330b17fbae58cb1d93d581e010d6726e2c233c831935a27c4327fd9f7c3f37b0 mcbedrock-get-windows-v2.0.0-rc.11.zip
abf6a6f88149b3c8a61a75b813604e042b6c887f228bc045a41a4bc90f4b241c mcbedrock-get-linux-x86_64-v2.0.0-rc.11.AppImage