AFK Farming with VMOS Pro: Game in a VM, Phone Still Usable

You want a farm, raid, or energy timer to keep going while you use WhatsApp, Chrome, or another game on the real phone. Native Android will freeze that title the moment you leave it. This guide shows AFK farming with VMOS Pro: the game stays in a virtual Android, you keep using the host, and you set battery rules so the guest is not killed overnight.

Table of Contents

• Before You Start
• How AFK Farming with VMOS Pro Works
• Setting Up a Farming VM
• Keeping It Alive: Background and Battery Settings per Brand
• Adding Macros / Auto-clickers Inside the VM
• Floating Window and Picture-in-Picture
• Ban-risk Reality Check per Game Type
• Troubleshooting
• FAQ
• Conclusion

Before You Start

AFK is a running VM problem. If the bar never leaves 99%, that is a boot hang, not farming: stuck at 99% boot fix. If the game installs then closes, that is a crash (RAM, root, or 32-bit ROM): apps crashing in VMOS Pro.

1. Charge to at least 50%. A host kill while the game writes a save can corrupt the VM file.
2. Export the VM after a clean home screen — before you install the game (three-dot menu on the VM list).
3. Back up photos and chats on the real phone. VMOS Pro does not rewrite the host system, but a backup still matters.
4. Put messengers and banks on a different VM (or on the host). A farming VM with root + clickers is a bad place for WhatsApp.
5. Read the game’s rules. A VM and a clicker can still get the account banned. This page does not make that legal or safe.

Warning: do not factory-reset your real phone to “keep a game alive.” That wipes the host. Add a VM instead.

Need the APK first? Download VMOS Pro from vmospro.net. Then finish setup after install (ROM, RAM, Play Store) before this tutorial.

How AFK Farming with VMOS Pro Works

AFK farming with VMOS Pro means the game process lives inside the guest Android. Your host Android stays free for calls, maps, and a second title.

To run a mobile game in background Android VMOS is not the same as Android’s Recents tray. When you leave a game on the real phone, the system can freeze it, strip GPU, or kill it after a few minutes. Inside VMOS Pro, the guest is a second OS. As long as the VM process stays running, the game thinks it still has a display.

What actually keeps it alive:

• The VMOS Pro process must not be force-stopped, swiped from Recents, or put to sleep by a battery saver.
• The guest must keep a screen (full window, small window, or floating window). Many games pause if they see “display off.”
• VMOS Pro keep game running when screen off is only half true. Host screen-off often pauses GPU work. Dim the host and keep the VM window; do not expect a black, locked phone to farm a 3D title all night.

The phone stays usable because you are not full-screening the guest. You shrink it, float it, or leave it in a small window while the host launcher is in front.

Warning: do not swipe VMOS Pro from Recents to “free RAM” while a farm is running. That is a force-kill. Use the floating Shutdown in the guest, then swipe.

Setting Up a Farming VM

One game, one VM. Do not stack LSPosed, a bank app, and a 3D farm on the same disk.

1. Install VMOS Pro and grant storage + overlay. Full path: setup guide after install.
2. Add VM → download Android 9.0 64-bit. Current Play Store games fail on 7.1 32-bit.
3. VM settings, guest off: RAM 3 GB if the phone has 6 GB+ (2 GB on a 4 GB phone). Storage 8–16 GB.
4. For max battery life, set resolution 720×1280, DPI around 320. AFK does not need 1080p. FPS and heat notes: lag fix and low FPS.
5. Leave Root off until you actually need a clicker. Leave Xposed off. Enable Google services if Play Store is missing, then boot once to the home screen.
6. Sign in to Play Store inside the VM with a throwaway Google account. Do not use the account that holds your bank or host backups.
7. Install one game from Play Store (or a split APK installer for .xapk). Wait until it is idle (no update download).
8. In the game, pick Low / Medium graphics and a 30 FPS cap if the title offers it. A stable 30 drains less than a swinging 50–18.
9. Export this VM after the first successful login. If anti-cheat later bricks the guest, you restore a clean farm image.

Optional name: Farm so you never open the messenger VM by mistake.

Warning: do not give the VM more RAM than the phone has free after Android and VMOS Pro. On a 4 GB phone, a 3 GB guest will freeze both systems and the “AFK” will die.

Keeping It Alive: Background and Battery Settings per Brand

Host battery savers freeze VMOS. Then you restart the VM, which costs more battery than leaving it Unrestricted.

Do this on the real phone, not inside the guest:

