Skip to content

Latest commit

 

History

History
599 lines (466 loc) · 33.1 KB

README.md

File metadata and controls

599 lines (466 loc) · 33.1 KB

Androidbox: Android on your PC. No ads.

An ad-free Android emulator for Windows.
Google Play, game controls, multiple instances, and nothing trying to sell you anything.

Latest release Downloads License Stars

Download the Androidbox installer
Windows 10 or 11 · free · MIT license

Features · How it works · Using it · Tips · FAQ · Build it yourself


Androidbox runs Google's official Android Emulator, the same engine inside Android Studio, on your graphics card, and shows Android in one clean window. There are no ads, no accounts to create, no bundled apps and no telemetry. Everything it needs downloads from Google, or from a mirror you choose, and everything it stores stays in one folder you can delete.

Nothing to install beyond what Google ships, nothing bundled, and because it can't be rooted, banking apps and games with root detection just work.

Androidbox running Android 16, with the inspector open beside the screen

Why Androidbox

Looking for an ad-free alternative to BlueStacks, LDPlayer, Nox or MuMu for playing mobile games and running apps on a Windows PC? Here is exactly what Androidbox does, and where you can check each point yourself.

Androidbox Where to check
Ads and promoted apps None The source is in this repository
Account None for Androidbox itself. Google Play asks for your Google account, as on any Android phone Nothing in the app asks for one
Servers it contacts dl.google.com for Android downloads, GitHub to look for updates, Mozilla only when you install Firefox from the app, and any download mirror you add yourself Search the source for web addresses
Android engine Google's official Android Emulator, the one inside Android Studio How it works
Google Play The real Play Store, on Android 16 and 11 Android 16 with Google Play
Source code Open, MIT license LICENSE
Cost Free

Other emulators publish their own privacy policies, so you can compare: BlueStacks, LDPlayer, Nox and MuMu.

It's aimed at playing mobile games and running apps on a PC: key mapping and controller support, macros, several Androids at once, and an experimental Android 4.1 image for OUYA and GameStick games.

Getting started

You need:

  • Windows 10 or 11, 64-bit
  • Windows Hypervisor Platform turned on. Androidbox tells you if it's off and opens the right settings page
  • A graphics card with current drivers
  • About 4 GB of disk space for Android, plus up to 10 GB per instance

Then:

  1. Download Androidbox-Setup-<version>.exe from the latest release.
  2. Run it. Windows may warn that the app is from an unknown publisher, because it isn't code-signed. Choose More info, then Run anyway.
  3. Follow the setup wizard. It installs Androidbox in Program Files for everyone on the PC and asks Windows for permission once. No admin rights? Choose Install for me only on the first page and it installs in your own folder instead. If Windows Hypervisor Platform is off, the wizard offers to turn it on for you.
  4. Open Androidbox and choose Download and install. This happens once.
  5. Press Start Android.

Closing Androidbox saves and shuts down every running Android, unless you choose to keep it running in the tray. Androidbox keeps itself up to date (see Updates), and you can also run a newer installer over the old one. Your instances and settings stay where they are, and an older per-user install is replaced.

Features

Android 16 with Google Play

Runs on your GPU at 60, 90, 120, 144 or 240 FPS, with ARM apps and games supported. For older games that only ship 32-bit ARM code, create an instance with Android 11, which runs both 32-bit and 64-bit ARM apps.

Each instance has its own hardware, set in its Settings:

  • Processor and memory up to what your PC has, and new instances start with a sensible share of it.
  • Display from six presets, or any size from 320 to 3840 pixels with your own density.
  • Storage of 16, 32, 64 or 128 GB, which only takes the space Android actually uses. Big games need 64 GB or more.
  • Graphics: your graphics card, Automatic, or Software when a GPU crashes the emulator.

Game controls

Saved separately for every game:

Control What it does
Tap A key or controller button taps a spot on the screen
Joystick WASD (rebindable), the D-pad or the left stick moves
Aim Shooter mode: press its key (F1) and the mouse turns the camera. The right stick aims too
Look Free look: the mouse turns the camera only while you hold its key (Alt)
Fire and Scope The left and right mouse buttons while aiming
Skill MOBA casting: hold the key, point with the mouse, release to cast
Turbo Hold the key to tap the same spot rapidly
Hold Press once to hold a spot down and again to let go, for sprint and auto-run
Swipe One key performs a drag along an arrow you place, for dodges and lane changes
Tilt Keys, or the left stick, tip the device like a steering wheel, for racing games
Macro One key plays a macro you recorded, and stops it if you press it again
Zoom Ctrl and the mouse wheel pinch in and out, with no setup

