Jump to content
HyperSync, HyperList and FTP are now back online ×

Search the Community

Showing results for tags 'Android'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Believe the Hype!
    • HyperNews
  • HyperSupport
    • HyperSpin
    • HyperSpin Android
    • HyperSpin 3rd Party Applications
    • HyperWorld
  • HyperStudio
    • Graphic & Theme Creation
    • Cabinets and Projects
  • HyperBase
    • HyperBase Live
    • HyperSync
    • HyperBase Databases
  • HyperPin
    • Content and Support
    • HyperPin Cabinet Forum
  • 1st Hyperspin Club's Club Brainstorm
  • 1st Hyperspin Club's History
  • Hyper Metal MoshPIT's Welcome brothers and sisters
  • Unofficial Tutorials's You Tube Releases

Categories

  • HyperSpin
    • HyperSpin (Windows)
    • HyperSpin (Android)
    • 3rd Party Apps
  • HyperMedia
    • Arcade Systems
    • Computer Systems
    • Console Systems
    • Handheld Systems
    • Pinball Systems
    • Miscellaneous Systems
    • Other Media
    • HTPC Themes
    • Universal Themes
    • Hall of Champions
  • HyperPin
  • HyperPin Systems

Categories

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Biography


Location


Interests


Occupation

Found 26 results

  1. 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/)
  2. 347 downloads

    Second attempt at doing a theme!!! I've not used hyper theme and edited it all by hand, rewriting the .XML and changing the images on my nexus 9. I think I will be doing in future, unless anyone knows of a way to create a .swf file on an android device??? Which I really need to start using to give the themes animation. Please rate if you like it, going to start doing a few more in the coming weeks
  3. 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
  4. 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
  5. As you probably know there is a RetroArch core to play Daphne games BUT currently it's broken! I wish the developer luck getting the official core stable. Thanks to @Reznnate. We now have access again to the working test core (HERE: https://drive.google.com/open?id=1frcFNWPinSkfyafsBXsnfHd46_kS1yIY). We can install this .so file through a new feature in RA, an install core option under "load cores" has been added. I've put together a video to help you peeps understand the Daphne game files and the settings required to get the games playing through RA and Hyperspin. I hope it's of help to some of you....
  6. 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
  7. 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
  8. 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... Android hardware is getting faster and faster. Emulators for Android are getting better and better. We wanted to play with our Hyperspin setups outside the house. 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. 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 Android 4.4+ NVIDIA OpenGL drivers ONLY Tegra4, Tegra K1, Tegra X1 Drivers (Tegra Mobile Device List) Confirmed working device, but not limited to, Shield Portable, Tablet and TV, Google Nexus 9, MiiPad, ADT-1 Tested Emulators Release statements 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** 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 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 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. **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: A file explorer installed on your Android device (ES File Explorer in this case) 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 On your device open Google Play Store and search for Hyperspin 2. Install as any other Play Store app, accepting all permissions when prompted You will now see the Hyperspin app in you devices menu 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 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 Is my Local device directory /storage Is the name of my NAS Drive sdcard1 Next – Get a file explorer I Installed ES File Explorer (ESFE) by searching ES in your Play Store app and install as any other. A. Launch ESFE and navigate to the 1) Local then 2) Home - option. Place your Hyperspin folder here 3) 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. 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
  9. 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.
  10. uoYabause has been replaced by Yaba Sanshiro on Android. This is a very good Sega Saturn EMU with excellent compatibility. If you still have uoYabause as your EMU in your Hyperspin cfg you'll notice it no longer runs. http://www.uoyabause.org/blogs/46
  11. https://redream.io/ The Redream emulator for Sega Dreamcast, is available on the google playstore. I know people struggled with setting up the standalone Reicast emulator, Redream is far easier. No extra BIOS files are required and it detected my gamepad straight away, even found the game files! I have asked about launch intent, so the app is compatible with frontends like Hyperspin and Arc Browser. The reply I got was he meant to add the feature last night but "forgot" as inundated with day one crash reports. Once the feature is implemented, I'll do a video showcasing the emulator and show my settings.ini for Hyperspin
  12. Hi all, It seems retroarch (at least on android) has removed their Mupen64plus core and replaced it with Mupen64plus-next. My hyperspin (Nvidia shield) won't launch N64 games anymore because it's trying to launch a core that no longer exist. I have tried editing my "Nintendo 64.ini" file with multiple variations to get the new core to launch, but I cannot get it to work. Anyone know the new core parameters off hand? I've searched quite a bit and am coming up empty. Just to clarify I'm looking for the "Parameters =" line under the exe= that determines which core retro arch will use. I have confirmed manually loading the "Mupen64Plus-Next" core works with content. I just can't seem to get the command line correct to have it launch from hyperspin. Any help is appreciated thanks! I have already switched to it launching "Mupen64 FZ" in the meantime, but I prefer the launch coming from retroarch because FZ resumes mid-game where you left off when starting from hyperspin, and I prefer the WOW factor of games loading from the title screen.
  13. Version 0.139

    106 downloads

    MAME, HAME, HAAA! SUMMARY - MAME 0.139 version (is not 0.139u1, for that is needed to compile). - 7396 games (all working games, including mahjong, casino, quiz, etc). - Description names respected (i.e., King of Fighters will appear like "The King of Fighters"). - Only excluded from the xml BIOS and non working games. - Created Genres xml files that match 100% with this MAME 0.139 version (I did with the hope that someone someday will enable the genre feature in the Android version of HyperSpin). A bit of blablabla... I have on my own an Nvidia Shield TV and I was looking for an exactly and precise xml for MAME 0.139u1 (because mame4droid, the app in Android for MAME, use this version). Is MAME 0.139 like a Canon for Android? Humm, I don't know but that's seems, because after 8 years (MAME 0.139 was release is 2010) and 2 years of the app in Android, there still been using this version. I didn't know nothing about MAME, so I learned how MAME works. I couldn't create an exactly xml for MAME 0.139u1 because for that is neccesary compile MAME 0.139 with the source (that you can download from the official MAME site) and I don't know yet how to compile this "old" MAME version. At the end of the day, the most of the users don't go to compile nothing in their lives, and they will have the 0.139 version in theirs computers and not the 0.139u1 or others updates. If someone is looking for a perfect xml for 0.139u1, it's your lucky day, I did the hard work with this list, feel you free of download this xml and add thats extras of the 0.139u1 to the list. Anyway, I could create an exactly xml for MAME 0.139 and that was what I did. HOW I DID IT? First of all, I downloaded the official Database for MAME from this HyperSpin site. After that, I created a xml with the tool "HyperROM2XML" and then I started to copy/paste the info, but I took special care, because I learned that in every MAME update there are some fixings like roms changing names. So what I did was install a gui version of MAME 0.139 to compare sometimes if the info was correct. I checked too in arcade database website if the info was correct with somes older roms (for example, Mega Tech doesn't exist in MAME 0.139, but appear like Mega Play). So yeah, this is an exactly xml for this version. Maybe can contain some errors, Im not perfect, shit happens. The xml should be revised and fixed if there are some errors (ejem..., honestly I think that no one have the balls to do that lol). Enjoy! EXTRA NOTES: If you use this MAME xml like a "master" in your HyperSpin installation (because you have all this 0.139 roms) and you want install "systems" like Capcom Classics, Data East, Irem Classics, etc., maybe you should consider the following: This MAME 0.139 is older (but seems like a "Canon" for Android) and the official Databases that you will download from this HyperSpin site will have added more roms to their xml list. So, RocketLauncherUI will show you that you have missing roms. In my installation I have two MAME´s in my HyperSpin wheel: MAME and MAME Android (this 0.139). Why I have this? Because im doing a dual boot HDD, for PC and Android. Before I forget it, thanks to all the people that helped me to understand and modify the xml for Hyperpin, now im a xml god lol Well that's all
  14. Version 1.1

    25,207 downloads

    My Attempt at making Andriod, MAC, PC users 1st steps in to Hyperspin Android easier This is an adjusted version of the Media and Databases that are included with Hyperspin Full Install 1.3.3 Tweaked and cutdown for use directly with Android devices (It will not directly work with a PC although you can merge it with a PC setup to aid the building of an Android setup) Whats Included Indenticle Media files as 1.3.3 with some removals Pre configured Settings files Brief Android Emulator setup notes MAME Adjusted xml for 0.139 ROM set (Default one included also Outdated) Additional Settings files for 123 systems/collections (Provided by Badhemi) Systems Included & Emulators suggested Atari 5200 (Retroarch MAME (Arcade) Core) Atari Lynx (Retroarch Handy Core) MAME (MAME4droid Reloaded (Red) 0.139v romset NEC TurboGrafx-16 (Retroarch Mednafen PCE Fast Core) Nintendo 64 (Retroarch Mupen64Plus Core or Glupen Core) Nintendo Entertainment System (Retroarch Nestopia Core) Nintendo Game Boy Advance (Retroarch VBA Next Core Panasonic 3DO (Retroarch 4DO Core) Sega 32X (Retroarch Picodrive Core) Sega CD (Retroarch Picodrive Core) Sega Dreamcast (Reicast 73e2691 2016_05_22 Build) Sega Game Gear (Retroarch Genesis Plus GX Core) Sega Genesis (Retroarch Picodrive Core) Sega Master System (Retroarch Picodrive Core) SNK Neo Geo (Retroarch FB Alpha Core) SNK Neo Geo Pocket Color (Retroarch Madnafen NGP Core) Sony PlayStation (Retroarch PCSX Rearmed Core) Super Nintendo Entertainment System (Retroarch BSNES Mercury Performance Core) See this Thread for details (Tutorial) Hyperspin Android Overview & Installation Install Notes To install this Hyperspin Android base pack Step 1 - Combine the download parts Extract the "Hyperspin 1.3.3 Android PT1" (Hyperspin.zip) file Place the "Hyperspin 1.3.3 Android PT2" (Media.zip) file within the extracted Hyperspin folder Extract the "Hyperspin 1.3.3 Android PT2" (Media.zip) file and it will combine the two parts Alternativly extract both files and the cut and paste them together (Optional Addition) Extract the Settings_Android.zip and pick out the settings files you require as you build your setup. Place them in your Settings folder or Settings_Android folder depending on your setup Rename specific systems if needed ADD YOUR ROMPATH Step 2 - READ the Setup Notes.txt Step 3 - Organise your roms Organise your roms so they are located in the suggested folder structure OR place them in a location of your own choice. MAKE sure you adjust the "SYSTEMNAME".ini files to reflect your own rompath ****Remeber rom names will need to exactly match your Hyperspin databases (.xml) and be in a format that your chosen emulator can open**** Step 4 - Move the pack to your Android Device Once you have the complete Hyperspin folder place this at the root of your storage device connected to your android device (USB HDD, Internal storage, SDCard or Network drive) Step 5 - Download and configure your emulators Step 6 - Install Hyperspin Application Download and install the Hyperspin application from the Goggle Playstore
  15. The Hyperspin app is not on the playstore. (Google need confirmation about targeting children ?, App has been resubmitted, back up soon) Here is the download Here is a backup of the apk Hyperspin_Android-test.apk
  16. Version 1.0.0

    213 downloads

    These are files to go along with the Tutorial/Info thread I created @diskmach made some adjustments to the database. so everything is based off that.
  17. Bjalready

    Android - Bezel

    17 downloads

    ...
  18. MAME 0.139 + Genre (all working games) View File MAME, HAME, HAAA! SUMMARY - MAME 0.139 version (is not 0.139u1, for that is needed to compile). - 7396 games (all working games, including mahjong, casino, quiz, etc). - Description names respected (i.e., King of Fighters will appear like "The King of Fighters"). - Only excluded from the xml BIOS and non working games. - Created Genres xml files that match 100% with this MAME 0.139 version (I did with the hope that someone someday will enable the genre feature in the Android version of HyperSpin). A bit of blablabla... I have on my own an Nvidia Shield TV and I was looking for an exactly and precise xml for MAME 0.139u1 (because mame4droid, the app in Android for MAME, use this version). Is MAME 0.139 like a Canon for Android? Humm, I don't know but that's seems, because after 8 years (MAME 0.139 was release is 2010) and 2 years of the app in Android, there still been using this version. I didn't know nothing about MAME, so I learned how MAME works. I couldn't create an exactly xml for MAME 0.139u1 because for that is neccesary compile MAME 0.139 with the source (that you can download from the official MAME site) and I don't know yet how to compile this "old" MAME version. At the end of the day, the most of the users don't go to compile nothing in their lives, and they will have the 0.139 version in theirs computers and not the 0.139u1 or others updates. If someone is looking for a perfect xml for 0.139u1, it's your lucky day, I did the hard work with this list, feel you free of download this xml and add thats extras of the 0.139u1 to the list. Anyway, I could create an exactly xml for MAME 0.139 and that was what I did. HOW I DID IT? First of all, I downloaded the official Database for MAME from this HyperSpin site. After that, I created a xml with the tool "HyperROM2XML" and then I started to copy/paste the info, but I took special care, because I learned that in every MAME update there are some fixings like roms changing names. So what I did was install a gui version of MAME 0.139 to compare sometimes if the info was correct. I checked too in arcade database website if the info was correct with somes older roms (for example, Mega Tech doesn't exist in MAME 0.139, but appear like Mega Play). So yeah, this is an exactly xml for this version. Maybe can contain some errors, Im not perfect, shit happens. The xml should be revised and fixed if there are some errors (ejem..., honestly I think that no one have the balls to do that lol). Enjoy! EXTRA NOTES: If you use this MAME xml like a "master" in your HyperSpin installation (because you have all this 0.139 roms) and you want install "systems" like Capcom Classics, Data East, Irem Classics, etc., maybe you should consider the following: This MAME 0.139 is older (but seems like a "Canon" for Android) and the official Databases that you will download from this HyperSpin site will have added more roms to their xml list. So, RocketLauncherUI will show you that you have missing roms. In my installation I have two MAME´s in my HyperSpin wheel: MAME and MAME Android (this 0.139). Why I have this? Because im doing a dual boot HDD, for PC and Android. Before I forget it, thanks to all the people that helped me to understand and modify the xml for Hyperpin, now im a xml god lol Well that's all Submitter Peliculon Submitted 03/20/2018 Category Databases (XML) Credits GOD  
  19. Version 10May2015

    8,334 downloads

    **reported as broken archive, any problems please report with specific details** Reznnate's settings folder. Add additional folder to /Hyperspin/Settings_Android
  20. Version 1.0.0

    78 downloads

    Android it has 384 games
  21. Android (Unofficial Database) View File Android it has 384 games Submitter IceLancer Submitted 01/17/2018 Category Databases (XML) Credits IceLancer  
  22. Android Main/Default Themes Pack - 4:3 View File This theme can be used as default/system theme as it can as main theme. This pack contains Arcade, PSX or Xbox buttons to choose from. This theme doesn't use Special arts, deactivate them in HyperHQ or just move or delete the special folder which contains special.swf files. HyperHQ Settings, copy these settings, it will make the theme look correct with these themes: Here you can disable special artwork that won't be used in these themes: Submitter Aorin Submitted 12/08/2016 Category Main Menu Themes HyperBase Version Media Dimensions File Count Credits  
  23. 47 downloads

    Galaxy S6 Edge wheelart includes blank PSD file to add your own games.
  24. Version version 1

    1,530 downloads

    Example Android database
  25. Hyperspin (for Android) Updated 3/18/2017 New Issues SWF rendering (blending/shadow) issue with various 'arcade' themes - reported by AustinRock - http://www.hyperspin-fe.com/forums/topic/31297-menu-problem/ Known Issues - 6/10/2015 SWF Missing swf sound Slow decode speed when loading jpegs with alpha channel (Primal Rage, King of Monsters) Incorrect animation speed Boot Hill, Bomb Jack, Ironman ISSOTP, Ninja Gaiden, Red Baron, etc. Rendering clipped by movie bounds, wrong position 1943, Enduro Race, Fever SOS, Hippodrome, Jail Break, Jungle Hunt, Red Baron, Ninja Gaiden, SAR, Splatterhouse, Super SF2T (world), Tondemo Crisis, Wargods, etc. Crashes Crazy Kong, Heavy Barrel, Super Mario themes (NES/SNES), Sexy Parodius Incorrect animation looping point Assault, Jumping Jack, Life Force, Metal Slug, Mighty Pang, Millipede,, Konami's Ping Pong, Rabbit Punch, R-Type, Salamander, etc. Missing focal gradient support Missing blend modes (corruption) Galaxy Force 2, King of the Monsters, Lock-On, Night Driver, Return of Invaders, Super Bomberman2 (SNES), Windjammers ANIMATIONS Not yet implemented "type" animations Arc Grow, Arc Shrink Blur Bounce, Bounce Around 3D, Bounce Random Chase Elastic, Elastic Bounce Flag Flip Grow Blur, Grow Bounce Pendulum Pixelate, Pixelate Zoom Out Rain Float Scroll Stripes, Stripes 2 Strobe Not yet implemented "rest" animations Squeeze OTHER theme issues bshape="round" unsupported 1on1gov, battletoads, etc. Rotation along the y-axis not perspective correct Particle layer not yet implemented VIDEO Delay before looping on some videos Potential audio corruption/clipping with video playback At least one transition video MUST be copied in the frontend/video/transitions folder WHEEL (features not yet implemented) Missing up/down scrolling animation Missing left/right skipping animation Missing sound effects Missing left/center wheel position Missing text_stroke_size, text_stroke_color, text_color3, color_ratio Crash when loading an empty wheel Sub-wheel, wheel layout parameters Horizontal mode SPECIAL ART Missing special art switching animations Other missing features Favorites, Genres Widescreen mode Render 3D models Touch-screen input Additional settings and configuration hook-up Additional support for more Android devices
×
×
  • Create New...