Jason Carr

@spacemonkey Thanks, that should be enough. It looks like you're getting the same error as @Eyebrows Cat. I'll see what I can figure out.

Sure, sorry it's difficult. Can you screenshot it?

Have you posted that java error message? Can you post it?

Are you manually trying to install it, or using the built-in updater?

If it is a deadzone issue, it is possible that LaunchBox is not as forgiving as other apps with the deadzone, but that's all I can figure as to why it would only be affecting LaunchBox. There are many other reasons why it could be though. Every controller implementation is different. Do you have the option to reset the device to factory software (remove all configs and such)?

Thanks all. Beta 5 is out now with a hopeful fix for the above startup issues. There were several different issues posted, so I'm not 100% confident that everything will be fixed with this beta, but I'm hoping so. Please let me know how this beta fares. If you're unable to update because you can't get into the LaunchBox interface, you can manually download beta 5 here: https://www.dropbox.com/s/dzmzpzjmzcr1b4r/LaunchBox-Android-1.1-beta-5.apk?dl=0

Thanks good to know. For anyone running into these errors, if you could please share your most recent debug log file from under LaunchBox\Logs after experiencing the issue.

Thanks, that might be helpful. Is that similar to the issue you're getting @bundangdon? I also need to know what devices are having this issue.

There are debug log files in the Logs subfolder of the LaunchBox folder, so that might be helpful, but probably not because we haven't logged the controller input. It's probably still worth a shot though. You might have to turn on Debug Logs in the Options. I watched your video again, and it looks like some controller on the system is just permanently stuck in the "up" position. That could be an issue with a bad dead zone on the stick, or maybe some kind of other controller that's connected. I am wondering if maybe it could be a faulty device, because @ETAPRIME also has one and is not experiencing the issue.

Yes, version 1.1-beta-4 came out, as I'm trying to streamline the update process. Both beta 3 and beta 4 are related to that. What device are you using? We haven't seen that in any of our testing at this point.

Hi Greg, make sure you've updated to the latest official release, as that will fix all known issues with storage access on Android 11 and 12. However, I'm not sure what version of Android that the RG552 is running. Unfortunately there are some devices out there that just will not work to do what LaunchBox needs to be able to do in order to function properly as a frontend. In our experience, the devices that have these issues are lower-end devices that run older versions of Android, and unfortunately there are a lot of those types of devices that just don't implement Android properly. I don't have access to either an RG552 or an Odin Pro, but for what it's worth, I do have confirmation that this is not an issue on the Odin Pro.

@kevinlingley Are you still having this issue? I was able to confirm from someone else who has the device that they are not running into the issue, so it may be some kind of odd configuration issue (or maybe the device just needs rebooted). Or perhaps there's a malfunctioning Bluetooth device connected.

LaunchBox for Android 1.1-beta-2 is out now with the following: Deleting a platform will now optionally delete all media (including videos) instead of just images Improved the initial startup process so that the app does not have to be manually restarted after accepting the new storage permissions on Android 11 and 12 Fixed an issue where disabling media background downloads would prevent some existing media from showing

Usually this just means it was a corrupted download. Can you try again?

Yup, you can just check the box to update to betas in the Options of the Android app. Then just restart the app and you should be prompted to update.

Yes, that has not yet been tackled yet. If I don't note any related fixes here or in the change log, then chances are that specific issue has not been fixed.

@Soop Definitely don't blame you there. Windows is really still just miles ahead of Android on pretty much everything. And yeah, those Amazon tablets. While it's amazing that they're so cheap, they are pretty crappy.

Please let me know if the latest beta (version 1.1-beta-1) happens to fix this issue.

Can you post me your log file?

This will be hard to figure out without having the device on hand, unfortunately. I would definitely like to get this fixed though. Apparently they're doing some pretty non-standard stuff with controls on that device, because this is the first device we've seen in a long time with any issues. Is it possible to buy the device currently?

It's possible that the beta release I just put out (above) could fix whatever issue you're running into with network storage on the Pixel 6. But honestly, I have no idea what you might be running into there. The Pixel 6 *should* have already worked just fine with network and USB drives.

Hey all, LaunchBox for Android version 1.1-beta-1 is out now with a workaround for accessing network shares on the Nvidia Shield. The first post of this topic has been updated with all of the updated details (again). Thanks for bearing with us as we work through all of the Nvidia Shield issues. As far as we know, the only remaining issue with the Shield (assuming you've gone through the rigamarole to update to the latest Nvidia firmware) is that there's still no access to the USB drives in any app. This appears to be a still-remaining bug with the latest versions of the firmware.

LaunchBox for Android version 1.1-beta-1 is out now with a workaround for accessing network storage on the Shield devices that have been updated to the latest firmware. You will still need the latest Nvidia hotfixes, however. For more details on the Nvidia firmware situation, please see this thread:

Hmm, not sure why that would be. We'd have to dive in deeper to your actual setup. What do you mean by "ROMs stored locally but with network access mapped in Windows Explorer"?

Thanks guys for the heads-up on the RetroArch changes. I had been looking for a workaround for the Nvidia bugs, and the recent RetroArch commits clued me in. Version 1.1-beta-1 is out now, and you can now access network drives on Nvidia Shield devices with the latest firmware upgrades (but I believe you do still need the latest Nvidia hotfixes). For more details on the Nvidia firmware situation, please see this thread: https://forums.launchbox-app.com/topic/65300-issues-with-the-latest-firmware-on-nvidia-shield-tv-devices-how-to-fix/