Starter layouts give a game a head start: Shooter, MOBA, Racing, Action platformer and Endless runner place the usual controls, and you move each one onto the game's real button. Layouts export to a file, so you can share them or move them to another instance or PC.

Placing game controls on the screen

Controllers

Xbox, PlayStation and Switch Pro controllers, 8BitDo pads and most other gamepads work straight away, wired or over Bluetooth. Bind their buttons and triggers like keys. Plug in two and both work at once, which is handy for couch co-op. Without game controls they navigate Android: A is Enter, B is Back, Start is Home.

Macros

Record taps, swipes and key presses once, then play them back at half, normal, double or four times the speed. Repeat a macro a set number of times or until you stop it, with a wait of your choice between rounds, which suits idle and farming games. Edit steps shows each tap, swipe, hold and key press so you can change how long it waits or remove it. Give a macro a hotkey, and turn on Works in any program to fire it while another program has the keyboard.

Smart steps let a macro react to the screen instead of guessing. In Edit steps, choose Add after on any step (or Add a smart step at the start) and pick one of five:

  • Wait until the marked area looks the way it does now. Drag a box over something that only appears when the game is ready, such as a button or a title. The macro carries on once that part of the screen matches again. Check now on the step tells you whether it matches at this moment.
  • Wait until the screen stops changing. Good for loading screens, with nothing to mark.
  • If the marked area looks the way it does now, do the next steps. Wraps the steps you choose in an If and an End if, and skips them when the area doesn't match. Good for "tap Collect only if the button is showing".
  • Repeat the next steps until the marked area looks the way it does now. Runs them again until it does, up to a limit you set.
  • Tap the marked picture wherever it shows up. Drag a small box around a button or icon. The macro searches the whole screen for it, waits for it if it isn't there yet, and taps its middle. It suits buttons that move, such as a Collect or Skip button that appears in a different place each time.

Waits, repeats and picture searches have a limit, after which the macro stops with a message or carries on anyway. Settings on a step changes how strict the match is and what happens at the limit, and removing one end of an If or a Repeat removes the other too. Smart steps compare colours, so they don't read text, and a box that is nearly one flat colour is refused because it would match almost anywhere. A picture is found at its original size, so it won't match if the game is shown at a different resolution.

Profiles and sync

A profile keeps your game control layouts, macros, instance presets and preferences together. Make one for yourself, one for streaming, one for the family PC, and switch from the menu at the top right.

  • Save an instance's hardware as a preset and start new instances from it.
  • Profiles export to a single file.
  • Profiles sync between PCs through any folder that OneDrive, Dropbox, Google Drive or Syncthing already keeps up to date. Pick the folder once on each PC and your layouts, macros and presets follow you. There is no server and no login, and Androidbox uploads nothing itself.

Find anything, stay in the game

  • Search everything: press Ctrl+K for one search box over pages, instances, actions, settings, saved states and macros. Type a few letters, use the arrow keys and press Enter. "proxy" takes you straight to the proxy setting, "screenshot" takes one.
  • Inspector: a panel beside the running screen with saved states, keeping a game running, the daily start and stop times, network conditions and your macros, so you don't leave the game to change them. Ctrl+I hides and shows it, and it steps aside by itself when the window is narrow.
  • Instances in the sidebar: each one is a card with a live picture of its screen and its processor and memory use, and an instance's pages (Screen, Game controls, Macros, Apps, Settings) are tabs across the top. Hover a card and a small button starts or stops it without opening it. There may be a few Easter eggs, too. Try the logo, the Konami code on All instances, or odd things in the search.
  • A shorter toolbar: the tools you use all the time sit in a dock under the screen, in groups. Everything else, volume, installing apps, files, location, shake, eco mode, sync, mute and keeping Androidbox on top, is under the ... button, with its name.
  • Settings search: a box and a row of section buttons at the top of Settings narrow the page as you type or jump to a section.
  • Glitch theme: Settings has a Theme choice. Classic stays the default. Glitch matches wolklaw.dev: deep indigo and mint, sharp corners, and a magenta and cyan split that tears for a third of a second every few seconds. The scanlines stay off the Android screen, and nothing moves if Windows' animation effects are off. Androidbox restarts to switch.

