Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Announcement

    Sorry for the recent downtime. Still much to do but we have the site updated, secure and back online.  Expect more changes.

Honosuseri

User
  • Posts

    843
  • Joined

  • Last visited

  • Days Won

    4

Honosuseri last won the day on August 16 2019

Honosuseri had the most liked content!

4 Followers

About Honosuseri

  • Birthday 08/14/1980

Profile Information

  • Location
    UK

Converted

  • Location
    UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Honosuseri's Achievements

Rookie

Rookie (2/14)

  • Dedicated Rare
  • Very Popular Rare
  • First Post Rare
  • Collaborator Rare
  • Posting Machine Rare

Recent Badges

336

Reputation

  1. No, you clearly misunderstood the situation by saying just don't update RA. Hyperspin on PC and Android are two very different animals. When M$ does a Windows update which messes up Hyperspin, I'm confident it'll be fixed as that's happened many times. On Android I'm not as confident but hope for the best, the fact Launchbox has abandoned their Android version should tell you enough to be concerned. It's sound advice to warn new users about the changes to Android and the knock on effect it will have on HS with the STV. Arc Browser is a superior frontend with better features, being actively developed AND it's also compatible with phones/tablets when HS is not. When the Android OS changes kick in on the STV and HS is known to be working, I'll recommend HS "for show" and help people set it up. Until that day comes, I agree with Hyperseeder and new users should wait before sinking in a lot of time learning and setting up Android Hyperspin. I have a very nice Hyperspin PC setup, people are perfectly "safe" sinking time into that, many of the assets can then be shared with an Android setup later.
  2. Worst case scenario is that when the STV is updated to Android 11 or 12 that Hyperspin won't work, it's not about RetroArch but the changes Google is making to the OS. Perfectly valid post for him to make, I'd be livid if as a new user I sunk in a lot of time setting up HS for it just to stop working out of the blue. I help people with HS plenty BUT still recommend Arc Browser as it is a better frontend being actively developed. I've used HS on the STV for what 5 years, there's a suggested features thread here on the forum BUT nothing new has been added. I hope that HS will be updated when the Android OS changes kick in BUT I can't say for sure that it will be.
  3. To my knowledge it's @reznnate who we have to thank for the Android version of HS. I believe he created it originally for the Shield Portable device. I seem to recall the official HS app was updated, when it stopped working because of previous Android changes many moons ago. Of course I can't speak for future development. I applaud your efforts on modding and maintaining your version of the APK. I modded it solely for RA32 as IMHO adding the 64bit version of RA for it's limited benefits were not worth my time. I was aware of these Android changes coming, the dev for LaunchBox has stated they've stopped development of their Android version iirc. I hope FreeLancer will continue on with Arc Browser. All the best, I'm sure many people are thankful for your efforts
  4. I have very little interest in emulation on Android now, so it's been a very long time since I touched the STV, RA & HS. I can tell you that it used to install by default to shared storage and the RA paths were different to when on internal storage. So I had to go into apps select RA and move it before running it, once run RA set the paths automatically. If you use adopted storage and everything works with your HS build then that's awesome, nothing to worry about. I only mentioned it as people use different setups, some just have HS and "roms" on an external drive with others using adopted storage...maybe both.
  5. @reznnate is the guy who did the original build to have HS on his Nvidia Shield Portable. Not sure if he published it to Google Play BUT he's the guy we are all really thankful to. Congrats on your project, sadly I don't really have the time to test it out. Those who use adopted storage might need to install RetroArch and then immediately move it to internal storage before running, worth testing that out to prevent people saying your build doesn't work.
  6. Honestly I have very little interest in Emulation on Android these days. If anything it was more for my phone to be able to play decent games out and about (not that we can do that now with the current global situation). I'm more known for Amiga emulation here and have been chipping away at the missing Amiga media (videos, disks & boxart etc.) for a while now, with what little free time I have. Most of the emulation I've done lately is in PCVR with EMUVR and New Retro Arcade: Neon. My Youtube channel also takes up much of the free time I do have. So no I'm not looking to start any other projects, I wish you all the best with the Hyperspin modification.
  7. As I said NOT ALL apps have launch intent implemented. Best thing to do is message the developer and ask for them to add the feature. I did this a looong time ago for Redream (Sega Dreamcast) and tested the APK before it was released on the Playstore. Arc Browser has no profile for Duckstation standalone, only the RetroArch core. Freelancer adds profile updates for us to use for popular emulators, of course it's possible he's not done the profile yet BUT from what you've said it sounds like launch intent isn't being used in DS.
  8. Try "org.devmiyax.yabasanshioro2/org.uoyabause.android.Yabause", that's for the free version not Pro though. I'm not paying the developer again when the old version could have been restored on Google Play, if he wanted it to be. Remember not all apps will work with launch intent which is how frontends load them. Download QuickShortcutMaker from the Playstore to your phone and install the app you want to know the settings for and it will list the activity names.
  9. No worries. With the recent forced changes to Retroarch breaking compatibility with Hyperspin, using Arc Browser which is actively developed makes even more sense now
  10. My honest advice would be to purchase Arc Browser on the Google Play store and use that. It's actively developed and being constantly improved upon and sadly Hyperspin isn't. I actually have both configured on my STV. That single purchase can be shared with your family account and/or used on your Android phone, so although it costs money you can get quite a lot of use out of it. Arc Browser has ready made system presets and can scrape artwork online for the games. It integrates with the voice search which is a nice feature, you can say "Sonic" and all the Sonic games from all the systems you've added to AB's library will show. It now supports video previews, you can add favourite games (Hyperspin doesn't do that), choose to use Retroarch 32 or 64 bit versions for separate systems...I could go on and on. In short it'll make your life easier and is honestly a better frontend. Hyperspin will have to be configured manually through the ini files in the "settings_android" folder. Yes the Hyperspin themes do look more flash than Arc Browser BUT many of them use swf in the zip files, so aren't compatible on Android (trust me I know, having tested and fixed soooo many of them for my STV). It's definitely worth the time doing Hyperspin and Rocketlauncher on PC, as you can do many more systems than on Android. It's your decision of course but hopefully some advice from an experienced retro gamer (i.e me) helps.
  11. "There is so much more and beckons me. To look through to these, infinite possibilities..."

    Wishing you all a very happy new year!

  12. "There is so much more and beckons me. To look through to these, infinite possibilities."

×
×
  • Create New...