RetroArch Android releases (v0.9.8.4 - r12) (Page 1 of 11)

Good work on it, happily testing it all out now!

glad to hear about another release, however i just have a hopefully simple request.

as a porter for the OpenBSD project, it would be very nice to have the distfiles for the previous releases still be around, that way if in the interim the OpenBSD port still refers to a slightly older version, the link won't be broken right away.  Hopefully diskspace isn't too much of an issue here.  The port is still new and not committed yet so I can easily upgrade to the newest version now, but in posting the port to get testing we were immediately shut down when the 0.9.7 src tar was missing.

without causing the project too much duress in terms of storing old releases and 'how old is old enough to keep' perhaps a years worth of releases would be safe? the OpenBSD project itself releases every 6 months so as long as i am doing my duties the port would be able to follow at that schedule.  This could help the other bsds and any linux distros that use distfiles from the main project site.

presently i was only interested in retroarch exclusively for the libretro-bsnes core (i actually made the port when it was ssnes and libsnes-bsnes still)

thanks TheMaister for allowing me to get a working bsnes on OpenBSD!

one more quick question about libretro-bsnes:
i see two git repos, one on github (seems old) and one on gitorious (seems new)

the github one specifies c++98 the other doesn't, neither seem to have release tarballs.  the port i made for it tries the github link by requesting the tarball checkout, but it would be cool to have a real version to refer to.  does the gitorious tree still compile nicely like the github one?  are there plans to make an official release of the core?

cheers

Great news, def gonna try it on my tablet, thanks a lot!

Congrats and many thanks on this release!

I can't imagine the work that went into the Android version. It delivers on so many levels! I've been enjoying it on an "antiquated" Iconia a500 (Tegra 2, CM10 JellyBean 4.1.2) with a Saturn USB gamepad and the scanlines shader. Very impressive stuff.

Even games like R-Type Delta and Wipeout 3 are smooth (except for a few CD-DA hicups). I'm probably missing out on the NEON stuff though.

I can already see Yinlips/JXD jump on it and make RetroArch their defacto "classic games emulator" in future devices... I read the disclaimer about commercial derivatives but what's your take on that?

@Squarepusher, many thanks for finally releasing RetroArch for Android!!! I can't believe you guys give all those treasures free for us. God bless you all! 
I currently own one of these Yinlips devices and what I wanted to ask is if Android 2.3 will be supported too (maybe in future releases)?? 'Cause every ICS firmware available for this bastard is sooo buggy and battery draining... Any hope??
Thanks in advance and excuse my English!

This might be a stupid question but is there a way to configure a joystick?

I have one of the JXD consoles running ICS so i've got a set of buttons which seem to act as a gamepad. When I run the debug mode on input I get the following keycodes returned

up :    pad 0 19
down:   pad 0 20
left :  pad 0 21
right:  pad 0 22
...
etc

Is it possible to copy these values into the retroarch.cfg?

Great, the device im using is one of these:
http://www.jxd.hk/products.asp?id=611&a … sid=009006

the device name comes up as something quite generic..

HID [matrix_keyboard] unbo - the text goes off the screen at this point..

but after some digging i found the following in /proc/bus/input/devices

I: Bus=0017 Vendor=0001 Product=0001 Version=0001
N: Name="matrix_keyboard"
P: Phys=gpio-matrix-kbd/input0
S: Sysfs=/devices/platform/matrix_key.0/input/input3
U: Uniq=
H: Handlers=kbd mouse0 event3 
B: EV=b
B: KEY=400 db0000 0 0 0 0 0 1680 0 2000000 10000000
B: ABS=2650000 3

Button mapping is as follows:

d-pad

up :   19
down:  20
left : 21
right: 22

square:   100
x:        97
circle:   96
triangle: 99
select:   62
start:    66

left shoulder: 102
right sholder: 103

strange button with 4 squares on: 82
back button will exit the app so can't get a code 