Several Androids at once

Every instance has its own apps, accounts and settings. All instances shows each one as a card with a live picture of its screen and its processor and memory use. Create, clone, back up to a single file, restore, start them all at once, open any instance in its own window, tile them side by side, and mirror your input to all of them at the same time.

Apps and games

The Apps page lists what's installed on an instance. Open a game, give it its own frame rate that applies while it's in front, uninstall it, or put a shortcut to it on your desktop. A shortcut starts the instance if it's off and opens that game, even when Androidbox is already running, in full screen.

Those shortcuts just pass command-line arguments, which is also how a frontend like LaunchBox can launch a game: point it at Androidbox.exe with --instance <name or id> --launch <package> --fullscreen. --background starts the instance without raising the Androidbox window (handy for autostart), and leaving out --launch just opens or switches to that instance. --stop <name or id> shuts one instance down, and --start-all and --stop-all start or stop every instance.

Saved states

Save an instance exactly as it is, with its apps, its data and what's on screen, then come back to that moment any time. Handy before a boss fight, before trying a risky setting, or to keep a clean install to return to. Saving takes a few seconds, loading even less. Find it in an instance's Settings under Saved states.

Automation

In an instance's Settings, Automation can keep a game running, opening it again whenever it closes or crashes, which suits idle and farming games. It can also start and stop the instance at the same time every day. Androidbox has to be open for either to work, and the tray counts.

Network conditions

Slow an instance's connection to 4G, 3G, EDGE or GPRS speeds, with the delay that goes with them, to see how an app or game copes with a poor signal. It applies straight away, with no restart.

Network proxy

Give an instance its own IP by sending all of its traffic through a proxy, in its Settings under Extras. Type it the way your provider shows it: host:port, user:pass@host:port or host:port:user:pass for an HTTP proxy, or socks5://user:pass@host:port for SOCKS5. A SOCKS5 proxy typed without socks5:// is still recognised, and Androidbox runs a small relay on your PC to pass its traffic along, login included. Test connects through the proxy and tells you what's wrong if it can't: an address that can't be found, a refused login, or the wrong kind of proxy. It applies the next time Android starts. SOCKS4 and UDP aren't supported.

Updates

Androidbox checks GitHub for a newer release when it starts and every few hours while it runs. When one is out, it downloads the installer in the background and checks it against the checksum GitHub published for it, so by the time it asks, the update is already on your PC. Choosing Restart and update shows what it's doing at once: Androidbox saves your Androids, installs, and opens again afterwards. Windows asks for permission if it's installed in Program Files. If a shutdown ever stalls, Androidbox ends itself and carries on with the install rather than hang. It never restarts on its own. Turn the checks or the automatic download off on the All instances page, where Look for an update now also checks on demand.

Every push to main that raises the version publishes a new release, which is how an update gets to you.

Stays out of the way

  • Tray: keep Android running when you close the window, so idle games keep going. Quit from the tray icon.
  • Start with Windows: Androidbox opens in the tray and starts the instances you marked to start with it.
  • Boss key: one shortcut that works in any program hides every Androidbox window and mutes Android. Press it again to bring everything back.
  • Mute one instance, and keep Androidbox on top of other windows.

The instance manager

Download mirrors

If Google's servers are slow or blocked where you live, add a mirror and Androidbox downloads from it instead. Add one on the first-run screen with Slow or blocked? Use a mirror, or any time under Download mirrors on the All instances page, one web address per line, for example https://mirrors.cloud.tencent.com/AndroidSDK/. Mirrors are tried in order after Google, for both the package list and the downloads, and a download that stops partway carries on from a different source. Every package is still checked against its SHA-1 checksum, whichever source it came from.

The first-run screen, with a link to use a download mirror

No ads, two ways

  • Block ads filters ad networks inside every app and game through AdGuard DNS.
  • Ad-free browser installs Firefox from Mozilla, makes it the default browser and opens uBlock Origin for you. One tap later, websites are ad-free, YouTube included.

Let Claude Code test your apps

