Jason Carr

Unfortunately, from what I can tell, the save states issue in Dolphin MMJR is a bug with Dolphin MMJR. I tried launching it all the ways that we know how to launch and nothing seems to solve the issue. In addition, other frontends seem to have the same problem. So unfortunately this is most likely a bug that will need to be fixed by the developer of Dolphin MMJR. If anyone knows any further details or has any ideas for a fix, please let me know.

Unfortunately, from what I can tell, the save states issue in Dolphin MMJR is a bug with Dolphin MMJR. I tried launching it all the ways that we know how to launch and nothing seems to solve the issue. In addition, other frontends seem to have the same problem. So unfortunately this is most likely a bug that will need to be fixed by the developer of Dolphin MMJR. If anyone knows any further details or has any ideas for a fix, please let me know.

Gotcha, that makes sense. Yeah, as much as I would love to support that, it would be a tremendous amount of work. What app are you using on your phone?

Looking into this @Opak. From what I can tell, it looks like the issue is fixed if I resize the window to be bigger. Is that correct? Can you confirm that? If so, we'll just make the window bigger by default.

@jay_busacca @someguy How are you guys accessing the network share from your devices? Are you using some kind of special app? Are you using Samsung's My Files app? From what I can tell, network access on Android (other than for devices like that Nvidia Shield) is not system-wide access and is only provided by custom functionality within individual apps. This means that LaunchBox would have no access to shares you have in Samsung's My Files app, for example. This doesn't really surprise me because network shares are not a common/expected usage scenario for mobile phones and tablets. Therefore, in order to implement it, we would have to build our own code for implementing Windows network shares, which is a bit out of scope for the project. So unless I'm missing something, unfortunately it's not likely to happen any time soon. Network shares are only supported on devices that have built-in system-wide support for network shares, like the Nvidia Shield.

Thanks, and sorry for the delay here. I have this in for the next beta.

FYI, I have this fixed for the next beta. Thanks again for the report and sorry for the trouble.

I spoke with @C-Beats and he confirmed that that process is working correctly on his Odin Pro, so I still don't really know what's going on. Are you able to reproduce this issue? Any chance you can send me a copy of your data from before and after the failed change? All I can figure at this point was that the data was somehow not as expected before LaunchBox attempted to change the paths.

Okay, I've asked @C-Beats to test on his Odin Pro to see if he can replicate. I've tried it on all my devices and I can't seem to reproduce the issue.

Thanks, I did go ahead and remove this high score.

Sort of, but none of that has been fleshed out yet. If you put the media files in the right folders and name them exactly as LaunchBox expects, then it will pick up those media files on import. That means that if you want to pick up a bunch of existing media files, you can delete the platform (without deleting media) and re-import it and it should pick those files up, but only if they're named exactly as LaunchBox expects. We will add a process to make this smoother in the future, but it's probably a ways off.

If you import games on Android, and then delete the platform and re-import, it should keep any media files you previously downloaded without re-downloading any of them. However, there is a known issue where that will not always work if you exported from the desktop app instead of importing on Android. Sometimes it will re-download some of the media in that case.

Lol, that's sure proof that something is wonky on their end. But I'm super glad there's a workaround.

For the moment, we have not yet added options for this. We'll definitely be adding more controller options for things like this in the future, but it might be a while.

Unfortunately right now there are only two different ways to add videos: Download them from EmuMovies in LaunchBox for Android Export your collection from the desktop app (LaunchBox for Windows) So if you need to manually import videos, for the moment it can only be done on the desktop and then exported to Android. We will be adding more options for that in the future.

@neil9000 is correct. I'm curious though, where did you get that Neo Geo set? Can you screenshot me the list of files?

It looks to be supported in the latest version of LaunchBox for Android as well. @jamie1981uk Please let us know whether you're running LaunchBox for Windows or LaunchBox for Android and if this solves the issue for you.

