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
      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. 
    • By thatman84
      (FYI having trouble with upping some screenshots and the new formatting so please excuse the wierd format)
      Converting 16x9 Themes for Hyperspin Android
      List of theme animation compatibility
      https://drive.google.com/folderview?id=1-8Ofa_GrAdnQ22nf7W7QYVeQoKBQxA_-
      (I am in NO way competent with artwork resolutions but my method works and looks good to me)
      Why...
      Because sometimes that theme you really liked just doesn’t display correctly 
      The main reason for theme problems is the use of animation and scripting of the .swf assets in the “theme”.zip
      (It’s best to replace themes that cause Hyperspin to crash out, but you can try to convert them)
       What’s covered...
             1.      Extract PNG assets from swf files
             2.      Reduce HQ artwork to be compatible with Hyperspin
             3.      Further reduce artwork width to allow for Hyperspin 4x3 -> 16x9 stretching
             4.      Recompile your theme
       
      What is Needed:
      Update on resizing tool.
            Fotosizer is now advised against because of the compression/quality loss it causes.
      pPlease use Photoshop or this program recommended by @IceLancer https://sourceforge.net/projects/easyimagesizer/?source=typ_redirect
      A    A  Fotosizer (http://www.fotosizer.com/) batch resize image files
              B.     Flash Decompiler (https://www.free-dec...flash/download/) extract png’s from swf
              C.     Time and Themes
       I have done a little testing for Main Menu themes. This spreadsheet shows what I have tested and its Android compatibility status. The sheet has download section links for all themes I have tried.
       
       
      Let’s get to it... 
       
      So grab a theme zip you want to play with and Unzip it. Any 16x9 Main Menu, Game or System Default theme will do.
       
       
      BakerMan provided me a guide to extracting the PNG’s from SWF but it has since been lost. 
      These are the steps
              1.      Open JPEXS once downloaded and installed from link above
              2.      Click on the “Open” tab and browse to the offending .swf file from your unzipped theme
       
           SCREENSHOT
      3.     
       

       

             3.      Right click on “Images” on the left and click “Export Selection”
      (At this step you may find multiple images. If these images are only parts of one image, say the arms and legs of a character, you will have to lose that image completely from the theme or replace it with another one)
       
      SCREENSHOT2
             4.      Click “ok” to PNG file type then choose a location for the exported images (Default is Desktop. Only export one at a time and  then move the PNG out of the output folder as it overwrites each one if not)
       
       
      SCREENSHOT3
             5.      Now browse to that Output location and you will find your PNG’s in an “images” folder.
       

       
      You are now ready for phase 2 – Resizing the images
      Note, fotosizer does cause a reduction in artwork quality. If your sensitive to this you may want to use another method. (If you know of a better program please comment) I only run a 37' screen and don't mind myself.
      (Resizing Artwork is covered comprehensively by Avar in his tutorials found HERE)
      Open Fotosizer Add the Artwork that was converted to PNG Reduce the images to 68% KEEP MAINTAIN ASPECT RATIO TICKED (this is the best size for the ones I have done)  
              4.       Move the right side settings bar down and select an Output Folder
       

      5   Remove that Artwork from Fotosizer
      6.   Add the newly resized artwork back into Fotosizer
      7.   Reduce the Width to 75% (to allow HS to stretch it back when its loaded)
      8.   UNTICK MAINTAIN ASPECT RATIO
       
             9.   Now add this finished art back into the theme folder and zip it up again
            
             10.       Name the zip file the same as you have it in the “Main Menu.xml” database
       
      Final Thoughts...
       
       
      Now when you try this theme out you may find the artwork has slightly changed location. If so adjust the Artwork positions in the theme.xml file within the theme.zip OR load it into Hypertheme and adjust it as required
       
       
      Hope this helps someone.
       
       
      HS Android Theme Animations.txt
    • By reznnate
      Tested Emulators -- .ini config settings   Retroarch - Various emulators   exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture  parameters=<choose one of the emulator cores like below>   Examples of retroarch core parameters Atari 2600 core:  parameters=cores/stella_libretro_android.so PSX core:  parameters=cores/pcsx_rearmed_libretro_neon_android.so   libretro cores:  4do_libretro_android.so  bsnes_mercury_performance_libretro_android.so  bsnes_performance_libretro_android.so etc...     Dolphin - Gamecube/Wii/Wiiware exe=org.dolphinemu.dolphinemu/org.dolphinemu.dolphinemu.activities.MainActivity parameters=AutoStartFile    Newer Builds from Dolphin Website:-   exe=org.dolphinemu.dolphinemu/org.dolphinemu.dolphinemu.ui.main.MainActivity parameters=AutoStartFile    IrataJaguar - Atari Jaguar  exe=ru.vastness.altmer.iratajaguar/ru.vastness.altmer.iratajaguar.MainActivity  parameters=rom   Real3DOPlayer - 3DO  exe=ru.vastness.altmer.real3doplayer/ru.vastness.altmer.real3doplayer.MainActivity  parameters=cd   NES.emu - NES  exe=com.explusalpha.NesEmu/com.imagine.BaseActivity  parameters=   MSX.emu - Colecovision, MSX, etc.  exe=com.explusalpha.MsxEmu/com.imagine.BaseActivity  parameters=   Mame4Droid - MAME  exe=com.seleuco.mame4droid/com.seleuco.mame4droid.MAME4droid  parameters=   Mupen64Plus AE exe=paulscode.android.mupen64plus/paulscode.android.mupen64plusae.MainActivity
      parameters=    Nightly builds exe=org.mupen64plusae.v3.alpha/paulscode.android.mupen64plusae.SplashActivity parameters=     Play! - Playstation 2 exe=com.virtualapplications.play/com.virtualapplications.play.ExternalEmulatorLauncher parameters=   Reicast - Dreamcast  exe=com.reicast.emulator/com.reicast.emulator.MainActivity  parameters=   Redream - Dreamcast exe=io.recompiled.redream/io.recompiled.redream.MainActivity parameters=   Drastic - Nintendo DS  exe=com.dsemu.drastic/com.dsemu.drastic.DraSticActivity  parameters=GAMEPATH   Fpse - PSX  exe=com.emulator.fpse/com.emulator.fpse.Main  parameters=path   ePSX - PSX  exe=com.epsxe.ePSXe/com.epsxe.ePSXe.ePSXe   parameters=com.epsxe.ePSXe.isoName  * change romext=cue in settings.ini, iso did not work for me   PPSSPP (FREE version) - PSP  exe=org.ppsspp.ppsspp/org.ppsspp.ppsspp.PpssppActivity  parameters=org.ppsspp.ppsspp.Shortcuts PPSSPP Gold - PSP             exe=org.ppsspp.ppssppgold/org.ppsspp.ppsspp.PpssppActivity              parameters=   uoYabause - Sega Saturn exe=org.uoyabause.android/org.uoyabause.android.Yabause
      parameters=org.uoyabause.android.FileNameEx
      Yaba Sanshiro
           exe=org.uoyabause.uranus/org.uoyabause.android.Yabause
               parameters=org.uoyabause.android.FileNameEx
      Gearoid - Sega Game Gear  exe=com.androidemu.gg/com.androidemu.gg.EmulatorActivity   Parameters=   Colem - Speccy ZX - fMSX VGBANext  Emulators from Garage Research  PAID  com.fms.colem.deluxe - Colem - Colecovision  com.fms.fmsx.deluxe - fMSX  com.fms.ines - iNES  com.fms.emu - VGBAnext - GBA/GBC/GB Emulator  com.fms.vgb - VGBc - Gameboy Color  com.fms.mg - Master Gear - Sega Game Gear  com.fms.speccy.deluxe - Spectrum Sinclair ZX  FREE  com.fms.colem  com.fms.fmsx  com.fms.speccy    Set "??" to "com.fms.emulib.MainActivity" for all products but VGBAnext.   For VGBAnext:  ??=com.fms.vgba.MainActivity for opening *.gba files  ??=com.fms.vgb.MainActivity for opening *.gbc/*.gb files   OpenBOR - 2D Game Engine (Some integration issues with Hyperspin)              exe=org.openbor.engine/org.libsdl.app.SDLActivity Parameters=   Launch android app package names in database.xml Determine Android game name through Google Play web interface. i.e. https://play.google....ure.dragonslair   pcgame=true
    • By Honosuseri
      A video to help you understand the Redream emulator, covering issues and questions you might have. Currently Redream doesn't use launch intent but it will be added soon. I'll do another video to help with setting it up with Hyperspin (for STV) and Arc Browser (for phones & STV) once that feature is added in.

       
       
×
×
  • Create New...