Android 16 lets the Linux Terminal use your phone's entire storage
androidauthority.com
androidauthority.com
Using termux to ssh into my dev box already gets me access to a full Linux machine. I also think it's preferable relative to what Google is doing here creating a VM under a VM with weird bugs.
The java bytecode gets translated to a different virtual machine, dalvik/dex (iirc) so no jvm involved.
Other than that, afaik, there’s also a native development kit if you need to call into native code (c/c++/whatever).
BTW, Termux is awesome, but it has its downsides, like no proper thumb drive support due to Android SAF limitations. Yesterday, I went down the rabbit hole trying to access a CircuitPython virtual flash drive via SSH using Termux. (I actually opened this post hoping for something on that, but nope.)
It's not a VM running under a VM, but instead uses Linux (p)KVM.
Its already to the point where Termux is only available on F-droid, & is stuck on Android 9 levels of the SDK.
I also think there's different use cases than an ssh app. If you just need an ssh app, then why even bother with Termux (because .ssh/config is a pretty well known is somewhat of an answer but still doesn't require termux).
Supposedly Android has Wayland support too. Being able to run a VM witg GUI Linux apps is potentially very exciting. With hope it sparks real interest, increases the amount of people using Linux, alike how WSL2 has done.
You still need to run your ssh client somehow, and last time I looked termux+openssh was straight-up a nicer experience than anything else I could find on Android (which I always found funny, but there it is).
You're welcome to use the code if you want, other phone manufacturers can use it, you can fork and develop your own version without google's permission.
- pKVM relies on specific hardware features, such as ARM's Virtualization Host Extensions (VHEs) and IOMMUs, which are not universally present in all Android devices (eg many Mediatek SoCs, often found in budget phones lack this).
- pKVM requires the device's bootloader to support and enable execution at Exception Level 2 (EL2). Pixels have this thanks to their in-house SoC, but almost no other mainstream Android SoC supports EL2, as far as I'm aware (Qualcomm have their own tech called HypX and it can't co-exist with EL2, similarly Exynos have a thing called RKP. So in both SoCs you're limited to EL1, which isn't sufficient for pKVM).
- pKVM also requires device-specific vendor modules/firmware to glue the whole thing together, which is something that OEMs need to provide - and it's not something that an end-user/developer can just whip up themselves.
So yes, while the Linux Terminal is technically part of AOSP, it's pretty much useless on non-Pixels due to pKVM/AVF's design and requirements.