Controller Rescue 0.3.0 · One app

One app. One APK. All three shortcuts.

Controller Rescue now includes the optional LSPosed power module. The recovery button, connection check, volume shortcuts, and Double Power settings live together. The interface stays English-only and minimal.

Download controller-rescue-0.3.0.apk. Root is required. LSPosed/Vector is only needed for Double Power.

Upgrading from v0.2.x

1. Turn off Double Power in the app.
2. Disable and uninstall Controller Rescue · Power.
3. Install the new APK over Controller Rescue; your settings are preserved.
4. Enable Controller Rescue in LSPosed for System Framework / Android System, then reboot normally. If root is temporary, restore it through your usual rooting tool.
5. Turn on Double Power and use Test shortcuts first.

Do not run both modules together. Removing a module does not unload its running hooks; the full reboot is required. Setup details.

Still restricted to the tested Quest 3 / Quest OS build 52433670036000520. Recovery briefly pauses tracking and preserves pairing. The existing two-minute cooldown is unchanged.

Validation: 89 policy/sequence checks passed. APK signing, alignment, embedded module entry point, and exclusion of Xposed API classes were verified. The APK updated an existing installation successfully with the same signing certificate. Physical gestures were previously verified with the separate v0.2.x packages; the unified module has not yet been verified on physical buttons after activation. This remains a prerelease.

Controller Rescue 0.2.1

The same two-minute recovery cooldown now shows a live countdown, such as Try again in 1:42. It never queues or retries a repair when the timer ends.

• controller-rescue-0.2.1.apk: English-only recovery app, connection check, direct root-assisted accessibility setup, double Volume Up and double Volume Down.
• controller-power.apk: optional LSPosed/Vector companion v1.0.1 for double Power. This APK is unchanged from the previous release.
• SHA256SUMS: checksums for both APKs.

All three physical gestures were verified on the tested Quest 3 with app v0.2.0 and power companion v1.0.1. Double Power kept the headset awake and dispatched a real recovery; both controllers were subsequently connected. This UI-only update leaves shortcut behavior unchanged; v0.2.1 was installed and its connection check confirmed both controllers connected. If Android stops the app during recovery, it reports interrupted verification; use Check connection afterward.

Requires root and Quest OS build 52433670036000520. Recovery briefly pauses tracking and does not clear pairing. The power companion needs System Framework / Android System scope (Vector CLI: system/0) and a normal full headset reboot for activation. Avoid partial zygote restarts; see the power setup notes.

The app remains an early release for one tested firmware build. Nineteen app policy checks and seventy power-policy/sequence checks passed; APK signing and alignment were verified. Source and setup.

Controller Rescue 0.2.0

Controller recovery for rooted Quest 3, with an English-only minimal interface.

• controller-rescue-0.2.0.apk: repair button, connection check, double Volume Up and double Volume Down.
• controller-power.apk: experimental LSPosed/Vector add-on for double Power; physical verification is still pending. Activate only System Framework / Android System; Vector CLI uses system/0.
• SHA256SUMS: checksums for both APKs.

In the app, open Settings and select Enable volume shortcuts, then turn on the shortcuts you want. Accessibility is enabled directly with root while preserving existing services. Use Test shortcuts to check button delivery before running recovery.

Requires root and Quest OS build 52433670036000520. Recovery briefly restarts the shared sensor service; it does not clear pairing or provide a permanent firmware fix.

Source and setup

Validation: 89 local policy/sequence checks passed. Both volume shortcuts and direct accessibility setup were verified on a headset. Power remains experimental. A partial Android restart during development was followed by a watchdog timeout; use normal headset reboots for module activation. See the power companion README for the observed limits.