RetroArch Android releases (v1.0.0.2)

This is an incredible emulator!

i’m just having some issues with Samsung Galaxy Nexus 4.1.1:

There’s a random lag (not only sound) on all consoles. I’m playing and no more than 10 seconds the game slow down for 1 or 2 seconds. Something like bullet time. This issue occured at RetroARch first version, but was solved until R6 version. Now, R8 it come back again.

I think RetroArch needs an option “Force High Priority” or something. Maybe other apps (multitasking) are doing this issue. :-/

BTW, Thanks developers for such a great app!

A user reported that you will have no lag at all if you use Android 4.1 with TV-out as opposed to earlier versions.

Frameskip is not really a solution for attaining ‘smooth gameplay’ on TV-Out IMHO.

Maybe HDMI-OUT work with “no lag”, but i dont have it. I have only composite 3,5 mm jack out on board with PAL/NTSC support via special apk tool.
To my regret ICS Firmware for JXD-S601 is not provided by the manufacturer. Only custom firmware with lots of bugs and without TV-OUT, and the kernel is lock at 600 MHz only vs. Gigerbread 800-1000 MHz firmware kernel.

On the device all emu works fine, but when I connect him to tv = “bullet time” effect in the any 2D emulators and RetroArch PSX too. Helps only manual frameskip = 1 in NTSC mode.

Thanks bl@ck_m@ge…

Ill give that a go… Ive got loads of bios for the ps1 so ill try scph 101, which I used to use on epsxe.

AWSOME EMULATOR THOUGH!!

@Tanuki

Thanks for that… I also mentioned that I used NEO.EMU, now I dont know what the developer is using there but its a fairly new app so… I dunno.

Can you post a link to a site for roms which work on retroarch??

Thanks dude.

[quote=“Michigunskiy”]

Maybe HDMI-OUT work with “no lag”, but i dont have it. I have only composite 3,5 mm jack out on board with PAL/NTSC support via special apk tool.
To my regret ICS Firmware for JXD-S601 is not provided by the manufacturer. Only custom firmware with lots of bugs and without TV-OUT, and the kernel is lock at 600 MHz only vs. Gigerbread 800-1000 MHz firmware kernel.

On the device all emu works fine, but when I connect him to tv = “bullet time” effect in the any 2D emulators and RetroArch PSX too. Helps only manual frameskip = 1 in NTSC mode.[/quote]

Yes, I get the same lag as well with Android 4.0.4 (CM9) on an underpowered Cortex A8 tablet when I hook up with HDMI TV-Out. Still, I really don’t like the idea of adding a frameskip option just because TV-Out used to really suck before Android 4.1 came along. It just feels like a bad workaround overall and really - it’s not even a real ‘solution’ - it’s just an optical illusion trick to make the lag seem ‘less worse’ even though it is still all there - just skipping a few frames and therefore making the jerky motion seem more natural.

Anyway, I’ll talk it over with the other devs - dunno if we should succumb to end-user pressure on this front. Either something is running at fullspeed or it’s not - there can be no 'inbetween 'here - it either runs good and is playable or it doesn’t run fullspeed and therefore it’s useless and not worth playing. And playing TV OUT games with frameskip 1 to me definitely belongs in that latter category there.

@Tanuki

I forgot to metion aFBA 1.6…

The neo geo roms work on this but not full burn alpha(arcade) on retroarch…?

Can you please tell me why that is??

Last time he worked on that thing was 3 months ago - a lot happens within the space of 3 months in FBA land - for the exact same reason - they sync with the MAME romset.

Really man - these games run just fine on my end - it’s a problem on your end - period. Find the right ROMs already instead of arguing with people who know as an absolute fact it runs Neogeo games just fine right now.

Maybe HDMI-OUT work with “no lag”, but i dont have it. I have only composite 3,5 mm jack out on board with PAL/NTSC support via special apk tool.
To my regret ICS Firmware for JXD-S601 is not provided by the manufacturer. Only custom firmware with lots of bugs and without TV-OUT, and the kernel is lock at 600 MHz only vs. Gigerbread 800-1000 MHz firmware kernel.