Off by default. Turn on Let Claude Code control Android in Settings and Androidbox writes a helper to %LOCALAPPDATA%\Androidbox\claude and, if Claude Code is installed, registers it as an MCP server for you (turning the switch off removes it again). Registration edits Claude Code's own config, so it works even when the claude command isn't on your PATH; restart Claude Code afterwards. The README.md in that folder also shows the claude mcp add ... command if you'd rather do it by hand. Claude Code then gets tools for your running instances: screenshots returned inline, reading what's on screen or its full accessibility tree, waiting for text to appear or go away, tapping, swiping, typing, installing and launching apps, recording the screen, and reading logs. The same folder also has a plain command-line version of the same features, for scripting or when you'd rather not register an MCP server. Turn the switch off and the helper is deleted, and it refuses to run either way while the switch is off.

Prefer a plugin? This repo is also a Claude Code marketplace. In Claude Code run /plugin marketplace add Wolklaw/Androidbox, then /plugin install androidbox@androidbox. It ships the same tools plus a skill that points Claude at them instead of raw adb, which can't see Androidbox's phones. You still need Androidbox installed with the switch on, and Python on your PATH. With the plugin installed, Androidbox stops registering its own copy.

Everything else

  • Screenshots, and screen recording with no time limit (saved in 3-minute parts)
  • Drag and drop to install .apk, .apks and .xapk files, game data included
  • File import and export: add files to Android with a percentage while they copy, an automatic retry if a copy fails, and a check that the whole file arrived, or browse its storage and save files and folders to your PC
  • A clipboard shared with Windows
  • Your webcam as Android's camera
  • Rotate, shake, volume and GPS location
  • Full screen, an FPS counter that also shows how much processor and memory the emulator uses, and eco mode for idle games
  • Diagnostics: one button saves Android's log, an instance's settings and a plain summary of anything that looks wrong, such as an ARM translator crash, to a zip you can attach to a bug report
  • Move everything Androidbox stores to another drive when your C: drive runs short
  • Automatic updates that download in the background, with a check for new releases that you can turn off

Per-instance settings

How it works

The Androidbox window gets screen frames from the Android Emulator through shared memory. It sends touch, keys and sensors over gRPC, installs and settings over adb, and recording and shutdown over the emulator console. On the first run, the emulator is downloaded from dl.google.com.

  1. First run. Androidbox reads Google's SDK package index (or a mirror's, if you added one), downloads the emulator, adb and the Android 16 system image (about 1.9 GB), checks every file's checksum, and unpacks them into %LOCALAPPDATA%\Androidbox. The Android 11 image (about 1.4 GB) only downloads the first time you start an instance that uses it.
  2. Starting Android. Each instance is a standard Android virtual device. The emulator runs without a window of its own, uses your GPU, and resumes from a snapshot in a few seconds.
  3. Showing it. Androidbox asks the emulator over gRPC to draw each frame, at the size of your window, straight into memory the two share, so frames arrive without being copied through a socket. Mouse, keyboard and controller input go back as multi-touch and key events.
  4. Game controls turn keys, mouse movement and controller sticks into touches at the spots you placed, so they work in any game, even ones that were never built for a keyboard.
  5. Shutting down saves a snapshot, so the next start picks up where you left off.

Using it

  • Mouse: left-click taps, drag swipes, the wheel scrolls, right-click is Back, middle-click is Home.
  • Keyboard: typing goes straight to Android, and Esc is Back.
  • Files: drop them on the screen.
Shortcut Action
F11 Full screen
Ctrl+Shift+S Screenshot, saved to Pictures\Androidbox
Ctrl+Shift+R Record the screen, saved to Videos\Androidbox
Ctrl+Shift+K Game controls on or off
Ctrl+Shift+E Edit game controls
Ctrl+Shift+M Record a macro
Ctrl+Shift+O Rotate
Ctrl+Shift+W Open in its own window
Ctrl+wheel Pinch to zoom

Set up a game

Open the game, press Ctrl+Shift+E, click where a button is and press the key you want for it. Add control at the top adds a joystick, aim, look, fire, scope, skill, turbo or swipe control. Drag controls to move them (drag the tip of a swipe arrow to aim it), scroll over one to resize it, and right-click to remove it. Press Done, and the layout is saved for that game.

Record a macro

Press Ctrl+Shift+M, play, and press it again. On the Macros page you can rename a macro, change its speed and click the hotkey box to give it a shortcut such as Ctrl+1. Macros belong to your profile and remember the display they were recorded on, so they only play on instances with the same one.