1. Settings → Apps → VMOS Pro → Battery → Unrestricted (wording varies; you want “don’t optimize” / “unrestricted,” not “optimized”).
2. Allow Display over other apps so the window is not stripped when you leave VMOS.
3. On Android 11+: All files access for VMOS Pro.
4. Lock VMOS in Recents if your skin has a lock/pin icon (stops a swipe-kill).
5. Turn off host “game booster” freeze for other apps, or add VMOS Pro to its allow list.

Samsung (One UI)

1. Apps → VMOS Pro → Battery → Unrestricted.
2. Battery → Background usage limits → Never sleeping apps → add VMOS Pro.
3. Recents → tap the VMOS icon → Lock this app.

Xiaomi / Redmi / Poco (MIUI / HyperOS)

1. Apps → VMOS Pro → Autostart on.
2. Battery saver for VMOS: No restrictions.
3. Recents → drag VMOS downward → lock.
4. If HyperOS still kills it: Settings → Apps → VMOS Pro → Battery → Unrestricted plus “allow background activity.”

Huawei / Honor

1. Apps → VMOS Pro → Battery → Don’t optimize / ignore optimizations.
2. App launch (or “App launch management”): set VMOS to Manage manually — Auto-launch, Secondary launch, and Run in background on.

OnePlus / Oppo / Realme (OxygenOS / ColorOS)

1. Apps → VMOS Pro → Battery → Don’t optimize.
2. Recents → lock VMOS.
3. Turn off “high-load” or “smart freeze” for VMOS if those menus exist.

Google Pixel / stock Android

1. Apps → VMOS Pro → Battery → Unrestricted.
2. That is usually enough. If the VM still dies, also disable Adaptive Battery for a test night.

Vivo / iQOO

1. Battery → High background power consumption → allow VMOS Pro.
2. Autostart on. Lock in Recents.

VMOS Pro keep game running when screen off: set the host screen timeout long, or plug in and use a dim brightness. A fully off display often pauses 3D in the guest. Idle 2D / “tap to collect” games survive dim better than open-world 3D.

Warning: do not use random “RAM cleaner,” “game turbo,” or “anti-kill” APKs from unknown sites. They raise CPU, break Play Services, and can steal accounts.

Adding Macros / Auto-clickers Inside the VM

A VMOS Pro macro auto clicker runs inside the guest, not on the host. The game only sees taps in the virtual display.

Two levels:

• No root: an accessibility auto-clicker. Easy. Many games detect Accessibility and warn or ban. The service can also pause when the VM window is tiny.
• Root on (this VM only): a clicker that injects input with su. More reliable for long AFK. The host phone stays unrooted. How to turn the switch on: enable root in VMOS Pro.

Do not grant su to the game itself. Grant it only to the clicker.

Accessibility clicker (try this first)

1. Keep Root off.
2. In the VM, install a simple auto-clicker from Play Store (official listing, not a “mod APK”).
3. Guest Settings → Accessibility → turn the clicker on.
4. Open the game, start the clicker, set a slow interval (1–3 seconds). Fast spam looks like a bot.
5. Shrink the VM window and confirm taps still fire.

Root clicker (only if accessibility is not enough)

1. Shut down the VM. Enable Root for this VM only. Boot, confirm Superuser / Magisk prompt.
2. Install the clicker inside the VM. Open it once and Allow su.
3. Deny su for the game, Play Store, and any anti-cheat helper if it asks.
4. Record a short loop on a throwaway account first. Do not test on a paid rank or a years-old gacha login.
5. If the game closes at splash after root is on, turn Root off and go back to accessibility — or use a second unrooted VM for that title. Crash path: apps crashing in VMOS Pro.

Modules (LSPosed “hide clicker”) raise ban risk. They do not make farming “undetectable.” Skip them unless you already know that stack: Xposed and LSPosed.

Warning: do not use “anti-ban,” speed-hack, or packet-mod APKs. Click timing is already enough for many bans. Mods take the account and can infect the guest.

Floating Window and Picture-in-Picture

VMOS Pro floating window gaming is how you use the host while the farm keeps a visible surface.

1. Start the VM, open the game, wait until the farm loop is stable.
2. Use VMOS’s floating / mini window (controls on the VM chrome — not Android’s Recents). Drag it to a corner.
3. Grant Display over other apps on the host if the bubble vanishes when you open Chrome.
4. Keep the window large enough that the game still thinks a display exists. A 1-pixel trick will pause most titles.
5. Picture-in-picture is the same idea: a small always-on-top surface. If your build has PiP, enable it in VMOS settings with the guest off, then boot.

You can answer messages on the host with the farm in the corner. Overlay on = you see the game (and it usually keeps running). Overlay off = more privacy, easier for the host to freeze the VM.

