good work! you should add that log to the github issue linked on the previous page. i’m not sure, but it seems like it crashed during dfinput_activate ? this area was changed by the multitap commits, so maybe they are the problem.
maybe the android build shouldn’t bother with these commits for now? a lot of android devices wouldn’t be able to support 3+ controllers anyway, right?
As far as I know the shield devices support at least 4 or more controllers.
I was playing MAME on my Shield TV and tested 4 players 
There are also PSX games that support 5 players, such as Micromachines V3 - this is actually the game I wanted to play on retroarch in the living room with my friends
I’m having this exact same issue on my Shield (Android 5.1). Thought I was crazy! I verified my ROMs / BIOSes are working with Mednafen.
Has there been any update on a fix? Or did someone already fix it?
any fix and you will see it on the github issue, although one dev has updated on here a bit: https://retropie.org.uk/forum/topic/1673/lr-pcsx-rearmed-runcommand-sh-line-804-5728-segmentation-fault-since-3-8
I have 2 ShieldTVs, one a setup a while ago and is working fine with PSX Rearmed. The other one I just set up and I can’t get either PSX core to work. Frirckin tried everything. Just quits.
rclong: try running interpreter mode in the core options. It’ll be slower but a shield can probably still get full speed.
I can’t get the core to run anything so I can’t get to the core options. Mednafen PSX, either.
Here’s a post from another thread. If you’re crashing from startup, try this. Just manually replace the core’s .so file.
The problem you’re describing is exactly the problem i had,
[QUOTE=talos91;39312]Here is the last working version of the core for android: http://www109.zippyshare.com/v/eb1lVNDn/file.html[/QUOTE]
Download the .so core file, and go into your /data/data/com.retroarch and into the cores directory, and copy it over, and it’ll ask if you want to replace the existing file, hit yes of course. Just posting the quote here for other people. Someone needs to go back and replace the PSX core in the nightly/latest with this older one. would save a lot of headaches. The one Talos linked works perfectly for me, 60fps on any game i throw at it, with enhanced resolution enabled.
It stopped working a long time ago. I can’t remember when exactly, but I would say about 1 month.
[QUOTE=LazyBunny;40976]Here’s a post from another thread. If you’re crashing from startup, try this. Just manually replace the core’s .so file.
The problem you’re describing is exactly the problem i had,
Download the .so core file, and go into your /data/data/com.retroarch and into the cores directory, and copy it over, and it’ll ask if you want to replace the existing file, hit yes of course. Just posting the quote here for other people. Someone needs to go back and replace the PSX core in the nightly/latest with this older one. would save a lot of headaches. The one Talos linked works perfectly for me, 60fps on any game i throw at it, with enhanced resolution enabled.[/QUOTE]
Thanks that worked! 
my quotes were from talos91, he’s the one that fixed it, i was just relaying the fix. cause it’s the best fix so far. That talos91 person is awesome. ~_^
It seems the crashing is related to a recent commit related to multitaps. We’ll try to get it fixed in the nightlies soon.
[QUOTE=LazyBunny;40976]Here’s a post from another thread. If you’re crashing from startup, try this. Just manually replace the core’s .so file.
The problem you’re describing is exactly the problem i had,
Download the .so core file, and go into your /data/data/com.retroarch and into the cores directory, and copy it over, and it’ll ask if you want to replace the existing file, hit yes of course. Just posting the quote here for other people. Someone needs to go back and replace the PSX core in the nightly/latest with this older one. would save a lot of headaches. The one Talos linked works perfectly for me, 60fps on any game i throw at it, with enhanced resolution enabled.[/QUOTE] I can’t find the directory. do you need root?
I personally did with my file browser, but i think someone mentioned in http://libretro.com/forums/showthread.php?t=6070 it’s not actually required.
Edit: i have a feeling hunterk is going to either upload the older one, so it’ll at least work (old working is better than new broken) Or he’ll fix the newer one, sounds like he knows the cause.
The buildbot will just overwrite the older version if I manually replace it on the server, so we’ll just try to get the fix pushed up ASAP. If it ends up being harder to fix than we hope/suspect, we can revert the multitap commits.
So I have an issue finding the cores folder. I don’t know if anyone will have any insight but I might as well take a shot in the dark. According to Retroarch, the cores are stored here: “data/user/0/com.retroarch” when I go into my file browser and try to back out to find “data” it isn’t there. Note that it’s not stored in “Android/data”, where there are some Retroarch things sure, but not cores and a few other important things. I feel very sheepish looking for this for days now and I can’t find it. If I change the cores directory, they won’t start, I assume because other important things are in this elusive “data” root. How can Retroarch default to a directory that doesn’t seem to exist and yet if I try to direct it’s attention to directories that do exist, it breaks?! Please go easy on me.
It’s definitely not in the android folder the data/user/0/, is actually data/data/ it’s just another way of linking to the same folder. I used the cyanogen file explorer, with root/superuser access. So you may need to get rooted. Maybe the latest psx emu will be working soon.
People are confronting the cores directory issue in the Thread “Retroarch via Intent and putExtra(“LIBRETRO”, corePath)”, OBB and data files aren’t typically displayed without root as far as I know. We’ll see what pans out…