Pick a hotkey that works anywhere

Open Macros, click a macro's hotkey box and press something like Ctrl+1, then turn on Works in any program. Windows only lets a program claim a shortcut that includes Ctrl, Alt, Shift or Win, and not one another program already has.

Share a profile between PCs

Open the profile menu at the top right, or Manage profiles for the full page. Choose Choose a folder under Sync between PCs, on each PC, and pick a folder your cloud storage syncs. Instances, apps and accounts inside Android are not part of a profile, use Back up for those.

Tips

  • Google Play needs a Google account to install or update apps, and some Google apps that come with Android ask for an update before they open. If you'd rather not sign in, install apps from .apk files and use the ad-free browser for YouTube.
  • Games need more? Give the instance more cores and memory in Settings, or switch it to the Tablet display for landscape games. A game that won't install for lack of room needs more Storage, which is chosen when an instance is created, and changing it erases that instance.
  • Android crashes as it starts? In Settings, set Graphics to Automatic, then Software.
  • Idle game in the background? Turn on eco mode for that instance.
  • A game won't install or says the device isn't supported? It probably ships 32-bit ARM code only. Create a new instance, pick Android 11, and install it there.
  • High refresh rate monitor? Set the instance's frame rate to 144 or 240 FPS in Settings. Games that cap their own frame rate stay capped.

FAQ

Is it really ad-free?

Androidbox itself has no ads and never will. Inside Android, Block ads stops ad networks in apps and games, and the ad-free browser handles websites and YouTube. Ads that apps serve from their own servers can't be filtered by any DNS blocker.

Does it support root?

No. The Google Play images can't be rooted. The upside is that banking apps and games with root detection keep working.

Do I need an account?

No. A profile is just a name on your PC, with no password and no sign-in, and nothing about it leaves your PC unless you pick a sync folder. Anyone who can open that folder can read the profile, so don't share it with people you wouldn't hand your game layouts to.

Where is my data, and how do I remove it?

Everything lives in %LOCALAPPDATA%\Androidbox, apart from the program itself, which is in Program Files. To keep it somewhere else, open All instances and use Where Androidbox keeps its files: it copies everything to a drive you pick, restarts, and then removes the old copy. Uninstall Androidbox from Settings > Apps and it asks whether to delete that folder too, with all its instances. It keeps the folder unless you say yes, because the Android images take a while to download again. If you turned on sync, a copy of your profiles also sits in the folder you chose, in Androidbox Profiles.

Google's servers are slow or blocked for me. Can I download from somewhere else?

Yes. Choose Slow or blocked? Use a mirror on the first-run screen, or Download mirrors on the All instances page, and add a mirror's address, such as https://mirrors.cloud.tencent.com/AndroidSDK/. Androidbox still checks every download against its SHA-1 checksum. If Google can't be reached at all, the checksums come from the mirror's own package list, so only use a mirror you trust.

Can I run it without Google Play?

Yes. Skip signing in and install apps from .apk files.

Does Pokémon GO work?

No, and it won't. Niantic blocks emulators on purpose: the game checks Play Integrity and its own anti-cheat, and refuses to run on any of them. Getting around that means breaking their terms of service and risking a ban, so Androidbox doesn't try. The GPS location tool is meant for testing apps and games that allow it.

Clash of Clans (or another game) closes right after it starts

Some games, Clash of Clans among them, check at startup whether they are running on an emulator and quit straight away if they are. You see the game open and close within a second, and the log shows the game's own code exiting, not a crash in Android. Androidbox can't fix that, and it doesn't try to hide the emulator from a game: that would mean getting around the game's own protection and its terms of service. Other games that do the same include Pokémon GO. Try the game on a real phone, or on Google Play Games on PC if the publisher supports it.

I have an app called DroidCore, and it only sends me to a download page

DroidCore 1.9.0 and 1.9.1 were Androidbox under a short-lived name. They can tell that a newer version exists, but they can't install it themselves, so they open the release page instead. Download the Androidbox installer from there and run it once. It replaces DroidCore in place, so DroidCore disappears and Androidbox takes its place in the Start menu. It moves your instances, profiles and Android images back to the Androidbox folder, and brings over the start-with-Windows setting and the Claude Code registration. Updates arrive on their own after that.

