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.

(Tutorial) Hyperspin Android Overview and Install


thatman84
 Share

Recommended Posts

  • 3 months later...

Does anyone else find it impossible to make any changes once you have HS loaded up and running on ShieldTV?

as I experiment with media files and find mistakes like wrong file names I always feel like I have to start with a fresh install to see my changes take effect.

i want to make a simple setup with only NES, SNES, N64, and GENESIS. Can I just delete all files that are associated with all the other systems inclusive of media, ini, xml, cores etc?  I tried to do this and the app crashes after intro video. 

 

Thanks for the help looking forward to being involved in this community/project.

Link to comment
Share on other sites

1 hour ago, scott222 said:

Does anyone else find it impossible to make any changes once you have HS loaded up and running on ShieldTV?

as I experiment with media files and find mistakes like wrong file names I always feel like I have to start with a fresh install to see my changes take effect.

i want to make a simple setup with only NES, SNES, N64, and GENESIS. Can I just delete all files that are associated with all the other systems inclusive of media, ini, xml, cores etc?  I tried to do this and the app crashes after intro video. 

 

Thanks for the help looking forward to being involved in this community/project.

No. Only thing to do is if you remove items that use XML then you must redo XML.

Link to comment
Share on other sites

1 hour ago, scott222 said:

Does anyone else find it impossible to make any changes once you have HS loaded up and running on ShieldTV?

as I experiment with media files and find mistakes like wrong file names I always feel like I have to start with a fresh install to see my changes take effect.

i want to make a simple setup with only NES, SNES, N64, and GENESIS. Can I just delete all files that are associated with all the other systems inclusive of media, ini, xml, cores etc?  I tried to do this and the app crashes after intro video. 

 

Thanks for the help looking forward to being involved in this community/project.

I have only had minimal crashes with HS and usually after I have been messing with other things and or renaming my Hyperspin folder or using different ones. Also I have seen more instability from many apps after the latest shield update.

But your issue with removing systems should not be one.

dont delete any single folders from systems or the man in menu stuff (Videos for example)

you can always just remove the entries from the main menu.xml database if space is not a concern.

dont really want to be deleting any folders in Media/Main Menu or Media/Front End just in needed video or image files and theme zips maybe.

the key database folder in Main Menu and there are a couple of settings files you don't want to delete either settings.ini

main menu.ini cat think of others right now.

 

Link to comment
Share on other sites

When I was still getting used to the identical rename rule with Roma and xml files I had a few Roma that I needed to change the name for since they where not launching.  I would change the name with ESFE but it wouldn't fix the problem.  I would end up back on my PC rewriting the name and reinstalling lol. 

Im going to try you recommendation for slimming down the build. Space really isn't an issue I just don't want the other stuff there (on the wheels) if I'm not using it. 

Link to comment
Share on other sites

  • thatman84 pinned this topic
  • 1 month later...

I loaded Hyperspin and was blown away by the beauty!!!  I created a couple test folders (NES, SNES, Sega Genesis) with 2 or 3 moms in each folder.  When I select the system from the wheel and scroll through to the ROM that I have, I get an error message : Trying to load a missing ROM.  I renamed the ROMS in Don's tool prior to installation.  The .ini file for NES has a ROM path of Emulators/Nintendo Entertainment System/roms, exactly where they are located in .nes format.  I even tried adding Hyperspin/ to the beginning of the path to see if that would make a difference and they technically are in the Hyperspin folder.  Any suggestions?  I'm at a standstill!!!

 
Link to comment
Share on other sites

2 hours ago, swurver said:

I loaded Hyperspin and was blown away by the beauty!!!  I created a couple test folders (NES, SNES, Sega Genesis) with 2 or 3 moms in each folder.  When I select the system from the wheel and scroll through to the ROM that I have, I get an error message : Trying to load a missing ROM.  I renamed the ROMS in Don's tool prior to installation.  The .ini file for NES has a ROM path of Emulators/Nintendo Entertainment System/roms, exactly where they are located in .nes format.  I even tried adding Hyperspin/ to the beginning of the path to see if that would make a difference and they technically are in the Hyperspin folder.  Any suggestions?  I'm at a standstill!!!

 
  •  

You fixed this right?

Tips.

Names match whats in database xml of system

Path is exact CASE SENSITIVE

Extensìon is added to ini file

 

Link to comment
Share on other sites

  • 2 weeks later...
  • 7 months later...
  • 9 months later...

Hi I'm learning to setup Hyperspin on PC now and it seems to work. My goal is to have it eventually on my Nvidia Shield. But since you say both versions can live together, I can't figure out how I could "export" my pc configuration easily to an android version?

Do I have to do it manually by editing all the ini and xml files or is there an easier way like using rocketlauncher? E.g. Where you need to give the path to the emulator, you could just download the apk and point it to the apk?

Link to comment
Share on other sites

14 hours ago, pina said:

Hi I'm learning to setup Hyperspin on PC now and it seems to work. My goal is to have it eventually on my Nvidia Shield. But since you say both versions can live together, I can't figure out how I could "export" my pc configuration easily to an android version?

Do I have to do it manually by editing all the ini and xml files or is there an easier way like using rocketlauncher? E.g. Where you need to give the path to the emulator, you could just download the apk and point it to the apk?

