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.

Minecraft Bedrock handheld port 2.0.0-rc.13

Diagnostics only — the port payload is identical to rc.12. If rc.12 works for you, this changes nothing about how the game runs; it changes what Self test tells you, and it makes five tests that were silently skipped actually run.

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

The self test reported a runtime as missing while it was mounted. It looked for the Weston package only in PortMaster's own libs/ and runtimes/, which is where Knulli and Batocera install it. A firmware whose PortMaster does not carry it — muOS ships an empty libs/ — downloads and verifies it into the port's own runtime/ directory instead, and the self test never looked there. On muOS the warning could therefore never clear, no matter what you did. Found by running Self test on a device that had just downloaded, verified and mounted that package; the report on it now reads 17 ok, 1 warning, 0 failures.

Five contract tests had never executed. tests/test_cfw_contracts.py collects its tests out of globals() from an if __name__ == "__main__" block, and five had been appended after that block, so they did not exist yet when it ran — the muOS PortMaster redirect, the message ladder, the frontend stop/restart pairing, the interpreter check and the downloader gate parity. Every one was written this month to hold the muOS work in place, and none was being enforced, in CI either. The runner moved to the end of the file, with a comment saying why it stays there. All fifteen pass, and deliberately breaking one of the late tests now fails the run.

If you are 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. Everything there applies to this release.

Which file do I download?

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

Already running rc.12? Update port in the launcher menu 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.

What was verified, and what was not

Verified on hardware: rc.12 was installed on an RG34XX-SP running muOS 2601.0 through Update port itself, and the self test fix was confirmed on that device. Knulli and ROCKNIX reference devices continue to pass.

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

Known limits: the failsafe ladder's FS-1, FS-2, FS-5 and FS-9 still need firmwares nobody on the project owns. A volunteer on dArkOS running Self test remains the single most useful thing anyone could contribute.

Minecraft Bedrock handheld port 2.0.0-rc.12

muOS now plays Bedrock, with no PC involved. 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.

If you are on muOS

rc.11 and everything before it opened to a black screen on muOS and dropped back to the menu. Nothing had crashed: no Bedrock version was installed, the launcher said so, and muOS renders no console for it to say it on. That is fixed, along with everything that was hiding behind it.

On an RG34XX-SP running muOS 2601.0 (JACARANDA) the port now signs you in to Google on the handheld, downloads your purchase, installs it and plays it. From that session's boot report:

cfw=muos (explicit, CFW_NAME=muOS, os=muOS)
graphics=backend=mali compositor=none
audio=backend=pipewire alsa=1 pulse=0 pipewire=1
failsafe=rung=0 (tuned) floor=0 pinned=0
bedrock=1.16.221.01 code=971622101 abi=arm64
exit_status=0 after 488s (success)

Controls and sound both work.

Getting your APK on the device

Get APK from Google Play in the launcher menu signs you in on Google's own page, downloads the build you choose, validates it and installs it. You need Wi-Fi, about 1.5 GB free for the one-time browser runtime, and the Google account that owns Minecraft. Your password is only ever typed into Google's page.

This is a prototype, limited to 64-bit H700 devices on muOS, Knulli or Batocera — RG34XX-SP, RG35XX-H/Plus/2024 and relatives. The tile is greyed out elsewhere, which is not a bug: the sign-in browser needs a graphics path only those devices are proven on. Everyone else uses the Windows or Linux helper below, as before.

What was actually wrong

Eight faults, each hiding the next. In order:

1. PortMaster resolved to a stub. muOS ships /roms/ports/PortMaster holding only a control.txt that redirects at the real install. The launcher discarded that redirect and found no LOVE runtime, which removed the only route to installing an APK.
2. The message explaining it was invisible. show_msg wrote to /dev/tty1; muOS binds no framebuffer console. Messages now fall back to a LOVE frame, then to painting /dev/fb0 directly with the port's own font.
3. The downloader was gated to Knulli and Batocera, and behind the gate sat a real dependency: muOS has no Mesa. The same upstream package is now fetched and SHA-256 verified the way the Weston runtime already was.
4. Two firmware gates had drifted — the menu greyed the tile out from its own copy of the list. A test now fails if the two disagree.
5. muOS ships no 64-bit libcom_err.so.2, which the sign-in helper needs. The pinned Weston package carries it.
6. Crusty was never told where SDL is, so the sign-in helper died on its first SDL call, on every firmware — nothing had been setting $CRUSTY_LIBSDL.
7. The sign-in browser rendered nothing. Its Chromium renderer had no capabilities and could not allocate the shared memory a composited page arrives in.
8. Two more on the way in: a second muOS frontend drew over the running port and stole its input, and the sign-in window could not find the gamepad, because muOS calls it muOS-Keys where Knulli calls it Anbernic RG34XX-SP Controller.

