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

Hyperspin Android Overview & Installation

Credits

BBB

Reznate

Thatman84

Lilcza

And anyone I have forgotten helped me learn this

My guides are only an extension of Reznnate's sticky posts

PLEASE READ the OTHER sticky posts

 

What is it?

An Android version of Hyperspin that works with existing themes and data directly from the Hyperspin community.   It launches both Android games and Android emulators.

 

Why?

Several reasons...    

  1. Android hardware is getting faster and faster.    
  2. Emulators for Android are getting better and better.    
  3. We wanted to play with our Hyperspin setups outside the house.    
  4. I wanted to replace the old PC in my MAME cabinet with a mobile device so I could justify leaving it on all the time.  
  5. It needed the ultimate launcher!!!

 

How?

Since the Windows version of Hyperspin is dependent on Adobe Flash, it was necessary to build the app from scratch. With performance in mind, the Android version is highly-threaded and renders with the GPU using OpenGL.

 

 

Compatibility

 

 

 

 

Hyperspin/Android Limitations

 

RocketLauncher is not available for use on Android but the settings files it uses within a PC setup are compatible.
 

  • Vertical Systems/Wheel list only
  • No Touch Screen Input (Controller required)
  • Favourites list feature not supported
  • Genre feature not supported
  • Searching subfolders for ROM’s not supported
  • Games list only supports launching of one emulator (multiple emulators can exist in settings line and the 1st one installed will be launched)
  • PC based animations and themes not fully functional. See this detailed post HERE

 

 

 

Never used Hyperspin before?

 

As Hyperspin Android was originally designed to allow PC users to have another way to experience their setup you will need to first decide how you would like to proceed with your Hyperspin Android setup

**Skip to Installation section if NOT using a PC**

 

 

  1. The easiest way is to  install the PC version for testing and building your Android setup (Follow Avar’s official tutorial videos HERE or follow step by step guides HERE
  2. Alternatively build your Hyperspin Android setup from iOS computer or directly from your Android device.

 

Already using Hyperspin on a PC?

You can co-exist your PC and Android Hyperspin setups in one Hyperspin folder by making the following additions.

 

  • Optional additional database file called "Main Menu_Android.xml". Located in your Hyperspin/Databases/Main Menu folder. This will allow for a specifically tailored Main Menu for your Hyperspin Android setup

1 Main Menu_Android xml.png

 

  • Optional additional settings folder called /Settings_Android. Located in your Hyperspin directory and populated with your Android specific Main Menu.ini, Settings.ini and SYSTEMNAME.ini’s. This allows both Windows and Android launcher/rompaths to co-exist in separate .ini files within the same Hyperspin directory.

2 Settings_Android Folder.png

 

**Note

Some of your PC Themes and features may not be compatible with your Android setup so it may pay to build a specific Hyperspin folder for your Android setup. If you take this opportunity to trim unneeded files to save storage space it will likely mean some 3rd party tools (Don’s Filter list and Hypertools) may not function correctly.

 

Also adjustments to your Android set of settings will need to be done manually with a text editor

 

 

 

 

Installation

 

What’s Needed:

  1. A file explorer installed on your Android device (ES File Explorer in this case)
  2. Optional: PC to make life easier

Step 1 – App Installation

Note: The device you are using and your chosen Hyperspin folder location (local, sdcard, external HDD or NAS) will directly affect your steps and settings file values

All testing was done on my NVIDIA Shield TV Pro 3.2 Marshmallow 6.0, slight differences may be found on other devices

                                                                     

  1. On your device open Google Play Store and search for Hyperspin

Hyperspin App Store.png

 

       2. Install as any other Play Store app, accepting all permissions when prompted

 

You will now see the Hyperspin app in you devices menu

Hperspin App Installed.png

 

 

Step 2 – Build your Hyperspin directories

To function, Hyperspin pulls all data from an installation folder NOT included with the app installation. Without this directory you will see the below screen when trying to launch Hyperspin

No HS Folder.png

Note: New users without a Hyperspin directory and not installing a PC version of Hyperspin please download

 

 Hyperspin Android base pack

(Adjusted from BBB's Hyperspin 1.3.3 file)

Existing users please locate your PC Hyperspin directory and copy this to the root of your preferred storage device (USB, SD card, internal storage or NAS) see below details.

 

 

But First...

 

Decide on Storage Media & Location...

 

I will now show you how to install Hyperspin onto the internal storage of your Android device. You are free to place your Hyperspin directory on a different storage device, including SD cards, USB storage and Network Attached Storage (NAS), but please be aware Hyperspin will seek and prioritize booting 1st from

 

/usbdrive/Hyperspin

then

/sdcard1/Hyperspin

then

/sdcard/Hyperspin

for your data.

 

Also note that on the Shield TV Pro /storage/Emulated/0 & /storage/sdcard are in fact the same location

 

If you will be using a NAS to store your Hyperspin directory, please be aware that there can only be one directory level between your devices /storage directory and your Hyperspin directory. For this to work, you will need to share your Hyperspin folder from your NAS device and the map that device to you Android device through its storage settings. It should then be seen in your devices /storage folder (I will cover this in detail in subsequent tutorials)

 

Example of correct NAS Path:-           /storage/MYNAS/Hyperspin

Example of incorrect NAS Path:-        /storage/MYNAS/SUBFOLDER/Hyperspin

 

My TEST path screenshot

  1. Is my Local device directory /storage
  2. Is the name of my NAS Drive sdcard1

1 NAS Path.png

 

Next – Get a file explorer

 

I Installed ES File Explorer (ESFE) by searching ES in your Play Store app and install as any other.

 

Play Store ESFE.png

 

A.        

Launch ESFE and navigate to the 1) Local then 2) Home - option. Place your Hyperspin folder here 3)

 