Here is what i found with testing the PS3's Control Pad, not sure if it will be helpful, but posting anyway

PS3 Control Pad Button Mapping:

D Pad
up =  19
down:= 20
left = 21
right = 22

square = 96
x = 99
circle = 100 - Enters directories and selects
triangle = 97
select = Exits Emulator, cant get code
start = 100

L1 = 102
L2 = 104
L3 = 106

R1 = 103
R2 = 105
R3 = 107

PS Home button Exits Emulator.

Bravo gents, wore a giant smile all night revisiting classics thanks to your brilliant effort.

Retroarch works nearly flawlessly on a 50 dollar MK808b android stick hooked up to an HDTV.  The only weirdness I encountered was that if a mouse is plugged in, gamepad controls will not work.  Unplugged the mouse, and my DualShock3 works perfectly.  That and  despite my tinkering, I couldn't get the Wonderswan core to work, even with roms that work fine with Wonderdroid?

Thank you all.  Which way do I send a donation?

The core manual PDF is made to be generic and to apply to all ports - unfortunately in this case, it's a bit TOO GENERIC.

On Android we decided not to bother with a system directory because we can't exactly 'assume' a default directory or make it easy for users to drag the files to it - instead, the required BIOS file(s) should be in the same directory as the game you're trying to load.

Can't be done right now, but it's definitely something I want to add - I am thinking of 'binding' this to the 'Menu' button of a gamepad - ie. the DualShock3's 'PS button' or the 360 pad's '360' button.

Anything will go. I want as many devices reported to me as possible so we'll throw in autodetection support for all of them. I want this to be as close to a 'console port' as possible in terms of 'plug and play' factor.

This is definitely a glaring omission I made - part of it is that the Saturn lacks a 'Select button' so I wasn't sure what to map it to. Z or C is fine according to you?

Would have to look if it suits our purposes.

Yeah we know. We also knew beforehand that we would get bitching about touchscreen overlays even though the big 'plus point' here is that it's all user-customizable (might need a user-friendly WYSIWYG editor though before they'll jump on it).

Unsure about this - I guess for now we'll make a separate stickied thread for reporting new input keycodes.

I want to make RetroArch stretch across every architecture and every platform pretty much. However, up until now I've been taking money out of my own pocket to make this a reality, and now that you people can see that I delivered good on my promises, I would hope you guys could 'support' me getting RetroArch ported to as many new platforms as possible for free. You can help me in this by gifting me the hardware that is necessary to do this - for instance, I'm still on the lookout for an iPad 2 so that I can port RetroArch to that and put it up on Cydia for free.

Monetary donations I will never accept - and I hope the same applies for the other teammembers because as soon as money enters into the equation, it rapidly degenerates into sour grapes and envy and then the project falls apart. In a way, these 'gifts' could invite  a whole lot of envy and greed as well - so I'm even unsure about that aspect -but one thing is for sure - it sure as hell beats going the cynical route of 'Kickstarter projects' - and there's no way I'll be able to get an Ouya or insert whatever 'open device' that is free that will get released down the line - something suitable for RetroArch.

So if the interest is there, we'll be on other platforms from this point on as well that people would like to see.

Froyo is so old it can't ever be supported because that was before native activity support was even introduced.

And yes, upgrading your ROM to a much more recent version (ICS/Honeycomb) would do the trick - but I'm not sure if the specs of your phone would be up to snuff for those newer OS versions.

EDIT:

http://forum.xda-developers.com/wiki/ZT … ifications

Looks like an ARMv6 CPU. That's way too old for the RetroArch APK on the Play Store right now. Only way for it to work (that is - IF you upgrade the OS) is if somebody would compile it from source, leave the ARMv5-compatible binaries in and then distribute the APK.

I dunno - perhaps we could provide a separate APK - ARMv5 compatible - but it would turn into a big mess to maintain. Not sure if that's worth pursuing since these phones are on their way out anyway.