Full detail, with the measurements behind each one, is in CHANGELOG.md and PR #13.

Which file do I download?

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

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.

What was verified, and what was not

Verified on hardware for this release: the muOS session above, end to end. Knulli and ROCKNIX reference devices continue to pass.

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

Known limits: the failsafe ladder's FS-1, FS-2, FS-5 and FS-9 still need firmwares nobody on the project owns — an armhf 1.16.x build, the rk3326 and generic affinity profiles, and the ArkOS/KMSDRM display path. A volunteer on dArkOS running Self test remains the single most useful thing anyone could contribute.

If the port does not work on your device, run Self test from the launcher menu first. It prints a short redacted report that is safe to paste into an issue.

Minecraft Bedrock handheld port 2.0.0-rc.11

Cross-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 writes logs/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
  uname instead 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 rewriting 1.16.221.01 to
  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

Minecraft Bedrock handheld port 2.0.0-rc.10

Channel: testing

Testing channel release. Final R36S and revised RGDS physical acceptance checks remain pending; this release adds no stable or newly Validated claims. The automated gates — host tests, pinned container client builds, reproducible double-assembly, and the release-safety scan — all pass.

What is new in rc.10

Both Google Play downloaders — the optional on-device one and the mcbedrock-get helper — now have their safety rules written down and enforced by CI rather than stated in prose.

• DOWNLOADER-POLICY.md states the three rules: strictly open source, no hardcoded bypass or cracked licence, and no user credential stored on or transmitted through a third party. scripts/check_downloader_policy.py checks all three on every push.
• Provenance manifests. Every binary shipped with the downloader is declared with its SHA-256, size, upstream commit or in-repo source, licence and build script. An undeclared or rebuilt binary now fails the build. The Windows bundle carries its own PROVENANCE.json beside the executable.
• The helper's Play client is pinned. setup-downloader.sh previously cloned whatever the upstream default branch held that day, so the source behind a built binary could not be named afterwards. It now checks out one pinned commit — the same revision the port's ARM64 gplaydl is built from.
• The saved Google token is now owner-only. It was written at the default mode, which on Linux left a live account token readable by every other user on the machine. It is now 0600 inside a 0700 directory on both platforms.
• Three credential-hygiene leaks closed. A cancelled sign-in no longer leaves Google's one-shot token on the card; sign-out now clears the sign-in capture, exchange input and Qt diagnostic logs; and support bundles — which people attach to public issues — now redact email addresses, Google token prefixes, CRED=/CREDB64= lines and spaced user_token = ... assignments.

Also fixed: two documented %LOCALAPPDATA% paths contained literal control bytes instead of backslashes, printing as mcbedrock-getccount.json and mcbedrock-getersiondb\ in the section explaining where your account token is kept.

Known and documented in the policy: the shipped ARM64 binaries are not reproducible builds, and the sign-in window runs Qt WebEngine with its sandbox disabled.

Carried forward

• Separate standard and RGDS products; the standard archive contains no dual-screen runtime, while RGDS is arm64-only for ROCKNIX/Sway.
• Bedrock 1.16.221.01 remains recommended for performance and handheld UI scaling. The fingerprinted original 1.21.51.01 is the newest tested alternative; 1.26+ is unsupported.
• The Windows helper sets itself up from one button and offers every Bedrock version Google Play still serves. Verify its SHA-256 before allowing an antivirus exception.
• RGDS maps local worlds. LAN client sessions retain live telemetry and show remote terrain as unavailable instead of reusing cached local tiles.

Verifying

Every asset's SHA-256 is in SHA256SUMS.txt. The reproducibility job assembles the release twice and requires the two to be byte-identical.

Legal

No game files are included. Users must supply an official Minecraft Bedrock Android APK or complete split set from an account that owns it.

NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED BY OR ASSOCIATED WITH MOJANG OR MICROSOFT.

Minecraft Bedrock handheld port v2.0.0-rc.9

Bedrock on your handheld. No game files are included — you supply your own
Google Play copy, and the helper below is how you get it.

Which download?

You have	Take
Any normal PortMaster handheld	Standard edition
An Anbernic RG DS	RGDS edition (dual-screen, arm64 only)
A Windows PC, and no game files yet	Windows APK helper (.zip)
A Linux PC, and no game files yet	Linux APK helper (.AppImage)

Extract the port archive at the root of the storage holding your ROM folders,
refresh the Ports list, and launch Minecraft Bedrock once. Then use the
helper on a PC to download your own copy, put the files in
ports/minecraftbedrock-data/apk/, and choose Install APK.

