Jump to content

reznnate

Moderator
 View Profile  See their activity

  • Posts

    632

  • Joined

  • Last visited

  • Days Won

    6

 Content Type 

Everything posted by reznnate

  1. reznnate
    Bug with seeking to letters on the wheel is fixed. Was related to arm32->arm64 bug. Fixed! Bug with slower than expected video playback was due to arm64 config with ffmpeg library. Fixed!
  2. reznnate
    I connected my NAS today and confirmed the new Google/Shield OS version broke the ability for Hyperspin to scan the /storage folder for new paths and hyperspin folders. The fix for USB was to scan device IDs and then build the search path from that. The fix for NAS storage will involve adding the ability to specify the path directly in settings.ini.
  3. reznnate
    I've only been using external USB drives for testing external storage. It is possible YET ANOTHER regression happened with NAS drives and 9.x firmware. I'll look into it... @pmindemann do you have your data folder setup? This hyperspin .apk is only a player. It doesn't offer auto-download of media, themes, etc.
  4. reznnate
    I've been testing as well and have found issues with launching a few standalone emulators -- c64.emu, Redream, and PPSSPP. PPSSPP launches but won't load game. I've also been testing arm64 Retroarch cores and these don't seem to work (for me): freeintv, snesx, flycast, and mupen64plus_next_gles3. I've hit a crash issue with a Cave theme that worked previously. It uses a background.swf causing a crash (and may be raising a 64b issue).
  5. reznnate
    Let me know if you find something in hyperspin changed (possible, but less likely) or if it's related to .ini or those emulators behaving differently. For example, I've noticed emulators that haven't been updated cannot properly browse external media. Be sure the emulators have permissions giving them access to external storage (in Android TV settings->apps->permissions) In summary.... some of the key changes made for this build of Hyperspin include: 1. both 32b and 64b binaries... meaning that new 64b libraries (ffmpeg) are used as well (on Shield TV pro). 2. updated Android sdk version and life-cycle that addresses launch/return behavior and changes to external storage behavior and permissions 3. a few bug fixes
  6. reznnate
    Let me know if you find issues. As stated above, most issues I'm hitting involve Android's update and impact to emulators and external storage access/permissions, etc.
  7. reznnate
    Okay, I'm going to attach a test build here for the sake of quick feedback. LOTS of things have changed under the hood (including an arm64 binary) so let me know if you run into problems. Almost all the issues I've been hitting (while testing at this point) are related to emulator behavior, issues with my old config/.ini files, etc. Also, this build includes the change suggested by Hyperseeder for better support of the different Retroarch versions. -Reznnate Hyperspin-test-July22.apk
  8. reznnate
    I've been out of the scene for awhile and was wondering if new issues or emulator launch problems have cropped up. Are there patches or workarounds to consider?
  9. reznnate
    I had nearly given up due to the number of Android OS and SDK changes. Fortunately things are moving forward again and an update is looking likely.... soon too. Sorry it's taken so long.
  10. reznnate
    Sorry the app was broken. I'm working on a quick update to fix compatibility. It's been years since I've looked at this so I'm running into various build/env issues and I don't have an ETA. It should be easy but I've already spent more hours than I expected. I'm expecting an update in 2-3 weeks, but that's not a promise since I'm uncertain about the fixes required yet. While I'm at it, I intend to fix the issue raised with Retroarch as well. Cheers!
  11. reznnate
    Will do
  12. reznnate
    Hyperspin_Android-test.apk View File Before I post this to the Google Play store, I wanted to let you guys test it first. There are only 2 minor changes. 1. Properly sleeps in the background when an emulator is launched (this should help battery and potential lag) 2. Changed default path for retroarch.cfg to /storage/emulated/0/Android/data/com.retroarch/files/retroarch.cfg (was previously /data/data/com.retroarch/retroarch.cfg). This should unify the config files (when retroarch launched standalone) and make it R/W. Pointing to /data/data was a hspin app bug. SORRY! Submitter reznnate Submitted 07/07/2017 Category HyperSpin (Android) File Count Credits  
  13. reznnate
    More information about "Hyperspin_Android-test.apk"

    Version 1.0.8

    2,059 downloads

    Before I post this to the Google Play store, I wanted to let you guys test it first. There are only 2 minor changes. 1. Properly sleeps in the background when an emulator is launched (this should help battery and potential lag) 2. Changed default path for retroarch.cfg to /storage/emulated/0/Android/data/com.retroarch/files/retroarch.cfg (was previously /data/data/com.retroarch/retroarch.cfg). This should unify the config files (when retroarch launched standalone) and make it R/W. Pointing to /data/data was a hspin app bug. SORRY!
  14. reznnate
  15. reznnate

    Version 1.0

    2,595 downloads

    A few modifications were required to make it work smoothly on Android. These changes don't affect the PC functionality so it should work well on both Windows and Android. -- added new 'Main Menu_Android.xml' to remove MUGEN and OpenBOR wheels. No emulators have been ported yet. -- added Settings_Android folder -- fix -- added transition video to media/frontend, Hyperspin on Android needs this -- fix -- added English exit images to media/frontend -- fix -- replace 0-length SpecialA4.swf file (caused Android Hyperspin to crash)
  16. reznnate
    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.
  17. reznnate
    Yes, I use : exe=com.explusalpha.C64Emu/com.imagine.BaseActivity romextension=T64,D64 parameters= and this should work too exe=com.explusalpha.GbaEmu
  18. reznnate
    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).
  19. reznnate
    I do not -- likely needs a secondary rom parameter for param=. I suggest asking the developer.
  20. reznnate
    Indeed, my guess is you have a typo in the rompath, the .xml dbase entry doesn't match your rom file(s), OR the file extension is wrong (.zip, .7z, etc.)
  21. reznnate
    Updated initial post, thanks!!!
  22. reznnate
    Dolphin setup video on Shield TV --
  23. reznnate
    This should work according to the developer. I'd consider sending him an email, he's been very responsive to me.
  24. reznnate
    It's not you. But even the latest working builds are BARELY playable anyway. The Android build is undergoing substantial change and upgrade. Focus is on 64bit CPU support and an optimized OpenGL backend. Things are a mess right now but I'll start looking for new builds in 2-4 more weeks. You'll need an ARM system with 64b CPU and OpenGL4 support.
  25. reznnate
    exe=paulscode.android.mupen64plusae/paulscode.android.mupen64plusae.MainActivity
×
×
  • Create New...