Why use a virtual machine with 32-bit support?
On a supported 64-bit Android phone, use a Mixed or suitable 32-bit virtual machine for compatible 32-bit apps. A 64-bit-only virtual machine cannot run a 32-bit-only app. Android version, required services and device compatibility still matter.
Android apps can be 32-bit or 64-bit. The App architecture setting chooses which types your virtual machine can run. Your virtual machine must also meet the app’s Android-version requirement. Required services, graphics and phone hardware can affect whether it works.
Choose Mixed or 32-bit, not 64-bit only
When creating a virtual machine, Android 15, 12, and 10 offer Mixed, providing one environment for compatible 32-bit and 64-bit apps. Android 7 also offers a 32-bit-only option. Choose Mixed when you need both app architectures in one virtual machine.
A 64-bit-only virtual machine cannot run a 32-bit-only app. If you see an architecture warning, create a Mixed or suitable 32-bit virtual machine. Reimporting into the same 64-bit-only one will not help. Android 15, 12 and 10, and 64-bit-only Android 7, require Premium. Available systems also depend on your phone and installed VPhoneOS edition.
Import first, then adjust only if needed
Start the selected virtual machine, open Import&Export → Import to VPhoneOS from its floating menu, and use Files to choose an APK saved on your phone. Wait for Install success in the import record, then open the app inside the virtual machine and check its launch, display, and main functions.
Start with the default settings. If your phone’s processor only supports 64-bit and the app shows a black screen or crashes, try Force 32bit emulation in Other settings, then restart the virtual machine. This can make apps much slower, so leave it off unless needed.
Step-by-step instructions
Open creation and choose an Android version
VPhoneOS on the phone → Instances → Rightmost creation card → Android
Open VPhoneOS, tap Instances and swipe to the creation card on the far right. Select Android. Android 12 is selected by default; you can change it in the next step.
Check the result The chosen Android version should be selected and its available architecture options shown.
Explicitly select an architecture with 32-bit support
Creation card → Android → App architecture
First choose the Android version you need under System version, then choose App architecture. For Android 15, 12 or 10, select Mixed. For Android 7, select Mixed or 32-bit. A 32-bit-only app cannot run in a 64-bit-only virtual machine.
Check the result Mixed or 32-bit should be selected. A 64-bit-only environment is not a suitable destination for a 32-bit-only app.
Create your virtual machine
Creation card → Create virtual machine
Check your Android version and App architecture choice, then tap Create virtual machine. If Premium is required, sign in with an eligible account and try again. After the success message, tap OK and note the new card’s number.
Check the result A success message and a new card appear. A membership prompt alone does not mean creation succeeded.
Android 15, 12, and 10 require Premium.
Start the new virtual machine
VPhoneOS on the phone → Instances → Target virtual machine card
Return to the virtual machine list, find the new card, and check its number and Android version. Tap the play (triangle) button. If permission or background-process guidance appears, complete it, return, and start the same virtual machine again.
Check the result The selected virtual machine should show startup or ROM-preparation progress instead of the creation form.
You can start here with an existing virtual machine after checking its Android version and app architecture.
Download the system files if needed
Target virtual machine → First-start ROM preparation
A ROM contains the Android system files for your virtual machine. If the first start asks you to download one, follow the prompt. On mobile data, check the file size before choosing Download. Wait for downloading and extraction to finish; skip this if the files are already available.
Check the result After downloading and extraction, startup begins. If it fails, check the reported connection, storage or membership issue and retry.
You may still need to download the system after creating the virtual machine. Some editions ask you to download an app package containing that system first; follow the prompt.
Wait for the virtual Android desktop
Target virtual machine → System startup
Wait for startup to finish. Tap the desktop preview to enter your virtual machine, then complete any first-run Android setup shown.
Check the result The Android desktop or app list appears and responds to taps. You can now install an app.
A percentage indicator, black screen, or error page does not count as a completed start.
Open Import&Export
Running target virtual machine → Floating menu → Import&Export
Tap the floating control at the edge of the virtual machine and swipe up in its toolbar. Open Import&Export, check the virtual machine name or number, then tap Import to VPhoneOS. You can also open Import&Export from that card’s settings.
Check the result The same virtual machine’s import picker should show Apps, Pictures, and Files categories.
If asked to start the virtual machine first, return to the same virtual machine and complete startup before reopening import.
Select the app’s APK file
Target virtual machine’s import picker → Files → Download → Folder containing the APK
An APK is an Android app installation file. Save it in your phone’s Download folder. In the import screen, tap Files, open the correct folder and select the APK. If file access is requested, allow it and reopen the folder.
Check the result The APK’s checkbox should be selected, and the bottom Import button should show the selected count.
If an Android-version or architecture mismatch appears, choose a suitable virtual machine before trying to import again.
Start the import
Target virtual machine’s import picker → Bottom import button
Check the file name, tap Import or Import (count) at the bottom, and wait for transfer and installation. Small files may finish quickly.
Check the result Find the APK in the import records. If Importing is empty, check Complete. If neither shows it, go back and check that you selected the file and tapped Import.
Do not leave the import screen while the task is active, because doing so may interrupt it.
Wait for Install success
Target virtual machine → Import records
Wait while the record shows Installing. Open Complete and find your APK. Continue when it says Install success. If installation failed, follow the error message first. You do not need to tap the completed record.
Check the result Your APK shows Install success. A completed file transfer alone does not confirm installation.
APK import has separate transfer and installation stages. A completed file transfer is not confirmation that the app was installed.
Return to the virtual Android desktop
Import records → Back → Target virtual machine
After installation succeeds, use the back arrow to return to your virtual machine. If you reach the list, find it by number and enter it. Tap Home in the floating menu, then swipe up on the desktop to find the new app.
Check the result The original virtual machine’s Android desktop or app list should be visible, with the newly installed app available.
Home in the floating menu means the virtual Android desktop. Exit fullscreen returns to the VPhoneOS app; the two actions differ.
Open the app and try its features
Target virtual machine → Android desktop or app list
Open the new app and complete the permissions, sign-in and setup you need. If a system-version warning appears, read it before continuing. Try the features you need and check that saving works.
Check the result The app opens and its main features work. Seeing an icon alone does not confirm the app runs.
The screenshots use an offline 32-bit sample app. It ran after an older-version warning was confirmed. Try your own apps to check whether they work.
Frequently asked questions
Can Android 15, 12, and 10 run 32-bit apps without a 32-bit-only option?
Choose Mixed for compatible apps. Android 15, 12, and 10 have no 32-bit-only ROM option, but their mixed environments include 32-bit app support. The app must still meet the selected system’s version and other compatibility requirements.
Why does a 64-bit phone still report that a 32-bit app is unsupported?
Your phone's architecture and your virtual machine's architecture are separate conditions. A 64-bit-only virtual machine does not support a 32-bit-only app. Create a mixed virtual machine or an Android 7 32-bit virtual machine instead.
Should I enable forced 32-bit binary translation before installing?
No. Start with the default settings. This switch is intended for certain black-screen or crash problems on 64-bit-only CPUs. It may reduce performance and requires a restart.