What changed

You can now install the versions the browser offers you

rc.8 let you browse all 969 builds Google Play still serves. It just would not
install about 850 of them.

Picking, say, 1.14.60.5 downloaded 200 MB, unpacked the game code and assets,
hashed the game library — and only then said unsupported: outside the evidence-based 1.16-1.21 range. The check was the last thing the installer did.

Now the range is checked before any work happens, and being outside it is a
question rather than a verdict:

1.14.60.5 is outside the tested 1.16-1.21 range.
It may fail to install, or install and not launch.
                                   [ Install it anyway ]

Two kinds of "no" are now told apart:

• Blocked — the port cannot run it whatever you want. PairIP licensing
  (1.26 and newer) and unparseable version strings. No confirmation unlocks
  these, because there is nothing behind the door.
• Untested — nobody has run it here. That is your risk to take, and the
  version browser exists so you can take it. Untested builds record themselves
  as such in version.json, so a later bug report can say what it was.

Downloads are not asked twice: the download screen already carries the warning
and confirms there.

Reinstalling something you already have is not an error

Choosing a version that is already installed reported APK setup failed: version already installed. It now says so plainly and leaves the existing copy
alone.

Status

Testing channel. Final R36S and revised RGDS physical acceptance checks remain
pending, and nothing here is promoted to stable or newly labelled Validated.

Untested builds are untested. Outside 1.16–1.21 there is no evidence either
way, and 1.16.221.01 remains the build to pick if you want one that works.

Verify downloads against SHA256SUMS.txt. Neither helper is code-signed, so
SmartScreen and antivirus heuristics may complain about the Windows one.

NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED BY OR ASSOCIATED WITH MOJANG
OR MICROSOFT.

Minecraft Bedrock handheld port v2.0.0-rc.8

Superseded by v2.0.0-rc.9

Nothing here is broken, but this release offers you every Minecraft version
Google Play serves and then refuses to install most of them — the range check
ran only after the download and the full unpack had already happened.

rc.9 asks first, and lets you go ahead. Install rc.9 instead.

---

Bedrock on your handheld. No game files are included — you supply your own
Google Play copy, and the helper below is how you get it.

Which download?

You have	Take
Any normal PortMaster handheld	Standard edition
An Anbernic RG DS	RGDS edition (dual-screen, arm64 only)
A Windows PC, and no game files yet	Windows APK helper (.zip)
A Linux PC, and no game files yet	Linux APK helper (.AppImage)

Extract the port archive at the root of the storage holding your ROM folders,
refresh the Ports list, and launch Minecraft Bedrock once. Then use the
helper on a PC to download your own copy, put the files in
ports/minecraftbedrock-data/apk/, and choose Install APK.

What changed

All of it is the on-device launcher menu. The game, the client binaries and the
PC helpers are unchanged from rc.7.

Holding up or down scrolls

Get APK from Google Play → Other versions lists every build Google Play
still serves — over a hundred for ARM64 alone — and until now each one had to
be stepped past with its own button press. Hold a direction and it repeats: ten
rows a second, speeding up to twenty-five after a second of holding. A single
tap still moves exactly one row.

Left and right still switch ARM64/ARM32 on one press; they deliberately do not
repeat.

Every version says what it is

Each row now carries the same labels the desktop helper shows in its columns:

1.16.221.01 [ARM64]
RECOMMENDED | No RenderDragon | Bedrock | Nether Update

1.21.132.1 [ARM64]
AVOID: RenderDragon | Bedrock | Tricky Trials | Tiny UI

• RenderDragon is called out both ways round. Builds that use it stutter
  badly on this hardware and are marked AVOID; builds that don't say No
  RenderDragon, because that is a reason to choose one.
• Bedrock or Pocket Edition. Pocket Edition is a different, older game,
  and it is touch-only — the row says so, because a handheld's buttons will not
  work in it.
• The named update it belongs to: Nether Update, Trails & Tales, and so on.
• Tiny UI on anything newer than 1.16.221.01, whose interface is the most
  readable on a small screen.

The Play code moved off the row to make space for these. It is still on the
confirmation screen, along with the full warning for the build you picked.

1.16.221.01 remains the one to pick unless you have a reason not to.

Fixed: text running into the lines around it

Four places placed text at fixed fractions of the screen rather than measuring
it, and the overflow landed on the borders:

• The header's port version had a 92-pixel limit for a 135-pixel string, so it
  wrapped and the second line sat on the accent rule under the header.
• The subtitle could wrap the same way. It cleared by one pixel at 720px wide
  and did not fit at all at 640px.
