Sorry for the recent downtime. Still much to do but we have the site updated, secure and back online. Expect more changes.
Search the Community
Showing results for tags '32-bit'.
To anyone following my posts lately, I have been working in modifying HyperSpin so that it can run all modern versions of RetroArch. I know that some of you have been waiting for it since 2019. Well, the wait is finally over. Download: HyperSpin_v0.1.8_HyperSeeder.apk: https://mega.nz/file/uNx0gQQA#f5ktYDOV6nMAWxatrlg6XAYz14ZMdYlkWg994s-1WDg MD5: 4692846e4fe9a90bd0da3a6cd9f10ed3 SHA512: 2f5db6b625983c189b9f82c574bf48781921780825a38ceaf9c1094bd113545f9abdd06c5b4ac8707093e3e2ac0fc1185b9bc939f30f5ee830a41689c68e5b21 How to configure your Settings_Android ini files: Main APK from RetroArch's website and Google Play Store Version: exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture RetroArch's website 32bit version: exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture RetroArch's website 64bit version and RetroArch Plus: exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture Have fun! FAQ: Can I mix and match multiple RetroArch distributions? Yes, you just need to set different exe values for different systems. For instance, you can use the 64bit version of RA + Dolphin core for GameCube games (Nintendo GameCube.ini): exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture parameters=cores/dolphin_libretro_android.so And the 32bit version of RA + MAME Core (MAME.ini): exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture parameters=cores/mame2010_libretro_android.so Will it load separate configuration files for 32bit and 64bit versions? Yes, it will always load the default configuration file for each version. Default configuration files are in /storage/emulated/0/Android/data/[package name]/files/retroarch.cfg For example: /storage/emulated/0/Android/data/com.retroarch.ra32/files/retroarch.cfg Can I make Hyperspin launch my own custom compiled version of RetroArch? Yes. As long as the package name starts with com.retroarch everything should work. Can I configure HyperSpin to load retroarch.cfg from a custom location? Not for now. I find that I can accomplish what I want with the default config file + settings overrides. If you have a specific use case that would benefit from this feature comment bellow and I'll see what I can do. How was this implemented? I reversed engineered the original Google Store APK using Apktool and JEB. You can find the two lines of code that I've modified bellow. You can use APK Studio to verify my changes. Has it been tested? I tested it with my NVIDIA Shield 2017 and 2019. It worked with all mentioned distributions, RA versions 1.9.0 to 1.9.8 How can I help? If you know someone able to get my two lines change integrated in the official build and published to the Google Play Store, please point the person to this topic. Acknowledgment: Many thanks to@zerojay, @yarrick and @Honosuseri for "hacking" their own versions of HyperSpin. While this version is my own work, I couldn't do it without the information that you all made available to the community.
A few days ago, I decompiled and edited the Hyperspin APK to allow users to use 32-bit and 64-bit installations of Retroarch together. It's been confirmed working by the community and you can find that edited APK here: https://zerojay.com/nextcloud/index.php/s/3QfPqYM4A6ymjr4 It works as you would have originally expected using a 32-bit or 64-bit version of Retroarch to work, so in your Settings_Android system ini file, change the exe to com.retroarch to use the 32-bit version or change it to com.retroarch.aarch64 to use the 64-bit version. 32-bit Retroarch: exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture 64-bit Retroarch: exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture Currently, both 32-bit and 64-bit versions of Retroarch will be called using the 32-bit configuration files, however I will likely be updating the APK to allow you to use the 64-bit configs as well for those who may wish to use different settings for both. When that happens, I'll keep both versions of the APK available so that you can decide what you want to use. So now that the community has solved the Retroarch 32-bit problem, it would be really helpful to compile a list of cores and the version of Retroarch that it works best under. In some cases, certain cores currently only function under one or the other, but not both. In some rare cases, cores stopped working like Daphne, so again, these are things that we would like to call out. (By the way, for anything like Daphne where more recent cores no longer work, I can host them for the community if needed. Just let me know (and I do myself still need to get that working Daphne core myself). I'll update the top post here to reflect the community's findings so that people only need to come to one place to find the info they need. --- Core Information ---- atari800 - non-functional on 32-bit due to Android security changes, use 64-bit Retroarch core. mame - Latest version of MAME core only recently started compiling on 32-bit, not available yet on 64-bit. EDIT: Updated link for latest updated build.