Feature Request: Add support for Argosy-Launcher (Android)

@tmgast

Users running the Android frontend (Argosy-Launcher) cannot utilize RAOfflineProxy when playing games via Argosy's internal libretro core interface.

https://github.com/rommapp/argosy-launcher

Because Argosy manages its emulator configurations independently, it is impossible to route RetroAchievements data through the local offline proxy bridge. Forcing games to launch via standalone RetroArch works, but it breaks Argosy’s seamless, console-like frontend experience.

Possible Solutions:
Provide a way to redirect Argosy's internal libretro authentication requests to http://127.0.0.1:port/ by modifying the underlying cheevos_custom_host string in its configuration space.
This could be achieved via:

Documentation: A guide on how to manually edit the retroarch.cfg file inside Argosy's directory (if user-accessible).
Upstream Integration: Coordinating with the rommapp/argosy-launcher project to expose a custom RetroAchievements server field directly within the Argosy UI.

cc: @tmgast

I think this is only possible when collaborating with Argosy. They will always send their own customized config when launching a game. My idea would be the following:

On RAOfflineProxy side: expose a ContentProvider f.e. at content://com.raofflineproxy/config.

Argosy queries it at launch (or before starting a game). It returns something like:

proxy_running: true | false
proxy_host: "127.0.0.1"
proxy_port: 8080
proxy_value: "127.0.0.1:8080"

If the proxy isn't running, we return proxy_running = false and Argosy skips patching. If RAOfflineProxy isn't installed at all, the query throws, Argosy catches it and proceeds normally. Zero tight coupling.

--

Not 100% sure if this works as I don‘t know Argosy's exact architecture, but I would say it's worth a shot.
It would of course be grand if someone else did this as I am still pretty busy with the main app.

I just pushed the part that exposes the proxy-status to third-parts apps (88d3b66). Will be in the next release and RAOfflineProxy is then ready to support this.

It works like mentioned above, quick adb-check:

running:

~> adb shell content query --uri content://com.raofflineproxy.config
Row: 0 proxy_running=1, proxy_host=127.0.0.1, proxy_port=8080, proxy_value=127.0.0.1:8080

stopped:

~> adb shell content query --uri content://com.raofflineproxy.config
Row: 0 proxy_running=0, proxy_host=127.0.0.1, proxy_port=8080, proxy_value=127.0.0.1:8080

I'll take a look at this on my side. Argosy already does it's own thing for offline, but I can add whatever necessary to handle this use-case as well.

I'll take a look at this on my side. Argosy already does it's own thing for offline, but I can add whatever necessary to handle this use-case as well.

I just released a new version that now implements the ContentProvider

@misantronic

Thanks @misantronic. So, perhaps a dumb question, but how would one start the proxy in the first place when using only the ContentProvider path? Since I don't have one of the supported emulators installed, the Start Proxy button is disabled.

how would one start the proxy in the first place when using only the ContentProvider path? Since I don't have one of the supported emulators installed, the Start Proxy button is disabled.

Why would you need the proxy, if you don‘t have an emulator installed? 🤔

In this case, yes, in the sense that Argosy launches RetroArch cores directly, so it is a frontend that has a lot of auto-configuration done so that "it just works" (saves, states, achievements, directory management, etc.) for many users. That means that I don't actually have the RetroArch .apk installed, just the Argosy .apk and the ra cores that it downloads and uses.

A bit of a different animal I suppose, but where RAOfflineProxy app provides a nice advantage is that I can see the state of the cache, pending awards, and use it across other emulators should the need arise.

I'm adding an override option so you can force the built-in emulator to send to the proxy. Should be pretty easy.

@tmgast

Hey @tmgast, do you have an update about this?

Hi,

Sorry I didn't follow up. Argosy added support for setting a proxy URL shortly after this thread was opened. It works well, and I can use it to point Argosy's built-in emulator cores at the proxy url/port.

Note that I did still need to install the RetroArch app so the proxy will let me start it. Since the app doesn't recognize Argosy as an emulator, it requires a supported emulator app to be present for the proxy to start.

Anyway, with RA installed and Argosy pointed at the proxy everything works nicely.

It came in handy recently when RetroAchievements had that outage (I think it was a denial of service).

That sounds great! Not sure if it's implement, but it should be possible to pull the proxy-address via a ContentProvider (#40 (comment)), so the configuration could happen automatically :)

Closing as it's implemented now.

@misantronic

@misantronic sorry for reviving a closed issue, I installed Argosy and RAOfflineProxy on Android today (latest stable version) but I cannot start the proxy because it does not see an emulator (as others have described in this issue).
Is this still intended/is the workaround to have some emulator installed so the proxy can be started needed or am I missing something?

15. @misantronic sorry for reviving a closed issue, I installed Argosy and RAOfflineProxy on Android today (latest stable version) but I cannot start the proxy because it does not see an emulator (as others have described in this issue).
Is this still intended/is the workaround to have some emulator installed so the proxy can be started needed or am I missing something?

What device are you using + which version of android? best would be to "send logs" under settings and give me the log-id. I can then inspect your device specifics.

Thank you for the quick reply!

I am using an AYN Thor running Android 13.
Uploaded logs, ID witty-glacier-54.

@stephanrenggli

Thanks for the logs, @stephanrenggli. Nothing is wrong with your device. The log shows the proxy was never started, only some app stops from reinstalling.

What you're seeing is intended for now. The app only enables "Start proxy" when it finds a supported emulator (RetroArch, Dolphin, PPSSPP, etc.), and it doesn't recognize Argosy as one. Argosy runs its own libretro cores, so you don't need RetroArch to play, but the app doesn't know that yet.

Workaround until I change this: install RetroArch (you don't have to use it), start the proxy in RAOfflineProxy, then enter the proxy address (127.0.0.1:8080, or whatever port the app shows) in Argosy's proxy URL setting. Achievements from Argosy's built-in cores will then go through the proxy.

I'm looking into letting the proxy start when Argosy is installed, so the extra install isn't needed.

@stephanrenggli

@stephanrenggli I made a test build that lets you start the proxy with only Argosy installed, no RetroArch needed. The change is in #232.

APK: RAOfflineProxy-argosy-test.zip

To try it:

Install the APK over your current RAOfflineProxy. It has the same signature, so your settings and cache should stay.
Open the app. “Start proxy” should be enabled now, and the “No supported emulator” warning should be gone.
Start the proxy. Since there’s no emulator config to read the login from, the app will probably ask for your RetroAchievements username and password. Enter them there.
In Argosy, set the proxy URL to the address shown in the app (127.0.0.1:8080 unless you changed the port) and launch a game.

Awesome, works perfectly for me. Thank you!

Navigation Menu

Repository navigation

Feature Request: Add support for Argosy-Launcher (Android) #40

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Feature Request: Add support for Argosy-Launcher (Android) #40

Description

Activity

misantronic commented on Jun 13, 2026

misantronic commented on Jun 13, 2026

tmgast commented on Jun 13, 2026

misantronic commented on Jun 13, 2026

jtbrough commented on Jun 14, 2026

misantronic commented on Jun 14, 2026

jtbrough commented on Jun 14, 2026

tmgast commented on Jun 14, 2026

misantronic commented on Jul 10, 2026

jtbrough commented on Jul 10, 2026

misantronic commented on Jul 10, 2026

misantronic commented on Jul 10, 2026

stephanrenggli commented on Oct 8, 2026

misantronic commented on Oct 9, 2026

stephanrenggli commented on Oct 9, 2026

misantronic commented on Oct 9, 2026

misantronic commented on Oct 9, 2026

stephanrenggli commented on Oct 9, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions