A PojavLauncher install on Android has a few moving parts: the APK, a matching Java runtime, storage access and a Microsoft account that owns Minecraft Java Edition. Because the original project is now archived, this guide is best used for legacy installs and troubleshooting rather than as a current-release download page.
Key points
- You need a 64-bit device on Android 8.0 or newer, about 3 GB free storage and an account that already owns Minecraft Java Edition.
- Install the build from the project's GitHub repository, not from a download portal that repackages it.
- Let the launcher install its OpenJDK runtimes and grant storage access on first launch, or imports fail silently later.
- Start with Minecraft 1.12.2 or 1.16.5 and allocate roughly half your device RAM before touching anything else.
What you need before installing PojavLauncher
The PojavLauncher download itself is small, but the launcher only acts as a bridge. It supplies a Java runtime and translates the game's desktop graphics calls into something a phone GPU understands. Everything else still comes from Mojang's own servers, which means an owned copy of the game is not optional.
A device that can realistically run the game
Any 64-bit Android device on Android 8.0 or newer will start the launcher. Whether it plays well is a different question. Four gigabytes of RAM is the practical floor for vanilla 1.8 to 1.12, and six to eight gigabytes makes newer versions and light mod packs comfortable. Chipsets with Adreno or Mali GPUs from the last five years handle the renderer bridge far better than budget silicon.
A purchased Minecraft Java Edition account
PojavLauncher does not include the game and does not unlock it. You sign in with the same Microsoft account you would use on a PC. If the account has never owned Java Edition, the launcher will authenticate but no version will be downloadable.
Free storage and a stable connection
Reserve at least three gigabytes. The runtime, game assets, libraries and world data all live on the device. A patchy connection during the first asset download is the single most common cause of a broken first launch.
Downloading the PojavLauncher APK safely
This is the step to be careful with. The original repository is archived but still public, so you can verify historical releases without relying on random mirrors. Avoid repackaged APKs, especially when a site adds its own installer or asks for permissions the launcher never needed.
Use the archived official repository
For a legacy install, start with the archived PojavLauncher releases page. Our download section links there directly and explains the project's discontinued status. Do not download the repository source ZIP expecting it to install like an APK.
Allow installs from your browser or file manager
Android blocks sideloaded packages by default. Open Settings, then Apps, then Special app access, then Install unknown apps, and grant permission to whichever app you downloaded the file with. Revoke it afterwards if you prefer a tighter setup.
- Check the package name against the archived project documentation before installing
- Avoid any build asking for unrelated permissions such as SMS, contacts or accessibility access
- Keep a backup of worlds and control layouts before changing or reinstalling the app
Device tiers and what to expect
| Device RAM | Sensible version | Memory to allocate | Realistic experience |
|---|---|---|---|
| 3 GB | 1.8.9 or 1.12.2 | 1024–1536 MB | Playable at low render distance, no mods |
| 4 GB | 1.12.2 or 1.16.5 | 1536–2048 MB | Comfortable vanilla, a handful of light mods |
| 6 GB | up to 1.20.1 | 2560 MB | Steady vanilla, small Fabric sets |
| 8 GB or more | heavier/newer versions | 3072–3584 MB | More demanding versions and moderate mod packs |
First launch: runtime, storage and account
The first time PojavLauncher opens it performs a short setup pass. Do not skip through it. Each prompt configures something the game needs later.
Granting storage access
The launcher keeps game files in its own directory but needs read and write access to import mods, resource packs and worlds. Deny it and imports fail silently later, which is a frustrating bug to trace back.
Installing the Java runtime
Recent builds bundle OpenJDK 8, 17 and 21 and select the right one automatically. If your build asks, install all three. Minecraft 1.8 to 1.16 wants Java 8, 1.17 to 1.20 wants 17, and 1.20.5 and newer expect 21. Picking the wrong one produces an instant crash with an unsupported class version error.
Signing in to your Microsoft account
Choose the Microsoft option, complete the sign-in in the embedded browser window and return to the launcher. If the window loops back to the login screen, clear the launcher's cache and try again on a different network — captive portals break the redirect.
Downloading and starting a Minecraft version
With the account attached, the version list becomes usable. Start with something modest rather than the newest release; a version that loads is far more useful than one that stutters.
Picking a sensible first version
1.12.2 and 1.16.5 are the friendliest starting points on mobile hardware. They are well optimised, widely supported by mods and light on memory. Save 1.21 for after you know the launcher works.
Setting memory allocation
Open the launcher settings and set allocated RAM to roughly half your device total, capped around 2048 MB for a four gigabyte phone and 3072 MB for eight. Allocating everything is counterproductive: Android will kill the process when the system runs short.
The first world load
Expect a long initial load while assets unpack. A black screen for thirty seconds is normal. A black screen for five minutes usually means the renderer choice is wrong — switch between the available GL4ES and ANGLE style options in settings and retry.
Making the game comfortable to play
A working install and a playable one are different things. Two settings passes make most of the difference.
Video settings inside the game
Render distance of six to eight chunks, clouds off, smooth lighting minimum and particles decreased will roughly double frame rates on mid-range devices. Our performance guide covers the full list.
Control layout
The default touch layout is a starting point, not a finished design. Resize the movement pad, move the jump button under your right thumb and hide anything you never press. Layouts export as files, so you can back one up and reuse it after a reinstall.
External controllers and keyboards
Bluetooth keyboards and most gamepads are recognised without extra software. A cheap controller transforms survival play, particularly on a tablet.
If something goes wrong
Most failed launches can be narrowed to four areas: Java version, memory allocation, an incomplete first download or renderer compatibility. Check those in order and keep the latest log file nearby; it often points to the component that failed.
Reading the crash log
The launcher keeps logs in its files directory. Search for the word Exception and read the two lines above it. That is normally enough to identify whether the problem is Java, memory or a mod.
Starting clean
Clearing app data resets the runtime and version files without uninstalling. Back up your worlds folder first. A clean start fixes more first-week problems than any single setting change.
Keeping the install healthy over time
A first launch that works is not the end of the job. Updates, storage pressure and new game versions all change the picture, and a little maintenance avoids repeating the whole setup later.
Back up worlds before every version change
Copy the saves folder somewhere outside the launcher directory before upgrading a world to a newer release. Minecraft converts world data on first load and the conversion is one-way, so a copy is the only route back.
Keep one profile per purpose
Separate profiles for vanilla survival, a mod pack and an old PvP version stop a single broken configuration from taking everything down with it. Profiles are cheap; storage is the only cost.
Watch free storage
Android behaves unpredictably when free space runs low, and the launcher writes logs, assets and world data continuously. Keeping a couple of gigabytes spare prevents a class of failures that look like launcher bugs but are not.
Download reminder: take the build from the project's own repository. The download section on our homepage links straight to it.