Save sync between Grout and EmulatorJS not working

[Dxcv1]

Seems like there is a bug syncing save files between ROMM and Grout if you make progress in EmulatorJS

Steps to reproduce the behavior:

1. Start a new game and create a save file on the platform using Grout.
2. Sync the save to ROMM
3. Load the save in EmulatorJS through ROMM and make a little progress. Manually export the save file.
4. EmulatorJS will update the existing save and not create a new one.
5. Try to sync back to Grout. It will upload the old file instead of pulling the new one.

This should be pulling the new savs file down, but it seems like it might get hung up on the time stamp in the file name.

• CFW: muOS
• CFW Version: 2508.4 Loose Goose
• Handheld Device: RP34XXSP
• Grout Version: 4.6.1.3
• RomM Version: 4.6.1

[pawndev]

Okay just tried it on the exact same setup (except it was on my RG35XXSP)
I don't remember which variable grout use to check the last modified time (c.f. documentation about sync), but a difference can exist between the SBC device and the romm instance

But my logs are like this :

{
  "time": "2026-02-04T07:52:00.453789091+10:00",
  "level": "DEBUG",
  "msg": "Comparing save timestamps",
  "baseName": "Pokemon - Version Saphir",
  "localPath": "/mnt/sdcard/MUOS/save/file/mGBA/Pokemon - Version Saphir.srm",
  "localMtimeRaw": "2026-02-04T07:49:21+10:00",
  "localTime": "2026-02-04T07:49:21+10:00",
  "localUnix": 1770155361,
  "remoteFileName": "Pokemon - Version Saphir [2026-02-03 21-49-21-000Z]",
  "remoteTimeSource": "filename",
  "remoteTime": "2026-02-03T21:49:21Z",
  "remoteUnix": 1770155361,
  "diffSeconds": 0,
  "comparison": 0,
  "action": "SKIP",
  "reason": "equal"
}

[pawndev]

Just walk into https://github.com/pawndev/grout/blob/a196bebd4e6969c6c6321a873ec7549f90f4fffa/sync/roms.go#L98-L100
It's seems like this is not really bug, it's just that grout check based on the remoteFileName, but the save was not uploaded/edited from grout, so the timestamp is not updated in the save file title

[BrandonKowalski]

Yeah that timestamp check is a temporary stop gap until the save syncing stuff officially comes.

Definitely something I'll want to fix but I don't feel like spending time on something that is about to change upstream.

[Dxcv1]

Thanks for the responses everyone. Looks like the ROMM team just committed the first set of changes to lay the groundwork for native sync support. Really exciting times!

[BrandonKowalski]

Totally! I think we are gonna stay in a holding pattern until that stuff gets finalized. But then we'll be off to the races to hook into it!