Jump to content
zerojay

Hacked Hyperspin APK - 32 and 64 bit Retroarch together - Best Cores?

Recommended Posts

A few days ago, I decompiled and edited the Hyperspin APK to allow users to use 32-bit and 64-bit installations of Retroarch together. It's been confirmed working by the community and you can find that edited APK here: https://zerojay.com/nextcloud/index.php/s/3QfPqYM4A6ymjr4

It works as you would have originally expected using a 32-bit or 64-bit version of Retroarch to work, so in your Settings_Android system ini file, change the exe to com.retroarch to use the 32-bit version or change it to com.retroarch.aarch64 to use the 64-bit version.

32-bit Retroarch: 
exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture

64-bit Retroarch:
exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture

Currently, both 32-bit and 64-bit versions of Retroarch will be called using the 32-bit configuration files, however I will likely be updating the APK to allow you to use the 64-bit configs as well for those who may wish to use different settings for both. When that happens, I'll keep both versions of the APK available so that you can decide what you want to use.

So now that the community has solved the Retroarch 32-bit problem, it would be really helpful to compile a list of cores and the version of Retroarch that it works best under. In some cases, certain cores currently only function under one or the other, but not both. In some rare cases, cores stopped working like Daphne, so again, these are things that we would like to call out. (By the way, for anything like Daphne where more recent cores no longer work, I can host them for the community if needed. Just let me know (and I do myself still need to get that working Daphne core myself).

I'll update the top post here to reflect the community's findings so that people only need to come to one place to find the info they need.

--- Core Information ----
atari800 - non-functional on 32-bit due to Android security changes, use 64-bit Retroarch core.

mame - Latest version of MAME core only recently started compiling on 32-bit, not available yet on 64-bit.

EDIT: Updated link for latest updated build.

  • Like 2
  • Super Like 1

Share this post


Link to post
Share on other sites

I had the test core for Daphne which worked really well. Updating to the version from the buildbot broke it. I too would love this working again. 

Back on topic..

Reicast core crashes for me in Atomiswave games on RA64

Latest PUAE core for Amiga is best run on RA64 if you want to load hdf files directly. 

Dolphin core is available on RA64 but does have some graphical issues in some games (e.g Starfox) 

Share this post


Link to post
Share on other sites

Hmm this is interesting. Would love to try this out but from the beginning I ran into my first problem. The moment I started a mame game from the wheel I was presented with the message "Failed saving config to "/data/data/com.retroarch/retroarch.cfg". From there everything ran as if I was running Retroarch for the very first time, no shaders loaded, couldn't use hot key buttons etc. I also noticed you patched the last version of the Hyperspin apk instead of the latest 0.1.8 version.

Share this post


Link to post
Share on other sites
43 minutes ago, sonkun said:

Hmm this is interesting. Would love to try this out but from the beginning I ran into my first problem. The moment I started a mame game from the wheel I was presented with the message "Failed saving config to "/data/data/com.retroarch/retroarch.cfg". From there everything ran as if I was running Retroarch for the very first time, no shaders loaded, couldn't use hot key buttons etc. I also noticed you patched the last version of the Hyperspin apk instead of the latest 0.1.8 version.

Hmm, you're right. The version on the store is more up to date than what apkpure gave me. I'll fix this.

Share this post


Link to post
Share on other sites

I have a feeling installing that older version caused that, I'll see when you update it.

Share this post


Link to post
Share on other sites
5 hours ago, sonkun said:

I have a feeling installing that older version caused that, I'll see when you update it.

Another forum member had tested that apk and said it worked great. He's got a lot of experience with the STV and Hyperspin. Good catch that an older version of Hyperspin had been modded. 

I've not tested it myself. At this current time, there's no real incentive for me to use RA64

Share this post


Link to post
Share on other sites

Oh yeah definitely, I noticed right away when I tried to install the modded apk over my latest version. I actually had to delete the latest version just to install the mod. I figured that's the way things had to be since he chose that version until he replied lol. This is good development right here as far as pushing Android Hyperspin forward a little.

  • Like 2

Share this post


Link to post
Share on other sites

If things pan out I will have a word with the admins about getting this rolled out or at least more visible.

Theres probably some improvements to the Beetle HW core in 64 bit. I remember the RA mods mentioned it 

 

Edit: i tried to test it yesterday but I migrated my roms to NAS and now it wont launch ps1. Have to fix that 1st

Share this post


Link to post
Share on other sites

Here's the updated 0.1.8 build: https://zerojay.com/nextcloud/index.php/s/3QfPqYM4A6ymjr4

It gives me problems, likely because my configs aren't in the proper places anymore judging from the changelog for 0.1.8, so my controllers aren't recognized as they used to be, for instance. Once I figure this out for myself, I may move on to trying to update the CONFIGFILE part of the launch intent so that 32 and 64 bit will have their own configurations respected.

I can say that MAME-2013-plus seems to play Killer Instinct far smoother on 64-bit than 32-bit. 

  • Super Like 1

Share this post


Link to post
Share on other sites

So I tried the updated apk and I can now start a game from the wheel but now when I start a game a different message pops up saying "Warning: Missing assets, use the online updater if available. I then tried to go update the assets within Retroarch but that doesn't fix anything, in fact I'm not sure where it's saving/loading anything from as I can't get to the shaders/overlays etc folders. I can at least use hot keys and overrides still load up. Maybe everything will work if both Retroarchs use their own configs.

Share this post


Link to post
Share on other sites
On 4/9/2019 at 3:07 AM, sonkun said:

So I tried the updated apk and I can now start a game from the wheel but now when I start a game a different message pops up saying "Warning: Missing assets, use the online updater if available. I then tried to go update the assets within Retroarch but that doesn't fix anything, in fact I'm not sure where it's saving/loading anything from as I can't get to the shaders/overlays etc folders. I can at least use hot keys and overrides still load up. Maybe everything will work if both Retroarchs use their own configs.

Hi, so do you resolve your problem with assets and shaders ?

I hesitate to delete the official apk and test this marevous custom build ?

thanks for your confirmation

regards

Share this post


Link to post
Share on other sites

so I made a test this new apk after deleting the former one but unfortunaly, it doesn't work. when a load a romfrom hyperspin, it continue to point to the regular retroarch 32 bits.

I have change in settings of the core :

exe=com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture

but no luck

little disappointed because I thank we have found the best solution.

is others guys test it with success ?

thanks for your support

 

Share this post


Link to post
Share on other sites

I forgot to mention that severals of my 64 bits folder path aren't on default location but with custom path (example: I share the system folder 32 and 64 bits with the same path).

Maybe we have to keep all default location of 64 bits folder to work

I may need to make a fresh instal of retroarch 64 bits and then, make a new test of the apk.

If someone could confirm me if it already work on fresh install  thanks

Share this post


Link to post
Share on other sites

I deleted and installed a fresh copy of retroarch 64 and tested a game, this time I don't get that message about missing assets but I still can't do much else. I can still change directory paths, save overrides but can't load shaders or overlays cause it seems to point to a empty folder. I made a video to show you what i see using the snes 9x core. I believe the only way to fix this is to have hs load configs separately from each ra version instead of having ra 64 use the folders from the 32 one.

https://streamable.com/e6gyz

Share this post


Link to post
Share on other sites

Hey everyone... quick question....I had to reset my shield TV because I downloaded a shady apk that was causing my shield to act up and it would restart regularly on its own....so anyways moving forward , I installed the 1.8 Hyperspin apk and everything seems to work as far as my bezels per game and controller configs and even loading my own custom cores within the downlaods folder...my big issue is now now matter which apk I use (retroarch1.7.6, or retroarch64 1.7.5) when I exit out a game it restart hyperspin.....it doesn't exit back to the game wheels but instead I get the hyperspin startup video then the main menu wheels.....anyone experience that or is it just me?

Share this post


Link to post
Share on other sites

My fault....I had the shield button enabled to kill apps if not currently using...turned it off and all is working now as normal ?

Share this post


Link to post
Share on other sites
On 4/27/2019 at 9:28 AM, sonkun said:

I deleted and installed a fresh copy of retroarch 64 and tested a game, this time I don't get that message about missing assets but I still can't do much else. I can still change directory paths, save overrides but can't load shaders or overlays cause it seems to point to a empty folder. I made a video to show you what i see using the snes 9x core. I believe the only way to fix this is to have hs load configs separately from each ra version instead of having ra 64 use the folders from the 32 one.

https://streamable.com/e6gyz

Did u set those folders in the directory settings?....it seems like u didnt because when u 1st opened the menu it automatically pointed to the default location in hidden files section...I can confirm that I'm using hyperspin 1.8 retroarch3264 and using retroarch 1.7.6 and also using retroarch64 1.7.5....I changed all important locations that I personally use to edit things like configs folder, overlays folder downloads folder and info folder....did it for both retroarch apks...also changed the open menu buttons to start +back and exit left and right thumbs....did it twice on both apks...1 for standalone apk and again after hyperspin launched both apks....everything is confirmed working as it should

Share this post


Link to post
Share on other sites

so I made a fresh install of retroarch 64 and it works. thanks.
The only weird things (bu you ever advice us) is that all core override and others saves are made on the 32 bits installation if you do that
n retroarch launched by hyperspin.
i hope some days you could update your marvelous APK to have 2 config files separatly.
so we could use retroarch 32 bits in GL mode and retroarch 64 bits in vulkan mode. thanks again

Share this post


Link to post
Share on other sites
On 5/4/2019 at 12:18 AM, sanchezmike01 said:

Did u set those folders in the directory settings?....it seems like u didnt because when u 1st opened the menu it automatically pointed to the default location in hidden files section...I can confirm that I'm using hyperspin 1.8 retroarch3264 and using retroarch 1.7.6 and also using retroarch64 1.7.5....I changed all important locations that I personally use to edit things like configs folder, overlays folder downloads folder and info folder....did it for both retroarch apks...also changed the open menu buttons to start +back and exit left and right thumbs....did it twice on both apks...1 for standalone apk and again after hyperspin launched both apks....everything is confirmed working as it should

That right there did the trick. I assumed it was suppose to work off of the ra 32 version folders, thanks a lot. Feels good to be able to run bsnes (balanced) and beetle psx hw right off the wheel. Are you able to get dolphin working though? For some reason it crashes every time I launch a game just from stand alone ra. I remember that core working for me about 2 months ago, got all folders in the right place unless something changed or maybe the core went bad.

Share this post


Link to post
Share on other sites
14 hours ago, sonkun said:

Are you able to get dolphin working though? For some reason it crashes every time I launch a game just from stand alone ra. I remember that core working for me about 2 months ago, got all folders in the right place unless something changed or maybe the core went bad.

It works on the Google play store build but not the newer versions of RA64. 

As I've already said it's not worth using over the dedicated dolphin emulator, due to graphics glitches in some games. 

Share this post


Link to post
Share on other sites

Hi,

another weird thing is that when I load directly reicast on 64 bits version: it's fullspeed.

but when I load reicast 64 bits through hyperspin, the gamer are slower.

I know that it read the 32 bit "retroarch-cores-option" file so I made the exact same settings as my 64 bits "retroarch-cores-option" but

the game stay slower. weird no ?

I hope You could progress in your great custom apk in order to split the config and core option files between 32 and 64 bits.

thanks

 

NEVERMIND  SORRY !

I forgot to disable rewind on the 32 bits general option files witch create slowdown. (no activate on 64 bits).

Now it work like the standalone retroarch 64 bis  thanks again ans sorry

Share this post


Link to post
Share on other sites
20 minutes ago, mikty said:

I hope You could progress in your great custom apk in order to split the config and core option files between 32 and 64 bits.

ZeroJay said he would, be patient there's no need to keep pestering about it. If you really want RA64 that badly, pay for the Arc Browser frontend and use it alongside Hyperspin. AB is being actively developed and is technically a superior frontend. This thread is meant to point out cores that are working and on which version of Retroarch.

@zerojay RetroArch now allows us to install cores manually, if we have the *.so file in the Retroarch/Downloads folder! It will make sharing the working cores much easier now, no need for you to take on the hassle of creating an online server for RA's config file to be pointed to :)

  • Like 1

Share this post


Link to post
Share on other sites

@zerojay Would be great if you could decompile and change it so it runs with retroarch.ra32

Will try myself but dont now how to get it compiled again after I have decompiled.

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

Share this post


Link to post
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

  • Similar Content

    • 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/)
    • 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...