J2ME Loader

Before smartphones, most phone games were small Java programs, written for Java ME (also called J2ME or MIDP) and sold for Nokia, Sony Ericsson, Samsung and other phones. J2ME Loader runs them on Android. Its README: “J2ME-Loader is a J2ME emulator for Android. It supports most 2D and 3D games (including Mascot Capsule 3D ones). Emulator has a virtual keyboard, individual settings for each application, scaling support.” It turns each game’s Java code into Android code when you add it, and plays it with a virtual phone keypad on the screen.

Adding games

Tap + and pick a game file: .jar, or a .jad with its .jar, or .kjx from Japanese KDDI phones. Opening one of these files from a file manager or a browser works too; for a .jad web link, J2ME Loader downloads the game itself. Each game then gets its own settings, such as screen size, scaling, orientation, filtering and the keypad layout, and you can put a shortcut to a single game on your home screen.

To games, J2ME Loader presents itself as a Nokia phone. The README’s two tips for problem games: filtering can slow some games down, and the “Immediate processing mode” option fixes flickering.

Permissions

J2ME Loader declares 15 permissions because it implements the phone features Java games could use. Most are asked for only when a game uses them:

• Camera and microphone, for games that take pictures or record sound.
• Location, for games using the Java location API, and for Bluetooth on Android 11 and older.
• Bluetooth (five permissions on Android 12 and later), for Bluetooth multiplayer.
• Notifications on Android 13 and later, for games that post Nokia-style notifications.
• Internet, for games that go online, for downloading a .jad link and for crash reports.
• Vibration, home-screen shortcuts, and storage on older Android versions.

What goes online

J2ME Loader has no update checks, ads or analytics. It connects to the internet in three cases:

• A .jad web link you open with the app: it downloads that file and then the game file the .jad names.
• Games that use Java ME’s network functions connect wherever the game is written to, which depends on the game.
• Crash reports, only after you tap Send in the crash dialog (see the questions above).

Crash reports go to Microsoft App Center through code the developer added on top of the ACRA library, which is why our scan lists ACRA. The app turns crash reporting on only for its official builds, which it recognises by their signing key; F-Droid’s key is on that list, so this build has it, and there is no setting to switch it off. If sending fails, the report is saved as crash.txt in J2ME Loader’s working folder.

About this file

• This is F-Droid’s build of J2ME Loader 1.8.2, compiled from the developer’s source and signed with F-Droid’s key. The developer released 1.8.2 on 7 August 2024, without release notes; its changes, from the code history, fix home-screen shortcuts and a crash on the menu button. 1.8.0, a week earlier, added an option for the screen cutout area and fixed loading games on Android 14.
• It is still the latest release. The project became active again in September and October 2026, with many changes from the JL-Mod developer, but so far only as automatic development builds.
• J2ME Loader is also on Google Play, where it is free; the listing still mentions in-app purchases “for donations only”, which the code removed in July 2024. This build has no purchases, ads or donation screen.
• The 8.5 MB file runs on Android 4.0 and later, on ARM and x86, 32- and 64-bit. Taking pictures from games needs Android 5.0.
• The app is translated into Brazilian Portuguese, about four fifths of it.
• The one screenshot shows a game’s settings screen, from the project’s store images; the others show commercial games, so we left them out.
• J2ME Loader is licensed under the Apache-2.0. Inside are Nokia’s open-source 3D engine for Java games (M3G), under the Eclipse Public License 1.0, and parts of FFmpeg for old ringtone-format sound, under the LGPL. Three files for Nokia’s other 3D format carry an Apache-2.0 header with the same author as the matching files in FreeJ2ME, which are GPL-3.0; we found no record of why. The keypad font, Roboto-Regular.ttf, is in fact Google Sans 1.023, whose own licence field says: “Google offers many fonts on open source terms. Google Sans is not one of them.”

CPU types in this build: arm64-v8a (64-bit ARM, almost every phone since 2017); armeabi-v7a (32-bit ARM, older and budget phones); x86 (32-bit Intel, emulators); x86_64 (64-bit Intel, emulators and Chromebooks).

Versions currently kept in the F-Droid repository. We host and check only the newest one.