Binder

Priv Kit connects applications to explicit Binder endpoints and system services while preserving raw transaction contracts. The application supplies the framework interface and defines the domain behavior built on top of it.

Access a system service

Resolve an explicit service name through the connected Privileged Server:

val activityBinder = PrivilegeBinderWrapper.fromSystemService("activity")
val activityManager = IActivityManager.Stub.asInterface(activityBinder)

Log.d(
    "activity",
    activityManager.getTasks(1).toString(),
)

Some services must be resolved inside the shell or root server process:

val binder = PrivilegeBinderWrapper.fromSystemService(
    serviceName = "miui.mqsas.IMQSNative",
    source = PrivilegeSystemServiceSource.SERVER_PROCESS,
)

The integrating app owns the framework interface and the meaning of each transaction.

Understand failures

Project-owned control calls normalize a missing or dead server to PrivilegeServerUnavailableException. Raw wrapper calls keep forwarded Binder failures unchanged, preserving the uncertainty between a target Binder death and a Privileged Server death for application-specific recovery.

Use PrivilegeBinderCall.orElse(...) when the app has an explicit fallback for a server-related or UserService Binder invocation:

• PrivilegeBinderCallFailure.ServerUnavailable means the Privileged Server was unavailable.
• PrivilegeBinderCallFailure.BinderDied means a directly called endpoint died.
• Other exceptions retain their original semantics.

Use fallbacks for recovery paths that remain safe when the remote result is uncertain. The remote process may have completed a mutating operation before dying.

Keep domain behavior in the app

The library transports Binder calls. The app remains responsible for:

• choosing and compiling any hidden framework interface;
• validating arguments and permissions;
• interpreting results;
• deciding whether an operation is safe to retry;
• defining high-level Android operations in the app's own contract.