RAOfflineProxy — earn RetroAchievements offline on muOS

Applications Release
1

RAOfflineProxy now runs on muOS.

Normally RetroAchievements needs an internet connection to track and unlock achievements. RAOfflineProxy makes it possible to keep earning them completely offline. It runs quietly in the background, remembers your games’ achievement data, and queues up any unlocks earned while offline. As soon as the device is back online, everything syncs to RetroAchievements automatically, so handheld gaming on the go no longer means missing out on achievements.

On muOS it works just like it does on KNULLI, with nothing complicated to set up.

This is an early alpha release and hasn’t been through formal testing yet, so some rough edges are to be expected. Feedback and bug reports are welcome.

:globe_with_meridians: Website & setup guide: https://raofflineproxy.com
:package: Latest release: Releases · misantronic/RAOfflineProxy · GitHub

7 Likes
2

You don’t even know how many times I didn’t get the achievement, because wi-fi disconnected. This is a big QOL app and I love the idea. This is amazing, I’ll try it out tonight.

1 Like
3

@misantronic Does this work for hardcore achievements?

4

No, that’s not the case, and it most likely never will be. This isn’t a technical decision, but a deliberate decision by retroachievements.org

5

Adding games via “Smart Cache” worked for me. I wanted to manually add some games using the “Add ROM” option but it is searching for ROMS in “/mnt/mmc/ROMs”, which is on the SD1(mmc) sdcard. Is possible to add an option for SD2(sdcard)? This would be helpful for 2-sdcard users.

Device: RG34XXSP (2gb black)

OS: MUOS 2601.1 Funky Jacaranda

1 Like
6

it should probably not use either of those locations and instead use the union path so that it doesn’t matter where the roms are…

7

fyi that path has been deprecated in Andromeda.

8

Andromeda doesn’t exist. It can’t hurt you. :grin::grin:

3 Likes
9

When i try to launch the app on TUI brick, it just freezes saying loading app.

10

Make sure to use the latest version. The one I linked previously in the thread had problems with the TrimUI Brick

11

What do you mean by “union”-path?

12

In the next version, there will be a switcher between /mnt/mmc/ROMS and /mnt/sdcard/ROMS (when available) (fdcf6b6)

1 Like
13

Thanks! Now it works great

1 Like
14

Added support in the latest release.

2 Likes
15

What’s the correct way to update this? Do we just copy the latest .muxapp file from GitHub to the archive folder on the SD card and run it, or should we uninstall the previous version first?

Also, this is an absolute killer feature and should probably be included by default in the next official muOS release.

As for bugs, I’ve noticed that the proxy sometimes fails to autostart on an RG35XX H running muOS 2601.1 Jacaranda with RAOfflineProxy-muOS-v1.13.0-alpha1. But maybe that’s because I hit the 100 cached games limit already?

16

You just install it over the existing installation.

Currently, the dev of spruceOS is working on integrating RAOfflineProxy into their own platform. For that, I provided a CLI so the frontend-part can be completely outsourced to wherever needed. This is possible today, but it needs someone to do it. Unfortunately I discovered I will not be the person as I am way too busy with working on the core app.

Thanks for the report, I will put it on my list and check what might be wrong here. The limit seems unlikely, but we’ll see.
Feel free to join the discord for more direct conversations about the app :folded_hands:

17

I don’t think the 100-game cache limit is related. The proxy opens its port before the cache queue even starts.

I tested autostart on an RG40XX-H (muOS NeXT) with 30 reboots: plain, resume-last-game, and resume-last-game with wifi off. The proxy started every time. So I can’t reproduce it yet and need a few details from your RG35XX-H.

Could you send:

  1. RAOfflineProxy/data/launch.log and data/service.log (from the app folder on the SD card)
  2. The contents of /opt/muos/config/settings/advanced/user_init (it should be 1)
  3. Whether /run/muos/storage/init/raofflineproxy.sh exists
  4. Whether the failure happens on a plain boot or only when muOS resumes the last game, and whether you updated the app in-app before it started

If you open the RAOfflineProxy app once, it re-creates the autostart hook, which might already fix it. A coming version will also log boot problems to data/boot.log, so the next failure is easier to trace.