Its all manual im afraid. There is a collection of settings files in the downloads section iirc.

Link to comment
Share on other sites

15 hours ago, pina said:

Hi I'm learning to setup Hyperspin on PC now and it seems to work. My goal is to have it eventually on my Nvidia Shield. But since you say both versions can live together, I can't figure out how I could "export" my pc configuration easily to an android version?

Do I have to do it manually by editing all the ini and xml files or is there an easier way like using rocketlauncher? E.g. Where you need to give the path to the emulator, you could just download the apk and point it to the apk?

My honest advice would be to purchase Arc Browser on the Google Play store and use that. It's actively developed and being constantly improved upon and sadly Hyperspin isn't. I actually have both configured on my STV. That single purchase can be shared with your family account and/or used on your Android phone, so although it costs money you can get quite a lot of use out of it.

Arc Browser has ready made system presets and can scrape artwork online for the games. It integrates with the voice search which is a nice feature, you can say "Sonic" and all the Sonic games from all the systems you've added to AB's library will show. It now supports video previews, you can add favourite games (Hyperspin doesn't do that), choose to use Retroarch 32 or 64 bit versions for separate systems...I could go on and on. In short it'll make your life easier and is honestly a better frontend.

Hyperspin will have to be configured manually through the ini files in the "settings_android" folder. Yes the Hyperspin themes do look more flash than Arc Browser BUT many of them use swf in the zip files, so aren't compatible on Android (trust me I know, having tested and fixed soooo many of them for my STV). It's definitely worth the time doing Hyperspin and Rocketlauncher on PC, as you can do many more systems than on Android. It's your decision of course but hopefully some advice from an experienced retro gamer (i.e me) helps.

Link to comment
Share on other sites

  • 3 weeks later...

Great guide, thanks. Quick question...I think I already know the answer but wanted to confirm...

Ideally for me (Shield TV 2017 with external USB drive attached for ROMs & Media), the Hyperspin folder would be located on my USB drive in the NVIDIA_SHIELD folder so that I can directly edit *.ini files, etc from my PC. However when I put the Hyperspin folder there I get the "can't find Hyperspin folder" message. If I move the folder to the root of the USB drive then the Hyperspin app sees it and boots in fine. I know it was stated that for ROMs/Media on a NAS drive need to be in the root of the NAS drive but is the same true for external USB drives? Is there any way to change that or is it just baked in that way?

Thanks...Piper

Link to comment
Share on other sites

1 hour ago, PiperCalls said:

Great guide, thanks. Quick question...I think I already know the answer but wanted to confirm...

Ideally for me (Shield TV 2017 with external USB drive attached for ROMs & Media), the Hyperspin folder would be located on my USB drive in the NVIDIA_SHIELD folder so that I can directly edit *.ini files, etc from my PC. However when I put the Hyperspin folder there I get the "can't find Hyperspin folder" message. If I move the folder to the root of the USB drive then the Hyperspin app sees it and boots in fine. I know it was stated that for ROMs/Media on a NAS drive need to be in the root of the NAS drive but is the same true for external USB drives? Is there any way to change that or is it just baked in that way?

Thanks...Piper

Unfortunately those locations are fixed. The app would need updating and afaik theres no dev maintaining it currently. 

Link to comment
Share on other sites

  • 2 weeks later...
  • 6 months later...

Trying this out of curiosity. When I start a game Retroarch loads but stays on a black screen. I tried Mame4Droid, as it is the only non retroarch emulator, and that worked fine. Also the wheel seems to have every game listed in the xml rather than just the ones I have. Not sure if that's a bug or normal behavior for Hyperspin.

:edit: I think it's because I've both the 32bit and 64 bit RetroArch installed. Unfortunately I can't uninstall the 64 bit one because I have weeks of customisations on it.

Link to comment
Share on other sites

  • 2 weeks later...
On 3/29/2020 at 5:25 AM, VanZan said:

Trying this out of curiosity. When I start a game Retroarch loads but stays on a black screen. I tried Mame4Droid, as it is the only non retroarch emulator, and that worked fine. Also the wheel seems to have every game listed in the xml rather than just the ones I have. Not sure if that's a bug or normal behavior for Hyperspin.

:edit: I think it's because I've both the 32bit and 64 bit RetroArch installed. Unfortunately I can't uninstall the 64 bit one because I have weeks of customisations on it.

I have both 32 and 64 installed. Hyperspin can only run from the 64bit (the one in playstore) , so make sure you have installed the right cores in the 64 version. 

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 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 HyperSeeder
      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?
      Barely. I tested it with my NVIDIA Shield 2017 and 2019. It worked with all mentioned distributions, RA versions 1.9.0 and 1.9.1 How can I help?
      Test it and let me know if it works :).
      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.
    • 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/)
    • By iamthamiz
      Hi Guys if your trying to set up M64plus FZ on android this is what i did to get my one up and running with NVida Sheild TV
       
      exe=org.mupen64plusae.v3.fzurita/paulscode.android.mupen64plusae.SplashActivity
      parameters=
      romextension= n64,z64,zip,v64
      searchsubfolders=false
       
    • 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 '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
×
×
  • Create New...