I spoke with @C-Beats, and apparently his Odin Pro is on Android 10, not Android 11. So apparently the Lite is definitely running different stuff than the Odin/Pro. It sounds like Odin has some work to do on the firmware on the Lite.

It would be good to know if it's a configuration or data issue, so at least temporarily starting over is a good idea. What I would do is leave your current LaunchBox folder in tact so that you can back to it if you want/need to. Just run the LaunchBox installer and select a different folder. That way you can safely run two different copies of LaunchBox in two different folders. It doesn't sound like you're doing anything wrong in that regard. Sometimes issues like these can be caused by faulty/dying drives or a corrupted file system, though. So it would probably be worth running chkdsk to see if you have any errors on your drive.

I reviewed the code, and we are not looking for write permissions when browsing for a folder in imports, so unfortunately that's not the issue. We've set up the permissions in LaunchBox to act as a file manager app, which is supposed to give LaunchBox full access to files on both internal and external storage, but unfortunately some manufacturers are failing us in that regard. It still doesn't make any sense why the Odin Pro would work but the Odin Lite doesn't. Unfortunately, in order to resolve this I'll probably need an Odin Lite. I do wonder if there are any options for custom firmware on the Odin Lite that might not have this problem. Other than that, for the time being I'm not sure what to do.

@Aj67 @borf42 Thanks for the detailed video. It's strange because we've confirmed that everything works fine with the Odin Pro. @C-Beats actually owns an Odin Pro and didn't run into any of those issues. So all I can figure is that there's some inherent difference between the Odin Lite and the Odin Pro, which seems pretty dumb. But I don't know what else it would be. Watching through the video, it doesn't look like you're doing anything wrong. It does appear to be a broken version of Android, as far as I can tell. My best guess as to what's going on from the video, is that the SD card is read only when it shouldn't be. I will look to see if there's anything I can do to force those folders to show up even though they can't be written to, if you're just browsing for ROMs to import, though I thought I had already done that. But I will confirm. Per those deeply nested com.unbrokensoftware.launchbox folders, those are just automatically created by Android and are separate from all the other permissions. LaunchBox doesn't use them for much at all, because yes, nothing in them can be accessed by any other app.

Yes, this should be fixed in 12.13 and work properly.

The first 12.14 beta is out now here:

Can you explain specific situations/platforms where you're having issues? I'm having trouble following.

Hey all, the first 12.14 beta is out now with the following: New Premium Feature: Big Box now has a new default theme with a brand new look and a ton of new goodies for our theme developers; the old Default theme is now called "Old Default" and is still available for use Improvement: All Big Box popups and options pages have been overhauled Improvement: In Big Box, the alpha-numeric index used in platforms and games views now opens to the letter you are currently on, instead of where you last left it Improvement: The drop downs in Big Box's filters popup are now ordered alphabetically Improvement: Wall views in Big Box can now utilize game details (for theme developers) Improvement: 14 new popups are now fully themeable in Big Box and can be placed anywhere on the screen (for theme developers) Improvement: Added 25 new converters usable in Big Box (for theme developers; courtesy of y2guru) Improvement: You can now use the string "LAUNCHBOX_THEME_FOLDER" in your xaml to point to the root folder of your Big Box theme (for theme developers) Improvement: Navigating the Recent Games and Favorites thumbnails will now work in more themeable situations (for theme developers) Improvement: Recent Games and Favorites thumbnails can now be used in all platforms views (for theme developers) Improvement: These available bindings are now usable in Big Box (for theme developers): DateEarned (DateTime), DateEarnedString (string), and EarnedHardcore (bool) added to AchievementView SelectedItemIndex added to FlowControl Count and SelectedItemIndex added to Platform and Game views You can now access FilterDetailsViewModel via any platform view to access bindings found in the details view 51 bindings added to FilterDetailsView 36 bindings added to GameDetailsView PreviousPage binding added to all Platform, Game, Game Details, Options, and System menus Fixed: Not passing an image type to FlowImage will now select the image type in user settings (for theme developers) Fixed: Various minor potential issues with the Export to Android process