Automatic GBA emulator save game synchronization
2,045 views
Skip to first unread message
Aironfaar
Oct 22, 2013, 5:21:54 PM10/22/13
to tas...@googlegroups.com
Hello everyone,
I recently picked up playing emulated GBA games on my computer and figured I might try to automate save game synchronization between my home computer and Android. On computer, I use VBA Link which saves battery files as ".sa1" to ".sa4" files; the only ones that matter to me there are the ".sa1" ones. My emulator of choice on Android is My Boy!, which uses the standard ".sav" files.
So far, I managed to synchronize the files between my computer and android using FolderSync and my Dropbox. The plan was to synchronize the .sa1 files and replacing the current .sav file on my Android with it by copying and renaming upon starting the emulator and to do the same vice versa - i.e. replacing the .sa1 file with the .sav file on the Android before synchronizing with the Dropbox again - upon closing it, everything with an appropriate amount of backup copies in a separate folder.
It worked well. However, I have one problem though: After selecting the rom in My Boy!, the emulator closes the main process and starts another process for the emulation. The result is that the Application Context doesn't see the emulation process and instead starts the "My Boy! was closed" routine. After closing the emulation, the app goes back to the main process for rom selection...which, again, triggers the synchronization from computer to Android. That said, my plan failed because of the way My Boy! behaves.
Can any of you think of a fix for that? I'm out of ideas.
Cheers,
Aironfaar
I recently picked up playing emulated GBA games on my computer and figured I might try to automate save game synchronization between my home computer and Android. On computer, I use VBA Link which saves battery files as ".sa1" to ".sa4" files; the only ones that matter to me there are the ".sa1" ones. My emulator of choice on Android is My Boy!, which uses the standard ".sav" files.
So far, I managed to synchronize the files between my computer and android using FolderSync and my Dropbox. The plan was to synchronize the .sa1 files and replacing the current .sav file on my Android with it by copying and renaming upon starting the emulator and to do the same vice versa - i.e. replacing the .sa1 file with the .sav file on the Android before synchronizing with the Dropbox again - upon closing it, everything with an appropriate amount of backup copies in a separate folder.
It worked well. However, I have one problem though: After selecting the rom in My Boy!, the emulator closes the main process and starts another process for the emulation. The result is that the Application Context doesn't see the emulation process and instead starts the "My Boy! was closed" routine. After closing the emulation, the app goes back to the main process for rom selection...which, again, triggers the synchronization from computer to Android. That said, my plan failed because of the way My Boy! behaves.
Can any of you think of a fix for that? I'm out of ideas.
Cheers,
Aironfaar
Wes Stacey
Oct 22, 2013, 6:20:56 PM10/22/13
to tas...@googlegroups.com
so let me see if i understand.
When My Boy! starts it triggers the enter task on the App Context as expected.
Then once you select the actual ROM it start another process which to Tasker looks like the My Boy! app has closed triggering the Exit Task on the profile.
Is this correct?
Stephen Smith
Sep 12, 2019, 9:58:18 AM9/12/19
to Tasker
I managed to synchronize the files between my computer and android
using FolderSync and my Dropbox. The plan was to synchronize the .sa1 files
and replacing the current.
Stephen Smith
Sep 30, 2019, 4:14:12 AM9/30/19
to Tasker
Try out this site, it'll definitely help you download it easily.
Reply all
Reply to author
Forward
0 new messages