Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Announcement

    Sorry for the recent downtime. Still much to do but we have the site updated, secure and back online.  Expect more changes.

Modified Hyperspin APK for RetroArch - Works with all modern versions


Recommended Posts

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:

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

     

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

     

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

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

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

     

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

  • Like 1
  • Super Like 5
Link to comment
Share on other sites

6 hours ago, HyperSeeder said:

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.

@reznnate is the guy who did the original build to have HS on his Nvidia Shield Portable. Not sure if he published it to Google Play BUT he's the guy we are all really thankful to.

Congrats on your project, sadly I don't really have the time to test it out. Those who use adopted storage might need to install RetroArch and then immediately move it to internal storage before running, worth testing that out to prevent people saying your build doesn't work. 

Link to comment
Share on other sites

7 hours ago, Honosuseri said:

@reznnate is the guy who did the original build to have HS on his Nvidia Shield Portable. Not sure if he published it to Google Play BUT he's the guy we are all really thankful to.

I've emailed him as well as the email address registered for HyperSpin in Google's Play Store. Hopefully someone still has the source and access to publish new official versions of HyperSpin. It would be great if someone could update the official version.

7 hours ago, Honosuseri said:

@reznnateThose who use adopted storage might need to install RetroArch and then immediately move it to internal storage before running, worth testing that out to prevent people saying your build doesn't work. 

Interesting stuff. RA in adoptable storage may actually be a use case that would justify implementing support to load a custom retroarch.cfg with HyperSpin.

On my Shield, RetroArch APK installs directly to internal shared storage. It doesn't even give me an option to install it to my adopted SSD.

More than that, once installed it also doesn't give me an option to move RetroArch outside of internal shared storage.

Is installing RA in adopted storage even possible nowadays? https://github.com/libretro/RetroArch/issues/8353

If there's a guide somewhere to get RA to install outside of internal shared storage I can try to make HyperSpin work with it.

Link to comment
Share on other sites

22 minutes ago, HyperSeeder said:

Is installing RA in adopted storage even possible nowadays? https://github.com/libretro/RetroArch/issues/8353

If there's a guide somewhere to get RA to install outside of internal shared storage I can try to make HyperSpin work with it.

By the way. Looks like RA will soon have to comply with even more restrictive storage permissions from Google (https://github.com/libretro/RetroArch/issues/12181). I'm not sure if installing RA in adopted storage is a good idea at this stage.

Link to comment
Share on other sites

1 hour ago, HyperSeeder said:

Is installing RA in adopted storage even possible nowadays? https://github.com/libretro/RetroArch/issues/8353


I have very little interest in emulation on Android now, so it's been a very long time since I touched the STV, RA & HS. I can tell you that it used to install by default to shared storage and the RA paths were different to when on internal storage. So I had to go into apps select RA and move it before running it, once run RA set the paths automatically.

If you use adopted storage and everything works with your HS build then that's awesome, nothing to worry about. I only mentioned it as people use different setups, some just have HS and "roms" on an external drive with others using adopted storage...maybe both.

Link to comment
Share on other sites

Hi guys,

Just giving everyone a heads up.

While my version of the app is still working great, unfortunately whoever is in charge of the Play Store version ignored my emails about merging changes upstream.

More than that, in a few months (November 1st deadline) Google will start enforcing Android 11 / API Level 30 as the minimum target for Play Store apps updates. Updating Hyperspin to comply with Android 11 requires non trivial changes, particularly around Scoped Storage. https://developer.android.com/about/versions/11/behavior-changes-11

I don't know if there is someone in charge for the app right now (as far I can tell, there isn't). But what I can say is that, if the person in question isn't willing to merge a 3 LoC patch, I doubt that he will be willing to do what it takes to keep HS alive. So, you have heard here first, the official Play Store version is likely dead in the water. New versions are unlikely to be released (unless things change and the official development team takes over the Android version).

Also, contrary to some posts in the forum that previously led me to believe that there is active development going on and community members hacking the app to keep it alive behind closed doors, to the best of my knowledge, both official and community development efforts around the Android version of HS are basically non-existent.

As far as I can tell, the modded APK in this thread is the only version that works with all modern versions of RetroArch. I couldn't find a working alternative anywhere else.

I'll try my best to keep this version alive for as long as possible. Nevertheless, I feel the need to echo the message from older community members: If you are starting from scratch, don't use HS. There are great Emulator Front Ends for Android (E.g., Dig and Arc Browser).

  • Super Like 1
Link to comment
Share on other sites

6 hours ago, HyperSeeder said:

Hi guys,

Just giving everyone a heads up.

