AnyPS5/docs/dev/debt/libSceNpSessionSignaling.md

libSceNpSessionSignaling technical debt

Unknown function info

• sceNpSessionSignalingGetMemoryInfo (libSceNpSessionSignaling) - unknown signature
• sceNpSessionSignalingGetConnectionStatistics (libSceNpSessionSignaling) - unknown signature
• sceNpSessionSignalingGetConnectionStatus (libSceNpSessionSignaling) - (int32 context id, int32 connection id, int32* status, SceNetInAddr* peer address, uint16* peer port) is ASTRO BOT's (PPSA21564 01.007.000) call at 0x30622B: the context id from a 32-bit field, the connection id, three stack outputs, a negative result taken as an error, then the address passed to sceNetInetNtop(AF_INET, ...) and the port to sceNetNtohs. It matches PS4's sceNpSignalingGetConnectionStatus. The title reaches it only for a connection id from the signaling library, which offline never hands one out. No session ever activates offline, so every connection id answers CONN_NOT_FOUND (0x8055330C, from shadPS4) without writing the outputs, and a null status answers INVALID_ARGUMENT. The context id is not checked, as contexts are not tracked. The console's answer for an unknown context or connection is unverified
• sceNpSessionSignalingCreateJoinActivate, sceNpSessionSignalingGetCustomProperty, sceNpSessionSignalingGetGroupFromPeerAddress, sceNpSessionSignalingInitializeWithPort, sceNpSessionSignalingJoinActivate and sceNpSessionSignalingSetCustomProperty (libSceNpSessionSignaling) - names and NIDs are present in the PS5 3.20 export inventory, but no credible prototypes were found. They are declared without parameters solely to resolve known imports; this is not an ABI claim.

Functional

• sceNpSessionSignalingGetGroupInfo, sceNpSessionSignalingGetGroupFromSessionId, sceNpSessionSignalingGetConnectionFromNetAddress, sceNpSessionSignalingGetConnectionFromNetAddress2, sceNpSessionSignalingGetConnectionFromPeerAddress, sceNpSessionSignalingGetConnectionFromPeerAddress2 (libSceNpSessionSignaling) - the signatures, the null-pointer result (0x80553303) and the not-found results (group 0x8055330A, connection 0x8055330C) are the console module's. No session ever activates here, so every lookup ends at not-found. The console module's two earlier checks are not reproduced, because neither initialization nor contexts are tracked: an uninitialized library (0x80553301) and an unknown context id (0x80553308) get the same not-found result