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

SETTINGS: Android emulator settings

Recommended Posts

Working on (My Boy!) GBA emulator :)

Got this line:

exe=com.fastemulator.gba/com.fastemulator.gba.MainActivity

But opens to the game menu, any idea's on how to get it to launch the game straight off???

 

I do not -- likely needs a secondary rom parameter for param=.   I suggest asking the developer.

Share this post


Link to post
Share on other sites

Yeah, i thought so :/ Just dropped him an email, I'll post the parameters if they reply :)

Share this post


Link to post
Share on other sites

If I use this:

 

paulscode.android.mupen64plusae/paulscode.android.mupen64plusae.MainActivity

 

It launches the emulator and I can then launch the ROM. But how do I make it launch the ROM directly like with the other emulators? 

Share this post


Link to post
Share on other sites

Don't think you can with that version, but the newest alpha version can. (as of now roms have to be unzipped, probably for debugging reasons)

Share this post


Link to post
Share on other sites

Don't think you can with that version, but the newest alpha version can. (as of now roms have to be unzipped, probably for debugging reasons)

Do you know where I can get an .apk of the latest alpha version so I don't have to build one? 

 

Edit: nevermind... found it. 

Edited by dbowles1975

Share this post


Link to post
Share on other sites

Try this line instead :)

org.mupen64plusae.v3.alpha/paulscode.android.mupen64plusae.SplashActivity

Mupen 64 plus AE beta is available on the play store, there's a free version and a paid which is only £0.62 and well worth it!!!

Share this post


Link to post
Share on other sites

I'm almost done with not using retroarch for all the emulators as I can't figure out how to even use it to begin with. The only ones I'm having trouble with is the Sega Genesis. I believe I got GameGear going finally but have to check later. But I'm curious about Atari Lynx.. Does alynx work with the ShieldTV or are there any other emulators to use other than retroarch for that system?

 

Also, I'm curious as I haven't seen a dos emulator mentioned anywhere. Has anyone gotten that going? I've been looking for the emulator settings for them but can't seem to find them noted anywhere. Thank you ahead of time!

  • Upvote 1

Share this post


Link to post
Share on other sites

Got Sega figured out.. Just trying to figure out Lynx and Dos... Has anyone looked into this and got it going. If so, what emulator other than retroarch are you using?

Share this post


Link to post
Share on other sites

I can't get MAME to work at all. I hit MAME and it just flashes and goes back to the main screen.

 

I've tried downloading Mame4Droid and using these settings:

rompath=Emulators/MAME/roms/
exe=com.seleuco.mame4droid/com.seleuco.mame4droid.MAME4droid
romextension        = zip
parameters=
 
Then I tried using RetroArch which has the following settings:
rompath=Emulators/MAME/roms/
exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
romextension        = zip
parameters=mame_libretro_android.so
 
I've also tried mame2014_libretro_android.so and the others listed but nothing works. I have been able to get NES working with RetroArch.
 
Using NVIDIA Tegra, any help would be appreciative.
 

Share this post


Link to post
Share on other sites

if you didn't already, double check that directories & names match(settings.ini, rom path, etc).

I don't know if it's just how it pasted, but make sure parameters = is on it's own line, & not on the same line as rom extension

check that your using the correct roms, as well as database that matches (.139) Try the rom in mame4droid. If it works, look in your database to see if your romname matches. If it does, then its a settings issue.

Share this post


Link to post
Share on other sites

if you didn't already, double check that directories & names match(settings.ini, rom path, etc).

I don't know if it's just how it pasted, but make sure parameters = is on it's own line, & not on the same line as rom extension

check that your using the correct roms, as well as database that matches (.139) Try the rom in mame4droid. If it works, look in your database to see if your romname matches. If it does, then its a settings issue.

Yeah I've triple checked directories, everything is the same setup as Nintendo (which works), except MAME. Everything is on its own line as well. Roms work fine if I play them directly through mame4droid. All the rom names have been matched using Don's tools. Still doesn't list any of the roms sadly.

Share this post


Link to post
Share on other sites

Both MAME Reloaded and Retroarch mame cores are working for me.

 

>> I can't get MAME to work at all. I hit MAME and it just flashes and goes back to the main screen.

 

I am assuming 'hit MAME' is you are attempting to launch a MAME rom from your Hyperspin wheel?   And when you say 'back to the main screen', this is the Hyperspin wheel again?

 

>> Still doesn't list any of the roms sadly.

 

What doesn't list?  You have no entries in your Hyperspin wheel?

Do you have any theme or rom_filters enabled?  

Is Hyperspin reporting an error?

Please be more specific about your error condition and what is happening.

Unfortunately, Hyperspin setup is very fragile and it's lacking good error messages.

