Ephinea PSO BB natively on Android via Winlator

By opening the launcher? Which you need mono and internet for,

Would still like to try xinput one day.
Anyway got joystick issue fixed on newer winlator. fix from discord (that i tried once and couldnt get it to work on cmod, got integrated. this it dll maps xinput to dinuput) Using this. https://github.com/MrPhryaNikFrosty/Winlator-Frost/releases/tag/0.3.0.1

Works fully now no issue. 30fps 1600/900
tried attaching a gif but this forum errors out every time.

But yea works 100% now. if anyone wants the settings u can ask.
 
Last edited:
tried getting this to run and i managed to do everything but the game on bottom left reads DLL Error and logging in does nothing. :')
 
okay didn't use the winlater that was posted on 3rd page.

also had to run it on direct x12

ps. using Samsung Tab S9 Tablet
 
i'll try to update my winlator guide with the last working settings. everything works for me on multiple devices. just been busy
 
After banging my head against the wall trying to get Ephinea PSOBB to work (it still doesn't for me, at least) I decided to try Ultima PSOBB to see if I could get that to run. The installation worked just fine, but launcher's updater didn't work, so I simply copied all the client's files from another machine onto my phone. I did have to add ultima.dll to the list of libraries within the Wine configuration menu and set that to Native Only. To my surprise, it works great!

Winlator@Frost 10.0Final v4.1
Device chipset = Snapdragon 8 Gen2
Android version = 15
Box64 = v0.3.6
Box64 Preset = Performance
Preferred Input API = DirectInput
Driver = Turnip 25.2.0 (set to 4GB VRAM)
DXVK = v2.6.2
Startup = Aggressive
Windows version = 10
Resolution = 1280x720
Env variables changed = WINEESYNC set to DISABLED

If I had to guess, I think the problem we were facing with the error 916 and/or freezing was because of ephinea.dll (or other DLLs) not being able to hook into the game's process correctly. Something similar happens to Skyrim SE when you try to use the SKSE (a script extension library, with its own DLLs) loader within a container.

I'll continue trying things out!
 

Attachments

  • Screenshot_20250619-213750.png
    Screenshot_20250619-213750.png
    1.9 MB · Views: 29
  • Screenshot_20250619-213505.png
    Screenshot_20250619-213505.png
    2.3 MB · Views: 29
Last edited:
(GOOGLE TRANSLATED TO ENGLISH)

After a long time, i was able to configure the game to run on my phone (Galaxy S22+) with a Snapdragon 8 gen 1 processor, even resolving my error (No. 916).

The container needs services set to Aggressive so it can start logging in (result: error no. 916). However, if you start the container with services set to Essential or Normal (result: black screen), it fails to start, resulting in a weird loop.

My solution to the error no. 916 is as follows:

1. Open the container and open the PSOBB launcher.
2. Set the game to windowed.
3. Log in and DO NOT PRESS ANY BUTTON ON THE SERVER INFO SCREEN (This Screen)
4. Open Winlator's task manager and run the default task (taskmgr.exe).
5. Once both programs are open (taskmgr.exe and the game), move the windows to show both programs at the same time.
6. Click on the game and IMMEDIATELY AFTER THE BLUE ICON DISAPPEARS IN THE CORNER, DO THE NEXT STEP.
7. In the Task Manager, click New Task and start the following task: services.exe

This will start the stopped services and resolve error no. 916.

This process involves several attempts. If you don't start the services.exe task at the right time, you'll get error 916 or the game will crash, so it requires several attempts. I hope it will be easier in the future, with another Winlator mod, process or an update to the original GitHub, I don't know. For now, this process fixes error No.916.

MY WINLATOR SETTINGS ARE SIMILAR AS IN THE PREVIOUS POST
(Winlator@Frost 10.0 Final v4.1
Device chipset = Snapdragon 8 Gen1
Android version = 15
Box64 = v0.3.6
Box64 Preset = Compatibility
Preferred Input API = DirectInput
Driver = Turnip 25.2.0 (set to 4GB VRAM)
DXVK = v2.6.2
Startup = Aggressive
Windows version = 7
Resolution = 1280x720
Env variables changed = WINEESYNC set to DISABLED)

And the installation of the app and the game in general can be found in This post

My Discord name is Mobo
 
Last edited:
Mobo said:
(GOOGLE TRANSLATED TO ENGLISH)

After a long time, he was able to configure the game to run on my phone (Galaxy S22+) with a Snapdragon 8 gen 1 processor, even resolving my error (No. 916).

The container needs services set to Aggressive so it can start logging in (result: error no. 916). However, if you start the container with services set to Essential or Normal (result: black screen), it fails to start, resulting in a weird loop.

My solution to the error no. 916 is as follows:

1. Open the container and open the PSOBB launcher.
2. Set the game to windowed.
3. Log in and DO NOT PRESS ANY BUTTON ON THE SERVER INFO SCREEN (This Screen)
4. Open Winlator's task manager and run the default task (taskmgr.exe).
5. Once both programs are open (taskmgr.exe and the game), move the windows to show both programs at the same time.
6. Click on the game and IMMEDIATELY AFTER THE BLUE ICON DISAPPEARS IN THE CORNER, DO THE NEXT STEP.
7. In the Task Manager, click New Task and start the following task: services.exe

This will start the stopped services and resolve error no. 916.

This process involves several attempts. If you don't start the services.exe task at the right time, you'll get error 916 or the game will crash, so it requires several attempts. I hope it will be easier in the future, with another Winlator mod, process or an update to the original GitHub, I don't know. For now, this process fixes error No.916.

MY WINLATOR SETTINGS ARE SIMILAR AS IN THE PREVIOUS POST
(Winlator@Frost 10.0 Final v4.1
Device chipset = Snapdragon 8 Gen1
Android version = 15
Box64 = v0.3.6
Box64 Preset = Compatibility
Preferred Input API = DirectInput
Driver = Turnip 25.2.0 (set to 4GB VRAM)
DXVK = v2.6.2
Startup = Aggressive
Windows version = 7
Resolution = 1280x720
Env variables changed = WINEESYNC set to DISABLED)

And the installation of the app and the game in general can be found in This post

My Discord name is Mobo
Click to expand...
thanks!
 
Mobo said:
(GOOGLE TRANSLATED TO ENGLISH)

After a long time, i was able to configure the game to run on my phone (Galaxy S22+) with a Snapdragon 8 gen 1 processor, even resolving my error (No. 916).

The container needs services set to Aggressive so it can start logging in (result: error no. 916). However, if you start the container with services set to Essential or Normal (result: black screen), it fails to start, resulting in a weird loop.

My solution to the error no. 916 is as follows:

1. Open the container and open the PSOBB launcher.
2. Set the game to windowed.
3. Log in and DO NOT PRESS ANY BUTTON ON THE SERVER INFO SCREEN (This Screen)
4. Open Winlator's task manager and run the default task (taskmgr.exe).
5. Once both programs are open (taskmgr.exe and the game), move the windows to show both programs at the same time.
6. Click on the game and IMMEDIATELY AFTER THE BLUE ICON DISAPPEARS IN THE CORNER, DO THE NEXT STEP.
7. In the Task Manager, click New Task and start the following task: services.exe

This will start the stopped services and resolve error no. 916.

This process involves several attempts. If you don't start the services.exe task at the right time, you'll get error 916 or the game will crash, so it requires several attempts. I hope it will be easier in the future, with another Winlator mod, process or an update to the original GitHub, I don't know. For now, this process fixes error No.916.

MY WINLATOR SETTINGS ARE SIMILAR AS IN THE PREVIOUS POST
(Winlator@Frost 10.0 Final v4.1
Device chipset = Snapdragon 8 Gen1
Android version = 15
Box64 = v0.3.6
Box64 Preset = Compatibility
Preferred Input API = DirectInput
Driver = Turnip 25.2.0 (set to 4GB VRAM)
DXVK = v2.6.2
Startup = Aggressive
Windows version = 7
Resolution = 1280x720
Env variables changed = WINEESYNC set to DISABLED)

And the installation of the app and the game in general can be found in This post

My Discord name is Mobo
Click to expand...
How did you even figure this out? Was this just in the logs or something? This did fix my problem but man is this a pain in the ass to do every time.
 
Last edited:
I have been trying to get this to work forever on my Retroid Pocket 4 pro. I followed all of the steps exactly. However, when I go to Shortcuts and click "Ephinea Launcher" the screen goes to black and a white arrow (mouse) appears on the screen. Nothing further happens. When I click on the PSOBB shortcut, it goes black with the white arrow, and then crashes back to winlator. Does anyone have any idea what I am doing wrong??
 
M8P177 said:
I have been trying to get this to work forever on my Retroid Pocket 4 pro. I followed all of the steps exactly. However, when I go to Shortcuts and click "Ephinea Launcher" the screen goes to black and a white arrow (mouse) appears on the screen. Nothing further happens. When I click on the PSOBB shortcut, it goes black with the white arrow, and then crashes back to winlator. Does anyone have any idea what I am doing wrong??
Click to expand...

If you're struggling to get the launcher to run check these:
  • Box64 version
  • Box64 preset
  • dxvk version (or VKD3D/VirGL)
  • Driver version
  • Wine mono version
  • Wine gecko version
  • VC Redistributables installed

If your game is crashing on startup, check these:
  • Box64 preset
  • Game API selected (D3D8/D3D12/Vulkan/etc)
  • Game Resolution
  • DXVK version (or VKD3D/VirGL)
  • Box64 version
  • Driver version
  • VC Redistributables installed
  • DX Runtimes installed
  • Wine Mono installed
  • Wine Gecko installed
  • Additional game settings (those available to the launcher/registry)
If nothing works still, you could try working around it using a second computer to export a set of registry entries for use in your container
(treat this workaround as a last resort)

This assumes your device's Ephinea client is up to date (Launcher & Game)
  1. Use a second computer with its own installation
  2. Open the launcher
  3. Change the game's API to anything other than what is crashing you. (I found D3D8 or D3D9 works best for my device)
  4. Change the game's resolution to match that of your device's container
  5. Change the game's Windowed mode to Fullscreen
  6. (Optional) Enable Fast Startup
  7. Click on More and Enable 'Save ID and pass'
  8. Log in to the game world on your character and enter a lobby
  9. Quit the game
  10. Open the registry editor ('regedit' without quotes after pressing Win+R)
  11. Navigate to [HKEY_CURRENT_USER\Software]
  12. Right click "SonicTeam" and click export. Save that on your desktop
  13. Copy that exported .reg file onto your device and make it accessible to your container (your android's downloads folder is D: in the container by default)
  14. Launch your container
  15. Open your container's the registry editor (Start-> System Tools -> Registry Editor)
  16. In the Registry Editor, Click on the top left where it says 'Registry' and select Import Registry File
  17. Select the registry entries that you exported
  18. Close Registry Editor
  19. Launch the game.

In my experience, the instant crash to desktop was usually remedied by changing the game's API, the box64 preset/version, and the wrapper version/settings. I'd start there first.
 
greyscale said:
If you're struggling to get the launcher to run check these:
  • Box64 version
  • Box64 preset
  • dxvk version (or VKD3D/VirGL)
  • Driver version
  • Wine mono version
  • Wine gecko version
  • VC Redistributables installed

If your game is crashing on startup, check these:
  • Box64 preset
  • Game API selected (D3D8/D3D12/Vulkan/etc)
  • Game Resolution
  • DXVK version (or VKD3D/VirGL)
  • Box64 version
  • Driver version
  • VC Redistributables installed
  • DX Runtimes installed
  • Wine Mono installed
  • Wine Gecko installed
  • Additional game settings (those available to the launcher/registry)
If nothing works still, you could try working around it using a second computer to export a set of registry entries for use in your container
(treat this workaround as a last resort)

This assumes your device's Ephinea client is up to date (Launcher & Game)
  1. Use a second computer with its own installation
  2. Open the launcher
  3. Change the game's API to anything other than what is crashing you. (I found D3D8 or D3D9 works best for my device)
  4. Change the game's resolution to match that of your device's container
  5. Change the game's Windowed mode to Fullscreen
  6. (Optional) Enable Fast Startup
  7. Click on More and Enable 'Save ID and pass'
  8. Log in to the game world on your character and enter a lobby
  9. Quit the game
  10. Open the registry editor ('regedit' without quotes after pressing Win+R)
  11. Navigate to [HKEY_CURRENT_USER\Software]
  12. Right click "SonicTeam" and click export. Save that on your desktop
  13. Copy that exported .reg file onto your device and make it accessible to your container (your android's downloads folder is D: in the container by default)
  14. Launch your container
  15. Open your container's the registry editor (Start-> System Tools -> Registry Editor)
  16. In the Registry Editor, Click on the top left where it says 'Registry' and select Import Registry File
  17. Select the registry entries that you exported
  18. Close Registry Editor
  19. Launch the game.

In my experience, the instant crash to desktop was usually remedied by changing the game's API, the box64 preset/version, and the wrapper version/settings. I'd start there first.
Click to expand...

this will be quite helpful to people im sure but its a lot to take in too and manual.

The problem with fully importing registry files is it could also lead to a broken instance and not work at all. *could get dll error etc)As you said, last resort is probably right unless you have it nailed down. The sonicteam reg entry is not the only one too.
The only reg install i automated that worked clean was login credentials.
 
Has anyone here gotten it to work on an Odin 2? I can’t get it to work at all.

It crashes on log in if I select anything but DirecX11 in the launcher.

If I select Dx11, it FREEZES at log in, unless I kill services.exe, which allows me to bypass the freeze and get hit with error 916.

I’ve been at this for hours. Trying multiple settings in winlator.

I followed all of yummaypatrol’s steps for the most recent guide (only reason I even got the launcher to boot).

Just at a loss, with no clue what to do
 
I got the ephinea client to run on my android phoe, but I didnt figure out how to log in :P (never got the controls properly figured out and had to go to bed for work x_x)
 
So I managed to get this to sort of work on my phone (Sony Xperia 1 V; Snapdragon 8Gen2; Android 15)


Using Gamehub 5.1.0

Code: 
Compatiblity Layer:    proton10.0-arm64x-2
Translation Params:    Performance
DInput Library:        Prefer Native
GPU Driver:            Turnip_v25.3.0_R10
Surface Format:        RGBA8
Audio Driver:          Pulse
DXVK Version:          dxvk-2.6-arm64ec-async or dxvk-2.3.1-arm64ec
VKD3D Version:         NONE
CPU Translator:        Fex_20250910
Core Limit:            No Limit
VRam Limit:            No Limit

Components installed:
  • vcredist2022 (aka vcredist2015-2022)
Game Settings:
Code: 
Resolution:    1280x720
Window mode:   Virtual Full Screen
Direct3D API:  Direct3D 9
Low Perf:      On (Didn't seem to have much of an observable effect)
Fast Startup:  On
Motion Blur:   Off
Bloom:         Off
DOF:           Off
Detect Pad:    On



NOTES:

  • Within "Wine Configuration", PSOBB.exe's Windows version should be set to "Windows 7". Additionally, online.exe should be set to Windows 7. Use online.exe as your launcher
  • While the game doesn't require mono/gecko installed, the Launcher does.
  • There is additional setup required. You will need a copy of PSO's registry entries (Detailed in a previous post i made in this thread).
  • I noticed that under these settings, EphineaPSO would not run above 14-15FPS. Like, hard capped at 15FPS at all times, regardless if your phone has the horsepower or not. Strangely, if the ephinea.dll fails to load (like when you launch PSO directly without the required registry entries), the game runs at a locked 30FPS. However, you will not be able to log in.
  • Additionally, with these settings, online.exe and online_win7.exe would fail to launch. You're either met with nothing happening or a completely blacked-out window where the launcher should be. Changing the compatibility layer to "proton10.0-x64-1" fixes this, however it will also make psobb.exe crash on launch. If you change the compatibility layer in Gamehub in a container that's already been made, it will reset the registry and you will have to reinstall all the additional components from container options.
  • When either online.exe or online_win7.exe launch correctly, they eat up a staggering >800MB of memory at startup (The launcher, not the game!)
  • I also experienced a couple of instances of hard freezing, requiring a forced shutdown of Gamehub.
  • I was unable to get EphineaPSO to run properly on any version of Winlator. (EDIT 2025-10-08: I managed to get it working. Same results as Gamehub)
  • Keyboard support is EXCELLENT on Gamehub. works right out of the box, unlike Winlator.
 

Attachments

  • Screenshot_20251005-013953.png
    Screenshot_20251005-013953.png
    3.2 MB · Views: 13
  • Screenshot_20251005-021513.png
    Screenshot_20251005-021513.png
    2.5 MB · Views: 12
  • Screenshot_20251005-225832.png
    Screenshot_20251005-225832.png
    3.2 MB · Views: 12
Last edited:
--ignore--
S25 Ultra
Android 16 (OneUI 8)
winlator ludashi 2.9
proton 9.0 arm64ec
FEX 2601
DXVK 2.7.1 async
Essential or Normal Services.

After setting the wine version to windows 7 for psobb.exe, adding ephinea.dll to libraries tab and making sure my registry entries are present (read: delete the classic fullscreen reg entry in the ephinea reg subfolder to get it from insta crashing) i have the game booting into the main menu with the Ephinea client DLL loading. however, upon trying to connect (yes, services.exe is present when trying), it gives me a 916 error.
Edit:
Scratch that. Using Winlator CMod 1.13.1 with Wine 10 instead of winlator ludashi got it working for me.
--ignore--

Here's my documented way to get it working on my s25 ultra:
Winlator version: Winlator CMod (Coffincolors) 1.13.1
Important container settings:
Wine 10 arm64ec (proton 9 arm64ec also works)
DXVK 2.7.1 gplasync arm64ec (enable async and async cache) (using this myself as i use turnip 8xxx v26 drivers)
Fexcore 2603
Fastest TSOMode
Fast X87
Multiblock Enabled
adjust cores (s25 ultra, only 4 and 5 enabled)
Essential Services

1 - Create Container with settings above, Install Mono, Gecko and Visual C++ Redists 2015-2022 (an AIO is a good idea) and copy over the PSOBB folder from PC (installer may work, YMMV on that).
2 - Set PSOBB.exe to windows 7 compatibility and add ephinea to the libraries tab as native, builtin.
3 - either configure a low end setup on your PC or use the registry file in the code below and import it or some of it's entries into regedit (grpahicctrl is configured to be more mobile friendly). no matter what though, delete the CLASSIC_FULLSCREEN registry entry if it is present, it causes crashes upon startup.
Code: 
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\SonicTeam\PSOBB]
"ACCOUNT_CHECK"=dword:00000001
"ACCOUNT_CTRL"=hex:3d,aa,d0,6e,ae,64,cd,48
"BILLING_SITE"="https://ephinea.pioneer2.net"
"CLIENT_CODE"=dword:0000000e
"CTRLBUF"=hex:02,00,00,00,01,00,00,00,00,00,00,00
"EXT0"=dword:00000002
"FOCUS_SOUND"=dword:00000001
"FONT_JPN"="Tahoma"
"GRAPHICCTRL"=hex:03,00,00,00,00,00,00,00,01,00,00,00,01,00,00,00,02,00,00,00,\
  02,00,00,00,00,00,00,00,00,00,00,00,00,00,ff,ff
"INSTALL"=dword:00000001
"OFFICIAL_SITE"="https://ephinea.pioneer2.net"
"OldCheck"=dword:00000001
"SOUNDCTRL"=hex:01,00,00,00,01,00,00,00,01,00,00,00
"WINDOW_MODE"=dword:00000000
"WORD_WRAP"=dword:00000001

[HKEY_CURRENT_USER\Software\SonicTeam\PSOBB\Ephinea]
"ACCOUNT_CHAR_SELECTS"=hex(7):6a,00,6a,00,78,00,62,00,3d,00,30,00,20,00,00,00,\
  00,00
"AF_QUALITY"=dword:00000000
"AUTO_DETECT_ACTIVE_GAMEPAD"=dword:00000000
"BANK_SHORTCUTS"=dword:00000000
"BGM_LEVEL"=dword:00000006
"BLINKING_SDJZ"=dword:00000001
"CAMERA_CONTROL"=dword:00000000
"CAMERA_DEADZONE"=dword:0000000a
"CAMERA_KEY_LEFT_STR"=""
"CAMERA_KEY_RIGHT_STR"=""
"CAMERA_KEYS_ENABLED"=dword:00000000
"CAMERA_SENSITIVITY"=dword:00000005
"CHARACTER_BANK"=dword:00000001
"CHASE_CAM_STYLE"=dword:00000000
"CLASSIC_INTRO"=dword:00000000
"DAMAGE_SCALE"=dword:00000064
"DGV_DISABLETOGGLE"=dword:00000000
"DGV_PRESENTATION"=dword:00000000
"DGV_USEPHONG"=dword:00000000
"DGV_VRAM"=dword:00000000
"DISABLE_MOTION_BLUR"=dword:00000001
"DISABLE_NEW_FONT"=dword:00000000
"ENHANCED_MAP_DRAW"=dword:00000000
"FAST_STARTUP"=dword:00000001
"HUD_SCALE"=dword:000000a0
"IME"=dword:00000000
"LANG"=dword:00000000
"LARGE_BANK_WINDOW"=dword:00000001
"LOW_PERF"=dword:00000001
"MAG_ALERT_ENABLED"=dword:00000000
"MAG_ALERT_TIME"=dword:0000001e
"MENU_SCROLL_REPEAT_DELAY"=dword:00000006
"MENU_SCROLL_REPEAT_INTERVAL"=dword:00000005
"MSAA_QUALITY"=dword:00000000
"NEW_FONT_RES"=dword:00000000
"NEW_RES_HEIGHT"=dword:000002d0
"NEW_RES_WIDTH"=dword:00000500
"NO_DAMAGE_SCALE"=dword:00000000
"NO_MINIMAP_SCALE"=dword:00000000
"NO_SKIN_SFX"=dword:00000000
"NUMPAD_AS_NUMBER_KEYS"=dword:00000000
"OPM_INVULNERABILITY"=dword:00000001
"PAGEUPDOWN_ITEMS"=dword:00000000
"PICKUP_AND_PB_ALT_KEY"=dword:00000000
"PICKUP_AND_PB_PAD_CONFIG"=dword:00000000
"PICKUP_AND_PB_PATCH_ENABLED"=dword:00000000
"PICKUP_AND_PB_SHIFT_KEY"=dword:00000000
"PICKUP_AND_PB_SPECIFIED_KEY"=dword:00000000
"PICKUP_AND_PB_SPECIFIED_KEY_VALUE"=dword:00000000
"PRIMITIVE_SCALE"=dword:00000064
"QUICK_MENU_MATERIALS"=dword:00000001
"QUICK_MENU_UNTEKKED_WEAPONS"=dword:00000001
"RARE_DROP_SFX"=dword:00000001
"RES_HUD"=dword:00000000
"SFX_LEVEL"=dword:00000006
"SHOW_MOB_DROP"=dword:00000000
"USE_BLOOM"=dword:00000000
"USE_CELSHADER"=dword:00000000
"USE_CLEARTYPE"=dword:00000000
"USE_D3D9"=dword:00000003
"USE_DOF"=dword:00000000
"USE_NEW_CAPTURE"=dword:00000000
"USE_SSAO"=dword:00000000
"USE_TONEMAP"=dword:00000000
"USE_XINPUT"=dword:00000001
"XINPUT_AXIS_SNAPPING"=dword:0000000a
"XINPUT_DEADZONE_RADIUS"=dword:0000000a
"XINPUT_TRIGGER_PRESS"=dword:0000000a
4 - Create your shortcut to PSOBB.exe and run it. it'll complain about xinput but ok past that and you have it going.
5 - Optional - Edit resolution with NEW_RES_HEIGHT and NEW_RES_WIDTH (above reg file has 1280x720 set). Play around with USE_D3D9 and USE_XINPUT if you wish as well.

I've been using external keyboards to do any entry but using the "RTS" touch profile will let you do keyboard input where absolutely needed (recommend external kb though), i haven't been able to get android keyboard working though.
 
Last edited:
You must log in or register to reply here.
Back
Top