On the device all emu works fine, but when I connect him to tv = “bullet time” effect in the any 2D emulators and RetroArch PSX too. Helps only manual frameskip = 1 in NTSC mode.[/quote]

Yes, I get the same lag as well with Android 4.0.4 (CM9) on an underpowered Cortex A8 tablet when I hook up with HDMI TV-Out. Still, I really don’t like the idea of adding a frameskip option just because TV-Out used to really suck before Android 4.1 came along. It just feels like a bad workaround overall and really - it’s not even a real ‘solution’ - it’s just an optical illusion trick to make the lag seem ‘less worse’ even though it is still all there - just skipping a few frames and therefore making the jerky motion seem more natural.

Anyway, I’ll talk it over with the other devs - dunno if we should succumb to end-user pressure on this front. Either something is running at fullspeed or it’s not - there can be no 'inbetween 'here - it either runs good and is playable or it doesn’t run fullspeed and therefore it’s useless and not worth playing. And playing TV OUT games with frameskip 1 to me definitely belongs in that latter category there.[/quote]

Many thanks for the explanation of this problem. I agree with you about this issue. Better to play well without “lags” on the device screen, than “jerky” playing on old CRT-TV.

Quick menu without use my resistive tochscreen is more need for me than TV-Out fix.

This is not the pressure from my side. I just asked a question for add this if possible… Anyway RetroArch Playstation 1 emu core is great. And for me it work definitely smooth,fast and compatible than FPse and ePSXe, even if they do not slow down with TV-Out on my device without FS, but slow down at many PSX games.

Thanks again for porting RetroArch on Android 2.3

Do you plan to add support for Android 2.2? It would be great to run RetroArch on the Android STB (ARM V7) 1-GHz device like A.C.Ryan VEOLO or Pearl Meteorit MMB-422! I think there should be any lags on TV play. I test FPse and ePSXe it work well and smooth on my MMB-422 , but slow 25-40 fps. Like as on JXD-601 with 1Ghz core. 2D Emulators like Nesoid,Gensoid,Snesoid,Tiger arcade run great on both device without any frameskip.

scph101 and scph7502 won’t work (at least for me). For MGS you need exactly scph1001.bin in the same folder.

@Squarepusher, thank you so much for adding Android 2.3 support! I have some minor requests if you don’t mind of course, it shouldn’t be so hard to implement:

  • can you please add such handy feature as ‘recently played games’ list of 5-7 titles?
  • in the “Path Settings” 't would be nice if you add option for custom shaders folder too.
  • what if pressing “back” button may show up ‘yes/no’ confirmation box first instead of stoping emulation at once? This would prevent accidental closings on some devices

hi guys, a suggestion regarding ROMs if I may - the most common complaints are from people trying to source the correct ROMs - could you please release a .DAT file that has the XML data for the correct ROMs / CRCs etc. using a tool like CLRMAME, Romulus, DatUtil, RomVault etc.?

Then if users download the .DAT file on their desktop / laptop they can then ‘build’ a correct 100% ROM list for use on their mobile / tablet / console.

This would then hopefully reduce the number of complaints about retroarch not working etc.etc.

I’ve been getting e-mails like this -

How do us noobs use this? There isnt any description on how to use this. youtube videos suck just as bad when it come to a simple explanation on how to play games with this. How do you expect noobs to utilize this application!!!

And honestly, the more responses I get like this (and 1 stars like this), the more I feel tempted NOT to do ANYTHING as far as making it ‘more noob-friendly’. I know that it being free makes them feel entitled to this or that but really - PC and console emulators have ALWAYS expected of the user that users have a basic frame of reference as to what they need to do with this thing - it isn’t hard - I know that we’re dealing with Generation Idiocracy these days but honestly - if you can’t figure out the procedure of how to play a game with these cores, then said person is not exactly the sharpest nail in the box.

