Jump to content
reznnate

SETTINGS: Android emulator settings

Recommended Posts

FYI... that version hasn't been updated since 2014.  The more up to date version is on Paulscode.com which is 3.a.0.  Also I wouldn't recommend the FZ version on shieldtv as there is some serious audio lag using either audio driver.  Just try Mario64 and jump... there is a significant lag from when mario hits the ground to when you hear the sound.  Paulscode's latest in my opinion runs best but Glupen64 on retroarch is getting better everyday using the latest GlideN64 video drivers.

 

I went to his site, and all I saw listed is 2.4.4... Not sure where you saw 3.

Share this post


Link to post
Share on other sites

The auto builds. It doesn't list the version on the site but once you install it the version is 3.a.0. This is also discussed in the forums.

But again who even cares about version numbers. Android play store tracks the date as well. The last time it was updated on the play store was 2014. These latest versions on Paul's code are from 2016.

Share this post


Link to post
Share on other sites
9 minutes ago, raygst said:

Whats the parameters= for the dreamcast?

Does the one in the 1st post under reicast not work for you?

Share this post


Link to post
Share on other sites

I got it to work but every-time I try and exit the dream-cast emulator it keeps starting back up on a loop

Share this post


Link to post
Share on other sites

I had that problem you need a different build.

in the android base pack in my signature there is a setup notes txt file that has the builds I used. Needs a mouse if  it doesn't recognise the shield mouse if your using shield. Mouse Just for setup though

Share this post


Link to post
Share on other sites
1 hour ago, raygst said:

whats the setting to run Neo Geo in neo.emu? 

 

plzzz help

Don't know but go on play store and get shortcut maker. Then create shortcut with the app and use those parameters.  Easy to use

Share this post


Link to post
Share on other sites

Can u sent me the link because I can't find anything by that name in the play store

Share this post


Link to post
Share on other sites

its called quickshortcutmaker

https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut&hl=en_GB

You need to get the APK and sideload it onto the Shield

I get mine by using my Nexus tablet and an APK extractor. Then just copy the APK over to the shield and run it to install.

Its because it is not tagged as Android TV compatible so you cant find it on the Play STore from the Shield.

You can get Sideload Launcher on the Shield play store and that organises your side loaded apps to you can get to them from the home screen via sideload launcher.

This is an old copy of the quickshortcut maker if you dont have a way to get it from playstore

com.sika524.android.quickshortcut.apk

Share this post


Link to post
Share on other sites

Hi guys,

Has anyone founded the parameters for the nostalgia.gg emulator?

exe=com.nostalgiaemulators.ggfull/com.nostalgiaemulators.gg.GGGalleryActivity
parameters=????
romextension=gg

When I select the rom, I'm redirected to the emulator main page.

Thanks

 

Share this post


Link to post
Share on other sites
On 07/04/2017 at 11:10 AM, siulprime said:

Hi guys,

Has anyone founded the parameters for the nostalgia.gg emulator?

exe=com.nostalgiaemulators.ggfull/com.nostalgiaemulators.gg.GGGalleryActivity
parameters=????
romextension=gg

When I select the rom, I'm redirected to the emulator main page.

Thanks

 

Salut, tu tiens absolument a utiliser cet émulateur ?

Moi j'utilise le core Genesis Plus gx sur retroarch pour lancer les jeux game gear en direct depuis hyperspin.

Share this post


Link to post
Share on other sites

I had an issue with PPSSPP Gold recently. Not sure what changed but didnt play PSP for a monh or 2 and it stopped launching (invalid emulator)

The new exe line im using is 

 exe=org.ppsspp.ppssppgold/org.ppsspp.ppsspp.PpssppActivity

NO parameters

The 2nd "gold" has been removed from the exe command in the OP

@reznnate maybe you could edit 1st post idk my exe line needs confirming

Share this post


Link to post
Share on other sites
On 5/16/2017 at 3:13 PM, thatman84 said:

I had an issue with PPSSPP Gold recently. 

The new exe line im using is 

 exe=org.ppsspp.ppssppgold/org.ppsspp.ppsspp.PpssppActivity

@reznnate maybe you could edit 1st post idk my exe line needs confirming

Will do

Share this post


Link to post
Share on other sites

Hi all, 

Seem to be having an issue with Dolphin-emu and gamecube, on Shield TV (8)

The emulator is installed fine from the app store and runs games fine

the ini as per the main page but I get "warning - Attempting to launch invalid emulator(s):org.dolphinemu.dolphinemu/org.dolphinemu.dolphinemu.activities.MainActivity"

 

 

 

Share this post


Link to post
Share on other sites

Did you get the debug app maybe?

exe=org.dolphinemu.dolphinemu.debug/org.dolphinemu.ui.main.MainActivity

I have not updated for months so not sure if anything changed

Share this post


Link to post
Share on other sites

I tried the current play store version and the latest version from the site (5.0-8474)

Out of interest what version are you using and I will try it?

Share this post


Link to post
Share on other sites

@ciscosurplus lets move the convo back here from the Shield Experience thread :) its better placed

I am running old 5.0 5566

There may have been a change to the launch command

Screenshot_20180719-211323.png

Share this post


Link to post
Share on other sites
22 minutes ago, thatman84 said:

@ciscosurplus lets move the convo back here from the Shield Experience thread :) its better placed

I am running old 5.0 5566

There may have been a change to the launch command

 

I just downloaded and sideloaded the version above (5566) and get the same error

I also tried with .debug and .free and no dice. 

the package name is "org.dolphinemu.dolphinemu" according to ES FE.

Will try again tomorrow.  

Edited by ciscosurplus
pressed go to quick!

Share this post


Link to post
Share on other sites

Thanks to @ Honosuseri for sharing his settings. 

The first post needs amending to include

exe=org.dolphinemu.dolphinemu/org.dolphinemu.ui.main.MainActivity (no ui on the first post) 

most of the downloads don't include this either. 

I also noticed the play store version does seem to have a .free in it, I haven't tested this version with a new exe yet and will try to tomorrow and report back

 

 

 

  • Like 1

Share this post


Link to post
Share on other sites
9 hours ago, ciscosurplus said:

Thanks to @ Honosuseri for sharing his settings. 

The first post needs amending to include

exe=org.dolphinemu.dolphinemu/org.dolphinemu.ui.main.MainActivity (no ui on the first post) 

most of the downloads don't include this either. 

I also noticed the play store version does seem to have a .free in it, I haven't tested this version with a new exe yet and will try to tomorrow and report back

 

 

 

Let me know how the testing goes.

I can amend the OP unless @reznnate has any additional info to add.

 

Share this post


Link to post
Share on other sites

Sometimes things change with updates....I noticed this when I was testing the scummvm apk...I had like 4 different versions and each one had a different launch parameter

  • Like 1

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...