For a long night: plug in, brightness low, 720p, one game, Unrestricted. Feel the back of the phone after 20 minutes. Too hot to hold → drop resolution or stop. Heat is a kill 10 minutes later.

Warning: do not run a screen recorder + 3D farm + host video at the same time unless you must. Extra overlays cost GPU and battery.

Ban-risk Reality Check per Game Type

Nobody can promise “undetected.” A VM is a second cheap phone. A clicker is still a clicker.

What games usually punish: inhuman tap timing, overlay / accessibility on the game package, root / Magisk, known emulator fingerprints, many accounts from one IP, speed hacks.

What a clean 9.0 guest looks like: a cheap second phone. That is not a bypass. Official in-game auto-battle is safer than any VMOS Pro macro auto clicker.

Use a throwaway login for the first week. Do not put a paid skin account in a rooted farm VM. Do not mix this VM with a second WhatsApp.

Warning: hiding root or spoofing a device to break a game’s checks can violate the terms and can get the account banned. If the title matters, farm on the host with the game’s own auto mode, or accept the risk on a junk account.

Troubleshooting

Game pauses when you open Chrome on the host. Overlay permission off, or the floating window is too small. Enable Display over other apps. Enlarge the mini window. Pin VMOS in Recents.

Farm dies when the screen turns off. Expected for many 3D titles. Raise screen timeout, dim instead of off, keep the VM visible. Unrestricted battery does not replace a display.

VM gone after “overnight.” Xiaomi Autostart off, Samsung Sleeping apps, or you swiped Recents. Re-apply the brand list. Do not restart-loop; that corrupts the disk.

Clicker works in full screen, not in the float. Accessibility lost the window. Use a larger float, or a root clicker. Confirm the clicker is still enabled in guest Accessibility after a VM reboot.

Game closes at splash after you turned Root on. Detection. Turn Root off. Use an unrooted VM + in-game auto-battle, or a second VM.

Phone burning hot, FPS 10. 1080p + 3D AFK. Set 720p, Low graphics, 30 FPS cap. See lag fix and low FPS.

“App not installed” / Play incompatible. 7.1 32-bit ROM. Add a 9.0 64-bit VM; do not sideload a random host APK.

Save lost after a 99% hang. Repair does not always save a half-written disk. Export before login and again after a stable farm night.

Warning: do not keep force-stopping VMOS Pro to “refresh” the farm. That corrupts the virtual disk. Shutdown inside the guest, then start again.

FAQ

How do I do AFK farming with VMOS Pro?

Create an Android 9.0 64-bit VM, set 720p and 3 GB RAM on a 6 GB+ phone, install one game from Play Store, then set VMOS Pro to Unrestricted battery on the host. Keep a floating or mini window so the game still has a display. Add a clicker only on a throwaway account.

Can I run a mobile game in the background with Android VMOS?

Yes. The game runs in the guest OS while you use the host. The VMOS Pro app must stay running: Unrestricted battery, overlay allowed, not swiped from Recents. That is different from leaving the game in the host Recents tray.

Will VMOS Pro keep the game running when the screen is off?

Often no for 3D. Host screen-off pauses GPU. Dim the screen, plug in, and keep the VM window visible. Idle 2D games survive dim better than open-world titles.

Do I need a VMOS Pro macro auto clicker?

Only if the game has no usable in-game auto-battle. Try an accessibility clicker with root off first. A root clicker is more stable and easier to detect. Never grant su to the game.

What is VMOS Pro floating window gaming for?

It keeps a small always-on-top guest display so you can use WhatsApp or the browser on the host while the farm keeps a screen. Grant Display over other apps or the bubble disappears and the game pauses.

Will I get banned for farming in a VM?

A VM is not a ban by itself. Clickers, root, mods, and multi-account bots are. Competitive and gacha anti-cheat is strict. Use official auto modes when you can, and a junk account if you cannot.

Conclusion

You now have a working path for AFK farming with VMOS Pro: a dedicated 9.0 VM at 720p, Unrestricted battery on every skin that likes to kill apps, a floating window so the game still has a display, and a clicker only if the title has no real auto-battle — on an account you can afford to lose.

• Beginner path: how to use VMOS Pro
• ROM, RAM, Play Store: setup guide after install
• Heat, 720p, FPS: lag fix and low FPS
• Root for a clicker: enable root in VMOS Pro
• Game closes at splash: apps crashing in VMOS Pro
• Farm dies after a host OS update: does VMOS Pro work on Android 14

Need a clean guest first? Download the latest VMOS Pro version from vmospro.net, boot 9.0 at 720p with Unrestricted battery, then put one farm game in the window — not a modded APK.