Many, many things can screw it up (rom filters, rom extensions, rom path, filenames, themes, dbase.xml file).   

 

Earlier versions of MAME reloaded required you to set it's rompath.   I think the newest version works with Hyperspin without this setup (for me).

Share this post


Link to post
Share on other sites

I'm pretty much done or at a stand still right now with my hyperspin setup on my satv. I have the following going with no problems:

Atari2600, MAME, NES, SNES, N64, DS, Gameboy, Gameboy Advance, Gameboy Color, GameCube, Sega Game Gear, Sega Genesis

 

 

I'm having trouble with the last 3 systems I'm trying to get going... I need to know basically everything, which emulator, the path and parameters needed for it to work.

 

Atari Lynx - Just need a working emulator other than retroarch and the path for it... alynx?

DOS emulator - Has anyone gotten one to work? dosbox?
SegaCD - launches emulator and crashes (maybe something to do with the parameter field?)

Share this post


Link to post
Share on other sites

MD.emu

exe=com.explusalpha.MdEmu/com.imagine.BaseActivity

parameters=

I have it so that the emulator launches but it brings me to the menu where I then select load and then the game. Am I missing something?

Thanks

Share this post


Link to post
Share on other sites

 

I can't get MAME to work at all. I hit MAME and it just flashes and goes back to the main screen.

 

I've tried downloading Mame4Droid and using these settings:

rompath=Emulators/MAME/roms/
exe=com.seleuco.mame4droid/com.seleuco.mame4droid.MAME4droid
romextension        = zip
parameters=
 
Then I tried using RetroArch which has the following settings:
rompath=Emulators/MAME/roms/
exe=com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture
romextension        = zip
parameters=mame_libretro_android.so
 
I've also tried mame2014_libretro_android.so and the others listed but nothing works. I have been able to get NES working with RetroArch.
 
Using NVIDIA Tegra, any help would be appreciative.

 

 

Hi, caffeinepills, are you still round here ?

 

Cause I had exactly the same problem as you and I solved it easily by downloading - in my case, via the Google play store on my computer - MAME4droid (0.139u1). Now everything works fine and I can even launch any game I want (previously, when I used MAME 2003 and MAME 2014 from RetroArch, some games would launch on one emulator and not on the other, which was a problem when using Hyperspin).

 

Hopefully this information will help someone else.

Share this post


Link to post
Share on other sites

I have it so that the emulator launches but it brings me to the menu where I then select load and then the game. Am I missing something?

Thanks

 

I successfully set the Genesis / Mega Drive emu on my system. If you need it, I can share my .ini with you. Tell me.

  • Upvote 1

Share this post


Link to post
Share on other sites

I'm pretty much done or at a stand still right now with my hyperspin setup on my satv. I have the following going with no problems:

Atari2600, MAME, NES, SNES, N64, DS, Gameboy, Gameboy Advance, Gameboy Color, GameCube, Sega Game Gear, Sega Genesis

 

I'm having trouble with the last 3 systems I'm trying to get going... I need to know basically everything, which emulator, the path and parameters needed for it to work.

 

Atari Lynx - Just need a working emulator other than retroarch and the path for it... alynx?

DOS emulator - Has anyone gotten one to work? dosbox?

SegaCD - launches emulator and crashes (maybe something to do with the parameter field?)

 

Hi,

 

I have a problem with Atari 2600, 5200 and 7600 games that can't launch on my system : I'm using .bin roms, maybe the problem comes from this ? Would it be possible that you share your ini file with me, please ?

 

At the contrary, I have no problem with the Lynx emulator. Did you solve your problem or can I help you ?

 

 

Now I have to find a way to lauch Mega CD and PC Engine CD games : I didn't even find videos and config files for it, so I can't lauch any game. I have to find a fully working pack or at least to understand how Hyperspin works when you decide to create your own game list.

 

 

 

NOTE TO ALL : for the sake of all Shield users we have to keep this topic alive, so please come and give the most informations you can. To those who only posted one message or two, don't hesitate to come back and share your experience, even when your problem is solved ; this is how a community grows.

Share this post


Link to post
Share on other sites

***NOTE TO ALL : for the sake of all Shield users we have to keep this topic alist ve, so please come and give the most informations you can. To those who only posted one message or two, don't hesitate to come back and share your experience, even when your problem is solved ; this is how a community grows.***

Really??? You should become a platinum member, that is how a community grows!!! If anyone has a problem message me and help you the best I can, but becoming platinum helps the people behind the scenes creating Hyperspin and making it better for everyone!!! Don't just take, give something back!!!

  • Upvote 1

Share this post


Link to post
Share on other sites

