DoJa SDK 5.1 Emulator Setup Guide

READ THIS FIRST!!

Our friend Yuvi has released a beta of the Keitai World Launcher, which allows you to play i-mode games without the hassle of setting up the DoJa 5.1 SDK! We highly recommend you use this!!

Upon first installation, run the .exe as an administrator! You don’t need to do this for subsequent launches.
For games with online leaderboards: join the Keitai Wiki Discord server and use the Butler Sheep bot in the i-mode channel to obtain a UID (type /get-uid). Then put this UID into Keitai World Launcher under the config menu. Choose the “online” game variant, and you’re good to go.
Simple game selection, constantly updating as new i-mode games are preserved. It also has filters and a search box
Game importer, in case you want to add something that isn't on the list
Easy switching between DoJa/Star SDK versions (some games require earlier versions of the SDK)
Easy switching between audio types (standard vs 903i)
Built-in ShaderGlass for screen enlargement
Controller configurator for gamepads (you need DS4Windows if you’re using a PlayStation controller). It’s XInput-based.
Network UID configuration for online-enabled games
A help button with the default keybinds, in case you get confused

Setting up the DoJa 5.1 SDK’s emulator

Installing the emulator

You need:

i-αppli dev tools (specifically the DoJa 5.1 SDK) (for majority of the games, some may need Star 2.0 or DoJa 2.5 International)

DoJa 2.5 International can be found here
Katamari Damacy Mobile can only be run on the DoJa 5.0 SDK (use the same link as above)

Install the JDK. It should be 32-bit, otherwise, it will not work.
Install the DoJa 5.1 SDK. Note that the installation path should not have spaces or non-ASCII characters.
Try running bin\doja.exe in the SDK installation path. If everything got installed correctly, you will see this window:
Close doja.exe for now
Install the Locale Emulator. To do that, extract the archive with the utility to an empty folder and run LEInstaller.exe.
When you need to run the emulator, right-click doja.exe and pick Locale Emulator - Run in Japanese. This will run with the Shift-JIS character set, which is necessary in order to display text in games properly.

Installing games to play

If you already have a game from somewhere, with a “.jam”, “.jar” and an optional “.sp”, use DoJaject to easily import the game. Instructions are in the repo. First, you set the DoJa directory (where the SDK is), and then after that, you can select the “.jam”s of games you want to import.

After making a folder with the name of the game (this folder and the game files must have the same name), create two folders: bin and sp. Put the jar/jam files in the bin folder, and put the sp file in the sp folder.

If your computer’s language is not English or Japanese, the emulator will not boot without Locale Emulator.
If the console tells you DrawArea の値が不正です and doesn’t boot up the game, that means the game has a custom defined resolution that may not be chosen while running the emulator. To fix this:

See what resolution the game is made for by clicking on ADF Configuration and scrolling down to DrawArea parameter.
Edit -> Emulator Environment Setup -> Device Configuration and then add a device with the main screen size which is equal to the one in the ADF. Sub display may be whatever.
RECOMMENDED DEVICE RESOLUTIONS:

240x320
320x240
480x854
854x480

Notes for games logging “SecurityViolation”

Go to Edit -> Trusted Configuration.
Codes:

35 - Enable Bluetooth
37 - Enable OpenGL/ES
40 - Enable i-appli call
48 - Enable myMenu request

Note for games logging “java.lang.string”

Click the “ADF Configuration” button
Add http://localhost/ to the PackageURL

If this doesn’t work, append a single ./ until the exception goes away

Removing DoJa SDK’s phone UI + use ShaderGlass for a bigger game screen

Before doing any of these steps, be sure to copy and save the skin folder (iDKDoJa5.1\lib\skin) so you can revert back to the original UI if needed
Go to iDKDoJa5.1\lib\skin\device1 and overwrite skin.conf with this modified skin.conf
For every device in iDKDoJa5.1\lib\skin\deviceinfo, change the subwindow size to 1,1 via a text editor like Notepad (they were originally 120,120)

Download ShaderGlass
Recommended setting for your UI-less game window

Input -> Pixel size -> x1
Output -> scale -> 200% to 300%
Output -> frame skip -> none
Shader -> Turn off "Active"
Input -> window or desktop

If the image in ShaderGlass looks blurry

Notes for European games

For these, you might need DoJa (EU) 2.5 SDK
Much of the operation is the same, but scratchpad files have to be headerless (without the SP header required for 5.1 SDK). The naming appears to be different: “.scr” extension as opposed to “.sp”, and the scratchpad files have to be numbered starting from 0 (basically, look for what the game tries to create if it does).
Locale Emulator also shouldn’t be required for obvious reasons

If fonts appear too large for older games

Go to iDKDoJa5.1\lib\skin\device1
Add this line to skin.conf

font_size=16,24,30,12

Adjust sizes as needed (order is small, normal, huge, tiny font size)

Miscellaneous notes

Dirge of Cerberus Lost Episode - FFVII can only be run by launching the DoJa SDK through command line

doja.exe -i path\to\bin\doc_le.jam (path to the jam file)

The jar file must be in that same bin folder

If you just dumped a new phone and found folders named “adf” or “jar” or “sp” or files without formats which have contents of the formats mentioned in the previous section, or files with formats “.jar”, “.adf”, “.jam”, “.scr”, “.sp”, then you need to take measures to get them into a working state. Each case is different. Some may require simple renaming, some may require .jam rebuilding (some of the files which are actually “.jam”s are in a weird format which can’t be read without a hex editor). Then, if you do find proper files which are of proper formatting, and you also have an uninitialised (without a 64-byte header) “.sp” file, use keitai-tools to modify the scratchpad file with a header, which will let the game load without any problems in the SDK.