[Feature]: declare MANAGE_VIRTUAL_MACHINE permission

[JacobTDC]

Feature description

Termux should declare the android.permission.MANAGE_VIRTUAL_MACHINE permission in it's manifest. While it is a signtaure|privileged permission, the AVF allows granting it via. ADB, and it would allow usage of the /apex/com.android.virt/bin/vm utility and related system services to create, manage, and interact with VMs within Termux.

Additional information

More details about the Android Virtualization Framework can be found at the following sources:
https://android.googlesource.com/platform/packages/modules/Virtualization/+/refs/heads/main/libs/framework-virtualization/README.md
https://source.android.com/docs/core/virtualization

[robertkirkman]

Is there currently any way that ADB can be used to grant access to this /apex/com.android.virt/bin/vm command to current Termux builds, and then create an AVF VM from Termux? or would it be necessary to recompile Termux entirely in order to achieve that?

[JacobTDC]

Is there currently any way that ADB can be used to grant access to this /apex/com.android.virt/bin/vm command to current Termux builds, and then create an AVF VM from Termux? or would it be necessary to recompile Termux entirely in order to achieve that?

Currently, I'm able to use it using Shizuku as well as a function/alias mapping vm to rish -c "/apex/com.android.virt/bin/vm $@". Crucially, this requires you to have everything set up in /data/local/tmp/, as the Android shell does not have access to Termux files.

Otherwise, yes, you would have to rebuild Termux to add the permission to the manifest.

[JacobTDC]

Oh, also, if using it in Termux with the permission granted (and not through ADB/Shizuku), you have to unset LD_PRELOAD before running it.