Thanks for the information, I didn't know about the Premium accounts. I'll give money to support developers later, they deserve it.

But I'm sorry I have to tell you that your answer to my message is irrelevant. I talked about the community, about the fact that users should share their experience, give informations to other ones and not just expect to get answers to their questions and never come back in this forum. I never meant to ask people fund the development of Hyperspin, even if your intention is good that's another topic : we could give as much money possible, it won't help up set Hyperspin correctly on our Android devices, only its community will help ! ;)

Share this post


Link to post
Share on other sites

I understand what you mean about an active community. Most of the questions with setting up are answered elsewhere on the forums, since this topic only deals with the port to Android. (It's assumed that you already have it working on the pc)

With a platinum account, you have unlimited access to artwork and themes, plus other interesting stuff on the ftp, as well as hypersync which will automatically sync & rename the files to match your roms. Videos can be found at emumovies.com. Again, a subscription allows you faster downloads and use of their syncing utility. Most will agree that a subscription will save you a LOT of time, but is not necessary.

If you want an Android front-end with minimal setup there is arc browser and gamesome.

I've been very busy, but I'll try to help the best I can.

Share this post


Link to post
Share on other sites

Anyone know if this will work for C64.emu:

 

exe=com.explusalpha.C64Emu/com.imagine.BaseActivity   ????

 

And for GBA.emu:

 

exe=com.explusalpha.GBAEmu/com.imagine.BaseActivity  ????

Share this post


Link to post
Share on other sites

Anyone know if this will work for C64.emu:

 

exe=com.explusalpha.C64Emu/com.imagine.BaseActivity   ????

 

And for GBA.emu:

 

exe=com.explusalpha.GBAEmu/com.imagine.BaseActivity  ????

 

Yes, I use :

 

 exe=com.explusalpha.C64Emu/com.imagine.BaseActivity

romextension=T64,D64
parameters=
 
and this should work too
 
exe=com.explusalpha.GbaEmu

Share this post


Link to post
Share on other sites

Just updated my settings files and will go test everything and report back.  The mame emu for Android TV I believe is for version 1.39.  Do you have to have a romset for that version or would a newer set work?  I've got mine filtered to the 500 or so games I want and didn't want to have to start over if possible. That will take many hours.

  • Upvote 1

Share this post


Link to post
Share on other sites

If your romset doesn't match, it's likely that some games (or many games) won't work.   See my other response on this topic.

 

The main reason I like Retroarch is that once you have it setup, it provides a uniform experience across all systems/wheels.

It's a little confusing at first since input aspects are a little abstracted but it's more powerful too.   For Hyperspin, I bind a button to exit Retroarch and return directly to Hyperspin.  It's pretty sweet.

 

Retroarch continues to improve and expand as well.   Dreamcast is coming soon.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Honosuseri
      Right guys as some of you are aware Google changed how things work on the Google Play Store a while back, when we install an app it will use the 32 or 64 bit version depending on what's native to the device. As we're mainly focused on the Shield TV here on the Android part of the forum, it is a 64 bit device. This has proved to be a bit of an issue for those of us who love Retroarch as there are some serious differences between the 32bit and 64bit versions. In a nutshell currently we have access to more cores for us to play our retro systems on the 32 bit version. RetroArch provide a RetroArch_ra32.apk which is a dedicated 32bit version we can sideload/install and use, however Hyperspin is NOT setup to use this version as some of the paths changed.

      So...I decompiled the Hyperspin.apk and made the necessary changes (yes including the config path) to solely use RA_32. I've done some limited testing with RA_32 (1.8.7) and it seems a okay to me (even the Daphne test core works) however I don't use screen overlays or really bother with alternate config setups (in truth I've not used the STV in many months!). Feel free to download it and test yourselves, obviously backup your essential files AND do remember the .ini files need to be adjusted to use RA32....

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

      It's easy enough to open all your .ini files with notepad++. Use the Search and replace feature to find com.retroarch/ and replace to com.retroarch.ra32/ do this for all opened files then save all.

      Those who use adopted storage it's wise to move the Retroarch_ra32 app to internal storage after installing AND before running it for the first time. Let me know how it works for you, I'll do a Youtube video to help those less experienced with setting up Hyperspin when I know it's working 100% and I have the free time.

      Mega Link for Hyperspin_0.1.8_Hono.apk (https://mega.nz/file/zQNBCYKI#QVrG4uVVmvXHshl8LbosQi7LAjQmUA09R5k_YqhcMBI)
      RetroArch_ra32 (1.8.7) newest stable version at time of posting (http://buildbot.libretro.com/stable/1.8.7/android/)
    • By Wandurlust
      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.
    • 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
       
       
×
×
  • Create New...