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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By Honosuseri
      I realise there is already a thread for the Commodore Amiga in the Android section. I should know, as of late I've essentially taken it over! It's one of the most viewed threads in the Android section, so clearly many of you adore the Amiga as much as I do. 
      That thread has become quite long and it's quite confusing with people choosing to emulate the Amiga in different ways. I decided it would be best to start my own thread, streamlining it to show the best way to get this done. As I do have a "proof of concept" setup working! 
      This project I've taken on is a mammoth undertaking, as the Amiga is quite a complicated system to do. I'll try to explain why and how I've decided to proceed, keeping you guys up to speed with my progress here. 
      The first real issue is the naming that Hyperspin has been using for some time now. It's based from the Whdload zip file names, which was a logical choice BUT the problem is these zip names keep changing over time as they get updated. This throws the database entries and all media assets out of whack. It's my belief that this naming is what is really holding us back doing the Amiga justice.
      Second problem for us Android users anyway, is that we can't use the zip files directly with an emulator. They needed to be extracted out and we used a bootloader to patch the files for the emulator and launch the games. All seemed well and good until I started testing games and found many wouldn't work. Very confusing as the same game files worked fine from a workbench environment I'd set up, with it's own bootloader I added in. I suspected it was the "ultimate amiga" bootloader for the Hyperspin wheel at fault, which proved to be correct. 
      So the best way to launch these Amiga games from the Hyperspin wheel, is to actually use HDF versions of the games. This removes the need for the bootloader. I decided to keep the game folders extracted from the whdload zip files. Continuing to use these with the workbench (Amiga's OS) hdf I created. Having this is a nice nostalgic nod, I'm sure genuine Amiga fans will appreciate. 
      Unfortunately we can't just point the emulator to these hdf files, it's not that simple. Each game requires a config file that points to where the particular hdf game file is, what kick-start (i.e Bios) to use, video settings, control bindings etc. These files are known as uae files, as that is the extension we tell Hyperspin to look for. We trick it into thinking these uae's are the actual "game Roms".
      Sadly uae files aren't universal between emulators. So choosing the right emulator to begin with is important. Many people had chosen to use RetroArch. Which can't do the CD32, so I'll strike it off for that reason alone (although there are other reasons). I spent a long time waiting on Amiberry to be ported to Android but the devs haven't delivered. I'm not waiting any longer, so I'm continuing to proceed with Uae4arm. 
      As I write this, the latest version of Uae4arm crashes on Android TV (i.e Shield TV) but does run fine on Android phones. The devs are aware and trying to resolve this. There is an older apk version we can install for now, which does work. Another slight annoyance is that Uae4arm is quite fussy about how the uae files are named. They can NOT have special characters in them (e.g a space) or the emulator won't launch them!
      My next complaint was that Hyperspin has "rules" about what games should be included in the xml database file. I do NOT agree with these "guidelines". I want a definitive collection of Amiga games. 
      I've decided to branch the Amiga out into different wheels, ECS, AGA and CD32. As an analogy think of Sega's Megadrive and it's hardware addons. Megadrive=ECS, Sega32X=AGA (better graphics chipset on later Amigas) and finally the MegaCD=CD32 (better audio track and FMV).
      There is a "HDF game set" floating around. However... I got to know the creator, from doing videos on my proof of concept setup. I've persuaded him to rename the files to something more sensible, that should help other frontends scrape for metadata and artwork. These names will not change over time as he updates the collection. He does release notes, so this info can be used to keep the xml database file up to date. Currently he's overhauling the hdf files so they take up less storage and even adding cheat and trainer options to the loading splash screen....very cool stuff!
      I'm working on creating missing artwork (wheel, 3D box, diskette and video snaps), keeping busy until this new hdf collection is complete. Then I can start creating the uae files needed. This will be laborious, as Uae4arm doesn't do cycle exact emulation. I need to make sure each game is configured correctly to run at the proper speed, I'll also bind commonly needed keyboard keys to the gamepad on a per game basis.
      If you're confused, that's OK! It should all make sense, once I get around to uploading some more videos. Yes I will make my assets available to you all (minus the games obviously due to Hyperspin rules), once I'm happy with the collection.

      ***UAE4ARM BETA APK LINK***

      https://mega.nz/#!TYMQQKob!9pzwooQbkxVd-__mwmqtFWNF9JSR7D7rEgY8tqu31Vg
       
    • By Honosuseri
      Retroarch (Google Play) has updated itself to the latest version 1.7.8 and it seems to have broken compatibility with Hyperspin 😕

      Having done some quick reading (https://www.libretro.com/index.php/retroarch-1-7-8-important-changes-for-people-using-the-google-play-build/) it seems under the "infinite wisdom" of Google. They're forced to build in both 32 and 64bit support for the app, so the device (Shield TV) will default to using the 64bit version as it is a 64bit device. I'm not entirely sure what's gone wrong as I haven't had time to delve further into it, although I know ZeroJay did a modded Hyperspin apk for 64bit support (that doesn't work either). Just wanted to warn users so they don't update and have any aggro.

      You can still side load 32bit versions of Retroarch, I'll do that later and test. I'm actually quite excited about some of the features that have now come in the latest version.

      ***EDIT***

      The retroarch_ra32.apk (v1.7.8) changes the path (typical). So it's now "exe=com.retroarch32/com.retroarch.browser.retroactivity.RetroActivityFuture". Hyperspin doesn't like this and it misbehaves as it did trying to load the original 64bit Google play version, which is why ZeroJay did the modified Hyperspin apk.
       
    • By thatman84
      Please note my knowledge of this system does not run deep but everything here works and plays fine.
      What is it?
      Capcom Play System III or CPS-3 is an arcade system board that was first used by Capcom in 1996 with the arcade game Red Earth. It was the second successor to the CP System arcade hardware, following the CP System II. It would be the last proprietary system board Capcom would produce before moving on to the Dreamcast-based Naomi platform.
      How to emulate in Android (Shield TV)
      Quick and simple way is with the FBA core of RetroArch and matching FBA romset.
      At time of writing current versions are:-
      Core:- FB Alpha v0.2.97.42 (commit 6b7a701)
      FBA:- 0.2.97.42 (9 July 2017)
      Other options are MAME core in RetroArch or MAME4Droid reloaded (0.139mame romset). I believe the CHD files are needed for some games and with MAME4Droid, at least,  I had to "install" the game when it 1st launched in the emulator. That process took about 20-30mins and not all worked. Redearth was one I tested and "installed".
      Games
      JoJo no Kimyouna Bouken: Miraie no Isan (Japan 990913) = (jojoba.zip)
      JoJo's Venture (USA 990108) = (jojo.zip)
      Red Earth (Euro 961121) = (redearth.zip)
      Street Fighter III 2nd Impact: Giant Attack (USA 970930) = (sfiii2.zip)
      Street Fighter III 3rd Strike: Fight for the Future (EUR 990608) = (sfiii3.zip)
      Street Fighter III: New Generation (USA 970204) = (sfiii.zip)
       
      Note:-
      I replaced this entry in the official database with the european version as I could not get it to launch in FBA.
      Street Fighter III 3rd Strike: Fight for the Future (USA 990608) = (sfiii3u.zip)
      EDIT:- USA version is working with RetroArch core version 0.2.97.44. Make sure you have the correct RomSet version
      Setup Steps...
      1.  Open RetroArch and download the Arcade (FA Alpha) core.
                                     Main Menu -> Online Updater -> Core Updater

      1a. Transfer your games to your prefered location (You only need the six zip files listed in the database and above)

      2. Add the "Capcom Play System III" system to your Hyperspin setup with HyperHQ on a PC and transfer the files/folder to your device or by manually creating all the relevent folders to your device. (Download at bottom of guide)
      3. Add Capcom Play SYstem III to your Main Menu.xml or Main Menu_Android.xml
      4. Add these lines to your Capcom Play System III.ini file found in Hyperspin/Settings/ or Hyperspin/Settings_Android/
      exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
      romextension=zip
      parameters=cores/fbalpha_libretro_android.so
       
      PLAY SOME STREET FIGHTER .......................
       
      Extra Notes:-
      Under the FB Alpha "Quick Menu -> Options" you can select between different regions. Choosing a different region will give you the different loading screens along with other things I'm not sure about.
      Street Fighter III 3rd Strike (Default)Euro

      Street Fighter III 3rd Strike (USA)

       
      ANDROID MEDIA PACK AND DATABASE (Get your videos from emumovies.com)
      Hyperspin-CPS3Android.zip
       
       
    • By Honosuseri
      As we celebrate 25 years of DOOM! John Romero has brought us SIGIL, an unofficial 5th chapter to the original game. So as Retroarch's Prboom core has now been updated to support it...figured I should really add it to my Doom Classics wheel...
      Threw together a Sigil theme, wheel art and video snap. I was pleasantly surprised, that the prboom core now played the midi music natively. Doom 1&2 originally required me to add the music tracks as mp3 files. 
×
×
  • Create New...