Repository navigation
Conversation
The check accepted only a panthor render node, so on the OnePlus 7T Pro (renderD128 on msm_dpu, an Adreno 640 bound, freedreno in Waydroid's vendor image) it reported no GPU and the container would not start. The check still looks for panthor on every render node first, exactly as before, with the same lines. Only where none is panthor, it takes the first render node, which Waydroid binds, and accepts msm or msm_dpu when an Adreno is bound; its numbers are then checked against lxc-omamobile.conf as panthor's are. "omamobile-waydroid mesa" (and init, which runs it) skips the Mali-G710 patch only on msm; every other phone is patched as before. docs/ANDROID_APPS.md: how to run Android apps in Waydroid, per phone, from the install to troubleshooting. Its status is the OnePlus 7T Pro's run of 2026-11-05 with the port's build of this check (Android boots on the Adreno, reaches the internet through ufw, can't reach block devices or debugfs; F-Droid installs and opens from the launcher); not yet tried on the Pixel 7 Pro. Checked read-only on the 7T Pro with the port's check: "renderD128 is msm_dpu with an Adreno bound". test/all passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 19, 2026
Draft
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
omamobile-waydroid 0.1.4, plus a how-to,
docs/ANDROID_APPS.md.The check accepted only a panthor render node. On the OnePlus 7T Pro (#931) the render node is renderD128 on msm_dpu, with an Adreno 640 bound and freedreno in Waydroid's vendor image. So the check reported no GPU, and the container wouldn't start.
Pixels unchanged:
lxc-omamobile.confas it does for panthor.omamobile-waydroid mesa(andinit, which calls it) skips the Mali-G710 patch only on msm. Every other phone is patched as before.docs/ANDROID_APPS.mdcovers running Android apps in Waydroid on each phone, from install to troubleshooting.Device and build
uname -r):7.3.0-rc6-omamobile-push1-g7539ca3e06f6Checks (no phone needed)
tools/pr-check origin/mainpassestests/packages: omamobile-waydroidtest/allpassesCo-Authored-By:trailerOn the phone
userdata, weakens the storage guard, or reads registers from userspace🤖 Generated with Claude Code