• List rows put a title and a description in a row too short to hold both, so
  descriptions ran under the titles and through the row's own bottom border.
• The 1/111 position counter was aligned to the screen edge while the list
  frame stops short of it, so it was drawn across that frame's border.

These are now sized from the font's metrics, and trimmed rather than wrapped.
Rows are never shorter than the text they hold.

Faster to draw

The menu backdrop's dot grid and scanlines were about 1500 individual draw
calls every frame. They never change, so they are now baked once into a single
batch — worth having when a held direction redraws the list continuously.

Status

Testing channel. Final R36S and revised RGDS physical acceptance checks remain
pending, and nothing here is promoted to stable or newly labelled Validated.

Verify downloads against SHA256SUMS.txt. Neither helper is code-signed, so
SmartScreen and antivirus heuristics may complain about the Windows one. The
Linux sign-in window has not yet been exercised on a real desktop; if it
misbehaves, please open an issue at
mcbedrock-get.

NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED BY OR ASSOCIATED WITH MOJANG
OR MICROSOFT.

Minecraft Bedrock handheld port v2.0.0-rc.7

Superseded by v2.0.0-rc.8

Nothing here is broken — rc.8 is rc.7 plus a much better version browser:
holding up or down scrolls instead of one press per row, every build says
whether it is RenderDragon, Bedrock or Pocket Edition, which named update it
belongs to and whether its UI is tiny, and several places where menu text ran
into the lines around it are fixed.

Install rc.8 instead. Your worlds and installed versions are untouched by the
upgrade.

---

Bedrock on your handheld. No game files are included — you supply your own
Google Play copy, and the helper below is how you get it.

If you are on rc.5 or rc.6, update. Those two will not start on a device
whose shared data directory is hidden (.minecraftbedrock-data), which is how
Knulli keeps it out of its recursive Ports inventory. They refuse to launch
rather than risk your data — but they refuse, and rc.4 did not. This release
fixes that and is otherwise identical to rc.6.

Which download?

You have	Take
Any normal PortMaster handheld	Standard edition
An Anbernic RG DS	RGDS edition (dual-screen, arm64 only)
A Windows PC, and no game files yet	Windows APK helper (.zip)
A Linux PC, and no game files yet	Linux APK helper (.AppImage)

Extract the port archive at the root of the storage holding your ROM folders,
refresh the Ports list, and launch Minecraft Bedrock once. Then use the
helper on a PC to download your own copy, put the files in
ports/minecraftbedrock-data/apk/, and choose Install APK.

Fixed

The port starts again on devices with a hidden shared-data directory. The
migration step understands both minecraftbedrock-data and the hidden
.minecraftbedrock-data once more. rc.5 and rc.6 shipped a version that knew
only the visible name and stopped with:

shared-data migration: …/apk points to unexpected target
Shared-data migration failed without overwriting user data.

Found by installing rc.6 on a real RG34XXSP that had been running rc.4 happily.

Also in this release, if you are coming from rc.4

The APK helper now runs on Linux

One file, about 26 MB: download it, chmod +x, run it. It works the same as on
Windows, minus the parts Windows only needs in order to have a Linux to run
in — no subsystem, no Ubuntu to install, so setup is two steps instead of four.
The downloader is still built on your own machine from
Google-Play-API, using
apt, dnf or pacman, with a single graphical authorisation. Only that package
install is privileged; the build runs as you.

The sign-in window uses your system's GTK/WebKit rather than bundling a browser
engine, which measured 525 MB against 58 MB for everything else.

The Windows helper offers every version

It lists every Minecraft build Google Play still serves for your architecture,
scrollable and searchable, each row saying what it is: Bedrock or Pocket
Edition, which named update, and whether it uses RenderDragon — those stutter
badly on handhelds and are marked. 1.16.221.01 is still the one to pick.

Setup there is one button now, and signing in no longer asks for your email
twice.

Fixed

• mcbedrock-get --list | head ended in a BrokenPipeError traceback. It exits
  quietly now, and Ctrl-C does too. This affected Windows as well, since rc.3.

Status

Testing channel. Final R36S and revised RGDS physical acceptance checks remain
pending, and nothing here is promoted to stable or newly labelled Validated.

Verify downloads against SHA256SUMS.txt. Neither helper is code-signed, so
SmartScreen and antivirus heuristics may complain about the Windows one. The
Linux sign-in window has not yet been exercised on a real desktop; if it
misbehaves, please open an issue at
mcbedrock-get.

NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED BY OR ASSOCIATED WITH MOJANG
OR MICROSOFT.

Minecraft Bedrock handheld port v2.0.0-rc.6 (withdrawn - use the latest release)

