@leegao
Hello! sir,
I hope you are doing well.
Recently, during the Android MC session at Linux Plumbers Conference 2025, a Google engineer mentioned something very interesting while presenting about AVF.
As of Android 16 QPR3 Beta 1, AVF now supports GPU-accelerated virtualization, and it is possible to run GUI applications with Weston.
At the moment, it works roughly as follows:
Linux VM app → Weston + Kiosk Shell (inside the guest VM) → gfxstream / virtio-gpu / AHB → Android SurfaceView / SurfaceControl → display output
According to the presentation, this approach still has some performance issues, and they are continuing to improve it.
However, what really caught my attention was that Wayland compositor integration on Android was mentioned as a mid- to long-term goal.
I see this as a very positive direction. If this is eventually realized, Termux may no longer need Termux-X11 for X server-based graphical output, although I assume Xwayland would still be needed alongside it for compatibility.
It also seems possible that Wine + Box64 (with FEX)-based emulators such as Winlator, GameHub, and GameNative could use Wayland output integrated with Android, instead of relying on their built-in legacy X servers.
If Android eventually provides an integrated Wayland compositor, I think it could also improve the synchronization and performance issues that have often been reported in emulator gaming between X servers and Android surfaces.
Of course, this is still a discussion about the future.
Even so, the fact that AVF can already provide Wayland-based graphical output, even in a limited form through Weston + Kiosk Shell, makes me think it is only a matter of time. Legacy emulators would still need extra work to move away from their built-in, outdated X servers and make use of a Wayland environment integrated into Android, but the possibility now feels much more realistic.
For that reason, I think it may not be a bad idea for bionic-vulkan-wrapper to prepare Wayland WSI support (VK_KHR_wayland_surface) in advance.
Thank you!
[Mid-/Long-term features]
@leegao
Hello! sir,
I hope you are doing well.
Recently, during the Android MC session at Linux Plumbers Conference 2025, a Google engineer mentioned something very interesting while presenting about
AVF.As of Android 16 QPR3 Beta 1,
AVFnow supports GPU-accelerated virtualization, and it is possible to run GUI applications withWeston.At the moment, it works roughly as follows:
Linux VM app→Weston + Kiosk Shell (inside the guest VM)→gfxstream / virtio-gpu / AHB→Android SurfaceView / SurfaceControl→display outputAccording to the presentation, this approach still has some performance issues, and they are continuing to improve it.
However, what really caught my attention was that Wayland compositor integration on Android was mentioned as a mid- to long-term goal.
I see this as a very positive direction. If this is eventually realized,
Termuxmay no longer needTermux-X11for X server-based graphical output, although I assumeXwaylandwould still be needed alongside it for compatibility.It also seems possible that
Wine + Box64 (with FEX)-based emulatorssuch as Winlator, GameHub, and GameNative could useWaylandoutput integrated with Android, instead of relying on their built-in legacy X servers.If Android eventually provides an integrated Wayland compositor, I think it could also improve the synchronization and performance issues that have often been reported in emulator gaming between X servers and Android surfaces.
Of course, this is still a discussion about the future.
Even so, the fact that
AVFcan already provide Wayland-based graphical output, even in a limited form throughWeston + Kiosk Shell, makes me think it is only a matter of time. Legacy emulators would still need extra work to move away from their built-in, outdated X servers and make use of a Wayland environment integrated into Android, but the possibility now feels much more realistic.For that reason, I think it may not be a bad idea for
bionic-vulkan-wrapperto prepareWayland WSI support (VK_KHR_wayland_surface)in advance.Thank you!
[Mid-/Long-term features]