reznnate

I'm actively working on broad compatibility. I just bought an Ayn Odin for testing. When this app was written 10yrs ago, the mobile gpu driver situation was _terrible_. Things are much, much better now but still very complicated due to the large number of products and different drivers shipping out of China. My renderer is relatively basic and I've shifted some of the 'hardware acceleration' complexity onto the (faster) cpus. It probably won't work everywhere but some of the Shield dependencies are unnecessary now. I should have a test build ready in a week or two.

mrfomt found that the order of the rom extension mattered (and is a bug). He moved his extension (gcm) to the front and dolphin worked. I need to look into ps2 emus next.

Yeah, obviously at this point the Shield is too old for it to be relevant. But I still love Hyperspin and wanted this for myself.

Posted beta5. Added a bunch of features intended to help make setup and emulator changes easier. There is a lot going on so I added a brief doc intended to help explain a bit of it. Comment here if things don't work the way you'd expect, you run into bugs, or if you'd like clarification on anything.

Hyperspin-beta5.apk View File Lots of new features intended to help with setup and switching emulators Submitter reznnate Submitted 04/15/2026 Category HyperSpin (Android) File Count Credits  

I don't like how your sonic wheel images are squished and wondering if I could handle that scenario better. Most wheels have wide rectangular images. Do they have a proper aspect ratio on Windows? Are there other wheel designs that suffer like this?

Did this previously work in prior builds? Do other non-.gcz formats work? In the Nintendo Gamecube .ini file, is gcz listed as a valid rom format? I'm actually revamping a lot of this code right now although SOME of these issues tend to be emulator-related so this feedback is useful right now. I ran into issues with both saturn.emu (his other .emu apps work fine, I use c64.emu) and a 'newer' hacked version of Drastic (DraStic_r2.5.2.2a.apk works).

Awesome feedback, thanks. I've been out of the scene for a long while. The Shield is 10yrs too-old at this point but for most of the older systems I care about, it's still kicking. Shield won't be able to handle newer emulators/systems but as ARM-based hardware gets more powerful, I will update the Hyperspin app for myself, if nothing else... I've added a few useful features so I'll be posting another update this week.

Other than Retroarch, what are the most important emulators still being updated and maintained for Android? With all the new Android handhelds, I expected the scene to be vibrant but the play store has become a wasteland of sorts. I don't intend to post my app there either. I'm working on some fixes, new features, and will have another update relatively soon.

Okay, I've posted beta4. I overhauled the app so hopefully it works okay as a drop-in replacement. I've done a lot of testing but let me know if you have questions or run into issues with it. Next, I'm going to see if I can simplify emulator setup.

Hyperspin-beta4.apk View File Added additional Flash rendering capability. Now includes a fast .swf renderer and a slower engine with greater accuracy and compatibility. Other new features include Attract mode, 4:3 rendering on wide display, 7 new wheel designs, wheel animations, additional Hyperspin animations, .particles, and 4xMSAA rounded borders. Also, tons of bug fixes and performance optimizations. Submitter reznnate Submitted 04/06/2026 Category HyperSpin (Android) File Count Credits Reznnate  

I'm not aware of any emulator launcher issues. The current system (using .ini files) is NOT convenient (and I do intend to improve this), but it does allow the flexibility to support any (one) emulator (per wheel).

Back in the day, the NVIDIA shield was my hardware of choice. The Hyperspin app is being updated soon and it's pretty great now. If you can find a cheap used Shield TV (pro, not the tube), it's still pretty good (I still use mine) with HDMI/LCD panel. REALLY hard to pay for a new one now that it's 10yrs old. For my older CRT-cabinet, I need Windows.

Still rock'in the TV version. Also have a prototype handheld that never shipped. HUGE update to app incoming. It will run better if NVIDIA ever releases a new Shield. Shield is 10yrs old!

WHY!?!? It's been nearly 11 years!?!? Well, I fell back in love with Hyperspin and decided to update the app. I uploaded a quick 'attract' test to see if I'm the only one left here but a few people downloaded and that's enough for me, particularly for an 11 year old Android device. Anyway, the update is coming along well and it's turned into a significant app overhaul/rewrite. I'm quite proud of it. There are a few remaining things to fix and then I should be able to post next month.

HyperspinFE-beta3.apk View File I've always wanted an attract mode and finally got around to it. Updated to latest Android SDK as well. Add or edit these lines in Settings.ini [AttractMode] Active=true Time=120 ;seconds delay before spinning MaxSpinTime=10 ;max seconds it will spin to next theme MaxTopSpeed=0.05 ;seconds between fast-speed wheel steps (increase for slow storage) HyperSpin=true ;ignored on Android Wait_For_Video=true ;ignored on Android Submitter reznnate Submitted 02/14/2026 Category HyperSpin (Android) File Count 1 Credits Reznnate  

HyperspinFE_AndroidR_arm64_beta2.apk View File Latest beta fix for Android R Still need an update/fix for new launcher method used by a few emulators Submitter reznnate Submitted 07/20/2023 Category HyperSpin (Android) File Count 1 Credits Reznnate  

I wish the retroarch MAME core was better on Shield, but it's buggy... Am working on SAF support but it will be a few weeks (I think) for an update. I'll post the new beta here when it's ready.

Thanks for the info guys. I do think there is a needed feature in Hyperspin related to SAF URL or whatever. Looking into it...

@pmindemann Yep, arcade is important for me too but mamereloaded is getting a bit old for me so I've been using Retroarch cores. I've been out of the loop for a few years and am not familiar with the current state of Google's constantly changing OS. It looks like Arc Browser has been keeping up with the launching parameters (and it was able to launch Mamereloaded for me). I don't know why it's not working in Hyperspin. I could use some help determining the correct intents and parameters. I'm not sure what else is wrong.

@pmindemann I'm not sure what's wrong with mamereloaded. I was able to get it working standalone but it's not launching from Hyperspin for me either.

Here is an updated beta to test. It fixes all of the known regressions I could find and the crash and performance issues reported so far. HyperspinFE_AndroidR_arm64_beta2.apk