⚠️ Withdrawn — use v2.0.0-rc.7 instead

This release will not start on some devices. If your shared data
directory is the hidden .minecraftbedrock-data — which is how Knulli keeps
it out of its recursive Ports inventory — the port refuses to launch with:

shared-data migration: …/apk points to unexpected target
Shared-data migration failed without overwriting user data.

Nothing is damaged: it refuses precisely so that it does not touch your
worlds or installed versions. But it will not run, and rc.4 did.

rc.5 is affected in the same way. rc.7 fixes it and is otherwise
identical. Found by installing this release on a real RG34XXSP.

---

Bedrock on your handheld. No game files are included — you supply your own
Google Play copy, and the helper below is how you get it.

Which download?

You have	Take
Any normal PortMaster handheld	Standard edition
An Anbernic RG DS	RGDS edition (dual-screen, arm64 only)
A Windows PC, and no game files yet	Windows APK helper (.zip)
A Linux PC, and no game files yet	Linux APK helper (.AppImage)

Extract the port archive at the root of the storage holding your ROM folders,
refresh the Ports list, and launch Minecraft Bedrock once. Then use the
helper on a PC to download your own copy, put the files in
ports/minecraftbedrock-data/apk/, and choose Install APK.

What changed since rc.5

Nothing that runs on the device. The port binaries, scripts and runtime are
unchanged. Everything below is the PC-side helper.

The helper now runs on Linux

One file, about 26 MB: download it, chmod +x, run it. It works the same as on
Windows, minus the parts Windows only needs in order to have a Linux to run
in — no subsystem, no Ubuntu to install, so setup is two steps instead of four.
The downloader is still built on your own machine from
Google-Play-API, using
apt, dnf or pacman, with one graphical authorisation.

The sign-in window uses your system's GTK/WebKit rather than bundling a browser
engine, which measured 525 MB against 58 MB for everything else.

Fixed

• mcbedrock-get --list | head ended in a BrokenPipeError traceback. It
  exits quietly now, and Ctrl-C does too. This affected Windows as well.

Status

Testing channel. Final R36S and revised RGDS physical acceptance checks remain
pending.

NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED BY OR ASSOCIATED WITH MOJANG
OR MICROSOFT.

Minecraft Bedrock handheld port v2.0.0-rc.5 (withdrawn - use the latest release)

Bedrock on your handheld. No game files are included — you supply your own
Google Play copy, and the Windows helper below is how you get it.

Which download?

You have	Take
Any normal PortMaster handheld	Standard edition
An Anbernic RG DS	RGDS edition (dual-screen, arm64 only)
A Windows PC, and no game files yet	Windows APK helper

Extract the port archive at the root of the storage holding your ROM folders,
refresh the Ports list, and launch Minecraft Bedrock once. Then use the
helper on a PC to download your own copy, put the files in
ports/minecraftbedrock-data/apk/, and choose Install APK.

What changed since rc.4

Nothing that runs on the device. The port binaries, scripts and runtime are
unchanged; only the packaged README differs. If rc.4 works for you, rc.5 behaves
identically.

Everything new is in the Windows helper:

• Setup is one button. It used to mean an administrator PowerShell, a typed
  command, a restart, inventing a Linux username and password, and typing that
  password into a terminal. All gone — it installs what it needs itself and
  shows progress in the window.
• It says it is installing Linux, first. Getting Minecraft out of Google
  Play needs a Linux program, so the helper installs Ubuntu to run it in. It
  now explains that up front — what it installs, how big it is, and how to
  remove it — and asks before doing anything.
• Any version you like. Instead of nine buttons it lists every Minecraft
  version Google Play still offers for your device, scrollable and searchable,
  and marks what each one is: red for the RenderDragon builds that stutter on
  handhelds, Pocket Edition for the touch-only ones below 1.2, ★ for the
  versions people have actually tested. 1.16.221.01 is still the one to pick.
• Signing in is simpler, and no longer asks for your email twice.

The install instructions in the README and
GETTING-BEDROCK-APKS.md
have been rewritten to match, in plainer language.

The helper also has its own home now —
DankMiimer/mcbedrock-get — where
it is released and where its issues live. Its newest build is always there,
while the copy attached here only refreshes when the port does.

Status

Testing channel. Final R36S and revised RGDS physical acceptance checks remain
pending, and nothing here is promoted to stable or newly labelled Validated.

Verify downloads against SHA256SUMS.txt. The Windows helper is unsigned, so
SmartScreen and antivirus heuristics may complain about it.

NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED BY OR ASSOCIATED WITH MOJANG
OR MICROSOFT.