Using Android on a Linux computer, especially on ARM 64bits (Also called Aarch64) where all appliations will work natively.
As XFCE still doesn't work (at least in my case with Wayland, and that's my prefered desktop, I still use X11. I want to use some Android application on my Desktop computer. However, Waydroid, the Android virtual machine for Linux is made for Wayland display (so the name Way(land) + (An)droid). Weston is of good help to make it working.
Update 2028-09-01, I managed to have XFCE4 working on Wayland on this hardware, probably due to recent XFCE updates. It use labwc as compositor, that depend itself on wlroots. Still have some limitation (keyboard forced to english, no mean to switch (keyboard and iBus should depend on labwc or wlroots layers), parameters not available at least on menus, no screensaver/locker, see also one of the XFCE4 author's blog entry for more details), so I will wrote a new article about some tweaks in this case
WARNING!! Waydroid start some components at root level, it may contains some Google ads/private data or NSA spies, that's probably better to use it on a VM or a system without sensitive content
If you have other Aarch64 hardware you can skip this, but in my case, I use since about 6 month now a Rockchip RK3588 based (ARM 64bits) Radxa ITX board as main computer There is relatively good management of Vulkan 1.4 and Zink since this summer in GIT version, a stable base is available in Mesa 25.2.0 since 2025-08-06) for the Mali-G610 MP4 GPU included in the SoC. the RK3588 NPU start to be managed by the Rocket driver since 2025-07-28 in mainline Mesa, will be available in this first state in following release of Mesa.
It's hard to have a working Blender on ARM64 (or AARCH64) on Linux, I found a working solution on current state of Panfrost driver
This could be updated depending on driver, box64, and new ARM/RISC-V Blender port progress
I'm runing it on RK3588, with Arch Linux ARM, using box64-git-0.4.3.4.r65.g78383901f (git rev 7838390 or git rev 1058aae) or stable 0.4.2. It work some times with box64 0.4.4 stable and not at all with version git 0.4.4.r6.ge0ae94d74. An issue about this 0.4.4 regression is open, you can follow it, I will update this post as soon it is resolved, if don't forget.
Warning, it fails at first launch, as you see in the video, with message "Open dir error: Connection refused", you need to launch it a second time, at first launch.
>
Blender 2.79b with emulation, note that the video is not 60fps due to video capture pipeline, and recording at 25fps on a 60Hz display ^^>
Tests of in editor Blender rendering and Cycles rendering with mirror material and subsurfacescattering matierial.
I already managed to compile and making 2.76 work on ARM 32bits (RK3288), nativen ten years ago (October 2015) with a simple few lines patch. Software rendering was fast enough for old version of Blender at this time. As it become very hard to compile this time version with today systems libs, I found a solution, with x86_64 version + Box64, a 86_64 JIT + dynarec CPU emulator and native system library wrapper. Software rendering is still usable, but that's now possible to use full hardware acceleration for the on screen 3d rendering. Thanks to Panfrost Mesa driver.
Blender 2.93.18 can run on the same system but only with Mesa LLVMpipe software rendering (see the last line of this post for the launch line), it is a bit slow, but not unusable for simple scenes or modeling light objects.
