MuntashirAkon/AppManager · error

Error! Could not start local server

Error message

Error! Could not start local server: %s\n

What it means

execv("/system/bin/app_process", exec_argv) returned in the forked child, which only happens when the exec itself failed — e.g. app_process is missing, lacks the execute bit, or the argument list is invalid. The child reports errno, unlinks both copied jars, and exits, so the background server never starts.

Solutions

1. Verify /system/bin/app_process exists and is executable on the target device
2. Check errno (ENOENT vs EACCES vs E2BIG) to pinpoint the cause
3. Ensure the CLASSPATH jar and JAR_MAIN_CLASS are valid for the exec'd runtime
4. Fall back to an alternative server-start mechanism (e.g. app_process64 or a shell wrapper)

When it happens

Trigger: Thrown at app/src/main/cpp/run_server.c:269 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of MuntashirAkon/AppManager@0152f468fc (2026-09-12). Data as JSON: /api/errors/d2d4b8b3b9cf19c6. Report an issue: GitHub.

Appendix: source

Thrown at app/src/main/cpp/run_server.c:269

        exit(1);
    }

    // Detach from shell
    int null_fd = open("/dev/null", O_RDWR | O_CLOEXEC);
    if (null_fd >= 0) {
        dup2(null_fd, STDIN_FILENO);
        dup2(null_fd, STDOUT_FILENO);
        dup2(null_fd, STDERR_FILENO);
        if (null_fd > STDERR_FILENO) {
            close(null_fd);
        }
    }

    // Execute local server
    execv("/system/bin/app_process", exec_argv);

    // If execv returns, an error occurred
    fprintf(stderr, "Error! Could not start local server: %s\n", strerror(errno));

    // Cleanup
    unlink(exec_jar_path);
    unlink(main_jar_path);
    free(exec_argv);
    exit(1);
}

View on GitHub (pinned to 0152f468fc)