LaunchBox for Android New Version - Beta Testing

[Jason Carr]

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...

[Goodmango]

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 . 😃👍

[Luca82]

i recieved this error when i tried to install the apk: error during package analysis  does anyone know how to solve it?

Allow installation from unknown resources is activated, the error occurs after the download from the launchbox app and if I try to install with a explorer app...

Android 12, Samsung tab s7

Edited January 6, 2022 by Luca82

[bundangdon]

@Jason Carr Thanks a lot for this update. However, I just tested AetherSX2 and it only launches the main program but not the games. When I launch a game within LaunchBox, it takes me into the bios of the PS2, without launching the game itself. Is there anything I'm missing on this, or is anyone else having the same issue?

[UnnUndrgrnd4114]

I'm getting an error where launching games with AetherSX2 through Launchbox brings me to the "Browser/System Configuration" Menu. Launching games directly through AetherSX2 gives me no issues whatsoever though.

Edited January 7, 2022 by UnnUndrgrnd4114

[angerman]

On 1/4/2022 at 10:56 PM, Jason Carr said:

 

To be honest, I'm not sure. Probably worth a shot.

unfortunetly can't instal on that device ....... I tried 2 versions.... 

[richie1973]

On 1/6/2022 at 11:34 PM, Luca82 said:

i recieved this error when i tried to install the apk: error during package analysis  does anyone know how to solve it?

Allow installation from unknown resources is activated, the error occurs after the download from the launchbox app and if I try to install with a explorer app...

Android 12, Samsung tab s7

Same here on 2 different devices

[cash84]

Beta 2 crashes when I launch launchbox. I have the SHIELD Android TV Pro. V0.42 works great and so did Beta 1.

[argi73]

I am trying to setup a sample environment before purchase a license and I heave the following problems so far

I update to new beta but the problem with the SAF on some emulators still exists (e.g M64Plus FZ )

I am from Greece and in the setting is impossible to change to English . (change it and never saved I change also the config file by hand) The menu is a mix of Greek and English.

The above I think it's create problem to the theme as I am missing the image for "all games"

thanks in advanced

Hope soon to have support for themes!

Edited January 11, 2022 by argi73

[krys2fur]

Yep, it crashed my Shield Pro also. Wish I would've came here and read that before turning on beta update switch.

 

[hobapli]

I checked the android version today.
 In one word it looks great but I couldn't view the video snaps.
 Do I need to make any settings for this? 
good job congratulations.

[cash84]

2 hours ago, krys2fur said:

Yep, it crashed my Shield Pro also. Wish I would've came here and read that before turning on beta update switch.

 

You can uninstall it and reinstall the stable version. As long you don't say yes to deleting your media, everything should load right back up.

[neil9000]

13 hours ago, hobapli said:

I checked the android version today.
 In one word it looks great but I couldn't view the video snaps.
 Do I need to make any settings for this? 
good job congratulations.

Do you have a paid subscription to emumovies and did you enter those login details into Launchbox?

[krys2fur]

Thank you for that. I was wondering about that last night and instead of chancing deleting everything and starting over, I was going to wait for another update and hopefully fix the problem. I just added just about all the platforms that was available. But, now I will go ahead and uninstall and re-install the stable version. I was wondering about other platforms that aren't available, ex. SuperGrafx , is there a way to manually add them?

 

Edited January 12, 2022 by krys2fur

[hobapli]

32 minutes ago, neil9000 said:

Do you have a paid subscription to emumovies and did you enter those login details into Launchbox?

i had emumovies account and i downloaded what i need then unsubscribed. Whatever i have imported video files from Launchbox PC and there are videos under /video folder. Do i still need emumovies account ?

My second problem is really bad... can anyone choose data folder from SD card? im getting write and read error... launchbox is getting blocked when trying to change xml files i guess. Can I keep the rom files on the sd card and edit the xml files myself?

[thewhite]

Hi hobapli,

Check my post, it's maybe your problem for video;

You can edit the xml file, copy it on your desktop, do change, save, and put it back on your phone.

[hobapli]

there is no such a line <AndroidVideoPath>

 

 

 like

[hobapli]

oh ok ill try to change AndroidGameplayScreenshotPath" to "AndroidVideoPath" and let you know ...

[hobapli]

5 hours ago, thewhite said:

Hi hobapli,

Check my post, it's maybe your problem for video;

You can edit the xml file, copy it on your desktop, do change, save, and put it back on your phone.

After opening Launchbox, the changes I made to the xml file are lost and rearranged. Frankly, all the "mp4" or video related entries disappear when I open and close the application after doing this. I really don't understand where I went wrong. I downloaded it a couple of days ago from the link in my email. Could it be out of date?

[Cineaste]

I just upgraded my Shield TV to Android 11, which broke Snes9x, Mupen64 and PPSSPP. It now throws a permission error.

What gives?

Edit: According to Jason's post above it is up to emulator developers to work around this, yes?

I don't know why my setup is affected because the files are all saved in internal storage (USB formatted to expandable storage). Isn't this scoped storage problem exclusive to external storage devices?

Edited January 13, 2022 by Thornback