While my version of the app is still working great, unfortunately whoever is in charge of the Play Store version ignored my emails about merging changes upstream.

More than that, in a few months (November 1st deadline) Google will start enforcing Android 11 / API Level 30 as the minimum target for Play Store apps updates. Updating Hyperspin to comply with Android 11 requires non trivial changes, particularly around Scoped Storage. https://developer.android.com/about/versions/11/behavior-changes-11

I don't know if there is someone in charge for the app right now (as far I can tell, there isn't). But what I can say is that, if the person in question isn't willing to merge a 3 LoC patch, I doubt that he will be willing to do what it takes to keep HS alive. So, you have heard here first, the official Play Store version is likely dead in the water. New versions are unlikely to be released (unless things change and the official development team takes over the Android version).

Also, contrary to some posts in the forum that previously led me to believe that there are active development going on and community members hacking the app to keep it alive behind closed doors, to the best of my knowledge, both official and community development efforts around the Android version of HS are basically non-existent.

As far as I can tell, the modded APK in this thread is the only version that works with all modern versions of RetroArch. I couldn't find a working alternative anywhere else.

I'll try my best to keep this version alive for as long as possible. Nevertheless, I feel the need to echo the message from older community members: If you are starting from scratch, don't use HS. There are great Emulator Front Ends for Android (E.g., Dig and Arc Browser).

Thanks for all your hard work keeping this working.

I am assuming it will still work fine with RA 32bit and other versions that are NOT on Google Play ?

Link to comment
Share on other sites

On 8/31/2021 at 9:23 AM, Creezz67 said:

Thanks for all your hard work keeping this working.

I am assuming it will still work fine with RA 32bit and other versions that are NOT on Google Play ?

