Jump to content
LaunchBox Community Forums

Goodmango

Members
 View Profile  See their activity

  • Posts

    47

  • Joined

  • Last visited

 Content Type 

Posts posted by Goodmango

    bootPath for AetherSX2 (and other maybe)

    in Android

    Posted

    1 minute ago, Jason Carr said:

    Unfortunately I've already proven that they do not all require exactly the same solution. They may in the future, but the other emulators don't yet work as they should.

    What do you want to know. The the address that each emulator needs to launch the games.  Like this (org.mupen64plusae.v3.fzurita/paulscode.android.mupen64plusae.SplashActivity).

    bootPath for AetherSX2 (and other maybe)

    in Android

    Posted

    4 minutes ago, Jason Carr said:

    @Goodmango @bundangdon @GabiAle97 LaunchBox for Android 1.0-beta- 2 is out now, and AetherSX2 now works properly in my testing. Details are here:

    That said, unfortunately none of the other related emulators that I tested are working properly with the new solution (Dolphin, PPSSPP, Mupen, etc.). It appears that AetherSX2 has implemented the content URIs properly, but the other emulators haven't yet. We can dive in with more details in the beta testing thread. I'm hoping to reach out to emulator developers to get those figured out here soon.

    All you need is to contact mupen64 developer. The same solution for his emulator will work with PPSSPP, dolphin and all other emulators. By the way implementing aethersx2 to your front end is all you need for other emulators including mupen64 to work the way is the same and I am pretty sure aethersx2 implementing is the hardest of them all . 

    LaunchBox for Android New Version - Beta Testing

    in Android

    Posted

    4 minutes ago, Jason Carr said:

    Version 1.0-beta-2 is out now with the following:

    • Support for the dreaded new Android file permissions model has been added; devices that are running Android 11 or higher will now be prompted to allow access to all files on startup, which is necessary in order to properly launch some emulators

    • Full support for the new AetherSX2 PS2 emulator has been added

    Unfortunately I had to switch gears away from the videos for a bit in order to solve the annoying permissions issues that are popping up everywhere. This is the first step in solving the issues launching games with various emulators on Android 11+. AetherSX2 properly implements the new content URIs, and so we are now able to launch games with it, even when restricted on Android 11+.

    However, unfortunately there are numerous other emulators that have chosen to upgrade/compile against the new Android version, but have not yet added full support for the content URIs, and thus we're currently up a creek until the emulator developers finish developing those features. Those emulators include PPSSPP and Dolphin, as far as we can tell. Both emulators work fine with earlier versions and earlier Android versions, but have issues launching games on Android 11+. It's possible that there is yet another solution to otherwise solve this issue that we haven't found yet, because Google's documentation is terrible, so speak up if you know of a solution. Otherwise, we will work to contact the various emulator developers as we can.

    Also, this release may solve some issues with file and folder permissions, if you were previously running Android 11+ and couldn't access a particular folder (such as when trying to move the LaunchBox folder).

    The good news in all of this is that we no longer have to worry about Google's new permissions changes, because we've finally worked through them and confirmed that we can still properly operate as a frontend (even though there will likely be many more pain points along the way, such as not being able to launch emulators that have only half-way updated to the new permissions stuff). That said, and this is very important to note: if we were still on the Play Store, we would not have been able to continue operating as a frontend at all. This is because we require the new MANAGE_APP_ALL_FILES_ACCESS_PERMISSION in order to parse all files on the device (find ROMs, etc.), which Google refuses to allow apps like ours to use while on the Play Store. It's a permission that is granted only to file browser apps and similar, and we don't fit into any of the "allowed" categories. All of this is just to explain the confusing history in this thread, and our having to stop developing for Android for a while. It's all thanks to Google's poor decisions; that said, we are very grateful to at least be able to continue developing for Android, and finally get most of these issues figured out.

    So thankfully, we no longer have to worry about the future feasibility of LaunchBox on Android. That is, until Google turns around and makes another exceedingly poor decision... ;)

    Finally the biggest android update for launch box. I was waiting for this day since I joined this forum . Great work and make launch box the greatest front end on Android . 😃👍

    • Like 1

    Ppsspp error loading file: IdentifyFile: File doesn't exist

    in Android

    Posted · Edited by Goodmango

    3 hours ago, PhenomenJan said:

    I'm not sure it's all on LaunchBox.

    I managed to get it working with Pegasus FrontEnd, because it lets you send the file location as a ContentUri.

    However, that required a change to ppsspp, because they were expecting differently formatted ContentUris.

    We'll see if my pull request gets accepted.

    In case the developer sees this, here is the commit where Pegasus FrontEnd added ContentUri support.

    I'd try adding it myself, but I think LaunchBox maybe isn't open source?

    Pegasus added it recently. Because they were searching for a way to solve the scoped storage problem. Here is the page

    https://github.com/mmatyas/pegasus-frontend/issues/915#issuecomment-993139861

     

    By the way PPSSPP can be opened through front end apps. No need for them to change anything.

    LaunchBox for Android New Version - Beta Testing

    in Android

    Posted

    2 hours ago, Jason Carr said:

    Yes, of course it can be done. It's on our list. I'm on vacation currently though, so it will be a bit before I'm back tackling new things for the Android version.

    Great to hear 😊. That's means you will add the support for all emulators that's using scoped storage like PPSSPP and mupen64.

×
×
  • Create New...