Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
The VM isn't running in user space, it runs through the hypervisor, shell in userspace is just a convenience feature of accessing the VM that is running parallel to Android and the hypervisor enables passthrough of certain SoC features to talk directly to CPU/GPU, without traversing the android userspace.
It's like running wsl on windows, both windows and wsl are virtualized and talking to hypervisor, your wsl instance isn't running within your windows instance.
Can you link any direct confirmation that this is actually a VM on hypervisor, and not just a non-hypervised VM but with GPU passthrough like the Crostini on ChromeOS? These two are very different things.
It uses the Android virtualization framework: https://source.android.com/docs/core/virtualization
Using a modified KVM: https://source.android.com/docs/core/virtualization/architecture
Thanks, this might prove promising!