VMOS is an APP software based on Virtual Machine (VM).
VMOS can be installed in the form of a normal APP to Linux or Android system through VM technology.
That is to run another complete Android system through an application.
Moreover, VMOS is not controlled by the host system. (Android on the phone).
VMOS is running locally, including the memory (RAM) consumed by the runtime and the storage space (ROM) consumption.
The biggest difference between VMOS and cloud mobile phones lies in resource consumption.
All the performance parameters of cloud mobile phones are derived from the merchants, you can only change the internet speed.
However, VMOS is completely dependent on the performance of the real machine.
Because VMOS is a virtual system, the size of the system is difficult to reduce.
So at least 3gb (RAM) + 4gb (ROM) free space is required to enter VMOS, and 3gb ram + 32gb ROM or higher mobile phones are recommended.
we are asking all these permissions for better simulation of a physical phone.
VMOS is a system can install Apps, we are asking specific permissions to make sure users can use apps that need those specific permissions. (Android 5.1 ask all permissions before you download apps)
1. Floating window permission: For better playing the virtual machine on the real machine interface.
2. Storage permissions: Because the data in the virtual machine is empty, considering that you need to transfer the local file. This permission will only be used for the file transfer station.
3. Recording permission: This permission will only be used when you use voice transmission or call.
4. Camera Permissions: This permission will only be used when you use the camera, such as scanning QR code, taking photos, and video calling.
5. Device information: Because the device information of VMOS is originally empty, you need to obtain the device information of the real machine to make the device information of the virtual machine the same. There is sensitive information in these data, but we do not upload and collect data.
6. Telephone rights: The device information such as IMEI of some mobile phones is permission.
For better user experiences, we collect your phone model and the error log.
The floating ball needs to be granted permission by the real system.
The color of the floating ball is for better distinguish the physical machine and the virtual machine.
Blue: In the virtual machine.
Green: The physical machine.
The floating window can change VMOS's picture into a small window, similar to the application window on the PC.
It can be freely zoomed and dragged.
You can also realize the simultaneous operation of the physical machine and the virtual one.
When the pushpin in the upper left corner of the floating window is white, zoom in and out by two fingers.
Click the pushpin to lock/unlock the window.
When the pushpin is white, there is a spin button in the lower right corner of the floating window.
When the pushpin is white, there is a mute button on the lower-left corner of the floating window.
There is a minimize button in the upper right corner of the floating window, click it to zoom out.
Restart VMOS after Xposed installed.
VMOS and Magisk need to be adapted. It takes time.
After running the application, click "Return" in the floating ball, or press HOME in the physical machine.
1. The phone's memory is exhausted and is killed by the system.
For example, if a game's running in the virtual machine, which is also running in the physical one, one of them will be killed when the storage is insufficient.
2. The battery optimization's been added, the system automatically detects high power consumption.
Then the system kills the process by default.
It would be solved by adding a whitelist to the battery optimization of the real machine settings.
Compatibility issues exist in some apps or games, our dev team would fix it case by case.
The configuration of the physical device is not good enough.
Or you are running a game.
This function is currently under development.
As VMOS is always sharing the network environment with the physical system,
the buttons inside VMOS with the same function are useless.
So we've temporarily removed them, which will be back after they could work separately.
If the VMOS on your device is unable to connect the internet,
please uninstall VMOS and download it again.
Since we haven't solved the technical difficulties on the function yet,
Regarding our apology, it's not possible to use Bluetooth in VMOS currently.
However, we've already got several feedbacks, and are trying to figure out a way to manage that.
Please keep an eye on our updates.
It's under development.
Sure, we have a built-in app in VMOS called file transfer station in yellow.
VMOS has purchased the same phone type abroad to fix this problem.
Please keep an eye on the VMOS update.
A. Game detects VMOS
B. The game needs some physical hardware sensors or information that the virtual machine couldn't get from the physical system.
C. The Android version is too low. Can not run the game
D. The configuration of the device is not good enough.
1. the internet connection of VMOS depends on the physical device.
If the physical device connected with wifi, so does VMOS.
If the physical device connected with data, VMOS would be connected as well.
2. Keep the [wifi] button inside of VMOS on.
3. the [wifi] button of VMOS and the [Data] button of VMOS is just a switch, but can't choose which wifi to use.
Please connect VPN in your physical system.
The VM system shares the same internet environment with the physical system.
Adjust your settings depends on your device.
We have recorded this issue.
Developers are working on it.
VMOS itself doesn't need your location.
Location permission is for Apps (like Ar-game, etc.) in VMOS that might need it
It's already on our plan list.
We will upgrade Android 5.1 to higher version soon.
Keep an eye on our updates.
The entire app is around 300 MB.
Considering apps will be installed in VMOS, we recommend at least 4 GB free spaces in the device.
However, sometimes the insufficient storage would still pop up even if there are 4 GB empty spaces.
In this case, please try to spare more for VMOS.
Now you can see that the root option is on the first setting page, no longer need to switch it on/off in the developer options.
We recommend running VMOS on a phone with more than 3GB RAM and 32 GB Storage.
CPU is also related.
Click VMOS ball→Notifications→Auto-rotate.
VMOS is not a simple app, it's a virtual system
Don't install too many apps in VMOS. Please shut down all other apps before using VMOS and run PUBG again.
We will optimize the system as much as we can.
Currently, it's not possible to change the brightness in VMOS.
It's synchronized with the physical system.
We apologize for the inconvenience.
We'll figure out a solution to add a hint in the virtual system.
VMOS can't adapt to Flash Player currently.
VMOS can't adapt to the Android 4 system currently.
It's in our plan list.
Please keep an eye on the VMOS updates.
Download MT file manager→Delete related file folders.
The system app won't be shown. The running of the system app relies on the physical system.
We have noticed this problem.
We will optimize it as much as we can.
Currently, the wifi penetration inside VMOS is uncompleted.
Some wifi-related Apps can't be supported.
We will try our best to fix it as soon as possible.
This is because of the rules of Google Play.
Google filters device by type and checks the compatibility of apps with the emulator.
We will keep trying our best to make VMOS compatible with more apps.
Currently, VMOS has a function to turn on/off the root access.
Since completely remove root access needs to delete some relevant files, which including technical difficulties, this function is still under developing.
Please kindly spare with us and keep an eye on our updates.
We are now developing this function.
Please check our updates.
This function is coming soon!
The camera function has already been developed.
We are now testing and optimizing it.
We'll put it into VMOS as soon as possible.
This function is already developed and under testing. The virtual machine with Viper4android supported would be coming soon!
To better analyze this problem,
please send the running log which is under the vmos.log in the Internal storage to our mailbox.