After unlocking the Pad 6S Pro (sheng), flashing back to the official 306 build, and getting root set up, beyond “one more machine I can tinker with,” I wanted it to do some laptop things: LibreOffice, a terminal, a browser, drawing.
Let’s be clear about what this is first: this is a chroot, not native Linux. Android keeps running underneath, competing for memory and throttling the CPU, and graphics go through X11 forwarding rather than direct output. Light office work is doable; don’t count on 4K editing or big builds.
The trade-offs of three paths
- Native dual-boot (installing Linux on slot B): best performance, but you have to touch the slots. Right after unlocking and flashing the official system, the risk of switching slots counts as a separate item, and it isn’t worth it.
- Fedora + KDE: someone on sheng did do it in 2026, but it’s marked “experimental” — the repo builds
rootfs.imgon the fly with GitHub Actions, and the author was still changing it ten hours ago. Installing it is not just a matter of grabbing an ISO. - Termux + chroot: everything lives inside
/data, no partitions touched; if you screw it up, delete the directory and start over — you don’t even necessarily needreboot.
I chose the third. The Debian 13 image includes KDE Plasma; proot-distro is used once as an unpacker only, and proot is never involved again afterward.
Three pitfalls that decide success or failure
Anyone who doesn’t know these three points will hit all of them, and the symptoms all look a lot like “the performance just isn’t there.”
One: you must swap out Mesa. Debian’s bundled Mesa goes through the DRM msm driver, while the Android kernel only exposes /dev/kgsl-3d0. Installing the official Mesa directly gets you llvmpipe software rendering, and KWin is so laggy you can’t even click. You have to switch to the kgsl build from lfdevs/mesa-for-android-container (supports the Adreno 740, made for chroot use), run apt-mark hold after installing, then use glxinfo -B to confirm the renderer is FD740 / Adreno (TM) 740 and OpenGL 4.x. If all you have left is llvmpipe, it didn’t work.
Two: starting X inside the chroot has to be done the right way. setenforce 0 and TMPDIR must point to the chroot’s /tmp, XKB_CONFIG_ROOT must point to the chroot’s xkb, and you start the X server with app_process rather than the termux-x11 command. Miss one and you get a black screen or an xkbcomp error.
Three: use the sharedUid APK of Termux:X11. If you don’t, Android will throttle Termux’s CPU because “X11 is in the foreground and Termux is in the background,” and the desktop drops frames outright. The cost is that it only accepts the GitHub-signed Termux; the F-Droid build has a different signature and can’t be installed under the same UID.
Root gives you permissions, not scheduling weight
This is the easiest one to get wrong.
Having root doesn’t mean the desktop will be smooth. Throttling and root are two separate mechanisms:
system_servershoves the entire process tree into thetop-app/foreground/background/cachedcgroups based on “is this app visible right now.” Processes spawned bysuare still children of Termux and inherit Termux’s group;sudoesn’t re-queue them.- The specifics:
cpuset.cpus(background/cached get pinned to the little cores),cpu.weight(a weight gap of an order of magnitude),cgroup.freeze(ten seconds after entering cached, the whole process tree gets frozen). Once Termux freezes, the X server hanging off it freezes too, and the desktop locks up.
So I added a 05-pin-priority.sh: unfreeze cgroup.freeze, raise cpu.weight to 1000, open up all cores in cpuset.cpus, and pin Termux and the X server to cores with oom_score_adj=-900, renice -10, taskset.
But this is a patch, not a cure. system_server rewrites these files on every foreground/background switch; switch away once and come back and things are basically back to how they were, so you have to re-run it. It only governs whether you can win CPU time — it can’t stop the freezer from freezing your processes the moment you switch away.
The real way to never get demoted in the first place is that sharedUid APK; the cost is covered above.
Prep before you start
- Install Termux from GitHub Releases or F-Droid, not Google Play (it’s abandoned); get Termux:X11 from the nightly builds.
- Set the battery policy for both apps to “Unrestricted.”
- Set aside 15 GB or more (a KDE install comes to about 4 GB).
- Keep USB debugging on; if things go wrong,
adbis your rescue. - You need to be able to
su.
Wrapping up
The desktop comes up, Chromium opens, LibreOffice opens, the terminal works — the cost is a stutter when you switch back from another app, and a freeze if you leave it in the background too long.
(This is part 1 of 2 of the same post.)
It turns into a tablet that can serve as an emergency fallback, not a laptop. Put that expectation up front, and everything else is just an acceptable operating cost.
FAQ
Q: Can the Pad 6S Pro run native Linux or Fedora?
Yes, but the maturity is far worse. A native dual-boot means touching slot B; Fedora on sheng is still in a lab state, and you have to run GitHub Actions yourself to produce an image. Debian 13’s chroot is the path that works out of the box.
Q: Does this require root?
Yes. chroot needs /dev, /proc, and /sys mounted and SELinux switched, and without su you can’t do it.
Q: Why is the desktop so laggy?
Check Mesa first: if glxinfo -B reports llvmpipe as the renderer, you’re still on software rendering and the kgsl build of Mesa isn’t installed. If it’s still laggy after installing it correctly, Android’s cgroups are throttling you — cpuset, cpu.weight, and cgroup.freeze have nothing to do with root and need to be patched continuously.
Related
- Xiaomi 13 (fuxi) OS3.0.309 Bootloader Unlock: Only One of Four Routes Doesn’t Gamble with the Motherboard
- After unlocking Xiaomi 13 / Pad 6S Pro: empty userdata, dual-slot abl, and the location of init_boot
- Rooting the Xiaomi 13 and Pad 6S Pro: when the patch went on boot, the tool even built it a ramdisk
(This is part 2 of 2 of the same post.)