They don’t want to read a PDF? Then that confirms what I’ve said before. I didn’t even have to go to the length of providing a link to a PDF with most of the information they would need - it was a lot of work writing all that and most other people wouldn’t have even felt like doing that all for free in the first place. I don’t see Broglia doing this - I don’t see any of the guys doing this - yet because I’m free and they’re not, I apparently have to spoonfeed these people.

I don’t feel like spoonfeeding them just because these users think they can somehow ‘persuade’ the author/developer to do certain things because they think this irrelevant ‘stars rating system’ on a Play Store gives them bargaining power.

I also got requests to build in a ‘ROM search utility’ with the caveat ‘It may be a little illegal’ - seriously, the moment you start appealing to this kind of stupid stuff, it will never end and it will just get more and more ridiculous. Best not to go there entirely.

@squarepusher

Who’s arguing dude? Im merely informing that the roms work fine in 3-4 different emulators including full burn alpha 1.6 but they do not work on full burn alpha on retroarch…?

Does that sound like arguing or just someone giving feedback so the devs can sort out the problem??

In future, if you’e got nothing worthwhile to say, then I suggest you keep quiet.

Squarepusher is one of the devs, so anything he has to say regarding this is worthwhile, even if what he says is “no.”

Im gonna test today again this mother of all emulation applications, trying to get working my arcade stick on a hdmi connected tablet. Retro console everywhere ftw!!

Just a few questions for being curious:

-Is there any plan on adding any more cores to the Android port?

-Any more customization options general/per core in the future?

-How many people is involved in this project?

Again, thanks for your hard work, few years ago this was unbelievable, having all this emus on a handled device.

Cheers!!

Squarepusher, I’m really sorry to hear about all the idiots and I hope you don’t think I’m one of them. I just really like this project, I want it to be even better, and I try to contribute the only way I can by reporting bugs/issues and suggesting improvements.

I think having some way of verifying an image could be a good idea, but personally it’s mainly so that I can avoid giving false bug reports, and I fully understand if you don’t want to bother with it.

Can you post a link to a site for roms which work on retroarch??

No. You have enough information in this thread and in the FAQ to get started. Show me you are willing to do a bit of work by yourself and maybe I’ll help. And lose the attitude. Seriously.

could you please release a .DAT file that has the XML data for the correct ROMs / CRCs etc. using a tool like CLRMAME, Romulus, DatUtil, RomVault etc.?

There is no need to release anything. The DATs in question are already out there. The FBA Core in RetroArch is Final Burn Alpha (made into a library that is “talked to” by RetroArch). As we speak, the FBA Core is Final Burn Alpha 0.2.97.28. Thus, all you need to do is generate the Arcade DAT from the “real” Final Burn Alpha (from the Misc Menu IIRC) and import it in ClrMAME.

For cartridge based console, no-intro is usually better and for CD-based systems images from the Redump project are almost guaranteed to work. EDIT: There are DATs for that too =)

I would volunteer to write a quick tutorial about sane ROM management when the wiki is up but then again, Squarepusher pretty much underlined where the problem lies… I guess that was to be expected going into Android and its wide-reaching user base.

Thanks for this port.

One thing I noticed on my Nexus 7 is that the joystick on my MOGA controller does not work in analog mode. The manual says to make sure ’Enable left analog input’ is checked, but I found that it only works when this option is unchecked.

It’s not really a big deal to me, just thought I’d report it.

edit: I checked and there are no keycodes reported from the sticks in analog mode, not sure if that’s normal or not.

Haven’t gotten around to that yet.

Proper ‘joystick support’ is another of these borked ‘halfway there’ things of the NDK - AFAIK you have to do dlopen hacks to ‘check’ if joystick support is there on your OS and then ‘grab’ function pointers to it.

We’ll have to try to sort out that stuff. Suffice it to say it isn’t exactly fun.

Ah, ok.