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

4 minutes ago, C0ntrA said:

Give me more credit than that...

Bruh...

😎

Got a mini pc on it's way to be added to my home theater and Retro gaming setup for more of that horsepower.

But was thinking of leaving hyperspin on my Shield as I typically only play up to around ps1/DC/saturn games.

Namco racing games would be sick though...

Hmmm.

 

If you are getting a mini PC it would be better to use that for the later stuff.

I have about 200 odd wheels setup on Shield, but hardly ever use it because my PC setup has loads more stuff on it like Switch, XBOX,XBOX 360, PS2 etc

Link to comment
Share on other sites

6 hours ago, Creezz67 said:

If you are getting a mini PC it would be better to use that for the later stuff.

I have about 200 odd wheels setup on Shield, but hardly ever use it because my PC setup has loads more stuff on it like Switch, XBOX,XBOX 360, PS2 etc

Yeah that was a thought, for now though, it's going to be for Steam/indie games and of course PC access.

Rather keep Hyperspin on one platform.

For me, Hyperspin = my retro games. I don't have any interest in playing xbox games and such, that's not nostalgic for me as I am 42 years old.

Figured the mini pc should satisfy my "current game" itch (mostly indie because they are retro inspired), and maybe some SFV online etc.

If everything goes right, Nvidia shield will release a couple more generations of it's hardware and I would be already set up while appreciating that those harder to run games would improve :)

Link to comment
Share on other sites

Edited Update:

 

I have been able to get most of my systems working, but Namco systems like Namco System 22 don't want to cooperate with mame or mamearcade or mame2010.

I assume I haven't tried the "correct" core yet?

 

 

 

Link to comment
Share on other sites

Alright, so it was an error on my part.

At this point though Creezz67, I do see what you mean about the Nvidia Shield limitations. I figured that arcade games would be mostly smooth experiences, but the later Namco titles seem to struggle. Using Mame4Droid helps a bit, but apparently it will take another couple hardware upgrades/future releases of the Nvidia Shield to handle my entire arcade library. Glad I was able to get it resolved, and thank you for your assistance in this barren wasteland of a forum...:)

Link to comment
Share on other sites

On 10/25/2021 at 3:40 AM, C0ntrA said:

Edited Update:

 

I have been able to get most of my systems working, but Namco systems like Namco System 22 don't want to cooperate with mame or mamearcade or mame2010.

I assume I haven't tried the "correct" core yet?

 

 

 

I would give up on Namco System 22 personally, it won't work correctly on the shield.

Link to comment
Share on other sites

55 minutes ago, Creezz67 said:

I would give up on Namco System 22 personally, it won't work correctly on the shield.

I see that.

Still got my library set up as best I can anyway.

Link to comment
Share on other sites

16 hours ago, C0ntrA said:

Alright, so it was an error on my part.

At this point though Creezz67, I do see what you mean about the Nvidia Shield limitations. I figured that arcade games would be mostly smooth experiences, but the later Namco titles seem to struggle. Using Mame4Droid helps a bit, but apparently it will take another couple hardware upgrades/future releases of the Nvidia Shield to handle my entire arcade library. Glad I was able to get it resolved, and thank you for your assistance in this barren wasteland of a forum...:)

Yes, people seem to think because 1 game works on an emulator, they will all work.

Unfortunately that is not the case (across every system)

Even the best emulators on Windows like PCSX2 and PPSSPP still don't have anywhere near 100% compatibility.

We can just be thankful that 10's thousand's of games if not 100's thousand's all work perfectly and every day another one is tweaked to work .... and on and on the emulation scene goes  (hopefully) !!

Link to comment
Share on other sites

3 hours ago, Creezz67 said:

Yes, people seem to think because 1 game works on an emulator, they will all work.

Unfortunately that is not the case (across every system)

Even the best emulators on Windows like PCSX2 and PPSSPP still don't have anywhere near 100% compatibility.

We can just be thankful that 10's thousand's of games if not 100's thousand's all work perfectly and every day another one is tweaked to work .... and on and on the emulation scene goes  (hopefully) !!

Yeah, I hit the reality wall recently in that regard. Some games just simply won't work even with the correct systemname.ini configurations. It is what it is.