Why Android 16, and not the newest Android?

Google publishes Play Store images for new versions long before they are stable enough for games. Android 16 is the newest stable one, and its ARM translator runs games that crash on Android 15, such as BitLife. Android 11 stays available because it's the last one that runs 32-bit ARM apps.

An ARM game crashes on my Android 15 instance

On a PC, Android runs ARM-only games through Google's ARM translator, and the one in Android 15 crashes some Unity games a few seconds after they start. Create an Android 16 instance and install the game there. Apps and accounts don't carry over between Android versions, so you sign in to Google Play again on the new instance.

Building

.\build.ps1

This creates a virtual environment, installs the packages in requirements.txt plus PyInstaller, bundles the app with PyInstaller, and wraps it in a setup wizard with Inno Setup 6 (winget install JRSoftware.InnoSetup). The installer lands in dist\Androidbox-Setup-<version>.exe, and the version comes from androidbox/__init__.py. The wizard's artwork is drawn by installer/make_art.py, and the PNGs it writes are committed. Raise VERSION and push to main, and .github/workflows/release.yml builds the installer the same way and publishes it as release v<version>, which installed copies then offer to download. Dependencies are pinned in requirements.txt so that release builds match what was tested. To run from source instead:

python -m venv .venv
.venv\Scripts\pip install -r requirements.txt
.venv\Scripts\pythonw Androidbox.pyw
What's in the source
  • androidbox/installer.py: downloads and verifies the emulator, adb and the system image, from Google or your mirrors
  • androidbox/instances.py: instances, ports, virtual hardware, backup and restore
  • androidbox/emulator.py: starts and stops the emulator, adb and console commands
  • androidbox/bridge.py: the gRPC link, with the screen stream, touch and key input, and sensors
  • androidbox/keymap.py, gamepad.py: game controls and controller input
  • androidbox/profiles.py, settings.py: profiles, presets, per-game settings and the sync folder, plus preferences
  • androidbox/macros.py, browser.py: macros, with their editing, and the ad-free browser
  • androidbox/system.py, relocate.py, hotkeys.py: what the PC has, shortcuts and Windows startup, moving the files to another drive, and shortcuts that work in any program
  • androidbox/diagnostics.py: the zip of logs and findings for bug reports
  • androidbox/ui/palette.py, inspector.py: the Ctrl+K search and the panel beside the screen
  • tools/ui_shots.py: renders every page to PNG files, off-screen, to check a change to the UI by eye
  • androidbox/claude.py: the Claude Code helper, as an MCP server and a command line
  • plugin/: the Claude Code plugin, rendered from claude.py by tools/build_plugin.py
  • androidbox/updates.py: asks GitHub for the newest release, then downloads and verifies its installer
  • androidbox/ui/: the windows. window.py, popout.py and host.py lay them out, phone.py draws Android, and files.py browses Android's storage
  • androidbox/proto/: bindings generated from the emulator's gRPC definition
  • build.ps1, setup.iss, installer/: build the app and its Windows installer, and the wizard's art

Credits

  • The Android Emulator, its system images and its gRPC definition (emulator_controller.proto) are made by the Android Open Source Project and Google. The bindings in androidbox/proto are generated from that definition, which is licensed under the Apache License 2.0. The emulator and system images are downloaded from Google under the Android SDK License, which you accept on first run.
  • The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License.
  • Firefox is made by Mozilla, uBlock Origin by Raymond Hill and contributors, and AdGuard DNS by AdGuard. Androidbox only helps you install or use them.
  • Built with Qt for Python (PySide6) and gRPC. Controller support comes from SDL, through PySDL2.
  • Indexed as a worked example for AI coding agents by the XERJ Corpus Hub: XERJ Corpus Hub contributor

Code signing policy

Androidbox's installer isn't code-signed yet, which is why Windows warns about an unknown publisher. Free code signing from SignPath.io, with a certificate from the SignPath Foundation, has been applied for. Once it's approved, every release installer will be signed with it, and this section will say so.

  • Who signs: only releases built from this repository's main branch by the release workflow on GitHub Actions.
  • Who approves a release: the project maintainer, Wolklaw.
  • Privacy: Androidbox collects no data about you. It contacts Google to download Android, GitHub to check for updates, and Mozilla only when you install Firefox from it. See Why Androidbox.

License

Androidbox is released under the MIT License.