Yes, the modded APK works with the website (https://www.retroarch.com/?page=platforms) 32 and 64 bits versions , F-Droid and Google Play Store versions, as well as modded / recompiled versions of RetroArch (as long as its package starts with com.retroarch). 

Sideloading the modded APK will work until Google permanently remove READ_EXTERNAL_STORAGE permissions and force everyone to use Storage Access Framework (SAF).

They are already enforcing Scoped Storage and SAF for new Android Applications in the Google Play Store. Google will also be enforcing it for new versions of already published apps from November 1st.

Despite the Play Store situation, I won't expect Android devices to stop supporting READ_EXTERNAL_STORAGE permission soon, so sideloading should be fine for a while. Nevertheless, my advice would still be for people to move on to a different Emulation Front End so that they aren't caught by surprise when it happens.

Link to comment
Share on other sites

On 8/31/2021 at 2:57 AM, HyperSeeder said:

As far as I can tell, the modded APK in this thread is the only version that works with all modern versions of RetroArch. I couldn't find a working alternative anywhere else.

I'll try my best to keep this version alive for as long as possible. Nevertheless, I feel the need to echo the message from older community members: If you are starting from scratch, don't use HS. There are great Emulator Front Ends for Android (E.g., Dig and Arc Browser).

To my knowledge it's @reznnate who we have to thank for the Android version of HS. I believe he created it originally for the Shield Portable device. I seem to recall the official HS app was updated, when it stopped working because of previous Android changes many moons ago. Of course I can't speak for future development.

I applaud your efforts on modding and maintaining your version of the APK. I modded it solely for RA32 as IMHO adding the 64bit version of RA for it's limited benefits were not worth my time. I was aware of these Android changes coming, the dev for LaunchBox has stated they've stopped development of their Android version iirc. I hope FreeLancer will continue on with Arc Browser.

All the best, I'm sure many people are thankful for your efforts

Link to comment
Share on other sites

15 hours ago, HyperSeeder said:

Yes, the modded APK works with the website (https://www.retroarch.com/?page=platforms) 32 and 64 bits versions , F-Droid and Google Play Store versions, as well as modded / recompiled versions of RetroArch (as long as its package starts with com.retroarch). 

Sideloading the modded APK will work until Google permanently remove READ_EXTERNAL_STORAGE permissions and force everyone to use Storage Access Framework (SAF).

They are already enforcing Scoped Storage and SAF for new Android Applications in the Google Play Store. Google will also be enforcing it for new versions of already published apps from November 1st.

Despite the Play Store situation, I won't expect Android devices to stop supporting READ_EXTERNAL_STORAGE permission soon, so sideloading should be fine for a while. Nevertheless, my advice would still be for people to move on to a different Emulation Front End so that they aren't caught by surprise when it happens.

Not really the place to be giving people advice about NOT using Hyperspin mate, but thanks again for your work on the modded apk.

It works great and worst case scenario is to just get to a setup you are happy with and not update RA after a certain point.

Link to comment
Share on other sites

1 hour ago, Creezz67 said:

Not really the place to be giving people advice about NOT using Hyperspin mate, but thanks again for your work on the modded apk.

It works great and worst case scenario is to just get to a setup you are happy with and not update RA after a certain point.

Worst case scenario is that when the STV is updated to Android 11 or 12 that Hyperspin won't work, it's not about RetroArch but the changes Google is making to the OS. Perfectly valid post for him to make, I'd be livid if as a new user I sunk in a lot of time setting up HS for it just to stop working out of the blue.

I help people with HS plenty BUT still recommend Arc Browser as it is a better frontend being actively developed. I've used HS on the STV for what 5 years, there's a suggested features thread here on the forum BUT nothing new has been added. I hope that HS will be updated when the Android OS changes kick in BUT I can't say for sure that it will be.

Link to comment
Share on other sites

3 hours ago, Honosuseri said:

Worst case scenario is that when the STV is updated to Android 11 or 12 that Hyperspin won't work, it's not about RetroArch but the changes Google is making to the OS. Perfectly valid post for him to make, I'd be livid if as a new user I sunk in a lot of time setting up HS for it just to stop working out of the blue.

I help people with HS plenty BUT still recommend Arc Browser as it is a better frontend being actively developed. I've used HS on the STV for what 5 years, there's a suggested features thread here on the forum BUT nothing new has been added. I hope that HS will be updated when the Android OS changes kick in BUT I can't say for sure that it will be.

All I am saying is don't put Hyperspin down.

It is struggling as it is and some people won't be happy until it's gone forever !

Link to comment
Share on other sites

On 9/2/2021 at 11:53 AM, Creezz67 said:

All I am saying is don't put Hyperspin down.

It is struggling as it is and some people won't be happy until it's gone forever !

No, you clearly misunderstood the situation by saying just don't update RA. Hyperspin on PC and Android are two very different animals. When M$ does a Windows update which messes up Hyperspin, I'm confident it'll be fixed as that's happened many times. On Android I'm not as confident but hope for the best, the fact Launchbox has abandoned their Android version should tell you enough to be concerned.

It's sound advice to warn new users about the changes to Android and the knock on effect it will have on HS with the STV. Arc Browser is a superior frontend with better features, being actively developed AND it's also compatible with phones/tablets when HS is not. When the Android OS changes kick in on the STV and HS is known to be working, I'll recommend HS "for show" and help people set it up.

Until that day comes, I agree with Hyperseeder and new users should wait before sinking in a lot of time learning and setting up Android Hyperspin. I have a very nice Hyperspin PC setup, people are perfectly "safe" sinking time into that, many of the assets can then be shared with an Android setup later.

Link to comment
Share on other sites

7 hours ago, Honosuseri said:

No, you clearly misunderstood the situation by saying just don't update RA. Hyperspin on PC and Android are two very different animals. When M$ does a Windows update which messes up Hyperspin, I'm confident it'll be fixed as that's happened many times. On Android I'm not as confident but hope for the best, the fact Launchbox has abandoned their Android version should tell you enough to be concerned.

It's sound advice to warn new users about the changes to Android and the knock on effect it will have on HS with the STV. Arc Browser is a superior frontend with better features, being actively developed AND it's also compatible with phones/tablets when HS is not. When the Android OS changes kick in on the STV and HS is known to be working, I'll recommend HS "for show" and help people set it up.

Until that day comes, I agree with Hyperseeder and new users should wait before sinking in a lot of time learning and setting up Android Hyperspin. I have a very nice Hyperspin PC setup, people are perfectly "safe" sinking time into that, many of the assets can then be shared with an Android setup later.

I understand what you are saying, and appreciate what you and Hyperseeder have done to help keep it afloat on Android.

I have an awesome setup on Hyperspin and even with zero development it's still the best setup you can get on both android and PC (IMO)

I also have a full 800 wheel setup with 200,000 games on Launchbox,  and even though it looks great it's as slow as hell compared to my super slick Hyperspin setup.

Note: Launchbox has started up their Android paid version and it's now in full speed development.

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Similar Content

    • By therourke
      I have a fully working build for Commodore Amiga now on my NVIDEA Shield (2017 model). It took me a good while to get it up and running.

      I thought it might be useful to post an 'all in one place' tutorial. Thanks go to Honosuseri over in this post for convincing me it was possible.
      Commodore Amiga is infamously painful to configure on any and all emulation setups. Retroarch takes the pain out of some of this, since we don't need individual .uae files for every single game now. But there are still some hoops to jump through.
      Onto the tutorial
       
      1. Find/setup your own Hyperspin
      Hyperspin is free and available on this very website. Install the app on your NVIDEA Shield, and compile your roms and Hyperspin setup on an appropriately sized external harddrive/USB.
      As for the ROMs, videos, wheel images and all the aesthetic stuff you need to get your setup running, you will have to source that yourselves. The Hyperspin website is good for some material, emumovies for videos, and Google and Archive dot org for everything in between. 
      For this setup I used a properly named romset for Commodore Amiga in .zip format, but you can also use .lha or .hdf format. .lha is smaller in size, but all of these run pretty much the same on Retroarch now. 
      There is no need for those pesky .uae files anymore!!!!!!!!!!
      Once you have all your roms, you will need to allocate them to the right videos and images and build your .xml database. The info for how to do this is available elsewhere on this very website. I used HyperspinChecker to do this.
      Now, onto the part where we make Hyperspin and Retroarch play nicely so you can finally play your Commodore Amiga games 
      2. WHDLoad and kickrom setup (bios file preparation)
      I obviously can't link to kickroms or WHDload.hdf and some other stuff, but Google is your friend.
      You can get kickroms legally as part of the Amiga Forever app on Google Play Store for only £1.79.
      You ABSOLUTELY NEED to get hold of these EXACT kickroms:
      kick34005.A500 kick37175.A500 kick40063.A600 kick40068.A1200 Some info on kickrom file names and how to match them up correctly can be found here.
      MAKE SURE THE FILENAMES ARE PRECISE! I left one of those As in lowercase and Retroarch didn't like it.
      You also need a properly prepared WHDLoad.hdf file: ADD THESE EXACT KICKROMS TO YOUR WHDload.hdf file (guide to do this here using ADF Opus)
      Copy all these file to the external drive you are keeping your Hyperspin setup on (I made a 'bios' folder in mine for safe keeping).
      3. Retroarch Setup
      Install the latest Retroarch on your NVIDEA Shield (probably works on other Android setups too). You can do this through the Google Play store, but as of writing this, version 1.8.9_GIT definitely works.
      You will need to make sure you have setup a way to load the Retroarch main menu from within games. Go to 'Settings', 'Input', 'Hotkeys' and set the 'Menu Toggle Gamepad Combo' to something like 'Select + Start'.
      Download the latest Commodore - Amiga (P-UAE) core from within Retroarch (use 'Online Updater' menu)
      Now 'Load Core' and choose the P-UAE Core. Start the core, then immediately go back to the Retroarch menu (Start + Select). From the 'Quickmenu' select 'Options'. Change the 'Model' here to something with plenty of power like the 'A1200 (2MB + 8MB)'. Scroll down to 'WHDLoad Support' and make sure this says 'HDFs'.
      (NOTE: ONLY if that last setting doesn't work, try this: Scroll down to 'Global Boot HD' and 'WHDLoad Support' and make sure both of these are marked as 'Files'.)
      One other thing from within Retroarch: having a way to 'Quit' from within games is useful for Hyperspin. So go to 'Settings', 'Hotkeys' choose a button for 'Quit Retroarch' (I use the click of my Left Analogue, but anything will do). You may also need to mess around with button mappings, but most of this should work fine if you have a NVIDEA Shield compatible gamepad. Mouse and keyboard are also, obviously, nice additions for Amiga stuff.
      Go back to 'Quick Menu', 'Overrides' and select 'Save Core Overrides' to make sure your Retroarch Amiga setup is saved.
      Lastly, and very importantly...
      Leave Retroarch. You will need an Android directory viewing program like 'FX File Explorer' for this step. Copy the EXACT kickroms listed above and the WHDload.hdf file you created into the /Retroarch/System/ folder on the INTERNAL drive of the NVIDEA Shield.
      4. Commodore Amiga.ini Commands
      In your Hyperspin setup you should now have all your roms, videos, images, menu setup, and a Commodore Amiga.xml database file all neat and tidy.
      You now need to get Hyperspin to talk to Retroarch properly.
      Back on your PC, load your Hyperspin folder and go to the /Settings_Android/ folder.
      Create or open the Commodore Amiga.ini in a text editor. Most of the stuff in here will be the same as other systems, but you can find my ini file attached here.
      Make sure the top lines in your ini read like this:
      [exe info] path=H:\hyperspin\emulators\Commodore Amiga\ rompath=Roms/Commodore Amiga/roms userompath=true exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture romextension=zip,hdf,lha,HDF,ZIP,LHA parameters=cores/puae_libretro_android.so searchsubfolders=false pcgame=false winstate=HIDDEN hyperlaunch=true Each of these lines corresponds to your setup. So if you have your roms folder somewhere else, you need to tell the file. If you are ONLY using .zip versions of your roms, then you don't need the entire 'romextension=zip,hdf,lha,HDF,ZIP,LHA'  line - you can change this to just 'romextension=zip' and it will work fine. (But my line here covers all the possible rom extensions, so you can leave it). The 'exe' and 'parameters' entries are really important, as this tells Hyperspin to load Retroarch, and then Retroarch which core to load for Commodore Amiga.
      Save your file, and hook your Hyperspin external drive back to your NVIDEA Shield.
      5. Play some games
      Everything *should* be working now. If you are having problems with videos and roms matching up, or entries showing in the Amiga menu on your Hyperspin, then that is an issue with your original setup. There are many tutorials out there.
      I can vouch that THIS EXACT setup works great, and loads and plays most Amiga games I have thrown at it without too many glitches.
      6. Now, please answer me a Q 
      When using an external mouse in Retroarch and playing a game like Lemmings, I get TWO cursors - the in game Lemmings cursor, and the NVIDEA Shield arrow.
      Does anyone know how to get rid of this for good? Thanks
      Commodore Amiga.ini
    • By edboy542
      I have attached a short video showing that the Arcade games not launching and other games launching perfectly with no problem. So when I try to launch the Arcade Game it appears to open up Retroarch, but does not load the core. Do I have to edit the Hyperspin Info Settings to make sure it is opening up the Core to launch the game? I am trying to provide all information that I can in order to get this build fully up and running. Once again thanks in advance for any assistance with this. 
    • By HyperSeeder
      HyperSpin v0.1.8 for Android
      This is an unofficial version of HyperSpin for Android able to launch all modern versions of RetroArch.
      Support topic: https://hyperspin-fe.com/forums/topic/42774-modified-hyperspin-apk-for-retroarch-works-with-all-modern-versions/
      File Information:
      HyperSpin_v0.1.8_HyperSeeder.apk
      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.
       
       
    • By NEO207
      Hello hyperspinners...
      I updated my retroarch to 1.9 by downloading the retroarch folder and overwriting my existing Retroarch folder.
      I have done that a couple of times without any problems so far but this time, i can access the games via retroarch directly but the games won't open, when i want to start them through hyperspin.
       
      Besides that, I have the exact same problem with the dolphin emulator. games start via dolphin perfectly but don`t start through hyperspin. when i exit hyperspin via task manager, i can see that the dolphin emulator window gets opened by "starting the game via hyperspin".
    • By Honosuseri
      Right guys as some of you are aware Google changed how things work on the Google Play Store a while back, when we install an app it will use the 32 or 64 bit version depending on what's native to the device. As we're mainly focused on the Shield TV here on the Android part of the forum, it is a 64 bit device. This has proved to be a bit of an issue for those of us who love Retroarch as there are some serious differences between the 32bit and 64bit versions. In a nutshell currently we have access to more cores for us to play our retro systems on the 32 bit version. RetroArch provide a RetroArch_ra32.apk which is a dedicated 32bit version we can sideload/install and use, however Hyperspin is NOT setup to use this version as some of the paths changed.

      So...I decompiled the Hyperspin.apk and made the necessary changes (yes including the config path) to solely use RA_32. I've done some limited testing with RA_32 (1.8.7) and it seems a okay to me (even the Daphne test core works) however I don't use screen overlays or really bother with alternate config setups (in truth I've not used the STV in many months!). Feel free to download it and test yourselves, obviously backup your essential files AND do remember the .ini files need to be adjusted to use RA32....

      exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
      becomes
      exe=com.retroarch.ra32/com.retroarch.browser.retroactivity.RetroActivityFuture

      It's easy enough to open all your .ini files with notepad++. Use the Search and replace feature to find com.retroarch/ and replace to com.retroarch.ra32/ do this for all opened files then save all.

      Those who use adopted storage it's wise to move the Retroarch_ra32 app to internal storage after installing AND before running it for the first time. Let me know how it works for you, I'll do a Youtube video to help those less experienced with setting up Hyperspin when I know it's working 100% and I have the free time.

      Mega Link for Hyperspin_0.1.8_Hono.apk (https://mega.nz/file/zQNBCYKI#QVrG4uVVmvXHshl8LbosQi7LAjQmUA09R5k_YqhcMBI)
      RetroArch_ra32 (1.9.0) newest stable version at time of posting (https://buildbot.libretro.com/stable/1.9.0/android/)
×
×
  • Create New...