@GiraffeMan3125 Yeah, so my cores don’t seem to be compatible, which is strange since I compile them with iOS 5 support minimum…
If it’s a permissions problem, you could try to change the cores folder’s permissions or core permissions themselves to mobile:mobile or root:mobile or root:wheel…
If it’s not the permissions, you may try the official buildbot: http://buildbot.libretro.com/nightly/apple/ios/latest/
I have no idea how to change the permissions, and for some reason, when I close the app, all my settings get reset. (including the Cores URL)
@GiraffeMan3125 Ok, you could try the official buildbot anyway…
For settings, you now need to save them manually in the Configuration File option, in the main menu…
I switched over to the official buildbot (and saved my settings), downloaded a new core, but that new core still crashes.
Ok, I wish I still had an iOS 5 device to figure it out, but I think I’ll just have to remove the iOS 5 RetroArch I put on my website…
@GiraffeMan3125 I just thought about this, but you may very well HAVE to jailbreak for RetroArch to work, I just put an iOS 5 RetroArch version on the Cydia repo for you to try, if you are willing to…
Here is all you need:
Then you could delete the ipa version and install my iOS 5 version directly from Cydia after adding my Cydia repo ([iOS/tvOS] — RetroArch 1.9.0 and other emulators (Download/Cydia repo))…
I was already jailbroken when I tried this but I’ll try your repo.
It still crashes, and now when I switch the Cores URL, it says no Cores were found.
@GiraffeMan3125 You can stay with my buildbot which is more complete, can you try a simple core like 2048?
Hi! I have the same problem that GiraffeMan. I tried with 2048 core but it doesn’t work for me. The app crashed!
I’m having the same exact issue.
@GiraffeMan3125 @Emiliapol81 Can you try 2048 again from my iOS repo?
I compiled many other cores too! (On an older version of OSX, with an older developer SDK…) We have some chances they will work on iOS 5!
I tested the core 2048 with the ipa from this thread and also with the repo version. But neither of them worked. The application closes unexpectedly, with 2048 and with any other core.
@Emiliapol81 Ok, it may be RetroArch itself then…
@GiraffeMan3125 @Emiliapol81 Could you try updating RetroArch itself now? I made some changes to it, let’s hope this works now…
@Weedy_Weed_Smoker thank you very much for your help. I installed the new update from cydia and it worked perfect. So far I have tried the 2048 core and some nes and snes roms and I had no problems!
At the moment the problem I have is that I cannot run n64 roms. The app crashes after loading the content. Can you help me with that?
I just tested it, and the new version works for me too.
Thank you very much for compiling for iOS 5. This allowed me to dust off the iPad1Gen and run PS1 games on it, which to my surprise run at full speed! 
But there is a small problem:
The ReARMed core freezes spontaneously in some games and does not allow the application to be minimized - have to do a hard hardware reboot, the process simply not respond to SSH terminal commands. It also freezes when trying to load a game from a snapshot of the emulator. At the same time, on a PC, all these games work without problems on the this core.
I also tested Snes9x, PicoDrive, FBNeo - they work great and saved (if incompatibility with rom occurs ios does not die)
@dagazik That may very well be because of the extremely small amount of RAM available on the first iPad (only 256MB!), which has to be shared between the system and apps…
I think the apps can use virtual memory up to 4GB on 32-bit devices, but you may not have enough space left on the device for that to happen efficiently, and I’m not even sure if iOS 5 allocates virtual memory… There might be a tweak that allows you to use virtual memory on early iOS but I don’t quite remember…
I also thought about RAM first and connected via “PuTTY” ssh by running “top” - the RetroArch with ReARMed and game takes 90 MB RAM in peak and about 60 MB more free! In addition, if there is a lack of memory, then in normal mode the system forcibly closes the process.
Here are some examples of why this is NOT RAM:
Demo in YouTube: https://www.youtube.com/watch?v=W3yJ9tax5-8 The video showed how it freezes at the moment of loading the save, but game can also freeze in any other place.
Metal Slug 5 on the FBNeo(NeoGeo) core occupying 140MB works without problems.
The core of the Beetle PSX runs good but is slow.
Problem is not in the save (this is an additional bug that I identified, but i can also use the memory card). The problem is that on the ReARMed core the games freeze in those places where they work on the PC version RetroArch/ReARMed, and also that the hang kills the entire system before a hard reboot.
