RAOfflineProxy

Settings & Auto-start ​

Auto-start and shutdown behavior differ by target.

Auto-start ​

On KNULLI, autostart is available from the menu.

If you enable it, the proxy starts automatically through the KNULLI startup hook:

text
/userdata/system/custom.sh

Persistent config and cache data live under the KNULLI/Linux config path, so the menu, manual launches, and autostarted proxy services after reboot all see the same state.

== Allium

Allium autostart is available from the app menu.

Allium has no drop-in startup folder either, so RAOfflineProxy adds a small guarded block to Allium's own boot script:

text
/.tmp_update/updater

That block calls the app's headless launcher in the background, so Allium's own startup is never held up:

text
/Apps/RAOfflineProxy.pak/autostart-launch.sh

It is also skipped entirely while an Allium firmware update is pending, so the proxy never starts up in the middle of an update.

Reinstalled automatically

An Allium update rewrites /.tmp_update and removes the block. The app reinstalls it every time you open RAOfflineProxy, so autostart repairs itself after an Allium update.

:::

Start / Stop Behavior ​

Starting the proxy:

  • Patches RetroArch
  • Starts the background local proxy service
  • Keeps the required RA settings active while the service is running

Stopping the proxy:

  • Stops the service
  • Reverts the RetroArch config patch

On Onion, the app also installs a shutdown cleanup hook under:

text
/.tmp_update/checkoff/raofflineproxy.sh

That hook calls the app's cleanup helper so the proxy can stop and revert during orderly Onion shutdown.

This is best-effort cleanup. It helps with normal shutdown, but it is not a guarantee against crashes or hard power loss.