There is another front end that does allow you to select from a list of emulators at the wheel in case that one rom isn't working on the expected core (allowing a higher chance of functionality), I think that is a real nice touch! But for folks like me, with a HUGE list of roms, it's sorta a guessing game of which emulator will run the selected game EVERY TIME since there is no category based on cores like Hyperspin...

But Hyperspin is so dang flashy and attractive that it's a "pick your poison" situation.

Link to comment
Share on other sites

1 hour ago, C0ntrA said:

Yeah, I hit the reality wall recently in that regard. Some games just simply won't work even with the correct systemname.ini configurations. It is what it is.

There is another front end that does allow you to select from a list of emulators at the wheel in case that one rom isn't working on the expected core (allowing a higher chance of functionality), I think that is a real nice touch! But for folks like me, with a HUGE list of roms, it's sorta a guessing game of which emulator will run the selected game EVERY TIME since there is no category based on cores like Hyperspin...

But Hyperspin is so dang flashy and attractive that it's a "pick your poison" situation.

On windows it's fine because you can just use alternate emulators in RocketLauncher, but for android there is no RL.

The only way around it would be to have 2 wheels for same system and then you can have a different core on each for example.

Not ideal, but any games you really want could then be added.

  • Like 1
Link to comment
Share on other sites

2 hours ago, Creezz67 said:

On windows it's fine because you can just use alternate emulators in RocketLauncher, but for android there is no RL.

The only way around it would be to have 2 wheels for same system and then you can have a different core on each for example.

Not ideal, but any games you really want could then be added.

Yeah, I have more than a few sets of arcade categories under my wheel. One specifically for Mame4Droid as well. Never the less, each arcade category has at least a couple examples of "non compatibility" with the specific emulator no matter what. Luckily for the most part, switching between the Mame wheel and Mame4Droid wheel, I can play most of my arcade/mame games without issue.

 

Link to comment
Share on other sites

Thanks for this thread, and effort to keep Hyperspin living. I recently came across the Bandit's No Clutter release, and have been trying to get it working on my Shield Pro with 8.2.3. The problem I am running into isn't isolated to HS, but really any and all Frontends I've tried.

 

What's happening is, I load whatever Frontend I have and designate games to load in Retroarch (Hyperspin, Launchbox, etc). I choose the game tell it to play, and it loads Retroarch but not the game. It's simply the main screen that shows no core loaded. I have ensured all the cores are downloaded and up to date, but it simply will not launch a game. I've even tried various versions of Retroarch for giggles, but it didn't help. If I go to load content, I can get them to load through RA, but that really defeats the purpose of a frontend.

 

I tried the tip in this thread for editing the exe= location, but yielded the same results. I feel like there is something blocking the full launch command or I'm doing something stupidly wrong.

 

Anyone else run into this and come up with a fix? Driving me nuts over here.

 

Also worth noting, I'm not married to using Hyperspin, I only started with it thanks to the 200gb Bandit release.

Link to comment
Share on other sites

I used that package last month, and it was my first experience with HS.

Anyway, it almost sounds to me as if you aren't using the 32 bit version of Retroarch.

If you are using Retroarch Plus, you will have issues with that collection. 

Also, that collection was intended to work with the playstore version of hyperspin, so effectively limited to the playstore version of retroarch (32).

 

Have you downloaded the modded apk from this thread?

Link to comment
Share on other sites

  • 2 weeks later...
On 10/24/2021 at 4:11 AM, C0ntrA said:

Update.

 

Thankfully your method still works. Just took a bit more knowledge of how to do the editing of ini files.

Still going strong in 2021!

I'm glad everything is still working. I wasn't notified of the messages for some reason l. Yes, this version is still working and configurations are done within the HyperSpin folder as you have already figured out.

MAME works well, but I found out that I rather stick with older roomsets + cores. 

Hopefully the next version of NVIDIA Shield will be backwards compatible with its existing architecture / software. I've heard that NVIDIA is going to shut down Tegra even though Nintendo Switch helped move a lot of NVIDIA hardware. It's too bad as Tegra was / is still the best SoC on Android TV hardware.

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