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

Archived

This topic is now archived and is closed to further replies.

thatman84

(WIP Tutorial) Commodore Amiga on Shield TV

Recommended Posts

This is the start of the WIP guide and Amiga Project thread

DONT REPLY TO THIS THREAD

REPLY TO THIS ONE(clicky)

 

For now this will become a tempory guide to UAE4arm setup with the Ultimate Amiga Raspberry Pi Project a helpful source of information in google

Step 1 - Install Uae4arm (beta)

You need to follow this link to sign up to be a beta tester to gain access to the apk that can launch games directly from Hyperspin.

https://play.google.com/apps/testing/atua.anddev.uae4arm

Link above taken from the English Amiga Board and the post below

http://eab.abime.net/showpost.php?p=1158186&postcount=349

 

Step 2 - Install Kickstarts

WIP

 

Database taken from this thread post

 

More to follow

 

Amiberry Android progress threads

https://github.com/midwan/amiberry/issues/206

https://github.com/midwan/amiberry/issues/241

Share this post


Link to post
Share on other sites

Lools like cash may get the Amiberry emulator over to android. Theres a poll on the Amiberry facebook page.

The dev is struggling with the complications of building cross platform and a software upgrade will help the effort.

Im in anyone else???

Screenshot_20181207-085532_Facebook.jpg

Share this post


Link to post
Share on other sites

No! Purely based on how they've been misleading on Android development to date. 

I have no issue paying devs for their time, providing they actively support and do develop the software. 

If (and it's a big IF) Amiberry is ported to Android and it is a noticeable improvement over Uae4arm, I'll use it. In fact I would even pay for it. 

Android users have access to the Google reward scheme. Answering surveys give us credit to spend on the play store. It's a great way for us to support devs, without us spending our own money. 

Share this post


Link to post
Share on other sites
4 hours ago, Honosuseri said:

Android users have access to the Google reward scheme. Answering surveys give us credit to spend on the play store. It's a great way for us to support devs, without us spending our own money. 

I should do some of that. Always gloss over these money saving ideas.

 I dont really think Midwan done much wrong. He did say he would have something in 6mths but seemed he didnt fully understand the challenges. Now he does he is bringing a solution forward. I would rather help push it forward however I can...uae4arm is seeing very minor developments and amiberry seems very actively developed.

Not gonna wait around though, uae4arm is the focus until something better comes along

Share this post


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

I dont really think Midwan done much wrong. He did say he would have something in 6mths but seemed he didnt fully understand the challenges. Now he does he is bringing a solution forward. I would rather help push it forward however I can...uae4arm is seeing very minor developments and amiberry seems very actively developed

No! He said he'd compiled the emulator in android studio which was a lie. He finally admitted it was the "Hello world" simple program instead. In essence they're learning how to develop on Android.

I remember this all too well because I wasted time trying to compile it because of what they said, when it was never going to work! 

It's in their own interest to Port it to Android. There are faaaar more android users than Raspberry Pi owners. Providing they don't price it stupidly people will pay for it. Doesn't take long to save up a couple of quid with Google rewards. The Amiga kickstarts are £1.79 iirc

I wish them luck with it BUT I'll believe it when I see it. They only have themselves to blame for that

Share this post


Link to post
Share on other sites
23 minutes ago, Honosuseri said:

No! He said he'd compiled the emulator in android studio which was a lie.

Ah I get ya now. Fair point

 

Im a forgiver anyway, but yes will believe it when I see it also.

Share this post


Link to post
Share on other sites

Updated OP with links to Amiberry github issues relating tho android. For background info

 

Share this post


Link to post
Share on other sites

  • 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.8) newest stable version at time of posting (http://buildbot.libretro.com/stable/1.8.8/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
       
×
×
  • Create New...