Quest Emu Setup

This project provides tools for setting up a Quest-like emulator and patching APK files to run within it.

Usage: quest_emu_setup [OPTIONS] <COMMAND>

Commands:
  setup  
  apk    
  help   Print this message or the help of the given subcommand(s)

Options:
      --yes   Skip all prompts and use default values
  -h, --help  Print help

Debugging native code (lldb-dap)

quest_emu debug install <package> [arch]   # push + copy lldb-server into the app's private storage
quest_emu debug attach <package>           # install + start lldb-server + attach info, in one go

attach installs lldb-server into the app's private storage, starts it as a platform server, forwards the debug port, and by default attaches to the app as it's already running — pass --relaunch to force-stop and relaunch it fresh first (useful right after installing/reinstalling the app, or when you want a clean process). It prints the 4 lines needed to actually connect a debugger once the target process is found:

Port: 5039
Attach URI: vscode://llvm-vs-code-extensions.lldb-dap/start?config=...
PID: 12345
Config: {"request":"attach","pid":12345,"attachCommands":[...]}

Example: debugging a QPM mod

If you're iterating on a QPM mod, build it first so quest_emu has a .so with debug symbols to load, then attach with that build folder as --symbols (any .so files under it are picked up automatically):

qpm build   # or ./build.sh / build.ps1, produces ./build/libmymod.so

quest_emu debug attach com.beatgames.beatsaber --relaunch --symbols ./build --open

--open opens the printed Attach URI in VS Code directly (requires the llvm-vs-code-extensions.lldb-dap extension) and starts debugging immediately, no launch.json needed.

Example: tasks.json + launch.json, fully automatic with F5

For a reusable debug entry instead of --open, use quest_emu as a preLaunchTask that writes the fresh pid to a file, and read it back into launch.json with the Command Variable extension:

.vscode/tasks.json:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "quest-emu: attach",
      "type": "shell",
      "command": "quest_emu",
      "args": [
        "debug", "attach", "com.beatgames.beatsaber",
        "--relaunch",
        "--symbols", "./build",
        "--pid-file", "${workspaceFolder}/.vscode/.quest-pid"
      ],
      "problemMatcher": [],
      "presentation": { "reveal": "always", "panel": "dedicated" }
    }
  ]
}

.vscode/launch.json:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Attach to Quest mod (lldb-dap)",
      "type": "lldb-dap",
      "request": "attach",
      "preLaunchTask": "quest-emu: attach",
      "pid": "${input:questPid}",
      "attachCommands": [
        "platform select remote-android",
        "settings set target.inherit-env false",
        "platform connect connect://localhost:5039",
        "attach -p ${input:questPid}",
        "pro hand -p true -s false SIGPWR",
        "pro hand -p true -s false SIGXCPU",
        "pro hand -p true -s false SIG33",
        "target symbols add ./build/libmymod.so"
      ]
    }
  ],
  "inputs": [
    {
      "id": "questPid",
      "type": "command",
      "command": "extension.commandvariable.file.content",
      "args": { "fileName": "${workspaceFolder}/.vscode/.quest-pid" }
    }
  ]
}

Hitting F5 runs the task (installs/starts lldb-server, force-stops and relaunches the app, writes its pid to .vscode/.quest-pid), then the questPid input re-reads that file — after the task finishes, so it's always current — and feeds it into both the pid field and the attach -p command before lldb-dap connects. No copy-pasting between runs.

• platform connect connect://localhost:<port>: the port is adb forwarded to the device, so it's always localhost; update it if you pass --port.
• target symbols add <path>: one per .so under the path(s) passed to --symbols — here, QPM's ./build output.