Local Hyperspin Folder Edit.png

 

 

Note: For a HSA to work the ONLY required files/folders for an Android installation are as follows

/Hyperspin

/Databases

/Media

/Settings

/Emulators (optional ROM location structure for ease of setup)

 

B.

Please now exit to your home screen and launch the Hyperspin App, to test everything is correct. Depending on your correct choice of Hyperspin directory you should now be greeted with the Hyperspin intro video and your Main Menu wheel of systems.

 

The base pack download will look similar to this example.

 

Default HS.png

 

This is what you get with the default Hyperspin 1.3.3 version I have adjusted

 

 

Now you have completed the basic installation there are some settings that require adjusting and reviewing to enable games to be launched.

Also the per system/wheel settings are covered here

 

  • Upvote 6
Link to comment
Share on other sites

There is badhemi'S set of about 86 systems in the Nividia beginners guide thread and also Reznates set of about 40 in the downloads section.

There is also a blank ini file in the

Anyone feel free to post up settings as settings will be my next focus.

There really is not many settings to change in the android version and big sets can leave odd problems I am aiming to overcome if possible.

Link to comment
Share on other sites

The only space I see for these is templates. That is where my base pack is.

As they can't be used directly on the PC or with RocketLauncher

If your ok with it badhemi I will take your settings files and do the following for release.

1. Strip out RocketLauncher parameters

2. Set all filters to false

3. Set all indexes to true

4. Default any custom positions

5. Adjust the rompath to uniform location except those that require specific (MAME softlists)

This should give anyone new a solid and simple base to start with.

I have a vanilla set of about 217 so will basically copy the rompath, exe and parameters out.

You have any problems with reload_backgrounds. I have seen that issue pop up. I don't have transitions and I think that's to option for them.

Link to comment
Share on other sites

  • 2 weeks later...

So I don't suppose rezznate or whatever his name is ever added the ability to define different themes to be used for the Android version? A lot of my themes don't work on the android version and I definitely don't want to switch them just for android and make my PC themes be different. Was hoping putting those files on the internal of the shield would override what was on the external drive but it seems the external is taking priority.

Link to comment
Share on other sites

Well that's not so bad then.

I have a process to convert the themes which works well depending on the animation used.

Sounds like you would be best creating a copy of your Hyperspin setup and adjusting the media for android. Then leave the rompath pointing to wherever it is. May be hard if your swapping a drive between droid and PC

(Reznate has done a great job getting it this far, but yes an update would be awesome. Developers are hard to come by on Android, I think it's the main reason for stagnation)

Link to comment
Share on other sites

Nah, I don't wanna break/lessen themes for PC just for Android. My Hyperspin for PC resides on my drive in the root in the Hyperspin folder, I would rather not have to rename that as I have a lot of other stuff dependent on that path. Oh well though, will drop Android until the day he may issue an update. Probably around the same time HS PC will get one =P

Link to comment
Share on other sites

So I don't suppose rezznate or whatever his name is ever added the ability to define different themes to be used for the Android version? A lot of my themes don't work on the android version and I definitely don't want to switch them just for android and make my PC themes be different. Was hoping putting those files on the internal of the shield would override what was on the external drive but it seems the external is taking priority.

what do you mean by your themes dont work? What's it doing?
Link to comment
Share on other sites

badhemi cheers for the themes any chance you could share your ini files too. PLEASE

Post #9 has badhemi's settings files link and it you look at the android base pack linked in first post you will find a cleaned up version with all RocketLauncher and filter preference's removed. For I hope easier setup.

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 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?
      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.
    • 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 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
       
×
×
  • Create New...