Codex PS5 - Prototype (PPSA99105)

[NevesHenry]

Existing thread

• I searched this category for the title ID and no thread exists for this title on any platform.

Title

Codex PS5 - Prototype (PPSA99105)

Content version tested

00.000.004. This is the codex-ps5-0.0.4-Folder.zip release of Portablelle/Codex-PS5. Its SHA-256 is b6f8952b72eaa4806baab21634aae950f69a365bee4215a373d750e8f652364b, the same as in the darkxex homebrew catalog. The title is the front end only. Its engine is a separate payload, assistant-service.elf, which listens on 127.0.0.1:49322. According to the release's INSTALL.md, that payload needs a jailbroken console with an ELF loader. I didn't run it.

AnyPS5 commit

main e61a7c7

System tested

Ubuntu 22.04 on WSL2, Ryzen 9 7900, lavapipe, GCC 13, Release (Xvfb in a container with loopback only)

Furthest point

Boot. VideoOut opens at 1920x1080, the title writes frames, and it keeps retrying its service connection.

What is shown

The title starts, opens the pad and VideoOut, and writes this to /download0/codex-ps5-network.log:

User service initialized
Pad initialized
Network initialized
connect timeout 8041012d 0000002d
Cached CPU raster enabled; VideoOut buffers are write-only
VideoOut initialized at 1920x1080
Controller handle opened
connect timeout 8041012d 0000002d
connect timeout 8041012d 0000002d
...

The connect timeout line repeats every 500 ms. Its first number is SCE_NET_ERROR_EOPNOTSUPP. A stand-in listener on 127.0.0.1:49322 never gets a connection.

Current blocker

Before connecting, the title sets SOL_SOCKET option 0x1109 (shadPS4's ORBIS_NET_SO_CONNECTTIMEO, microseconds) to 1,500,000. sceNetSetsockopt fails that option with EOPNOTSUPP. The title then closes the socket and tries again, so it never calls sceNetConnect.

Open pull request: #11571 (accepts 0x1109 and bounds a blocking sceNetConnect by it). With it, the title connects and sends its initialize request ({"id":1,"method":"initialize",...,"clientInfo":{"name":"codex_ps5","title":"Codex PS5","version":"0.0.4"}}). With nothing listening, it gets connect 8041013d 0000003d (ECONNREFUSED), which is what it sees on a console when the service isn't running.

How it was run

1. Unpacked the release zip and unwrapped eboot.bin and sce_module/libc.prx with tools/unwrap_self.py.
2. Relinked with relinker --registry.
3. Ran app.elf for 30 s without input, with and without a stand-in TCP listener on 127.0.0.1:49322.

AI-assisted report (Claude Code).